js without jquery: remove IE support

Related to #23586
Removed IE 10 and 11 support, hacks and polyfills.
Button bsChecked custom attribute is not needed anymore since Edge correctly set checked attribute on input (tested in Edge 17 on Win10)

Ops, missed one reference. Fixed now

What's my manager going to do when they find out Bootstrap 5 doesn't support IE? 🐙

@rbonomo it was a long time ago, we added back IE 11 support for our v5

What's my manager going to do when they find out Bootstrap 5 doesn't support IE?

You can't stop progress...

@myorangeca yeah take the easy way out


Add support for specifying fontweight

Is your feature request related to a problem? Please describe.
I would like to be able to style the charts to fit in more with my project. It´s nice that you have added support for font-family. But i would like to have more customisation. More precisely specifying font-weight.
Describe the solution you'd like
I would like to be able to specify the font-weight of the title.
Describe alternatives you've considered
As far as i can see svg.js support font weight. So it should be similar to implementing the font-family.

I may include it in the future releases.
For now, you can also target elements with CSS
.apexcharts-title-text {
  font-weight: 600
}

All the elements of ApexCharts have specific classes added to them, so you can easily modify design properties with CSS if you don't find an option to specify in JS config. Doing with CSS also helps in applying styles globally unlike specifying each and every option in each chart config.


Add modern Recycle Bin path in Analytic rule malware_in_recyclebin.yaml

Change(s):

Add another path for the recycle bin files to be checked.

Reason for Change(s):

It seems RECYCLER path was for XP and older systems and $RECYCLE.BIN is being used by newer Windows systems.

Version Updated:

Yes

Testing Completed:

Yes

Checked that the validations are passing and have addressed any issues that are present:

Yes

Maybe this rule should not look for the process to be a LOLBAS and the command to have a Recycle Bin path... maybe it should strictly look for a path that contains the recycle bin strings and the lolbas strings, but I prefer not to question that part in this pull request.

Hi @devikamehra, could you please provide your feedback on this. Thanks


feat: make element types more accurate

This widens the usage of HTMLDivElement to HTMLElement throughout.
Also narrows the allowed tag names to actual HTML elements. Closes #251

I don't get it. It looks like you changed formatting only.


Add support for preconfigured MongoDB connections (fixes #327)

Added functionality to insert or update a preconfigured connection.
It checks for the MONGOCLIENT_DEFAULT_CONNECTION_URL env variable on startup and if it is present - parses it as a connection, deletes the old one if present and inserts the new connection in the database.
The preconfigured connection is matched by name Default (preconfigured).
You may want to add additional sanity checks - in case of a malformed connection URL.
Here is the original discussion where it all started.

@artiommft
thank you for PR, I'm going to merge this
note to myself: Gotta check that before 2.0 release, and won't touch environment variable name. (just have a chance to look at code couldn't try myself).
Thanks again :)


Question about running ctest based on the instructions in HACKING.md

The command I ran:
cmake --preset=dev

The error message I was getting:
We added -Wno-error=dev flag and was using vcpkg
The machine is based on Ubuntu.
Preset CMake variables:

  CMAKE_BUILD_TYPE="Release"
  CMAKE_CXX_EXTENSIONS="OFF"
  CMAKE_CXX_FLAGS="-Wall -Wextra -Wpedantic -Wno-error=dev"
  CMAKE_CXX_STANDARD="17"
  CMAKE_CXX_STANDARD_REQUIRED="ON"
  operon_DEVELOPER_MODE="ON"

CMake Error (dev) at build/vcpkg_installed/x64-linux/share/FastFloat/FastFloatConfig.cmake:16 (foreach):
  uninitialized variable 'fast_float_FIND_COMPONENTS'
Call Stack (most recent call first):
  build/vcpkg_installed/x64-linux/share/FastFloat/FastFloatConfig.cmake:28 (check_required_components)
  CMakeLists.txt:82 (find_package)
This error is for project developers. Use -Wno-error=dev to suppress it.

Hi,
Sorry, ctest integration is not complete yet.  If you want to check the available presents, please see cmake --list-presets.
If you do want to run the available unit tests, there are available in a separate project. Just pass -Doperon_DEVELOPER_MODE=ON to cmake and it will get build in build/test/operon-test.

hi @foolnotion, @msnliu is working with me to install and test operon. Thanks for your quick response. Could you recommend a simple starting example we can follow for running the CLI version?

This is mostly from the top of my head as I can't test everything right now, but you have some options:

in a conda environment, run the install script e.g. install.sh from the competition (don't forget to update the revisions to get the latest version of operon). you can remove pyoperon from that script if it's not needed.
using nix, as per BUILDING.md will get you a dev shell where you can configure and build operon.
one can also do to get a built version. a result symlink will then point to its location in the nix store.nix build github:heal-research/operon/cpp20 --no-write-lock-file

same as above but inside docker:docker run -ti --rm docker.nix-community.org/nixpkgs/nix-flakes nix shell github:heal-research/operon/cpp20 --no-write-lock-file

vcpkg - this might not work as I suspect some of the port files might be outdated, but instructions are present in BUILDING.md

Feel free to reopen this and I'll do my best to help.

thanks @foolnotion ! we went the vcpkg route, but will switch to 1 or 2 and see how it goes.

Happy to help! For option 1, the cmake flag -DBUILD_CLI_PROGRAMS=OFF needs to be -DBUILD_CLI_PROGRAMS=ON. eve, vstat, operon revisions need to be the latest ones. You probably also want to pass -DCMAKE_CXX_FLAGS=-march=x86-64-v3 or something similar, in order to get the best performance.


TypeError: null is not an object (evaluating 'RNAudioSession.setActive')

I am getting this error for the line AudioSession.setActive(true), is there any additional setup I need to do besides importing AudioSession? I can't see why this would be causing an error.

Hi @morganruffner, did you run 'pod install'?

Hi there,
I also had the same issue as above when running on the react-native TV fork. Any ideas what might be causing the issue?
I've created an example repo that shows the issue:
https://github.com/pkaneriendeavor/rn-tv-test-app
Any help appreciated!

same issue generated, it works for me after
react-native link react-native-audio-session


filter is executed on route change

Version
2.5.13
Reproduction link
https://jsfiddle.net/50wL7mdz/99316/
Steps to reproduce
alert pop up at start indicates filter being called
on route change alert pop ups again meaning filter executed again
What is expected?
filter should not be called on route change?
What is actually happening?
filter called on route change

is this behaviour normal?

This is expected behavior, router view is a functional component, so it registers the route as a dependency to the component that is using it.


[5.7][CSSimplify] Don't fix invalid r-value use for misplaced &

Cherry-pick of https://github.com/apple/swift/pull/60024

Explanation:

When & is misplaced it creates r-value -> l-value mismatch
in the code which is just a consequence and shouldn't be diagnosed.

Scope: Invalid assignments with incorrectly used & on the right-hand side.

Main Branch PR: https://github.com/apple/swift/pull/60024

Resolves: rdar://96631324

Risk: Very low

Reviewed By: @hborla

Testing:  Added a regression test-case to the suite.

Resolves: rdar://96631324
(cherry picked from commit ff6112024e24dfb8ada85d7b339ef2d9cd0cad04)

@swift-ci please test

@swift-ci please clean test

@swift-ci please nominate

@swift-ci please test macOS platform


Dev to Master - 5.4.0-preview

Coverage increased (+0.3%) to 75.411% when pulling ff3c6a41e32305380e0491e6411616cf33208b09 on yitam:master into 9654020d67aeae672e3d4c71496f6ae8d1f0fe2c on Microsoft:master.

Codecov Report

Merging #853 into master will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #853      +/-   ##
==========================================
+ Coverage   80.06%   80.18%   +0.11%
==========================================
  Files          25       25
  Lines        7325     7419      +94
==========================================
+ Hits         5865     5949      +84
- Misses       1460     1470      +10

Impacted Files
Coverage Δ

...-7.1.20-src/ext/pdo_sqlsrv/shared/core_results.cpp

...phpdev/vc14/x86/php-7.1.20-src/ext/sqlsrv/stmt.cpp

...php-7.1.20-src/ext/pdo_sqlsrv/shared/core_stmt.cpp

...x86/php-7.1.20-src/ext/sqlsrv/shared/core_init.cpp

...phpdev/vc14/x86/php-7.1.20-src/ext/sqlsrv/conn.cpp

...php-7.1.20-src/ext/pdo_sqlsrv/shared/core_conn.cpp

...phpdev/vc14/x86/php-7.1.20-src/ext/sqlsrv/init.cpp

...c14/x86/php-7.1.20-src/ext/pdo_sqlsrv/pdo_util.cpp

...ev/vc14/x86/php-7.1.20-src/ext/sqlsrv/php_sqlsrv.h

.../php-7.1.20-src/ext/sqlsrv/shared/core_results.cpp

... and 40 more

Continue to review full report at Codecov.

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


PR Reviews

https://github.com/zcash/librustzcash/pull/1634#pullrequestreview-2483198781 half way of the first pass of this review

Reviewed new crate PR
https://github.com/zcash/librustzcash/pull/1657

reviewed small PR https://github.com/zcash/zcash-devtool/pull/75

https://github.com/zcash/librustzcash/pull/1634 continued to review this


Unable to run as an npx command

Sandworm version
latest (ran as 'npx' command)
Describe the bug
When running npx @sandworm/audit I receive the following error

Error: Cannot find module<EMAIL_ADDRESS>Require stack:

/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/dependency-path/lib/index.js
/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/<EMAIL_ADDRESS>/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/dependency-path/lib/index.js:7:30)
at Module._compile (node:internal/modules/cjs/loader:1105:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/dependency-path/lib/index.js',
'/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/<EMAIL_ADDRESS>'/my/user/.npm/_npx/51438d1c8ff7d360/node_modules/<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>]
}

To Reproduce
Run npx @sandworm/audit against a local repository
Expected behavior
To receive the expected output
Node (please complete the following information):

Version [e.g. 14.17.3]: 16.16.0
OS: Mac OS Monterey 12.6.3

Browser (please complete the following information):

Device: MacBook Pro
OS: Mac OS Monterey 12.6.3
Browser: Chrome(?)
Version: 110.0.5481.177 (Official Build) (x86_64)

Hey, @cutterbl. Thanks for submitting this, we're aiming to publish a fix ASAP.
In order to help us repro the issue a bit easier, could you share the package.json and package-lock.json files you're using? If this is impossible to share, could we at least get the dependencies and devDependencies objects from your package.json?
Thanks!

I saw this from multiple repositories, some with a private package manager (which I see you don't currently support). I did run it against Big Calendar, receiving the same error. package.json and yarn.lock are in GitHub repo.

Hi, @cutterbl. Thanks for that!
Judging by the contents of the stack trace you might be running a slightly old version of audit (about 1.5 weeks old I believe). I've just tried reproducing this using the latest Audit and it seems to work correctly (worth noting that npx won't download the latest version by default in case one already exists locally).
Attaching a screenshot below of the run for the current master HEAD of Big Calendar. Would you perhaps mind trying with npx @sandworm-audit@latest and seeing if this did the trick?

