aws-cloud-collector is not collecting data

Hello!
I have installed the the aws-cloud-collector in a EC2 instance with an IAM role with administrative permission. I have installed mongoDB 3, java8 and the EC2 monitoring feature is enabled. When I tried to run the collector, it seems to connect to mongoDB and the EC2 credentials seems to be fine as well. The collector is running but there is nothing in mongo database.
Here is a few lines of the log file of the aws-cloud-collector:
2016-07-16 15:05:59.540  INFO 24542 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup 2016-07-16 15:05:59.553  INFO 24542 --- [           main] com.capitalone.dashboard.Application     : Started Application in 7.975 seconds (JVM running for 8.768) 2016-07-16 15:10:00.000  INFO 24542 --- [taskScheduler-1] c.c.dashboard.collector.CollectorTask    : Running Collector: AWSCloud 2016-07-16 15:10:00.006  INFO 24542 --- [taskScheduler-1] c.c.dashboard.collector.CollectorTask    : Starting AWS collection... 2016-07-16 15:10:00.012  INFO 24542 --- [taskScheduler-1] c.c.dashboard.collector.CollectorTask    : Collecting AWS Cloud Data... 2016-07-16 15:10:02.078  INFO 24542 --- [taskScheduler-1] c.c.dashboard.collector.CollectorTask    : Finished Cloud collection.
Here is a mongoDB data:

db
dashboard
show collections
authentication
cloud_instance
cloud_instance_history
cloud_subnetwork
cloud_virtual_network
cloud_volume
collectors
feature
scope
system.indexes
db.cloud_instance.count()
0
db.collectors.find()
{ "_id" : ObjectId("57897450c0a8fc0b25754c46"), "_class" : "com.capitalone.dashboard.collector.AWSCloudCollector", "name" : "AWSCloud", "collectorType" : "Cloud", "enabled" : true, "online" : true, "lastExecuted" : NumberLong("1468683901286") }

This is a part of the aws.properties file:
AWS ValidTag Key - To look for tags that you expect on your resource
aws.validTagKey[0]=Name
aws.validTagKey[1]=Profile
AWS Proxy Host
aws.proxyHost=
AWS Proxy Port
aws.proxyPort=
AWS Non Proxy
aws.nonProxy=
AWS Profile to be used if any
aws.profile=
Well, all counts return 0 value...
What am I doing wrong?
Thank you!

It will start collecting data once you configure the cloud widget in Dashboard, which is visible when you have configured the deploy widget, it requires your AWS account number and a tag you want to filter on, if you dont supply a tag you see every thing

Ok, I went to AWS Cloudwatch console -> Dashboard - > create new Dashboard
Then, Add witget -> select metrics ->  select all interested metrics -> Save.
Now, I have a Dashboard with a graph in that screen....
I didn't catch this "which is visible when you have configured the deploy widget,t, it requires your AWS account number "
Thanks!

you don't have to go to AWS CloudWatch console, you need to create a new Hygieia Dashboard and configure the deploy widget.

Ahh! okok, What if I want to use the aws-cloud-collector as standalone process. I want to collect data and the process that data...

Once configured you will see something like below
Here

@gfpalacios that work is in progress, we are going to separate this and make it as a standalone product though integrated with Hygieia

Excellent! I am really interested on that collector. Thank you!

Hi @amitmawkin , I'm with the same problem as @gfpalacios , I cannot see anything on my dashboard, what do you mean 'configure deploy widget' ? I thought udeploy was the only option of deploy widget.

@rodrigosiviero @gfpalacios The latest changes should solve the problem of cloud widget only getting displayed when deploy widget is configured.
If the issue still exist please open a new one, closing this due to no activity

@gfpalacios  @amitmawkin
Hello, I am unable to get the aws cloud collector to work and I know it has everything to do with the properties file.
Can you guide me what should the respective fields in the properties file should contain.

Hi,
I am also facing the same issue.
The properties file is as below
Database Name
dbname=dashboarddb
Database HostName - default is localhost
dbhost=localhost
Database Port - default is 27017
dbport=27017
Database Username - default is blank
dbusername=*****
Database Password - default is blank
dbpassword=****
Logging File location
logging.file=./logs/cloud.log
Collector schedule (required)
aws.cron=0 0/5 * * * *
AWS ValidTag Key - To look for tags that you expect on your resource
aws.validTagKey[0]=
aws.validTagKey[1]=
aws.proxyHost=
aws.proxyPort=
aws.nonProxy=
aws.profile=default.
The collector starts up fine without any error. But no data is collected in the DB.
2017-08-24 14:30:00,000 INFO  c.c.d.collector.CollectorTask - Running Collector: AWSCloud
2017-08-24 14:30:00,018 INFO  org.mongodb.driver.connection - Opened connection [connectionId{localValue:8, serverValue:161}] to localhost:27017
2017-08-24 14:30:00,022 INFO  c.c.d.collector.CollectorTask - Starting AWS collection...
2017-08-24 14:30:00,022 INFO  c.c.d.collector.CollectorTask - Collecting AWS Cloud Data...
2017-08-24 14:30:03,759 INFO  c.c.d.collector.CollectorTask - Finished Cloud collection.
2017-08-24 14:31:46,826 INFO  org.mongodb.driver.connection - Closed connection [connectionId{localValue:8, serverValue:161}] to localhost:27017 because it is past its maximum allowed idle time.
aws s3 ls command also works fine. and displays the correct result.


Integrate siibra-cli as an optional package

Integrates siibra-cli as an optional package.
pip install siibra[cli] (to test pip install -e ./[cli] in siibra-python directory).
@dickscheid Let us use this PR to discuss the scope and design of the cli.

IMO, cli of siibra
must do:

