Error wile autodeploy: The process can not access the file because part of the file is locked by another process

I start one instantance and create one db on them
Then i start second instance and db not deployed
2015-03-26 18:26:50:585 INFO  [beta] Saving distributed configuration file for database 'skeddy' to: ..\db2\databases\skeddy\distributed-config.json [OHazelcastPlugin]
2015-03-26 18:26:54:608 WARNING [beta]->[[alpha]] requesting deploy of database 'skeddy' on local server... [OHazelcastPlugin]
2015-03-26 18:26:54:647 INFO  [beta]<-[alpha] received updated status beta.skeddy=SYNCHRONIZING [OHazelcastPlugin]
2015-03-26 18:26:54:662 INFO  [beta]<-[alpha] received updated status alpha.skeddy=SYNCHRONIZING [OHazelcastPlugin]
2015-03-26 18:23:05:006 WARNING [beta]->[[alpha]] deploy returned: {alpha=java.io.IOException: The process can not access the file because part of the file is locked by another process}
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at com.orientechnologies.common.io.OIOUtils.copyStream(OIOUtils.java:156)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:142)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:120)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:120)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.addFolder(OZIPCompressionUtil.java:120)
at com.orientechnologies.orient.core.compression.impl.OZIPCompressionUtil.compressDirectory(OZIPCompressionUtil.java:51)
at com.orientechnologies.orient.core.storage.impl.local.paginated.OLocalPaginatedStorage.backup(OLocalPaginatedStorage.java:152)
at com.orientechnologies.orient.server.distributed.ODistributedStorage.backup(ODistributedStorage.java:1218)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.backup(ODatabaseDocumentTx.java:2495)
at com.orientechnologies.orient.server.distributed.task.ODeployDatabaseTask.execute(ODeployDatabaseTask.java:129)
at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.executeOnLocalNode(OHazelcastPlugin.java:757)
at com.orientechnologies.orient.server.hazelcast.ODistributedWorker.onMessage(ODistributedWorker.java:300)
at com.orientechnologies.orient.server.hazelcast.ODistributedWorker.run(ODistributedWorker.java:121)
Exception in thread "main" com.orientechnologies.orient.server.distributed.ODistributedException: No response received from remote nodes for auto-deploy of database
at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.installDatabase(OHazelcastPlugin.java:968)
at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.installNewDatabases(OHazelcastPlugin.java:1226)
at com.orientechnologies.orient.server.hazelcast.OHazelcastPlugin.startup(OHazelcastPlugin.java:185)
at com.orientechnologies.orient.server.OServer.registerPlugins(OServer.java:871)
at com.orientechnologies.orient.server.OServer.activate(OServer.java:265)
at com.orientechnologies.orient.server.OServerMain.main(OServerMain.java:41)
Version: 2.0.5

I have same problem while deploying database from first node to second node.
After some tests, I found Lucene index (Spatial) is cause of problem. All job is done well when I delete the index from my class of first node.
But, the index have to be in my database, so the problem is still not solved perfectly.
any suggestions or helps?

https://github.com/orientechnologies/orientdb/issues/4012

@maggiolo00 Is this already fixed on last snapshots?

Any news on this?

I'm closing it in the meanwhile, in case please reopen/comment it.


Document links need to be modified

Document links need to be modified into https://allenfang.github.io/react-bootstrap-table/

sorry, where's the link should be change? thanks

here!

Fixed it, thanks :)


Dimension discrepancy for Deepbench