@andreimarinescu Ah. All npm requests, for me, run through a proxy in our private package manager (Nexus), because of my .npmrc file. I'll clear the cache there and hopefully get the up-to-date version. Sorry for the confusion.


Fail gracefully on IE8

Since the site will no longer support IE8 (or lower), try to fail gracefully. An alert box or something should do.

Best I could do 299e74da5933a13a50094c2fb4bc2befb48ed0b0


"ValueError: Value is too big!" when importing stream in Blender

Expected vs. Actual Behavior
Expected the stream receive to work, but instead it crashes out saying this:
Error: Python: Traceback (most recent call last):
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\bpy_speckle\operators\streams.py", line 273, in execute
    stream_data = operations.receive(commit.referencedObject, transport)
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\api\operations.py", line 70, in receive
    return serializer.read_json(obj_string=obj_string)
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 242, in read_json
    return self.recompose_base(obj=obj)
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 300, in recompose_base
    base.__setattr__(prop, self.handle_value(value))
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 321, in handle_value
    obj_list = [self.handle_value(o) for o in obj]
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 321, in <listcomp>
    obj_list = [self.handle_value(o) for o in obj]
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 335, in handle_value
    return self.recompose_base(obj=obj)
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 260, in recompose_base
    obj = self.get_child(obj=obj)
  File "C:\Users\vince\AppData\Roaming\Blender Foundation\Blender\3.0\scripts\addons\modules\specklepy\serialization\base_object_serializer.py", line 353, in get_child
    return ujson.loads(ref_obj_str)
ValueError: Value is too big!

location: <unknown location>:-1

Number of elements in the stream: 2701
Original source: Revit 2022
Trying to receive stream in Blender 3.0 (MS App Store Version)
Reproduction Steps & System Config (win)
It seems to work fine with other smaller models, so I'm not sure if this because of a specific element type or we are simply hitting a limitation somewhere in the sync process.
May be linked to the maximum size of JSON object because of this line:
return ujson.loads(ref_obj_str)

hi @vinnividivicci,
funnily enough, this has nothing to do with the size of your data. this is due to you having an integer that is too long
https://github.com/ultrajson/ultrajson/issues/49
I'm not sure what this int could be, but it would be helpful if you'd be able to share this stream with me? I've not had this pop up before so I'd be curious to have a look

I sent you a DM through the community.

this has been closed by specklesystems/specklepy#154 and should no longer be an issue! let me know if you are still running into anything similar 😊


Concurrency issue using the trivy binary directly

when setting up docker: false as recommended by  #3 I run into concurrency issues because the binary is installed always on the same path /tmp/bin and the task forces a recursive remove of that path before installation.  Concurrent builds bump into issues because of this.

Logs of the issue:
2022-10-19T12:12:35.0784064Z Run requested using local Trivy binary...
2022-10-19T12:12:35.0786422Z Finding correct Trivy version to install...
2022-10-19T12:12:35.0788644Z Required Trivy version is v0.29.2
2022-10-19T12:12:35.0809149Z Downloading Trivy...
2022-10-19T12:12:35.0920532Z Downloading: https://github.com/aquasecurity/trivy/releases/download/v0.29.2/trivy_0.29.2_Linux-64bit.tar.gz
2022-10-19T12:12:35.8130978Z Extracting Trivy...
2022-10-19T12:12:35.8131596Z Extracting archive
2022-10-19T12:12:35.8147206Z [command]/bin/tar xC /tmp/ -f /tmp/trivy
2022-10-19T12:12:36.8918681Z Setting permissions...
2022-10-19T12:12:36.8930999Z [command]/bin/chmod +x /tmp/trivy
2022-10-19T12:12:36.9057310Z /bin/chmod: cannot access '/tmp/trivy': No such file or directory
2022-10-19T12:12:36.9063806Z ##[error]The process '/bin/chmod' failed with exit code 1
2022-10-19T12:12:36.9139645Z ##[section]Finishing: trivy


Add liblbfgs makeball

This library is a C port of the implementation of Limited-memory Broyden-Fletcher-Goldfarb-Shanno      (L-BFGS) method written by Jorge Nocedal.
http://www.chokkan.org/software/liblbfgs/

@igorbonadio,
Thanks for the pull request. Please make two small changes in your implementation before I merge it: remove the unnecessary redefinition of $(CURL) and put the default definition of LIBTOOLIZE in an else clause of the ifeq. This way all the platform specific data will be inside the same block.

Thanks for the changes!


Replace old Operate process instances route URLs

What should we do?
With the release of Camunda Platform 8 Operate replaced the routes /instances with /processes because now we have the two kinds of instances, processes, and decisions.
The Camunda Modeler should reflect these changes by changing the old routes [1][2]
Operate routes for reference
Why should we do it?
Because the old routes don't exist anymore (but we're redirecting the old routes to the new ones)

@vsgoulart Is this change live already?

@vsgoulart Is this change live already?

Yes, from our side it is. But we're redirecting old /instances routes to /processes

Let us please consider what switching to new URLs means for backwards compatibility with recent (but old) Camunda Cloud / operate versions.
Sticking to old URLs for the moment, for old clusters is a safe choice.

I tested changing this with an outdated cluster, and if we do change to /processes, then it leads nowhere. So should we maybe keep it as is? That is, the old url and re-direct it.

@nikku That's true, but I guess it all depends on how many old clusters we still have.
I'll talk with Felix and ask if he has this data and what is his opinion this.

I tested changing this with an outdated cluster, and if we do change to /processes, then it leads nowhere. So should we consider keeping it as is? That is, the old url and re-direct it.

I'm talking with Felix, I'll post his feedback when he answers me so you can decide

@vsgoulart Do you have any update on this?

Hi @smbea, sorry for the delay.
Felix was on vacation and I forgot to check this topic again so I asked Menski and Aleksander Dytko yesterday.
Their opinion is that it's ok to only have the redirect from Operate's side for now but they're still not sure when we should update the modeler.
I'll setup a reminder for before the next cloud release in 6 months and check if we can update the modeler by then.
I think for now we can close this issue. I'll reopen it when we decide it's a good moment for the update.

Sorry for the unnecessary work from your side :grimacing:


Test modules and examples with Terraform 0.12.x

We haven't yet used Terraform 0.12.x on the repository, and there are likely to be 0.12.x-specific updates we need to review and make. We do not need to maintain compatibility with 0.11.x, we can say version X of the modules supports 0.11.x while the new releases do not.
Requirements

Use the latest stable release of Terraform 0.12.x
This could take for ever if we wanted to review everything, so instead, pick high-traffic examples and modules and go for breadth of review more than completeness.
Running Terraform init/plan should be enough to exercise the details and confirm if there are issues to update, but we may need to do a full apply on the example to do that testing, that's ok.
When we find a particular type issue, review the rest of the repo for that same type of issue and update.

bind-server/

