Unable to deploy management zone

Describe the bug
Management zone deployement is not possible. There is only a minor tag change on the new file version.
Issue happens with both 1.47.3 and 1.51.0 providers
To Reproduce
Steps to reproduce the behavior:

terraform init (works)
terraform plan (works)
terraform apply (
See error

Expected behavior
Management zone deploys correctly
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Win11

Additional context
Error message with TF_LOG:TRACE:
2024-03-04T14:19:48.777+0100 [TRACE] provider.terraform-provider-dynatrace_v1.47.3.exe: Calling downstream: tf_provider_addr=provider tf_resource_type=dynatrace_management_zone tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-sdk/v2@v2.25.0/helper/schema/resource.go:846 @module=sdk.helper_schema tf_req_id=247a51eb-8ec1-9438-1b04-c6752c06572c timestamp="2024-03-04T14:19:48.776+0100"
2024-03-04T14:19:48.864+0100 [TRACE] provider.terraform-provider-dynatrace_v1.47.3.exe: Called downstream: tf_provider_addr=provider tf_rpc=ApplyResourceChange @module=sdk.helper_schema tf_req_id=247a51eb-8ec1-9438-1b04-c6752c06572c tf_resource_type=dynatrace_management_zone @caller=github.com/hashicorp/terraform-plugin-sdk/v2@v2.25.0/helper/schema/resource.go:848 timestamp="2024-03-04T14:19:48.864+0100"
2024-03-04T14:19:48.868+0100 [TRACE] provider.terraform-provider-dynatrace_v1.47.3.exe: Received downstream response: diagnostic_error_count=1 tf_rpc=ApplyResourceChange tf_provider_addr=provider tf_req_id=247a51eb-8ec1-9438-1b04-c6752c06572c @module=sdk.proto tf_resource_type=dynatrace_management_zone @caller=github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/tf5serverlogging/downstream_request.go:37 diagnostic_warning_count=0 tf_proto_version=5.3 tf_req_duration_ms=105 timestamp="2024-03-04T14:19:48.868+0100"
2024-03-04T14:19:48.868+0100 [ERROR] provider.terraform-provider-dynatrace_v1.47.3.exe: Response contains error diagnostic: @module=sdk.proto diagnostic_severity=ERROR tf_provider_addr=provider tf_resource_type=dynatrace_management_zone tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/diag/diagnostics.go:55 diagnostic_detail="" diagnostic_summary="Could not map JSON at 'rules[4].type' near line 1 column 1146" tf_req_id=247a51eb-8ec1-9438-1b04-c6752c06572c tf_proto_version=5.3 timestamp="2024-03-04T14:19:48.868+0100"
TF File content:
cd_comfy.tf.txt

Hi @gkdevopsmon,
Hmm, that's interesting. I'm unfortunately not able to replicate the issue with the TF file that you provided as the apply succeeds in my environment.
Can we try a couple of things? The dynatrace_management_zone resource used in your example is actually deprecated, can you try with the dynatrace_management_zone_v2 resource? I've included what should be the v2 equivalent resource below.
resource "dynatrace_management_zone_v2" "CD_comfy" {
  name = "CD_comfy"
  rules {
    rule {
      type    = "ME"
      enabled = true
      attribute_rule {
        entity_type                 = "SERVICE"
        service_to_host_propagation = true
        service_to_pgpropagation    = true
        attribute_conditions {
          condition {
            key      = "SERVICE_TAGS"
            operator = "EQUALS"
            tag      = "app-id:APP-119728"
          }
        }
      }
    }
    rule {
      type    = "ME"
      enabled = true
      attribute_rule {
        entity_type = "CLOUD_APPLICATION_NAMESPACE"
        attribute_conditions {
          condition {
            case_sensitive = true
            key            = "CLOUD_APPLICATION_NAMESPACE_NAME"
            operator       = "CONTAINS"
            string_value   = "comfy"
          }
        }
      }
    }
    rule {
      type    = "ME"
      enabled = true
      attribute_rule {
        entity_type = "CLOUD_APPLICATION"
        attribute_conditions {
          condition {
            case_sensitive = true
            key            = "CLOUD_APPLICATION_NAME"
            operator       = "CONTAINS"
            string_value   = "comfy"
          }
        }
      }
    }
    rule {
      type    = "ME"
      enabled = true
      attribute_rule {
        entity_type               = "PROCESS_GROUP"
        pg_to_host_propagation    = true
        pg_to_service_propagation = false
        attribute_conditions {
          condition {
            key      = "PROCESS_GROUP_TAGS"
            operator = "EQUALS"
            tag      = "app-id:APP-119728"
          }
        }
      }
    }
  }
}

If you continue to experience issues, can you enable the following environment variables? This will dump the HTTP traffic and debug information into the files terraform-provider-dynatrace.log, terraform-provider-dynatrace.http.log and terraform-provider-dynatrace.http.err.log. Please feel free to send the logs to<EMAIL_ADDRESS>DYNATRACE_DEBUG=true
DYNATRACE_HTTP_RESPONSE=true
DYNATRACE_LOG_HTTP=terraform-provider-dynatrace.http.log

Looking forward to your response!

Hi @kishikawa12 ,
Thanks a lot for your response. I have tried to deploy the code you have provided but unfortunately it did't work.
I will provide the requested log files.
╷ │ Error: Management zone with this name already exists. Please provide a different one. │ │   with module.management_zone.dynatrace_management_zone_v2.CD_comfy, │   on management_zone\cd_comfy.tf line 2, in resource "dynatrace_management_zone_v2" "CD_comfy": │    2: resource "dynatrace_management_zone_v2" "CD_comfy" { │ ╵
2024-03-05T09:28:45.991+0100 [ERROR] provider.terraform-provider-dynatrace_v1.47.3.exe: Response contains error diagnostic: diagnostic_severity=ERROR tf_resource_type=dynatrace_management_zone_v2 tf_rpc=ApplyResourceChange @caller=github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov5/internal/diag/diagnostics.go:55 tf_proto_version=5.3 diagnostic_detail="" diagnostic_summary="Management zone with this name already exists. Please provide a different one." tf_req_id=742e12a6-b9ec-7f0b-5bcd-a86c30c68800 @module=sdk.proto tf_provider_addr=provider timestamp="2024-03-05T09:28:45.991+0100"
Best regards,
Geza

Hello @gkdevopsmon,
The most recent error you're getting just originate from the fact, that your Dynatrace Environment already contains a Management with the name CD_comfy.
Dynatrace (to be more specific: the REST API) therefore rejects the creation.
And Terraform (because it isn't aware of its existence) tries to create it.
Could you delete the Management Zone using the WebUI before running terraform apply?

Hi @Dynatrace-Reinhard-Pilz ,
Thanks for the feedback.
Strange enough after setting the enviroment variables I was able to deploy the new config.
Thanks for your help.
Best,
Geza


seaweedfs: 3.65 -> 3.66

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/seaweedfs/seaweedfs/releases.
meta.description for seaweedfs is: Simple and highly scalable distributed file system
meta.homepage for seaweedfs is: https://github.com/chrislusf/seaweedfs
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.66 in filename of file in /nix/store/l6r5d8l41yz57s37s10paql31s2v8cn4-seaweedfs-3.66

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

seaweedfs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/l6r5d8l41yz57s37s10paql31s2v8cn4-seaweedfs-3.66 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A seaweedfs https://github.com/r-ryantm/nixpkgs/archive/2d4ae69fd5d477f3eba336086c4abcb1d5050bc3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2d4ae69fd5d477f3eba336086c4abcb1d5050bc3#seaweedfs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/l6r5d8l41yz57s37s10paql31s2v8cn4-seaweedfs-3.66
ls -la /nix/store/l6r5d8l41yz57s37s10paql31s2v8cn4-seaweedfs-3.66/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

seaweedfs

Maintainer pings
cc @azahi @cmacrae @wozeparrot for testing.

Result of nixpkgs-review pr 309556 run on x86_64-linux 1

1 package built:

seaweedfs


Fix poetry secondary source bug

Fixes #4026 (hopefully).
PyprojectPreparer made sure to get all of the originally-defined Poetry sources (with their original names), and any sources configured based on python-index sources in Dependabot's config (with short random hex strings as names).
However, it then used these to generate poetry.lock without trying to combine them, so packages in private repos would end up with the short random hex string as their reference in poetry.lock, which would not work.
This PR merges any configured sources into the originally-defined Poetry sources in PyprojectPreparer.replace_sources, so that the final sources should have the original name they had in pyproject.toml.

Please let me know if there are any code style or other changes you'd like made to this. Ruby isn't my main language, but I'm happy to change whatever's needed.

Is this something that I should address with more tests, or is it something that you'd have to run yourself?

@isobelhooper apologies for the slow response on this! It would be great to add a few tests to python/lib/dependabot/python/file_updater/poetry_file_updater.rb, as we call the changed code from there. We want to make sure that the updated files do not contain hard-coded secrets after that code has been called. If you happen to have a project I could manually test this against, that'd also be much appreciated!

Is this something that I should address with more tests, or is it something that you'd have to run yourself?

@isobelhooper apologies for the slow response on this! It would be great to add a few tests to python/lib/dependabot/python/file_updater/poetry_file_updater.rb, as we call the changed code from there. We want to make sure that the updated files do not contain hard-coded secrets after that code has been called. If you happen to have a project I could manually test this against, that'd also be much appreciated! I can set one up if not though

I'm afraid I don't have a project I could test this against - setting one up would be much appreciated!
I had a try at writing tests for poetry_file_updater.rb using Webmock for the PyPI responses, but ran into the problem that the updater calls out to poetry update and Webmock can't mock out the requests that it makes. A test project would be good for this.

Apologies for the slow response on this - I've pushed another commit with a test in python/lib/dependabot/python/file_updater/poetry_file_updater.rb that will, unfortunately, currently not work. It relies on having a Python repository set up to allow username / password test / test and that hosts the luigi package.
I did this using pypiserver and following the instructions in https://pypi.org/project/pypiserver/ to set up a server running on localhost:8080 that serves no local packages and instead redirects all queries to pypi.org (which would then serve the luigi package). My test setup just ran pypiserver as a separate process, but there's a Docker image that could be used to do the same.
The new test should pass once there's a Python repository like this (with auth credentials) that it can access - though I wouldn't expect it to be on localhost, and the credentials could be passed in as secrets

Would it be possible for the Dependabot CI to either set up a temporary Python repository like this just for testing, or use an internal private Python repository?

I'm not sure, both approaches seem fairly brittle and involved 🤔 is there a way that we could mock out those calls instead?

Would it be possible for the Dependabot CI to either set up a temporary Python repository like this just for testing, or use an internal private Python repository?

I'm not sure, both approaches seem fairly brittle and involved 🤔 is there a way that we could mock out those calls instead?

Unfortunately those calls are made as part of the poetry update command that's called by PoetryFileUpdater.updated_lockfile_content_for - we could mock out how Poetry updates lock files, but that also seems brittle and involved.
I'm thinking that it might be possible to move the test to a little earlier in the file updating, and avoid having to make an external call at all.
Since the only thing that updated_lockfile_content_for changes about the lockfile once Poetry has generated it is the hash, my thought is that if we make sure that the project file from PoetryFileUpdater.prepared_pyproject (which is then used to generate the lockfile) doesn't contain any credentials, then any leaking of credentials into the lock file would be a Poetry bug.
I'll have a go at making a test for PoetryFileUpdater.prepared_pyproject in the case where we have auth credentials.

Thanks for all your work on this!


BPMSPL-202 - REST Query APIs with POST method

Functionality to invoke REST Query APIs with POST method.
Tested here: https://github.com/mrietveld/kie-tests/commit/2a012b58416091f6585150932b04397d32ba9c59 (Waiting for a PR (commit before this) to push it to the blessed repo).

Marco, isn't this sort of abuse of REST API to use POST for queries (which are essentially read operation that should be implemented as GET)? I see this as similar thing as we have the execute end point that does not really fit into REST api.
Wouldn't it be better to somehow encrypt the parameters instead of using post? I read the jira and security issue has some value but the other with xml for staring process does not belong here - start process is already POST so it should always use body for the data.

Rescinding this PR because of Maciej's comment: I indeed do not want to extend the REST API in this way.

Hmm.. actually, after rereading the BPMPSL issue, there are 2 valid issues:

Even if you use HTTPS/SSL, using GET means that the query parameters are in the URL and thus are exposed.

POST allows the user to post a far larger content (with regads to query parameters) than with GET.

@mswiderski both of these points are valid with regards to the Query API. I agree with your points here, but given that both points are valid (and that I also think that security is an important issue), I'm thinking of going through this anyways..

Even if you use HTTPS/SSL, using GET means that the query parameters are in the URL and thus are exposed.

is this really valid for REST operations? Usually you don't expose REST endpoints in like a browser URL bar or similar. You either use JavaScript (like XmlHttpRequest) or some other type of client library that do not expose the URL any way.

POST allows the user to post a far larger content (with regads to query parameters) than with GET.

that's true but what is the use case to send big amount of data when quering for items via given end point? Isn't the idea of the GET endpoints to return (possibly big) data?

Closing this pull request, since I don't think we want to implement this (because using POST in this case is an anti-pattern).


Calling auto discovery the second time returns nothing

Hello, I am working on a client that runs on devices with very poor internet connection. This is why I am calling the wapi.js multiple times in order to ensure it's executed at some point.
However, in 20% of the cases, users report they've had to click my interface's refresh button (causing the page in the background to reload and executing the wapi again).
The problem in my case is that if the wapi.js is executed too early, it will leave you with a half-complete Store (e.g. only containing .Conn) and then never refreshes again. How can I ensure it's complete?

After use the auto discovery, the webpack function “consumes” the included modules, so the code just run once. But the autodiscovery runs only when document is ready, I don’t know why the poor connection causes a problem in the load, because the event will be triggered only after full page load.

Hey, no idea why it fails after that but it does. Delaying the function call by a few seconds helps the case but it also makes everything slower.
Do you know of any other way to get this method to run twice?


List all accounts in the service

List All Accounts in the Service
As a regulatory agent
I need an API to list all customer accounts
So that I can audit accounts and ensure compliance
Details and Assumptions
The list should be paginated to manage large datasets.
Acceptance Criteria
Given the request for all accounts
When I access the list API endpoint
Then the system should return a paginated list of accounts


Nit: Unused import in document leaf element handler

Suggest for spring cleaning to handle the finding
flake8 → cvrf2csaf/section_handlers/document_leaf_elements.py:1:1: F401 'logging' imported but unused
Just remove line 1 stating:

import logging

@tschmidtb51: dont really understand in this issue, that removing an unused libary from the imports is part of critical acceptance. Also observing addition of acceptance where the usage is questionable.

Not being part of the process, but in my experience the inclusion into acceptance depends on what is expected of code security as well as quality. Here, unused code has been removed. I know of companies where you only ship when all unused code is gone for good.

@cgi1: I just want to point out that subsection "Code Qualität" (5.1.3, page 14) of your tender mentions flake8 as one of the best practices...


Allowing a leading 0 to be entered to mm or dd segment of Date Field

🙋 Feature Request
Allowing a leading 0 to be entered to the date field mm or dd segment.
🤔 Expected Behavior
Users would be able to enter 01, or 02, or 03, ... 09 to the mm or dd segment without it get shortened to 1, 2, 3, ...9.
😯 Current Behavior
The leading 0 will be removed if user type in 01, or 02, or 03, ...09 to mm or dd segment
💁 Possible Solution
I am not sure because it looks like useDateSegment process user input value as a number. And I think JavaScript don't consider 01 to be a number so that why's it only comes back as 1 without the leading 0
🔦 Context
I am using the placeholder mm/dd/yyyy for the date field component and thought it'd be misleading to the users if only one character get display for value that is less than 10 inside mm or dd segment.
💻 Examples
Found this example from mui date field that allow entering the leading 0 in the mm or dd segment. TBH, I use react aria because you guys keep great documentation on how to use your components/hooks.
🧢 Your Company/Team
N/A
🎁 Tracking Ticket (optional)
N/A

Whether the leading zero is expected or not depends on the locale:
new Intl.DateTimeFormat('en-US').format(new Date())
> "3/23/2023"

new Intl.DateTimeFormat('fr-FR').format(new Date())
> "23/03/2023"

We could add an option to override the formatting but it might result in improper formatting in some languages/regions if it were hard coded.

forgive my ignorance, can you help me understand more on why locale such as 'en-US' displays 3 for March instead of 03?

Would like more info on this as we

Whether the leading zero is expected or not depends on the locale:
new Intl.DateTimeFormat('en-US').format(new Date())
> "3/23/2023"

new Intl.DateTimeFormat('fr-FR').format(new Date())
> "23/03/2023"

We could add an option to override the formatting but it might result in improper formatting in some languages/regions if it were hard coded by an app.

Is there a way to change the locale? I'm having some trouble finding it in the documentation

That would be a question for CLDR, we let the browser format the date, as shown in @devongovett's examples in the last comment. https://cldr.unicode.org/translation/date-time


pylhc submitter pages

Add a separate category and pages for the new pylhc-submitter.
Fixes #43  and #44

Previous commit removes the description + API details parts of the files and links to the (updated after merging https://github.com/pylhc/submitter/pull/11) API doc pages for this.
These refer to the new content of this PR for guides & more info.


 Here are the errors in the console I got when trying to publish a note that included a lot of pictures:

Not sure what the right fix is for this. Should images be linked instead of encoded? Tough to tell.

Better late than never: @uroybd recently improved this by instead uploading images separately in to its own folder, and referencing them in the note. This problem should now be solved 🎉


Add bytesrepr codec to muxink

This PR adds the bytesrepr codec to muxink crate.
It also adds unit tests to the bincode codec and fixes some minor issues in it.
Closes https://github.com/casper-network/casper-node/issues/3198

bors r+


Fix a bug where calling API with wrong HTTP method to check security …

…enabled

Thanks, @minwoox !


Bug: difficult to properly set axes ranges

bug: it is difficult to set axis range under graph … for example, in UMSP "Observation date" often loads as 0002 or 0201, etc rather than 2014 … perhaps only when loading graph reduces bandwidth?

I think an image would help explain the issue.


⚠ WSINGRESOS - RECIBOPAGO has degraded performance

In 8647d80, WSINGRESOS - RECIBOPAGO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsRecibosPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 6232 ms

Resolved: WSINGRESOS - RECIBOPAGO performance has improved in 07703ec after 10 minutes.


feature: code refactoring tools

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
Are there currently tools available for code refactoring within Lazyvim?
Describe the solution you'd like
A plugin like integrated like: https://github.com/ThePrimeagen/refactoring.nvim
Describe alternatives you've considered

Additional context
No response

no, but as you found, you can use that plugin (which is not that great to be honest).
Most lsps provide refactoring through code actions. <leader>ca


[Feature Request] Types export

It would be great if we could use some types in our app like for example SubscriptionObject, if we want to store a user subscription in a class.

I would also love it, I'm creating webhooks and would love to reuse already defined types. I already did that with lemonsqueezy.ts
If you need help with implementing this, let me know

While the types are not exported from the package, I'm deriving them from the client methods.
Here are some examples:
const lemonClient = new LemonSqueezy(/** */);

type SubscriptionResponse = Awaited<ReturnType<typeof lemonClient.getSubscription>>;
type OrderResponse = Awaited<ReturnType<typeof lemonClient.getOrder>>;
type SubscriptionInvoicesResponse = Awaited<ReturnType<typeof lemonClient.getSubscriptionInvoice>>;

Types are now exported with v2.0.0.


[KYUUBI #2361] [Improvement] Configuring Trino Engine heap memory and java opts

Why are the changes needed?

Configuring Trino Engine heap memory and java opts
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #2387 (e8ef7f6) into master (b8d04af) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #2387      +/-   ##
============================================
+ Coverage     62.67%   62.73%   +0.06%
  Complexity       69       69
============================================
  Files           360      360
  Lines         17116    17136      +20
  Branches       2310     2311       +1
============================================
+ Hits          10728    10751      +23
+ Misses         5379     5378       -1
+ Partials       1009     1007       -2

Impacted Files
Coverage Δ

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
96.42% <100.00%> (+0.18%)
:arrow_up:

...ache/kyuubi/engine/trino/TrinoProcessBuilder.scala
92.50% <100.00%> (+1.59%)
:arrow_up:

.../org/apache/kyuubi/operation/KyuubiOperation.scala
66.66% <0.00%> (-1.34%)
:arrow_down:

...ache/kyuubi/operation/KyuubiOperationManager.scala
96.29% <0.00%> (+1.85%)
:arrow_up:

...rg/apache/kyuubi/engine/trino/TrinoStatement.scala
71.26% <0.00%> (+2.29%)
: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 b8d04af...e8ef7f6. Read the comment docs.

thanks, merged to master


[SMALLFIX]In alluxio/client/block/AlluxioBlockStore.java, changing    private Random mRandom; to    private final Random mRandom;

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17518/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.JournalShutdownIntegrationTest.multiMasterJournalStopIntegration
Test FAILed.


Using -c prevents CNAME configuration from being restored

Not sure what's going on, but on a fresh pihole install, using the -c option will result in seemingly everything being restored except CNAME configurations. Lemme know if you need more info.
Thanks for this utility!

This seems to only happen on a fresh install, for some reason - if I run pihole_restore after that, without the '-c', the CNAMEs are restored, and after that, running it again with -c works as expected (table cleared, CNAMEs restored).

Hey @bdruth , sorry I've been away from this for a while. Let me check and fix this, but it'll take a couple of weeks because of some life events.

No rush! Thanks for looking into it!!

reproduced


Use hard links for intra-page navigation

Use hard links for intra-page navigation:

Player titles
Tournament event matches
...

Completed


Add support for configurable Histograms in all statistic views

The Analysis view allows to configure custom Histograms. It would be useful if the user could also add custom Histograms to other staistic views as the User view or status view

Merged


<EMAIL_ADDRESS>Update to 2.6.0 and fix autoupdate url

Since the binary releases URLs changed on 2.4.x, the autoupdate url field was properly fixed. After running .\bin\checkver.ps1 the version and its hash were automatically updated as well.

[x] I have read the Contributing Guide.

/verify


UI error when "database not found"

This is happening on v0.9-RC9.
See screenshot for visual support.

It looks like this is a result of new headers being sent after they were already written. I think #1985 has solved this, so I'm closing it out.


Constraints

Does anyone has a constraints example  ?
I have tried HOSTNAME|UNIQUE to deploy on every host, it didn't work.
"constraints": [
  [
    "hostname",
    "UNIQUE"
  ]
]

I am trying to figure out how should the RACK attribute be used :
"constraints": [
  ["rack", "EQUALS", "rack-[1-2]"],
],

Does anyone has a link that explain this to share with me ?

I have the same difficulty, when I am using constraints my job is stuck in queued state with Log message: Insufficient resources (Needed: [cpus: 0.05 mem: 10.0 disk: 10.0], Found: [cpus: 0.97 mem: 152.0 disk: 3962.0]

Did you define the attributes on the mesos slaves where you intended for the jobs to run?
mesos-slave  --attributes="rack:rack1"

I have been facing the same problem. I did set the attributes of the slave. To reconfirm, this is what I found in the slave logs: Slave attributes: [ id=1 ]

Please specify the command line you are using to start the slave (and env vars) and the Chronos JSON job description object. Difficult to help without knowing ALL of the details.

I'm starting the slave with: sudo start mesos-slave
I have this in my /etc/mesos-slave/attributes: id:1
And this is my chronos job:
{
"name": "ConstraintTest",
"command": "mkdir /home/abc/chronostest",
"shell": true,
"epsilon": "PT60S",
"executor": "",
"executorFlags": "",
"retries": 2,
"owner"<EMAIL_ADDRESS>"ownerName": "",
"description": "",
"async": false,
"successCount": 0,
"errorCount": 0,
"lastSuccess": "",
"lastError": "",
"cpus": 0.1,
"disk": 256,
"mem": 128,
"disabled": false,
"softError": false,
"dataProcessingJobType": false,
"errorsSinceLastSuccess": 0,
"uris": [],
"environmentVariables": [],
"arguments": [],
"highPriority": false,
"runAsUser": "root",
"constraints": [
[
"id",
"EQUALS",
"1"
]
],
"schedule": "R/2016-03-30T12:47:00.000Z/PT24H",
"scheduleTimeZone": ""
}
Am I missing something??

Your setup appears to be correct and I've run this on my servers, finding the same thing. The job gets queued and never executed. I changed the attribute to all strings ["attrName" , "EQUALS", "valueStr"] and it queues and runs. Might be a bug with numeric equality.

Oh yes!
I tried it out with a string and it works.
Thanks a lot @planenutz


Add kRPC-MechJeb

Fixes #7963.
https://github.com/Genhis/KRPC.MechJeb/releases

ckan compat add 1.5

They're all still pre-releases; closing. Will re-open if that ever changes.

Apparently I signed up for release notifications!
https://github.com/Genhis/KRPC.MechJeb/releases/tag/v0.6.1

Apparently I signed up for release notifications!
https://github.com/Genhis/KRPC.MechJeb/releases/tag/v0.6.1

Needs ksp versions...

Needs ksp versions...

@Genhis, kRPC's latest release seems to only support up to KSP 1.5.1, going by the version file:

http://ksp-avc.cybutek.net/version.php?id=254

and the release notes:

and the forum thread:

This will present challenges for users wishing to install your mod. Is there another kRPC release out there for 1.8–1.11 that we don't know about? Alternately, has the author said somewhere else that it's supported on 1.11?

@Genhis, kRPC's latest release seems to only support up to KSP 1.5.1, going by the version file:

http://ksp-avc.cybutek.net/version.php?id=254

and the release notes:

and the forum thread:

This will present challenges for users wishing to install your mod. Is there another kRPC release out there for 1.8–1.11 that we don't know about? Alternately, has the author said somewhere else that it's supported on 1.11?

Unfortunately, kRPC does not officially support KSP 1.8 because the author is busy doing other projects. However, it works mostly without issues on newer versions. There are a few API parts which do not work but since the mod only provides remote procedures without major changes to the game, I think it should be fine.
There is an unreleased version 0.4.9 (https://github.com/krpc/krpc/pull/566) which adds support for KSP 1.8/1.9 but I don't think it will be released in the near future.

Unfortunately, kRPC does not officially support KSP 1.8 because the author is busy doing other projects. However, it works mostly without issues on newer versions. There are a few API parts which do not work but since the mod only provides remote procedures without major changes to the game, I think it should be fine.
There is an unreleased version 0.4.9 (https://github.com/krpc/krpc/pull/566) which adds support for KSP 1.8/1.9 but I don't think it will be released in the near future.

OK, we can still work with that as long as your users are prepared to figure out installation of kRPC. Some on the forum thread have already done so, so that may be less of a hurdle than I thought...

OK, we can still work with that as long as your users are prepared to figure out installation of kRPC. Some on the forum thread have already done so, so that may be less of a hurdle than I thought...

Thanks for contacting us and working out the kinks with the release!

Thanks for contacting us and working out the kinks with the release!

Well, you did most of it by yourself, even signing up for release notifications :D
Thank you for including my mod! I'll try installing it using CKAN to see if it works.

Well, you did most of it by yourself, even signing up for release notifications :D
Thank you for including my mod! I'll try installing it using CKAN to see if it works.


Unable to use published module

Hi there
Pretty cool project!! However, several issues make it unusable out-of-the box.

The version published on npm is not transpiled, you quickly run into unexpected import errors - typically one excludes the node_modules from transpiling in a real-world project
Trying to npm run build the downloaded version inside node_modules fails - because of some gh-pages file not found error

So I went ahead, made a fork and published it under my namespace. I changed the build setup from browserify to babel and already fixed several issues.
I'm really happy with the version I am using now.
If you'd like to revive the project, we can surely merge back via PR - otherwise I'd be happy if you give me full access here so I can maintain the project and deprecate my fork.
https://www.npmjs.com/package/@loopmode/dis-gui
https://github.com/loopmode/dis-gui
https://github.com/loopmode/dis-gui/blob/master/CHANGELOG.md

@loopmode That would be awesome. I've invited you to collaborate. Go ahead and take over.

@loopmode I've also added you as a collaborator to the npm repo.

great! thank you


Don't use roaming profile on Windows for cache files

Hi VSCode team,
Unfortunately VSCode uses user roaming profile for storing cache. It's this location:
c:\Users\USER\AppData\Roaming\Code\
I don't think this is in general a good idea as roaming profile really can be synchronized over the network to user's other computer profile. And it's quite a significant amount of data that can be transfered and also it has to be also inspected / compared for changes slowing down computer operation significantly.
Please consider using different location for cache, I'd suggest
c:\Users\USER\AppData\Local\Code\
I think for example extensions use of roaming profile could be ok, but for caching this leads to file system attrocities.
Thank you for your consideration.

Thank you for this post.
We use roaming profiles on a domain with more than 20,000 users, also often use remote VPN connections.
When you log on or log off to Windows (roaming profile synchronization), a large number of small files significantly slows down the loading of a user profile. In general, this load cannot be skipped unless you are a domain administrator. (Then it is possible to set skipping of some listed folders.)
For example, my folder: %appdata%\Code contains 3,447 files (size ~1 GB),
of which there are 2,482 files in the folders %appdata%\Code\Cache* and %appdata%\Code\Code Cache (size ~678 MB).
Following the previous post, please change the storage of temporary files in the folder:
%LOCALAPPDATA%\Code instead of %APPDATA%\Code
Thank you politely and have a nice day.

Looks like duplicate/part of #3884

/duplicate https://github.com/microsoft/vscode/issues/3884


Bisect improvement

This patchset is trying to ease up usage of syz-bisect tool and also implements storing results of bisection into files located in crash directory. This make syz-bisect more usable as standalone tool. Also syz-bisect results are now added into syz-report output. Example report is attached in this pull request.
syz-reporter.html.gz

Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

I found it quite hard to review because the change seems to do several unrelated things at the same time, do both some refactoring/preparatory changes (threading debugDir) and actual functional changes (saving files), and has some duplication (checking if debugDir is empty, MkdirAll).
It would be easier to review if it's split into smaller, cohesive changes.
E.g. handling empty kernel/syzkaller commits seems to be unrelated to everything else. Also can it be handled in tools/syz-bisect only? I think it would be better to handle it there rather than complicate actual production logic more.
For the tracing change I think the first step should be to add:
type DebugTracer interface {
	Log(msg string, args ...interface{})
	SaveFile(filename string, data []byte)
}

thread it everywhere as dt DebugTracer and add an implementation that can be initialized from (io.Writer, debugDir), or from (t *testing.T) or with no arguments as no-op tracer.
This would improve overall architecture, reduce duplication, reduce number of arguments we need to pass, make it easier to reuse it in other parts, etc.
It can also duplicate all log messages in debugDir/log file as a bonus. I think it will make later debugging much easier (currently we don't have trace log for bisections), and e.g. you save candidate configs during config minimization to both places, it won't be necessary anymore.

I found it quite hard to review because the change seems to do several unrelated things at the same time, do both some refactoring/preparatory changes (threading debugDir) and actual functional changes (saving files), and has some duplication (checking if debugDir is empty, MkdirAll).
It would be easier to review if it's split into smaller, cohesive changes.
E.g. handling empty kernel/syzkaller commits seems to be unrelated to everything else. Also can it be handled in tools/syz-bisect only? I think it would be better to handle it there rather than complicate actual production logic more.

I considered this originally, but then decided not add git repository handling into syz-bisect. Now as you pointed this out it seem being more correct solution.

For the tracing change I think the first step should be to add:
type DebugTracer interface {
	Log(msg string, args ...interface{})
	SaveFile(filename string, data []byte)
}

thread it everywhere as dt DebugTracer and add an implementation that can be initialized from (io.Writer, debugDir), or from (t *testing.T) or with no arguments as no-op tracer.
This would improve overall architecture, reduce duplication, reduce number of arguments we need to pass, make it easier to reuse it in other parts, etc.
It can also duplicate all log messages in debugDir/log file as a bonus. I think it will make later debugging much easier (currently we don't have trace log for bisections), and e.g. you save candidate configs during config minimization to both places, it won't be necessary anymore.

Ok, this sounds better approach. Another thought I originally had here is that this is not necessarily debugging stuff at all. Meaning bisection result (commit, fix, config) should be stored into workdir/crashes/ when bisection is done using syz-bisect tool. Then definition of  was problematic to me. I.e. is it the first observed crash or something else. To keep it simple I decided to continue using user given crashdir. Now as you pointed out we should write more generic debugging interface for this purpose I think the question whether this is debugging stuff at all is still valid. What do you think?
Maybe at some point we might want to trigger bisection from syz-ci/syz-manager without syzbot interaction?

I considered this originally, but then decided not add git repository handling into syz-bisect. Now as you pointed this out it seems being more correct solution.

 For git HEAD is the current commit.

I considered this originally, but then decided not add git repository handling into syz-bisect. Now as you pointed this out it seems being more correct solution.

 For git HEAD is the current commit.

Ok, I will do that. I was thinking that wouldn't be ok as other VCSs are not supporting it. Anyways this bisection is very much git feature...

Meaning bisection result (commit, fix, config) should be stored into workdir/crashes/hash when bisection is done using syz-bisect tool.
Maybe at some point we might want to trigger bisection from syz-ci/syz-manager without syzbot interaction?

I don't fully understand this part.
Everything that's really the end result of bisection (commit, config) is returned in pkg/bisect.Result type.
tools/syz-bisect can store these to files as necessary, syz-ci/syz-manager can do the same.
The other way around: files stored into debugDir are not captured/accessible via syzbot.
As I understand this: pkg/bisect.Result is for real results and debugDir is for anything that's intermediate details that are only useful in understanding what happened and why.
This scheme seems to work for syzbot, syz-ci/syz-manager and tools/syz-bisect. Or is there still any issue here?

Ok, I will do that. I was thinking that wouldn't be ok as other VCSs are not supporting it. Anyways this bisection is very much git feature...

You are right.
We could do:
// in pkg/vcs/vcs.go
const HEAD = "HEAD"

and then use this as an "abstraction" layer.

Meaning bisection result (commit, fix, config) should be stored into workdir/crashes/hash when bisection is done using syz-bisect tool.
Maybe at some point we might want to trigger bisection from syz-ci/syz-manager without syzbot interaction?

I don't fully understand this part.
Everything that's really the end result of bisection (commit, config) is returned in pkg/bisect.Result type.
tools/syz-bisect can store these to files as necessary, syz-ci/syz-manager can do the same.
The other way around: files stored into debugDir are not captured/accessible via syzbot.
As I understand this: pkg/bisect.Result is for real results and debugDir is for anything that's intermediate details that are only useful in understanding what happened and why.
This scheme seems to work for syzbot, syz-ci/syz-manager and tools/syz-bisect. Or is there still any issue here?

Yes, you are right here. I got somehow lost. Originally passed debug directory into kconfig to get identified config options stored into file. Using baseline and minimize config I should have done diff and use that. I didn't want to do that. Would it be ok to add those "suspected" configs into bisection result struct?

Would it be ok to add those "suspected" configs into bisection result struct?

Will it work for you if we start with just saving them into debugDir? This would be simpler for the rest of the system (no need to pass them around, etc).

Would it be ok to add those "suspected" configs into bisection result struct?

Will it work for you if we start with just saving them into debugDir? This would be simpler for the rest of the system (no need to pass them around, etc).

Yes, let's starti with that.

I considered this originally, but then decided not add git repository handling into syz-bisect. Now as you pointed this out it seems being more correct solution.

 For git HEAD is the current commit.

Ok, I will do that. I was thinking that wouldn't be ok as other VCSs are not supporting it. Anyways this bisection is very much git feature...

This is now addressed in latest patch set

I found it quite hard to review because the change seems to do several unrelated things at the same time, do both some refactoring/preparatory changes (threading debugDir) and actual functional changes (saving files), and has some duplication (checking if debugDir is empty, MkdirAll).
It would be easier to review if it's split into smaller, cohesive changes.
E.g. handling empty kernel/syzkaller commits seems to be unrelated to everything else. Also can it be handled in tools/syz-bisect only? I think it would be better to handle it there rather than complicate actual production logic more.

I did some more splitting of the patch set, please check.

For the tracing change I think the first step should be to add:
type DebugTracer interface {
	Log(msg string, args ...interface{})
	SaveFile(filename string, data []byte)
}

thread it everywhere as dt DebugTracer and add an implementation that can be initialized from (io.Writer, debugDir), or from (t *testing.T) or with no arguments as no-op tracer.
This would improve overall architecture, reduce duplication, reduce number of arguments we need to pass, make it easier to reuse it in other parts, etc.
It can also duplicate all log messages in debugDir/log file as a bonus. I think it will make later debugging much easier (currently we don't have trace log for bisections), and e.g. you save candidate configs during config minimization to both places, it won't be necessary anymore.

Please check my implementation.Hopefully it is what you expected.

Looks good to me. Thanks!


Native support for 'traveler' bit

Feature description
Provide a traveler bit in the batch upload, specific to an individual TEK. When this is set to true, mark that TEK as being present in all participating countries.

This could either do server-side fanout (preferred, but would break end-2-end batch signature)
Pass the traveler bit all the way through the batch, where downloaders can interpret this as "has been in my country" when the bit is true.

As an alternative, provide an endpoint where a fresh list of all participating countries can be obtained so that this fan-out can be done on the client side.
Problem and motivation
The Google exposure-notifications-server and the Apple+Google Exposure Notifications Express program does not give the granularity of individual countries a TEK may be been in, but instead has home country plus traveler (or not).
The current solution is for the exposure-notifications-sever EFGS integration to say that a given key is all participating countries - but any given server implementation has no way to know this. So our current integration will just send ALL ISO codes. This is lots of wasted bits over the wire and in the database, when a boolean captures the same item.
Is this something you're interested in working on
Yes

This is specifically what I'm worried out. With the "traveller only" roaming model, and the current need to do fan out client side, we will be passing a rather large list absent the ability to get it dynamically:
https://github.com/google/exposure-notifications-server/pull/1095/files#diff-0ae5d7acb5bc1b9b2a36d8a7e622155209a0dec7249e64d4c7cf1ac87b189738
I would be happy to submit PRs to add support for a "traveler" bit directly, greatly reducing the key size on the wire and in the database.

Thank you for the input, the underlying issue already generate a number of discussion between the participating countries. @SchulzeS will follow up the discussion.

Hello - any guidance here?
I'm happy to contribute PRs to add support for the Apple + Google roaming model (home country + traveler boolean)

Hello,
Currently we add all EU+EFTA countries listed on this page if you are using Traveller or OneEU/World Pattern:
https://ec.europa.eu/eurostat/statistics-explained/index.php/Glossary:Country_codes
Your idea with the traveller bit it is good for upload, but in the download not transparent, because there are mixed patterns in the keys. A new route to give out the existing onboarded members is under discussion.

I don't believe the traveler bit is any more or less transparent. It conveys the information that is known about the key in total, which is origin country of the key + traveler status.

The bit itself is not intransparent, but the meaning and the interpretation on the national backend side. If you set this bit, it means you are a traveller, but the country of interest interpretation didn't know where do you travel to. Of course we can define something like "bit means DE,NL,AT,... etc pp" But this is not very explizit. It avoids simply some mb of traffic. The same effect is also reached with a custom value in the visitiedCountries Array like "visitedCountries:[*]" which has the same effect. I saved some bytes but everyone needs to know what that means. This needs a lot of alignment between all attendees. Of course the insertion of explizit countries is not beautiful, but it's currently explicit and understandable. It can also turn back to a country of interest pattern without so much effort. (just country list is smaller) We must be very careful here. Would be the * solution also an acceptable way for you?

For the Apple+Google roaming model, traveler=true indicates that key may have been in all countries.
Having visitedCountrues:[*] could function the same way, but having to look for a sentinel value in an array would seem to be more error prone than an explicit boolean value.
We could work with either solution.

I'm gong to close this issue out. We're no longer requesting this change.


Tooling reorg

(As described in internal proposal document.)
Google.Cloud.Tools.sln ends up with 12 projects instead of the current 27.

Post-generation fix-up code was still using netcoreapp2.1, which now won't work with the SourceManipulation library. Updated and push an extra commit.


Translate "Not connected to the internet, please try again" to Chinese

Please help translate "Not connected to the internet, please try again". Shown when user taps a MagicLink but has no internet connection.
at: https://github.com/alpha-wallet/alpha-wallet-ios/blob/master/AlphaWallet/Localization/zh-Hans.lproj/Localizable.strings#L257

@bootingman

@bootingman bump.

sorry, missed Github issues, I updated it


the size of image in the model

If I would like to train my model, the size of image in the model need to be same?
If the size is different, will have any problem?
The light and position of object in image will affect the prediction?
Below is Example :

The size of the images do not need to be the same. ImageAI will automatically resize the images to a default value of 224 x 224.


Compare politeness histograms across different corpora

I have two different corpora, one of which has longer utterances than the other. If I want to compare the politeness histograms showed in this example, since it shows count/utterance, the corpus with longer utterances will have higher bars. What's the best way to mitigate this problem?

As a general note, proper length normalization is a broader NLP problem that harder than it might sound (I am not aware of a perfect solution).
Depending on your use case, here are a couple of imperfect solutions you might consider if the average length of the sentences are comparable between the two datasets (i.e., the difference in utterance length comes from the fact that in one dataset some utterances have more sentences, not from the fact that the sentences are longer):
a) subsample one sentence per utterance and use those to extract politeness features (and generate the plots).  You can do this easily in convokit this way: create a utterance metadata field that contains one (random) sentence of each utterance (call that "random_sentence").  Run the TextParser transformer by setting the input_field= random_sentence.  Run the Politeness transformer as before.
b) Macroaverage counts of politeness strategies at the sentence level.  This would involve writing a custom summarize function, but should not be that hard.
If the difference in utterance lengths comes from sentence length, not from number of sentences within each utterance, then you might try to compare apples and oranges.  One (again, imperfect) solution is to match each utterance in one corpus with an utterance in the other corpus that has a similar length.  In convokit you could do this by merging the corpora and then using the Pairer Transformer.
Of course, you will have to make sure to keep in mind the imperfections of the solution you choose when you interpret your results.  Good luck.
PS: Consider contributing the corpora you are working with to ConvoKit (since you already formatted them).


React on Rails v7 Breaking Changes

React on Rails v7 Breaking Changes

[ ] Upon startup, when the gem and npm versions don't match, an exception is thrown. Nobody is paying attention to warnings or errors being logged.
[ ] Generator and all examples changed to use webpacker_lite.
[ ] env_stylesheet_tag and env_javascript_tag deprecated for webpacker_lite apis.
[ ] 7.0 should still support putting assets through the asset pipeline. Places to check:

[ ]  assets precompile hook setup
[ ] rspec helper

CC: @udovenko @kaizencodes @robwise


Add another batch of missing struct keywords, Add definition for ImDrawVert

Hi, I added some other missing struct as well as a definition for ImDrawVert, which was missing under the CIMGUI_DEFINE_ENUMS_AND_STRUCTS define.
With those changes, I can successfully compile cimgui with Visual Studio.

Thank you very much


NormalModuleReplacementPlugin and lib files

trying to use NormalModuleReplacementPlugin for lib files that aren't exported.
question 1. is this supported? couldn't find it in documentation
example usage:
module.exports = function overrideModule(options){
    return new webpack.NormalModuleReplacementPlugin(
        new RegExp("^"+options.match.replace(/\./g, "\\.")+"$"), (resource) => {
            if (resource.context.includes(options.withinModule)) {
                resource.request = options.replacement
            }
        }
    )
}

overrideModule({
  match: "./ModuleFoo",
  withinModule: "@submodule/component/lib/another-component",
  replacement: path.join(modulePath, "ModuleBar")
})

works fine without /lib path

It looks like you just deleted our issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


Intergrating DrawerLayoutAndroid

Im wondering how one will go about using DrawerLayoutAndroid with this?
@jlyman @ericvicenti

Unfortunately DrawerLayoutAndroid has an imperitive API where we call methods on it to change internal state rather than a declarative API where we simply update props. So this isn't a super easy thing to do right now

i made it work by setting the navigator as a child of DrawerLayout and passing the method to toggle the drawer to the app toolbar, it could even be a app global state state, listen with a componentWillReceiveProps or something and toggle with a dispatch, there are a lot of ways to do this i believe, the way i did it works just fine.


Invalid right side of assignment issue

Hi, it is a long shot and you probably don't maintain this repo anymore ( given last update was 5 years ago ) I really like the way Laravel handles configuration and wanted to use this in my project. When I set the NODE_ENV to development I get an error in index.js line 21 where you assign env parameter to either process.env.NODE_ENV or environmentDetector.
var env = process.env.NODE_ENV = environmentDetector.detect(environments);

if you have a chance to take a look, much appreciated. I feel like something like this may quickly resolve and I can submit a PR if you like
var env = process.env.NODE_ENV || environmentDetector.detect(environments);

I will take a look at this over the weekend. Thank you.


Support for Alamofire Statistical Metrics?

From Alamofire documentation, DataResponse provided a lot of useful information.
Statistical Metrics
Timeline
Alamofire collects timings throughout the lifecycle of a Request and creates a Timeline object exposed as a property on all response types.
Alamofire.request("https://httpbin.org/get").responseJSON { response in
    print(response.timeline)
}

The above reports the following Timeline info:

Latency: 0.428 seconds
Request Duration: 0.428 seconds
Serialization Duration: 0.001 seconds
Total Duration: 0.429 seconds

Does RxAlamofire currently provides such API?

Currently we don't have a this option. I believe what you want is method that would return Observable<DataResponse> right?

@sergdort exactly! My project needs to time the API later... It would be super nice if RxAlamofire can return Observale that include all useful meta data.

@sergdort Any workaround for this? I have a different use case. The backend error message contains a key which is needed to identify what causes a validation error. http code is 400 but it's not enough. The error key provides additional details for a signup function, examples can be invalid_password, or email_already_exists.

I'm not 100% in-the-know of the structure of RxAlamofire but if you need a workaround, a simple wrapper function would assist here.
Something like this would work @gaplo917 @simoami
If I'll have some time I can look into how to add this into RxAlamofire after I learn the code there a bit :)
public func requestJSON(_ method: Alamofire.HTTPMethod,
                        _ url: URLConvertible) -> Observable<DataResponse<Any>> {
    return Observable.create { observer in
        let request = Alamofire.request(url)

        request.responseJSON { resp in
            observer.onNext(resp)
            observer.onCompleted()
        }

        return Disposables.create {
            request.cancel()
        }
    }
}

I added code to allow this directly from RxAlamofire but

I'm not sure of the naming (requestJSONData, as to indicate it returns a DataResponse)
I don't know Alamofire well enough to say if this is intuitive. Could anyone weigh in ? @kzaher

@freak4pc maybe just RxAlamofire.dataResponse? ¯\_(ツ)_/¯

@kzaher It comes specifically from responseJSON e.g.
Alamofire.request(...).responseJSON { resp in
 /// resp is DataRespnse<Any>
}

and also the naming convention across seems to be that
requestJSON returns a result, so that might be a confusing naming convention ?
Might need to have other overloads for raw data etc but the basic use case here is JSON response

@freak4pc I think  ****response****JSON**** might make sense since the original method is responseJSON. Somebody who is in the "zone" should figure out what it should exactly be :)

Yup thats why I tagged @sergdort who is definitely more active than me on this :) Using the library and maintaining, that is.
I'm also in favor of responseJSON but that gets "requestJSON" to not make much sense :)
The original responseJSON method is for a request() method.
Having similar syntax to Alamofire here would be nice but its not consistent with RxAlamofire right now so I'm not sure that's a good idea as well (e.g. RxAlamofire.request(...).responseJSON)
where request returns Observable and responseJSON is something like
extension ObservableType where E == DataRequest {
    func responseJSON() -> Observable<DataResponse<Any>> {
        // some sort of flatmapping of self
    }

Some feedback from the community would be great here. Probably involving this level of complexity is less of a good idea. I think leaving everything under RxAlamofire.method is easier/more understood, so it's just a naming convention thing.

This is actually probably the nicest syntax for this, I reckon.
Thoughts? @kzaher @sergdort

I think it feels very nice and natural (also similar to how non-Rx Alamofire works), I'm comfortable with pushing a PR for it.

@freak4pc @kzaher
not sure how relevant this is or if there's a simpler way but I worked around my use case, that is to fetch the error message and other attributes from the response:
        request(method, path, parameters: parameters, encoding: encoding, headers: headers)
            .flatMap { (req: DataRequest) in
                return req
                    .validate({ (request, response, data) -> Alamofire.Request.ValidationResult in
                        // Only check for known error codes
                        if self.isHTTPSuccess(code: response.statusCode) { return .success }
                        let (name, message) = data != nil ? self.getHttpError(data!) : (nil, nil)
                        // do something with error name and message
                    })
                    .rx.json()
            }

    func getHttpError(_ json: Data) -> (String?, String?) {
        var errorName: String?
        var errorMessage: String?
        let d = try? JSONSerialization.jsonObject(with: json, options: JSONSerialization.ReadingOptions.allowFragments)
        if let data = d as? Dictionary<String, AnyObject> {
            if let message = data["error"]?["message"] {
                errorMessage = message!
            }
            if let name = data["error"]?["name"] {
                errorName = name
            }
        }
        return (errorName, errorMessage)
    }

Thanks @simoami for sharing!
While that works well specifically for your case, the original question was about exposing the DataResponse object that currently has no good method of being accessed. I'm glad you were able to resolve your issue but it doesn't exactly relate to the original question. Also, with having the new syntax you could easily just access the DataResponse object which might reduce some of the headache you're having here (even though that is a bit more specific).

@freak4pc I'm aware of the difference to the original question, which is why I keep referring to mine as a specific "use case" for fetching response data. btw, mind pointing me to the new syntax? I didn't check is a new update was published to make the response accessible. would love to incorporate!

Hey @simoami - Take a look here, I just pushed a PR explaining my thoughts on how to expose DataResponse. I'd love your feedback if it makes sense to you as an active user!

Nice, great. It definitely look more like an easier interface. Will it also get onNext with other http status codes? say 401 or 500?

I haven't tested but I don't believe so? Alamofire works with throws. If an error is thrown it would be pushed as an onError event.

Fixed by #79

Thanks @freak4pc.


Feature Request: Extract code snippets

Extract code snippets to dedicated files to enable sanity checking the code examples

(and to use them as an additional test suit for the tools; if usage and documented usage differ there is at least a documentation bug)

It's a great idea in principle but the effort is significant to implement this properly, esp. when using those code snippets for testing. There's more urgent areas we need to focus on, so closing for now.


Move documentation related to CWL from e3sm_to_cmip

The documentation that needs to be moved over include: https://github.com/E3SM-Project/e3sm_to_cmip/commit/d5ce9305832ae89f505e4afb8d45cfef3fc919c6#diff-d9f19138e04f4828fb20ea86fa9f5cc50490d1e0a68ed96fe3df9d9df3dae577

Closed by PR #129


Support for ED25519 keys/cert

The Ed25519 support has been added to openssl in the version 1.1.1. This version is not yet released by OpenSSL but they do have pre-release versions. I'd like to check if a enhancement PR that adds support for Ed Certificates/keys with the generate/sign/verify operations is of interest.
I could also add it for Ed448.

Sure. Ed25519 is my favorite.

Closed by #103.


Problem with custom rules?

I have a form that have some custom rules which was working fine. Just today I've noticed that the custom rules aren't working anymore.
After various tests i cannot find the reason why. Just in case, i made a new application like this:
composer create-project --prefer-dist yiisoft/yii2-app-basic basic

After configuring db, i added in my ContactForm a rule like this:
return [
    //...
    ['name', 'validateTest']
]

And i added the function:
public function validateTest($attribute)
{
    $this->addError($attribute, 'error');
}

Still, if i submit the form with any value in the name, it won't show any error. Something changed? Is there is a new method to add rules that i don't know of? If i am doing something wrong, i apologize.

Failed to reproduce.
Maybe related to https://github.com/yiisoft/yii2/issues/10723?

I Just found what was happening:
If i don't have enableAjaxValidation  set in my form, after submit it, it will not do any of my custom rules if any other attribute have an error.
In my example above, if i submit the form with only a name, it won't trigger the custom error. But, if i have all fields filled it will.
This happens only with me? Or is this the expected behavior of the form? If so, is it possible to change that to show all errors after submit including the ones made by custom rules? In my applications i usually don't enable the ajax validation.

It's expected. I've pointed you to the issue #10723 where @cebe posted an answer on your question: https://github.com/yiisoft/yii2/issues/10723#issuecomment-177975280

I see. Thank you for clarify this.

You're welcome :)


[WIP] Implementation of Maps API

This is the corresponding implementation PR for https://github.com/SpongePowered/SpongeAPI/pull/1162. Much is yet to be completed, but since the implementation of maps is uniquely weird, I assumed it might be useful to shape the progress.

Thanks @kashike http://scr.hu/1s1h/1zk64 :smile_cat:

Please refrain. I'm currently working on this and I value my inbox. ;)
On Sat, Apr 2, 2016, 8:15 AM kamcio96<EMAIL_ADDRESS>wrote:

Thanks @kashike https://github.com/kashike http://scr.hu/1s1h/1zk64 [image:
:smile_cat:]
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/SpongePowered/SpongeCommon/pull/625#issuecomment-204715000

Status of this?

In progress, sorry next two weeks are very busy. I have time to comment and
respond but not a whole lot of time to dedicate to working on the code till
after these two weeks are.
On Sun, Apr 17, 2016 at 7:40 PM Robert Herhold<EMAIL_ADDRESS>wrote:

Status of this?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/SpongePowered/SpongeCommon/pull/625#issuecomment-211140340

This is now under active development again, I'm sorry for the delay I've been holding off making any time commitments until my job situation was settled.

Please update the target branch to bleeding (Edit this PR and change the target branch) and reopen.

Worth discussion is the patches I made to RegistryTestUtil in order to get CatalogTypeClassesTest to pass.
I made it check that members that are purported to be CatalogType members and handed to the test are actually public members, not just any static field. This prevents the factory member in MapColors from breaking the build.
To actually allow the member to be set, even though it's kept as private after the AT pass, I updated RegistryHelper to remove the private access when doing the field access during setting the factory.
This is the cleanest solution I felt made sense, but another possible solution would be to patch the test itself or the gather method to only produce instances that are actually implementing CatalogType. But I wasn't quite sure of the test's purpose so I only narrowed the test's scope slightly.

How long to finish this AMAZING thing?

Probably I won't look at this until winter break starts and I have some time to focus on non-work, non-school projects. Right now I don't have a lot of time to focus on projects like this. So best case it's done between December and January.


Remove focus border

Remove focus border on webkit browser (Safari and Chrome).
Just a little aethstetic fix.
Smart directive for angular.
Thank you
Thierry

Current coverage is 100% (diff: 100%)

Merging #385 into master will not change coverage

@@           master   #385   diff @@
====================================
  Files           1      1
  Lines         846    846
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          846    846
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 324ea00...eadc5c9

The outline is here in purpose for the keyboard support. If you don't want it just disable the keyboard support.

Interesting features. I understand the concept.
For UX the dark blue dot is good focus.
The default border is too much. The squared focus do not match the circle.
Both options should not be linked.
This is just a suggestion.
Google Material design follow this option.
Best


Getting Error: Cannot find module 'aws-sdk' in Lambda since switching to node18

How did you install the Amplify CLI?
yarn
If applicable, what version of Node.js are you using?
node18 in my Lambda
Amplify CLI Version
12.5.1
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I've recently updated all my Lambdas to run on node18 instead of node16 following the manual steps in https://github.com/aws-amplify/amplify-cli/issues/10894
However to get it running again I've manually switched my Lambda back to node16.
Describe the bug
When running my Lambda in production I get the following error:
Error: Cannot find module 'aws-sdk'
From what I've read (https://aws.amazon.com/blogs/compute/node-js-18-x-runtime-now-available-in-aws-lambda/) this is to be expected when switching to node18 as aws-sdk isn't bundled up for node18 as it was for node16.
Trouble is I'm not importing aws-sdk in my Lambda so I'm not sure where this error is coming from?
For now I've manually reverted back to node16 to get the Lambda running.
Expected behavior
If I'm not importing aws-sdk I'm not sure why its complaining?
Its a Lambda created with Amplify CLI that I'm using in my schema via the @function directive. Its talking to GraphQL via axios but thats about it.
Reproduction steps
Create a lambda.
Edited the cloudformation templates ala https://github.com/aws-amplify/amplify-cli/issues/10894#issuecomment-1251564540 but for node18
Push up
Run the Lambda
Now this Lambda was created on an older version of the CLI so I'm not sure if this is a fixed thing now or not.
Project Identifier
This never works for me :(
Log output

# Put your logs below this line
2023-09-27T13:33:38.717Z	undefined	ERROR	Uncaught Exception
{
    "errorType": "Runtime.ImportModuleError",
    "errorMessage": "Error: Cannot find module 'aws-sdk'\nRequire stack:\n- /var/task/index.js\n- /var/runtime/index.mjs",
    "stack": [
        "Runtime.ImportModuleError: Error: Cannot find module 'aws-sdk'",
        "Require stack:",
        "- /var/task/index.js",
        "- /var/runtime/index.mjs",
        "    at _loadUserApp (file:///var/runtime/index.mjs:1061:17)",
        "    at async UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1093:21)",
        "    at async start (file:///var/runtime/index.mjs:1256:23)",
        "    at async file:///var/runtime/index.mjs:1262:1"
    ]
}

Additional information
No response
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hey @PeteDuncanson :wave: thanks for raising this! With support for Node 18 in Lambda AWS SDK v2 was removed from the base image in favor of AWS SDK v3. As you have found downgrading to Node 16 will resolve this, however you can also install aws-sdk as a Function dependency ahead of migrating to use version 3 of the SDK

I am also curious about the issue you're experiencing with diagnose :eyes: do you get an error and/or stack trace if you run amplify diagnose --send-report?

Hey @josefaidt my friend.
I'll try that. So with v2 installed by default does that mean I don't have to import it? Im not importing anything from aws in my functions but maybe there's something global that im using somewhere and that's the issue. That would make sense. I'll check tomorrow.
For your last comment there's an issue for it. Would love to get it sorted to help with stuff like this so feel free to cast an eye over it https://github.com/aws-amplify/amplify-cli/issues/10980

Got the same issue when upgrade to nodejs18.x, since nodejs12.x is deprecated.
it related to the error https://github.com/aws-amplify/amplify-cli/issues/3173, but that ticket has been closed.
Not sure nodejs16.x, will take a try.  But not sure what can be done if nodejs16.x is deprecated later.

I am having this problem with the AdminQueries created by amplify update auth.  Works fine when I downgrade the runtime to "nodejs16.x" but when I upgrade to the recommended "nodejs20.x" or even "nodejs18.x" it doesn't. Not sure how to fix this since I am not hosing my front end (nextjs) on AWS.

I'm never ashamed to be that one person that puts their hand up and says they don't know something. If I'm feeling confused others must be to.
Could I has for a hand holding walk through of how this issue should be found and fixed as currently I'm still unsure how to make it go away (other than leaving it running on Node 16).
What commands do we need to run?
Where do we run them?
What files need editing?
What steps do we need to take to clear this up?
Give me a walk through like I'm an idiot so I can understand more and others coming behind can follow along without having to be the one to put their hand up :)

Hey @PeteDuncanson :wave: I went through the motions of upgrading an "older" project and captured the following notes:

install Amplify CLI 9.2.1 to simulate "older" project, run amplify init
add a Function with the base "Hello World" template
observe Function CloudFormation template is set to use the nodejs14.x runtime
push with amplify push -y
upgrade to latest Amplify CLI (12.10.1 at the time of writing)
find and replace nodejs14.x with nodejs18.x

add aws-sdk to your Function's package.json#dependencies block{
  "name": "functionawssdkupgradce3aa97f",
  "version": "2.0.0",
  "description": "Lambda function generated by Amplify",
  "main": "index.js",
  "license": "Apache-2.0",
  "dependencies": {
+   "aws-sdk": "^2.1548.0"
  },
  "devDependencies": {
    "@types/aws-lambda": "^8.10.92"
  }
}

push with amplify push -y
🎉

This is assuming the Function source code is not being migrated to use AWS SDK v3, which is now baked into the Node.js 18.x runtime for Lambda.
Let me know if this helps!

I had already migrated the rest of my project to the v3 SDK so what I ended up doing was to copy the Admin Queries source code from a new project that was generated with the Node.js 18x runtime to my older project.  Since I hadn't customized the actual generated Admin Queries code, this worked perfectly.
This code can be found in the project folders under /amplify/backend/function//src/

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

Hey @PeteDuncanson 👋 I went through the motions of upgrading an "older" project and captured the following notes:

install Amplify CLI 9.2.1 to simulate "older" project, run amplify init
add a Function with the base "Hello World" template
observe Function CloudFormation template is set to use the nodejs14.x runtime
push with amplify push -y
upgrade to latest Amplify CLI (12.10.1 at the time of writing)
find and replace nodejs14.x with nodejs18.x

add aws-sdk to your Function's package.json#dependencies block{
  "name": "functionawssdkupgradce3aa97f",
  "version": "2.0.0",
  "description": "Lambda function generated by Amplify",
  "main": "index.js",
  "license": "Apache-2.0",
  "dependencies": {
+   "aws-sdk": "^2.1548.0"
  },
  "devDependencies": {
    "@types/aws-lambda": "^8.10.92"
  }
}

push with amplify push -y
🎉

This is assuming the Function source code is not being migrated to use AWS SDK v3, which is now baked into the Node.js 18.x runtime for Lambda.
Let me know if this helps!

How do you do this update for UserPoolClientLambda?


chore: update weights

Updated weights of all used pallets.
Fixed various benchmarks due to issues with existenial deposits.
Basilisk pallets:

[x] asset registry
[x] duster
[x] exchange
[x] lbp
[x] nft
[x] transaction-multi-payment
[x] xyk

Orml

[x] tokens
[x] currencies
[x] vesting

Substrate

[x] system
[x] balances
[x] timestamp
[x] democracy
[x] treasury
[x] schedule
[x] utility
[x] tips  ( Fails with ReasonTooBig error )
[x] collator-selection

LGTM when build succeedes


Don't reset claim name when re-selecting a new file during an edit

Steps: edit a claim, then reselect a new file (with a different name from the current claim name) and the claim name will update. If in edit mode, this should not happen or the user should be prompted.

from my duplicate issue: a final window with a summary of your settings should be shown (feature request I guess)

There's a ticket filed for that.

Fixed this, will be in next release.


Many warnings generated when compiling and simulating code at tip of main

Using an issue to track fixes discussed offline.
VCS generates many warnings when compiling:

PCWM-W Port connection width mismatch.

This includes wstrb signal in axi_adapter, ibi_queue_wdata_o in controller_active.sv, and host_enable_i in i2c_controller_fsm.sv, among others.

IWNF Implicit wire has no fanin

ibi_queue_wready_i in controller.sv
send_tti_tx_desc_ready in recovery_handler.sv

Runtime warnings are generated for several unique case statements missing a matching condition, in recovery_executor.sv

those will be adressed in https://github.com/chipsalliance/i3c-core/tree/lint-fixes (and merged into main). Some warnings are already addressed


SailsJS Fibers / Sinchronize integration Middleware not extending fibers up to controllers

Sails version: 0.12
Node version: v4.4.3
NPM version: 3.8.7
Operating system: MacOS Sierra

Hello,
Im trying to integrate synchronize / fibers within sailsjs but Im running into a somehow strange issue.
I have been using sailsjs for a while and on a project we wanted to try using fibers to improve the way async code is written.
We decided over synchronize lib for this.
In order add fibers to all requests, we added a new middleware which is as shown below:
    sincronized: function (req, res, next) {
      //console.log('Sincronizing request....', req.method, req.url);
      sync.fiber(next);
    }

We added this middleware before cookie parser.
With the log we have confirmed that the middleware is working and executing properly.
Inside a controller I do use sync.await and sync.defer, but they do fail.
This due to the fact that the execution/thread seems to not be inside a fiber.
Although if I create the fiber inside the controller (not using the middleware), everything works just fine.
Code example:
    find: function(req, res){
    console.log('PatientList.sync....');
      try {
        const result = sync.await(MyService.findAll(sync.defer() ));
        return res.ok(result);
      }catch(err){
        sails.log.error('Error getting records', err);
        return res.serverError(err);
      }
  },

Again if the fiber is created as the first level of the controller everything works fine.
But when I rely on the middleware to create the fiber and reach up to this point, the defer generates and exception due to the fiber not reaching this code.
As a side comment, I also thought that the fiber had issues creating in the middleware code, but I have tested creating a fiber with async(timeout) methods and console logs, and everything works fine. So this is not the case.
Wanted to ask for some guidance of why is this occurring and how to solve.
Is the controller execution done in another thread later on in the app?
Thanks in advance.

@kvindasAB Hmm, that's interesting.  I don't know anything about the sinchronize package, but this might be because other asynchronous steps are occurring in the other HTTP middleware (e.g. if you're using sessions, it has to look that up using your sid cookie.  Or if you have any asynchronous policies, could be that).  What happens if you try putting your middleware in sails.config.http.middleware.order right above router?
Something else that might work (and that would actually be cleaner IMO) would be to create api/hooks/sinchronize/index.js and try attaching sinchronize in a "before" shadow route.
Hope that helps, and good luck!

Hello Mike, thanks a lot for your response.
I tried different approaches, among those, creating a policy and put it at last order within all policies, that seemed the most effective although was a bit trickier too.
At the end, I decided to switch to generators to handle async code.
Again thanks a lot for the response.


V2.0.x Issue with Mobx Observable Arrays

I know you can't account for all various state management packages, but just something i found when using Mobx and Observable Arrays, with the latest method for loading the data (using data instead of "columns" and "rows") you have to flatten the observable array for it to work. Otherwise you run into issues with the array being read properly.
so this:
data={projectState.timelineRows}
needs to be:
data={projectState.timelineRows.slice()}
the ".slice()" flattens the array and fixes the issues. this is more for anyone else running into the issue than something to fix.

Hey @preludeofme,
Thanks for reporting this, for future readers !
That makes sense to me, the Chart component only does a shallow check to see if the data has changed ( prevProps.data !== props.data ).
With Mobx Observable Arrays the reference to the observable array doesn't change so prevProps.data !== props.data is always false.
By calling slice on the array you're creating a new array from the Observable one which causes it to re-render (prevProps.data !== props.data becomes false)
Cheers !


Added delegate approval resource

New resource harness_delegate_approval added.
resource "harness_delegate_approval" "test" {
  name    = "mydelegate"
  approve = true
}

Closes #39


Please Add Azure Service Fabric from Microsoft

Hello!
Wanted to see if we could add Service Fabric to the landscape. The clearest home would be Orchestration & Management / Scheduling and Orchestration.
If it's possible to be included in other areas as well please let me know. Arguably Service Fabric participates in the following as well:

Coordination and Service Discovery
Service Management
Platforms / PaaS Container Service
App Definition & Development / Application Definition
Runtime / Cloud-Native Storage

Happy to have a longer conversation about any of these and provide evidence and any docs or other information required.
Thanks
-Matt
@MikkelHegn fyi

I suppose pointing to the basic landing pages would also help kick things off :)
Basic marketing landing page --> https://azure.microsoft.com/en-us/services/service-fabric/
Docs home -> https://docs.microsoft.com/en-us/azure/service-fabric/

@masnider Could you please answer these questions for us (we created the issue template after you opened the issue):
Please only report on one project or product per issue
Guidelines for getting added to the CNCF Cloud Native Landscape:

We generally will only list a company in one box, to represent its major or best known offering. We occasionally make exceptions for large companies.
Projects with at least 250 GitHub stars that clearly fit in an existing category are generally included.
We are unlikely to create a new category for products/projects as we'd rather find the best home with the current options.
We are generally not including commercial versions of open source software, when that version just includes minor tweaks.
Closed source products need to link to a clear description of your product; no stealth mode companies.
Your project or company needs a logo.

Project or Product name:
Is it open source?:
What are the best URL(s) for it? Repo and homepage (if different) for open source, product homepage for closed source.:
What category does it belong in?
What's the URL for the best logo (and it needs to include the name)?
Anything else we need to know?:

Hi @dankohn - thanks. Glad I didn't just skip the template originally. Answers below:
Project or Product name: Microsoft Azure Service Fabric
Is it open source?: Partially. The programming models and some tools are currently open source, and the plan is for more of the product to become open source, however we have not publicly disclosed a timeline for that at this time.
What are the best URL(s) for it?:
https://azure.microsoft.com/en-us/services/service-fabric/
https://github.com/Azure/service-fabric
What category does it belong in?: Orchestration & Management / Scheduling and Orchestration
Service Fabric also has capabilities that fall into the following categories:

Coordination and Service Discovery
Service Management
Platforms / PaaS Container Service
App Definition & Development / Application Definition
Runtime / Cloud-Native Storage

I don't know if it's possible to be included in multiple categories. If that's the case can we have a quick discussion about how to represent that Service Fabric is a large platform?
What's the URL for the best logo?:
https://raw.githubusercontent.com/Azure/service-fabric/master/service-fabric.png
Anything else we need to know?: Service Fabric is widely deployed inside of Microsoft, running directly on about (as of this writing) one-third of all Azure cores. Service Fabric is the platform behind many services from Microsoft, including SQL Azure, Cosmos DB, EventHubs, IotHubs, Cortana, Intune, PowerBI, Dynamics 365, the core Azure Resource Providers, and more. Service Fabric currently supports Windows and has a public preview for Linux. Service Fabric provides a development platform for writing services should developers wish, with capabilities for lifecycle management and stateful computation. Service Fabric orchestrates and manages bare processes, containers, and services written against Service Fabric's service APIs.
Thanks and let us know if you need any more information.
-Matt

Great, thanks. We are very likely to put it in Service Management.

@masnider Could you please email me: dan at linuxfoundation.org

Confirming this will go as a closed source product in Orchestration. Thanks.

Thanks for all the detail @masnider and @dankohn ... this will be included in the upcoming 0.9.8 version!

Hi @masnider, closing as this update was included in the most recent version https://github.com/cncf/landscape#current-version

@dankohn @shawnpreissner Thanks! This is great.


[Narwhal] Update batch execution latency metric & logging

Description
Ensure all latencies of steps in NW are logged from batch creation to batch being fetched for execution, so we can spot check some digests from start to finish. Additionally update how batch execution latency is calculated. Whenever we receive a batch from other workers we update the metadata to the current time signifying the time we received the batch and not calculating based on the time the batch was created at the originating validator.
Test Plan
Existing Unit Tests

I hope the approach of updating batch creation time can be avoided. If the creation time becomes unexpected, it will be hard to tell if the problem happened during creation or overwriting. Is it possible to attach another timestamp, or just debug log the report batch latency so they can be subtracted if needed?

Agreed on keeping another timestamp for this, it will make things cleaner. I am approving to have this merged and maybe we can  work on another PR?

I was actually thinking about updating the code later to distinguish between batches received by others vs our own batches in the latency measurements. But I think adding a received_at timestamp to Batch metadata will do the job. Then we can just separate the batch execution latency into two buckets (others vs ours).
However because metadata is not versioned I cant just update the existing struct without causing issues right? Can I version it now and follow the protocol upgrade flow?

I was actually thinking about updating the code later to distinguish between batches received by others vs our own batches in the latency measurements. But I think adding a received_at timestamp to Batch metadata will do the job. Then we can just separate the batch execution latency into two buckets (others vs ours).
However because metadata is not versioned I cant just update the existing struct without causing issues right? Can I version it now and follow the protocol upgrade flow?

We do the proper versioned update later. Btw for the information we need, is it needed across all validators?


Add support for regex command matching

I am not sure if I hacked up the module manager right, but this seems to work based on my testing.

LGTM. Mind rebasing and squashing a bit before i merge?

Not at all.
One feature this lacks that might be nice is an optional argument to the command function saying which regex matched. I don't know if that's already done, though.

And that should add the last feature I want from this.

Nice, thanks!


ref: review remote add/modify --local info.

rel https://github.com/iterative/dvc.org/issues/2970

any substantial changes (we didn't have --local and now we set it) ... something besides moving things around?


Use of glider_devices

Are the fields in glider_devices from the deployment yaml used anywhere? I couldn't find them being accessed by any of the scripts in gliderpy. These fields include sensor names, serial numbers and calibration information. Could be useful to include in netCDF metadata, but I don't know how that would be done. Could just append them to metadata?

@callumrollo just reading through this now. Feel free to also join the debate about OG1.0 in the OceanGliders Data Format repo


{App Service} Skip tests to unblock CI

Related command

Description

Skip the tests temporarily to unblock CI:

Testing Guide

History Notes

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

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

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

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

more error messages please refer to: error.log

+@khkh-ms for awareness
Our CI is blocked by the failed tests mentioned in this PR, so we skip them temporarily.

This is similar to https://github.com/Azure/azure-cli/pull/30289#issuecomment-2464105440


Release Training SDK 1.8.1

I released kubeflow-training==1.8.1 SDK version: https://pypi.org/project/kubeflow-training/1.8.1/
/assign @kubeflow/wg-training-leads

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 35.423%

Totals

Change from base Build<PHONE_NUMBER>1:
0.0%

Covered Lines:
4380

Relevant Lines:
12365

💛  - Coveralls


Inconsistent indentation of multi-line strings

What version of CUE are you using (cue version)?
b51368ea / v0.3.0-beta.6
Does this issue reproduce with the latest release?
Yes
What did you do?
cue fmt output for this snippet:
let _foo = """
foo \(f)
bar
"""

let _bar = """
	foo
	bar
	"""

What did you expect to see?
let _foo = """
foo \(f)
bar
"""

let _bar = """
foo
bar
"""

Apparently, indentation depends on whether or not interpolations exist. I would expect it to always behave like it does with interpolations (no indent - much easier to work with).

Confirmed with tip (7c5d28e6):
exec cue fmt x.cue
cmp x.cue x.cue.golden

-- x.cue --
f: 5

let _foo = """
foo \(f)
bar
"""

let _bar = """
foo
bar
"""

y: "\(_foo) - \(_bar)"
-- x.cue.golden --
f: 5

let _foo = """
	foo \(f)
	bar
	"""

let _bar = """
	foo
	bar
	"""

y: "\(_foo) - \(_bar)"

I took the liberty of looking into this issue. I have not been able to find a fix, but hopefully my findings can help.
The indentation added to the multi-line string _bar seems to be intentional (see commit 2ac4d850af7a13a3e561ea1bafbcdce05bb616a5).
Further, indentation is not added to multi-line string _foo because an error occurs during formatting. The presence of interpolation \(f) causes the multi-line string to be split into two parts/quotes ("""\nfoo \( and )\nbar\n"""). The split results in an error when trying to add indentation to each of them because neither of the two parts are valid quotes (see https://github.com/cuelang/cue/blob/447606047bdd32f79029a4be5424af3a09ea15f2/cue/literal/indent.go#L24). The end result is that the multi-line string remains unformatted.

cc @mpvl for thoughts on @stromsvag's comments.

This issue has been migrated to https://github.com/cue-lang/cue/issues/834.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Remove version: SBCL.SBCL version 2.0.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: Package still available.;


aws.ecs.Service does not appear to accept enable_execute_command parameter (Python sdk)

aws.ecs.Service is not accepting enable_execute_command parameter.
Expected behavior

I would expect for pulumi up to succeed and for enable_execute_command to be incorporated into the service configuration.
Current behavior

Per the documentation here https://www.pulumi.com/docs/reference/pkg/aws/ecs/service/ I am trying to set the optional enable_execute_command parameter to aws.ecs.Service. I am encountering the following TypeError when running pulumi up:
TypeError: __init__() got an unexpected keyword argument 'enable_execute_command'

Additionally, when I attempt to export the value, I get an AttributeError:
AttributeError: 'Service' object has no attribute 'enable_execute_command'

Here is the full traceback:
Diagnostics:
  pulumi:pulumi:Stack (aws-pulumi-dev):
    error: Program failed with an unhandled exception:
    error: Traceback (most recent call last):
      File "/usr/local/bin/pulumi-language-python-exec", line 85, in <module>
        loop.run_until_complete(coro)
      File "/Users/bryce/.pyenv/versions/3.7.8/lib/python3.7/asyncio/base_events.py", line 587, in run_until_complete
        return future.result()
      File "/Users/bryce/.pyenv/versions/aws-pulumi-spike/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 83, in run_in_stack
        await run_pulumi_func(lambda: Stack(func))
      File "/Users/bryce/.pyenv/versions/aws-pulumi-spike/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 34, in run_pulumi_func
        func()
      File "/Users/bryce/.pyenv/versions/aws-pulumi-spike/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 83, in <lambda>
        await run_pulumi_func(lambda: Stack(func))
      File "/Users/bryce/.pyenv/versions/aws-pulumi-spike/lib/python3.7/site-packages/pulumi/runtime/stack.py", line 106, in __init__
        func()
      File "/usr/local/bin/pulumi-language-python-exec", line 84, in <lambda>
        coro = pulumi.runtime.run_in_stack(lambda: runpy.run_path(args.PROGRAM, run_name='__main__'))
      File "/Users/bryce/.pyenv/versions/3.7.8/lib/python3.7/runpy.py", line 280, in run_path
        run_name, mod_spec, pkg_name).copy()
      File "/Users/bryce/.pyenv/versions/3.7.8/lib/python3.7/runpy.py", line 85, in _run_code
        exec(code, run_globals)
      File "./__main__.py", line 366, in <module>
        opts=ResourceOptions(depends_on=[web_listener]),
    TypeError: __init__() got an unexpected keyword argument 'enable_execute_command'
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

Steps to reproduce

service = aws.ecs.Service(
    'app-svc',
    cluster=cluster.arn,
    desired_count=1,
    launch_type='FARGATE',
    task_definition=django_web_task_definition.arn,
    network_configuration=aws.ecs.ServiceNetworkConfigurationArgs(
        assign_public_ip=True,
        subnets=default_vpc_subnets.ids,
        security_groups=[security_group.id],
    ),
    load_balancers=[aws.ecs.ServiceLoadBalancerArgs(
        target_group_arn=app_target_group.arn,
        container_name=AWS_WEB_CONTAINER_NAME,
        container_port=AWS_CONTAINER_PORT,
    )],
    enable_execute_command=True,
    opts=ResourceOptions(depends_on=[web_listener]),
)

With the above configuration (along with reasonable defaults for the other resources), run pulumi up
Context (Environment)

This is blocking me from connecting to a container with AWS ECS Exec, which I need for some debugging.
Affected feature

aws.ecs.Service

Hi @bryceAebi
What version of pulumi-aws are you using?
Paul

Ah, I see I was running an older version (3.32.0). Upgrading to 4.0.0 solved my issue. Thanks for the help!


final.zip，modules folder “_is_full_backward_hook : NoneType”error

Hello, I want to generate a new torch model, that is, to generate a library for C + +. There is an extra sentence for each function in the final.zip file I output：“_is_full_backward_hook : NoneType”.

However, the corresponding function has not been changed in the original project.As a result, an error will be reported in the program.

On the left is the pre trained downloaded model, and on the right is the model generated by myself. Moreover, there are differences in the functions in some files. For example, there will be several more functions, but I haven't changed the codes of these parts. How should I adjust them.These files are in the final.zip, torch->nn->modules,like activation.py,conv.py etc.

Thanks a lot!

I solved this problem by downgrading pytorch and libtorch version to 1.7, you may try it :)

pull latest code and retry