ng build can't have sourceMaps: true AND extractCss: true

Bug Report or Feature Request (mark with an x)
- x ] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)
- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions
Angular CLI: 6.0.4
Node: 10.9.0
OS: linux x64
Angular: 6.0.4
... animations, cli, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router, service-worker
Package                           Version
@angular-devkit/architect         0.6.4
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.4
@angular-devkit/schematics        0.6.4
@ngtools/webpack                  6.0.8
@schematics/angular               0.6.4
@schematics/update                0.6.4
rxjs                              6.2.2
typescript                        2.7.2
webpack                           4.8.3
Repro steps
Change this in angular.json:
{
  "projects": {
      "your-project": {
         "architect": {
             "build": {
                "configurations": {
                   "production": {
                        "sourceMap": "true"
                   }
                }
             }
         }
      }
  }
}

ng build --prod gives you the error below.
If you also change
   "extractCss": false,

the error goes away and the build succeeds.
The log given by the failure
With sourceMap: true and extractCss: true, the error at build time is:
 92% chunk asset optimization cleancss-webpack-plugin/####/node_modules/webpack-sources/node_modules/source-map/lib/source-map-generator.js:298
      throw new Error('Invalid mapping: ' + JSON.stringify({
      ^

Error: Invalid mapping: {"generated":{"line":626,"column":195},"source":"/####/node_modules/@bisnode/ui/build/css/components/_forms.scss","original":{"line":2,"column":-11},"name":null}
    at SourceMapGenerator_validateMapping [as _validateMapping] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-map-generator.js:298:13)
    at SourceMapGenerator_addMapping [as addMapping] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-map-generator.js:110:12)
    at /####/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:351:13
    at SourceNode_walk [as walk] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:230:9)
    at SourceNode_walk [as walk] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:226:13)
    at SourceNode_walk [as walk] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:226:13)
    at SourceNode_toStringWithSourceMap [as toStringWithSourceMap] (/####/node_modules/webpack-sources/node_modules/source-map/lib/source-node.js:342:8)
    at ConcatSource.proto.sourceAndMap (/####/node_modules/webpack-sources/lib/SourceAndMapMixin.js:30:32)
    at CachedSource.sourceAndMap (/####/node_modules/webpack-sources/lib/CachedSource.js:56:31)
    at files.filter.map.file (/####/node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/cleancss-webpack-plugin.js:52:48)
    at Array.map (<anonymous>)
    at hook (/####/node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/cleancss-webpack-plugin.js:44:18)
    at compilation.hooks.optimizeChunkAssets.tapPromise (/####/node_modules/@angular-devkit/build-angular/src/angular-cli-files/plugins/cleancss-webpack-plugin.js:11:101)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/####/node_modules/tapable/lib/HookCodeFactory.js:24:12), <anonymous>:13:1)
    at AsyncSeriesHook.lazyCompileHook [as _callAsync] (/####/node_modules/tapable/lib/Hook.js:35:21)
    at hooks.additionalAssets.callAsync.err (/####/node_modules/webpack/lib/Compilation.js:952:36)
error Command failed with exit code 1.

Desired functionality
Not sure, I can live with  sourceMap: true and extractCss: false.
All I need is better investigation assistance.
My use case is that I am investigating the startup behaviour and I need source maps temporarily switched on.  It won't stay that way.
Is this a known limitation ?
Mention any other details that might be useful
None.

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.
I have tried to replicate this by using scss and I was able to generate a sourcemap
``json
{
"version": 3,
"sources": [
"webpack:///./src/styles.scss"
],
"names": [],
"mappings": "AAEC,QACC",
"file": "styles.9500dc80ca2ab0fed6b7.css",
"sourcesContent": [
"/* You can add global styles to this file, and also import other style files */\r\na {\r\n\t&-hello {\r\n\t\tcolor: red;\t\r\n\t}\r\n}"
],
"sourceRoot": ""
}

From the above stacktrace it looks like might be something from<EMAIL_ADDRESS>
Thanks

Closing as inactive.

Actually, I have not reproduced it, upgraded to 6.1.5 there-about and have not seen the problem since.
Also, @bisnode/ui was updated since.


Count events

Can anyone show how can I add the count of events each day in the month view?

Any idea ??

why closed? This seems also has problem when moving the events to another date


Extend DescribeMethod

DescribeMethod is checking at the moment only for the second argument of the top-level describe to be a method name.
I can think for some extensions:
limit type
By default its disabled, but maybe we can enable it if we limit it to top-level describe with type: :model This should be configurable, since :helper and maybe others should be checked as well.
# good
describe FooClass, type: :model do; end

describe 'my tests' do; end

# bad
describe 'my tests', type: :model do; end

extend to nested describe
We could also check non-top-level describe. If the type of the top-level describe matches.
# good
describe FooClass, type: :model do
  describe '#foo' do; end
  describe '.foo' do; end
end

describe 'my tests' do
  describe 'foo' do; end
end

# bad
describe FooClass, type: :model do
  describe 'foo' do; end
end

What do you think?

Can also have a look into #680 as part if this.

I'm not sure I correctly understand this. Particularly, this bad example for nested describe:
describe FooClass, type: :model do
  describe 'foo' do; end
end

gets me worries as I tend to use example groups to group similar examples, e.g. validations:
RSpec.describe FooClass, type: :model do
  describe 'validations' do
    it 'validates the presence of the first name' do
      # ...
    end
    it 'validates uniqueness of kind' do
      # ...
    end
  end

  describe 'associations' do
    # ...
  end

  describe 'callbacks' do
    # ...
  end

  # etc
end

I don't really mind, however, I don't really understand the reasoning behind having several root example groups in a spec. I agree that they are still logically grouped by a spec file, however I can imagine that document output will be slightly off.
What I can think of as a middle ground is something like this:
# Associations
RSpec.describe FooClass, type: :model do
  # association-related examples
  end
end

# Validations
RSpec.describe FooClass, type: :model do
  # validation-related examples
end

with or without a nested describe namespace.
I don't see that model/helper specs are any different from others, on the contrary, models have declarations in it that not necessarily result in methods being defined on that model, but still need some testing.
@geniou I don't see your point very clearly, do you mind to elaborate on this a bit?

@geniou Can you please shed more light on the idea?

There's no clear way how to proceed.


Can Badgy charge LiPo batteries?

I'm considering soldering on a JST-PH header breakout to use with a LiPo battery.
The charging circuit can charge LIR2450 coin batteries. Can it also charge LiPo batteries, or would I need a separate charger for this?
Thanks!

Yes, the built in charging circuit is for LiPo.

Amazing, thanks for confirming!


Boot-Strapping "My Health Clinic" template fails

Error while creating build definition: The pipeline is not valid. A task is missing. The pipeline references a task called '4fa3aac0-0020-4832-9089-9979c9dd3e69'. This usually indicates the task isn't installed, and you may be able to install it from the Marketplace: https://marketplace.visualstudio.com. (Task version 0.*, job 'Phase_1', step 'Bower_3'.)
It appears that the pipeline has an invalid reference to a task.
I am using all free services with the account I was attempting to deploy to.  My organization name is tkon781 I have a couple of local agents running.  One agent in a Windows container and the other running as a service in my host operating system which is WIndows 10 Enterprise Build 10.0.19042.

Kindly refer to #626
Install the required extension and try again.


SB 3.0

Spring Boot 3

@AndriiMaliuta Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@AndriiMaliuta Thank you for signing the Contributor License Agreement!

@gregturn  @bclozel

@gregturn @bclozel


Initial release

Q
A

New sample
yes

What's in this Pull Request?
In SharePoint there used to be a 'copy shortcut' option in the right-click menu on a document. This feature is not available currently. Now we need to go to the share sub-menu to get a link to the document, but what is offered there is the docidredir link, not the full path.
This SPFx extension opens a dialog where the user can see the document full path. The Email Link button helps the user to share the link via default email client.

@sprider,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

thx Joseph, appreciated.


Seek feedback on existing data from providers

Description
As a developer, I want to ensure the data that we have in PDX Finder is in line with provider's expectations.
Folder with the query results here: https://drive.google.com/drive/folders/1NUk9ZH0FKGAZFU2c5Ecavyu-uwSROhzO
Acceptance criteria

[x] make a survey for providers
[x] send the survey to all contacts in the list

sent individual emails instead, got feedback


Parameterized Functions Always Error

I am working on a Rust based WASM project. I'm running some simple tests to familiarize myself with you awesome plugin. However, whenever I try to invoke functions which take parameters an error is thrown by the plugin.
Here is my sample rust code
#[no_mangle]
pub extern "C" fn add(left: i32, right: i32) -> i32 {
    left + right
}

#[no_mangle]
pub extern "C" fn foo() -> u32 {
    1
}

#[no_mangle]
pub extern "C" fn bar() -> u32 {
    42
}

This is built using cargo build --release --target wasm32-wasi.
When importing the WASM into godot and executing the function add like so
print_debug(wasm.function("add", [1, 2]))

The error in question is then thrown from this line here - https://github.com/ashtonmeuser/godot-wasm/blob/23cff0715f2e2a9fd3e00fbc7c5c9acb95825828/src/godot-wasm.cpp#L424
For clarity sake here is the GDScript I am using to test things out.
extends Node

# Called when the node enters the scene tree for the first time.
func _ready():
	var wasm: Wasm = Wasm.new()
	var file = FileAccess.open("res://wasi_test.wasm", FileAccess.READ)
	var buffer = file.get_buffer(file.get_length())
	#var imports = { "functions": { "index.callback": [self, "callback"] } } # Set imports according to Wasm module
	#wasm.load(buffer, {})

	var err = wasm.compile(buffer)
	print_debug(err)
	err = wasm.instantiate({})
	print_debug(err)
	print_debug(wasm.inspect())

	# invoke some functions
        # works returns 1
	print_debug(wasm.function("foo", []))
	# returns null for some reason
	print_debug(wasm.function("add", [1, 2]))
	# works returns 42
	print_debug(wasm.function("bar", []))

	file.close()

The functions which do not take any arguments and only return a value do work correctly.
I'm not entirely sure what the issue could be. I suspect perhaps something to do with the way the arguments are being collected?
When I invoke the add function from the cli using wasmer it works as expected.
 wasmer run --entrypoint add target/wasm32-wasi/release/wasi_test.wasm 1 2

Below is an inspection of the wasm.
Type: wasm
Size: 1.6 MB
Imports:
  Functions:
  Memories:
  Tables:
  Globals:
Exports:
  Functions:
    "add": [I32, I32] -> [I32]
    "foo": [] -> [I32]
    "bar": [] -> [I32]
  Memories:
    "memory": not shared (16 pages..)
  Tables:
  Globals:

I'm not sure if I'm just missing something in my Rust code that is needed or in my build process. Or if there is a bug in the godot-wasm addon. Any insight would be greatly appreciated.
Thanks!

Quick fix: Try i64/f64 parameter types.
@corysabol Thank you for your compliments and for your very thorough bug report. I scratched my head for a while on this one but have a theory as to what's going wrong.
Internally, GDScript uses 64-bit integers and floats (docs). Calling your exported Wasm function add(i32, i32) -> i32 with GDScript integers will supply incorrect argument types by default.
I'll leave this issue up as a reminder to myself to come up with a better solution. A stopgap solution may be a clearer error message or even a documentation page re: Wasm function parameter data sizes. A more longterm fix would likely include recording (im/ex)ported Wasm function signatures and automatically converting arguments. I'd be more than happy to hear your feedback on this or even welcome a PR.

Ah okay that makes sense then. I will try experimenting with using 64 bit data types and see how that fares. I would be happy to see if I can take stab at a PR if you can point me in the right direction / let me know a bit more about what you think needs to happen to improve things in this area.
I thinks clearer error messages is a great stop gap and some fleshed out documentation as well. As for a more permanent solution I wonder if having some additional type casting logic would make sense, or if that would create more headaches as opposed to just documenting that end users need to use a certain types to align with the API.
Cheers!

For posterity: closed for Godot 4.2 in https://github.com/ashtonmeuser/godot-wasm/commit/7ad22dd84ff05c99deac2b9620c8bfa60aaa2fc1 and Godot 3.x in https://github.com/ashtonmeuser/godot-wasm/commit/3cc750644760f186d50aab9d8e93dfd5021b34fe.


fix bad syntax

this is to fix new error since https://github.com/AdoptOpenJDK/openjdk-installer/pull/217
call Build.OpenJDK_generic.cmd  'ADOPT_NAME' is not recognized as an internal or external command, operable program or batch file.


Farm devnet

Description
How has this been tested?
Types of changes

[ ] Technical Debt (non-breaking change which removes unused code/assets)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The related ClickUp task has been linked to this PR
[ ] The person creating the pull request is listed in "Assignees"
[ ] My code follows the code style of this project .
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Screenshots or Loom Video (if appropriate):

Task linked: CU-2mjugnb UI: Farm - Update SSL with SDK

Task linked: CU-2phxcwn UI: Add Latest SDK for Compute Budget IX on Swap TX


tests fail for the library code

best guess would be that it's not getting the header files and iconv library in the dev build (but it's a guess)

fixed now


Resolved #20

Hey, @Kushagraw12!
Kindly, review my code and merge the PR.
Best,
Kushal

@KushalBhanot the issue has been resolved already. Moreover, your edits do not quite solve the issue! :)
Feel free to have a look on other issues!


Regression: Let's Encrypt not working with DDEV v1.23.4

Preliminary checklist

[X] I am using the latest stable version of DDEV (see upgrade guide)
[X] I have searched existing issues
[X] I have checked the troubleshooting guide
[X] I have run ddev debug test to include output below

Output of ddev debug test
Expand `ddev debug test` diagnostic information
[COPY-PASTE HERE THE OUTPUT OF `ddev debug test`]

Expected Behavior
Let's Encrypt should work as described
Actual Behavior
I see this in docker logs -f ddev-router:
2024-08-14T15:50:48Z ERR github.com/traefik/traefik/v3/pkg/provider/acme/provider.go:396 > Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [^d10\\.traefik\\.thefays\\.us$]: acme: error: 400 :: POST :: https://acme-staging-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rejectedIdentifier :: Invalid identifiers requested :: Cannot issue for \"^d10\\\\.traefik\\\\.thefays\\\\.us$\": Domain name contains an invalid character" ACME CA=https://acme-staging-v02.api.letsencrypt.org/directory acmeCA=https://acme-staging-v02.api.letsencrypt.org/directory domains=["^d10\\.traefik\\.thefays\\.us$"] providerName=acme-tlsChallenge.acme routerName=d10-web-80-https@file rule="Host(^d10\.traefik\.thefays\.us$)"
Reported in https://github.com/ddev/ddev/pull/6388#issuecomment-2288711456
Steps To Reproduce
Set up Let's Encrypt, simple config.yaml like
name: d10
type: drupal
docroot: web
php_version: "8.3"
webserver_type: nginx-fpm
xdebug_enabled: false
additional_hostnames: []
additional_fqdns: []
database:
    type: mariadb
    version: "10.11"
use_dns_when_possible: true
composer_version: "2"
web_environment: []
corepack_enable: false

And with global settings like
$ ddev config global |egrep "lets|tld"
<EMAIL_ADDRESS>project-tld=traefik.thefays.us
use-letsencrypt=true

After start, docker logs -f ddev-router
Anything else?
As reported,
changing the project .ddev/traefik/config/<project>.yaml to change Host() statements to remove regex characters in the hostnames fixes this.  (And remove #ddev-generated from the top of the file), ddev restart
In addition, with additional_hostnames set, the generated config in traefik comes out to be something like rule: Host(d10.traefik.thefays.us, one.traefik.thefays.us) but it should be
Host(`d10.traefik.thefays.us`) || Host(`one.traefik.thefays.us`)

Obviously you have been faster creating the issue, thanks again 👍
Just an idea, but I testet it in my case and it seems to work:
Maybe one can use the HostRegexp Syntax also if letsencrypt is enabled, if domains are defined in the tls section, for your example:
      rule: "HostRegexp(`^d10\.traefik\.thefays\.us$`) || HostRegexp(`^one\.traefik\.thefays\.us$`)"
      tls:
        certResolver: "acme-tlsChallenge"
        domains:
          - main: "d10.traefik.thefays.us"
            sans:
              - "one.traefik.thefays.us"

Please try out the HostRegexp in your setup. I don't see how it offers value when you have to explicitly specify the domains a second time.

I hope you'll try out

https://github.com/ddev/ddev/pull/6494
@h1nds1ght

Don't forget that you have to move your existing edited config settings out of the way or delete them to test


implement support for asyncio [double-plus-WIP]

DO NOT TRY THIS AT HOME JUST YET
Note: in the v2 API implementation PR, we removed the AsyncIOHTTPTransport. It might make sense to re-add it with this PR.

@beniwohli can you rebase against master when you can, I'd like to test this on twisted

@ciarancourtney done :) let me know how it goes!

Sorry I misunderstood the PR, I thought it added support for twisted. FYI I'm using 3.0.1 just fine for a twisted/thrift based RPC server using the public API

Hi, do you still plan to release this?

@menecio I think that this MR is a bit outdated and not closed... Support for asyncio was added in v4 of apt-agent-python.

@approxit unfortunately, that is not quite correct. We did merge some preliminary support for asyncio in 4.0 (like the usage of contextvars), but some work still remains to get proper support. I hope to get to this is in the coming few months.

Closing this, as most parts have been merged or are in the process of being merged in other PRs. Progress on asyncio can be tracked in #598


Disable PL/pgSQL creation

Disable PL/pgSQL procedural language creation, since it's created by default in modern postgres, and attempting to create it breaks hosted postrgres.

+1 MA.
The only way this could cause problems is if you're spinning up a new dev environment with Postgres < 9.4, right?

yep! It's even safer though, postgres < 9.0 I think


Add status badges to readme

Should we add some status badges to readme? Any suggestions for other useful ones?

Investigating
Under Consideration
In Development
Saved for Next Version
Needs more Discussion

Let's start with these badges first.


Add en moke clone for rebase

Changelog entry
Changelog category

Documentation

Additional information

This has already been merged elsewhere


Null safety

Hi again.
Is there a plan to support null safety for the generator sometime in the future?
Thanks.

I assume that you're referring to the null safety of dart and how we will interact with non-nullable types in the code analysis and generation. And (speaking for me) there absolutely is one.
The sqlparser integration(still WIP but complete feature-wise) already supports type derivation of (non-)null query parameters and type checking of (non-)nullable returns. Implementing this should mostly consist of more tests and maybe ten lines of code in the actual generator. Columns of entities and views already have a nullability assigned to it through the @ColumnInfo annotation. I'm not sure on how to proceed there yet, but I think we should use some combination of type/deprecation warnings and type checking errors while slowly phasing out the nullable parameter. This also depends on how optional the non-nullable types are (this is something I haven't checked out yet).
Let's track this feature here.
I've written a lot of Java and a bit of Rust before I started dabbling in Dart and the decision to have nullable types (even primitives like booleans!) seemed really backwards to me, so I'm very happy they found a solution and I am all for also supporting it in floor.
Btw, internally, vitus already introduced @nullable and @nonNull for annotating (non-)null returns of internal functions, just to get us ready for also using nonnullable types inside the floor codebase. This won't matter for users of floor but will probably ease our pain when migrating a lot more, even if the annotations were only cosmetically until now.

I do agree with everything @mqus mentioned. There is high interest in supporting Dart's non-nullable types!

Bookmark with lots of useful details: https://dart.dev/null-safety/understanding-null-safety

Work on null safety support has been started here https://github.com/vitusortner/floor/tree/nullsafety

Nice that you are working on it.
Would you mind publishing your branch as an unstable version to pub because I want to try it out.
If I include the dependency like so:
  floor:
    git:
      url: https://github.com/vitusortner/floor
      path: floor
      ref: nullsafety

I get the error Invalid description in the "floor" pubspec on the "floor_annotation" dependency: "../floor_annotation/" is a relative path, but this isn't a local pubspec. Even if I try to override the floor_annotation dependency it doesn't work.

Hi @dkunzler! I'll look into creating a nullsafety release. Until then, you can clone the repository and use the project that way. Dependency overrides have been faulty for a while and unluckily don't work in this scenario.

You can get the first null safe version of floor now on pub https://pub.dev/packages/floor/versions/1.0.0-nullsafety.0 🚀

Thank you, I appreciate your fast response!

We got flutter 2.0 the day before yesterday, any forecast on when this package will be updated?
Thanks!
@vitusortner

We're looking into it right now and we'll create a new null-safe release as soon as possible.

We just published the 1.0.0-nullsafety.1 release with support for Dart 2.12.0. We unluckily can't go stable as crucial dependencies haven't yet been migrated. If you encounter problems with 1.0.0-nullsafety.1, please raise a new issue on GitHub.

The stable, null-safe 1.0.0 release has just been published. Thanks to everyone that helped! 🎉


[TW#12672] Memory leak. WiFi + BT fails after 1.5h of operating.

Worked for ~1.5h (104min).
BT is scanning for nearby beacons and publishes a data related to each detected device into MQTT topic.
esp-idf #https://github.com/espressif/esp-idf/commit/1ddf40feb73386df26ac51bd80aac2210229b164 is used.
wifi_fail_log.txt
The following params used:
BLE gattc:
static esp_ble_scan_params_t ble_scan_params = {
        .scan_type                        = BLE_SCAN_TYPE_ACTIVE,
        .own_addr_type            = BLE_ADDR_TYPE_RPA_PUBLIC,
        .scan_filter_policy      = BLE_SCAN_FILTER_ALLOW_ALL,
        .scan_interval            = **220**,
        .scan_window                    = **25**
 };

From sdkconfig:
BTC_TASK_STACK_SIZE = 4096
SW_COEXIST_ENABLE = y

Scan duration is 60sec.
Tried to play with interval/window values. Seems to be a little helpful, e.g. after changing it from interval/window = 220/30 it increases the operating time before fail on ~15min.
But this values is inapplicable in our environment as we need longer window and shorter interval.
I've inserted the logging of free heap on every scan completion and it looks OK before wifi fail.
After such, it leaks without a hesitation.
Please pay an attention on my comments into log.
/*
 * ...
 *
 * A lot of similar logs reporting ~18000 bytes of free heap every minute when scan completes
 *
 * ...
 */

I (4701142) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (4701142) gattc: free heap: 18000
E (4761152) BT: btc_search_callback  BLE observe complete. Num Resp 130

I (4761152) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (4761152) gattc: free heap: 18000
E (4821162) BT: btc_search_callback  BLE observe complete. Num Resp 116

I (4821162) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (4821162) gattc: free heap: 17680
E (4881172) BT: btc_search_callback  BLE observe complete. Num Resp 78

I (4881172) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (4881172) gattc: free heap: 18000

/*
 * And here it starts the memory leak
 */

I (4930742) wifi: bcn_timout,ap_probe_send_start
I (4933252) wifi: ap_probe_send over, resett wifi status to disassoc
I (4933252) wifi: state: run -> init (1)
I (4933252) wifi: pm stop, total sleep time: 0/626181837

I (4933252) wifi: n:6 0, o:6 0, ap:255 255, sta:6 0, prof:1
E (4934012) aws_iot: failed! mbedtls_ssl_write returned -0x4e

/*
 * An error of IoT_Error_t (NETWORK_ATTEMPTING_RECONNECT)
 */

E (4934202) mqtt_task: rc = 4
E (4941182) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (4941182) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (4941182) gattc: free heap: 59384
E (4941792) aws_iot: failed! mbedtls_net_connect returned -0x52
E (4941792) mqtt_task: attempting reconnect failed, rc = 4

/*
 * After wifi fail, this fail occurs
 */

E (4949192) BT: command_timed_out hci layer timeout waiting for response to a command. opcode: 0x200c
E (5001192) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (5001192) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (5001192) gattc: free heap: 62564
E (5009172) BT: command_timed_out hci layer timeout waiting for response to a command. opcode: 0x200c
E (5061202) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (5061202) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (5061202) gattc: free heap: 61044
E (5069162) BT: command_timed_out hci layer timeout waiting for response to a command. opcode: 0x200c
E (5121202) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (5121202) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (5121202) gattc: free heap: 58760
E (5181202) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (5181202) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (5181202) gattc: free heap: 55944
E (5241202) BT: btc_search_callback  BLE observe complete. Num Resp 253

/*
 *...
 * Look into attached file
 * ...
 */

I (6201202) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (6201202) gattc: free heap: 4496
E (6261202) BT: btc_search_callback  BLE observe complete. Num Resp 253

I (6261202) gap_cb: ESP_GAP_SEARCH_INQ_CMPL_EVT
I (6261202) gattc: free heap: 1476
E (6261202) BT:  bta_dm_ble_observe start observe failed. status=0x3

E (6261212) gattc: Scan start failed
W (7229192) wifi: alloc eb len=76 type=2 fail

W (7229192) wifi: m f probe req l=0

W (8853012) wifi: alloc eb len=76 type=2 fail

W (8853012) wifi: m f probe req l=0

/*
 * nothing more
 */

interesting - I too am trying to implement something like this, and find the BLE gap observe just eventually stops seeing anything.

Try turning CONFIG_SW_COEXIST_ENABLE off, and increase the scan interval in esp_ble_scan_params_t from the 0x50 from the examples to 0x100
	esp_ble_scan_params_t _params = 	{ 		.scan_type = BLE_SCAN_TYPE_ACTIVE, 		.own_addr_type = BLE_ADDR_TYPE_PUBLIC, 		.scan_filter_policy = BLE_SCAN_FILTER_ALLOW_ALL, 		.scan_interval = 0x100, 		.scan_window = 0x30 	};

@FHFS Thanks for reply.
Turning CONFIG_SW_COEXIST_ENABLE hasn't helped, the picture is the same.
I think that problem is that I'm publishing MQTT messages too frequently.
I'll report here if I'll succeed.

Hi @mkonnov , how about this issue now? Is there any update?

Hi @FayeY .
Sadly not. I have bypassed this problem just by picking esp_restart() in bta_dm_ble_observe if status == BTM_NO_RESOURCES.
I will return to this issue in a nearest days so once I will fix it, I will share it here.
BTW, maybe it's not a memory leak at all, but it behaves as a leak: the issue makes itself felt after ~1h of operating.

@mkonnov , could help make sure that is MQTT cause memory leak or Bluetooth or Wifi something cause memory leak? We are doing testing of excluding MQTT.

@mkonnov , I try BLE scan and wifi connect AP without SW_COEXIST_ENABLE and MQTT, I cannot reproduce your problem. So could you try a test without MQTT, then we can make sure which module cause the memory leak.

@TianHao-Espressif could you post or pm the test code you are using? I am also trying to diagnose similar issues where either BLE scan stops seeing things and/or wifi disconnects and won't reconnect after an hour or so, but I am using mongoose-os (and their cloud build system) which complicates things. I would like a simple way to start with something that actually works (without mongoose, mqtt etc) and add back in things until it breaks.

@murraysst. I try BLE scan and wifi connect AP without SW_COEXIST_ENABLE and MQTT. It have no memory leak , then I put AP into sheildbox, then ESP32 station disconnect and try to reconnect, there's no memory leak, too. The test code is in attachment.
Archive.zip

Hi guys ! My apologies for long silence.
After I have found that BTM_NO_RESOURCES can indicate the lack of free heap to allocate and at the same time I have estimated the decreasing of free heap, therefore I concluded that it was a memory leak without a hesitation.
Now after a few updates of esp-idf, I'm not estimating such free heap decrease anymore, but my latest investigations brought me to my mistake.
I'm making BLE advertising and scan consequently in one task and I have found that
esp_ble_gap_start_advertising together with esp_ble_gap_start_scanning
is not starting advertising/scanning immediately due to callback-style API. We need to wait for event to be sure that scan/adv has started. Or not started.
This way, my error has been caused by the lack of synchronization between this two routines.
So I have used xEventGroupSetBits for appropriate events in esp_gap_cb callback and awaiting by  xEventGroupWaitBits this events in my app.
@TianHao-Espressif, @murraysst Thank you guys for your help.
I have tried the codes @TianHao-Espressif has shared and yes - there's no memory leak.

Is this problem solved?

@FayeY The problem is not solved, but things starts to be clear.
I can say exactly: it's not a memory leak.
The problem has been reproduced by turning off WiFi connection (on WiFi router).
After WiFi has tried to reconnect, it tooks too much memory it has been available and this way it tooks all the memory available. What leads to inability to scan and do whatever what uses memory allocation.
This way, I have walked through possible places that takes too much heap and noticed that my MQTT task takes 16kb for stack (btw, it has bee token from example) and recuded it to 10kb. And it works fine. Also, I have put a suspension of BLE task when MQTT task notices the reconnection attempt and resume it only after network is reconnected. All errors is from IoT_Error_t.
But for now I see the following error in a loop:
aws_iot: failed! mbedtls_net_connect returned -0x52
2 modules is running simultaneously in the same environment and this error occured only on one of them.
So do anybody have some suggestions ?

Also I often see the current fail:
ASSERT_ERR(0), in ld_fm.c at line 185Guru Meditation Error: Core  0 panic'ed (Interrupt wdt timeout on CPU0)
Do smbd know what it related to and where to look for solution ?
I know, it's a wdt timeout, I know how to increase its period, but I need to know the reason of that fail.
I have made a coredump and it says nothing bad.

@mkonnov , please check something:

do you use classic bt?
do you use dual core?
please update esp-idf to the newest.

@TianHao-Espressif  thanks for your reply.

I use BT dual mode
As far as I know, this is controlled from checkbox "Run FreeRTOS only on first core". If so, then yes, I'm running dual core.

esp-idf is the newest.

@mkonnov ，I'm very interesting at "often see the current fail".  So could you provide me your tests code?

@TianHao-Espressif please test it with with a huge amount of BT advertisers, as more as you can.
ble_mqtt_test.zip
Also hardcode your AWS certificates and WiFi credentials in aws_iot_mqtt_task.c. Sorry for crappy hardcodes, I tried to make it ASAP for you.
Thanks a lot.

@TianHao-Espressif
I have an updates. I have run this code with just a few advertisers and it fails.
You may be interested in the following crash report.
But I'm very interested in a reason of such fail, so please give me a direction to look for.
Pasting the crash report of the code I have attached above. Code hasn't been changed instead of my AWS key and WiFi credentials.
I (18472) gattc: REG_EVT
I (18472) gattc_cb: EVT 0, gattc if 4
I (18472) gattc: REG_EVT
I (18482) BT: ESP_GAP_BLE_SCAN_PARAM_SET_COMPLETE_EVT
ASSERT_ERR(bt_intcntl_finetgtintmsk_getf() == 1), in ea.c at line 497Guru Medit
ation Error of type LoadProhibited occurred on core  1. Exception was unhandled
.
Register dump:
PC      : 0x40086121  PS      : 0x00060033  A0      : 0x400879df  A1      : 0x3ffd6790
A2      : 0x00050023  A3      : 0x00000001  A4      : 0x3ffc4f38  A5      : 0x3ffc4f38
A6      : 0x00000001  A7      : 0x00060b20  A8      : 0x00000017  A9      : 0x00000002
A10     : 0x3ffc1398  A11     : 0x00000000  A12     : 0x3ffc510c  A13     : 0x3ffe31e8
A14     : 0x00000000  A15     : 0x00000000  SAR     : 0x00000015  EXCCAUSE: 0x0000001c
EXCVADDR: 0x00000048  LBEG    : 0x00000000  LEND    : 0x00000000  LCOUNT  : 0x00000000

Backtrace: 0x40086121:0x3ffd6790 0x400879dc:0x3ffd67b0 0x40087996:0x3ffd691c

Guru Meditation Error o

Despite I have shared my source code, here's a link to actual elf for which this crash has take place:
https://drive.google.com/open?id=0B5Q2K4xNERwCZkUtY2N1Ung4a2M

@TianHao-Espressif Hi there !
Have you tried the code I sent ? Is the problem I described reproducible ?
Thanks.

@mkonnov , I tried your code. But there's some logs

.[0;32mI (10502) gattc: REG_EVT.[0m
.[0;32mI (10512) BT: ESP_GAP_BLE_SCAN_PARAM_SET_COMPLETE_EVT.[0m
I (12132) wifi: pm start, type:0
.[0;31mE (12602) mqtt_task: rc = -13.[0m
.[0;31mE (12602) mqtt_task: An error occurred in the main loop (rc = -13), rebooting....[0m
I (12602) wifi: state: run -> init (0)
I (12602) wifi: pm stop, total sleep time: 0/473683

@TianHao-Espressif  Sorry, I assumed you have some.
Can I send you the certificate set via the email to you will test it out ?

@mkonnov , sure. Email is in my profile. You can click my head photo to see it.


Change default location when you create an image

Hello,
I am trying to use udocker (I am novel with this program). When I create the image that I want, I don't know where it is stored. So I would want to change the directory (adding a specific path) where the image is going to be stored.
How can I do that?
Thank you in advance,

They are all stored by default under ~/.udocker/containers you will find both their sha256 sum as directory and if theyre named there will be a symlink to the sha256sum dir, too.

Closing no activity


Ban statistics

In gitlab by @A-Lawrence on Jan 11, 2016, 21:18
Allow admins to generate ban statistics.

In gitlab by @A-Lawrence on Jan 14, 2016, 00:15
mentioned in commit fe5625d08677a672825103e6c95c32cee57778f2

In gitlab by @A-Lawrence on Jan 14, 2016, 00:15
mentioned in commit 797fe989dd19e7d185aca3cad27934e935bc03ca

In gitlab by @A-Lawrence on Feb 6, 2016, 13:19
Milestone removed

In gitlab by @A-Lawrence on Aug 20, 2016, 19:39
Removed ~98471 label


Document an SOP for external users to make a PR

I can help with this, but will need guidance from @nicoleruiz and @keilbeck as I don't know the current workflow. I think @mikebada and @msinclair2 should be able to help, we should be aiming for aligned SOP for MSO
Note: this may be easier to do after refactoring the repo: #462
However, in order to help @sabrinatoro help, we can provide some guidance for the current repo. @nicoleruiz:

Which file is the source file you edit? Is it so.obo or so.owl
Do you use oboedit or Protege
How do you assign ID ranges? Do you have an idranges file as is currently standard (see #462)
How do you build downstream products once you edit the source?

Once you answer these I can help come up with the SOP

I'm willing to answer any questions I can, but I first need to make sure I understand the acronyms, ha ha: SOP = standard operating procedure?  And what is PR?

I think I can answer these questions.  I also want to know what PR is.
so.obo is the file that is edited.
obo-edit is the editor used.
I don't think any ID ranges are assigned, if you mean ranges assigned to different editors.
OORT is run manually to build downstream products.
Is this right @nicoleruiz ?

PR = pull request.
OK, can you clarify, is so.obo still edited or is the mso file the source?
I strongly recommend assigning blocks of ID ranges, and having the ID ranges be in a file in github
For more background on standard github ontology setup and workflow practices, see:
https://docs.google.com/presentation/d/1nIybviEEJiRKHO2rkBMZsQ0QjtsHyU01_-9beZqD_Z4/edit#slide=id.p
And I recommend experimenting with:
https://github.com/INCATools/ontology-development-kit
Use it to generate a fake ontology repo, and then look at the generated internal documentation

Sorry just saw this ticket.
@msinclair2 yes everything you said is correct.
In obo-edit, we have set an ID profile for SO. This is the rule we use: SO:$sequence(7,0,9999999)$

Thanks, Nicole.  But, I don't know what an ID profile or rule in obo-edit is.

@msinclair2 I recommend using the ODK to create an example github repository according to standard conventions. This will give you an idranges file, plus a README-editors.md file that includes information on how the idranges file is used.
This is the template:
https://github.com/INCATools/ontology-development-kit/blob/master/template/src/ontology/README-editors.md.jinja2
Recall we set up an idrange for you for you to make PRs on RO: https://github.com/oborel/obo-relations/pull/233
The rule that @nicoleruiz is showing is analogous to the new entity creation preferences form in Protege.
@nicoleruiz it is standard it include an id-profiles file in the github repository that states what the range is for each person editing. This is necessary to avoid clashes. How do you manage this in SO at the moment?

Hi guys, my name is Dave and I am the new postdoc that is going to work on this. @nicoleruiz has shown me how to edit the so.obo files, but I could not get owl tools to help me generate the other files because of compatibility issues on my computer. She had to take care of it for me last time.
Nicole has suggested that I learn to use Protege instead because it the program that is still supported. She has sent me some tutorials from Mike and Michael that I will look through when I get the chance. @cmungall, Nicole has suggested that you would be very familiar with Protege and Robot, do you mind if contact you if I run into issues running the programs?
Thanks!

Hi David,
I recommend subscribing to
https://groups.google.com/forum/#!forum/obo-tools
There's a small group of us on obo-tools that are developing ROBOT etc -
you'll get faster responses than if you just email me
I also recommend subscribing too
https://groups.google.com/forum/#!forum/obo-discuss
On Mon, Mar 11, 2019 at 3:29 PM David Sant<EMAIL_ADDRESS>wrote:

Hi guys, my name is Dave and I am the new postdoc that is going to work on
this. @nicoleruiz https://github.com/nicoleruiz has shown me how to
edit the so.obo files, but I could not get owl tools to help me generate
the other files because of compatibility issues on my computer. She had to
take care of it for me last time.
Nicole has suggested that I learn to use Protege instead because it the
program that is still supported. She has sent me some tutorials from Mike
and Michael that I will look through when I get the chance. @cmungall
https://github.com/cmungall, Nicole has suggested that you would be
very familiar with Protege and Robot, do you mind if contact you if I run
into issues running the programs?
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/463#issuecomment-471686996,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADGOY1iggs5264pSLGbCBUa1NpqXM_zks5vVq6mgaJpZM4bDwdX
.

Thank you for the help. I will do as you suggested.

Hi @cmungall,
I have finally updated the SO repository to be able to effectively work with pull requests. I have included as much information in the README as I thought could help. As far as I am aware, MSO is no longer being updated along with the SO, so for now I think we should only focus on SO.
Until now, our group has been editing the so.obo file, but the Makefile can run with either so.owl or so.obo. I have included this info in the README so that editors will be aware that they can work with either file.
I am still working with OBOedit, but have been practicing working with Protege. However, as far as I am aware, the build will end with the same output.
@nicoleruiz mentioned how we assigned the ranges. The last few that I have added have been given the IDs SO:0002226-SO:0002231. These are not the highest IDs, as one of the oldest terms (gene_segment) actually has the ID SO:3000000.
The downstream products are now created using the Makefile, which uses OWLTools Ontology Release Tool.
Your other issue request mentions using underscores instead of spaces and no special characters in terms. This is not yet in the README--do you think it should be included?
Do you think there should be a separate SOP from the README.md document that is now included with the repository? Is there any other info that needs to be included in the README?
Thanks,
Dave

Hi Dave
I think you should settle on one file being the source, and derive everything from that. I would use the so.obo file, so you can edit using either OE or Protege. It's conventional to call this something like so-edit.obo, but what you have set up seems like a great first step!
For the IDs I recommend an ID ranges file to document which range each editor has

I am happy to server as an alpha tester for the SOP.  There is a
PR I want to submit to fix an open ticket.
Chris Mungall<EMAIL_ADDRESS>writes:

Hi Dave
I think you should settle on one file being the source, and derive everything from that. I would use the so.obo file, so you can edit using either OE or Protege. It's conventional to call this something like so-edit.obo, but what you have set up seems like a great first step!
For the IDs I recommend an ID ranges file to document which range each editor has
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/463#issuecomment-606316690
Hi Dave
I think you should settle on one file being the source, and derive everything
from that. I would use the so.obo file, so you can edit using either OE or
Protege. It's conventional to call this something like so-edit.obo, but what
you have set up seems like a great first step!
For the IDs I recommend an ID ranges file to document which range each editor
has
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.*

Hi @diekhans,
I am sorry nobody has gotten to the issue requests. When I joined the group, a graduate student had kindly volunteered some of her time to update requests even though it had nothing to do with her project. Once she graduated, it was left alone until I was able to take over. I have not looked at any of the requests from before 2019. If you would like to try generating your own files and sending a pull request, I would be glad to use it as a test case to see if this will work as well as I hope it does. I believe all of the instructions for using the Makefile are on the README.md. It requires OWLTools, but I have found that most people that know ontologies are familiar with OWLTools. Let me know if any info is missing or it doesn't work and I will try to respond as quickly as I can.
Thanks,
Dave

Dave, it was part of Nicole’s project and she published on it. Not sure where you got that idea from.
From: David Sant<EMAIL_ADDRESS>Reply-To: The-Sequence-Ontology/SO-Ontologies<EMAIL_ADDRESS>Date: Monday, March 30, 2020 at 6:49 PM
To: The-Sequence-Ontology/SO-Ontologies<EMAIL_ADDRESS>Cc: Karen Eilbeck<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [The-Sequence-Ontology/SO-Ontologies] Document an SOP for external users to make a PR (#463)
Hi @diekhanshttps://github.com/diekhans,
I am sorry nobody has gotten to the issue requests. When I joined the group, a graduate student had kindly volunteered some of her time to update requests even though it had nothing to do with her project. Once she graduated, it was left alone until I was able to take over. I have not looked at any of the requests from before 2019. If you would like to try generating your own files and sending a pull request, I would be glad to use it as a test case to see if this will work as well as I hope it does. I believe all of the instructions for using the Makefile are on the README.md. It requires OWLTools, but I have found that most people that know ontologies are familiar with OWLTools. Let me know if any info is missing or it doesn't work and I will try to respond as quickly as I can.
Thanks,
Dave
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/The-Sequence-Ontology/SO-Ontologies/issues/463#issuecomment-606330189, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACS6AF2VMAUV6JZDIJ67BX3RKE4Y7ANCNFSM4GYPA5LQ.

Hi @cmungall,
I have added an edit file, so-edit.obo. I have updated the Makefile to work from so-edit.obo, as you have suggested.
I have a couple of questions about the ID ranges, however. The Eilbeck lab has currently used IDs for SO:0000001-SO:0002234. I was thinking perhaps we could block off perhaps up through SO:0004000 for our group. For the past several years we have had one person in the group update the files, so I think a single range for our group should be sufficient. Should we make a range for pull requests? I was thinking perhaps from SO:0004001-SO:0005000 might be more than enough. We do not have any terms used between SO:000234 and SO:0005836, so I thought that range would be appropriate. You have more experience with this, so I would like your opinion--what do you think? Do you think a single range for pull requests is sufficient until we have more than one group submitting pull requests?
Additionally, as for making a record of which ranges are available for which editors, do you just put this in a text file like perhaps "ID_ranges.txt"? I was thinking there could just be one line per editor with the info about the ranges to use, such as "Eilbeck Lab: SO:0000001-SO:0004000". What have other groups done?
Thanks,
Dave

The danger is from clashing IDs, that's why it's best to assign a range to
either an individual (or a collection of individuals who are internally
coordinated if they have their own mechanism for avoiding clashes.. but
really I would recommend individuals)
it's a bit of a pain to set up but only has to be done once per
contributor, and most ontologies have a relatively low number of
contributors that can get over the hurdle of using protege or oboedit
It's up to you whether the id-ranges file is a txt file or the more
standard owl file, it's more of a social mechanism. The person making the
PR for a new term has to know they have to do some Protege configuration to
assign things in a range. But everything should all be in the same file
You could also try other workflows. E.g. external people just use a UUID,
and then you and the core editors would replace these with IDs. But you'll
want mechanisms in place to stop these escaping
On Tue, Apr 14, 2020 at 10:46 AM David Sant<EMAIL_ADDRESS>wrote:

Hi @cmungall https://github.com/cmungall,
I have added an edit file, so-edit.obo. I have updated the Makefile to
work from so-edit.obo, as you have suggested.
I have a couple of questions about the ID ranges, however. The Eilbeck lab
has currently used IDs for SO:0000001-SO:0002234. I was thinking perhaps we
could block off perhaps up through SO:0004000 for our group. For the past
several years we have had one person in the group update the files, so I
think a single range for our group should be sufficient. Should we make a
range for pull requests? I was thinking perhaps from SO:0004001-SO:0005000
might be more than enough. We do not have any terms used between SO:000234
and SO:0005836, so I thought that range would be appropriate. You have more
experience with this, so I would like your opinion--what do you think? Do
you think a single range for pull requests is sufficient until we have more
than one group submitting pull requests?
Additionally, as for making a record of which ranges are available for
which editors, do you just put this in a text file like perhaps
"ID_ranges.txt"? I was thinking there could just be one line per editor
with the info about the ranges to use, such as "Eilbeck Lab:
SO:0000001-SO:0004000". What have other groups done?
Thanks,
Dave
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/463#issuecomment-613584246,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOLZPWJEU4TKJC2UGOTRMSON7ANCNFSM4GYPA5LQ
.

Hi @cmungall,
I have created a tab-delimited text file ID_ranges.txt that contains the ranges that should be used by different groups. I have added information about this in the README.md so that contributors will know to use IDs in a certain range. I also mentioned that they can create an issue request to ask for ranges and I can reserve a range for their group. I think this fulfills everything in your issue requests. I hope SO is fully ready for pull requests now. Please let us know if anything else needs to be updated.
Thanks,
Dave

perfect thanks!
On Wed, Apr 22, 2020 at 2:25 PM David Sant<EMAIL_ADDRESS>wrote:

Hi @cmungall https://github.com/cmungall,
I have created a tab-delimited text file ID_ranges.txt that contains the
ranges that should be used by different groups. I have added information
about this in the README.md so that contributors will know to use IDs in a
certain range. I also mentioned that they can create an issue request to
ask for ranges and I can reserve a range for their group. I think this
fulfills everything in your issue requests. I hope SO is fully ready for
pull requests now. Please let us know if anything else needs to be updated.
Thanks,
Dave
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/463#issuecomment-618048601,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOMSSYFLCZV7VYR4MIDRN5OCVANCNFSM4GYPA5LQ
.


failed downloading 'https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.18.0.zip' which is required by binary target 'onnxruntime': badResponseStatusCode(404)

I added 'onnxruntime-swift-package-manager' in my Xcode project, but I got error like this.
xcodebuild: error: Could not resolve package dependencies:
  failed downloading 'https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.18.0.zip' which is required by binary target 'onnxruntime': badResponseStatusCode(404)
  failed downloading 'https://download.onnxruntime.ai/pod-archive-onnxruntime-extensions-c-0.11.0.zip' which is required by binary target 'onnxruntime_extensions': badResponseStatusCode(404)
  fatalError

and I visited the https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.18.0.zip on website, i got error like this.
The requested content does not exist.
HttpStatusCode: 404
ErrorCode: WebContentNotFound
RequestId : ec3b033f-801e-00a1-52d7-c7ef5a000000
TimeStamp : 2024-06-26T14:46:26.1417489Z

How can I solve this error?

I tried https://download.onnxruntime.ai/pod-archive-onnxruntime-c-1.18.0.zip and it's working currently.


Missing readers in SAC groups

When SAC groups are created, it seems like the SAC is not reader of the group he/she is member of.
Example:
{
  "id": "ICLR.cc/2022/Conference/Paper1/Senior_Area_Chairs",
  "cdate":<PHONE_NUMBER>821,
  "ddate": null,
  "tcdate":<PHONE_NUMBER>821,
  "tmdate":<PHONE_NUMBER>710,
  "tddate": null,
  "web": null,
  "signatures": [
    "ICLR.cc/2022/Conference"
  ],
  "signatories": [
    "ICLR.cc/2022/Conference",
    "ICLR.cc/2022/Conference/Paper1/Senior_Area_Chairs"
  ],
  "readers": [
    "ICLR.cc/2022/Conference",
    "ICLR.cc/2022/Conference/Program_Chairs" // ICLR.cc/2022/Conference/Paper1/Senior_Area_Chairs is not a reader!
  ],
  "nonreaders": [
    "ICLR.cc/2022/Conference/Paper1/Authors"
  ],
  "writers": [
    "ICLR.cc/2022/Conference"
  ],
  "members": [
    "~Carlos_Mondragon1"
  ],
  "tauthor": "OpenReview.net"
}

I think this issues is fixed by #1120 cc @purujitgoyal


SCMO-9967 Added nullIfAbsent flag to transform body plugins

Jira Task
Description
Allows instances of the transform-request/response plugin to set the nullIfAbsent flag to false (true by default). Normally, if an attribute in the body.set mapping configuration is not found, an explicit null is set in the body under that key. This flag enables dropping the key instead.
Motivation and Context
See description in JIRA ticket for motivation
Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] Tests (extending the test suite)
[ ] Documentation Update (if none of the other choices apply)

How has this been tested?

Unit tests in pyron, usage in Evluma localstack
Screenshots (if appropriate):
Checklist:

[x] My code follows the code style of this project.
[x] I have added tests to cover my changes
[x] All new and existing tests passed
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Further comments

may need to udpate the doc also with an example of this flag and a statement about this configuration.

@ce-rbabu That's what the SCMO-9968 is for!


ZCLread Basic Attributes returning empty Value or not a valid AttributeValue

When running ZCLread for Basic cluster not all Attributes are returning Value or valid AttributeValue
List of Attributes returning Null/Empty Value filed:

ProductName
VendorName
UserLabel
Location
SoftwareVersionString
ManufacturingDate
PartNumber
ProductURL
ProductLabel
SerialNumber

Controller logs:
VendorName:
chip-device-ctrl > zclread Basic VendorName 1 0 0
[1625878813.435173][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56414.
[1625878813.435280][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22133786 msec
[1625878813.435340][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625878813.435559][113310:113310] CHIP:IN: Secure msg send status No Error
[1625878813.458134][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625878813.458292][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56414
[1625878813.458525][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625878813.458776][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625878813.458826][113310:113317] CHIP:ZCL:   attributeId: 0x0001
[1625878813.458878][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625878813.458937][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625878813.458980][113310:113317] CHIP:ZCL:   value:
[1625878813.459054][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625878813.459424][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56414.
[1625878813.459535][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22133811 msec
[1625878813.459585][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625878813.459792][113310:113317] CHIP:IN: Secure msg send status No Error

ProductName:
chip-device-ctrl > zclread Basic ProductName 1 0 0
[1625878900.304690][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56415.
[1625878900.304785][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22220656 msec
[1625878900.304838][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625878900.305043][113310:113310] CHIP:IN: Secure msg send status No Error
[1625878900.320995][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625878900.321125][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56415
[1625878900.321310][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625878900.321388][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625878900.321423][113310:113317] CHIP:ZCL:   attributeId: 0x0003
[1625878900.321452][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625878900.321482][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625878900.321512][113310:113317] CHIP:ZCL:   value:
[1625878900.321547][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625878900.321762][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56415.
[1625878900.321813][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22220673 msec
[1625878900.321841][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625878900.322011][113310:113317] CHIP:IN: Secure msg send status No Error

UserLabel:
chip-device-ctrl > zclread Basic UserLabel 1 0 0
[1625878968.489257][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56417.
[1625878968.489342][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22288840 msec
[1625878968.489387][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625878968.489579][113310:113310] CHIP:IN: Secure msg send status No Error
[1625878968.500133][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625878968.500260][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56417
[1625878968.500446][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625878968.500486][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625878968.500543][113310:113317] CHIP:ZCL:   attributeId: 0x0005
[1625878968.500599][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625878968.500629][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625878968.500661][113310:113317] CHIP:ZCL:   value:
[1625878968.500692][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625878968.500923][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56417.
[1625878968.500989][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22288852 msec
[1625878968.501022][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625878968.501211][113310:113317] CHIP:IN: Secure msg send status No Error

Location
chip-device-ctrl > zclread Basic Location 1 0 0
[1625878981.816976][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56418.
[1625878981.817060][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22302168 msec
[1625878981.817105][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625878981.817286][113310:113310] CHIP:IN: Secure msg send status No Error
[1625878981.839884][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625878981.840076][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56418
[1625878981.840374][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625878981.840444][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625878981.840504][113310:113317] CHIP:ZCL:   attributeId: 0x0006
[1625878981.840588][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625878981.840641][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625878981.840696][113310:113317] CHIP:ZCL:   value:
[1625878981.840756][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625878981.841072][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56418.
[1625878981.841259][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22302192 msec
[1625878981.841323][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625878981.841593][113310:113317] CHIP:IN: Secure msg send status No Error

HardwareVersionString
chip-device-ctrl > zclread Basic HardwareVersionString 1 0 0
[1625879041.375272][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56420.
[1625879041.375357][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22361726 msec
[1625879041.375403][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625879041.375579][113310:113310] CHIP:IN: Secure msg send status No Error
[1625879041.385317][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625879041.385454][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56420
[1625879041.385653][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625879041.385701][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625879041.385740][113310:113317] CHIP:ZCL:   attributeId: 0x0008
[1625879041.385776][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625879041.385805][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625879041.385838][113310:113317] CHIP:ZCL:   value:
[1625879041.385875][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625879041.386101][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56420.
[1625879041.386218][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22361737 msec
[1625879041.386313][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625879041.386545][113310:113317] CHIP:IN: Secure msg send status No Error

SoftwareVersionString:
chip-device-ctrl > zclread Basic SoftwareVersionString 1 0 0
[1625879097.017481][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56421.
[1625879097.017577][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22417369 msec
[1625879097.017630][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625879097.017883][113310:113310] CHIP:IN: Secure msg send status No Error
[1625879097.740863][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625879097.741057][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56421
[1625879097.741350][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625879097.741420][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625879097.741480][113310:113317] CHIP:ZCL:   attributeId: 0x000a
[1625879097.741534][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625879097.741587][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625879097.741642][113310:113317] CHIP:ZCL:   value:
[1625879097.741701][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625879097.742078][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56421.
[1625879097.742184][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22418093 msec
[1625879097.742307][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625879097.742501][113310:113317] CHIP:IN: Secure msg send status No Error

ManufacturingDate
chip-device-ctrl > zclread Basic ManufacturingDate 1 0 0
[1625879154.796207][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56423.
[1625879154.796315][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22475147 msec
[1625879154.796377][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625879154.796659][113310:113310] CHIP:IN: Secure msg send status No Error
[1625879155.807149][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625879155.807307][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56423
[1625879155.807539][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625879155.807637][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625879155.807684][113310:113317] CHIP:ZCL:   attributeId: 0x000b
[1625879155.807725][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625879155.807765][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625879155.807838][113310:113317] CHIP:ZCL:   value:
[1625879155.807884][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625879155.808237][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56423.
[1625879155.808360][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22476159 msec
[1625879155.808409][113310:113317] CHIP:IN: Sending secure msg on generic transport
chip-device-ctrl > [1625879155.808633][113310:113317] CHIP:IN: Secure msg send status No Error

PartNumber
chip-device-ctrl > zclread Basic PartNumber 1 0 0
[1625879265.385086][113310:113310] CHIP:IN: Encrypted message 0x25ce2138 from 0x000000000001B669 to 0x0000000000000001 of type 2 and protocolId 5 on exchange 56424.
[1625879265.385190][113310:113310] CHIP:IN: Sending msg 0x25ce2138 to 0x0000000000000001 at utc time: 22585736 msec
[1625879265.385251][113310:113310] CHIP:IN: Sending secure msg on generic transport
[1625879265.385479][113310:113310] CHIP:IN: Secure msg send status No Error
[1625879265.401691][113310:113317] CHIP:IN: Secure transport received message destined to fabric 0, node 0x000000000001B669. Key ID 3
[1625879265.401822][113310:113317] CHIP:EM: Received message of type 5 and protocolId 5 on exchange 56424
[1625879265.402006][113310:113317] CHIP:ZCL: ReadAttributesResponse:
[1625879265.402042][113310:113317] CHIP:ZCL:   ClusterId: 0x0028
[1625879265.402076][113310:113317] CHIP:ZCL:   attributeId: 0x000c
[1625879265.402111][113310:113317] CHIP:ZCL:   status: Success                (0x0000)
[1625879265.402157][113310:113317] CHIP:ZCL:   attribute TLV Type: 0x0c
[1625879265.402204][113310:113317] CHIP:ZCL:   value:
[1625879265.402296][113310:113317] CHIP:ZCL:   attributeValue: (span of length 0)
[1625879265.402568][113310:113317] CHIP:IN: Encrypted message 0xffff82fddef0 from 0x000000000001B669 to 0x0000000000000001 of type 16 and protocolId 0 on exchange 56424.
[1625879265.402653][113310:113317] CHIP:IN: Sending msg 0xffff82fddef0 to 0x0000000000000001 at utc time: 22585754 msec
[1625879265.402699][113310:113317] CHIP:IN: Sending secure msg on generic transport
[1625879265.402892][113310:113317] CHIP:IN: Secure msg send status No Error

should be fixed in https://github.com/project-chip/connectedhomeip/pull/8241

Fixed via #8241


Editing categories of an existing picture: Reuse categories selection UI from the Upload Wizard

I think categories editing should be revamped: It currently uses a special UI, which takes time to improve and maintain.
It would be better if it reused the existing category selection UI of the Upload Wizard.

@nicolas-raoul Can I work on it?

@Ayan-10 Sure, thanks! :-)

@nicolas-raoul Should I show already selected categories In this UI? If yes, then how do you prefer to show those?

Yes, that would be great!
They could show just like in the current upload wizard when you:

Select some categories
Tap "Previous"
Tap "Next". At this step you should see selected the categories from step 1.

@nicolas-raoul I was talking about the previously selected categories. In the current update UI, the previously selected (While uploading) categories are shown in a Textview. Is it necessary to show the previously selected (While uploading) categories in this new UI? If yes then how do you prefer to show those?

Ah, good point!
Yes, showing previously selected categories would be great!
Showing them the same way as when uploading is fine.
Actually, using the exact same logic to remember previously used categories (both when uploading and when categorizing existing pictures) would be ideal.
Example: If I categorize an existing picture as "building", then chances are high that next time I categorize another existing picture I will also want to categorize it as "building".

@nicolas-raoul Sorry, but I am not getting your point can you explain me a little elaborately.
In the current UI, previously (while uploading the image) selected categories are shown in Textview.
Like this

Where should I show these previously (while uploading the image) selected categories in the existing category selection UI of the Upload Wizard?

Thank you for the screenshot, that makes things clearer.
What you highlighted in red (categories that the existing picture currently has) should be shown as pre-selected checkboxes.
Some categories such as All free media are "technical", do not worry if they do not appear. If they appear it is OK too, though.
Example of the current category edition UI, and of how the future category edition UI could look like when first opening it:


Create LICENSE.md

Name ha been changed

Remember that you are fixing an issue, so it is important to ask the owner in the comment section of the issue to assign it to you.

Okey.Thank you for the info


Where is parent POM?

"Getting started" examples uses a parent pom, where is it?
https://github.com/GoogleCloudPlatform/getting-started-java/blob/master/pom.xml#L25

The parent pom is provided by this project https://github.com/GoogleCloudPlatform/java-repo-tools That said, you should be able to safely remove the parent definition and have the sample still work. If it doesn't, that's definitely a bug.
Closing, since hopefully I answered your question but feel free to reopen.


ufw returns errors

Your Windows build number:  (Type ver at a Windows Command Prompt)

15063

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

Typing the command "ufw status" returns the following error:
"ERROR: problem running iptables: iptables v1.6.0: can't initialize iptables table 'filter': Table does not exist (or do you need to insmod?) Perhaps iptables or your kernel needs to be upgraded."

What's wrong / what should be happening instead:

Command should be returning "Status: inactive" instead. The ufw enable and disable commands don't work either.

Strace of the failing command, if applicable:  (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)

Running "strace -o strace.txt -ff ufw status" produces the following files (renamed to be uploadable):
strace.366.txt
strace.367.txt
strace.368.txt

iptables has both userspace and kernelspace components.  The kernel module part of iptables does not exist in WSL (which is why it asks you to run insmod, since it's not detecting the expected module).  I think it will be neat if MS decides to support something like IPtables though.

#767


Missing std io error impls for ReadExactError & WriteAllError

Currently depends on changes from https://github.com/rust-embedded/embedded-hal/pull/472.
I don't think the move of to_std_error to embedded-io will cause any stabilization concerns, it seems unlikely that that signature would change. If it is, I can make this hidden within embedded-io and we can duplicate the function for the adapters crate.

with the From impls I added, to_std_error becomes 1 line: std::io::Error::new(err.kind().into(), format!("{:?}", err)) . With that I think it's less critical to share it, I'd rather not expose it as public API.

Ah, good point! Changed :).

Incorporated into #472. Thank you! :)


OpenClassroom IE (Closes #234)

New IE from me. http://openclassroom.stanford.edu/

I already started and just pushed an IE for OpenClassroom. If the current implementation is missing anything, feel free to comment / or pull request on what.
Since the current implementation supports downloading whole courses (or even youtube-dl openclassroom.stanford.edu), I think it's preferable.


Mix up in iot_test_common_io_internal.h between pwm and power conditi…

Fix conditional compile mixup in iot_test_common_io_internal.h.
Description

There looks like some confusion with conditional compiles for pwm and power.  Fixed them.
Checklist:

[ x ] I have tested my changes. No regression in existing tests.
[ x ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

/bot run checks

/bot run checks

/bot run checks

/bot run checks


chore(main): release 1.1.1

:robot: I have created a release beep boop
1.1.1 (2023-04-20)
Bug Fixes

(node:43476) [DEP0128] DeprecationWarning: Invalid 'main' field in ... (d326a57)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/LinLin00000000/openai-billing/releases/tag/v1.1.1 :sunflower:


Save window position and size until Quit

A couple of things with this one:

Creating a electron-settings "Defaults" object for easy reset on Quit
Listening for cropperWindow move and 'resize` and saving x,y & position
On Quit, reset to "Defaults"

Gonna close this, as #76 does the same thing, and more.


getOutputs() documentation is sparse.

Please can the contents/shape of the dictionary output by getOutputs() be documented?  From my testing it appears that the output is a dictionary of objects.
dictionary<string> = object {
     paramType: ???
     type: number
     value: any    <- guessing this depends on the type parameter
}

e.g.

It would be good to document the structure of the keys for the dictionary, and also the elements/fields within each object.
Thanks!

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

ID: 3da99044-d3b2-e660-b305-dd907182af4a
Version Independent ID: 3da99044-d3b2-e660-b305-dd907182af4a
Content: control.getOutputs (Client API reference) - Power Apps
Content Source: powerapps-docs/developer/model-driven-apps/clientapi/reference/controls/getoutputs.md
Service: powerapps
Sub-service: mda-developer
GitHub Login: @noazarur-microsoft
Microsoft Alias: noazarur

Thanks for your comment, @filcole. This issue has been assigned to the doc author for review.

The reason for asking is to improve/clarify the @types/xrm type definitions:
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62749

@filcole
My guess is that this will vary by control and will depend on the manifest and what is defined for https://learn.microsoft.com/en-us/power-apps/developer/component-framework/reference/control/getoutputschema
@noazarur-microsoft is there a connection here?


Duplicate operation Ids (Currently blocking Microsoft Graph SDK PowerShell releases)

Running the weekly open Api refresh pipeline updates the sliced Open Api files in PowerShell with duplicate operation Ids causing AutoREST build failures.
This is an example of a call made to DevX API to slice the larger Open API file to small files based on tags passed to the service.
https://devxapi-func-prod-eastus.azurewebsites.net/$openapi?tags=^users.calendar$&title=Calendar&openapiversion=3&style=Powershell&fileName=powershell_v2&graphVersion=v1.0&singularizeOperationIds=true
If you execute a GET request and search for user.calendar.calendarView.instance_ListExtension, you will see that the operation Id has been assigned to two different paths.

Attached is a file showing all the duplicated operation Ids for v1.0 paths.
duplicateOperationIds.csv

When the refresh runs, there is a ForceRefresh query parameter passed to DevX and my expectation is that no stale data will be downloaded. Is there something else that needs to be done to ensure freshness of data?

@timayabi2020 @irvinesunday @Ndiritu
To summarize our earlier discussion, the conversion library is not to blame for the duplicate operation ids in the document.
This is also validated at PR level in the metadata repo using the check added at the link below.
https://github.com/microsoftgraph/msgraph-metadata/blob/350c13155dbf986baee9b9664357e343a4059abf/.github/workflows/openapi-parser-validation.yml#L41
The issue causing the duplicate Id is the singularization logic in devX api which we discovered due to updated groupings of paths( paths for functions/actions moved to other files making the bug apparent) due to the issue at https://github.com/microsoft/OpenAPI.NET.OData/issues/605.
For now we can close this specific issue(regarding duplicate operation ids) as it is not an issue with the library and follow it up on devXApi via https://github.com/microsoftgraph/microsoft-graph-devx-api/issues/2255
I'll also provide more details on the tags grouping issue at https://github.com/microsoft/OpenAPI.NET.OData/issues/605


Full i18n support

[x] en
[x] zh-Hans
[x] zh-Hant

My ability is limited, only supports those languages temporarily.


Rename mutation_support into twoarg_support

Core

Rename mutation_support into twoarg_support
Rename Mutation(Not)Supported into TwoArg(Not)Supported

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

Project coverage is 94.94%. Comparing base (cc73842) to head (f651ae2).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #230      +/-   ##
==========================================
- Coverage   96.13%   94.94%   -1.20%
==========================================
  Files          74       15      -59
  Lines        3911     1759    -2152
==========================================
- Hits         3760     1670    -2090
+ Misses        151       89      -62

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


Qbit/Deluge category api methods

Adds GetCategory and SetCategory API methods for Qbit from https://github.com/golift/qbit/pull/19
Adds GetLabels and SetLabel API methods for Deluge from https://github.com/golift/deluge/pull/28
These are the first api methods for non-starr/plex.
Splits the integrations.go file into 1 file per downloader.
Lays groundwork to add more API methods to other downloaders.
Partially completes #571.
Fixes a bug that causes a deadlock when restarting a file watcher. Deadlock noticed at reload/shutdown.

We no longer have need to interface with download clients.


execute_value_order returns {'code': 'InternalError'}

Hi, can i have more information about this problem? It seems that you forgot to pass some mandatory value in the request. I need to see your code to spot the error.

My code is the same as your example code but using 'TSLA'. Apologies, I should have said this.
value_buy_order = trading212.execute_value_order(
	ValueOrder('TSLA', value=200))

I have just tried using 'TSLA_US_EQ' instead and that seems to work.


feat(schema) do not run custom_entity_check if fields are invalid

This is inspired by #3846.
For the generic checkers we had so far, running them on invalid fields and
reporting everything at once was okay, and avoided the "get one error, fix
thing, get another error" experience. But for a custom checker, it's safer to
only run it on valid fields (especially thinking of making things less
error-prone for third-party plugin authors).
The commit is lengthy because the errors table is now passed along
and is used to check whether there are recorded errors by the time
entity checkers run; a side effect of this is that the code is now
simpler, and produces fewer intermediate tables.

Is there a way that a custom validator could specify run_with_invalid_fields itself?

@james-callahan not at this point, I didn't want to expose this unless it becomes actually needed, to avoid feature bloat/documentation overhead


axInput: link.post is not always available

In the control AxInput in line 610 (input.js) the link.post is in some cases undefined.

Closing invalid: Cannot reproduce. This seems to have been a setup problem.
@jonaswjs feel free to reproduce if the problem should occur again


adding a comment field to the session field

done

@awhoa Could you please reference your commit ?

ac4cd80262a44440f6f1e504f85ef9e29f35087b

ac4cd80262a44440f6f1e504f85ef9e29f35087b


Passable leaves bug

In server-config of dynamictrees there are "isLeavesPassable" function, which allows entities to go through them. This works fine, however, function "vanillaLeavesCollision" (no matter if true or false) doesn't work (you fall through like it was just airblock). It should slow down the entity and reduce fall damage. Good example how it can work and maybe sound is mod "passable fooliage": https://www.curseforge.com/minecraft/mc-mods/passable-foliage

Added in in 1.3.6


Static analyzer findings (NPEs, resource leaks)

Static code analyzer tool found some possible issues:
NPE:

RecordReaderImplementation:131
GlobeNode:61,100,139

Resource leak:

ByteBasedBitPackingGenerator:68
IntBasedBitPackingGenerator:59
VersionGenerator:53

Don't catch throwable:

DumpCommand:334
Registry:42,57
PrettyPrintWriter:82,91

Reporter: Gabor Szadovszky / @gszadovszky
Assignee: Gabor Szadovszky / @gszadovszky
PRs and other links:

GitHub Pull Request #399

Note: This issue was originally created as PARQUET-825. Please see the migration documentation for further details.

Julien Le Dem / @julienledem:
Issue resolved by pull request 399
https://github.com/apache/parquet-mr/pull/399


refactor(renovate): Upgrade MSW + Cypress + Vitest

MSW upgraded to v2 & intercepts refactored
Cypress upograded to v13

The changes look good to me. Are the build & e2e tests run as part of the CICD process on github? Or would it be safer to check locally? And if we're choosing to run locally (which I'm happy to try), is there a backend I could point the frontend to so I don't need to run it locally (given that I haven't set it up)?

Yes they are all running on the CI pipeline, see the .github/ actions on the top repo.
Re: backend, actually that's a good point: Cypress needs the frontend running to work (just run dev) but the backend is not needed since I'm intercepting all the requests (most of them at least). So even if you cannot run the frontend, you should be able to rn the test.
MSW used to be set up for running the frontend when there was no API available. I need to try it again; with all the mocks, you could have a decent-enough environment locally.


[AVM Module Issue]: many variable blocks are missing heredoc descriptions

Check for previous/existing GitHub issues

[x] I have checked for previous/existing GitHub issues

Issue Type?
Bug
(Optional) Module Version
0.1.0
(Optional) Correlation Id
No response
Description
descriptions should use the heredoc format and include per parameter guidance, ref spec:
https://azure.github.io/Azure-Verified-Modules/specs/terraform/#id-tfnfr1---category-documentation---descriptions

i've got these descriptions in another project so I'll raise a PR to remediate.

@kewalaka Thanks, I appreciate your suggestion and updating the code; I will create a separate branch for testing before merging it into the PR.


DataSet.rename(): pick up Dims. mappers / rename_from_mapper()

jamesrkg has added DataSet.rename_from_mapper(), DataSet.dimensionize() and DataSet.undimensionize() (#707).
These should be unified with the rename() method.

This is not longer relevant.


Drop copied utils in favor of python-ecdsa

[to discuss] Use https://cryptography.io/ instead of python-ecdsa:

https://cryptography.io/en/latest/hazmat/primitives/asymmetric/ec/
https://cryptography.io/en/latest/hazmat/primitives/asymmetric/serialization/

ACK, let's go with cryptography.


Kubernetes 1.1.8 cluster setup with Flannel 0.5.5: cannot ping pod-ips from different nodes

We currently have setup Kubernetes 1.1.8 cluster with two VMs, using Flannel 0.5.5 with vxlan backend:
vm-1 (public-ip: <IP_ADDRESS>):  master + worker-node
vm-1 (public-ip: <IP_ADDRESS>): worker-node
The VMs have ubuntu trusty installed.
uname -a
Linux ngsn02 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
We followed this Kubernetes ubuntu setup guide:
http://kubernetes.io/docs/getting-started-guides/ubuntu/
The Flannel config at the etcd is:
etcdctl get /coreos.com/network/config
{"Network":"<IP_ADDRESS>/16", "SubnetLen": 24, "Backend": {"Type": "vxlan", "VNI": 1}}
etcdctl ls /coreos.com/network/subnets
/coreos.com/network/subnets/<IP_ADDRESS>-24
/coreos.com/network/subnets/<IP_ADDRESS>-24
etcdctl get /coreos.com/network/subnets/<IP_ADDRESS>-24
{"PublicIP":"<IP_ADDRESS>","BackendType":"vxlan","BackendData":{"VtepMAC":"de:71:6e:55:36:75"}}
etcdctl get /coreos.com/network/subnets/<IP_ADDRESS>-24
{"PublicIP":"<IP_ADDRESS>","BackendType":"vxlan","BackendData":{"VtepMAC":"06:c8:be:55:f2:e6"}}
From master node vm-1:
ip route
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/25 dev eth0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/16 dev flannel.1  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev docker0  proto kernel  scope link  src <IP_ADDRESS>
From node vm-2:
~# ip route
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/25 dev eth0  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/16 dev flannel.1  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev docker0  proto kernel  scope link  src <IP_ADDRESS>
After the setup, we deployed two pods:
The pod-ip at node vm-1:  <IP_ADDRESS>:80
The pod-ip at node vm-2:  <IP_ADDRESS>:80
The problem is that we cannot ping the pod-id from the different node, while can ping the pod-id from the same node.
vm-1~# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms
By reviewing the flannel.log, we found the "L3 miss" and "AddL3 succeeded" logs, but not any "L2 miss" and "AddL2" logs.
flannel.log from vm-1:
I0331 09:56:02.102326 01852 main.go:275] Installing signal handlers
I0331 09:56:02.106208 01852 main.go:188] Using <IP_ADDRESS> as external interface
I0331 09:56:02.106289 01852 main.go:189] Using <IP_ADDRESS> as external endpoint
E0331 09:56:02.278504 01852 network.go:53] Failed to retrieve network config: 100: Key not found (/coreos.com) [1]
E0331 09:56:03.279482 01852 network.go:53] Failed to retrieve network config: 100: Key not found (/coreos.com) [10]
E0331 09:56:04.280478 01852 network.go:53] Failed to retrieve network config: 100: Key not found (/coreos.com) [13]
E0331 09:56:05.281463 01852 network.go:53] Failed to retrieve network config: 100: Key not found (/coreos.com) [13]
I0331 09:56:06.633421 01852 etcd.go:204] Picking subnet in range <IP_ADDRESS> ... <IP_ADDRESS>
I0331 09:56:06.634529 01852 etcd.go:84] Subnet lease acquired: <IP_ADDRESS>/24
I0331 09:56:06.637852 01852 ipmasq.go:50] Adding iptables rule: FLANNEL -d <IP_ADDRESS>/16 -j ACCEPT
I0331 09:56:06.644230 01852 ipmasq.go:50] Adding iptables rule: FLANNEL ! -d <IP_ADDRESS>/4 -j MASQUERADE
I0331 09:56:06.650452 01852 ipmasq.go:50] Adding iptables rule: POSTROUTING -s <IP_ADDRESS>/16 -j FLANNEL
I0331 09:56:06.658806 01852 ipmasq.go:50] Adding iptables rule: POSTROUTING ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE
I0331 09:56:06.665567 01852 vxlan.go:153] Watching for L3 misses
I0331 09:56:06.665658 01852 vxlan.go:159] Watching for new subnet leases
I0331 09:56:06.666996 01852 vxlan.go:273] Handling initial subnet events
I0331 09:56:06.667053 01852 device.go:159] calling GetL2List() dev.link.Index: 4
I0331 09:56:28.184209 01852 vxlan.go:232] Subnet added: <IP_ADDRESS>/24
I0331 09:56:28.184401 01852 device.go:164] calling NeighAdd: <IP_ADDRESS>, 06:c8:be:55:f2:e6
I0331 10:04:40.677618 01852 vxlan.go:345] L3 miss: <IP_ADDRESS>
I0331 10:04:40.677708 01852 device.go:187] calling NeighSet: <IP_ADDRESS>, 06:c8:be:55:f2:e6
I0331 10:04:40.677976 01852 vxlan.go:356] AddL3 succeeded
I0331 10:05:00.388439 01852 vxlan.go:340] Ignoring not a miss: 06:c8:be:55:f2:e6, <IP_ADDRESS>
I0331 10:05:08.902727 01852 vxlan.go:345] L3 miss: <IP_ADDRESS>
I0331 10:05:08.902816 01852 device.go:187] calling NeighSet: <IP_ADDRESS>, 06:c8:be:55:f2:e6
I0331 10:05:08.903024 01852 vxlan.go:356] AddL3 succeeded
I0331 10:05:28.612475 01852 vxlan.go:340] Ignoring not a miss: 06:c8:be:55:f2:e6, <IP_ADDRESS>
I0331 10:08:07.298189 01852 vxlan.go:345] L3 miss: <IP_ADDRESS>
I0331 10:08:07.298292 01852 device.go:187] calling NeighSet: <IP_ADDRESS>, 06:c8:be:55:f2:e6
I0331 10:08:07.298666 01852 vxlan.go:356] AddL3 succeeded
I0331 10:08:29.924520 01852 vxlan.go:340] Ignoring not a miss: 06:c8:be:55:f2:e6, <IP_ADDRESS>
.............
Also some more info from node vm-1 (node vm-2 info is similar):
ip -d link show flannel.1
4: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/ether de:71:6e:55:36:75 brd ff:ff:ff:ff:ff:ff promiscuity 0
vxlan id 1 local <IP_ADDRESS> dev eth0 port 32768 61000 nolearning ageing 300
arp -n
Address                  HWtype  HWaddress           Flags Mask            Iface
<IP_ADDRESS>             ether   3c:8a:b0:8a:a3:31   C                     eth0
<IP_ADDRESS>                ether   02:42:14:01:24:02   C                     docker0
<IP_ADDRESS>                         (incomplete)                              flannel.1
<IP_ADDRESS>             ether   00:50:56:a9:58:7a   C                     eth0
bridge fdb show dev flannel.1
06:c8:be:55:f2:e6 dst <IP_ADDRESS> self permanent
bridge fdb show dev docker0
02:42:cf:32:13:6f vlan 0 permanent
bridge fdb show dev eth0
01:00:5e:00:00:01 self permanent
33:33:00:00:00:01 self permanent
33:33:ff:a9:11:21 self permanent
ifconfig
docker0   Link encap:Ethernet  HWaddr 02:42:cf:32:13:6f
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::42:cfff:fe32:136f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
RX packets:80 errors:0 dropped:0 overruns:0 frame:0
TX packets:25 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20968 (20.9 KB)  TX bytes:3043 (3.0 KB)
eth0      Link encap:Ethernet  HWaddr 00:50:56:a9:11:21
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::250:56ff:fea9:1121/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:14131 errors:0 dropped:13 overruns:0 frame:0
TX packets:21040 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1793686 (1.7 MB)  TX bytes:80814089 (80.8 MB)
flannel.1 Link encap:Ethernet  HWaddr de:71:6e:55:36:75
inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
inet6 addr: fe80::dc71:6eff:fe55:3675/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1450  Metric:1
RX packets:26 errors:0 dropped:0 overruns:0 frame:0
TX packets:85 errors:0 dropped:8 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2016 (2.0 KB)  TX bytes:9186 (9.1 KB)
Also we tried to use Flannel backend "udp", and it did not have this above-described issue when using  backend "vxlan". When using backend "udp", the pods from different nodes can ping/communicate with each other. And we noticed in the flannel.log file, both "L3 miss"/"Added L3 succeeded" and "L2 miss"/"Added L2 succeeded" logs.
It is strange that when use Flannel backend "vxlan",  the pods from different nodes cannot ping/communicate with each other. And in the flannel.log file, only "L3 miss"/"Added L3 succeeded" logs are there, without any "L2 miss"/"Added L2 succeeded" logs.
Any insight and help with this issue will be appreciated very much.

Correction:
Our Kubernetes two-nodes-cluster setup is:
vm-1 (public-ip: <IP_ADDRESS>): master + worker-node
vm-2 (public-ip: <IP_ADDRESS>): worker-node

Looking at error in Flannel log:
E0331 09:56:02.278504 01852 network.go:53] Failed to retrieve network config: 100: Key not found (/coreos.com) [1]

I assume, that Flannel has misconfigured in etcd.
Are you sure that proper etcd server is used?
Are you sure that /coreos.com/network is a proper value for Flannel configuration?

No, this is not the root cause. Because we also tried to restart flannel and docker on each node, and then this etcd errror logs were gone. But the reported ping issue persisted (couldn't ping podIPs from different nodes).


Sample code has some uninitialized values causing random D3D failures

Hi! I'm on 38402c9efb67ee5a004d03d3545362b9435d1bae and integrating the DX11 sample code into my application, I noticed that a few data structures are not zero'ed and have uninitialized fields. This leads to some D3D calls randomly failing.
The one I hit last night was with the samplerDesc in the bilinear upscaler:
https://github.com/NVIDIAGameWorks/NVIDIAImageScaling/blob/main/samples/DX11/src/BilinearUpscale.cpp#L105
There is no ZeroMemory() and the MinLOD fields is left uninitialized. Somehow this works OK when I am using a certain device, but with another one, I get this error with the D3D debug layer:
D3D11 ERROR: ID3D11Device::CreateSamplerState: MinLOD be in the range [-INF to +INF].  -1.#QNAN0 specified. [ STATE_CREATION ERROR #228: CREATESAMPLERSTATE_INVALIDMINLOD]

Same remark in the DeviceResources implementation here:
https://github.com/NVIDIAGameWorks/NVIDIAImageScaling/blob/main/samples/DX11/src/DeviceResources.cpp#L127
This goes away by explicitly setting MinLOD to 0.
Thanks!
PS: You have done an amazing job with both the NIS shader and the the sample code! It's been super smooth to integrate into my application. Thank you!

@mbucchia, thanks for reporting the bug and the fix :). We're glad that you found the shaders easy to integrate with your application!

Awesome! I also see you committed a fix for the pixel shift that started in 1.0.1, which I intended to report soon. Looking forward to trying it out!


Plans for NET7 support

Hi @johan-v-r  !
First of all thanks for your lib ;)
As for the .Net 7 support event if it's still in preview, do you plan to migrate yourself ?
Could we create a 'preview' of  LibSassBuilder with NET7 support ?
If you want I can initiate a new PR for this.
Thanks !

Hi @wihary - yes this will be upgraded when .NET 7 is released.
Don't think we really need the preview.. You can use this package in a .NET 7 project - LSB just needs .NET 6 installed on the machine as it executes before your app actually runs.

.NET 7 is out now. Please provide a version i can use for building my projects with CI CD & Docker.  The Containers from Microsont i use for .net core 7 dont provide .net core 6 SDK

.NET 7 supported with v3 👍


Resolve ENS addresses on snapshot

When creating snapshots, we should try to resolve ens names to their true address.
This is the segment of code where we process the addresses: https://github.com/nftlabs/nftlabs-sdk-ts/blob/main/src/core/index.ts#L524
As you can see, the addresses are passed-as is.
The tests we need for this ticket:

[ ] Passing in an ENS address when creating a snapshot results in the resolved address being added to the snapshot
[ ] All addresses passed to the createSnapshot function should be lowercased

We have more enhancements coming to the snapshot module, but lets keep the tickets lean so this one only accomplishes the above two goals.

@atbe @ayshptk  let's punt on this for now. we should leave resolving we need an rpc connection to mainnet and we need to deal with the rpc rate limit.