Error: Unsupported block type

  on main.tf line 67, in resource "null_resource" "bind":
  67:   triggers {

Blocks of type "triggers" are not expected here. Did you mean to define
argument "triggers"? If so, use the equals sign to assign it a value.

consul-agent-generic-init/

Error: Unsupported block type

  on main.tf line 47, in resource "template_file" "generic_init":
  47:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

consul-demo-server/

Error: Unsupported block type

  on ../init-snippet-attach-ebs-volume/main.tf line 55, in data "template_file" "init_snippet":
  55:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

consul-leaders-generic-init/

Error: Unsupported block type

  on main.tf line 17, in resource "template_file" "generic_init":
  17:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

cross-account-role/

to confirm

dnsmasq-server/

Error: Unsupported block type

  on main.tf line 45, in resource "null_resource" "dnsmasq":
  45:   triggers {

Blocks of type "triggers" are not expected here. Did you mean to define
argument "triggers"? If so, use the equals sign to assign it a value.

ec2-auto-recover-instances/

Error: Unsupported block type

  on main.tf line 7, in data "template_file" "cnt":
   7:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

ec2-nat-instances/

Error: Unsupported block type

  on ../ec2-auto-recover-instances/main.tf line 7, in data "template_file" "cnt":
   7:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

Error: Unsupported block type

  on ../init-snippet-exec/main.tf line 17, in data "template_file" "init_snippet":
  17:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

Error: Unsupported block type

  on ../init-snippet-hostname-simple/main.tf line 35, in data "template_file" "init_snippet":
  35:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

elasticsearch/

Error: Attribute redefined

  on master-nodes.tf line 43, in resource "aws_launch_configuration" "master-node-lc":
  43:   security_groups      = ["${aws_security_group.transport-sg.id}"]

The argument "security_groups" was already set at master-nodes.tf:42,3-18.
Each argument may be set only once.

elk-stack/

Error: Attribute redefined

  on ../elasticsearch/master-nodes.tf line 43, in resource "aws_launch_configuration" "master-node-lc":
  43:   security_groups      = ["${aws_security_group.transport-sg.id}"]

The argument "security_groups" was already set at
../elasticsearch/master-nodes.tf:42,3-18. Each argument may be set only once.

Error: Missing key/value separator

  on ../logstash/iam.tf line 51, in data "aws_iam_policy_document" "logstash-role":
  47:
  48:
  49:
  51:     principal {

Expected an equals sign ("=") to mark the beginning of the attribute value.

Error: Attribute redefined

  on ../elasticsearch/master-nodes.tf line 43, in resource "aws_launch_configuration" "master-node-lc":
  43:   security_groups      = ["${aws_security_group.transport-sg.id}"]

The argument "security_groups" was already set at
../elasticsearch/master-nodes.tf:42,3-18. Each argument may be set only once.

Error: Missing key/value separator

  on ../logstash/iam.tf line 51, in data "aws_iam_policy_document" "logstash-role":
  47:
  48:
  49:
  51:     principal {

Expected an equals sign ("=") to mark the beginning of the attribute value.

ha-management-cluster/

Error: Unsupported block type

  on ../consul-agent-generic-init/main.tf line 47, in resource "template_file" "generic_init":
  47:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-attach-ebs-volume/

Error: Unsupported block type

  on main.tf line 55, in data "template_file" "init_snippet":
  55:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-config-consul-leader/

Error: Unsupported block type

  on main.tf line 47, in data "template_file" "init_snippet":
  47:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-config-upstart-consul/

Error: Unsupported block type

  on main.tf line 49, in data "template_file" "init_snippet":
  49:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-consul-agent/

Error: Unsupported block type

  on main.tf line 12, in data "template_file" "init_snippet":
  12:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-consul-leader/

Error: Unsupported block type

  on main.tf line 16, in data "template_file" "init_snippet":
  16:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-consul-template/

Error: Unsupported block type

  on main.tf line 47, in data "template_file" "init_snippet":
  47:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-curator/

Error: Unsupported block type

  on main.tf line 20, in data "template_file" "curator-setup":
  20:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-exec/

Error: Unsupported block type

  on main.tf line 17, in data "template_file" "init_snippet":
  17:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-hostname/

Error: Unsupported block type

  on main.tf line 52, in data "template_file" "init_snippet":
  52:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-hostname-simple/

Error: Unsupported block type

  on main.tf line 35, in data "template_file" "init_snippet":
  35:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-install-awscli/

to confirm

init-snippet-install-consul/

Error: Invalid variable name

  on main.tf line 17, in variable "version":
  17: variable "version" {

The variable name "version" is reserved due to its special meaning inside
module blocks.

init-snippet-install-ops/

Error: Invalid variable name

  on main.tf line 9, in variable "version":
   9: variable "version" {

The variable name "version" is reserved due to its special meaning inside
module blocks.

init-snippet-nexus/

Error: Unsupported block type

  on main.tf line 42, in data "template_file" "init_snippet":
  42:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-nomad-agent/

Error: Unsupported block type

  on main.tf line 16, in data "template_file" "init_snippet":
  16:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-prometheus/

Error: Unsupported block type

  on main.tf line 45, in data "template_file" "init_snippet":
  45:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

init-snippet-write-bootstrap-pillar/

Error: Unsupported block type

  on main.tf line 32, in data "template_file" "init_snippet":
  32:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

kibana/

Error: Unsupported block type

  on main.tf line 55, in data "template_file" "kibana-setup":
  55:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

logstash/

Error: Missing key/value separator

  on iam.tf line 51, in data "aws_iam_policy_document" "logstash-role":
  47:
  48:
  49:
  51:     principal {

Expected an equals sign ("=") to mark the beginning of the attribute value.

persistent-ebs-volumes/

Error: Unsupported block type

  on main.tf line 31, in data "template_file" "volume_mount_snippets":
  31:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

prometheus-server/

Error: Unsupported block type

  on ../init-snippet-attach-ebs-volume/main.tf line 55, in data "template_file" "init_snippet":
  55:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

Error: Unsupported block type

  on ../init-snippet-hostname/main.tf line 52, in data "template_file" "init_snippet":
  52:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

Error: Unsupported block type

  on ../init-snippet-prometheus/main.tf line 45, in data "template_file" "init_snippet":
  45:   vars {

Blocks of type "vars" are not expected here. Did you mean to define argument
"vars"? If so, use the equals sign to assign it a value.

single-node-asg/

to confirm

ssh-sg/

to confirm

vpc-legacy/

Error: Unsupported argument

  on main.tf line 37, in module "subnets":
  37:   public_subnet_cidrs  = "${var.public_subnet_cidrs}"

An argument named "public_subnet_cidrs" is not expected here.

Error: Unsupported argument

  on main.tf line 38, in module "subnets":
  38:   private_subnet_cidrs = "${var.private_subnet_cidrs}"

An argument named "private_subnet_cidrs" is not expected here.

terraform 0.11.14 provides 0.12checklist command to verify the configurations. But from my understanding of https://www.terraform.io/upgrade-guides/0-12.html, there are also behavior changes besides syntax changes.
I am working on making modules pass checklist first.

ebs-snapshot-iam/
After analyzing this configuration and working directory, we have identified some necessary steps that we recommend you take before upgrading to Terraform v0.12:

[ ] Terraform couldn't reach the Terraform Registry (at registry.terraform.io) to determine whether current provider plugins are v0.12-compatible.
In general, we recommend upgrading to the latest version of each provider before upgrading to Terraform v0.12.

Taking these steps before upgrading to Terraform v0.12 will simplify the upgrade process by avoiding syntax errors and other compatibility problems.
init-snippet-install-consul/
After analyzing this configuration and working directory, we have identified some necessary steps that we recommend you take before upgrading to Terraform v0.12:

[ ] The variable name "version" is now reserved.
Terraform 0.12 reserves certain variable names that have (or will have in future) a special meaning when used in a "module" block. The name of this variable must be changed before upgrading to v0.12. This will unfortunately be a breaking change for any user of this module, requiring a major release to indicate that.
For more information on the reserved variable names, see the documentation at https://www.terraform.io/docs/configuration/variables.html .

Taking these steps before upgrading to Terraform v0.12 will simplify the upgrade process by avoiding syntax errors and other compatibility problems.
init-snippet-install-ops/
After analyzing this configuration and working directory, we have identified some necessary steps that we recommend you take before upgrading to Terraform v0.12:

[ ] The variable name "version" is now reserved.
Terraform 0.12 reserves certain variable names that have (or will have in future) a special meaning when used in a "module" block. The name of this variable must be changed before upgrading to v0.12. This will unfortunately be a breaking change for any user of this module, requiring a major release to indicate that.
For more information on the reserved variable names, see the documentation at https://www.terraform.io/docs/configuration/variables.html .

Taking these steps before upgrading to Terraform v0.12 will simplify the upgrade process by avoiding syntax errors and other compatibility problems.
vpc-legacy/
Error: module "subnets": "public_subnet_cidrs" is not a valid argument
Error: module "subnets": "private_subnet_cidrs" is not a valid argument
Error: module "subnets": missing required argument "cidr_blocks"
Error: resource 'aws_route_table_association.public-rta' config: "public_ids" is not a valid output for module "subnets"
Error: output 'private_subnet_ids': "private_ids" is not a valid output for module "subnets"
Error: module 'nat-gateways': "public_ids" is not a valid output for module "subnets"
Error: module 'nat-gateways': "private_ids" is not a valid output for module "subnets"
Error: output 'public_subnet_ids': "public_ids" is not a valid output for module "subnets"
vpc-scenario-1/
After analyzing this configuration and working directory, we have identified some necessary steps that we recommend you take before upgrading to Terraform v0.12:

[ ] Provider "aws" may need to be upgraded to a newer version that supports Terraform 0.12. (Request for supported version information failed: Get https://registry.terraform.io/v1/providers/-/aws/versions: net/http: TLS handshake timeout.)

Module "public-gateway"
Module "public-subnets"
Module "vpc"
Taking these steps before upgrading to Terraform v0.12 will simplify the upgrade process by avoiding syntax errors and other compatibility problems.

nexus-asg/
Error: module "snasg": "name" is not a valid argument
Error: module "snasg": "key_file" is not a valid argument
Error: module "snasg": "az" is not a valid argument
Error: module "snasg": missing required argument "name_prefix"

elasticsearch/

Error: Unrecognized block type

  on data-nodes.tf line 278, in data "aws_iam_policy_document" "source_policy":
 278:     principal {

Blocks of type "principal" are not expected in
data.aws_iam_policy_document.source_policy.statement.

Error: Unrecognized attribute name

  on data-nodes.tf line 283, in data "aws_iam_policy_document" "source_policy":
 283:     action = ["sts:AssumeRole"]

No attribute named "action" is expected in
data.aws_iam_policy_document.source_policy.statement.

Error: Unrecognized attribute name

  on data-nodes.tf line 288, in data "aws_iam_policy_document" "master-node-role":
 288:   source_policy_json = "${data.aws_iam_policy_document.source_policy.json}"

No attribute named "source_policy_json" is expected in
data.aws_iam_policy_document.master-node-role.

Error: Unrecognized attribute name

  on data-nodes.tf line 292, in data "aws_iam_policy_document" "data-node-role":
 292:   source_policy_json = "${data.aws_iam_policy_document.source_policy.json}"

No attribute named "source_policy_json" is expected in
data.aws_iam_policy_document.data-node-role.

Error: Unrecognized attribute name

  on data-nodes.tf line 298, in data "aws_iam_policy_document" "ec2-discovery-policy":
 298:     resource = ["*"]

No attribute named "resource" is expected in
data.aws_iam_policy_document.ec2-discovery-policy.statement.

Error: Unrecognized attribute name

  on data-nodes.tf line 299, in data "aws_iam_policy_document" "ec2-discovery-policy":
 299:     action   = ["ec2:DescribeInstances"]

No attribute named "action" is expected in
data.aws_iam_policy_document.ec2-discovery-policy.statement.

elk-stack/ (uses elasticsearch which is broken)

Error: error resolving providers:

- provider.aws: no suitable version installed
  version requirements: "(any version)"
  versions installed: none

logstash/

Error: Unrecognized block type

  on iam.tf line 51, in data "aws_iam_policy_document" "logstash-role":
  51:     principal {

Blocks of type "principal" are not expected in
data.aws_iam_policy_document.logstash-role.statement.

Error: Unrecognized attribute name

  on iam.tf line 56, in data "aws_iam_policy_document" "logstash-role":
  56:     action = ["sts:AssumeRole"]

No attribute named "action" is expected in
data.aws_iam_policy_document.logstash-role.statement.

I'm not sure if you have a WIP local branch for this, but I am using terraform 0.12upgrade in a for loop with terraform init to run thru each module and example and run this upgrade. So far, this has worked well in practice, to get a bunch of the code auto-updated. I'll push a branch with Terraform's changes to the modules and examples, which we can then run more tests on to find the specific problems that remain.

Yes, I have. 0.12upgrade could not solve all the issues. Many manual works have to be done. And I am on it.

Here is the loop I am running:
modules$ for m in `ls` ; do echo updating $m ; cd $m && cp -r ../.terraform ./ && cp ../providers.tf ./ && terraform-0.12.2 init && terraform-0.12.2 0.12upgrade -yes ; cd .. ; done

where .terraform has the plugins after terraform init for a module with aws, template, and local providers (so there is no need to download those), and providers.tf has an entry for the aws provider (to set the region).

 If you could push that branch, it would be helpful, as I could then use it for some of the R&D I'm doing in parallel (I mostly using VPC examples w/ ASG).

Sure. A minute.

Great, that's perfect, thanks!

What would the "count" be here?
modules/vpc-scenario-3/main.tf
98:       "Name" = "${var.name_prefix}-private-vpn-${format("%02d", count.index)}"
The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

vpc-scenario-3/

Error: Reference to "count" in non-counted context

  on main.tf line 98, in resource "aws_route_table" "private-vpn":
  98:       "Name" = "${var.name_prefix}-private-vpn-${format("%02d", count.index)}"

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

setup-meta-infrastructure/

Error: Invalid value for module argument

  on policies.tf line 56, in module "assume-admin-role-policy":
  56:   account_ids = [
  57:     data.aws_caller_identity.current.account_id,
  58:     var.admin_control_account_ids,
  59:   ]

The given value is not suitable for child module variable "account_ids"
defined at ../cross-account-assume-role-policy/main.tf:18,1-23: element 1:
string required.

Error: Invalid value for module argument

  on policies.tf line 145, in module "assume-power-user-role-policy":
 145:   account_ids = [
 146:     data.aws_caller_identity.current.account_id,
 147:     var.power_user_control_account_ids,
 148:   ]

The given value is not suitable for child module variable "account_ids"
defined at ../cross-account-assume-role-policy/main.tf:18,1-23: element 1:
string required.

Error: Invalid value for module argument

  on roles.tf line 9, in module "admin-role":
   9:   trust_account_ids = [
  10:     data.aws_caller_identity.current.account_id,
  11:     var.trust_account_ids,
  12:   ]

The given value is not suitable for child module variable "trust_account_ids"
defined at ../cross-account-role/main.tf:9,1-29: element 1: string required.

Error: Invalid value for module argument

  on roles.tf line 19, in module "power-user-role":
  19:   trust_account_ids = [
  20:     data.aws_caller_identity.current.account_id,
  21:     var.trust_account_ids,
  22:   ]

The given value is not suitable for child module variable "trust_account_ids"
defined at ../cross-account-role/main.tf:9,1-29: element 1: string required.

persistent-ebs-volumes/

Error: Reference to "count" in non-counted context

  on iam.tf line 26, in data "aws_iam_policy_document" "ebs-volume-policy":
  26:       "arn:${data.aws_partition.current.partition}:ec2:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:volume/${element(aws_ebs_volume.volumes.*.id, count.index)}",

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

elasticsearch/

Error: Reference to undeclared resource

  on data-nodes.tf line 348, in data "aws_iam_policy_document" "master-node-role":
 348: source_json = data.aws_iam_policy_document.source.json

A data resource "aws_iam_policy_document" "source" has not been declared in
the root module.

Error: Reference to undeclared resource

  on data-nodes.tf line 352, in data "aws_iam_policy_document" "data-node-role":
 352: source_json = data.aws_iam_policy_document.source.json

A data resource "aws_iam_policy_document" "source" has not been declared in
the root module.

Error: Reference to "count" in non-counted context

  on ../persistent-ebs-volumes/iam.tf line 26, in data "aws_iam_policy_document" "ebs-volume-policy":
  26:       "arn:${data.aws_partition.current.partition}:ec2:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:volume/${element(aws_ebs_volume.volumes.*.id, count.index)}",

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

Error: Reference to "count" in non-counted context

  on ../persistent-ebs-volumes/iam.tf line 26, in data "aws_iam_policy_document" "ebs-volume-policy":
  26:       "arn:${data.aws_partition.current.partition}:ec2:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:volume/${element(aws_ebs_volume.volumes.*.id, count.index)}",

The "count" object can be used only in "resource" and "data" blocks, and only
when the "count" argument is set.

cross-account-assume-role-policy/

Error: Incorrect attribute value type

  on main.tf line 54, in data "aws_iam_policy_document" "assume-role":
  54:     resources = [

Inappropriate value for attribute "resources": element 0: string required.

bind-server/

Error: Incorrect attribute value type

  on main.tf line 112, in resource "null_resource" "bind":
 112:     inline = [

Inappropriate value for attribute "inline": element 8: string required.

Can you refer to the code in the repo by URL? I need to see the larger context.

You mean the error message? No worries. I am just making a log. Fixing on the way.

There was a separate comment I was referring to, sorry, I thought you were asking a question.

I see what you meant. The count usage. Also listed in https://github.com/fpco/terraform-aws-foundation/issues/199#issuecomment-504666750. I look through the code and fixed. But I do need a review on that. I am validating. Later will push the branch.

Pushed changes in modules.

High priority reviews

[ ] vpc-scenario-2
[ ] ami-ubuntu
[ ] security-group-base
[ ] single-port-sg
[ ] open-egress-sg
[ ] asg

Running terraform plan pops more errors for examples/.

Cannot plan vpc-scenario-2.
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

module.ubuntu-xenial-ami.data.aws_partition.current: Refreshing state...
data.aws_availability_zones.available: Refreshing state...
module.ubuntu-xenial-ami.data.aws_ami.ubuntu: Refreshing state...

Error: Error fetching Availability Zones: UnauthorizedOperation: You are not authorized to perform this operation.
	status code: 403, request id: dbb219f8-a2d4-4241-87a2-fb7be6ffcdf2

  on main.tf line 51, in data "aws_availability_zones" "available":
  51: data "aws_availability_zones" "available" {

Error: UnauthorizedOperation: You are not authorized to perform this operation.
	status code: 403, request id: 789a4a32-d5b9-4850-8927-f48c5c077951

  on ../../modules/ami-ubuntu/main.tf line 77, in data "aws_ami" "ubuntu":
  77: data "aws_ami" "ubuntu" {

A confusing part of init-snippet-gitlab-docker.
https://github.com/fpco/terraform-aws-foundation
variable "config_elb" { # line 82
  default = true # apparently this var is of type boolean.
}
data "template_file" "omnibus_config_elb" { # line 93
  count = var.config_elb # count expects number.
}
data "template_file" "omnibus_config_eip" { # line 112
 count = 1 - var.config_elb # count expects number.
}

@ketzacoatl Please help review and test the count change. It is a change I am not certian of.
https://github.com/fpco/terraform-aws-foundation/commit/83639dbbd0e950c6b51da5e808874c9dbd8b7ded

On the surface, yea, that looks right.

Since terraform may mistake an unclearified type. I am putting types to all variables. Following are the files I need to work.
./asg-lifecycle/variables.tf
./cluster-network/variables.tf
./consul-agent-generic-init/variables.tf
./consul-agent-sg/main.tf
./consul-cluster/variables.tf
./consul-demo-server/variables.tf
./consul-leader-sg/main.tf
./consul-leader-wan-sg/main.tf
./consul-leaders-generic-init/variables.tf
./consul-leaders/variables.tf
./ha-management-cluster/variables.tf
./init-snippet-attach-ebs-volume/main.tf
./init-snippet-config-consul-leader/main.tf
./init-snippet-config-upstart-consul/main.tf
./init-snippet-consul-agent/variables.tf
./init-snippet-consul-leader/variables.tf
./init-snippet-consul-template/main.tf
./init-snippet-curator/main.tf
./init-snippet-exec/main.tf
./init-snippet-gitlab-docker/main.tf
./init-snippet-hostname-simple/main.tf
./init-snippet-hostname/main.tf
./init-snippet-install-awscli/main.tf
./init-snippet-install-ops/main.tf
./init-snippet-nexus/main.tf
./init-snippet-nomad-agent/variables.tf
./init-snippet-prometheus/main.tf
./init-snippet-write-bootstrap-pillar/main.tf
./kubernetes-vpc/variables.tf
./multi-volumes/main.tf
./nomad-agent-sg/main.tf
./nomad-agent-worker-ports-sg/main.tf
./nomad-server-sg/main.tf
./persistent-ebs-volumes/variables.tf
./prometheus-server/tests/main.tf
./s3-full-access-policy/main.tf
./s3-remote-state/main.tf
./ssh-sg/main.tf

@Magicloud what do you recommend as our next steps? How much validation should we do before merging?

I won't recommending merging soon. But I am OK to let other people know this branch and give it a try.
On the other hand, I suggest to open another project as to add unit test of each module. At least get them pass plan with no human interfere. So we can use CI to verify changes in the future.

vpc-scenario-2 deployed cleanly for me. I will test a few other env out as well.

Assign back to @ketzacoatl to allocate testing resource.

@AronT-TLV please be vocal in here when you choose an example, so other engineers running tests can choose other examples to test and distribute our work. I'll add a list to the description of the PR.

To the ticket description, I've added a checklist with the list of examples, and I've checked off the examples I tested last week.

The branch has been merged and v0.9.0 has been released.


Is there a Maximum or Minimum number of instances setting?

Found the answer myself.
I can throttle the number of instances by limiting the number of IP addressed in the subnet at cluster startup.


create two migration files for plan and agreement tables

@micheal-w-wells I have created these migration files so that you can work on it later.
Here are the links of the trello cards related to this merge.
https://trello.com/c/gs93EYIc/1557-api-save-a-snapshot-of-for-each-approved-plan
https://trello.com/c/EsztuVYM/1559-api-add-a-column-in-the-plan-table-to-save-the-current-approved-plan-id
I will leave this open and let you decide whether you keep it open or close.

addressed by #134


Fixes SAM issue 994

Test file...
SAM_994.zip
Note that changing analysis period resets DataLifetimeMatrix to single value - consistent behavior now.
Also, note that when analysis period changes, the widget resets to single value when reopened and then the variable is updated. So, exporting code and running can be inconsistent when analysis period is changed if the merchant plant values are not rechecked. Finally, the SetAnalysisPeriod and the "analysis_period" property of the DataLifetimeMatrix is no longer used but left in the callbacks to prevent merge conflicts. We can remove and merge in a separate pull request.

Great job finding and fixing the bug!
Would it make sense to add a pop-up when users change the analysis period? I worry that reverting things to single value is not intuitive, and users would benefit from a warning that's what's happening. Am I correct that trimming the values to a shorter analysis period (or adding zeroes) was significantly more difficult?
Also, I'm having some trouble with the Cambium downloads for analysis periods different than 25 years:

Is this related or should it be a separate issue?

Definite separate issue - created https://github.com/NREL/SAM/issues/1042

Would it make sense to add a pop-up when users change the analysis period? I worry that reverting things to single value is not intuitive, and users would benefit from a warning that's what's happening. Am I correct that trimming the values to a shorter analysis period (or adding zeroes) was significantly more difficult?

I agree with Brian's suggestion:

A message box that appears when you change the analysis period with text like "Analysis period change!\nThe merchant plant price data does not match the analysis period. Go to the Revenue page to update the Energy Market or Ancillary Service price data as appropriate.".

Preserve the mode and truncate or extend the pricing table in necessary to match analysis period instead of changing the mode to Single Value.

Remove UI callback code that sets the value of the widget's AnalysisPeriod property now that this is handled in the widget's C++ code.

@sjanzou These latest changes look good. I used a message box for the analysis_period on_change function so the red debt-related UI text warnings still work. The message box gives a strong reminder to check the price data when the user changes the analysis period.

The message works well, but I'm having some issues with multiple changes to the analysis period. Example:

Start a merchant plant case
Shorten the analysis period to 10 years
Energy Market widget has 87600 values as expected
Lengthen the analysis period to 25 years
Restore the analysis period to 25 years
Now there is a 30 minute timestep, with values 87601 - 438000 as zeroes

In the above case, I would expect the widget to maintain hourly values, with zeroes from 87601 - 219000. I was also able to produce the issue by lengthening to 30, then 40 years (that one went to 1 minute timesteps).

The message works well, but I'm having some issues with multiple changes to the analysis period. Example:

Start a merchant plant case
Shorten the analysis period to 10 years
Energy Market widget has 87600 values as expected
Restore the analysis period to 25 years
Now there is a 30 minute timestep, with values 87601 - 438000 as zeroes

In the above case, I would expect the widget to maintain hourly values, with zeroes from 87601 - 219000. I was also able to produce the issue by lengthening to 30, then 40 years (that one went to 1 minute timesteps).

Hmmm... I am unable to duplicate:

PVWatts / MP default 25 years hourly - 219000 rows

Change analysis period to 10 years - stays hourly with 87600 rows

Change analysis period to 25 years - resets to 219000 rows with zeros from 87601 to 219000

How did you produce a 30 minute timestep with 438000 rows?
Same  thing when extending to 30 years and 40 years - expected behavior as outlined in last meeting and this pull request - what am I missing?

However, there is a major bug if the analysis period is changed twice before rechecking the revenue per the message

The number of rows in the DataLifetimeMatrix goes to the last analysis period / number of rows mode... working through that now and will request re-review after fixing.


Log error in sample/GUI !

I ran the sample/GUI/py in spyder3.6. The error show in log !
09/08/2019 02:46:05 PM : ManagedWindow connected to logging (INFO)
09/08/2019 02:46:07 PM : Worker thread started (INFO)
09/08/2019 02:46:07 PM : couldn't connect to ZMQ context (ERROR)
Traceback (most recent call last):
File "D:\Anaconda3\lib\site-packages\pymeasure\experiment\workers.py", line 154, in run
self.publisher.bind('tcp://*:%d' % self.port)
File "zmq/backend/cython/socket.pyx", line 555, in zmq.backend.cython.socket.Socket.bind
File "zmq/backend/cython/checkrc.pxd", line 25, in zmq.backend.cython.checkrc._check_rc
zmq.error.ZMQError: Address in use
09/08/2019 02:46:07 PM : Worker started running an instance of 'TestProcedure' (INFO)
How to reslove the ZMQ.error?

I have modified as Kassikakk commented on 20 Jun in  #168 issue!
This problem had resolved!


BlazeAndroidSyncBuildFlagsProvider should parse fat_apk_cpu flag from build_flags too

Currently, bazel intellij plugin will try to parse fat_apk_cpu flag from sync_flags. If no flag found x86_64 would be added to sync flags.
However, according to doc sync_flags should be used only when absolutely necessary, as it can defeat bazel caching. So normally we will add fat_apk_cpu in build_flags since it will also be added to sync flags.
But now if bazel intellij plugin doesn't find the fat_apk_cpu flag in sync_flags, it will add --fat_apk_cpu=x86_64 which further override the fat_apk_cpu in build_flags. This may cause sync to fail if the project doesn't target x86_64 platform.

Please refer this for workaround

BlazeAndroidSyncBuildFlagsProvider is removed in https://github.com/bazelbuild/intellij/commit/583537c63866eac13169ce128bb53aa0017bc6e0, this commit will be included in 10.01.2023 release, please reopen if this did not resolve the issue.


EOFError when using num_gpus > 2

Yuxin, thank you very much for the awesome blog and code repo! The main-multigpu-sharedmem.py works nicely as expected when using 2 GPUs. However, if I set the num_gpus here to 3, it will crash with the full error stack as follows:
❯ python main-multigpu-sharedmem.py
Serializing 860001 elements to byte tensors and concatenating them all ...
Serialized dataset takes 505.05 MiB
Traceback (most recent call last):
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/multiprocessing/resource_sharer.py", line 147, in _serve
    send, close = self._cache.pop(key)
KeyError: 1
Worker 2 obtains a dataset of length=860001 from its local leader.
  time     PID  rss    pss    uss    shared    shared_file
------  ------  -----  -----  -----  --------  -------------
 77856  616200  1.5G   1.5G   1.4G   105.0M    104.9M
  time     PID  rss     pss     uss     shared    shared_file
------  ------  ------  ------  ------  --------  -------------
 77856  616202  229.4M  150.6M  124.7M  104.7M    104.7M
Traceback (most recent call last):
  File "main-multigpu-sharedmem.py", line 56, in <module>
    launch(main, num_gpus, dist_url="auto")
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/detectron2/engine/launch.py", line 69, in launch
    mp.start_processes(
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
    while not context.join():
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 160, in join
    raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:

-- Process 1 terminated with the following error:
Traceback (most recent call last):
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 69, in _wrap
    fn(i, *args)
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/detectron2/engine/launch.py", line 123, in _distributed_worker
    main_func(*args)
  File "/home/xiaot/Downloads/RAM-multiprocess-dataloader/main-multigpu-sharedmem.py", line 24, in main
    ds = DatasetFromList(TorchShmSerializedList(
  File "/home/xiaot/Downloads/RAM-multiprocess-dataloader/serialize.py", line 73, in __init__
    self._addr, self._lst = mp.reduction.ForkingPickler.loads(serialized)
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/site-packages/torch/multiprocessing/reductions.py", line 305, in rebuild_storage_fd
    fd = df.detach()
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/multiprocessing/resource_sharer.py", line 58, in detach
    return reduction.recv_handle(conn)
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/multiprocessing/reduction.py", line 189, in recv_handle
    return recvfds(s, 1)[0]
  File "/home/xiaot/miniconda3/envs/ram/lib/python3.8/multiprocessing/reduction.py", line 159, in recvfds
    raise EOFError
EOFError

I wonder if this can be reproduced by others and if there are any potential solutions to it? Many thanks.

Thanks! I should use ForkingPickler to serialize the dataset once for every local worker (i.e. twice if num_gpu=3).

Should be fixed now.

Thank you very much for the prompt response! Confirm that the commit 795868a37446d61412b9a58dbb1b7c76e75d39c4 fixed the issue. Many thanks again!


setMockMethodCallHandler is deprecated. Use tester.binding.defaultBinaryMessenger.setMockDecodedMessageHandler instead

In Flutter 2.5, setMockMethodCallHandler was moved into a new file: deprecated.dart. This meant I had to an import, import 'package:flutter_test/src/deprecated.dart'; in 1 test file.  This test file uses it like so:
Platform.methodChannel.setMockMethodCallHandler(handler);

The documentation related to deprecation states:
/// Rather than calling [setMockMessageHandler] on the message channel, use
/// `tester.binding.defaultBinaryMessenger.setMockDecodedMessageHandler`
/// directly. This more accurately represents the actual method invocation.

We should use tester.binding.defaultBinaryMessenger.setMockDecodedMessageHandler instead.

Fixed by https://github.com/ably/ably-flutter/pull/243


💡[FEATURE]: 🌟 Reveal Elements On Scroll 🌟

issue #103
Before Changes:
Before Changes.zip
After Changes:
After Changes.zip
Checklist

[X] I have gone through the [contributing guide](## PR Description

Checklist

[X] I have gone through the contributing guide
[X] I have updated my branch and synced it with project main branch before making this PR
[X] Is this a bug fix/enhancement/documentation changes

Undertaking
I declare that:

The content I am submitting is original and has not been plagiarized.
No portion of the work has been copied from any other source without proper attribution.
The work has been checked for plagiarism, and I assure its authenticity.

[X] I have updated my branch and synced it with project main branch before making this PR
[X] Is this a bug fix/enhancement/documentation changes
[X] Part of GSSOC
[X] Tested for any breaking changes
[X] Other relevant checks completed

I understand that any violation of this undertaking may have legal consequences that I will bear and could result in the withdrawal of any recognition associated with the work.

[X] I Agree

issue #103
Before Changes:
Before Changes.zip
After Changes:
After Changes.zip
Checklist

[X] I have gone through the [contributing guide](## PR Description

Checklist

[X] I have gone through the contributing guide
[X] I have updated my branch and synced it with project main branch before making this PR
[X] Is this a bug fix/enhancement/documentation changes

Undertaking
I declare that:

The content I am submitting is original and has not been plagiarized.
No portion of the work has been copied from any other source without proper attribution.
The work has been checked for plagiarism, and I assure its authenticity.

[X] I have updated my branch and synced it with project main branch before making this PR
[X] Is this a bug fix/enhancement/documentation changes
[X] Part of GSSOC
[X] Tested for any breaking changes
[X] Other relevant checks completed

I understand that any violation of this undertaking may have legal consequences that I will bear and could result in the withdrawal of any recognition associated with the work.

[X] I Agree

Here , before changes zip file is their

Can't download them. Can send screenshot of them? and also resolve the conflicts of index.html

Okay

@varshith257 conflicts are resolved

@Anishkagupta04 will review this PR

@Anishkagupta04 please review the changes

@Anjaliavv51 Can resolve the conflicts. Glas to see you on the GSSOC leaderboard


operator [O] project-quay (3.8.0-rc.6)

Add v3.8.0-rc.6 to community operators

/merge possible

/merge possible


Release/0.4.1

Hey @alexanderdean, 0.4.1 was a release candidate for isolating a problem Josh was having getting factotum to start.
It has two minor fixes in it, one is changing the panic! into a sensible error message if factotum cannot use the log file in .factotum/factotum.log (for invalid perms etc). This is the reason for the RC (confirming that this was the problem).
The second is a minor fix to the behaviour of the --overwrite flag with the dot subcommand. It now will allow you to call --overwrite if the file does not exist (rather than error). I just had a few minutes and the code open to fix this one.
This isn't blocking 0.5.0, but rather these fixes should be cherry-picked into 0.5.0 when ready.

Hmm - given we put out rcs for 0.4.1, shouldn't we formally release the 0.4.1? It feels a bit strange to have rcs for a release we are not putting out...

Sure - we can release an official 0.4.1, I'm working on it now

Thanks @ninjabear - please re-add the relevant tickets to the 0.4.1 milestone, I think it's empty currently...


Question: providing public properties from internal superclass for public subclasses without knip to see it as a problem

Knip version: 1.10.0
I have a internal class that provides few public static properties for public subclasses that also are handled internally like:
/**
* Internal class providing common methods and properties for letters.
* @internal
*/
export abstract class A { // exported into other internal file
   /**
   * Predefined helper object
   *  @public
   */
    static B: A

    function something(): A | null {
        return isSomething() ? (this.constructor as typeof A).B : null
    }
}

/**
* Class for representing a B
* @public
*/
export class B extends A {
    static B: B
}

/**
* Class for representing a C
* @public
*/
export class C extends A {
    static B: C
}

In VSCode documents are inherited from the superclass, so I don't need to document the subclasses. While it works with the public subclasses, knip has a problem with the internal superclass:
Unused exported class members (1)
B                     A                  src/index.ts

Is there a way to bypass this?

Interesting. I think the syntax of function something is incorrect for a class method. But that's not the issue.
When I run knip (from https://github.com/webpro/knip/tree/a15f8c371db49dd0fdd2f730f45559a1c42a4d3d/test/fixtures/issue-59)  I get this:
$ knip
Unused exported class members (1)
something  A  something.ts

That looks correct to me. What do you think might cause this difference?

I think the syntax of function something is incorrect for a class method

Oh, this is unrelated. I just made a mistake while making this example.
In my API its basically this:
export abstract class Uint8Color extends Uint8ClampedArray implements Color {
	/**
	 *	Predefined color black for this color space.
	 *	@public
	 */
	static readonly Black: Uint8Color
	/**
	 *	Predefined color white for this color space.
	 *	@public
	 */
	static readonly White: Uint8Color
        highContrastColor(): Color {
	 	const constructor = this.constructor as typeof Uint8Color
	 	return this.hasBrightContrast() ? constructor.White.copy() : constructor.Black.copy()
	 }

}

I have another class in the format Uint16Array, where I just copied this into that class, but for some reason knip doesn't detect that. I have internally only 2 use cases of this class that only check if the object is an instance of that class. So I really don't know why knip says it's not used.
Or is it because not all my subclasses implement it? Because I am in the process of developing it.

Your first example references A.B by (this.constructor as typeof A).B, I guess that's why Knip didn't argue about it when I tried.
Happy to look into any issues, but I will need a full (but minimal) repro, including file(s) that reference the problematic method. Could be with files in this repo in the test/fixtures directory (like I did), or anywhere else I have access to.

Ok, I needed some time to look into the whole lifecycle of my use case:
index.ts
function main() {
   const hsv = Colors.buildHSV(new RGB([23, 45, 78]))
}
main()

utils/colors.ts
export abstract class Colors {
    static buildHSV(color: any): HSV {
        if (color instanceof Uint8Color || color instanceof Uint16Color) return color.hsv()
        else return HSV.White
    }
}

utils/colorspaces.ts
export abstract class Uint8Color extends Uint8ClampedArray {
	/**
	 *	Predefined color black for this color space.
	 *	@public
	 */
	static readonly Black: Uint8Color
	/**
	 *	Predefined color white for this color space.
	 *	@public
	 */
	static readonly White: Uint8Color
         /**
	 *	Predefined color blue for this color space.
	 *	@public
	 */
	static readonly Blue: Uint8Color

	contrastTo(c: Uint8Color): number {
		return Math.random() * 5 // just for this test
	}

	hasBrightContrast(): boolean {
		const constructor = this.constructor as typeof Uint8Color
		return constructor.White.contrastTo(this) > constructor.Black.contrastTo(this)
	}

	hasDarkContrast(): boolean {
		const constructor = this.constructor as typeof Uint8Color
		return constructor.Black.contrastTo(this) > constructor.White.contrastTo(this)
	}

	highContrastColor(): Uint8Color {
		const constructor = this.constructor as typeof Uint8Color
		return this.hasBrightContrast() ? constructor.White : constructor.Black
	}

        abstract hsv(): HSV
}

export abstract class Uint16Color extends Uint16Array {
	/**
	 *	Predefined color black for this color space.
	 *	@public
	 */
	static readonly Black: Uint16Color
	/**
	 *	Predefined color white for this color space.
	 *	@public
	 */
	static readonly White: Uint16Color
         /**
	 *	Predefined color blue for this color space.
	 *	@public
	 */
	static readonly Blue: Uint16Color

	contrastTo(c: Uint16Color): number {
		return Math.random() * 5 // just for this test
	}

	hasBrightContrast(): boolean {
		const constructor = this.constructor as typeof Uint16Color
		return constructor.White.contrastTo(this) > constructor.Black.contrastTo(this)
	}

	hasDarkContrast(): boolean {
		const constructor = this.constructor as typeof Uint16Color
		return constructor.Black.contrastTo(this) > constructor.White.contrastTo(this)
	}

	highContrastColor(): Uint8Color {
		const constructor = this.constructor as typeof Uint16Color
		return this.hasBrightContrast() ? constructor.White : constructor.Black
	}

       abstract hsv(): HSV
}
/**
*     @public
*/
export class RGB extends Uint8Color {
    static readonly Black = new RGB([0, 0, 0])
    static readonly White = new RGB([255, 255, 255])
    static readonly Blue = new RGB([0, 0, 255])

    hsv(): HSV {
         return new HSV([360, 100, 100])
    }
}
/**
*     @public
*/
export class LAB extends Uint8Color {
    static readonly Black: LAB
    static readonly White: LAB
    static readonly Blue: LAB

    hsv(): HSV {
       throw new Error('Not implemented yet')
    }
}
/**
*     @public
*/
export class HSV extends Uint16Color {
    static readonly Black: HSV = new HSV([0, 0, 0])
    static readonly White: HSV = new HSV([0, 0, 100])
    static readonly Blue: HSV = new HSV([244, 95, 78])

    hsv(): HSV {
       return this
    }
}

In my repo, if I comment out the static members from Uint8Color, knip suddenly detects the static members from Uint16Color.
But, if for some reason, it still doesn't detect it in your reproduction, I just assume knip hates my repo and just hope it fixes itself magically.

Any chance you could try knip v2 and see how things are going?

The situation has improved, but the problem is not completely fixed. While White and Black are now recognized as used export, Blue is still a false positive.
I think it would solve the problem to check if the unused static properties of private classes are used to inherit documentation comments, since VSCode uses the documentation comments of the parent classes for the child classes.

Thanks for getting back to me, @ElPrudi.  Closing this issue though:

Happy to look into any issues, but I will need a full (but minimal) repro, including file(s) that reference the problematic method. Could be with files in this repo in the test/fixtures directory (like I did), or anywhere else I have access to.


CMR: Table too wide when cloning Linodes (status column is expanded, causing overflow)

Description
This fixes the issue of table overflow, the result is that a longer status (such as clone) will become scrunched up, depending on the label. Unless we consider truncation, I can't think of a better way to handle for this 🤷♀ Open to suggestions/feedback!

Type of Change

Non breaking change ('update')

@johnwcallahan I don't believe that is being tracked- I can create a separate task for that.
@DevDW I agree with you, I don't think the temporary scroll is a big deal, especially for tables (which we've determined are sometimes going to scroll based on their contents). This feedback came from stakeholders, but it's worth comparing the 2 options to see which is preferable. I can understand on one hand wanting the linodes table to be as polished as possible, but the scroll is at least consistent elsewhere in the app.

An option is to have a parent and child icon that could be appended to the label and truncate the message to something similar to our other pending actions

An option is to have a parent and child icon that could be appended to the labels of the linodes being cloned and shorten the message to something similar to our other pending actions, ie. "Cloning 42%"

Agree with truncating the label to "Cloning" so it aligns with our other status messaging. The user can click the label to open the drawer and get full details.
Rather than using different icons, we could just use different labels. Use "Cloning" for the parent and "Creating" for the child, or something similar.


Update React based Program Page to latest changes

The program page based on React needs to be updated to reflect the latest CSS and markup found in mangosteen such that it will be ready for release.

Finding some minor issues that will be thrown into unrelated tickets but nothing blocking or stopping the overall functionality and usefulness and intended function of the indicator setup/edit tool modals/page.


Neomake! and Show terminal

sometimes make command asks terminal input (yes/no for example). Is it possible to run neovim terminal during run Neomake and without terminal if passed bang option eg Neomake! as it makes vim-dispatch extension?

This is not currently possible with neovim jobs to the best of my knowledge, which also makes it impossible with neomake.


Add support for dark mode

It would be great to have access to the classes .ns-light and .ns-dark to determine whether the dark mode is enabled or not.

Since version 6.2, NativeScript detects the system appearance of the running mobile operating system and applies a respective CSS class to the application's root view. In particular, if you run the application on iOS 13.0 in Light mode, a .ns-light CSS class will be assign to the root view of your application. In analogy, if you change the system appearance from Light to Dark, the .ns-light class will be replaced with .ns-dark and vice versa.

Ref.: https://docs.nativescript.org/ui/dark-mode
.ns-light Page {
    background-color: lightblue;
}

.ns-dark Page {
    background-color: darkblue;
}

Workaround to detect dark mode on iOS:
import { topmost } from "tns-core-modules/ui/frame";
const isDarkModeEnabled = topmost().viewController.traitCollection.userInterfaceStyle === 2;

Closed. It works using the :global scope like so:
:global(.ns-light) page {
  background-color: yellow;
}


[BEAM-6146] WIP Portable Python Precommit test

Please add a meaningful description for your change here

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
 Wanted to auto-close from the commit message but referenced a wrong, already-closed PR.


Update zio-config, zio-config-typesafe to 3.0.0-RC4

Updates

dev.zio:zio-config
dev.zio:zio-config-typesafe

from 3.0.0-RC3 to 3.0.0-RC4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #753.


feat: randomized namespace

Resolves: #491

Codecov Report

Merging #496 (81240e7) into main (539f460) will decrease coverage by 0.01%.
The diff coverage is 43.75%.

@@            Coverage Diff             @@
##             main     #496      +/-   ##
==========================================
- Coverage   56.09%   56.07%   -0.02%
==========================================
  Files          50       50
  Lines        9279     9289      +10
==========================================
+ Hits         5205     5209       +4
- Misses       3314     3320       +6
  Partials      760      760

Impacted Files
Coverage Δ

config/config.go
72.72% <43.75%> (-14.23%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

#1547

#978

#436

#1315

Closing as stale PR


[AKS] az aks: Add --gpu-instance-profile for Nvidia multi-instan…

…ce gpu
Related command

az aks create --gpu-instance-profile
az aks nodepool add --gpu-instance-profile
Description

Support multi instance gpus for AKS.
Testing Guide

see live test
History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


Spring amqp doesnt support more than 1 server-named/anonymous queues

Back port issue of https://github.com/spring-projects/spring-amqp/issues/2439

Fixed via: https://github.com/spring-projects/spring-amqp/commit/6ed749e4dcdd48b4a5b924df1bc1cc67df26384b


All clips downloaded after a certain point are only 20 bytes in size

Describe the bug
When calling download_videos(), many clips will only be 20 bytes in size after about 10 downloads. I have had to brute force downloading all of my videos by deleting every clip that is 20 bytes and then trying the download again. Eventually all clips are downloaded successfully.
I have set a delay of 5 seconds between download attempts.
I am not familiar with the Blink API spec. Is hash validation available?
To Reproduce
Steps to reproduce the behavior:

Call download_videos() with a since value far enough in the past to ensure dozens of clips will be downloaded
Check download folder after job is complete

Expected behavior
All downloaded clips should be valid MP4 files.
Home Assistant version (if applicable): N/A
blinkpy version (not needed if filling out Home Assistant version):
Name: blinkpy
Version: 0.22.4

Log Output/Additional Information
Logs are normal. Blinkpy does not think anything is wrong.
2024-02-15 08:27:08,272 DEBUG: checking device {'id': 486442, 'created_at': '2023-12-14T01:58:37+00:00', 'updated_at': '2024-02-15T16:21:18+00:00', 'name': 'Outdoor 1', 'serial': 'GNT2CV013294AU0R', 'fw_version': '13.42', 'type': 'sedona', 'enabled': True, 'thumbnail': '/api/v3/media/accounts/257243/networks/322719/sedona/486442/thumbnail/thumbnail.jpg?ts=1702858610&ext=', 'status': 'done', 'battery': 'ok', 'usage_rate': False, 'network_id': 322719, 'issues': [], 'signals': {'lfr': 5, 'wifi': 5, 'temp': 53, 'battery': 3}, 'local_storage_enabled': False, 'local_storage_compatible': True, 'snooze': False, 'snooze_time_remaining': None, 'revision': '01', 'color': 'black'}
2024-02-15 08:27:08,272 DEBUG: checking device {'id': 488723, 'created_at': '2023-12-15T00:54:36+00:00', 'updated_at': '2024-02-15T13:38:57+00:00', 'name': 'Outdoor 2', 'serial': 'GNT2CV013294AU16', 'fw_version': '13.42', 'type': 'sedona', 'enabled': True, 'thumbnail': '/api/v3/media/accounts/257243/networks/322719/sedona/488723/thumbnail/thumbnail.jpg?ts=1702604958&ext=', 'status': 'done', 'battery': 'ok', 'usage_rate': False, 'network_id': 322719, 'issues': [], 'signals': {'lfr': 5, 'wifi': 4, 'temp': 53, 'battery': 3}, 'local_storage_enabled': False, 'local_storage_compatible': True, 'snooze': False, 'snooze_time_remaining': None, 'revision': '01', 'color': 'black'}
2024-02-15 08:27:08,272 DEBUG: Found unique_info {'id': 488723, 'created_at': '2023-12-15T00:54:36+00:00', 'updated_at': '2024-02-15T13:38:57+00:00', 'name': 'Outdoor 2', 'serial': 'GNT2CV013294AU16', 'fw_version': '13.42', 'type': 'sedona', 'enabled': True, 'thumbnail': '/api/v3/media/accounts/257243/networks/322719/sedona/488723/thumbnail/thumbnail.jpg?ts=1702604958&ext=', 'status': 'done', 'battery': 'ok', 'usage_rate': False, 'network_id': 322719, 'issues': [], 'signals': {'lfr': 5, 'wifi': 4, 'temp': 53, 'battery': 3}, 'local_storage_enabled': False, 'local_storage_compatible': True, 'snooze': False, 'snooze_time_remaining': None, 'revision': '01', 'color': 'black'}
2024-02-15 08:27:08,272 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/network/322719/camera/488723/signals
2024-02-15 08:27:08,337 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/488723/thumbnail/thumbnail.jpg?ts=1702604958&ext=
Session started
2024-02-15 08:27:08,650 INFO: Retrieving videos since 2024-02-01T08:00:00+0000
2024-02-15 08:27:08,651 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v1/accounts/257243/media/changed?since=2024-02-01T08:00:00+0000&page=1
2024-02-15 08:27:09,007 DEBUG: Processing page 1
2024-02-15 08:27:09,007 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v1/accounts/257243/media/changed?since=2024-02-01T08:00:00+0000&page=2
2024-02-15 08:27:09,239 DEBUG: Processing page 2
2024-02-15 08:27:09,240 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v1/accounts/257243/media/changed?since=2024-02-01T08:00:00+0000&page=3
2024-02-15 08:27:09,304 DEBUG: Processing page 3
2024-02-15 08:27:09,304 INFO: No videos found on page 3. Exiting.
2024-02-15 08:27:09,305 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/486442/cv_motion/3988760529.mp4
2024-02-15 08:27:09,938 INFO: Downloaded video to ./clips/outdoor-1-2024-02-15t16-21-25-00-00.mp4
2024-02-15 08:27:14,944 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/488723/cv_motion/3988759994.mp4
2024-02-15 08:27:15,440 INFO: Downloaded video to ./clips/outdoor-2-2024-02-15t16-21-21-00-00.mp4
2024-02-15 08:27:20,446 INFO: ./clips/outdoor-1-2024-02-15t15-37-12-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,447 INFO: ./clips/outdoor-1-2024-02-15t15-34-44-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,447 INFO: ./clips/outdoor-1-2024-02-15t13-39-05-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,447 INFO: ./clips/outdoor-2-2024-02-15t13-39-02-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,448 INFO: ./clips/outdoor-1-2024-02-15t08-47-47-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,448 INFO: ./clips/outdoor-1-2024-02-15t08-41-13-00-00.mp4 already exists, skipping...
2024-02-15 08:27:20,448 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/486442/cv_motion/3986754188.mp4
2024-02-15 08:27:21,331 INFO: Downloaded video to ./clips/outdoor-1-2024-02-15t07-33-55-00-00.mp4
2024-02-15 08:27:26,337 INFO: ./clips/outdoor-2-2024-02-15t07-33-53-00-00.mp4 already exists, skipping...
2024-02-15 08:27:26,337 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/488723/cv_motion/3982891616.mp4
2024-02-15 08:27:27,108 INFO: Downloaded video to ./clips/outdoor-2-2024-02-15t00-29-41-00-00.mp4
2024-02-15 08:27:32,114 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/486442/cv_motion/3982892341.mp4
2024-02-15 08:27:32,643 INFO: Downloaded video to ./clips/outdoor-1-2024-02-15t00-29-44-00-00.mp4
2024-02-15 08:27:37,649 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/488723/cv_motion/3982921160.mp4
2024-02-15 08:27:38,382 INFO: Downloaded video to ./clips/outdoor-2-2024-02-15t00-31-57-00-00.mp4
2024-02-15 08:27:43,387 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/486442/cv_motion/3982921245.mp4
2024-02-15 08:27:44,069 INFO: Downloaded video to ./clips/outdoor-1-2024-02-15t00-31-57-00-00.mp4
2024-02-15 08:27:49,075 DEBUG: Making GET request to https://rest-u030.immedia-semi.com/api/v3/media/accounts/257243/networks/322719/sedona/486442/cv_motion/3982993185.mp4
2024-02-15 08:27:49,869 INFO: Downloaded video to ./clips/outdoor-1-2024-02-15t00-37-26-00-00.mp4

However, after the download is complete many files are only 20 bytes in size:
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t02-09-17-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t02-10-06-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t02-13-45-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t02-33-53-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:31 outdoor-2-2024-02-14t02-35-24-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:31 outdoor-2-2024-02-14t03-06-01-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:29 outdoor-2-2024-02-14t19-44-26-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:29 outdoor-2-2024-02-14t22-25-18-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:29 outdoor-2-2024-02-14t22-51-05-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t22-51-36-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:30 outdoor-2-2024-02-14t22-55-01-00-00.mp4
-rw-rw-r-- 1 media-server media-server 1986602 Feb 15 08:27 outdoor-2-2024-02-15t00-29-41-00-00.mp4
-rw-rw-r-- 1 media-server media-server 1974024 Feb 15 08:27 outdoor-2-2024-02-15t00-31-57-00-00.mp4
-rw-rw-r-- 1 media-server media-server 2037158 Feb 15 08:28 outdoor-2-2024-02-15t00-58-56-00-00.mp4
-rw-rw-r-- 1 media-server media-server      20 Feb 15 08:28 outdoor-2-2024-02-15t06-01-55-00-00.mp4
-rw-rw-r-- 1 media-server media-server 1700192 Feb 15 08:07 outdoor-2-2024-02-15t07-33-53-00-00.mp4
-rw-rw-r-- 1 media-server media-server 1828582 Feb 15 08:06 outdoor-2-2024-02-15t13-39-02-00-00.mp4
-rw-rw-r-- 1 media-server media-server 1718476 Feb 15 08:27 outdoor-2-2024-02-15t16-21-21-00-00.mp4

Looks like we handle this here:
https://github.com/fronzbot/blinkpy/blob/0ec0346f776952f7abe5b9feb53200e60e488bf6/blinkpy/blinkpy.py#L421-L423
I suspect the socket is timing out on the download and closing the file "early", but would expect some type of error message from aiohttp or async.
This is working for me 100% - but I have a sync module so it's a bit different.


What does "This method cannot be used by desktop callers." mean in context?

Having followed the guide here https://docs.microsoft.com/en-us/windows/uwp/design/shell/tiles-and-notifications/send-local-toast-desktop to get notifications working, I then worked through to this page and found the note:
Important
This method cannot be used by desktop callers.
Can some elaboration be made on this? For context, I have used the document I linked to above to get notifications working (at least as proof of concept), in a desktop application (classic Win32). Having done so, I modified my code to try out creating a scheduled notification:
		// And create the toast notification
		var toast = new ScheduledToastNotification(doc, DateTimeOffset.Now.AddSeconds(10));

		// And then show it
		DesktopNotificationManagerCompat.CreateToastNotifier().AddToSchedule(toast);

To my surprise, it seems to work without issue, at least in this simple case? Is it an accident? Can it be expected to work in general?

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

ID: dea899e9-6fe7-a482-1d81-372d394599d9
Version Independent ID: 48f7ccfa-84a8-bec4-a718-3a3e1add6281
Content: ToastNotifier.AddToSchedule(ScheduledToastNotification) Method (Windows.UI.Notifications) - Windows UWP applications
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.ui.notifications.toastnotifier.yml&version=GBlive&_a=contents
Product: uwp
Technology: winrt-reference
Git Login: mijacobs
Microsoft Alias: mijacobs

Scheduling notifications no longer seems to work in a regular win32 app. Tested on Windows 11 22H2, 22621.3007.


Update HStoreWhereNode to follow django's WhereNode

The Constraint class has been deprecated since django17 and was removed in django19 (django/django@5008a4) in favour of the Lookup class, which was introduced in django17 (django/django@20bab2).
Consequently django's WhereNode class looks very different now than it used to and HStoreWhereNode needs to be rewritten to follow suit.
Required action:
-Update HStoreWhereNode to behave like WhereNode in django19, ensuring backward compatibility down to django17.
-Drop django16 support.

Closing this as #133 was merged


Adui 6097 multifacet is so pale that it s looking disabled

Proposed Changes
We will let the disabled component as it is, but we made some upgrade on it. We now make a distinction between a multiselect disabled and in readonly. I've added an example to the multiselectexamples file and added UTs for draggable component and selectedoption component
Potential Breaking Changes

Acceptance Criteria

[x] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

Would it be possible to have a demo for the multi-select in read-only mode with no selected value?
Or if would just be an empty box?

Would it be possible to have a demo for the multi-select in read-only mode with no selected value?
Or if would just be an empty box?
Something like this?


Filter expected warnings in the test suite

FWIW one thing I'd be keen for to do generally — though maybe this isn't the place to start it — is handle warnings in the test suite when we add a new warning — i.e. filter them out where we expect them.
In this case, that would be the loading the netCDF files that have duplicate dims.
Otherwise warnings become a huge block of text without much salience. I mostly see the 350 lines of them and think "meh mostly units & cftime", but then something breaks on a new upstream release that was buried in there, or we have a supported code path that is raising warnings internally.
(I'm not sure whether it's possible to generally enforce that — maybe we could raise on any warnings coming from within xarray? Would be a non-trivial project to get us there though...)
Originally posted by @max-sixty in https://github.com/pydata/xarray/issues/8491#issuecomment-1834615826

Closed by #8974


bug: lazy-loaded plugins can't report health

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.11.0-dev-1096+g079e5f4f9b-Homebrew
Operating system/version
MacOS 14.6
Describe the bug
Plugins that are not yet loaded by Lazy can't report health in Nvims :checkhealth
Steps To Reproduce

Create a minimal plugin:

mkdir -p /tmp/lazyplugin/lua/lazyplugin
nvim /tmp/lazyplugin/lua/lazyplugin/health.lua:

local M = {}

M.check = function()
  vim.health.start("lazyplugin health")
  vim.health.info("hi from lazyplugin.health.check()")
end

return M

Load in lazy: return { dir = '/tmp/lazyplugin', lazy = true }
:checkhealth lazyplugin

Expected Behavior
Maybe not expect, but I was hoping their would be a way that nvim can still discover the plugins health file. But if this is not feasible, feel free to close this issue (although maybe that could be mentioned on the developers page of the docs.
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    { dir = '/tmp/lazyplugin', lazy = true },
  },
})

Well yes, since they're not loaded....


[Bug Report] Palworld server exits while container install

Have you read the Important information text above

[X] Yes i did

Current behavior
When I run "docker-compose up", after a while, the container exits and restarts
Desired behavior
the container doesn't exit
Links to screenshots
No screenshot but here are the logs (at least towards the end where everything started going bad):
Update state (0x81) verifying update, progress: 61.15<PHONE_NUMBER> /<PHONE_NUMBER>)
palworld-dedicated-server  |  Update state (0x81) verifying update, progress: 87.57<PHONE_NUMBER> /<PHONE_NUMBER>)
palworld-dedicated-server  | Success! App '2394010' fully installed.
palworld-dedicated-server  | >>> Doing an update and validate of the gameserver files
palworld-dedicated-server  | tid(94) burning pthread_key_t == 0 so we never use it
palworld-dedicated-server  | Redirecting stderr to '/home/steam/Steam/logs/stderr.txt'
palworld-dedicated-server  | Logging directory: '/home/steam/Steam/logs'
palworld-dedicated-server  | [  0%] Checking for available updates...
palworld-dedicated-server  | [----] Verifying installation...
palworld-dedicated-server  | Steam Console Client (c) Valve Corporation - version<PHONE_NUMBER>
palworld-dedicated-server  | -- type 'quit' to exit --
palworld-dedicated-server  | Loading Steam API...OK
palworld-dedicated-server  |
palworld-dedicated-server  | Connecting anonymously to Steam Public...OK
palworld-dedicated-server  | Waiting for client config...OK
palworld-dedicated-server  | Waiting for user info...OK
palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 0.32 (7340032 /<PHONE_NUMBER>)
palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 16.18 (365611604 /<PHONE_NUMBER>)
palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 41.43 (936390301 /<PHONE_NUMBER>)
palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 66.97<PHONE_NUMBER> /<PHONE_NUMBER>)
palworld-dedicated-server  |  Update state (0x5) verifying install, progress: 90.83<PHONE_NUMBER> /<PHONE_NUMBER>)
palworld-dedicated-server  | Success! App '2394010' fully installed.
palworld-dedicated-server  | >>> Starting the gameserver
palworld-dedicated-server  | >>> Setting up Engine.ini ...
palworld-dedicated-server  | > SERVER_SETTINGS_MODE is set to manual, NOT using environment variables to configure the server!
palworld-dedicated-server  | > File /palworld/Pal/Saved/Config/LinuxServer/Engine.ini has to be manually set by user
palworld-dedicated-server  | >>> Finished setting up Engine.ini ...
palworld-dedicated-server  | >>> Setting up PalWorldSettings.ini ...
palworld-dedicated-server  | > Checking if config already exists
palworld-dedicated-server  | > No config found, generating one
palworld-dedicated-server  | mkdir: cannot create directory '/palworld/Pal': Operation not permitted
palworld-dedicated-server  | cp: cannot stat '/palworld/DefaultPalWorldSettings.ini': No such file or directory
palworld-dedicated-server  | > SERVER_SETTINGS_MODE is set to manual, NOT using environment variables to configure the server!
palworld-dedicated-server  | > File /palworld/Pal/Saved/Config/LinuxServer/PalWorldSettings.ini has to be manually set by user
palworld-dedicated-server  | >>> Finished setting up PalWorldSettings.ini ...
palworld-dedicated-server  | > Setting Community-Mode to enabled
palworld-dedicated-server  | > Setting Multi-Core-Enchancements to enabled
palworld-dedicated-server  | /servermanager.sh: line 36: ./PalServer.sh: No such file or directory
palworld-dedicated-server exited with code 0
To Reproduce
nada
Software setup

OS: macOs Monterey

Hardware setup
nada
Additional context
here is my env file:
Change this for logging and backup, see "Environment variables" in the README.md
TZ=Asia/Kolkata
ALWAYS_UPDATE_ON_START=true
MULTITHREAD_ENABLED=true
COMMUNITY_SERVER=true
BACKUP_ENABLED=true
BACKUP_CRON_EXPRESSION=0 * * * *
BACKUP_RETENTION_POLICY=true
BACKUP_RETENTION_AMOUNT_TO_KEEP=30
STEAMCMD_VALIDATE_FILES=true
Change this to manual if you want to edit your configs yourself
SERVER_SETTINGS_MODE=manual
WEBHOOK_ENABLED=false
WEBHOOK_URL="YOUR-URL-IN-HERE"
WEBHOOK_START_TITLE="Server is starting"
WEBHOOK_START_DESCRIPTION="The gameserver is starting"
WEBHOOK_START_COLOR="2328576"
WEBHOOK_STOP_TITLE="Server has been stopped"
WEBHOOK_STOP_DESCRIPTION="The gameserver has been stopped"
WEBHOOK_STOP_COLOR="7413016"
WEBHOOK_INFO_TITLE="Info"
WEBHOOK_INFO_DESCRIPTION="This is an info from the server"
WEBHOOK_INFO_COLOR="2849520"
NETSERVERMAXTICKRATE=120
DIFFICULTY=Normal
DAYTIME_SPEEDRATE=1.000000
NIGHTTIME_SPEEDRATE=1.000000
EXP_RATE=2.000000
PAL_CAPTURE_RATE=1.000000
PAL_SPAWN_NUM_RATE=1.000000
PAL_DAMAGE_RATE_ATTACK=1.000000
PAL_DAMAGE_RATE_DEFENSE=1.000000
PLAYER_DAMAGE_RATE_ATTACK=1.000000
PLAYER_DAMAGE_RATE_DEFENSE=1.000000
PLAYER_STOMACH_DECREASE_RATE=1.000000
PLAYER_STAMINA_DECREACE_RATE=1.000000
PLAYER_AUTO_HP_REGENE_RATE=2.000000
PLAYER_AUTO_HP_REGENE_RATE_IN_SLEEP=4.000000
PAL_STOMACH_DECREACE_RATE=1.000000
PAL_STAMINA_DECREACE_RATE=1.000000
PAL_AUTO_HP_REGENE_RATE=1.000000
PAL_AUTO_HP_REGENE_RATE_IN_SLEEP=1.000000
BUILD_OBJECT_DAMAGE_RATE=1.000000
BUILD_OBJECT_DETERIORATION_DAMAGE_RATE=1.000000
COLLECTION_DROP_RATE=1.000000
COLLECTION_OBJECT_HP_RATE=1.000000
COLLECTION_OBJECT_RESPAWN_SPEED_RATE=1.000000
ENEMY_DROP_ITEM_RATE=4.000000
DEATH_PENALTY=Item
ENABLE_PLAYER_TO_PLAYER_DAMAGE=false
ENABLE_FRIENDLY_FIRE=false
ENABLE_INVADER_ENEMY=true
ACTIVE_UNKO=false
ENABLE_AIM_ASSIST_PAD=true
ENABLE_AIM_ASSIST_KEYBOARD=false
DROP_ITEM_MAX_NUM=3000
DROP_ITEM_MAX_NUM_UNKO=100
BASE_CAMP_MAX_NUM=128
BASE_CAMP_WORKER_MAXNUM=15
DROP_ITEM_ALIVE_MAX_HOURS=1.000000
AUTO_RESET_GUILD_NO_ONLINE_PLAYERS=false
AUTO_RESET_GUILD_TIME_NO_ONLINE_PLAYERS=72.000000
GUILD_PLAYER_MAX_NUM=20
PAL_EGG_DEFAULT_HATCHING_TIME=72.000000
WORK_SPEED_RATE=2.000000
IS_MULTIPLAY=true
IS_PVP=false
CAN_PICKUP_OTHER_GUILD_DEATH_PENALTY_DROP=false
ENABLE_NON_LOGIN_PENALTY=false
ENABLE_FAST_TRAVEL=true
IS_START_LOCATION_SELECT_BY_MAP=true
EXIST_PLAYER_AFTER_LOGOUT=true
ENABLE_DEFENSE_OTHER_GUILD_PLAYER=false
COOP_PLAYER_MAX_NUM=4
MAX_PLAYERS=32
SERVER_NAME=Tequila-Sunsett
SERVER_DESCRIPTION=Palworld-Dedicated-Server running in Docker hosted by Tequila Sunsett
ADMIN_PASSWORD=adminPassword
SERVER_PASSWORD=darthsett
PUBLIC_PORT=8211
PUBLIC_IP=
RCON_ENABLED=true
RCON_PORT=25575
REGION=
USEAUTH=true
BAN_LIST_URL=https://api.palworldgame.com/api/banlist.txt

My bad
I forgot to chmod 777 game
But now my server isn't showing up on community servers list. My logs are giving some   S_API Fails at the end now

@DarthSett No worries. Next time, read the README.md carefully 😊
Also, read the FAQs, has your answer 😉
Close this issue after 😎

@thejcpalma Ok. I get that the errors are safe to ignore. But my server still doesn't show up on the community server list.

I'm also not able to enter the server using direct connect

@thejcpalma Ok. I get that the errors are safe to ignore. But my server still doesn't show up on the community server list.

Server list search is a known bug, use direct connect, and it will show up on recent servers later

I'm also not able to enter the server using direct connect

This is because you're using public IP for connecting (confirmed via discord) and your port forwarding is not done correctly, so you are able to join when in the same network with local IP but using public IP won't work.

Im closing this issue as resolved, feel free to reach out again if you need help.
If you like this project, please consider giving this repo and the docker-hub-repo a Star.