@scott-gray  I noticed that the dimensions (M, N, K) which are called out by Deepbench (https://github.com/baidu-research/DeepBench/blob/master/results/DeepBench_NV_TitanX_Pascal.xlsx) are different from those benchmarked by OpenAI-GEMM. For example what Deepbench calls (M, N, K, Op): 1760, 16, 1760, N, N is 16, 1760, 1760, 1760, N, N for OpenAI-GEMM. Therefore, M and N are flipped for this particular problem. Can you please explain this? As you will attest, the values of M, N and K can vastly affect performance, therefore, understanding this dimension discrepancy is important to get an idea of the performance.

My kernels are row-order, cublas is col-order.  So you need to swap M and N (and their transposes) for equivalence.
(A x B).T = B.T x A.T

Got it, makes sense now. Thanks !


Refactor AIRRt symbolic linkage matching logic

Fixup to enable a case where there are multiple unrolled sub-channels on the shim side, directly accessing buffers in one air.herd.

This PR changes the examples. Is that because they had bugs or is it to workaround bugs in the compiler?

My understanding is that there were bugs in the examples, and a few places where I incorrectly computed a value that just happened to have a correct value. Erwei fixed it so the values are computed correctly. I will review the other examples (the ones that work) to check to see if I'm getting accidental success elsewhere too.
My understanding is that this PR fixes one of the failing examples (multi core dma, associated with this issue: https://github.com/Xilinx/mlir-air/issues/624) but I will need to rewrite the multi core channel example to better fit the channel abstraction/implementation (changes needed described in comments here: https://github.com/Xilinx/mlir-air/issues/625).


Skeletal mesh is not render on latest 6s+ iOS devices

Operating system or device, Godot version, GPU Model and driver (if graphics related):
IPhone 6s, Ipad (2017). Bugsquad edit: master branch.
Issue description:
On IPhone 6s, iPad Pro (1st generation) and i guess all Apple A9 devices skeletal mesh dont draw.
In output log it displays the following error message:
skel_test.iphone[583:171369] GLDDevice failed to build pipeline state: Cannot convert attribute from MTLAttributeFormatUChar4 to a signed integer type

I try to debug and found that it failed on  https://github.com/godotengine/godot/blob/efe9a6ff5a55e1533a223dbaf43e7b7c20810b33/drivers/gles3/rasterizer_scene_gles3.cpp#L1486

CC @BastiaanOlij

I have attached screenshot of GPU trace on step that draw a skeletal mesh:

Additional details, this errors produced by line https://github.com/godotengine/godot/blob/efe9a6ff5a55e1533a223dbaf43e7b7c20810b33/drivers/gles3/shaders/scene.glsl#L45 , when I changed attribute type to:
layout(location=6) in ivec4 bone_indices; // attrib:6

cast errors was eliminated

I have added workaround PR that solve the issue.

There has to be a better way to fix it, changing to vec4 and casting everywhere these are used is a hack. I don't see mentions about iOS not support ivec4, so there should be a way to use it as it should be.


[semver:minor] feat: add squash param to dependabot-automerge

Adds squash parameter to the dependabot-automerge job so that PRs can be merged in repos with merge commit option disabled.
Depends on: https://github.com/salesforcecli/plugin-release-management/pull/404
@W-0@

@mohanraj-r after this is merged your circle config file should look like this:
jobs:
      - release-management/dependabot-automerge:
          squash: true


Add keyboard navigation

Fixes #39 by adding the following keyboard controls:

While in the tasks list, up/down arrows highlight tasks. Hitting space while a task is highlighted will toggle its selection. Hitting escape will clear the highlight. Hitting enter while a task is highlighted will open it in the browser.
While in the filters list, up/down arrows highlight filters. Hitting enter while a filter is highlighted will take you to the edit view. Hitting backspace while a filter is highlighted will delete the filter. Hitting escape will clear the highlight.

Other changes:

The filter name field is now autofocused on both the Edit Filter and New Filter views.
This adds a new View menu with shortcuts to switch between Tasks, Filters, and the authentication view. In macOS, Cmd-1 takes you to Tasks, Cmd-2 to Filters, and Cmd-3 to authentication. Tasks and Filters options are disabled when the user has not provided an access token.

This is just a first step for keyboard navigation. #50 can build upon this by adding key combinations to archive/snooze/ignore selected tasks.
/cc @probablycorey @summasmiff

Yesss!


[project-monitoring] Summary dashboard has no metrics for Disk I/O

Describe the bug
On all Project Monitoring installations the graph for Disk I/O are empty. The underlying dashboard Rancher/Pod has also no metrics. Prometheus has some metrics for container_fs_writes_bytes_total and container_fs_read_bytes_totak, but it seems there are some changes , linked with this pr, also mentioned in this OpenShift Issue
To Reproduce
I couldn't full reproduce the issue and what caused the empty metrics exactly. Maybe it needs a device-selector, optional a newer version from upstream (prometheus-federator 0.2.1)
Result
empty metrics
Expected Result
metrics for disc io on all Kubernetes and Rancher dashboard
SURE-6055

We can check to see if there is an upstream issue and link it, but beyond that it is out of our control.

I think this may be fixed with rancher-monitoring 102.0.0+up40.1.2. I tested it with RKE1 v1.24.10.
@eumel8 Can you check if this is fixed with new monitoring/prometheus-federator version for you as well?

Probably a dup of https://github.com/rancher/rancher/issues/38934, which was ported into the latest rancher-monitorng chart (which was brought into prometheus-federator as well).
@eumel8 feel free to open up a new issue if you are still seeing this, closing this out since it is probably fixed

seems fixed on the updated 102.0.0+up40.1.2 as of today on our clusters. thx, @aiyengar2


feature request: allow non mail links for mail contact field

See gonum/website#11.
We are using the academic theme for the https://gonum.org/ website and have a mail contact pointer to the google-groups page we use for development and user discussion. For practical reasons (avoiding spam) we ask people people (at least at first) to sign up with google groups/use the web client. This means that a mailto: scheme is incorrect for the URI we provide, but academic prefixes the URI with this scheme, giving us a link "mailto:https://groups.google.com/forum/#!forum/gonum-dev".
It could be said that we are holding it wrong, but a mailing list does seem appropriately signified with an envelope, and this is the only was that seems possible to achieve this. Are we missing an alternative, or if not, would a fix be considered? Two approaches are mentioned in the issue above, to allow configuration of the mail contact to not add a scheme, or add code to detect a scheme and not add one if it is present.

Since it's not actually a valid email address, it might be best we consider creating another parameter such as Forum or Mailing List for it rather than storing in the Email parameter...

This would be also useful in conjunction with the MailHide reCAPTCHA....

For the time being, a solution to this can be hacked together in three easy steps. First, in config.toml, where you would normally enter the contact email address, put a Markdown link to your Google group. It would look something like the following:
email = "[https://www.google.com/](https://www.google.com/)"
Next, in content/home/contact.md, disable the automatic mailto link:
autolink = false
Finally, in themes/academic/layouts/partials/widgets/contact.html, find the following line:
{{- if $autolink }}{{ . }}{{ else }}{{ . }}{{ end -}}
And replace it with this:
{{- if $autolink }}{{ . }}{{ else }}{{ . | markdownify }}{{ end -}}

How about this?

icon: http://fortawesome.github.io/Font-Awesome/icon/comments-o/
new variable name in config.toml: discuss, forum, or mailing_list

I'll look into implementing reCAPTCHA for hiding email address.

discussion = { name = "Discuss", url = "https://discourse.gohugo.io" } can now be added to [params] section of config.toml to add a link to forums/chat/mailing-list.

I have just tried that and I get a problem with a len on an untyped nil:
ERROR 2017/10/30 09:33:48 Error while rendering "home": template: theme/index.html:1:3: executing "theme/index.html" at <partial "widget_page...>: error calling partial: template: theme/partials/widget_page.html:23:9: executing "theme/partials/widget_page.html" at <partial $widget $par...>: error calling partial: template: theme/partials/widgets/posts.html:61:51: executing "theme/partials/widgets/posts.html" at <len .Params.tags>: error calling len: len of untyped nil

This uses hugo v0.30.2, and academic theme at ec4fe2eb299aa37cb6ed2d2f37554101528cc48d. I've gone through the breaking changes at https://sourcethemes.com/academic/post/v2.0.0/
diff --git a/config.toml b/config.toml
index 268fe76..468591f 100644
--- a/config.toml
+++ b/config.toml
@@ -25,7 +25,7 @@ defaultContentLanguageInSubdir = false
   organization_url = ""
   gravatar = false  # Get your avatar from Gravatar.com? (true/false)
   avatar = "gophernumerical.png"  # Specify an avatar image (in `static/img/` folder) or delete value to disable avatar.
-  email = "https://groups.google.com/forum/#!forum/gonum-dev"
+  discussion = { name = "Discuss", url = "https://groups.google.com/forum/#!forum/gonum-dev" }
   address = ""
   office_hours = ""
   phone = ""
diff --git a/content/home/posts.md b/content/home/posts.md
index 27195c7..08c66bd 100644
--- a/content/home/posts.md
+++ b/content/home/posts.md
@@ -12,8 +12,11 @@ widget = "posts"
 # Order that this section will appear in.
 weight = 2

-# Show posts that contain the following tags. Default to any tags.
-tags = []
+# Filter posts by tag.
+#  By default, show all recent posts.
+#  Filtering example: `tags_include = ["hugo", "academic"]`
+tags_include = []
+tags_exclude = []

 # Number of posts to list.
 count = 5
diff --git a/content/home/publications.md b/content/home/publications.md
index a17001e..0f489b0 100644
--- a/content/home/publications.md
+++ b/content/home/publications.md
@@ -15,8 +15,22 @@ weight = 3
 # Number of publications to list.
 count = 10

-# Show publication details (such as abstract)? (true/false)
-detailed_list = false
+# List format.
+#   0 = Simple
+#   1 = Detailed
+#   2 = APA
+#   3 = MLA
+list_format = 0

+# Filter by publication type.
+# -1: Any
+#  0: Uncategorized
+#  1: Conference proceedings
+#  2: Journal
+#  3: Work in progress
+#  4: Technical report
+#  5: Book
+#  6: Book chapter
+publication_type = "-1"
 +++

diff --git a/netlify.toml b/netlify.toml
index 2fb2c7a..01d1b02 100644
--- a/netlify.toml
+++ b/netlify.toml
@@ -1,4 +1,4 @@
 [context.deploy-preview.environment]
-  HUGO_VERSION = "0.27"
+  HUGO_VERSION = "0.30.2"
 [context.production.environment]
-  HUGO_VERSION = "0.27"
\ No newline at end of file
+  HUGO_VERSION = "0.30.2"
diff --git a/themes/academic b/themes/academic
index ab24e56..ec4fe2e 160000
--- a/themes/academic
+++ b/themes/academic
@@ -1 +1 @@
-Subproject commit ab24e5646cad8d4e7b6a31ca09f6f614f13dc8c4
+Subproject commit ec4fe2eb299aa37cb6ed2d2f37554101528cc48d

The error occurs here. I don't see anywhere not where Params.tags gets set.

You will get this error if one of your files in post/ folder is missing tags = [] in its frontmatter. Hope that helps.

Lovely. Thank you.

A follow up is how to set a discussion icon for social rather than an envelope?

@kortschak you appear to be using the old header and CSS style sheet. Your CSS is not up-to-date (not from Academic v2). Perhaps you are overriding the header and/or CSS with customizations that are based on the old theme?

It's unclear to me how to fix this. We are not over-riding anything, though do we have the hugo-academic.css in static/css/, (which does not exist in the repo here anymore) so this is probably the cause. I have tried replacing static/css and adding static/js/ (which was not present) and all the styling is broken. Can you point to documentation that explains how to make the changes (we were previously using academic at ab24e5646cad8d4e7b6a31ca09f6f614f13dc8c4).

There is a lot of colour an movement for that upgrade. The problem for us is that we use the meta tags for go get, so it means we need to override layouts/partials/header.html. Can you point to an easier way to do that?
All up though I'm satisfied that this issue is fixed. I'll raise others to cover the things I've run into in the upgrade.

@gcushen as netlify and formspree - two form providers included in the theme supports both honeypot (the hidden field that is not supposed to be filled) and reCaptcha (netlify on demand, formspree by default on and controlled from settings), could this setup be added into academic ? Something like https://github.com/alkuzad/hugo-academic/tree/secure_contact

@gcushen as netlify and formspree - two form providers included in the theme supports both honeypot (the hidden field that is not supposed to be filled) and reCaptcha (netlify on demand, formspree by default on and controlled from settings), could this setup be added into academic ? Something like https://github.com/alkuzad/hugo-academic/tree/secure_contact

I have tried to address this comment in my pull request.


Futures test data

Coverage increased (+0.4%) to 87.718% when pulling d0aaaaeca8c2f25ca0b962e975c30477f2a42cb8 on futures-test-data into cf7f05b403486c99905728c4f233025ca160d9a4 on master.


Continuous integration testing on linux and windows

:white_check_mark: Build SMT 0.1.3 completed (commit https://github.com/SMTorganization/SMT/commit/ed9db3fade by @)

:white_check_mark: Build SMT 0.1.4 completed (commit https://github.com/SMTorganization/SMT/commit/8efea36a9e by @)

:white_check_mark: Build SMT 0.1.5 completed (commit https://github.com/SMTorganization/SMT/commit/0608929c04 by @)

:white_check_mark: Build SMT 0.1.7 completed (commit https://github.com/SMTorganization/SMT/commit/84663fcfa8 by @hwangjt)

:white_check_mark: Build SMT 0.1.8 completed (commit https://github.com/SMTorganization/SMT/commit/8d3281d9f2 by @hwangjt)


[CT-3239] [Feature] Add a full_refresh option to on_schema_change

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
Add a full_refresh option to on_schema_change .
During an incremental load, any models that have this option set will automatically be fully refreshed if the schema of the model changes. Other models are unaffected (unless --full-refresh is applied, in which case all models are fully refreshed as usual).
Describe alternatives you've considered
The only alternative is to specify --full-refresh during dbt run.
This has some drawbacks:

It's blunt - all models selected will be fully refreshed, but we may only need one model from those selected to be fully refreshed
It's hard to automate - in a CI/CD context where we have models that are materialized by a pipeline, it's hard to know when a full refresh is needed
It's prone to human error - devs need to recognise when they need to do a full-refresh, and possibly pass this information on to the release manager who is ultimately responsible for the deployment (and materialization) in downstream environments.

Who will this benefit?
This is useful for those who meet at least one of the following criteria:

those targetting a DB that can't drop columns from an existing table
those who require new columns to be back filled

In our specific use case, we've got a transformation layer in DBT that targets Databricks (see https://docs.databricks.com/en/delta/delta-column-mapping.html for info on limitations for dropping columns). Once the incremental tables are materialized by DBT, we have a third party tool that loads the data into an external system (Salesforce). We use incremental tables so that we can maintain a last modified timestamp for each record, which allows us to do partial loads into the external system.
Whenever a column is added or removed from the materialized tables, we'd like to bulk update all the last modified timestamps so that all the data is re-loaded into Salesforce (thus back filling the new fields in Salesforce). If DBT could automatically do a full refresh whenever schemas change, this would alleviate three problems for us:

our target DB technology does not allow us to drop columns from existing tables
new columns are not back-filled by dbt
we want last modified timestamps (set to the time that the records are loaded into the materialized table) to be updated en whole so that all records are re-uploaded to our external system

Are you interested in contributing this feature?
If it's an easy enough change, and someone points me in the right direction I could have a go at it
Anything else?
No response

Thanks for opening @paynecrl97! I agree with the thrust of what you've written above.
I believe this is a duplicate of an open issue, and an open PR. You can take a look at the PR for a sense of why this would be more complex to implement:

https://github.com/dbt-labs/dbt-core/issues/4473
https://github.com/dbt-labs/dbt-core/pull/6412

I'm going to close this issue, and reopen ("un-stale") the previous one, to keep the conversation centralized there.


ReadWriteRaw

Adding a method that allows raw usage of ADS command ReadWrite.

Released in version 1.7.0


Register vetero.is-cool.dev

Added vetero.is-cool.dev using the CLI.
The website I want to host: https://vetero.surge.sh/
Source: https://vetero.surge.sh/vetero.js

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

I have read the CLA Document and I hereby sign the CLA


docs/.../sendgrid: update to sendgrid v3 API

Note: still doesn't work for GAE standard.

@broady looks like we have some merge conflicts + need a rebase.

@broady, is this still needed?

Might be worth another look. We were blocked on Sendgrid adding some features to their client (well, actually, I tried to add the feature but got blocked on their overreaching CLA). I think it was just the ability to set HTTP client (i.e., urlfetch).


VM's are not accessible.

Hi
I am trying to use this tool to create an attack dataset for my research. Unfortunately, all the VMs other than the controller is not available to download. Is it possible for you to make them public?
Thanks

Hi Bardia13,
We apologize for the inconvenience. We already update the VM link.
If you have any issues with it don't hesitate to contact us.
Thank you


Auto select bugfixes

Auto selection of Go Version & Pkgset based on .go-version & .go-pkgset weren't working in my environment. It was complaining about missing $GVM_ROOT/.gvm/scripts/use file, whenever I did cd.
I've made some changes to call appropriate "use" function/script in the same shell for both Go version & pkgset, so that the exported environment values are properly set in the user's shell. After these changes, they're working for me. I have done some basic testing in OS X. Please check.
Thanks for the great tool!

Thanks for your contribution. Give me a few days to check this PR.

Do you remember at all what the specific messages were that were output to the console?
I'm looking at this on macOS and this is what I see on an upgraded system after "sourcing" gvm from the same terminal session. Just to be clear, I start a terminal session, upgrade gvm2, source the $HOME/.gvm/scripts/gvm script, then run cd:
$ cd ..
-bash: /Users/jonytest/.gvm/scripts/env/use: No such file or directory
-bash: /Users/jonytest/.gvm/scripts/env/pkgset-use: No such file or directory

And for a directory with .go-pkgset and .go-version present:
-bash: __gvm_pwd: command not found
ERROR: Please specify the version. Execute 'gvm use --help' for command help.

What's happening in these cases is that the existing shell has some stale paths and stale function definitions defined. Opening a new terminal session results in no errors output.
It's helpful to provide output before submitting or along with a PR.

Parts of this PR have been merged and now appear in GVM2 0.10.2.
Thanks again for your contribution. Please open a new issue or PR if you continue to experience issues.


ISPN-14974 Fix opentelemetry-sdk-common dep version

https://issues.redhat.com/browse/ISPN-14974
This should fix the CI. I hope so

Thank you @ryanemerson


After upgrade to Monitoring v2 cluster name is no longer included in alerts

Issue description:
When an alert fires it does not mention from which cluster it comes.
Business impact:
Much time is lost going through each cluster looking for failures when an alert comes in. Some customers have hundreds of clusters and this renders the alert largely useless as an early response tool
Troubleshooting steps:
Enable Monitoring v2 and set an alert threshold low so the alert will fire.
Repro steps:
Enable Monitoring v2 (possibly have to upgrade from v1?)
Set an alert threshold low so the alert will fire.

Actual behavior:
Alert comes in without a cluster name.
Expected behavior:
Alert should include the cluster name
Additional notes:
Since this was working in v1 it is expected behavior this is a regression.
SURE-2912

QA, please confirm this is still an issue in 2.6.x

@MKlimuszka monitoring v2 doesn't include the cluster name in alerts. it is, however, configurable on the alert itself to include whatever information relevant to the alert that the user finds useful.
eg, in the alert name, I include the cluster name

As @ronhorton mentioned, you can always add the label to the alert. The field to configure to get this is https://github.com/rancher/charts/blob/949710afc89c78a07aa3f0082046526738ba547d/charts/rancher-monitoring/100.1.2%2Bup19.0.3/values.yaml#L566
But auto-inferring the cluster name on install and inserting it into this list is a feature request

I would argue that adding cluster name to the alerts is not a Feature Request as it was standard in Monitoring v1, and so this is a regression and bug.
Though we have a workaround, I believe it is not reasonable for a customer with tens or hundreds of clusters to go and edit each and ever alert for each of those clusters so that it includes the cluster name.  Since this is such an old regression (as v2 has been out for more than a year now), and since we are now removing the ability to easily deploy v1 or continue using it, I believe it's reasonable to argue that v2 should have reached feature parity with v1.  I would argue that this should be of a higher priority.
From speaking to Arvind, we have a couple approaches for resolution.  Can we get it slotted for an upcoming release?  I believe it warrants fixing the regression over more changes to UI that users will have to adapt to.

Still an issue - Alerts do not contain cluster name in 2.6.9-rc1

I have added a new cluster-id label to all existing Prometheus Recording rules within the monitoring chart. However, for any new rules created from the UI, we will need to make that change on the UI itself, and add another default label.
Related Ticket: https://github.com/rancher/dashboard/issues/7513

No cluster name reported in alerts by default
The default includes the cluster id, but does not include the cluster name. this is true in 2.6.12 and 2.7.2

testing blocked by https://github.com/rancher/dashboard/issues/8902

Pass verified in 2.7-head commit ID 707d173
clustername now included by default in alert labels.


Document the ability to set custom JPEG quality level

Could you please document (perhaps under AbstractSource::Encoder) the fact you can pass any value between 1 and 100 in the flags parameter when saving as JPEG to set a custom quality level. I only found this out from extensive googling on the FreeImage library.
image.save("./thumbnail.jpg", :jpeg, 90)

Cheers

Happy to accept a patch to the documentation if you have one.

Actually, this appears documented.  See
http://cfis.github.io/free-image-ruby/classes/FreeImage/File.html#method-i-save
And here:
http://cfis.github.io/free-image-ruby/classes/FreeImage/AbstractSource/Encoder.html

No that only documents the constants. It seems like you can only choose from a handful of predefined image quality levels (e.g. JPEG_QUALITYSUPERB, JPEG_QUALITYGOOD, JPEG_QUALITYNORMAL). The difference in quality and file size between JPEG_QUALITYSUPERB and JPEG_QUALITYGOOD is huge, and most people will want something between the two.
FreeImage allows you to use any JPEG quality value between 0 and 100. It reserves the first 7 bits of the JPEG flag parameter for this purpose. If you wanted to just set the quality to 90 like the example in my OP, you can do just that. If you want to set the quality to 90 and JPEG_OPTIMIZE, you could just do this:
image.save("./thumbnail.jpg", :jpeg, 90 | FreeImage::AbstractSource::Encoder::JPEG_OPTIMIZE)

I'll make a patch for the documentation.

Ah, I see.  Thanks, request merged.


feat(sequencer): implement generation of action tree commitment

first part of #153 (implementing solution 4. in that issue):

do the sorting on the block proposer side, create a commitment to the batch of txs with data for a specific rollup, and put that as a special "transaction" type inside a block. then, the flow will be:
a. conductor fetches batch of data for its rollup + the special "commitment transaction" + merkle proof of commitment tx inside data_hash
b. re-calculates and verifies the commitment using its batch of data
c. verifies that the commitment was included inside the block's data_hash
this seems like a good solution, but we'll need to update the application validator logic to verify that the commitment txs are valid commitments before voting yes for that block.

implement generation of "action tree" and put the merkle root of this tree as the first "transaction" in a block when proposing
verify this when receiving a proposal

next steps are #208 and then implementing the actual verification of the batch of rollup txs on the conductor side by verifying that it's included in the commitment transaction.

When this is all complete, I'd like to have a spec file about how it works and how to use it to verify data.

@joroshiba added a diagram w/ text to specs/, let me know what you think, I can also break the text out into the .md if that's easier to read

@joroshiba @SuperFluffy updated the spec doc, feel free to take another look!


Test Suite and Handling of HTTP 429 Response

Hi there,
I plan to add handling of the HTTP 429 Too Many Requests error, but felt safer attacking that problem with a test suite in place.
So, here 'tis.
Gavin.

Finally got around to testing this out myself. Thanks for the unit tests! Could be cleaned up a bit, but is better than the lack of tests I had before :)


Update py run path v2

@divyagandhii, @ahmelsayed, these are the changes for supporting Python 3.7 in this repo. I'm submitting a separate PR on the private repo.


Ability to ignore a steps ?

Hi,
I'm just discovered zero code and it is great.
I would like to know if there is a way to disable some steps from a scenario ? (for example by adding a attribut ignore: true ).
This ability could help me to do some "BabySteps coding". I would like to code in a T.D.D. style approach with Baby steps.
Here the process I like to follow :

Scenario is written in json and commit in a feature branch.
Scenario is review with P.R. and then merge into master (json file is not referenced in Junit Test File, so It won't be launch)
When implementing the code matching the scenario, all steps of the scenario are made disable except those that will be implements by the code, then iterate until all steps is active.

@schhor , ignoreStepFailures is already present, but this may be in a slight different context.
Please have a look here. This applies to the entire scenario, bot individual steps.

I would like to know if there is a way to disable some steps from a scenario ? (for example by adding a attribute ignore: true ).

Yes, we can sort this out for you in the upcoming release.  This is bit granular and you want the control in the individual steps. Sounds good 👍

Hi @nirmalchandra,
I have seen the ignoreStepFailures but like you have guess I don't want my build to fail.
It would be great if this can be done in the next release !  Thanks you so much :)

A another thing, can I contribute ? do you have any entry point to know how to to do? thanks

Note-
This is not kind of or related to issue #328
Can you please unlink(when you get a chance)?

Hi,
I have edited my comment to remove the link

Thanks @schhor. Apologies for the delay in getting this fixed.
This will be available in v 1.3.17.
Due to end-of-year and X-mas time, we are experiencing a slight delay in the review and release processes.  We are trying our best to get the fixes released by early 2020.

Hi,
I'm just discovered zero code and it is great.
I would like to know if there is a way to disable some steps from a scenario ? (for example by adding a attribute ignore: true ).
This ability could help me to do some "BabySteps coding". I would like to code in a T.D.D. style approach with Baby steps.
Here the process I like to follow :

Scenario is written in json and commit in a feature branch.
Scenario is review with P.R. and then merge into master (json file is not referenced in Junit Test File, so It won't be launch)
When implementing the code matching the scenario, all steps of the scenario are made disable except those that will be implements by the code, then iterate until all steps is active.

@schhor ,
I am one of the initial designer of the HTTP DSLs.
Just trying to understand the test-flow, before we actually implement it.
Can you please validate ?
Initially, you would have all ignored steps as below:
[{
		"step": "step1",
		"ignore": true,
		"method": "POST"
                ...
	},
	{
		"step": "step2",
		"ignore": true,
		"method": "GET"
                ...
	}
]

then once you implement the POST method(mark step1 as false):
[{
		"step": "step1",
		"ignoreStep": false, //or skip this field. Default is false.
		"method": "POST"

	},
	{
		"step": "step2",
		"ignoreStep": true,
		"method": "GET"
	}
]

next, after you implemented the GET method(mark both steps as false):
[{
		"step": "step1",
		"ignoreStep": false,
		"method": "POST"

	},
	{
		"step": "step2",
		"ignoreStep": false,
		"method": "GET"
	}
]

A another thing, can I contribute ? do you have any entry point to know how to to do? thanks

@schhor , Thanks for your interest.
assuming @vkjha2000 's proposal is what you are looking for, you can check this method
org.jsmart.zerocode.core.runner.ZeroCodeMultiStepsScenarioRunnerImpl#executeSteps

Then, check the isIgnored() flag is false, then do not execute this step.

This sounds simpler, but we are open to any other approach you think is great? Also, please go through the "CONTRIBUTING.md file" for the guidelines.

for (Step thisStep : parameterizedScenario.getSteps()) {
            ...
            if(thisStep.isIgnored()){
                 continue;
            }
            ...
}

Hi @vkjha2000,
this is exactly that I want to do.
thanks

To be released in V1.3.9


bug: ion-nav-bar behaves incorrectly with content insid

Type: bug
Platform: all
Hi guys,
After update ionic to beta-14, I notice that ion-nav-bar is not behaving correctly when has content inside (like buttons, inputs, etc...).
See here an example:
http://codepen.io/anon/pen/wBmrze
Look at the following ionic css lines:
6968: [nav-bar-transition="ios"] [nav-bar="cached"] { display: block; }
7001: [nav-view="cached"], [nav-bar="cached"] { display: none; }

Both rules will be applied to the element <div class="nav-bar-block" nav-bar="cached">, and since "display: block" is defined first, it will be applied.
Cheers,
Daniel

The element that I was referring, and is not showing is:
div class="nav-bar-block" nav-bar="cached"
Apparently github doesn't like html code...

Not the purpose of the nav-bar. It should have content added to it via ion-nav-buttons
http://codepen.io/mhartington/pen/JoZOEo
For your codepen, and ion-header-bar will do.


Json editor errors

Codecov Report

Merging #560 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #560      +/-   ##
==========================================
+ Coverage   99.74%   99.74%   +<.01%
==========================================
  Files         246      246
  Lines        5974     5993      +19
  Branches     1366     1369       +3
==========================================
+ Hits         5959     5978      +19
  Misses         15       15

Impacted Files
Coverage Δ

src/components/editor/JSONEditor.tsx
100% <100%> (ø)
:arrow_up:

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 47f599e...80c85ee. Read the comment docs.


Create 125 VMs with Isolated Configuration Files

This plugin will list all VMs with configuration files (.vmx, etc) on different datastores than their disks (.vmdks). This can cause issues with some programs, such as CommVault VM backups

Please submit to the dev branch

Merged manually


Remote clusterDeployment create options.

Signed off by: @jnpacker

Removed clusterDeployment support for AWS
Added vendorizing to the build process
Added Makefile.prow to the Makefile

/cc @itdove @hanqiuzh @leena-jawale

/lgtm
/approve

Reference: https://github.com/open-cluster-management/backlog/issues/9111


Upgrade to  bdk ffi v0.30.0

Unfortunately after the last commit, my app keeps crashing right at startup.

This is another issue caused by the upgrade: https://github.com/LtbLightning/bdk-rn/issues/75

Unfortunately after the last commit, my app keeps crashing right at startup.
Hi @Czino
Not able to replicate.
The demo app is updated to use the latest commit: https://github.com/LtbLightning/bdk-rn-demo
(Be sure to point bdk-rn to local path in package json)
Are you able to run the app? or does that crash too?

Unfortunately the demo does not run at all for me

Looks like some extra steps are needed to make it run on my machine.


refactor!: remove aggregator package and related function calls

This PR removes the aggregator package as requested in the ticket in SAP/cloud-sdk-backlog#329
Closes SAP/cloud-sdk-backlog#329

please create the initial diff document and list the change that we have removed the aggregator package in v2.


KingdomsX support

I want to condition the KingdomsX plugin's upgrades using CMI ranks, for example, but when I try to do it like shown in the image, it doesn't appear in the game

Wasn't this already answered in the Discord server?


[Bug][Mapbox] Sidebar filters dropdown are not filtering Places on the map.

Describe the bug
The filter dropdowns in the Terrastories sidebar are supposed to do a few things:
Filter the stories in the sidebar,
Zoom to the maximum extent of the Places with filtered stories,
Hide Place markers on the map that don't have a story in the active filter.
Currently, this last step is not working.
To Reproduce
Steps to reproduce the behavior (this is one example):

Use one of the dropdown filters.
It will zoom to the maximum extent of the Place markers.
Navigate the map to where there were other Place markers that should have been filtered out. You will still see them show up.

Expected behavior
The only Place markers on the map that should show up are Places that have a Story in the sidebar. (I.e. if there are 100 places in Terrastories, and an active filter is only showing stories for 25 places, only those 25 Place markers are shown).
Additional context
This demo, running a November 2020 version of the Terrastories codebase, does have the behavior as desired working. http://terrastories-2020imw.herokuapp.com/

@lauramosher I think this may have come up during the December Tech Matters work. Because the filters were operating just fine in November.

@lauramosher I think this may have come up during the December Tech Matters work. Because the filters were operating just fine in November.

@rudokemper I looked into this — the filter logic is all encompassed in the React code; not the rails code. This was likely accidentally introduced when we merged the new Map + Marker components since it changed how we update the markers on filtering.
See: https://github.com/Terrastories/terrastories/pull/563
Updating the labels. @mirandawang Do you have time to look into this?

Yeah, my mistake on this -- I thought that the November 2020 Heroku demo above was using a version of the codebase with the map marker refactoring work already done, but that is not the case. That took place shortly after IMW and before the TM work. Was getting my timelines confused :)

That's great! Thanks @astojanowski I just assigned it to you.

Fixed by updating map markers source every time the list of places has changed. Additionally I removed duplicates from the list of points, couldn't find any use of these duplicates...


docs(readme): update references to fluent-ui-react

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Missing processor for successfulPayment

In payment flow (see docs)after onPreCheckoutQuery telegram sends json containing successful_payment model.
The library missing a handler for this, I believe it should be added along side Televerse.onPreCheckoutQuery method.

Hey @Defuera, thanks for raising this.
The SuccessfulPayment object is already available in the library. When a payment is successful, Telegram sends a "service message" containing the successful_payment parameter. You can listen for this message by adding a listener using the Televerse.onMessage method, or by specifically filtering for successful payment messages using the Teelverse.filter method, as shown below.
  bot.filter((ctx) => ctx.message.successfulPayment != null, (ctx) async {
    // Do your stuff here...
  });

Hope this helps. ✨

Also, as you raised this we can may be add a filter method just for listening this service messages. Something like Televerse.onSuccessfulPayment.
Will that be something you're interested in?

Oh, that's great. Thx @HeySreelal
And thanks for the great library in general. I'm developing a framework around it, that allows to build a complex dialog flows keeping context. https://pub.dev/packages/chatterbox
It's very early stage. But just FYI :)

Wow! I'm so excited to hear that! Tbh, I'm super excited to contribute as well. If you have any issues with the Televerse package or need some tweaks in this package to make your tool better, feel free to reach out to me or in our Telegram group. I will be more than happy to help you out on this. ❤
When building Televerse, extensions to this package was in my mind. But I was not sure how much feasible it is until I heard this from you. Feel free to let us know if you need to tweak this library at any point of your extension development.
Have a good time Televersing! 🚀

Here's the implementation according to suggestion above.
Usage:
bot.onSuccessfulPayment((ctx) {
      //todo your code
      print('Successful payment ${ctx.update.message?.successfulPayment}');
    });

televerse_extensions.dart
import 'dart:async';

import 'package:televerse/telegram.dart';
import 'package:televerse/televerse.dart';

typedef SuccessfulPaymentHandler = FutureOr<void> Function(MessageContext ctx, SuccessfulPayment successfulPayment);

extension TeleverseExtensions on Televerse {
  void onSuccessfulPayment(SuccessfulPaymentHandler handler) {
    filter(
      (ctx) => ctx.message.successfulPayment != null,
      (ctx) => handler(ctx, ctx.message.successfulPayment!),
    );
  }
}

Yeah yeah! Consider this done! Btw, I meant if you need further tweaks in the project for extensions compatibility.
Peace ✌


[PROPOSAL] Archive this repository

What/Why
What are you proposing?
The opensearch-dsl-py client has been deprecated since 2.1.0. Time to archive it.
What users have asked for this feature?
Users are still confused what python client to use.
What problems are you trying to solve?
Have one less client.
What is the developer experience going to be?
Use opensearch-py.
Are there any security considerations?
None, we haven't patched/released anything from this repo in months.
Are there any breaking changes to the API
No.
What is the user experience going to be?
One less client.
Are there breaking changes to the User Experience?
No.
Why should it be built? Any reason not to?
None.
What will it take to execute?

Update README to say that the repo is now archived vs. what it says now, that the client is deprecated.
Resolve any open issues/close PRs.
Archive this repo.

Closing this and archiving the repo.


Fix: Add node flag to WASM queries (build-address)

Description
This PR adds a new --node flag to support custom endpoints for node connections while making Wasm queries specifically build-address. This update ensures that the provenanced q wasm build-address command works correctly with custom node configurations.
Issue:
While creating the predictable contract address I encountered the following error:
unknown flag: --node

This occurred when running the following command:
provenanced query wasm build-address <code-hash> <creator-address> <salt> --node https://rpc.test.provenance.io:443

It seems the flag is not being recognized properly. I suspect there might be an issue with either the flag registration in the command definition (root.go) or how the CLI parser processes the command.
The main file updated is:

cmd/provenanced/cmd/root.go

closes: n/a
I haven't created any particular issue for this change. However, this was discussed on Discord, where it was agreed that the node flag should function correctly.
Reference: Discord conversation.

Checklist

[x] Targeted PR against the correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
(I haven't created any issue for this minor fix.)
[ ] Wrote unit and integration tests (see Testing Guidelines).
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant GoDoc comments (GoDoc Documentation).
[ ] Added relevant changelog entries under .changelog/unreleased (see Adding Changes).
[x] Re-reviewed Files changed in the Github PR explorer.
[ ] Reviewed Codecov report in the comment section below once CI passes.

Summary by CodeRabbit

New Features

Introduced new command flags for custom denomination and message fee floor price.
Added a flag to specify the node connection for enhanced configurability.
Enhanced query wasm build-addr command with additional query flags for improved usability.

Improvements

Enhanced error handling for better user experience, including automatic creation of the snapshot directory.
Updated command initialization to disable the start command upon error, preventing misleading usage information.
Improved telemetry configuration for better flexibility.

Miscellaneous Adjustments

Removed shorthand options for conflicting flags and ensured correct command aliasing.

The query wasm build-address command does not add the standard AddQueryFlagsToCmd to it because it doesn't actually make a query of a node; it just runs some local calculations to output the desired result. So there's no need to provide a --node flag to it because it doesn't use a node; there's nothing in the command's code (defined in the wasmd library) that looks for the flag.

Yes, it doesn't actually have any dependency on the node but it does tries to connect with the node. Thus, giving the following error:
Error: post failed: Post "http://localhost:26657": dial tcp <IP_ADDRESS>:26657: connect: connection refused

We can also consider removing the validation for this.

Yes, it doesn't actually have any dependency on the node but it does tries to connect with the node. Thus, giving the following error:
Error: post failed: Post "http://localhost:26657": dial tcp <IP_ADDRESS>:26657: connect: connection refused

We can also consider removing the validation for this.

Sorry. You're right. I was looking at an earlier version of the command, but it looks like the current version does make a request of the node.

Hi @SpicyLemon @iramiller
I have made the required changes. Please review and let me know if anything is left.

Hi SpicyLemon iramiller I have made the required changes. Please review and let me know if anything is left.

Looks good! Thanks for the fix!

Oh darn. Sorry. We require all commits to be signed, so this can't be merged as it is. I've recreated it as #2199 (with signed commits), and I'll close this one.
Here's more info on signing commits: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
Thanks again for the fix!


Add/Update unit-tests

Adding few unit-tests for newly added source.
Updated existing unit-tests to work with the update source.

Additionally, adding few missing NULL checks at certain places in the
source, that were found and needed for unit-tests to work.
Signed-off-by: Chandrakar, Prateek<EMAIL_ADDRESS>

Updated.


How to implement Components in formio-grid (Angular 8)

Am new with Angular 8 and formio-grid.
Can anyone give me an example on how to implement Components in formio-grid?

Closing this thread as it is outdated. Please re-open if it is still relevant. Thank you for your contribution!


cupertino icon page not found

i can't see cupertino icon page in github.

cc @RedBrogdon  https://flutter.github.io/cupertino_icons is no longer up.

the package has been moved to here https://github.com/flutter/packages/tree/master/third_party/packages/cupertino_icons
see the changelog https://github.com/flutter/packages/blob/master/third_party/packages/cupertino_icons/CHANGELOG.md#103
I too need a preview page to select the icon !!

Here is a broken documentation page for your reference: CupertinoIcons class - cupertino library - Dart API
If it is possible to setup GitHub pages like flutter/cupertino_icons, I think we can fix 404 errors by replacing the URLs with the ones like https://flutter.github.io/packages/third_party/packages/cupertino_icons/something.

As a temporary method, you can download the cupertino_icons directory and on your computer simply open index.html in your browser, and everything works fine.

I deployed a temporary GitHub page (using my domain) of a fork repository: https://shuuji3.xyz/flutter-packages/third_party/packages/cupertino_icons/. Please use this until this issue is fixed if you want.

I deployed a temporary GitHub page (using my domain) of a forked repository: https://shuuji3.xyz/flutter-packages/third_party/packages/cupertino_icons/. Please use this until this issue is fixed if you

For those who want to find icons, as a temporary method, you can download the cupertino_icons directory and on your computer simply open index.html in your browser. Everything works fine.

Good idea, sometime I want to try..

I deployed a temporary GitHub page (using my domain) of a forked repository: https://shuuji3.xyz/flutter-packages/third_party/packages/cupertino_icons/. Please use this until this issue is fixed if you want.

Thanks bro

Lets keep the issue open for official link

Here it is an alternative: https://web.archive.org/web/20210728212734/https://flutter.github.io/cupertino_icons/

@HansMuller, @gspencergoog, or @stuartmorgan do any of y'all know how that page normally got published?

I wasn't aware of that page, but it looks like it was just auto-created via GitHub Pages. From a bit of skimming docs it sounds like we could use https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source to publish it at flutter.github.io/packages, but I didn't see a way to change the URL to get the old one back.
@Hixie Should we re-instate that repo just for the website part, or host the content differently?

FWIW, you can temporarily set up a redirect from the old repo's GH page to the new. Did this when we moved gallery from https://flutter.github.io/gallery to gallery.flutter.dev, https://github.com/flutter/gallery/commit/0c0ab858d8e99d35682aa751a2b7d37f64d2c098

Sorry, I don't know how that page was originally published.
Seems like we should set up a redirect to start with, and then figure out how to migrate it permanently.

Whoever has access to https://github.com/flutter/cupertino_icons/settings/pages and   https://github.com/flutter/packages/settings/pages can set that up

@Hixie definitely has repo access; I'm not sure who else does.

Any chance we can use dartdoc for this instead of having to host a separate page somewhere?

Can you guys add this issue link to README of cupertino_icons to people like me don't confuse, temporary?
Thank you.

@Hixie There's https://api.flutter.dev/flutter/cupertino/CupertinoIcons-class.html, but the icons aren't appearing since it relies on the .ttf and https://raw.githubusercontent.com/flutter/packages/master/third_party/packages/cupertino_icons/css/icons.css being hosted somewhere (Github pages works, raw Github doesn't work)

we should be able to make that work, we made it work for MaterialIcons.ttf and the Icons class

What about copying the css and tff from cupertino_icons into assets-for-api-docs: https://github.com/flutter/assets-for-api-docs/pull/171
Then updating the stylesheet link to point to the updated location? https://github.com/flutter/flutter/pull/92932
It's not ideal since we have two copies of the ttf file, but it will fix the doc glyphs until we come up with a better solution.
@gspencergoog can you sanity check, am I on the right track with those PRs? Or can you suggest a better way to do it?

@jmagman That seems OK to me. Most of the stuff in assets-for-api-docs is supposed to be generated from code, but there are already some exceptions, and these obviously can't be (and shouldn't be) generated.

Can we see if linking directly to resources works (e.g., set https://raw.githubusercontent.com/flutter/packages/master/third_party/packages/cupertino_icons/css/icons.css as the style sheet) before we copy them?

Can we see if linking directly to resources works (e.g., set https://raw.githubusercontent.com/flutter/packages/master/third_party/packages/cupertino_icons/css/icons.css as the style sheet) before we copy them?

I thought @guidezpl said that using raw Github wouldn't work...? Can you elaborate, @guidezpl ?

It relies on the .ttf and https://raw.githubusercontent.com/flutter/packages/master/third_party/packages/cupertino_icons/css/icons.css being hosted somewhere (Github pages works, raw Github doesn't work)

I can't get flutter/website running right now to test, but it was either a MIME type error or some Github protection to prevent using the site as a hosting platform without using Pages.

Sorry, I missed that it had already been tested and hadn't worked.

The broken icon gallery preview image will instead be replaced by a tool snippet, similar to the Icons docs:

Asset PR at https://github.com/flutter/assets-for-api-docs/pull/172

This is looking better in the master version of the API docs: https://master-api.flutter.dev/flutter/cupertino/CupertinoIcons-class.htm
Sample code with diagram image shows up, glyphs map link is working, the fonts are showing:

No more dead links in the pub package description:
https://pub.dev/packages/cupertino_icons
or README:
https://github.com/flutter/packages/tree/master/third_party/packages/cupertino_icons
gallery.flutter.dev doesn't have a section for Cupertino icons, so it probably doesn't make sense to point to the new link instead.  Not sure if there's additional value adding back the missing https://flutter.github.io/cupertino_icons gallery.

Hey guys, any updates on this issue? It has been a few months already, but the document of CuptertinoIcons class is still pointing to a dead page
When the master branch will be deployed?

@timnew It should be fixed in the next stable (sometime this quarter). You can see what will ship in the next stable here: https://master-api.flutter.dev/flutter/cupertino/CupertinoIcons-class.html
It looks like the fix above missed the last stable push by a hair's breadth unfortunately.

It could be great to have the Original Cupertino Icon Gallery again, and even better with our click-n-copy-to-clipboard™ feature.

Filtering and copy-to-clipboard are both good feature requests for both Cupertino and Material. I filed https://github.com/flutter/flutter/issues/97727 on your behalf.

Improved Cupertino API docs have been deployed at https://api.flutter.dev/flutter/cupertino/CupertinoIcons-class.html.  There are no more broken links in the API docs or GitHub README/pub entry.  See also the new example code snippet.
Closing as complete.


Add command line editing and history to amy-message

I've added this locally and it's nice for testing at the shell.
Is there interest in this for AMY's core or should I fork?

I use amy-message as my primary way to playing with and learning AMY.
In addition fo history, I have several enhancements:

Ignore all text following '#' for comments.
Allow multiple messages per line, separated by semicolons
Allow "relative timestamps", using "+" followed by an integer represending milliseconds. This is to avoid having to get the current sysclock value and doing math to schedule message.

I've gone crazy on this tool... here's a preview of what's possible:

This is from a terminal... another example that captures the PCM bird cheep. I can write the captured data as a JSON or WAV file as well.
I know this is all possible from amy.py, but I wanted to have a somewhat stand-alone tool.


wip(module:input) refactor input

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[x] Yes
[ ] No

Other information

Coverage remained the same at 98.345% when pulling 2645dd6ec9af7e9e8b85b93229850518ad18bb59 on vthinkxie:0.7.0 into 94a9e41d5f60ac110a239d58c94e333a72068fb4 on NG-ZORRO:0.7.0.


Support for SolaX X1

From the readme I understand that the SolaX X1 (not mini) isn't supported, but is there any reason to believe this project won't work with that inverter?

There are not much informations available about the different inverter models. Therefore it's hard to make a prediction about the supported protocols of the firmware.
If you own the device please give it a try! If you don't own the device: If this implementation doesn't work it's likely the inverter supports Modbus.
If the the inverter have an RS485 port and this implementation

I'm working on this just now - with an X1. Will report back on whether I can get it to run. I can confirm that it's built with RS485 and not modbus. It does seem like there may be an issue with the data integrity check on device serial number, as it seems mine is alphanumeric and not hexadecimal, so am getting tripped up in compile stage with esphome.

Seems my python coding skills (which are not great) have proven insufficient. I'd meant to simply cut out the integrity check requirement for hexadecimal, but the whole thing fails now. I have triple checked that my serial number is indeed alphanumeric - and I'm pretty sure it is a serial number as it is still 14 chars, and is listed on solax as "Inverter SN". Any chance someone else with more python skills than I could create a branch I could test that does this test as 14 char alphanumeric?

Please use the default SN from the example. The specific serial number isn't important / respected.

Ah - thx! Will try.

None of the projects I found seemed to work for my newest generation Solax X1 Boost (serial number starts with XB33). At some point, I wondered whether I could write a configuration for vanilla ESPHome instead, and I got it to work!
I've submitted the configuration to the repository of the creator of the Modbus shield that I'm using, but it should work if you wired things together yourself if you change the pinout.
@syssi Perhaps you can use the default baud rate, address, registers, etc. for your project in order to support the X1 Boost?

I can confirm this module doesn't work for my X1 (firmware flashed ok and unit connected to HAOS no probs). So far no data received on any of the entities created by the device in ESPHome. I'm working with an XY-017 unit wired into my esp32doit-devkit-v1, so will have a check and see how this corresponds to your modbus shield @benjaminvdb. Many thanks for this extremely useful info!

None of the projects I found seemed to work for my newest generation Solax X1 Boost (serial number starts with XB33). At some point, I wondered whether I could write a configuration for vanilla ESPHome instead, and I got it to work!
I've submitted the configuration to the repository of the creator of the Modbus shield that I'm using, but it should work if you wired things together yourself if you change the pinout.
@syssi Perhaps you can use the default baud rate, address, registers, etc. from my configuration for your project in order to support the X1 Boost?

PS, that modbus shield is a great piece of kit. Might get one of them as well!

No luck for me either way. Looks like I need to debug hardware setup a bit as I'm getting nothing from modbus:
[15:56:55][D][modbus_controller:032]: Modbus command to device=1 register=0x400 countdown=0 no response received - removed from send queue
Suspect it's a bad connection somewhere between esp32 and XY-017... Will report back as things progress.

At the modbus_controller approach you have to make sure the address matches with the Modbus address of the inverter configuration. Sometimes you have to enable Modbus at the inverter settings and double check the modbus address.
If you enable the debug mode of the uart component you can see the outgoing and incoming traffic at the logs. Does the TX led of your RS485 converter blink periodically?

@syssi how are you accessing the inverter configuration? I have a Pocket Wifi V3.0 Dongle, which won't allow access using admin:admin (I guess Solax is trying to push their cloud / api product?). But perhaps there's an alternative I'm missing here?

I see what you mean about RX/TX lights on the XY-017, I hadn't even noticed them! They are blinking symmetrically pretty often (e.g. every half second of so). That rules out lack of voltage to that board...

So I've enabled uart debug mode, but not quite sure what to make of the output. Here's a sample:
[16:42:57][D][modbus_controller:032]: Modbus command to device=1 register=0x414 countdown=0 no response received - removed from send queue
[16:42:57][D][uart_debug:114]: >>> 01:04:04:23:00:01:C1:30
[16:42:58][D][uart_debug:114]: >>> 01:04:04:23:00:01:C1:30
[16:42:59][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1031 count=1
[16:42:59][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1034 count=1
[16:42:59][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1059 count=1
[16:42:59][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1061 count=1
[16:42:59][D][uart_debug:114]: >>> 01:04:04:23:00:01:C1:30
[16:43:00][D][uart_debug:114]: >>> 01:04:04:23:00:01:C1:30
[16:43:01][D][uart_debug:114]: >>> 01:04:04:23:00:01:C1:30
[16:43:02][D][modbus_controller:032]: Modbus command to device=1 register=0x423 countdown=0 no response received - removed from send queue
[16:43:02][D][uart_debug:114]: >>> 01:04:04:07:00:01:81:3B
[16:43:03][D][uart_debug:114]: >>> 01:04:04:07:00:01:81:3B
[16:43:04][D][uart_debug:114]: >>> 01:04:04:07:00:01:81:3B
[16:43:05][D][uart_debug:114]: >>> 01:04:04:07:00:01:81:3B
[16:43:06][D][uart_debug:114]: >>> 01:04:04:07:00:01:81:3B
[16:43:07][D][modbus_controller:032]: Modbus command to device=1 register=0x407 countdown=0 no response received - removed from send queue
[16:43:07][D][uart_debug:114]: >>> 01:04:04:0A:00:01:10:F8
[16:43:08][D][uart_debug:114]: >>> 01:04:04:0A:00:01:10:F8
[16:43:09][D][uart_debug:114]: >>> 01:04:04:0A:00:01:10:F8
[16:43:10][D][uart_debug:114]: >>> 01:04:04:0A:00:01:10:F8
[16:43:11][D][uart_debug:114]: >>> 01:04:04:0A:00:01:10:F8
[16:43:12][D][modbus_controller:032]: Modbus command to device=1 register=0x40A countdown=0 no response received - removed from send queue
[16:43:12][D][uart_debug:114]: >>> 01:04:04:25:00:01:21:31
[16:43:13][D][uart_debug:114]: >>> 01:04:04:25:00:01:21:31
[16:43:14][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1024 count=5
[16:43:14][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1037 count=3
[16:43:14][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1044 count=2
[16:43:14][W][modbus_controller:113]: Duplicate modbus command found: type=0x4 address=1061 count=1
[16:43:14][D][uart_debug:114]: >>> 01:04:04:25:00:01:21:31
[16:43:15][D][uart_debug:114]: >>> 01:04:04:25:00:01:21:31
[16:43:16][D][uart_debug:114]: >>> 01:04:04:25:00:01:21:31
[16:43:17][D][modbus_controller:032]: Modbus command to device=1 register=0x425 countdown=0 no response received - removed from send queue
[16:43:17][D][uart_debug:114]: >>> 01:04:04:00:00:05:31:39
[16:43:18][D][uart_debug:114]: >>> 01:04:04:00:00:05:31:39
[16:43:19][D][uart_debug:114]: >>> 01:04:04:00:00:05:31:39
[16:43:21][D][uart_debug:114]: >>> 01:04:04:00:00:05:31:39
[16:43:22][D][uart_debug:114]: >>> 01:04:04:00:00:05:31:39
[16:43:22][D][modbus_controller:032]: Modbus command to device=1 register=0x400 countdown=0 no response received - removed from send queue
[16:43:23][D][uart_debug:114]: >>> 01:04:04:0D:00:03:20:F8
[16:43:24][D][uart_debug:114]: >>> 01:04:04:0D:00:03:20:F8
[16:43:25][D][uart_debug:114]: >>> 01:04:04:0D:00:03:20:F8

>>> is outgoing traffic. If the inverter responds you should see <<< lines.
RE inverter settings: I assumed your inverter have a display and an item somewhere at the on screen menu to enable the modbus support + set the modbus address.

>>> is outgoing traffic. If the inverter responds you should see <<< lines.
RE inverter settings: I assumed your inverter have a display and an item somewhere at the on screen menu to enable the modbus support + set the modbus address.

That makes perfect sense. Thx for the interpretation here. I've been through the on-screen menu, but it seems they've set a 4 digit numeric password for this as well, the obvious options (0000, 1234, 9999) haven't worked so far.

Please try 6868.

well, for future reference in case anyone else stumbles on this post with the same question, apparently the solax default installer password is 6868. These menus can also be accessed via https://www.solaxcloud.com, via "device management" and "remote setting". And just as you'd suggested, there's a place to enable modbus (was disabled!) and set the address (defaulted to 1).

Please try 6868 and 2014.

Sorry - was typing at the same time as you. 6868 has done the trick. I've got modbus enabled now.

Still no inbound modbus however, will see about switching back to uart0

BINGO! That's the ticket. Running like a charm now.

My Solar X1 mini turns off if it's dark out there / at night and doesn't respond anymore. I assume the Boost version behaves different because it's always on(?).

Good job! As last step I would be happy if you could try this custom component a last time. Just to make sure your inverter doesn't support the "special X1 mini protocol". It's possible your inverter is able to handle both protocols (special version + generic modbus registers).

Happy to test - there are other X1 users out there I'm sure. Am currently working off the config that @benjaminvdb mentioned above, which is:
substitutions:
  name: solax-x1-rs485_v2
  device_description: "Monitor a Solax X1 via RS485"
  tx_pin: GPIO1
  rx_pin: GPIO3
  prefix: solax

esphome:
  name: ${name}
  comment: ${device_description}
  platform: esp32
  board: esp32doit-devkit-v1

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  use_address: <IP_ADDRESS>
  ap:
    ssid: "ESP-Modbus"
    password: "configesp"

ota:

# Enable Home Assistant API
api:

captive_portal:

# Enable/Disable logging
logger:
  level: verbose
  baud_rate: 0 ## Must be 0 to prevent reading issues and buffer overflows

uart:
  id: mod_bus
  tx_pin: ${tx_pin}
  rx_pin: ${rx_pin}
  stop_bits: 1
  baud_rate: 9600

modbus:
#  flow_control_pin: D5
  id: modbus1
  send_wait_time: 1000ms

modbus_controller:
  - id: solax
    address: 0x1
    modbus_id: modbus1
    setup_priority: -10
    #command_throttle: 250ms
    update_interval: 15s

sensor:
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} PV1 Input Voltage"
    address: 0x400
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: V
    device_class: voltage
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} PV2 Input Voltage"
    address: 0x401
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: V
    device_class: voltage
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} PV1 Input Current"
    address: 0x402
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: A
    device_class: current
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} PV2 Input Current"
    address: 0x403
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: A
    device_class: current
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Grid Voltage"
    address: 0x404
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: V
    device_class: voltage
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Grid Frequency"
    address: 0x407
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 2
    unit_of_measurement: Hz
    device_class: frequency
    state_class: measurement
    filters:
      - multiply: 0.01
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Output Current"
    address: 0x40A
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: A
    device_class: current
    state_class: measurement
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Temperature"
    address: 0x40D
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 0
    unit_of_measurement: C
    device_class: temperature
    state_class: measurement
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Inverter Power"
    address: 0x40e
    register_type: read
    value_type: U_WORD
    unit_of_measurement: W
    device_class: power
    state_class: measurement
    accuracy_decimals: 0
  - platform: modbus_controller
    modbus_controller_id: solax
    id: ${prefix}_power_dc1
    name: "${prefix} Power DC1"
    address: 0x414
    register_type: read
    value_type: U_WORD
    unit_of_measurement: W
    device_class: power
    state_class: measurement
    accuracy_decimals: 0
  - platform: modbus_controller
    modbus_controller_id: solax
    id: ${prefix}_power_dc2
    name: "${prefix} Power DC2"
    address: 0x415
    register_type: read
    value_type: U_WORD
    unit_of_measurement: W
    device_class: power
    state_class: measurement
    accuracy_decimals: 0
    on_value:
      then:
        component.update: ${prefix}_total_dc_power
  - platform: template
    id: ${prefix}_total_dc_power
    name: "${prefix} Total DC Power"
    lambda: |-
      return (id(${prefix}_power_dc1).state + id(${prefix}_power_dc2).state);
    update_interval: never
    unit_of_measurement: W
    device_class: power
    state_class: measurement
    accuracy_decimals: 0
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Production Total"
    address: 0x423
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: kWh
    device_class: energy
    state_class: total_increasing
    filters:
      - multiply: 0.1
  - platform: modbus_controller
    modbus_controller_id: solax
    name: "${prefix} Production Today"
    address: 0x425
    register_type: read
    value_type: U_WORD
    accuracy_decimals: 1
    unit_of_measurement: kWh
    device_class: energy
    state_class: total_increasing
    filters:
      - multiply: 0.1

text_sensor:
  - platform: modbus_controller
    modbus_controller_id: solax
    id: ${prefix}_run_mode
    name: "${prefix} Run Mode"
    address: 0x40f
    bitmask: 0
    register_type: read
    raw_encode: HEXBYTES
    lambda: |-
      uint16_t value = modbus_controller::word_from_hex_str(x, 0);
      switch (value) {
        case 0: return std::string("Waiting");
        case 1: return std::string("Checking");
        case 2: return std::string("Normal");
        case 3: return std::string("Fault");
        case 4: return std::string("Permanent Fault");
        case 5: return std::string("Update");
        case 6: return std::string("Off-grid waiting");
        case 7: return std::string("Off-grid");
        case 8: return std::string("Self Testing");
        case 9: return std::string("Idle");
        case 10: return std::string("Standby");
        default: return std::string("Unknown");
      }
      return x;

Yes. Please try and adapt the example configuration: https://github.com/syssi/esphome-modbus-solax-x1/blob/main/esp32-example.yaml
This configuration should match your GPIO layout:
substitutions:
  name: solax-test
  device_description: "Monitor a Solax X1 via RS485"
  tx_pin: GPIO1
  rx_pin: GPIO3
  prefix: solax

esphome:
  name: ${name}
  comment: ${device_description}
  platform: esp32
  board: esp32doit-devkit-v1

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  # Enable fallback hotspot (captive portal) in case wifi connection fails
  use_address: <IP_ADDRESS>
  ap:
    ssid: "ESP-Modbus"
    password: "configesp"

ota:

# Enable Home Assistant API
api:

captive_portal:

# Enable/Disable logging
logger:
  level: verbose
  baud_rate: 0 ## Must be 0 to prevent reading issues and buffer overflows

uart:
  id: mod_bus
  tx_pin: ${tx_pin}
  rx_pin: ${rx_pin}
  stop_bits: 1
  baud_rate: 9600

modbus_solax:
  - id: modbus0
    uart_id: mod_bus

solax_x1:
  modbus_solax_id: modbus0
  serial_number: "3132333435363737363534333231"
  address: 0x0A
  update_interval: 1s

text_sensor:
  - platform: solax_x1
    mode_name:
      name: "${name} mode name"
    errors:
      name: "${name} errors"

sensor:
  - platform: solax_x1
    ac_power:
      name: "${name} ac power"
    energy_today:
      name: "${name} energy today"
    energy_total:
      name: "${name} energy total"

@kidwellj Friendly reminder.


tests: Reduce dbt versions to test on schedule and fix matrix option

We had too many tests scheduled: 4 Python versions and 4 dbt versions = 16 per adapter. So they were canceled because of time limits.
This brings them to 8 per adapter when scheduled and 4 per adapter for pull requests.
We can still improve by making each python version have a different schema to run adapter tests in parallel (the ones with remote data warehouse)

We're not going to test <v1 anymore?

Only when making changes (in pull requests)
          if '${{ github.event_name }}' == 'pull_request':
            # Add more versions for pull requests
            OUTPUT.extend(["0.20.*", "0.21.*"])


TTFiveComb

Would be nice to implement this unit, based-on the tap.5comb~ abstraction, but hopefully
sounding better.
see more on the original redmine issue http://redmine.jamoma.org/issues/137

not happening


fix: fixed scroll problem reported by user with charts on EntityDetails

Fixes this

It doesn't work - after changing the timeframe on the preview, the screen is still wider.

Closing in favor of working fix at https://github.com/kubeshop/testkube-dashboard/pull/791


Revisit LifecyclePhase

@Microsoft/vscode
A while ago we introduced LifecyclePhase as a way to give priority to all the things we do on startup. Our main goal is to delay code from executing after the editor has restored itself. The goal was and still is to get to a blinking cursor in the editor as fast as possible.
We used to have these phases:

LifecyclePhase.Starting: workbench is being created
LifecyclePhase.Restoring: we are about to restore views, editors and panels
LifecyclePhase.Ready: all views, editors and panels are restored
LifecyclePhase.Eventually: 5s after the last phase

The motivation for revisiting this is the fact that it was not possible to trigger any command (either via keybinding or via menu) until LifecyclePhase.Ready which is only met when editors have been restored. With remote editors today this can potentially take a long time so any user interaction was pretty much blocked until the editor contents have been loaded.
The new phases are as follows:

LifecyclePhase.Starting: workbench is being created
LifecyclePhase.Ready: workbench services and UI is created and we have started to restore parts, but this might not be finished yet
LifecyclePhase.Restored: all views, editors and panels are restored
LifecyclePhase.Eventually: 5s after the last phase

Here are the rules:

LifecyclePhase.Starting: put things here that have an influence on the creation of the workbench. e.g. if you have dynamic state (where is the search view - view or panel?), its fine to let that run in this phase to ensure there is no flicker on startup
LifecyclePhase.Ready: put things here that should execute even before the editors have been restored. remember that restoring can take any amount of time, so for a good user experience it makes sense to have somethings in this phase (e.g. commands, notifications)
LifecyclePhase.Restored: put things here that should not block editors from restoring. e.g. if you need to access files, use this phase such as you are not stealing resources from the editor that is trying to access the disk as well to restore the editor. getting to a blinking cursor as fast as possible is still our number one goal
LifecyclePhase.Eventually: pretty much the same as before, put things here that are absolutely not mission critical for the experience (e.g. cleanup tasks)

I made a pass over all our usages and adopted the phase as I think it makes sense.
@joaomoreno fyi this also impacts electron-main. Each window has a ready() method that can be used to wait for a window being ready and this used to be only after all editors have restored but I changed this now to the LifecyclePhase.Ready phase. I noticed the IURLService to depend on that but wasn't sure how that is being triggered, maybe you could check once we have this in insiders.

@jrieken do we depend on the name of lifecycle phase? I see LifecyclePhaseToString which seems to end up in a performance.mark call. I renamed LifecyclePhase.Running to LifecyclePhase.Restored and the previous LifecyclePhase.Restoring is now pretty much LifecyclePhase.Ready. I hope those changes do not break any performance queries we have setup?

I noticed the IURLService to depend on that but wasn't sure how that is being triggered, maybe you could check once we have this in insiders.

@bpasero Can you show me where in the code?

@bpasero re https://github.com/Microsoft/vscode/issues/63905#issuecomment-442497955
It should not, we send these number and they use different perf-marks: https://github.com/Microsoft/vscode/blob/07d7409240aca5b1469e5c97727b4adb6840421c/src/vs/workbench/services/timer/electron-browser/timerService.ts#L394-L412

@joaomoreno e.g. https://github.com/Microsoft/vscode/blob/4584935/src/vs/code/electron-main/app.ts#L629

@bpasero Looks OK.


Added Nested Endpoints to GET information about Game model (specifically Categories and Mechanics information)

With the updates to the Game model, there are now two new attributes Mechanics and Categories, that are represented as many to many relationships. This PR created two endpoint to easily GET the mechanics and categories respectively of a given game. This is very similar to the code needed to get the friends of a given user in previous issue #54.
Endpoints created: /api/games/<game_id>/mechanics and /api/games/<game_id>/categories
In addition, I modularized the API URLs, so that the urls dealing with different models
(Game, User, and Lobby models) are separated into sublists.

Had a type in code making these Retrieve API views instead of List API views. Should be able to see all Categories and Mechanics corresponding to a certain Game object now.
Also added Pagination support for these List Views as well

Closing Comment: Created two endpoints that support GET requests to get the categories or mechanics of a given Game. The specific Game is specified through the game_id within the URL.
Endpoints created: /api/games/<game_id>/mechanics and /api/games/<game_id>/categories

Issue Score: Excellent
Comments:
Happy we caught the typo!


Applying bbox labels to a file

Hello,
I am working with the mmdet3d code and trying to use the labels_3d that i get in the result file and want to run a for loop to add the labels to a json. i can not find out where and how i can access those numbers.
I already changed the box_3d_mode.py in the mmdet3d/core/bbox folder.

This is what i added to create a json and how to change the position values. But i am not able to get the label numbers from this. This is the results when i print it out from the pcd_demo.py file

If there is any idea on how to access the labels_3d that would be great. so i can add this to my json file

Sorry for the late reply. These keys including "boxes_3d", "labels_3d", and "scores_3d" are obtained here or similar places in other detectors.

Close due to inactivity. Please feel free to reopen it if there are any further questions.


rangeproof: add a test for all-zero blinding factors

I was curious about under what conditions you can create a rangeproof on an "unblinded" commitment which has a zero blinding factor. Apparently the answer is "when you are proving at least 3-bits". In this case rewinding words and you can encode 32 bytes of data. (In fact I believe you can encode up to 128 but I haven't tested that.)

Apparently the answer is "when you are proving at least 3-bits".

Hm, interesting... Do we also want to document this somewhere where it's user-visible?

Yeah, I think so. I was going back-and-forth but I think this is likely to be generally useful -- sometimes when balancing CT transactions you wind up being forced to set a blinding factor to 0 and it's good to know that you can still create a rangeproof so that the transaction will be accepted.

Valgrind failure: https://cirrus-ci.com/task/6618538872930304?logs=cat_tests_log#L11

Oops -- I forgot to initialize my msg array before encoding it.

Squashed the two commits in this PR; added another which fixes all the memcmp instances in the secp-zkp modules.

tACK 5a40f3d99bbd879391a3fb3c038a6d49ec01bc03


lokijs.org has no content relevant to lokijs?

Lokijs.org is linked from the documentation, however the website at that URL has no content specific to LokiJS. It seems to be a generic wordpress site about cloud computing.

Documentation link should be changed to the github repo as the .org domine got squatted.


AppRailAnchor: can't resize anchors using class override

Current Behavior
<AppRailAnchor class="w-16">
  <!-- .... -->
</AppRailAnchor>

this is not working because the size w-full is applied to the child div, so changing the parent anchor has no effect.
Expected Behavior
Changing the size of the anchor should be possible using the class override.
Steps To Reproduce
No response
Link to Reproduction / Stackblitz
No response
More Information
Discord issue
Workaround:
<AppRailAnchor href="/" class="[&>*:first-child]:w-16">
  <!-- .... -->
</AppRailAnchor>

Also as mentioned in the Discord issue, some users might want to change the aspect ratio of the tiles and anchors, so maybe providing an AspectRatio prop would be a nice addition.


Awan

This is a bash script to install prezto . It is a part of my dotfiles in which I have zprezto as submodule and once I clone it recursively and run this script, it install all other files with prezto. I'm gonna remove other enteries so it would become only prezto related.

Thanks for your contribution. Do you still plan on cleaning this up? It looks like there's quite a bit of personal changes in here.


Eve displaying data is interrupted quite often

Hi,
Great plugin! One thing/question, and  can't find out if it is because of my setup, or maybe something in the plugin.
Started using the plugin a week or 2 ago, the data displayed was interrupted 2 times a day (showing No Data for * Hours/Days.
Uninstalled Domoticz from my Pi as it was redundant and then the graph was moe stable, until last Friday. Rebooted Homebridge service, no solution. Rebooted my Pi, no solution.
Searched the closed issues and came across you mentioning to empty the cachedAccessories . Did that from the Homebrige wegui, restarted the Hombridge service et voila, working again. Can this emptying be automated in the plugin? Like empty after 72 Hours?
Other small thing is that I read you have your Electricity and Gas  accessory in Eve "powered ON" while mine shows my devices as "powered OFF", how can I switch to permanently on for both?

Can this emptying be automated in the plugin?

No.  The history entries are recycled, so it doesn't grow indefinitely.  I'm not sure what causes the corruption of the entries (maybe just a bad shutdown), nor how to recognise it.  Would have to see a couple of cachedAccessories files to analyse.

I read you have your Electricity and Gas accessory in Eve "powered ON"

Not sure where you read that, but with the outlet settings, these accessories are exposed as Outlet with power off.  If you set it on, it switches back to off after 0.5 seconds.  Home doesn't like disabling setting on, and the whole purpose of outlet was to pacify Home.

Hej, thanks for the swift response. Got the ON impression from one of your replies in an earlier  issue
since I emptied the cachedAccessories folder via the Homebridge webgui, and restarted my Pi it seems to run more stable and no No Data gaps in the graphs.

Got the ON impression from one of your replies in an earlier issue

That was probably a screenshot from a pre-released proof-of-concept version.


Release Google.Cloud.PubSub.V1 version 2.2.0

Changes in this release:

Commit 0ce91bb: feat: Enable server side flow control by default with the option to turn it off (see below)
Commit 0790924: fix: Add gRPC compatibility constructors
Commit 0ca05f5: chore: Regenerate all APIs using protoc 3.13 and Grpc.Tools 2.31

As of this release, flow control settings are enforced at the client and are also sent to the Cloud Pub/Sub server but not enforced on the server side yet. Server side flow control is on track to be enabled by the 2nd week of December 2020. Users that face issues with server side flow control can disable it by setting SubscriberClient.Settings.UseLegacyFlowControl# to true which will result in the enforcement of client side flow control only.

Created release for Google.Cloud.PubSub.V1-2.2.0


Fix signature::canonical_uri to produce invalid uri

Fixes #1700
CHANGELOG:

Fix signature::canonical_uri to produce invalid uri when Region::Custom::endpoint has / as path (eg. localhost:5555/).

@iliana @benesch would you be so kind to look at this?


Core debug level setting in English

Hello,
You instructions are clear, except the core debug level is shown with what looks like a Chinese character that is hard to translate. Can you add the setting in English?

Go to https://github.com/Xinyuan-LilyGO/T-Display-S3
Under "Quick Start" there is a list of settings.
The "core debug level" setting is a Chinese character.
Thanks!

I'm sorry that this character bothers you. I reproduced this interface here.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.12.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=81c4d1d83f88e15b26f4522a35cba6ffd8c5dfdd"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "81c4d1d83f88e15b26f4522a35cba6ffd8c5dfdd",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net:sfc: fix non-freed irq in legacy irq mode\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.12.11 by commit 81c4d1d83f88e15b26f4522a35cba6ffd8c5dfdd. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001015


Bugfix stop infinite resync

What's in this PR?
If we fail a repository resync completely (after 4 getrepopage failures) we must stop retrying the same repo.
This stops us trying to sync invalid repos forever.

In side getNextTask it has this line if (subscription.repositoryStatus !== "complete") {, so the change in this PR ( of setting syncStatus to FAILED ) won't prevent the app from re-pickup the repository task again?

I still don't think this is the issue. The task repository shouldn't fail unless the app was uninstalled or something since it's just looping through the repository list given to it. This logic hasn't changed since implemented 6 months ago. I think it's a side effect of something else.
Nonetheless, if it means not blocking, I'm happy to approve, but I don't think it's the root cause.

Agree, its not root cause, but it clean out the backfill. I do wonder if the installations i kicked off are uninstalled? Do we remove the entry on uninstall?


Paired results on test dataset

Has anyone inferenced the paired model on the test dataset and willing to share the output via Dropbox or similar?

Hi,
When I run the TF.py in the "[Online_Demo_Models]_Deep-Photo-Enhancer/LPGAN_exp_G3_736" file, I face this error:
Shapes (2, 1, 32, 32, 128) and () are incompatible
in line: netG_test_output1 = model(netG, test_df.input1, False, netG_act_o, is_first=True)
Would you mind helping me with it? Thank you in advance.


model load error when the module is defined with extrat positional auguments

🐛 Bug
https://github.com/PyTorchLightning/pytorch-lightning/blob/0.7.5/pytorch_lightning/core/lightning.py#L1552
When using ddp, this function will throw an error if the pl module is defined with extra positional arguments.
To Reproduce
Steps to reproduce the behavior:

define a pl module with extra positional arguments:
'''
class My_Classifier(pl.LightningModule):
def init(self, model_params: dict, train_params: dict) -> None:
'''

Train the model with ddp

At some point, a model reloading is triggered

Then, this function will have an error:

https://github.com/PyTorchLightning/pytorch-lightning/blob/0.7.5/pytorch_lightning/core/lightning.py#L1552
model = cls(*model_args, *args, **kwargs)
TypeError: init() missing 2 required positional arguments: 'model_params' and 'train_params'
Expected behavior
Either prevent using extra positional arguments when using ddp, or support more args others than  hparams
Environment

CUDA:
- GPU:
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- Tesla V100-SXM2-32GB
- available:         True
- version:           10.1
Packages:
- numpy:             1.18.1
- pyTorch_debug:     False
- pyTorch_version:   1.4.0
- pytorch-lightning: 0.7.5
- tensorboard:       2.1.1
- tqdm:              4.45.0
System:
- OS:                Linux
- architecture:
- 64bit
-
- processor:         x86_64
- python:            3.7.7
- version:           #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019

@cmpute mind have a look?

In my understanding, right now the trainer must have no argument or only hparam argument except for other arguments when it's used in DDP, because lightning only handles the hparams when loading temporary checkpoint: https://github.com/PyTorchLightning/pytorch-lightning/blob/e6b34ef90d5f3eac70154b305b476614a64f1981/pytorch_lightning/trainer/distrib_data_parallel.py#L400
To solve this problem, constructor parameters in lightning module should also be saved into the temporary checkpoint and loaded when DDP reconstruct the module. But this will be an additional feature. My personal reference is to wrap all parameters needed into the hparam argument.

I also got stuck in the similar issue.. I was trying to make customizable batch size for train/test/val dataloaders among other things(the goal was to reuse core code with different training setups) so that I can re-use the code with minimum changes to core training code.
Although not a clean solution, I ended up using setters to set these custom configs, and calling them before Trainer.fit(my_model)
`
class MyModel(LightningModule):
def init(self):
<your_code_here>
def set_train_batch_size(self, train_batch_size):
    self.train_batch_size = train_batch_size

#Now use this self.train_batch_size in your train dataloader
#your model loading code will look simpler now
model_1 = MyModel.load_from_checkpoint(<path_to_the_checkpointed_model>)
`
Please let us know if there is better way of doing this.

you can add more arguments to the load call... take a look at the docs

load
sorry, should have given more information, my load call is encapsulated in the prepare_data()

my goal is to have a Model class which i can create different instances of, and then use different configs such as datasources/batchsize etc among others, without changing the Model class, but controlling these things when i initialize the object form the class


Treemap window resize

Hello, I´ve created a html which has radiobuttons to control the d3plus treemps, according to the selection it should show a graph, it works ok, the problem is when the size of the screen changes, when it happens the graphic which is not selected is not showed completely. Anyone could help me?.  The code is the following:
CSS:
.cont{
margin: 0;
bottom: 0;
position: absolute;
top: 0px;
left: 0px;
width: 100%;
height: inherit;
}
html:

2016
2015

JS:
d3.csv("todos.csv", function(error, data) {
data.forEach(function(d){
d.id = d.id;
d.d2016 = +d.d2016;
d.color = d.color;
});
sdata = data;
new d3plus.Treemap()
.data(sdata)
.groupBy(["id"])
.sum("d2016")
.select("#viz")
.render();

new d3plus.Treemap()
.data(sdata)
.groupBy(["id"])
.sum("d2015")
.select("#viz1")
.render();

});
function switchChart(cont){
containers = document.getElementsByClassName("cont");
for (i = 0; i < containers.length; i++) {
containers[i].style.display = 'none';
}
document.getElementById(cont).style.display  = 'block';
};

I've created the JSFiddle (https://jsfiddle.net/ranucame/tLcge8bq/21/) but
it soesn't work, I tried several ways but without any result.
Regarding the use of .sum(), it could be something like this:
.sum(switch)
function switch(cont){
if(cont=="2016"){ return "d016"};
if(cont=="2015"){ return "d015"};
}
Thanks
On Mon, Aug 27, 2018 at 1:25 PM Dave Landry<EMAIL_ADDRESS>wrote:

@ranucame https://github.com/ranucame would you mind creating a JSFiddle
http://jsfiddle.net/ showing the problem? From the first look at your
code, it looks like you're creating multiple charts with almost identical
settings. Why not just create 1 chart and update the .sum( ) method in
the switchChart function?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexandersimoes/d3plus/issues/651#issuecomment-416321075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aovu1pD2bznm5gxs38zOzjRv-yU30Uwtks5uVDmWgaJpZM4WNGS6
.

Check out this solution: https://jsfiddle.net/tLcge8bq/53/

Thank you so much. An aditional question, for this treemap, how can modify
the size of the legend and remove the texts?
Sorry but I am new using D3plus.
On Tue, Aug 28, 2018 at 9:14 AM Dave Landry<EMAIL_ADDRESS>wrote:

Check out this solution: https://jsfiddle.net/tLcge8bq/53/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexandersimoes/d3plus/issues/651#issuecomment-416599896,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aovu1rgeITNSR7OYnBEAQ8LQjurGrGi9ks5uVVBTgaJpZM4WNGS6
.

The .legendConfig method provides access to all the methods for the Legend class: https://jsfiddle.net/tLcge8bq/55/
Full documentation here: http://d3plus.org/docs/#Legend

@ranucame you just need to define the .time() variable. In order to use the internal timeline behavior, d3plus expects a different data point for each year (not individual keys in the same object). So given data that looks like this:
var data = [
  {id: "alpha", value: 4, year: 2016},
  {id: "alpha", value: 5, year: 2017},
  ...
];

You would set this method to tell d3plus about which key corresponds with time:
.time("year")