Download maps/masks/meshes (using to_zip see #554 )
Provide a summary for feature query with a concept and feature type
Get a description and citation information on atlas concepts
Get related region information
should do:
Save plots of the features as pngs to working directory.
Download feature data (using to_zip)
Create links for viewer

What do you think @dickscheid?


Hook after download

I would love the ability to specify some sort of hook to run on downloaded/requested assets.  Could happen synchronously or asynchronously for my purposes (maybe even preferable asynchronously).  I'd see it as dispatching an action to the RBE scheduler, but probably lots of ways to skin that cat.
I'd use it to unpack and directly upload all constituent files into the CAS.  This way clients aren't downloading large assets only to unzip and upload them right back.
I'd also use it to log assets I'm using and maybe automatically mirror them into persistent object storage that I control (a la mirror.tensorflow.org).
Another use, less personally interesting, would be to enforce policy (whitelisting sources), etc.

Unpacking zips at the asset server level is definitely something that makes a lot of sense. I'm not sure how the clients currently behave and whether or not they fetch the zip regardless.
We definitely discussed this at one point as a bonus towards implementing the remote executor fetcher. Although I think it would likely be more standardised build actions such as unpacking zips rather than user customizable actions as it would be tricky to support these in situations without a remote executor configured.
This related issue is a little old but definitely has overlap https://github.com/buildbarn/bb-remote-asset/issues/10


TypeError: init() got an unexpected keyword argument 'loss_attr'

Hi there !
I got following error:
Traceback (most recent call last):
File "demo/test_attr_predictor.py", line 62, in
main()
File "demo/test_attr_predictor.py", line 45, in main
model = build_predictor(cfg.model)
File "/home/inomjon/.conda/envs/mmfashion/lib/python3.8/site-packages/mmfashion-0.4.0-py3.8.egg/mmfashion/models/builder.py", line 87, in build_predictor
return build(cfg, PREDICTOR)
File "/home/inomjon/.conda/envs/mmfashion/lib/python3.8/site-packages/mmfashion-0.4.0-py3.8.egg/mmfashion/models/builder.py", line 38, in build
return _build_module(cfg, registry, default_args)
File "/home/inomjon/.conda/envs/mmfashion/lib/python3.8/site-packages/mmfashion-0.4.0-py3.8.egg/mmfashion/models/builder.py", line 30, in _build_module
return obj_type(**args)
TypeError: init() got an unexpected keyword argument 'loss_attr'
please guide, thanks!

same error

Yes I'm having the same issue. Anyone got a solution for this?

I'm having the same issue. How to solve this?

I add 'loss_attr' to mmfashion/models/predictor/global_predictory.py init() input
def init(self,
backbone,
global_pool,
attr_predictor,
loss_attr,  # add Here
cate_predictor=None,
roi_pool=None,
pretrained=None):
It's work for me

I add 'loss_attr' to mmfashion/models/predictor/global_predictory.py init() input
def init(self,
backbone,
global_pool,
attr_predictor,
loss_attr, # add Here
cate_predictor=None,
roi_pool=None,
pretrained=None):
It's work for me

Thanks，I tried, but nothing changed.

I added that lost_attr paramerter to the init() method and it still won't work for me... can you explain further @genesysvip ?

same

i found it .. you should at it in the /usr/local/lib/python3.6/dist-packages/mmfashion-0.4.0-py3.6.egg/mmfashion/models/predictor/global_predictor.py .. thats for me .. and it's working now

One thing to note, when you change the mmfashion/models/predictor/global_predictory.py, don't forget to rerun the install command.

This issue has yet not been resolved!!


Sponge plugin badges

:clipboard: Description
These badges would be for Sponge plugins via Ore. They would be in the following formats (taking LuckPerms as an example):

:link: Data

Ore's public API is documented here. There's no API key required, although it requires a session to be created.
LuckPerms's API response looks like this:
URL: https://ore.spongepowered.org/api/v2/projects/luckperms
{
  "created_at": "2017-02-01T18:58:17.19",
  "plugin_id": "luckperms",
  "name": "LuckPerms",
  "namespace": {
    "owner": "Luck",
    "slug": "LuckPerms"
  },
  "promoted_versions": [
    {
      "version": "4.2.17",
      "tags": [
        {
          "name": "Sponge",
          "data": "8.0.0-SNAPSHOT",
          "display_data": "8.0",
          "minecraft_version": null,
          "color": {
            "foreground": "#333333",
            "background": "#F7Cf0D"
          }
        }
      ]
    },
    {
      "version": "4.1.7",
      "tags": [
        {
          "name": "Sponge",
          "data": "6.0.0",
          "display_data": "6.0",
          "minecraft_version": null,
          "color": {
            "foreground": "#333333",
            "background": "#F7Cf0D"
          }
        }
      ]
    },
    {
      "version": "3.0.14",
      "tags": [
        {
          "name": "Sponge",
          "data": "5.0.0",
          "display_data": "5.0",
          "minecraft_version": null,
          "color": {
            "foreground": "#333333",
            "background": "#F7Cf0D"
          }
        }
      ]
    }
  ],
  "stats": {
    "views": 56378,
    "downloads": 20231,
    "stars": 81
  },
  "category": "admin_tools",
  "description": "An advanced permissions plugin",
  "last_updated": "2019-12-27T23:50:23.984",
  "visibility": "public",
  "user_actions": {
    "starred": false,
    "watching": false
  },
  "settings": {
    "homepage": null,
    "issues": "https://github.com/lucko/LuckPerms/issues",
    "sources": "https://github.com/lucko/LuckPerms",
    "support": null,
    "license": {
      "name": "MIT",
      "url": "https://github.com/lucko/LuckPerms/blob/master/LICENSE.txt"
    },
    "forum_sync": true
  },
  "icon_url": "https://ore.spongepowered.org/Luck/LuckPerms/icon"
}

:microphone: Motivation

Sponge is a platform for server-side modding of Minecraft servers, and is Spigot's main competitor in that field. shields.io already has great badges for Spigot plugins via Spiget, but no such badges for Sponge plugins via Ore (the official plugin repository). This would allow Sponge plugin developers to display information in badge format about their Sponge plugins on GitHub or a documentation site.

Sessions seem to last for three hours, so it would indeed be beneficial to cache them. Storing the session key as property in the service class and getting a new one when it expires could be a simple way of handling this!


Preserve routing suffix on Linux

Do not overwrite OC_CLUSTER_ROUTING_SUFFIX if I already set it in my environment

@jorgemoralespou ptal

@csrwng thanks


When $scope is injected in a controller it appears to create dependency issues with Angular.mock.inject

For example given a controller:
.controller('View1Ctrl', ['$scope', function($scope) {
}]);

and a test:
describe('myApp.view1 module', function() {

	beforeEach(module('myApp.view1'));

	describe('view1 controller', function() {
		it('should ....', inject(function($controller) {
			//spec body
			var view1Ctrl = $controller('View1Ctrl');
			expect(view1Ctrl).toBeDefined();
		}));
	});
});

An error is given:
Error: [$injector:unpr] Unknown provider: $scopeProvider <- $scope <- View1Ctrl
The error is no longer present once the $scope injection is removed. The issue appears to be specific to $scope as other dependencies appear to work.
This can be quickly tested by cloning: https://github.com/tnajdek/angular-requirejs-seed.git
then adding the $scope injection in app/view/view1.js to see the error.

This is because $scope is not some sigleton service that can be directly injected. It is a Scope object that needs to be created (usually specifically for that controller instance).
Normally, Angular takes care of creating $scope and passing it to the controller, but when using the $controller service, you have to create it manually and pass it via locals. E.g.:
it('...', inject(function ($controller, $rootScope) {
  var scope = $rootScope.$new();
  var ctrl = $controller('...', {$scope: scope});
}));

--
Closing as it works as expected.

@gkalpak Thanks for clearing that up for me. I've re-reviewed the docs and it does state the $scope needs to be provided when using the $controller service. I should read more carefully. Thanks again.


Added attributes property to customer.

I had the need for adding the custom attributes property on the customer object. I've tested this code and it successfully updates custom customer attributes on a live Magento site.

Thank you for the PR. I'll create a new nuget package soon.


Generate and interpret ParseInstruction

[ch2310]
[ch2388]

There's likely some low-hanging fruit in the RValue interpreter implementations that we can address in this PR. But since all the tests are passing and the affected queries are running as fast as in master (checked this manually in the REPL), I wanted to get the ball rolling with this PR as is.

@wemrysi I pushed the changes I have planned. Still waiting for the travis build to start though; I'll keep an eye on it.


Add rehype-preset-minify

This allows the minification of blog posts.

There's no need for the plugin as both esbuild which is used by mdx-bundler and webpack / swc from nextjs will take care of it. It's intended for use in standalone applications.

Adding the plugin does have an effect (-> right-click -> view source):

source of a blog post without the plugin
source of a blog post with the plugin

esbuild / webpack / swc do minify the page but not the blog post.
It would probably make more sense to configure these build tools such that the blog post (and e.g. the json starting in line 2) is also minified. However, I haven't looked into the build setup too closely to fix this.

Thanks, good to know. Can we try turning on the minify option in esbuild? Mdx-bundler has an example over here. Would prefer this approach over a rehype plugin if this works.

I'm not seeing any minification when using options.minify = true in the esbuildOptions.

Took a deeper look into this issue. Mdx-bundler sets minify to true by default. Changing it to false does show a difference.
The output from xdm is probably treated by esbuild as a string literal and it does not minify it. Hence the plugin is required, if we truly want to minimize the size of HTML over the wire. It seems to be relatively minor about 6% smaller and am not too sure how much longer it takes to process but happy to merge in the change. Thanks!


Support opentelemetry sementic convention

Description
Support opentelemetry sementic convention
Issue reference
https://github.com/dapr/dapr/issues/1607
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[x] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test


can't seem to get npm run test:server to pass

npm info ok
npm info it worked if it ends with ok
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm WARN using --force I sure hope you know what you are doing.
npm info lifecycle malice@5.5.0~pretest:server<EMAIL_ADDRESS>npm info lifecycle malice@5.5.0~test:server<EMAIL_ADDRESS>
><EMAIL_ADDRESS>test:server /plugin/malice
> plugin-helpers test:server

  suite
    1) is a test test

  0 passing (170ms)
  1 failing

  1) suite is a test test:
     Error: expected true to equal false
      at Assertion.assert (node_modules/expect.js/index.js:96:13)
      at Assertion.be.Assertion.equal (node_modules/expect.js/index.js:216:10)
      at Context.it (server/__tests__/index.js:5:21)

child_process.js:504
    throw err;
    ^

Error: Command failed: /plugin/kibana/node_modules/.bin/mocha --require /plugin/kibana/test/mocha_setup.js server/**/__tests__/**/*.js
    at checkExecSyncError (child_process.js:481:13)
    at execFileSync (child_process.js:501:13)
    at module.exports (/plugin/malice/node_modules/@elastic/plugin-helpers/tasks/test/server/test_server_action.js:22:3)
    at run (/plugin/malice/node_modules/@elastic/plugin-helpers/lib/run.js:9:10)
    at /plugin/malice/node_modules/@elastic/plugin-helpers/cli.js:75:5
    at Command.actionWrapper (/plugin/malice/node_modules/@elastic/plugin-helpers/cli.js:12:8)
    at Command.listener (/plugin/malice/node_modules/commander/index.js:300:8)
    at emitTwo (events.js:106:13)
    at Command.emit (events.js:191:7)
    at Command.parseArgs (/plugin/malice/node_modules/commander/index.js:635:12)
npm info lifecycle malice@5.5.0~test:server: Failed to exec test:server script
npm info lifecycle Error<EMAIL_ADDRESS>test:server: `plugin-helpers test:server`
npm info lifecycle Exit status 1
npm info lifecycle     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
npm info lifecycle     at emitTwo (events.js:106:13)
npm info lifecycle     at EventEmitter.emit (events.js:191:7)
npm info lifecycle     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
npm info lifecycle     at emitTwo (events.js:106:13)
npm info lifecycle     at ChildProcess.emit (events.js:191:7)
npm info lifecycle     at maybeClose (internal/child_process.js:886:16)
npm info lifecycle     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm info lifecycle  malice@5.5.0~test:server: forced, continuing { Error<EMAIL_ADDRESS>test:server: `plugin-helpers test:server`
npm info lifecycle Exit status 1
npm info lifecycle     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
npm info lifecycle     at emitTwo (events.js:106:13)
npm info lifecycle     at EventEmitter.emit (events.js:191:7)
npm info lifecycle     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14)
npm info lifecycle     at emitTwo (events.js:106:13)
npm info lifecycle     at ChildProcess.emit (events.js:191:7)
npm info lifecycle     at maybeClose (internal/child_process.js:886:16)
npm info lifecycle     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm info lifecycle   code: 'ELIFECYCLE',
npm info lifecycle   pkgid<EMAIL_ADDRESS>npm info lifecycle   stage: 'test:server',
npm info lifecycle   script: 'plugin-helpers test:server',
npm info lifecycle   pkgname: 'malice' }
npm info lifecycle malice@5.5.0~posttest:server<EMAIL_ADDRESS>npm info ok

I have included the --force flag to get it to pass CI.

This is just the base plugin generated with your template

Yeah, the default test is a failing test. I'm not sure why though, it's a holdover from the old generator.
I'll update the test to at least pass by default.

Published v6.2.3 and v7.2.1, both now have passing tests.

thank you!


RTView: implement tests

Corresponds to previous issue CAD-2142.
Currently, there are tests for cardano-tracer, but not for RTView. Some functionality ofr RTView can be tested automatically.

Closing this. If this is still relevant please reopen.


VS C4503 warning

When I try to use tsl::hopscotch_map instead of std::unordered_map I often end up with VS C4503 warning. Do you have any good BKMs on how to handle such issues?

BTW, I do not have any complicated structure of containers in containers. I observe that for simple/flat one hopscotch_map<in_place_string<CharT, MaxSize, Traits>, ptr_type> for at least operator and erase(Key) operations. For in_place_string definition look here: https://github.com/mpusz/in_place_string.

Could you try this branch.
I'm able to instantiate things like
tsl::hopscotch_map<int, tsl::hopscotch_map<int, std::vector<std::pair<int, std::map<int, int>>>>> inner_map; without any warning.

I confirm that branch compiles fine for my case. Are there any side effects of that code (e.g. lower performance)?

The performances should be exactly the same. I just moved some inner-classes into the detail namespace reducing the length of the identifiers.


Add logging of transaction and query console output

The default format shows it indented 4 spaces. The output is controlled by the service author and is not sanitized. Beware if sending it to an automated consumer.

The output is controlled by the service author and is not sanitized. Beware if sending it to an automated consumer.

Seems like this warning should be in the logging.md docs


[Android] - WebView with embed video not working inside   or

I am trying to use the WebView component to have an external embed video.
When I have the WebView alone it works as expected:
<WebView style={styles.container} javaScriptEnabled={true} source={{uri: https://player.vimeo.com/video/159542449title=0&byline=0&badge=0&portrait=0&autoplay=1`}}/>`
If i use it inside a View it shows a white screen. Example: https://rnplay.org/apps/ZER6Lg
Using inside <Navigator> or  <DrawerLayoutAndroid> I am getting an black screen.
RN Version: Tried with 24 and 25-RC

When you remove:
alignItems: 'center',

it works.

Removing alignItems: 'center' works in IOS, but in android the problem still persists.
 I don't know if the issues are related or are two separated problem. But I will try to do some deeper investigation too when I have some time.

@lneves12 I think the iOS-issue might be related to #6110 actually, not sure why on Android is still broken.

I can't reproduce this from the rnplay link. I am going to theorize it's fixed and close this issue, but feel free to reopen it if the issue is persisting and I'll try to help repro it.


Another Error not listed

Task X, parameter 5. The target list should not be empty.
I figured out this is in regards to column E for anyone using a csv file upload.

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

ID: cfa08336-690e-0d21-6491-3f14f6d13391
Version Independent ID: 8927975a-7956-fc72-055e-36603e4eddaf
Content: Troubleshooting SharePoint Migration Tool - Migrate to SharePoint and OneDrive
Content Source: migration/troubleshooting-common-spmt-issues.md
Service: sharepoint-online
GitHub Login: @JoanneHendrickson
Microsoft Alias: jhendr

@Canis-Lupis  Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @Canis-Lupis
Thanks for reporting. I could reproduce and also added some more error messages.
Proposed thru a PR to improve the article with them.
Thanks

@Canis-Lupis Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


refactor: Don't re-parse the whole subdoc, expose only headings

refactor: Merge md extensions into one, to reduce boilerplate

refactor: Pass the actual used Markdown instance to update_env
The fact that we're re-instantiating Markdown used to be seen as a hack, but now it's required and preferred.

refactor: Move do_convert_markdown method into the class

refactor: Don't re-parse the whole subdoc, expose only headings
Previously the autodoc sub-document (HTML with nested Markdown) was being re-integrated into the top-level document by the way of parsing it as XML and inserting it back into the XML tree of the top-level markdown duri>
This gave a lot of side effects that need to be worked around. XML parsing, Markdown double-processing (with only situational workaround possible), etc.
Now, the document will be inserted as fully opaque HTML, so those issues are avoided entirely. But now there are new issues to overcome!

The ToC extension can no longer see through this subdocument, so no ToC entries can be generated. I thought a lot how to re-add these properly, and there's no easy solution without parsing the HTML. In the end I deci>

MkDocs can no longer fix relative paths in this subdocument. That one is much easier: just manually re-add its treeprocessor.

refactor: Actually exclude hidden headings from the doc
Now we separately control which headings appear in the doc and which in the ToC. No need to hide them with CSS now.

The lint failures are interesting.
https://github.com/oprypin/mkdocstrings/runs/1639842955
I'm using the leading underscore to designate things that are private to our whole code package, but the linter insists that this makes the things private to the class.
Maybe it's a design problem but I fail to see a simple solution. Maybe you'll find one.

The lint failures are interesting.
https://github.com/oprypin/mkdocstrings/runs/1639842955
I'm using the leading underscore to designate things that are private to our whole code package, but the linter insists that this makes the things private to the class.
Maybe it's a design problem but I fail to see a simple solution. Maybe you'll find one.

Yes usually an underscore in front of an attribute means it should be accessed from within its instance only (with self._attribute), and never from somewhere else (self.intermediate_instance._attribute). I think it's just annoying when you design your library to be mostly private, and expose only a few things publicly. If you would like to start doing that with mkdocstrings (as you noticed everything was public in my code), then we can decide to ignore these warnings.

Yes usually an underscore in front of an attribute means it should be accessed from within its instance only (with self._attribute), and never from somewhere else (self.intermediate_instance._attribute). I think it's just annoying when you design your library to be mostly private, and expose only a few things publicly. If you would like to start doing that with mkdocstrings (as you noticed everything was public in my code), then we can decide to ignore these warnings.

Regressions run is interesting.
Something weird with HTML escaping, will need to check that out.
Note that I'm filtering out the intentional addition of div.mkdocstrings and removal of .hidden-toc
- but see them in a non-filtered run here

Regressions run is interesting.
Something weird with HTML escaping, will need to check that out.
Note that I'm filtering out the intentional addition of div.mkdocstrings and removal of .hidden-toc
- but see them in a non-filtered run here

Could be autoescape=True: converting the templates to HTML with Jinja escapes a first time, and then during Markdown conversion it is escaped a second time?

Could be autoescape=True: converting the templates to HTML with Jinja escapes a first time, and then during Markdown conversion it is escaped a second time?

This is ready now.
Regressions run

This is ready now.
Regressions run

Latest regression run still looking very good.
No change from the previous one, but I'm no longer filtering out div.mkdocstrings because I got rid of the addition.
There's a diff that I hadn't realized before what it means
https://github.com/oprypin/mkdocstrings-regressions/runs/1715267244?check_suite_focus=true#step:6:1086
This is actually an accidental bug fix! I think previously Markdown was doing something weird to this content on the external pass, messing with newlines.
You can see it broken here
https://servir-mekong.github.io/hydra-floods/thresholding/#hydrafloods.thresholding.kmeans_extent

but now it's fixed because we "protect" the inner HTML from the outer Markdown processing.

Latest regression run still looking very good.
No change from the previous one, but I'm no longer filtering out div.mkdocstrings because I got rid of the addition.
There's a diff that I hadn't realized before what it means
https://github.com/oprypin/mkdocstrings-regressions/runs/1715267244?check_suite_focus=true#step:6:1086
This is actually an accidental bug fix! I think previously Markdown was doing something weird to this content on the external pass, messing with newlines.
You can see it broken here
https://servir-mekong.github.io/hydra-floods/thresholding/#hydrafloods.thresholding.kmeans_extent

but now it's fixed because we "protect" the inner HTML from the outer Markdown processing.

Hey! Indeed, last time I was wondering about all these
 disappearing in diffs. Well, if it's better now, great! Should I wait a bit more or do you think this is good to be merged?

Hey! Indeed, last time I was wondering about all these
 disappearing in diffs. Well, if it's better now, great! Should I wait a bit more or do you think this is good to be merged?

Also, one question: is there a reason we have update_env and _update_env? Couldn't we merge both into one?

Also, one question: is there a reason we have update_env and _update_env? Couldn't we merge both into one?

You can look at the individual commit that splits update_env into two parts. It is very intentional. One part is the one that must not be overridden, and the other part becomes very friendly to overriding, because it receives a pre-constructed inner Markdown instance (unlike previously where it received the useless outer Markdown instance)

You can look at the individual commit that splits update_env into two parts. It is very intentional. One part is the one that must not be overridden, and the other part becomes very friendly to overriding, because it receives a pre-constructed inner Markdown instance (unlike previously where it received the useless outer Markdown instance)

It is ready to be merged indeed (other than the merge conflict which I don't have my computer at the moment to resolve).
Merging is strongly recommended without squashing btw.

It is ready to be merged indeed (other than the merge conflict which I don't have my computer at the moment to resolve).
Merging is strongly recommended without squashing btw.

Merged. BTW another thing about update_env. I think maybe the outer _update_env should just get a new name, then it'd make more sense.I jusy didn't think of that.

Merged. BTW another thing about update_env. I think maybe the outer _update_env should just get a new name, then it'd make more sense.I jusy didn't think of that.

Great refactor! Thanks a lot :slightly_smiling_face:

Great refactor! Thanks a lot :slightly_smiling_face:


Vim9: "here" written on terminal when using nested closure

Describe the bug
In Vim9 script, using a nested closure might cause Vim to write here on the terminal.
To Reproduce
Run this shell command:
vim -Nu NONE -i NONE -U NONE -S <(cat <<'EOF'
    vim9
    def FuncB(l: any)
        map(l, (_, v) => map(l, (_, v) => v))
    enddef
    def FuncA()
        FuncB([])
    enddef
    FuncA()
    q
EOF
)

The text here is written on the terminal after Vim is quit.
Expected behavior
Nothing is written on the terminal after Vim is quit.
Screenshots

Environment

Vim version: 8.2 Included patches: 1-2323
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(363)

Additional context
Re-writing FuncA() into a legacy function fixes the issue:
vim9
def FuncB(l: any)
    map(l, (i, v) => map(l, (_, v) => v)[i])
enddef
fu FuncA()
    call FuncB([])
endfu
FuncA()
q

Regression introduced in 8.2.2322.

It's not just visible after quitting Vim; I can see multiple lines of hereherehere... while Vim is running, either on the command-line or in a Vim window.  They can be erased with :redraw.  I'm going to stay on 8.2.2321 for the moment.

It's not just visible after quitting Vim; I can see multiple lines of hereherehere... while Vim is running, either on the command-line or in a Vim window.  They can be erased with :redraw.  I'm going to stay on 8.2.2321 for the moment.

Fixed by 8.2.2327

Fixed by 8.2.2327


New release on PyPI for Django 1.11

Hey! I saw that django-babel has Django 1.11 support on master. Could we get a release on PyPI for downstream consumers?
Thanks

@akx That's an important one ! Do you have the rights to make a release on PyPI ?

It's relatively critical for us, since OpenStack Horizon relies on it, and requirements freeze is next week. If I can do anything to help the process along, please let me know.

@benselme I do indeed!
@robcresswell I'll do this tomorrow morning! :)

Fantastic. Thanks so much!

@robcresswell: 0.6.1 released 😸  https://pypi.org/project/django-babel/

@akx Great, thanks again


Code using require("raw-loader!") breaking after upgrading from 12.1 to 12.2.

🐞 Bug report
Command (mark with an x)

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

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Yes, this still worked in 12.1. Not sure if it was an intended feature, but it's been working for years.
Description
 A clear and concise description of the problem...
🔬 Minimal Reproduction
const csv = require("raw-loader!../../locale/translations.editor.csv").default;

Code such as the one above breaks upon trying to build the Angular application using ng build or ng serve after the update.

🔥 Exception or Error

./src/app/components/third-party/third-party-edit-dialog.component.ts:30:13-82 - Error: Module not found: Error: Can't resolve 'raw-loader' in 'C:\Users\Vincent\project\src\app\components\third-party'

./src/app/services/app-version.service.ts:10:47-112 - Error: Module not found: Error: Can't resolve 'raw-loader' in 'C:\Users\Vincent\project\src\app\services'

./src/app/services/app-version.service.ts:13:47-112 - Error: Module not found: Error: Can't resolve 'raw-loader' in 'C:\Users\Vincent\project\src\app\services'

./src/app/services/custom-translation.service.ts:31:22-84 - Error: Module not found: Error: Can't resolve 'raw-loader' in 'C:\Users\Vincent\project\src\app\services'

./src/app/services/custom-translation.service.ts:35:22-83 - Error: Module not found: Error: Can't resolve 'raw-loader' in 'C:\Users\Vincent\project\src\app\services'

Error: node_modules/@angular/compiler-cli/src/ngtsc/diagnostics/index.d.ts:10:10 - error TS2305: Module '"@angular/compiler-cli/src/ngtsc/diagnostics/src/error_code"' has no exported member 'COMPILER_ERRORS_WITH_GUIDES'.

10 export { COMPILER_ERRORS_WITH_GUIDES, ERROR_DETAILS_PAGE_BASE_URL, ErrorCode, ngErrorCode } from './src/error_code';
            ~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@angular/compiler-cli/src/ngtsc/diagnostics/index.d.ts:10:39 - error TS2305: Module '"@angular/compiler-cli/src/ngtsc/diagnostics/src/error_code"' has no exported member 'ERROR_DETAILS_PAGE_BASE_URL'.

10 export { COMPILER_ERRORS_WITH_GUIDES, ERROR_DETAILS_PAGE_BASE_URL, ErrorCode, ngErrorCode } from './src/error_code';
                                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~

Error: node_modules/@angular/compiler-cli/src/ngtsc/diagnostics/index.d.ts:10:79 - error TS2724: '"@angular/compiler-cli/src/ngtsc/diagnostics/src/error_code"' has no exported member named 'ngErrorCode'.
Seems to be related to: https://github.com/angular/angular-cli/pull/21305
Also if our broken code should never have worked in the first place, can you please indicate how to load local files from the project statically?

Indeed this is expected not to work. Webpack specific features are not supported by the Angular CLI.
CSV files should be loaded using XHR requests. See: https://angular.io/guide/http

We use raw-loader to inline svg icons and get the same error.
So there is no way to statically inline anything any more? Or is the webpack asset/source module type supported as #21305 seems to suggest? And if that is the case, how to enable it for additional file patterns?

The CSVs were just one example. But the a few of our cases don't really have access to HttpClient and/or can't be loaded asynchronously.


Document the schema migration process on the project wiki #270

Signed-off-by: Paul Bastide<EMAIL_ADDRESS>

Lots of good content here.  Left a bunch of comments and happy to discuss any of them.
Now that we have a better handle on the schema, I think we need to design a proper migration story.  We're doing all the work of tracking db object versions but with none of the benefit.
We need a framework for adding the migration logic, so that if the system detects that an update is needed to a given object it can apply it automatically.


doubly escape periods in counter names so we dont create invalid json

This fixes an issue created by https://github.com/youtube/vitess/pull/2992. This broke our automation and monitoring which relies on the json response of /debug/vars being proper json.
cc @nerdatmath @sougou

By the way, I found the original escaping change to be unnecessary, though I can work around it once the json is valid. Since we know the format of the keys, we could still properly split the keys accounting for potential periods. It was a bit involved, but worked:
# for maps where one of the keys is the username, the username may have periods in it.
# Account for that in how we parse split on periods below.
idx = tag_list.index('user')
if idx == 0:
    # no username, just split from right
    tag_data = name.rsplit(key_split_char, len(tag_list) - 1)
elif idx == len(tag_list) - 1:
    # username is the last item in the list, split from left
    tag_data = name.split(key_split_char, len(tag_list) - 1)
else:
    # limited split from left, up to where the username is
    lparts = name.split(key_split_char, idx)
    # limited split of remainder from right, backwards to username
    rparts = lparts[idx].rsplit(key_split_char, len(tag_list) - idx - idx)
    # contains everything up to but not including username
    tag_data = lparts[:idx]
    # add rparts on, the first item will be the username with dots in it
    tag_data += rparts

@bbeaudreault Congrats on pull request #3000 ! :) Sugu got #1000 and I #2000 back then :D

Woohoo!

Another bonus is this year we hit it a month early!

I want to see if the previous change can be rolled back in favor of an internal fix. I'll try to catch @nerdatmath when he's online to chat about it.

Sounds good, thanks

The problem's not in my change, although my change revealed it. The problem is in the String method of Counters. Compare it to the String method of expvar.Map, and you'll see that where they use %q (which does the escaping required to generate valid JSON), we use "%v", which is equivalent to "%s" in this case because keys are always strings, and %s doesn't do any escaping. I'll send a PR to fix that.

This was fixed more correctly by https://github.com/youtube/vitess/pull/3005


cpptrace and CPack Error: invalid characters in variable name

Hi i want to create an installer for my executable with CPack. Installation is working as expected. I include cpptrace via CPM: https://github.com/cpm-cmake/CPM.cmake.
Now when i run CPack i always get the error:
Error: invalid characters in variable name "cpptrace-development_selected", use only characters [a-z][A-Z][0-9], '.' and '_'
I does not know how to change the variable or where it comes from. Any help is appreciated.

Ok i now fixed the issue.
In InstallRules.cmake i changed all COMPONENT ${package_name}-development to COMPONENT ${package_name}_development and now CPack runs and creates an installer :D.
Should i make a PR to change the nameing for using CPack?


Can I just insert the @${name} as plain text without the surrounding span element?

Hi author and contributors, I just wanted to ask if inserting the selected text using the span element with the atwho-inserted is hardcoded because I just wanted to disable it using a config and just insert plain text @${name}, I read the wiki but I couldn't find how to get around this.

Same by me. As a workaround I have to edit final text while saving like this:
$('.atwho-query').contents().unwrap()
$('.atwho-inserted').contents().unwrap()


Wait segment deletion in startReplaceSegment api to make sure there will be at most 2 data snapshots.

This pr should solve the followings:

It's possible to violate the 2X storage usage because the segment cleanup in startReplaceSegment is async. E.g. a refresh table has 2 snapshots already. The the 3rd push got success response from startReplaceSegment api and starts to upload, but the cleanup for the 1st snapshot fails.
In case of rerunning the failed push, there's a race condition between retention manager/revertReplace and startReplace.

For example, the retention manager can delete the new uploaded s3 and s4 because the delete is async in retention manager.
Initial state:
lineageEntry1: { segmentsFrom: [s1, s2], segmentsTo: [s3, s4], status: REVERTED/IN_PROGRESS > 24h}

Running startReplace:
lineageEntry1: { segmentsFrom: [s1, s2], segmentsTo: [], status: REVERTED}
lineageEntry2: { segmentsFrom: [s1, s2], segmentsTo: [s3, s4], status: IN_PROGRESS}

This pr should solve the race condition by waiting for the clean up for s3 and s4 before completing startReplace so the client side hasn't upload s3 and s4 yet.

Codecov Report

Merging #8838 (cf3d86a) into master (e8f9d88) will decrease coverage by 42.81%.
The diff coverage is 0.00%.

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

@@              Coverage Diff              @@
##             master    #8838       +/-   ##
=============================================
- Coverage     68.56%   25.75%   -42.82%
+ Complexity     4640       45     -4595
=============================================
  Files          1741     1729       -12
  Lines         91475    91130      -345
  Branches      13674    13638       -36
=============================================
- Hits          62724    23469    -39255
- Misses        24363    65391    +41028
+ Partials       4388     2270     -2118

Flag
Coverage Δ

integration1
?

integration2
25.75% <0.00%> (?)

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ntroller/helix/core/PinotHelixResourceManager.java
31.05% <0.00%> (-34.96%)
:arrow_down:

...in/java/org/apache/pinot/spi/utils/StringUtil.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../java/org/apache/pinot/spi/utils/BooleanUtils.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/BaseRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/spi/trace/NoOpRecording.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/table/FSTType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/config/user/RoleType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...ava/org/apache/pinot/spi/data/MetricFieldSpec.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...java/org/apache/pinot/common/tier/TierFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...a/org/apache/pinot/spi/config/table/TableType.java
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 1301 more

Continue to review full report at Codecov.

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

@jtao15 Can you add a bit more context to the description?

@jtao15 Can you add a bit more context to the description?

Added more context.

cc @klsince to take a look at the change


Remove Antrea Octant plugin

The plugin was deprecated in Antrea v1.12 and replaced with the Antrea UI. It is being removed as of Antrea v1.13.
We remove all references to Octant in the repo, except for a single disclaimer in docs/octant-plugin-installation.md.
For #4640

/skip-all


Replace jieba3k with jieba

 Issue by pistolero
Wed Dec  6 09:31:32 2017
Originally opened as https://github.com/codelucas/newspaper/issues/482

jieba3k package is outdated. It is last updated in 2014.
Main jieba is Python3 compatible since 2015.

Replaced jieba3k with jieba
added tests for zh language
v0.9.2


Update namespace changes in docs

This updates the docs and comments to the namspace changes introduced in commit 9c42e95b3229c4ec348d191c1a8629e31fdda657: "Removed Representer and Feature namespace."

:heart: Thanks!!!


fix(docs): change npm to yarn in advanced usage docs

Description:
Update Advanced Usage docs to use yarn instead of npm
Motivation and Context:

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes:

changed usage of npm to yarn
updated node version to >= 12

Checklist:

[ ] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[ ] My commits have been squashed into a concise set of changes.

Thanks @dannypaz


Issue template update

The issue template is used by GitHub when a new issue is created.
Currently its main purpose is to prompt the issue reporter in to
providing all the information required to triage and investigate the
issue.
The main purpose of this patch is to give the individual working on
fixing the issue better guidence as to the steps that need to be taken
to complete it. This includes requiring the the individual to keep the
description (the section populated by the template) up-to-date with the
progress on work that has been done, e.g. pull requests created or
decisions made. In addition this patch seeks to make a clearer
distinction between the responsibilities of the issue reporter and the
issue assignee.

These updates are good. We had been using a similar list to track some of these issues for the onboarding team. These included the following requirements for the people doing the work so I'm wondering if we need a similar one to the revised bug template:

[ ] Reproduce the issue.
[ ] Create a PR for fix and/or docs.
[ ] Incorporate feedback from pull request reviews.
[ ]  What is the gating for this on DEV and/or QE? Add related gating if appropriate. Also make sure current gating passes with this fix.
[ ] Reach out to reporter to determine if the fix is resolving the issue.
[ ] What are the upgrade impacts (if any).
[ ] What are the backports are needed (if any).

This looks like a good change to me, and I like the clear separation of concerns between submitter and fixer. Shame we have to track it all in an issue description, but given that's what we have to work with...
👍

👍  I agree with @claco's comment, otherwise all good.

Other than that it looks like a good change :+1:

So... with the move to Jira, what does that mean for the issue template?

@sigmavirus24 I'll let @b3rnard0 answer that, also #1229 is in the same boat.

Outcome of team meeting was agreement to merge this pull request.


⚠ Bofrost.at has degraded performance

In 05b1e97, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1844 ms

Resolved: Bofrost.at performance has improved in 00e87dc after 31 minutes.


WIP: Get-Credential password confirmation

PR Summary

Adds -ReEnterPassword parameter to the Get-Credential cmdlet.
PR Context

This PR is logged to complete  #10625
PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

 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.:x: Shriram0908 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I am new to using git and I noticed that I committed .sln file also. I tried reverting the file but made a mess of my local repository. I have opened a new Pull request  #12782 . Please refer the new PR.


Biicode support

This allows CppMicroServices to be published to biicode. It's currently configured to publish to azriel/cppmicroservices1. If you like, you could create an account there and publish it under that.
I haven't managed to get the tests being built when bii is used to build the library, not sure if it's possible yet
1 block names can be camel case; when I first set up the block, it was mandatory to be lower case

Any chance of getting this merged in?

@saschazelzer: ping, have you had time to review the changes?
Also, for the long term, setting up the repository to automatically publish to biicode shouldn't be too much work. The secure keys for travis need to be done from your side, as this repository would be the main.

Closing - biicode is no longer supported.


Modify API execution privilege of NullResource.

Example
PROPFIND

Current  implementation

checkAccessContext(this.davRsCmp.getAccessContext(), BoxPrivilege.READ);

Correct  implementation

checkAccessContext(this.davRsCmp.getAccessContext(), BoxPrivilege.READ_PROPERTIES);

PROPPATCH

Current  implementation

checkAccessContext(this.davRsCmp.getAccessContext(), BoxPrivilege.WRITE);

Correct  implementation

checkAccessContext(this.davRsCmp.getAccessContext(), BoxPrivilege.WRITE_PROPERTIES);

"read" is superior privilege of read-properties, i.e. read includes read-properties. So it should go like:
PROPFIND

OK :read
OK :read-properties

GET

OK :read
NG :read-properties

Sorry. I made a misunderstanding writing style.
The description was corrected.

Released in 1.6.1.


Where is the paper?

Hi, thanks for your great work!
Could you provide the correct paper link? I can't find the paper.

Thanks for your interest. The paper will be made public next week.

Then 2 weeks passed, still not available


Unable to get past docker compose up stage

Describe the bug
Attaching to snap-camera-server-310-adminer-1, snap-camera-server-310-mysql-1, snap-camera-server-310-webapp-1, snap-camera-server-310-webproxy-1
Error response from daemon: error while creating mount source path '/Applications/snap-camera-server-3.1.0/mysql': mkdir /Applications: file exists

To Reproduce
Steps to reproduce the behavior:

docker compose up

Expected behavior
Server should start to run
Screenshots

System (please complete the following information):

OS: MAC OS
Server Version: 3.1.0
Snap Camera Version: [e.g. 1.19, 1.20, 1.21]
Signature Patch applied: [yes or no]

Additional context
Add any other context about the problem here.

Okay, what fixed it was restarting the docker app


Query Parameterization

Being able to parameterize SPARQL queries would enable more dynamic usage of Yasgui in other tooling.
There was a lengthy discussion on https://github.com/Triply-Dev/YASGUI.YASQE-deprecated/issues/24 about enabling this in Yasqe. This issue is a continuation of that one.
Relevant links:

Grlc (http://grlc.io/)
Sparql 1.2 (https://github.com/w3c/sparql-12/issues/57)

SPARQL 1.2 issue 57 references:

SPARQL $var vs ?var
rdf4j http param $var
jena java API for query parameterization
Basil's Convention (OpenU)
grlc that implements Basil and a bit more
Wikidata Query Templates


fix: command quote surround string format specifier

Spaces in image directory names cause the path to be unexpectedly truncated. This fix ensures that the full string returned from the config (including spaces) is captured.

Merged


GSSAPI sasl mechanism for Kafka scaler

Adding "GSSAPI" SASL mechanism for Kafka scaler.
Use-Case
I would like to be able to work with Kafka that configured with Kerberos principals using keytab, jass.conf and krb5.conf
Specification

kind: secret

data:
  saslMechanism: GSSAPI  # or PLAIN for user/password, relevant only when authMode is "sasl_plaintext" or "sasl_ssl"
  keytab: <your keytab>
  jaas: <your jaas.conf>
  krb5: <your krb.conf>

kind: TriggerAuthentication

spec:
  secretTargetRef:
  - parameter: saslMechanism
    name: keda-kafka-secrets
    key: saslMechanism
  - parameter: keytab
    name: keda-kafka-secrets
    key: keytab
  - parameter: jaas
    name: keda-kafka-secrets
    key: jaas
  - parameter: krb5
    name: keda-kafka-secrets
    key: krb5

Related: #1043

is there an update on this feature request? my guess is a lot of people running in Azure w/ HDInsight have a similar problem

is there an update on this feature request? my guess is a lot of people running in Azure w/ HDInsight have a similar problem

Any update on this?  This would still be nice to be able to use GSSAPI SASL mechanism.

Nobody has yet picked this up, we are open to contributions though @andrewbrown248

Is this really implemented?
I don't see anything in the docs

Can this be reopened?  Seems like a useful feature.  I would volunteer to contribute.


Update macOS keybindings to select multiple tags

Related to: https://github.com/axllent/mailpit/pull/378

Thanks, updated!


Feature Request: Only download language data

Hi,
Is there a way to only download the trajectories that are labeled with language data? I'd like to download the ABC->D dataset, but my use case requires only the trajectories with language data. This would be helpful as the disk space and download time would be only ~1% of what it is now.
Thanks!

Hey @jesbu1, currently it is not possible to download only the language dataset.
However, the asumption that it would be only 1% of the disk space is also wrong, for an explanation, please refer to this issue.

Got it, thanks.


Whoever made the decision to clear the console needs to be relieved of duty.
There is no opinion at play here, this is simply wrong.

+1

This is an ongoing issue for at least 5 years now. I hadn't used CRA in a while and was amazed this hasn't been resolved.
I understand not wanting to make major changes to defaults or introducing code that may be difficult to maintain, but in this case it is only a small adjustment.
I think now more than ever we rely on combining multiple CLI tools together and clearing the console is a very intrusive behaviour.
Early issue with good points made: https://github.com/facebook/create-react-app/issues/2495
Stale PR that even fixed the issue: https://github.com/facebook/create-react-app/pull/3288


[Event Request] Table 5965 "Service Contract Header" - OnAfterUpdateCont

Hello,
could you please add a new event at the end of the procedure UpdateCont:
procedure UpdateCont(CustomerNo: Code[20])
var
    ContBusRel: Record "Contact Business Relation";
    Cont: Record Contact;
    Cust: Record Customer;
begin
    if Cust.Get(CustomerNo) then begin
        ....
    end;
    // Start-----------
    OnAfterUpdateCont(Rec, CustomerNo);
    // Stop----------
end;

[IntegrationEvent(false, false)]
local procedure OnAfterUpdateCont(var ServiceContractHeader: Record "Service Contract Header"; CustomerNo: Code[20])
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52463.


Adds demisto/google-cloud-translate image

For demisto/content#5165
Signed-off-by: Luigi Mori<EMAIL_ADDRESS>

 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.

Docker Image Ready - Production
Docker automatic build at CircleCI has deployed your docker image: demisto/google-cloud-translate:<IP_ADDRESS>38
It is available now on docker hub at: https://hub.docker.com/r/demisto/google-cloud-translate/tags
Get started by pulling the image:
docker pull demisto/google-cloud-translate:<IP_ADDRESS>38

Docker Metadata

Image Size: 68.53 MB

Image ID: sha256:604f611309cce944d908a77bd827bd37e380d5ddd462c030a6f518892dd98445

Created: 2019-12-13T15:36:08.236202128Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D
PYTHON_VERSION=3.7.5
PYTHON_PIP_VERSION=19.3.1
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/ffe826207a010164265d9cc807978e3604d18ca0/get-pip.py
PYTHON_GET_PIP_SHA256=b86f36cc4345ae87bfd4f10ef6b2dbfa7a872fbff70608a1e43944d283fd0eee

Labels:

org.opencontainers.image.authors:Demisto<EMAIL_ADDRESS>org.opencontainers.image.revision:df09d0f02566eba3da72ed798d162a70c7ab48bf
org.opencontainers.image.version:<IP_ADDRESS>38


[dev_1.2.1] The node runs backward. If the next node also depends on other nodes, the process instance status is always running and will not end

As shown above, choose to run backward in the task shell_file_dev_1.2.1_2；
Task shell_file_dev_1.2.1_4 also depends on shell_file_dev_1.2.1_3；
As shown in the figure below, the status of the process instance is always running, there is no final state

@xingchun-chen
I will fix it.


Forward callbacks to all screens

When I first wrote this library I just passed certain callbacks to all screens on the stack, but over time I realized that maybe for convenience it should forward all callbacks to all screens on the stack.

I also thought about this, and a way to tell the screens down the stack if someone already consumed the event would be nice.
I also added some functions to my "fork" in Positive07/lovejam-training to call functions in the first stack or all the stacks

In my current project the callback handling works fine the way it currently is, so I don't really have an idea how to improve it.
Of course we could simply break the event handling if one of the screens returned false, but I'm not sure how nicely that would work in more complicated setups.
for i = 1, #stack do
  if not stack[i]:xyz( ... ) then
    break
  end
end

On the other hand I don't want to over-complicate the library. I'm open for ideas :)

I really like this idea by @s-ol
Basically you pass a first parameter to the callback which is a function that propagates the event down the stack

I would implement it really simply like this:
local function propagator( callback, level, args )
   local state = stack[level]

   local propagate = function()
      return propagator( callback, level + 1, args )
   end

   return state[callback]( state, propagate, unpack( args ) )
end

Then in each callback you would do something like:
function ScreenManager.gamepadpressed( joystick, button )
    return propagator( "gamepadpressed", 1, { joystick, button } )
end

It creates a table per event which I couldn't avoid easily, but maybe you can do something like:
local function propagator (callback, level, a, b, c, d, e, f)
   local state = stack[level]

   local propagate = function()
      return propagator(callback, level + 1, a, b, c, d, e, f)
   end

   return state[callback](state, propagate, a, b, c, d, e, f)
end

function ScreenManager.gamepadpressed( joystick, button )
    return propagator("gamepadpressed", 1, joystick, button)
end

Since currently love.event.poll only returns 6 arguments per event
Note that the callbacks could also be:
function ScreenManager.gamepadpressed( ... )
    return propagator( "gamepadpressed", 1, ... )
end

I have cleaned up the propagator function, now called delegate:
---
-- Delegates a callback to the stack, with the appropriate propagate function
-- callback is the callback name
-- a, b, c, d, e, f are the event arguments
-- level is the level of the stack to delegate to (defaults to the top)
--
local function delegate( callback, a, b, c, d, e, f, level )
    level = level or #stack
    local state = stack[level]

    if not state or type( state[callback] ) ~= "function" then return end

    local function propagate()
        return delegate( callback, a, b, c, d, e, f, level - 1 )
    end

    return state[callback]( state, propagate, a, b, c, d, e, f )
end

You could define all the callbacks by doing this:
for name in pairs( love.handlers ) do
    ScreenManager[name] = function ( ... )
        return delegate( name, ... )
    end
end

function ScreenManager.update( dt )
    return delegate( "update", dt )
end

function ScreenManager.draw()
    local values = { delegate( "draw" ) }

    ScreenManager.performChanges()

    return unpack( values )
end

Or alternatively:
function ScreenManager.draw()
    local values = { delegate( "draw" ) }

    ScreenManager.performChanges()

    return unpack( values )
end

return setmetatable( ScreenManager, { __call = function( self, callback, ... )
    return delegate(callback, ...)
end } )

And a usage example would be one like this:
local MainScreen = {}

function MainScreen.new()
    local self = {}

    local active = true

    function self:isActive()
        return active
    end

    function self:setActive( nactiv )
        active = nactiv
    end

    function self:draw( propagate )
        propagate() --We will draw after other screens in the stack
        --Here we draw our stuff
    end

    function self.mousepressed( propagate, x, y, button )
        if x > 100 and x < 700 and y > 100 and y < 500 then
            --We consume the event
        else
            --Since we didn't consume it we propagate it
            propagate()
        end
    end

    function self.keypressed( k )
        if k == "space" then
            --We consume the event
        end

        --We propagate anyway
        propagate()
    end
end

return MainScreen

Note that in the example I don't use Screen.lua, since the delegate function checks if the callback exists before trying to call it.
Also note that the metatable approach lets me define my own events so for example I could call ScreenManager.serverRequest( request ) and if the active state can handle it then it will be consumed otherwise nothing happens
delegate could propagate if the current state doesn't define the callback but I'm not sure if that is desirable

I like the general approach, but I'm not a fan of the table allocation in the draw function local values = { delegate( "draw" )} because it produces a ton of garbage. I'm usually not too concerned with (over) optimisation until it becomes necessary, but I want to keep ScreenManager as lightweight as possible.
I understand why you are doing it, but I'd prefer something like this:
local a, b, c = delegate( 'draw' )
Of course the user would have to know which values his functions return, but that's something he should know anyway.
The other thing I'm concerned with (though maybe it isn't a problem ... I haven't been able to test it yet) is delegate( callback, a, b, c, d, e, f, level ). This would mean we could only pass six parameters to the functions. Why not use delegate( callback, level, ... ) instead? I'm thinking about situations where you want to pass custom values through the function.

An ugly hack for the draw issue could be
local function vargsPerformChanges( ... )
    ScreenManager.performChanges()
    return ...
end

function ScreenManager.draw()
   return vargsPerformChanges( delegate( "draw" ) )
end

It could work hahaha

Of course the user would have to know which values his functions return, but that's something he should know anyway.

I'm not sure that I like the idea of ScreenManager assuming how many values I will return from my callback.

The a, b, c, d, e, f arguments are there to avoid the issue of varargs being undefined in propagate
local function delegate( callback, level, ... )
    level = level or #stack
    local state = stack[level]

    if not state or type( state[callback] ) ~= "function" then return end

    local function propagate()
        return delegate( callback, level - 1, ... ) --Errors! This function (propagate) doesn't take varargs
    end

    return state[callback]( state, propagate, ... )
end

The other alternatively is to allocate a table like I proposed first
local function delegate( callback, level, ... )
    local args = { ... }
    level = level or #stack
    local state = stack[level]

    if not state or type( state[callback] ) ~= "function" then return end

    local function propagate()
        return delegate( callback, level - 1, unpack( args ) )
    end

    return state[callback]( state, propagate, ... )
end

But I don't think you want that since you are trying to optimize the unneeded creation of tables.
So I proposed to use 6 arguments instead, which is the biggest quantity of arguments that love.event.poll can handle
Yet as I said I don't want ScreenManager to assume how many arguments a callback can take and that probably all callbacks should be defined like:
function ScreenManager.draw( ... )
    return delegate( "draw", ... )
    -- Of course there is a performChanges here
end

This way I can do stuff like:
love.draw = function ()
    ScreenManager.draw( "something", 123 )
end

An ugly hack for the draw issue could be

Haha :D I think it's better than creating a ton of tables.
I'll try to sit down this weekend and give your version a try. Right now I'm basically discussing just from looking at the code and a quick test I wrote today.
So maybe this is a stupid question, but what are the benefits of your delegate / propagate approach compared to my original suggestion of simply using a return value. I just like simple solutions and by default LÖVE callbacks don't have return values IIRC. That's why I'd do this:
function ScreenManager.update( dt )
    local consumed;
    for i = #stack, 1, -1 do
        consumed = stack[i]:update( dt )
        if consumed then
            break;
        end
    end
end

By default the user wouldn't have to change his current screens since nil would mean the event isn't consumed. So the user could do something like this:
function self:update( dt )
    if coolStuffIsHappening then
        -- Do stuff
        -- ...
        -- then consume the event
        return true
    end
end

Your example has a fixed order, it traverses the stack in a for loop from the top of the stack to the bottom. You cannot change the order of the stack while in the loop or that may shield undefined behaviour.
Still your example can be implemented with delegate/propagate like this:
function self:update( propagate, dt )
    if coolStuffHappening then
        -- Do stuff
    else --We didn't consume the event so we propagate
        return propagate()
    end
end

But you could also do something like this:
function self:update( propagate, dt )
    local value = propagate()

    if value then
        -- Do something
    end
end

This basically means that the current state updates AFTER the state underneath it, and depending on the value returned by it, it performs an action or not.
There is no way to implement this with the for loop approach without changing ScreenManager's code. And even then, this approach allows you to have states that behave differently in the mix and you can always decide how they draw

Any new thoughts on this?

Any new thoughts on this?

I see the benefits of it, but I'm not willing to merge the current implementation into ScreenManager as it produces too much garbage for my taste.

I'll keep this open, but for now I'll add the simple consume feature I talked about earlier:
for i = #stack, 1, -1 do
    local consumed = stack[i]:foo( xyz )
    if consumed then
        break;
    end
end

I know this isn't the perfect solution, but it's better than what we currently have.


Add duffle claim show --output [DO NOT MERGE]

DO NOT MERGE BECAUSE
This is built on top of https://github.com/deislabs/cnab-go/pull/82 . That needs to be merged first, and then this PR's Gopkg.toml needs to be updated to point to a version of cnab-go that's after that merge.
Part of https://github.com/deislabs/duffle/issues/747
After making the code compile against the cnab-go library with outputs support implemented, this PR adds a --output flag to duffle claim show. This allows users to dump the contents of output files to stdout.

The output flag takes the name of an output as stated in the bundle; by showing a claim the user can view the names of all the outputs that are part of the bundle.
Because the cnab-go library implementation returns all the outputs that were generated, even if errors occurred during execution, users will be able to see what output files the invocation image produced during failed runs.

cc @youreddy @jeremyrickard

@silvin-lubecki does this side of the PR look good?

/brig run

The PR in cnab-go was merged, going to update the Gopkg.toml file to point to the updated version!

@youreddy should we release cnab-go or are you planning on pinning to a commit #? I'd prefer a released version, but we can always update to that once we have a few more things in.

@jeremyrickard, I was going to specify master but you're right we should do a released version. And yes to releasing cnab-go!

/brig run

@jeremyrickard /brig run ?

/brig run

@astrieanna sorry for the delayed response. Were you asking me to re-run it, or what "/brig run" does? Happy to explain what it does if you'd like!

/brig run

Thanks for the persistence on this @astrieanna and @youreddy, much appreciated.


Resolve to newer versions of dependencies

This addresses the following CVEs:
CVE-2021-3807  - Inefficient Regular Expression Complexity in
                 chalk/ansi-regex
CVE-2022-24999 - Improperly Controlled Modification of Object
                 Prototype Attributes ('Prototype Pollution'),
                 qs vulnerable to Prototype Pollution
GMS-2022-3113  - glob-parent before 6.0.1 and 5.1.2 vulnerable to
                 Regular Expression Denial of Service (ReDoS)

Signed-off-by: Michael Froh<EMAIL_ADDRESS>Description
Describe what this change achieves.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #107 (1c945f8) into main (052c593) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  Coverage   81.42%   81.42%
=======================================
  Files          13       13
  Lines         140      140
  Branches       27       27
=======================================
  Hits          114      114
  Misses         24       24
  Partials        2        2

Flag
Coverage Δ

dashboards-search-relevance
81.42% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Add support for variable length arguments.

The ... syntax does not seem to be supported:
I have this in my scss ladder(blue, white 45%, black 46%, black 59%, #333  60%); and I have created a Java method with this signature public static SassColor ladder(@Name("color") SassColor color, @Name("stops") SassValue... stops) I want to map this to a sass funtion with this signature @function ladder($color, $stops...)

Perhaps a variable length argument could be created by using an annotation like @VarArg
public static SassColor ladder(@Name("color") SassColor color, @VarArg @Name("stops") SassString... stops)


messaging.client.id duplicated when generating semconv 1.26.0

Area(s)
area:messaging
What happened?
Description
When generating semantic conventions with otel/semconvgen:0.24.0 I notice that messaging.client.id is duplicated: one "deprecated" and one "normal"
Steps to Reproduce (if any)
Expected Result
Only one entry for messaging.client.id
Actual Result
Semantic convention version
1.26.0
Additional context
I think what's going on is that whichever code generates a const name from a semconv attribute, is ending up with the same answer for messaging.client.id and messaging.client_id (note the _ vs .). We use {{ attribute.fqn | to_const_name }}

Closing, duplicate of #1031


display cropped image preview + caption on form

update trello card once resolved https://trello.com/c/brg2UvhQ


FOSOAuthServerBundle not compatible with Sylius 1.9 when requiring Symfony ^4.4

Using the 1.9 branch of this repository, I get this kind of errors
[Symfony\Component\DependencyInjection\Exception\ServiceNotFoundException]
  The service "fos_oauth_server.controller.authorize" has a dependency on a non-existent service "templating".

Example : https://github.com/FLUX-SE/SyliusPayumStripePlugin/runs/2044287962?check_suite_focus=true
Anyone succeeded to require Symfony 4.4 while installing Sylius 1.9 ?

Hi @Prometee. You need to require-dev the package:
"friendsofsymfony/oauth-server-bundle": "^1.6 || >2.0.0-alpha.0 ^2.0@dev"

Thank you @bigboss86 this will be ok for Sylius 1.9 with Symfony 5.2 but not when using Symfony 4.4, here is the PR I made to fix the actual problem https://github.com/Sylius/PluginSkeleton/pull/255

It has worked for me. Do you know why?
https://github.com/odiseoteam/SyliusVendorPlugin/runs/2132264172?check_suite_focus=true

@bigboss86 I found why, I used "prefer-stable": true, making composer to choose ^1.6 instead of >2.0.0-alpha.0.
Thanks @bigboss86 to point it out 😉
Ping @vvasiloi, maybe it was the same for you.


Fix chart installation question groups are "None" if there is only 1 group defined

Summary
Fixes #9959

Occurred changes and/or fixed issues

fix issue where if tabbed=multiple and only 1 group would show a tab  called None

Technical notes summary

Areas or cases that should be tested

Go to <!---YOUR-RANCHER-BASE-URL-->/c/local/apps/charts/install?repo-type=cluster&repo=rancher-charts&chart=rancher-vsphere-cpi&version=102.1.0%2Bup1.5.1#Configuration and check that one tab appears name Configuration
Areas which could experience regressions

Screenshot/Video

Before

After

@aalves08 Could we add automated tests for this?
Also, in this case, can we hide the side tabs altogether when there is only one option? Perhaps we can add an option to the tab component to support this and then in this usage, turn this on?


cephfs: implement protect,unprotect snapshot,clone with go-ceph

updated the implementation of protect snapshot, unprotect snapshot, and clone snapshot with go-ceph
Signed-off-by: Madhu Rajanna<EMAIL_ADDRESS>

Subjects of the commits could be improved, but nothing blocks merging from my POV.

merging it for now. Thanks @nixpanic


Update output

It looks like you are reverting from using DataContainer for output to using GenericParameters for output-- is this the case? If so why?
Yes, In previous version, I used DataContainer. But, the output was not reflected in job.output. Therefore, I have reverted to Generic implementation. Can you please comment if this [https://github.com/pyiron/pyiron_continuum/pull/57/files#diff-7384e555bed4e72dd9d1d766df0a154957d47a6b4938e4697df4c8fe10b87e6fL60-L63] was the correct way to do it?

I will take a look later this morning. GenericParameters is on its way to the graveyard though so I really want to avoid this change.
Can you please explain in a bit more detail what is meant by the output not being reflected?

It seems you previously never wrote the input and output containers to HDF (by calling their .to_hdf).  This is why after reloading jobs they cannot reflect output previously collected.  You should add to_hdf and from_hdf (preferably after this is merged and pyiron_base is on the next version), that do the following things

call super()._to_hdf
call self.input.to_hdf(...)
call self.output.to_hdf(...)
Same for from_hdf.  Writing output might also be necessary in collect_output, will test that right now.

Super, yes I think Marvin hit the nail on the head. Implementing to_hdf and from_hdf routines and then invoking to_hdf in collect_output should do the trick.
A couple of Gotchas:

Instead of self.input = DataContainer() use self.input = DataContainer(table_name='dc_input'). Hopefully this won't be necessary in the future, but right now that stops the data container for conflicting with the GenericJob.to_hdf call that already writes to the HDF path input.
When calling data container to_hdf methods, pass the job's project_hdf5 as the argument, i.e. self.input.to_hdf(hdf=self.project_hdf5)

@pmrv please quickly read and let us know if I'm spouting nonsense here ;)

Super, yes I think Marvin hit the nail on the head. Implementing to_hdf and from_hdf routines and then invoking to_hdf in collect_output should do the trick.
A couple of Gotchas:
* Instead of `self.input = DataContainer()` use `self.input = DataContainer(table_name='dc_input')`. Hopefully this won't be necessary in the future, but right now that stops the data container for conflicting with the `GenericJob.to_hdf` call that already writes to the HDF path `input`.

* When calling data container `to_hdf` methods, pass the job's `project_hdf5` as the argument, i.e. `self.input.to_hdf(hdf=self.project_hdf5)`

@pmrv please quickly read and let us know if I'm spouting nonsense here ;)

Sounds good!

Thank you. I will update this.

Also don't hesitate to ping me in the future if problems like this pop up, before you sink a lot of time into it.

Sure, Thank you :)


May I ask why the reuslts are not very promising?

Hi, Thank you for sharing your work.
I have tested your code on KITTI dataset with your default parameters. However, the results are not very promising, which is much worse than yours. May I ask do you know the potential reasons?
Thank you very much.

Hi, I am sorry that this version is not quite stable and the performance is not good. However, by tuning the parameters, you can reproduce the results listed in the table. Besides, I am currently work on a new version of lls-loam (with ATE 0.66, ARE 0.003, 10Hz on KITTI seq 00) and I will publish it soon.
Thanks a lot for your interest.

That is a great result! Would you mind providing good parameters for me?
For the new version lls-loam, Do you only use laser measurements? or you
fuse other sensors? Do you have any published papers?
Thank you very much!
Shibo Zhao
On Thu, May 28, 2020 at 9:39 PM Yue Pan<EMAIL_ADDRESS>wrote:

Hi, I am sorry that this version is not quite stable and the performance
is not good. However, by tuning the parameters, you can reproduce the
results listed in the table. Besides, I am currently work on a new version
of lls-loam (with ATE 0.66, ARE 0.003, 10Hz on KITTI seq 00) and I will
publish it soon.
Thanks a lot for your interest.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/YuePanEdward/LLS-LOAM/issues/3#issuecomment-635707103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHA6EMMKAGEK2TPIQFRECILRT4G6RANCNFSM4MXLLKIA
.

Sorry for the late reply. Please refer to MULLS.


docs: Creation flows

{Arnaud Gillard submitting patterns from the Cloud Integration Design Guidelines: Submitted branch pull request as requested in #1641}
Changelog
New
{Updated the "Adding or Creating" living under the Patterns section. Renamed the page to "creation flows" and re-structured all content.}
Changed
{All New}
Removed
{All New }

Hey Anna! Sounds great. Thanks for your feedback! Yes I certainly agree that we should try and get this as polished as possible. In fact, as you brought this up, I checked with a visual and there are indeed elements which need checking. I was sent these files by the visual team so will check with them why it's not accurately following the carbon guidelines. Will push an update once I get them refined.

Hi all, I've unfortunately managed to push an update on a separate commit (although I tried staying within the same branch!). Here is the link to the updated page: https://github.com/carbon-design-system/carbon-website/pull/1689

Just adding a comment here to avoid it from closing :)

request from @jnm2377 :
Can we use the do-don't components for this set of example images? You can see an example here: https://www.carbondesignsystem.com/guidelines/color/overview https://github.com/carbon-design-system/carbon-website/blob/master/src/content/guidelines/color/overview.mdx

please refer to changes made in #1796 whilst I try to get that content onto the correct branch (this one).

Just copied the changes from #1796 over here so that its all in one pull request. I have updated the columns of the imagery and used the do/don't component from the carbon page. I will close #1796. I also have our visuals making the requested changes so will get that to you soon @aagonzales.

This work has been transferred over to the new website repo: https://github.com/carbon-design-system/carbon-website/pull/121


The problem on Installation

Hi, I tried to setup the base virtual environment, but I faced a problem.
$ conda env create -f semiseg.yaml
Then, I can see this message.

I skipped others since there are too many lines.
Maybe almost dependency packages cannot be found.

My environment.
Win10
Anaconda Version : 1.7.2
GPU: RTX3090
Please help me.
Thank you.

Hi, which version of CUDA do you use? The commond is nvcc -V.

Hi, which version of CUDA do you use? The commond is nvcc -V.

I have two workstation with different environment.

GPU: RTX3090, CUDA version: 11.2.142
GPU: V100, CUDA version: V10.0.130

I could not find the problem according to the current information. Maybe you could install Apex first (Cuda 9 or Cuda 10 is recommended) and then manually install the libraries needed at runtime.

@openmll I'm sorry to bother you. Have you successfully run the program on win10 system? I also encountered the same problem on win10 system.

@charlesCXK Hi, I tried to setup the base virtual environment, but I faced a problem.

@ChrisLiang2020 Sorry, we didn't test the code on Win10. We recommend to use Linux instead.

with linux i unfortunately get also a huge list of incompatabilities when trying to create the environment from yml:
UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package send2trash conflicts for:
jupyter==1.0.0=py36_7 -> notebook -> send2trash[version='>=1.5.0|>=1.8.0']
widgetsnbextension==3.4.2=py36_0 -> notebook[version='>=4.4.1'] -> send2trash[version='>=1.5.0|>=1.8.0']
jupyterlab_server==0.2.0=py36_0 -> notebook -> send2trash[version='>=1.5.0|>=1.8.0']
send2trash==1.5.0=py36_0
jupyterlab_launcher==0.13.1=py36_0 -> notebook -> send2trash[version='>=1.5.0|>=1.8.0']
notebook==5.7.2=py36_0 -> send2trash
jupyterlab==0.35.3=py36_0 -> notebook[version='>=4.3.1'] -> send2trash[version='>=1.5.0|>=1.8.0']

Package _openmp_mutex conflicts for:
[..]

Hi,
I'm also facing some conflict issues when trying to install the environment and was wondering if there was anything I could do to resolve the conflicts. I'm in a Linux environment, conda version 23.5.2 and Python 3.11.4. Please let me know if there something I could do to resolve the issue. Thank you!
I get the following error:
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Package jinja2 conflicts for:
nbconvert==5.4.0=py36_1 -> jinja2
widgetsnbextension==3.4.2=py36_0 -> notebook[version='>=4.4.1'] -> jinja2
jinja2==2.10=py36_0
conda-build==3.17.3=py36_0 -> jinja2!=3.0.0
spyder==3.3.2=py36_0 -> nbconvert -> jinja2[version='>=2.10|>=2.4|>=3.0|>=2.3']
jupyterlab_server==0.2.0=py36_0 -> notebook -> jinja2
notebook==5.7.2=py36_0 -> nbconvert -> jinja2[version='>=2.4|>=3.0']
sphinx==1.8.2=py36_0 -> jinja2[version='>=2.3']
flask-cors==3.0.7=py36_0 -> flask[version='>=0.9'] -> jinja2[version='>=2.10,<3.0|>=2.10.1,<3.0|>=3.0|>=2.4']
jupyter==1.0.0=py36_7 -> nbconvert -> jinja2[version='>=2.4|>=3.0']
jupyterlab==0.35.3=py36_0 -> notebook[version='>=4.3.1'] -> jinja2
flask==1.0.2=py36_1 -> jinja2[version='>=2.10,<3.0']
_ipyw_jlab_nb_ext_conf==0.1.0=py36_0 -> jupyterlab -> jinja2[version='>=2.1|>=2.10']
notebook==5.7.2=py36_0 -> jinja2
numpydoc==0.8.0=py36_0 -> sphinx -> jinja2[version='>=2.3']
jupyterlab_launcher==0.13.1=py36_0 -> notebook -> jinja2
Package libgcc-ng conflicts for:
alabaster==0.7.12=py36_0 -> python[version='>=3.6,<3.7.0a0'] -> libgcc-ng[version='>=7.2.0|>=7.3.0|>=7.5.0']
fastcache==1.0.2=py36h14c3975_2 -> libgcc-ng[version='>=7.2.0']
mkl_random==1.0.1=py36h4414c95_1 -> numpy[version='>=1.11.3,<2.0a0'] -> libgcc-ng[version='>=11.2.0|>=7.5.0|>=7.3.0']


Pull request creation failed. Validation failed: must be a collaborator

Each time i try to add my server i get this error Pull request creation failed. Validation failed: must be a collaborator

You need to make a fork then create the pull request from a fork


[2.0] Gluon2.0: switch to use forward interface

Description
#19138
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[x] Code is well-documented

Changes

[x] Adopt packed_func based ffi on npx.group_norm
[x] Gluon2.0 upgrade: use forward interface in blocks

[x] gluon/data/vision/*
[x] gluon/loss.py
[x] gluon/model_zoo/*
[x] gluon/nn/*
[x] gluon/rnn/*

[x] use np/npx interface in gluon/metric.py
[x] Implement infer_shape method

[x] gluon/nn/basic_layers.py::Dense
[x] gluon/nn/basic_layers.py::BatchNorm
[x] gluon/nn/basic_layers.py::InstanceNorm
[x] gluon/nn/basic_layers.py::LayerNorm
[x] gluon/nn/basic_layers.py::GroupNorm
[x] gluon/nn/conv_layers.py::_Conv
[x] gluon/nn/conv_layers.py::DeformableConvolution
[x] gluon/nn/conv_layers.py::ModulatedDeformableConvolution

[x] Remove hybrid mode with F in gluon/probability/*
[x] gluon/rnn/*

[x] conv_rnn_cell.py: implement forward, infer_shape, np/npx
[x] rnn_cell.py: implement forward, np/npx; use special infer_shape method based on layer, input_size and if it's bidirectional.
[x] rnn_layer.py: implement forward, infer_shape, np/npx

[x] fix issue np.average return ADT type; npx.pooling
[x] Copy control flow ops(loop_while, cond, foreach) from ndarray.contrib to mx.npx.control_flow
[x] Register some legacy ops in npx

[x] stes_op
[x] sync_batch_norm
[x] legacy pad (np.pad doesn't have backward computation for 'reflect" mode)
[x] Some rnn related: sequence_last, sequence_reverse, slice_channel, broadcast_greater, softsign

[x] Use forward, np/npx for all the gluon related tests; remove gluon tests with symbol inputs

[x] remove test_gluon_data_vision.py and test_gluon_probability_v1.py as related tests are covered in test_numpy_gluon_data_vision.py and test_gluon_probability_v2.py
[x] Test test_numpy_op.py::test_np_nan_to_num only for copy argument is set to True, since Inplace operations are not supported when recording in deferred compute mode

[x] Remove hybrid_block interface in gluon/block.py
[x] Remove hybrid_block interface in documentation and docstring

[x] update docs/python_docs/python/tutorials/packages/gluon/blocks/custom_layers
[x] remove python_tutorials/packages/gluon/blocks/custom_layers_beginners.md as it's duplicate to custom_layers
[ ] remove docs/python_docs/python/docstutorials/packages/legacy/ndarray/sparse/train_gluon as gluon2.0 do not support sparse
[x] update docs/python_docs/python/tutorials/packages/gluon/blocks/custom_loss
[x] update docs/python_docs/python/tutorials/packages/gluon/blocks/hybridize

[x] Turn on NumPy mode by default (#18631)
[x] Fix gluon2.0 reference leak.

Some skipped tests

tests/python/mkl/subgraphs/test_conv_subgraph.py::test_pos_concat_scale_align

Reason: Scale doesn't align in numpy for numpy operators

tests/python/mkl/subgraphs/test_fc_subgraph.py::test_fc_eltwise

Reason: Operator square, square_root, abs, exp cannot be found in numpy mode

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@mxnet-bot run ci [centos-cpu, centos-gpu, unix-cpu, unix-gpu]

Looks like GPU memory will not be released after using asnumpy() method for numpy ndarray on gpu context.
Code to reproduce:
import mxnet as mx
from mxnet import npx, gluon
from mxnet.gluon import nn
npx.set_np()

mx.context._current.set(mx.gpu(0))

def check_layer_forward_withinput(net, x):
    x_hybrid = x.copy()
    x.attach_grad()
    x_hybrid.attach_grad()
    net.initialize()
    with mx.autograd.record():
        out1 = net(x)
    out1.backward()
    net.hybridize()
    with mx.autograd.record():
        out2 = net(x_hybrid)
    out2.backward()
    a, b = mx.context.gpu_memory_info(0)
    print("Used memory {} GB, Total memory {} GB.".format((b - a) / (1024 * 1024 * 1024), b / (1024 * 1024 * 1024)))
    mx.test_utils.assert_almost_equal(x.grad, x_hybrid.grad, rtol=1e-5, atol=1e-6)
    mx.test_utils.assert_almost_equal(out1, out2, rtol=1e-5, atol=1e-6)

def test_slice_pooling2d():
    # transpose shape to bring feature dimension 'c' from 2nd position to last
    def transpose(shape):
        return (shape[0],) + shape[2:] + (shape[1],)

    for layout in ['NCHW', 'NHWC']:
        max_pooling = nn.MaxPool2D(layout=layout)
        avg_pooling = nn.AvgPool2D(layout=layout)
        global_maxpooling = nn.GlobalMaxPool2D(layout=layout)
        global_avgpooling = nn.GlobalAvgPool2D(layout=layout)
        pooling_layers = [max_pooling, avg_pooling, global_maxpooling, global_avgpooling]
        class Net(gluon.HybridBlock):
            def __init__(self,
                         slice,
                         pooling_layer,
                         **kwargs):
                super(Net, self).__init__(**kwargs)
                self.slice = slice
                self.pool0 = pooling_layer

            def forward(self, x):
                x_slice = mx.npx.slice(x, begin=self.slice[0], end=self.slice[1])
                out = self.pool0(x_slice)
                return out

        xshape = (16, 128, 256, 256)
        slice_shape = (4, 16, 32, 64)
        if layout == 'NHWC':
            xshape = transpose(xshape)
            slice_shape = transpose(slice_shape)
        x = mx.np.random.uniform(size=xshape)
        slice = [(0, 0, 0, 0), slice_shape]
        for i in range(len(pooling_layers)):
            net = Net(slice, pooling_layers[i])
            check_layer_forward_withinput(net, x)

if __name__ == '__main__':
    test_slice_pooling2d()

Before comment out mx.test_utils.assert_almost_equal() these two lines:
Used memory 2.142578125 GB, Total memory 14.755615234375 GB.
Used memory 4.119140625 GB, Total memory 14.755615234375 GB.
Used memory 4.619140625 GB, Total memory 14.755615234375 GB.
Used memory 5.119140625 GB, Total memory 14.755615234375 GB.
Used memory 5.119140625 GB, Total memory 14.755615234375 GB.
Used memory 6.119140625 GB, Total memory 14.755615234375 GB.
Used memory 6.619140625 GB, Total memory 14.755615234375 GB.
Used memory 7.119140625 GB, Total memory 14.755615234375 GB.

After comment out these two lines:
Used memory 2.142578125 GB, Total memory 14.755615234375 GB.
Used memory 2.142578125 GB, Total memory 14.755615234375 GB.
Used memory 2.1171875 GB, Total memory 14.755615234375 GB.
Used memory 2.1171875 GB, Total memory 14.755615234375 GB.
Used memory 2.1171875 GB, Total memory 14.755615234375 GB.
Used memory 2.1171875 GB, Total memory 14.755615234375 GB.
Used memory 2.1171875 GB, Total memory 14.755615234375 GB.
Used memory 2.6171875 GB, Total memory 14.755615234375 GB.

@mxnet-bot run ci [centos-gpu, unix-gpu]

@mxnet-bot run ci [centos-gpu]

@mxnet-bot run ci [centos-gpu, unix-gpu, windows-cpu, windows-gpu]

@mxnet-bot run ci [centos-gpu, unix-gpu, windows-cpu, windows-gpu]

@leezu @barry-jin A small general question - how does this deferred compute flow work when I have a network which has some static and some dynamic elements (e.g. I have 1 part that is static, then I do something on the output that can't be hybridized, then I have another hybridizable portion). In the previous interface I could do a Block containing 2 HybridBlocks and a non-hybridized portion inbetween. Can I have something similar now or I am left with not being able to hybridize anything (or having 2 models entirely)?

The dynamic part needs to be expressed with control flow ops if possible. Otherwise, Block containing 2 HybridBlocks should continue to work.

@leezu @barry-jin A small general question - how does this deferred compute flow work when I have a network which has some static and some dynamic elements (e.g. I have 1 part that is static, then I do something on the output that can't be hybridized, then I have another hybridizable portion). In the previous interface I could do a Block containing 2 HybridBlocks and a non-hybridized portion inbetween. Can I have something similar now or I am left with not being able to hybridize anything (or having 2 models entirely)?

Hi @ptrendx . I think the scenario you talked about is like this.
import mxnet as mx
from mxnet.gluon import HybridBlock, Block
from mxnet import autograd as ag

class Block1(HybridBlock):
    def __init__(self):
        super(Block1, self).__init__()

    def forward(self, a, b):
        return a - b

class Block2(HybridBlock):
    def __init__(self):
        super(Block2, self).__init__()

    def forward(self, a, b):
        if a > b:
            ret = a
        else:
            ret = b
        return ret

class Block3(HybridBlock):
    def __init__(self):
        super(Block3, self).__init__()

    def forward(self, a, b):
        return a * b

class MixedBlock(Block):
    def __init__(self, block1, block2, block3):
        super(MixedBlock, self).__init__()
        self.block1 = block1
        self.block2 = block2
        self.block3 = block3

    def forward(self, a, b):
        out1 = self.block1(a, b)
        out2 = self.block2(out1, b)
        out3 = self.block3(out2, a)
        return out3

block1, block2, block3 = Block1(), Block2(), Block3()
mix = MixedBlock(block1, block2, block3)
mix.initialize()
block1.hybridize()
block3.hybridize()
x_list = [mx.np.array([i]) for i in range(5)]
y_list = [mx.np.array([1])]*5
for x, y in zip(x_list, y_list):
    x.attach_grad()
    y.attach_grad()
    with ag.record():
        out = mix(x, y)
    out.backward()
    print(out, x.grad, y.grad)

And the output is
[0.] [1.] [0.]
[1.] [1.] [1.]
[2.] [1.] [2.]
[6.] [5.] [-3.]
[12.] [7.] [-4.]

Only block1 and block3 are hybridized while block2 has if-else conditions so I do not hybridize it.

@barry-jin Thanks for the examples, I just tested changing MixedBlock and Block2 to gluon.Block in your second example and then it works (so it actually looks the same as in 1.x) :-).

@mxnet-bot run ci [centos-cpu, centos-gpu, unix-cpu]

@mxnet-bot run ci [all]

@TristonC Thanks for your suggestions on improving the documentation!

@mxnet-bot run ci [centos-cpu]


[#1721] fix(coordinator): classCastExpection of boolean->String with yaml style remote client conf

What changes were proposed in this pull request?
fix classCastExpection of boolean->String with yaml style remote client conf
Why are the changes needed?
Fix: #1721
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests

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

Project coverage is 54.01%. Comparing base (6f6d35a) to head (bedaf04).
Report is 25 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1722      +/-   ##
============================================
- Coverage     54.86%   54.01%   -0.85%
- Complexity     2358     2531     +173
============================================
  Files           368      393      +25
  Lines         16379    18421    +2042
  Branches       1504     1665     +161
============================================
+ Hits           8986     9951     +965
- Misses         6862     7909    +1047
- Partials        531      561      +30

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