Brew installation issue with az policy event list command

Homebrew, Mac Installation, 2.0.44
$ az policy event list
No module named 'azure.mgmt.policyinsights'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 343, in execute
    result = cmd(params)
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 182, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/core/__init__.py", line 427, in default_command_handler
    client = client_factory(self.cli_ctx, command_args) if client_factory else None
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/command_modules/policyinsights/_client_factory.py", line 15, in policy_events_operations
    return _cf_policy_insights(cli_ctx).policy_events
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/command_modules/policyinsights/_client_factory.py", line 9, in _cf_policy_insights
    from azure.mgmt.policyinsights import PolicyInsightsClient
ModuleNotFoundError: No module named 'azure.mgmt.policyinsights'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/knack/cli.py", line 197, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/core/commands/__init__.py", line 366, in execute
    cmd.exception_handler(ex)
  File "/usr/local/Cellar/azure-cli/2.0.44/libexec/lib/python3.7/site-packages/azure/cli/command_modules/policyinsights/_exception_handler.py", line 10, in policy_insights_exception_handler
    from azure.mgmt.policyinsights.models import QueryFailureException
ModuleNotFoundError: No module named 'azure.mgmt.policyinsights'

Fixed.


Specify minimum Android API Version in the Readme

First of all, thanks guys for this great project!
I cannot find the minSdkVersion on the README so I checked the Grandle file from here:
https://github.com/turbolinks/turbolinks-android/blob/master/turbolinks/build.gradle
and for what I can understand the minSdkVersion is set to 19. Can you please confirm it?
I think it could be useful to specify to the minSdkVersion in the README as for turobolinks-ios
Thanks

Hi. That's correct -- the minimum SDK is 19. Sorry that wasn't make clear up front.
It'd be great to add that to the README in the prerequisites section if you'd like to cut a pull request. Thanks!

HI @risinglf, I added the minSdkVersion prereq to the README. Thanks for pointing that out.

Sorry @lateplate for the delay, and thank you very much!

👍


Removing/replacing defaults

Hi! Thanks for the great plugin.
I'd like to remove the default toggles from the config — they are a bit of a nuisance since many of them are partially the same as mine (for example i have ['body', 'header'] which conflicts with the default ['body', 'head']). Is it possible?

I too just ran into a similar problem. I wanted off to toggle to warn or error for setting eslint config values, but it only ever toggles between on and off.

The next version will include an option to not use the default toggles so they can be 100% customized by the user through the settings.


[BREAKING] Rust representation of GPU memory re-worked

Overview of the PR
Currently, we use a pretty awkward representation of on-device memory. This PR creates a more idiomatic pair: DeviceVec (which is not really a vector but a boxed slice) which allocates, deallocates and owns device memory, and DeviceSlice which provides mutable and immutable views into device memory.
@ChickenLover I also changed vector operations a little bit - Montgomery is removed as it was working differently for multiplication and addition/subtraction, plus device id checks have been added. Also, I wasn't sure how to change Poseidon related data that is currently raw slices, is it correct to say that here we should use DeviceVec (which should help with the memory leak, at least on the Rust side) and digest here should be a host slice?
Unresolved questions
One potential improvement for H2D/D2H memory operations would be to pin memory inside HostSlice::from_slice method. But I'm still not sure how effective pinned memory is for modern GPUs, plus we don't really have ownership of host data so it's hard to make sure it's pinned and unpinned exactly once (which I'm not sure is a real issue). If someone has good understanding of pinned memory, please comment. And maybe we can just provide a flag for the user to decide if they want to pin memory or not.

I like the distinction made for DeviceVec and DeviceSlice, and the usage of ManualDrop.
Would like to confirm one thing:
the updated msm() API now accepts either DeviceVec and DeviceSlice now, just to make sure the following flow won't cause double free:

assign a DeviceVec for some bases points (say 2^20)
get a DeviceSlice for a sub-slice of it (say 2^15 out of it)
pass on this slice to the msm(), for some reason, this cuda operation panic and failed (say due to GPU out of memory)

(currently I'm using mem::forget() to forget the subslice without calling destructor to prevent double-freeing. but double-freeing would still be a risk if msm() failed in the middle before I got a chance to call forget() since currently there's no differences between subslice on device and original owned vec on device, so both have the same cudaFree logic in their destructor.
so just want to double-check that changes introduced here would obviate my concern, since DeviceSlice's destructor won't do anything, correct?)

@alxiong yea, the new functions do accept either DeviceSlice, HostSlice or DeviceVec. The latter is accepted by Deref to DeviceSlice (similar to how other Rust functions that accept slices can be used with vectors). And like normal Rust slices, DeviceSlice doesn't own any data so won't call cudaFree, only DeviceVec frees data :)

Closing in favor of #443 which includes these changes


atan2

Add ATAN2 function.

Can you add documentation (Readme.md and JavaDoc) and also at least one unit test for the new function? Thank you.


Member access within null pointer detected via Libfuzzer & UndefinedBehaviorSanitizer

Member access within null pointer detected via Libfuzzer & UndefinedBehaviorSanitizer.
./fuzz_parseini crash-fb8.txt
Running: crash-fb8.txt
lib/bloom.c:95:26: runtime error: member access within null pointer of type 'struct bloom'
crash-fb8.txt

Not sure what this is for. Needs more information. Closing.


Fix response interpretation according to specification

The specification has changed a little since this tester tool was written. This PR changes some response interpretations to follow the specification.

This got merged, even though GitHub shows this as closed. I messed up with the branches a bit and GitHub got confused.


guide revised and guide-ja updated [ci skip]

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
--

Fixed issues
guide revised and guide-ja updated

Merged. Thanks!


Shrink the debug info

Summary of the Pull Request
What is this about?
PR Checklist

[ ] Applies to work item: #xxx
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #3247 (d2b03f9) into main (f4774c2) will decrease coverage by 3.75%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3247      +/-   ##
==========================================
- Coverage   29.65%   25.90%   -3.75%
==========================================
  Files         332      152     -180
  Lines       39290    16383   -22907
==========================================
- Hits        11651     4244    -7407
+ Misses      27639    12139   -15500

see 180 files with indirect coverage changes


Multi-threaded implementation

Currently, pynndescent doesn't take full advantage of multiple cores on a machine. There are some methods annotated with the Numba parallel option, but these don't provide any noticeable speed up when more cores are available.
This PR allows nearest neighbor computation to take advantage of multiple cores by processing heaps in parallel chunks. The basic idea is an application of the MapReduce approach described in section 2.8 of Efficient K-Nearest Neighbor Graph Construction for Generic Similarity Measures by Dong et al.
Note that in this PR all computation is carried out on a single machine using the standard Python concurrent.futures library, which complements Numba very well, as shown in this example.
Going into slightly more detail, a distributed heap can be updated in a MapReduce-style operation as follows.
We have a large array of all the heap updates held in memory and a thread pool to update chunks in parallel in two phases, called "Map" and "Reduce". Each Map partition holds an array of heap updates, corresponding to a row in the following diagram.

The Map phase adds updates in the order they were generated (from heap_push calls). After all the updates have been added for a partition, the updates for that partition are sorted by row number. Then the chunk boundaries corresponding to partitions are found, so that in the Reduce phase the array can process all the updates for a given partition together, and apply them to the target heap (not illustrated).
For the Map phase the array is processed row-wise, and in the Reduce phase it is processed column-wise (although the column bounds are different for each row owing to the different chunk boundaries). The result is an updated distributed heap.
This PR also adds tests that check the threaded implementation produces the same result as the regular implementation. Since NN-Descent uses a source of randomness, when running the tests the random seed is set to the value of each row index to ensure the same deterministic result is obtained. This per-row seeding is only used for tests. However, to make threaded runs more reproducible when run normally (outside of tests) each thread is seeded from the initial random seed, which means that the result from two threaded runs (with the same number of threads) is the same if the same initial seed is used in each case.
In terms of performance, the multi-threaded implementation outperforms the regular implementation with 4 cores or more. In one experiment, regular pynndescent took 27 minutes for a million rows (D=128, NN=25), compared to just over 3 minutes with 64 threads.
There is more work to consider how to wire up the implementation to the standard NNDescent object, but I wanted to get feedback on this approach before going any further.

This looks fantastic! It is going to take me a little while to find the time to work through this properly and review it, but please don't mistake that delay for a lack of excitement about this pull request! Definitely looking forward to digging into this one, and would be extremely happy to get this merged.

@tomwhite I still want to have some time to play around with this, but I have at least gone through and satisfied myself that I understand how it all works, and wanted to get some initial feedback as soon as possible.
First and foremost, this looks great! It is at heart very simple (which is a definite positive), and so fairly easy to follow, but very slickly done. I appreciate that you've kept the code very clean and that it matches nicely with the single threaded version.
On the question of going any further -- I think it definitely looks worth doing, and welcome whatever you view as appropriate for making it fit with the NNDescent object. I would also be happy to discuss options if you like. I haven't had the opportunity to do much benchmarking myself, but it sounds as if the single threaded case might be worth keeping for the 4-core or less case (depending on what the overhead is like for the threaded case).
Unless I've missed something it looks like your threaded version does not currently make use of the RP-trees when initialising the NNDescent. At least in the single threaded case this has been quite beneficial for performance. It is possible that this might get the threaded performance matching in the 4 or less core case. I will have to experiment and try some benchmarking to know for sure.
Lastly, given how well this works I would be interested in your thoughts on how well this might extend to working with dask (which has a concurrent.futures like interface) for out-of-core versions of pynndescent?
P.S.: Ignore the Codacy complaint, I turned it some time ago and was unimpressed but forgot to turn it off. It's off now.

One other thing to note: since about 0.38 numba has supported passing jitted functions as parameters. This obviates the need to use the indirection of the make_nndescent functions that produce jitted functions -- instead you can simply pass dist and dist_args directly to the function in question. I've been in the process of shifting pynndescent to this, but have been busy with other projects so it isn't exactly complete yet.

@lmcinnes thanks for looking at the code, and for your kind comments. Let me address your points in turn.
To make it fit with the NNDescent object, I thought having an algorithm='threaded' might be a reasonable way of doing this. I will try that out to see if it works, but let me know if you've got another approach in mind.
Regarding the existing code path, I agree that it is worth keeping since it is faster for less than 4 cores. Or even more with RP-trees. You are correct that I haven't looked at parallelising RP-trees, but I think there are various ways that it would be possible, the simplest being initialising each tree in a separate thread. But that could be a later addition I think.
BTW for benchmarking I've been using these scripts. If these are generally useful I'd be happy to contribute them too.
Regarding Dask, I'm very interested in this direction, and in fact, running on a distributed engine like Dask or Spark was my initial motivation for optimising pynndescent (for Scanpy). Obviously, the MapReduce technique naturally transfers to these engines, although there may be challenges regarding the amount of data that needs to be shuffled for each iteration. This is well worth investigating for the potential gains for scaling to very large datasets though.
Finally, thanks for the info about the Numba upgrade. I'll rebase this PR to reflect the fact that make_nndescent is no longer needed.

The algorithm='threaded' looks good for now. Ideally it might be beneficial to mirror sklearn's n_jobs approach to handling multiple threads/processes, but that can always be dealt with in the future.
I have been doing some benchmarking on datasets I expect to be more representative of real data than purely random data and the performance numbers seem to be comparable to what you describe, so I am fairly confident about this at this point. I am ready to hit the merge button as soon as you like -- did you have anything else you wanted to add before merging, or just get this merged and then look at anything else later?

@lmcinnes I don't have anything else to add before merging. I'll look at sklearn's n_jobs API separately.

Excellent, thanks for all your work on this! I will likely be porting some or all of this over to umap at some point soon as well.

Thanks @lmcinnes! I'll submit some follow-up PRs that are related to this one.
Re umap, are there plans to have it use pynndescent as a dependency at some point? I'd be happy to help in that effort.

I look forward to future PRs!
Adding a dependency on pynndescent is tempting from the point of view of removing duplication, but it does mean I would have to get pynndescent in a rather better state (testing, documentation, functionality), and right now umap is both in heavy development and also widely used so I was hoping to get to a good state on umap and associated new features before setting to work on pynndescent in earnest and getting to where it needs to be.


FakeStorageRpc generation support for copy fails on read

Hi,
I'm trying to use LocalStorageHelper for a test.   I do this (scala)
    val request = CopyRequest
      .newBuilder
      .setSource(BlobId.of(sourceBucketName, sourceKey))
      .setTarget(BlobId.of(destinationBucketName, destinationKey))
      .build
    gcsClient.copy(request).getResult

    val obj =  gcsClient.get(BlobId.of(destinationBucketName, destinationKey))
    val content: Array[Byte] = obj.getContent(BlobSourceOption.generationMatch)

So that's a copy followed by a read action on the new file (gscClient is the LocalStorageHelper in this case).
However, during the copy action here:
https://github.com/googleapis/google-cloud-java/blob/master/google-cloud-clients/google-cloud-contrib/google-cloud-nio/src/main/java/com/google/cloud/storage/contrib/nio/testing/FakeStorageRpc.java#L379
The target is stored in metadata without a generation, so the read throws a NPE attempting to perform a generationMatch.
I'm hoping to learn:

Do you agree this is a bug or at least "not optimal behavior" ?
Would you be open to a PR that does the following:
a) on copy, checks if destination exists, if it exists, gets the existing generation + 1
b) if it doesn't exist gets 0
c) uses that resolved generation in the target in the rewrite request target that is stored in the metadata in memory store.

The currently implemented generational match logic seems to be checking the destination:
https://github.com/googleapis/google-cloud-java/blob/master/google-cloud-clients/google-cloud-contrib/google-cloud-nio/src/main/java/com/google/cloud/storage/contrib/nio/testing/FakeStorageRpc.java#L366
Since generations are always updated on modification, I think my proposed changes are still good, but this precondition check in the code felt a little awkward to me as I read it.
Environment details

Specify the API at the beginning of the title (for example, "BigQuery: ...")
General, Core, and Other are also allowed as types: FakeStorageRpc
OS type and version: osx 10.14.5
Java version: scala 2.11.12
google-cloud-java version(s): 0.99.0-alpha

Steps to reproduce

use the LocalStorageHelper to copy a file
use the LocalStorageHelper to read the file that was just copied

Code example
    val request = CopyRequest
      .newBuilder
      .setSource(BlobId.of(sourceBucketName, sourceKey))
      .setTarget(BlobId.of(destinationBucketName, destinationKey))
      .build
    gcsClient.copy(request).getResult

    val obj =  gcsClient.get(BlobId.of(destinationBucketName, destinationKey))
    val content: Array[Byte] = obj.getContent(BlobSourceOption.generationMatch)

Stack trace
java.lang.NullPointerException
	at com.google.cloud.storage.Blob$BlobSourceOption.toSourceOptions(Blob.java:99)
	at com.google.cloud.storage.Blob$BlobSourceOption.toSourceOptions(Blob.java:196)
	at com.google.cloud.storage.Blob.getContent(Blob.java:478)
	at com.datadog.spark.util.GCSUtil$.readObject(GCSUtil.scala:110)

External references such as API reference guides used
Any additional information below
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Thank you for bringing this to our attention and thank you for the PR. This is definitely a bug, will take a look at the PR now


importing existing deployment

I have initialised fresh terraform with latest versions of everything
Imported deployment terraform import ec_deployment.dev<PHONE_NUMBER>0000000000000000000000
Did make sure that my manifest seems to be correct, so my local attempt to call terraform plan does say that everything is up to date and no actions needed
After creating an branch and pushing all that to github I have noticed that plan there differs and was:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # ec_deployment.dev will be updated in-place
  ~ resource "ec_deployment" "dev" {
      + apm_secret_token       = (sensitive value)
      ~ elasticsearch          = {
          ~ cloud_id       = "dev:BASE64=" -> (known after apply)
          ~ config         = {
              + plugins = (known after apply)
            }
          ~ http_endpoint  = "http://00000000000000000000000000000000.europe-west3.gcp.cloud.es.io:9200" -> (known after apply)
          ~ https_endpoint = "https://00000000000000000000000000000000.europe-west3.gcp.cloud.es.io:443" -> (known after apply)
          ~ resource_id    = "00000000000000000000000000000000" -> (known after apply)
            # (12 unchanged attributes hidden)
        }
        id                     = "00000000000000000000000000000000"
        name                   = "dev"
        # (7 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

And what is even worse after applied it performs changes to CloudElastic which means it become unresponsive
From a portal I see an action to Kibana, saying that there is no significant changes and for Elastic I see:
Set http.cors_enabled to false
Set http.cors_allow_credentials to false
Set http.cors_max_age to 1728000
Set http.compression to true
Set monitoring_history_duration to 3d
Set monitoring_collection_interval to -1
Set destructive_requires_name to false
Set auto_create_index to true
Set scripting.inline.enabled to true
Set scripting.stored.enabled to true

Which makes import process really scary, I wish not to touch/import production deployment till understand whats going on
There are two issues:

different plans locally and remotely
changes to elastic should not be done at all we are just importing everything as is

I have second staging cluster, which have exactly same issues, so if I can help with some additional details will be glad to do that

What is even wrong, even so changes were applied, second run going to apply them once again 🤦♂ while its happening I did run TF_LOG=TRACE terraform plan -no-color locally and in github, trying to check if there any significant difference and how noticed that terraform itself has different versions, so I have maked sure that my local terraform is exactly the same as in github and finally see the same change locally, but still it is not clear why does terraform tries to perform this changes

While I can reproduce it locally and it is an dev deployment, have tried to apply this changes, from elastic cloud portal I see applied changes with message

And indeed apply happened much faster than previous time
But still each time I run terraform plan it still says that it will perform in place update 🤔

Just in case here is terraform manifest

main.tf
resource "ec_deployment" "dev" {
  name                   = "dev"
  region                 = "gcp-europe-west3"
  version                = "7.17.1"
  deployment_template_id = "gcp-storage-optimized"

  elasticsearch = {
    autoscale = false
    hot = {
      zone_count = 3
      size       = "8g"
      autoscaling = {
        # max_size = "16g"
      }
    }
    master = {
      autoscaling = {}
    }

    cold = {
      autoscaling = {}
    }
    warm = {
      autoscaling = {}
    }
    ml = {
      autoscaling = {}
    }
    coordinating = {
      autoscaling = {}
    }
    frozen = {
      autoscaling = {}
    }
    config = {
    }
  }
  kibana = {
    zone_count  = 1
    size        = "1g"
    autoscaling = {}
  }
}

Duplicate with #599


Apps menu on help.hydroshare.org

The apps menu item on help.hydroshare.org links to https://apps.hydroshare.org/apps.  It should link to http://www.hydroshare.org/apps.  This is a regression that I noticed today. @cbcunc

Fixed.

Fixed on help.

Thanks.  It looks right now.

Re-opening.  This has happened again.  What can we do to prevent this happening?

Fixed in hydroshare/hs_pages#27


upstream: implement UpstreamLocalityStats.loadMetricStats

Implements a simple API allowing extensions to populate UpstreamLocalityStats.loadMetricStats in load reports, stored as a flat hash map of keys and values that may vary at runtime. Individual stats are accumulated by calling add(), which combines stats with the same name; the aggregated stats are retrieved by calling latch(), which also clears the current load metrics. The load metrics are latched and read by the load stats reporter.
Signed-off-by: Eugene Chan<EMAIL_ADDRESS>Commit Message: upstream: implement UpstreamLocalityStats.loadMetricStats
Additional Description: Implements a simple API allowing extensions to populate UpstreamLocalityStats.loadMetricStats in load reports, stored as a flat hash map of keys and values that may vary at runtime. Individual stats are accumulated by calling add(), which combines stats with the same name; the aggregated stats are retrieved by calling latch(), which also clears the current load metrics. The load metrics are latched and read by the load stats reporter.
Note: this implementation puts a copy of the stat name into every host that receives a copy of that metric. This can be improved by putting a single copy of the stat name into a thread-local key->index map and using the index as the key to the stat map instead.
Risk Level: low
Testing: CI
Docs Changes: n/a
Release Notes: n/a
Platform Specific Features: n/a

I think I'm missing some context as I was not aware of the load-stats-reporter infrastructure.
Where do these stats get consumed?

These stats are sent as part of LoadStatsRequest to the management server. (See https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/endpoint/v3/load_report.proto#envoy-v3-api-msg-config-endpoint-v3-upstreamlocalitystats)

Thanks, PTAL
/retest

@pianiststickman can you clarify comments please so we can submit it?

/wait

/wait

PTAL, and apologies for the delay on this. I've added comments explaining the performance considerations of the current implementation. I think since this is purely an implementation detail (putting key names in thread-local storage, eliminating contention on the locks used to hold the stat maps) I'd prefer to take a pragmatic approach and dispense with that when it becomes necessary.

/wait

/retest

We need another senior maintainer, since both Josh and PR author are Googlers :)

/assign-from envoyproxy/senior-maintainers

/assign-from envoyproxy/senior-maintainers


SSR is broken again for some reason

The problem was the timeout. Need to rethink that a little.

Not applying the ssr timeout limit seems to be the most sensible thing to do.


Play 2.3

It would be nice to see this template use Play 2.3 instead of Play 2.2, the migration is not easy for someone not familiar with Play.

it already in 2.3.6

@alexchooi it is on Play 2.2.3 https://github.com/gilt/activator-gilt-app/blob/master/project/plugins.sbt


feat(sentry): add SENTRY_PROJECT & SENTRY_URL

Overview

Added configuration for SENTRY_PROJECT & SENTRY_URL env vars. [Docs]
Type of change

[ ] Created a new plugin
[x] Improved an existing plugin
[ ] Fixed a bug in an existing plugin
[ ] Improved contributor utilities or experience

Related Issue(s)

Resolves: #
Relates: #

How To Test

Run sentry-cli info. The configured values for SENTRY_PROJECT & SENTRY_URL should show:
Sentry Server: https://sentry.io
Default Organization: acme
Default Project: example

Authentication Info:
  Method: Auth Token
  User<EMAIL_ADDRESS>  Scopes:
    - event:admin
    - event:read
    - member:read
    - org:read
    - project:read
    - project:releases
    - team:read

Changelog

Added support for SENTRY_PROJECT & SENTRY_URL.

Thanks for your contribution 🙌  Looks good!


Module build failed: Error: Final loader (unknown) didn't return a Buffer or String

Bug report

What is the current behavior?
Webpack 5.1.0 throws an error on compile, while webpack 4.44.2 completes successfully:
ERROR in #web/bundles/sonatacore/vendor/select2/select2.css
Module build failed: Error: Final loader (unknown) didn't return a Buffer or String
    at processResult (/home/app/src/node_modules/webpack/lib/NormalModule.js:592:17)
    at runLoaders (/home/app/src/node_modules/webpack/lib/NormalModule.js:669:5)
    at /home/app/src/node_modules/loader-runner/lib/LoaderRunner.js:404:3
    at iterateNormalLoaders (/home/app/src/node_modules/loader-runner/lib/LoaderRunner.js:233:10)
    at processResource (/home/app/src/node_modules/loader-runner/lib/LoaderRunner.js:227:3)
    at iteratePitchingLoaders (/home/app/src/node_modules/loader-runner/lib/LoaderRunner.js:171:10)
    at runLoaders (/home/app/src/node_modules/loader-runner/lib/LoaderRunner.js:395:2)
    at NormalModule.doBuild (/home/app/src/node_modules/webpack/lib/NormalModule.js:624:3)
    at NormalModule.build (/home/app/src/node_modules/webpack/lib/NormalModule.js:768:15)
    at module.needBuild (/home/app/src/node_modules/webpack/lib/Compilation.js:1083:12)
    at NormalModule.needBuild (/home/app/src/node_modules/webpack/lib/NormalModule.js:969:32)
    at Compilation._buildModule (/home/app/src/node_modules/webpack/lib/Compilation.js:1066:10)
    at hooks.beforeStart.callAsync.err (/home/app/src/node_modules/webpack/lib/util/AsyncQueue.js:235:10)
    at Hook.eval [as callAsync] (eval at create (/home/app/src/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at AsyncQueue._startProcessing (/home/app/src/node_modules/webpack/lib/util/AsyncQueue.js:228:26)
    at AsyncQueue._ensureProcessing (/home/app/src/node_modules/webpack/lib/util/AsyncQueue.js:218:9)
    at runCallback (timers.js:705:18)
    at tryOnImmediate (timers.js:676:5)
    at processImmediate (timers.js:658:5)
 @ ./src/Evp/Bundle/AdminBundle/Resources/assets/standard-layout/style.js 1:219-278

the contens of style.js:
import 'font-awesome/css/font-awesome.css';
import '#web/bundles/sonatacore/vendor/ionicons/css/ionicons.css';
import '#web/bundles/sonatacore/vendor/eonasdan-bootstrap-datetimepicker/build/css/bootstrap-datetimepicker.css';
import '#web/bundles/sonatacore/vendor/select2/select2.css';
import '#web/bundles/sonatacore/vendor/select2-bootstrap-css/select2-bootstrap.min.css';
import '#web/bundles/sonataadmin/vendor/admin-lte/dist/css/skins/skin-black-light.css';
import '#web/bundles/sonataadmin/vendor/jqueryui/themes/base/jquery-ui.css';
import '#web/bundles/sonataadmin/vendor/iCheck/skins/square/blue.css';
import '#web/bundles/sonataadmin/vendor/admin-lte/dist/css/AdminLTE.css';
import '#web/bundles/sonataadmin/vendor/x-editable/dist/bootstrap3-editable/css/bootstrap-editable.css';
import '#web/bundles/sonataadmin/css/styles.css';
import '#web/bundles/sonataadmin/css/layout.css';
import '#web/bundles/sonataadmin/css/tree.css';
import 'bootstrap3-wysihtml5-bower/dist/bootstrap3-wysihtml5.css';
import '#evp_admin/standard-layout/less/backend_theme.less';

the webpack.config.js part regarding styles looks like this:
            {
                test: /\.(css|less|scss)$/i,
                exclude: modulePath => /ckeditor5-/.test(modulePath),
                use: [
                    {
                        loader: MiniCssExtractPlugin.loader,
                    },
                    {
                        loader: 'css-loader',
                        options: {
                            sourceMap: true,
                        },
                    },
                    {
                        loader: 'postcss-loader',
                        options: {
                            postcssOptions: {
                                plugins: [
                                    [
                                        'postcss-preset-env',
                                    ],
                                ],
                            },
                        },
                    },
                ],
            },
            {
                test: /\.less$/i,
                enforce: 'pre',
                use: [
                    {
                        loader: 'less-loader',
                        options: {
                            sourceMap: true,
                        },
                    },
                ],
            },
            {
                test: /\.scss$/i,
                enforce: 'pre',
                use: [
                    {
                        loader: 'sass-loader',
                        options: {
                            sourceMap: true,
                        },
                    },
                ],
            },

package.json:
    "cache-loader": "^4.1.0",
    "bundle-loader": "^0.5.6",
    "babel-loader": "^8.1.0",
    "css-loader": "^5.0.0",
    "exports-loader": "^1.1.1",
    "expose-loader": "^1.0.1",
    "file-loader": "^6.1.1",
    "image-webpack-loader": "^7.0.1",
    "imports-loader": "^1.2.0",
    "null-loader": "^4.0.1",
    "less-loader": "^7.0.2",
    "raw-loader": "^4.0.2",
    "sass-loader": "^10.0.3",
    "script-loader": "^0.7.2",
    "style-loader": "^2.0.0",
    "worker-loader": "^3.0.4",
    "postcss-loader": "^4.0.4",

    "mini-css-extract-plugin": "^1.0.0",
    "optimize-css-assets-webpack-plugin": "^5.0.4",
    "terser-webpack-plugin": "^4.2.3",

    "webpack": "^5.1.0",
    "webpack-cli": "^3.3.12",
    "webpack-dev-server": "^3.11.0",

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/vbartusevicius/webpack5-final-loader-null

What is the expected behavior?
It should compile the assets.

Other relevant information:
webpack version:  5.1.0
Node.js version: 10.18.1
Operating System: Linux c26e1fafd4c7 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Additional tools: n/a

Thanks for your report. It would be great if you reduce your issue to a small reproducible example. Best put this example into a github repository together with instructions how to get to the problem.

Problem in image-webpack-loader, please migrate on https://github.com/webpack-contrib/image-minimizer-webpack-plugin, also please do not use optimize-css-assets-webpack-plugin, migrate to https://github.com/webpack-contrib/css-minimizer-webpack-plugin, feel free to feedback

Installed "css-minimizer-webpack-plugin": "^1.1.5", "image-minimizer-webpack-plugin": "^1.0.0"
Removed "image-webpack-loader" and "optimize-css-assets-webpack-plugin"
The result is still the same:
Module build failed: Error: Final loader (unknown) didn't return a Buffer or String

I also see some warnings:
(node:10523) [DEP_WEBPACK_COMPILATION_NORMAL_MODULE_LOADER_HOOK] DeprecationWarning: Compilation.hooks.normalModuleLoader was moved to NormalModule.getCompilationHooks(compilation).loader
(node:10523) [DEP_WEBPACK_COMPILATION_OPTIMIZE_CHUNK_ASSETS] DeprecationWarning: optimizeChunkAssets is deprecated (use Compilation.hook.processAssets instead and use one of Compilation.PROCESS_ASSETS_STAGE_* as stage option)
(node:10523) [DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET] DeprecationWarning: Compilation.chunks was changed from Array to Set (using Array method 'reduce' is deprecated)
(node:10523) [DEP_WEBPACK_COMPILATION_ASSETS] DeprecationWarning: Compilation.assets will be frozen in future, all modifications are deprecated.
BREAKING CHANGE: No more changes should happen to Compilation.assets after sealing the Compilation.
	Do changes to assets earlier, e. g. in Compilation.hooks.processAssets.
	Make sure to select an appropriate stage from Compilation.PROCESS_ASSETS_STAGE_*.

how could I trace the corrupted loader here?

@vbartusevicius some plugin doesn't have compatibility with webpack@5, if you want to help please provide reproducible test repo  (or configuration(s))

@evilebottnawi - I will try to.
Maybe you also could give me a little hint where I should put console.log to quickly identify the broken plugin?

No, because i don't know your configuration

@evilebottnawi - please check the reproducible repo: https://github.com/vbartusevicius/webpack5-final-loader-null

Reproduced, WIP

Notes:

you don't need cache-loader with webpack@5, look at https://webpack.js.org/configuration/other-options/#cache, image-minimizer-webpack-plugin respect this option
https://github.com/webpack/webpack-dev-server/issues/628 fixed
Do not override resolve.extensions and resolve.modules
Avoid using cacheDirectory and cacheCompression for babel-loader, this makes no sense
You have deprecations warnings, please open issues in repos which is not fix compatibility with webpack@5

And main answer, do not use # in imports, because it is wrong, in import you use URL, #test is fragment (hash) of url

I can provide more information and a link to the specification if you want to see it

Thanks, so basically we need to change # to something different, like ! or * not related to the URL spec?
Would gladly see more information.

Thanks, so basically we need to change # to something different, like ! or * not related to the URL spec?

Avoid using special characters, because not all file systems supports it, just use web/

Would gladly see more information.

What exactly would you like to know?

I can provide more information and a link to the specification if you want to see it

I think we moved to # prefix because otherwise, the esilnt complains about missing package #web/bundles vs web/bundles - no such package web

Thanks!

Upgrading from Webpack 4 to Webpack 5 , alias starting with '#' does not work. https://github.com/webpack/webpack/issues/11705#issuecomment-712875972 mentions that we should not use '#'. Is this a change in behavior in Webpack 5?


Not working with Xeus Python kernel (Jupyter with debugger)

The extension does not work when I use a xeus python kernel, which is the current official way to use the Jupyter debugger (https://jupyterlab.readthedocs.io/en/stable/user/debugger.html). On the same server, the extension works correctly with any classic python kernels.
Is this expected? It would be great to have both the debugger and the variable inspector with the new xeus kernel.

I can confirm this

I can confirm this

Currently the xeus kernel is not supported, since it only implements a subset of features of the regular IPython kernel. This extension relies on some of the IPython magics that are not yet supported by xeus.
This does not mean that it's not impossible to make this extension work with xeus, but one would need to write a new script that communicates between xeus-kernel and the variableInspector extension (e.g. as in src/inspectorscripts.ts).
Since I currently do not know how to retrieve active variables in xeus outside of the debugger mode, I'll leave this issue as a open todo.
But of course, if you come up with a solution I'm happy to add it to the extension.


Support page-level comment permissions

hi
two question:

how to allow user to comment page but without whole page edit permisions?

how to allow user to edit / delete own comments?

Hi @akurzawa,
Have you tried using the available role-level permissions for your requirements?:

Well later yes, it works - GLOBALLY, but now I'm trying to disable comments in one page - any idea how to do that?

@akurzawa Sorry for my late response. Currently there is no way to do this. I'll update the title of this issue to focus on that request to see if this is a feature that others would be interested in.

any changes in this matter?

I'm going to close this off since there's been little additional request for comment permissions, and I'd prefer not to add further complexity with more fine-grained comment permissions where possible.
On recent releases, you could visually hide the comments at a per-page level (For all users) by using tags and some custom CSS. I can provide an example, and further details, of this upon request if desired.


feat(cmd/influx): add profile management

Closes https://github.com/influxdata/influxdb/issues/15302
add multiple profiles feature as suggested in the ticket
add the ability to setup against another cluster, even if you have a profile file

[x] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[ ] http/swagger.yml updated (if modified Go structs or API)
[x] Documentation updated or issue created (provide link to issue/pr)
[x] Signed CLA (if not already signed)

@kelwang could you drop a demo of this in channel before merging? I think it'd be valuable to get feedback on the CLI UX from the team.


[DRAFT] Add tegra arm_variant_type

Just an experiment related to https://github.com/conda-forge/pytorch-cpu-feedstock/issues/303 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ The recipe is not parsable by parser conda-souschef (grayskull). Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.
ℹ The recipe is not parsable by parser conda-recipe-manager. Your recipe may not receive automatic updates and/or may not be compatible with conda-forge's infrastructure. Please check the logs for more information and ensure your recipe can be parsed.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12279986261. Examine the logs at this URL for more detail.

@conda-forge-admin please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12280136149. Examine the logs at this URL for more detail.


Request for releasing OpenSeesMP/SP

Thanks for sharing.
Can you please do the same for MP and/or SP version?
As you may know, Official release of OpenSees MP/SP has not been updated for a long time.

Hi @najafice ! I didn't compile these, I just downloaded them from the OpenSees website, and packaged them in an installer for easy installation with ActiveTcl.


Error running config for nvim-ts-autotag: [string "..."]:0: loop or previous error loading module 'nvim-ts-autotag'

As title, I'm using Packer.nvim and I got error:
Error running config for nvim-ts-autotag: [string "..."]:0: loop or previous error loading module 'nvim-ts-autotag'

How to ensure the treesitter loading first?

@issadarkthing: Try packer.nvim requires~

It doesn't work. This is my current setup for nvim-ts-autotag
  use {
    'windwp/nvim-ts-autotag',
    opt = true,
    ft = 'typescriptreact',
    requires = {{'nvim-treesitter/nvim-treesitter'}},
    config = function() require('nvim-ts-autotag').setup() end,
  }

@issadarkthing: I was busying clean out issues. Then you can try mine, which has to work :)
  use {
    'windwp/nvim-ts-autotag',
    branch = 'main',
    requires = {
      'nvim-treesitter/nvim-treesitter',
    },
    config = function ()
      require('nvim-ts-autotag').setup()
    end
  }

The error is gone now but it still doesn't auto-complete

@issadarkthing: I think the problem is on 'nvim-treesitter/nvim-treesitter'. You will need to add a standalone use { ... } for 'nvim-treesitter/nvim-treesitter'. I can provide you my config after work.

Alright sure


Search location validation

did NOT include the full street address....only City,ST and Zipcode....

New PR being created to resolve merge conflicts


Move Desmos val to own hw

Setup node
setup monitors
move validator key

Issue moved to bro-n-bro/bro_infra #73 via Zenhub


Prepare to update branch to main

Fixes #32

After merging, is it ok to switch default branch from master to main? @Keboo

No objections, just double check to make sure any branch policies are also recreated.

@Keboo any idea on why this continuous integration won't finish? I can't merge until it does

ouch, that looks like it is pointed at a really old appveyor pipelines (long since dead). I removed the web hook for it

There, removed the appveyor status check requirement. Looks like just the build failure is blocking now.

Looks like the last build on main was already failing so probably due to a previous issue as the issues listing for failure are the same as the previous build on main

@Keboo Looks like the last build on main was already failing so probably due to a previous issue as the issues listing for failure are the same as the previous build on main so I could just keep the failure and merge and just switch the branches since it seems like this project isn't being kept the most up to date unless we want to try and fix it first.

I am fine with that, but lets log an issue to get it fixed.


Q: Support for the Q.noConflict() method.

See also #4728

@msallin thanks mate!

note
https://github.com/kriskowal/q/blob/75058c0d70d36dd7e814c13493866043df39c858/q.js#L70


Replacing with new PR.


Serialize F# struct unions as a normal struct (flatten the case fields)

F# 4.1 allows discriminated unions to be represented as structs. In such unions, all case fields must have names that are unique across all cases.
I suggest that such unions should by default (or at least optionally) be serialized as a normal struct/class instead of using the special union serialization. This would make it much easier to make the serialized result of unions more compatible with other languages that don't have any concept of unions.
For example, given the following type and values:
[<Struct>]
type Foo =
  | Case1 of foo: int
  | Case2 of bar: float * baz: string

let foo1 = Case1 2
let foo2 = Case2 (3.0, "qwerty")

Values should be serialized like this:
{
  Case: "Case1",
  foo: 2
}

{
  Case: "Case2",
  bar: 3.0,
  baz: "qwerty"
}

These serializations are much easier to deserialize in other typed languages that don't have any concept of unions; for example, this C# class:
class Foo {

  enum Case { Case1, Case2 }

  public Case Case { get; set; }
  public int Foo { get; set; }
  public double Bar { get; set; }
  public string Baz { get; set; }
}

Note that the C# example above could cause problems when going the other way, since by default (AFAIK) Case would be serialized as an int. I therefore suggest that when deserializing to the F# Foo type, both case names (string) and tags (ints) are handled.

Respectfully, I opened a new issue that is similar to your open issue here but I felt different enough in aspects of its intent to warrant a separate issue. I had some problems with your proposed change that I reference in my new open issue which I would appreciate input on.
I hope I didn't break github protocol here as this is actually the first issue I've opened. Thank you.

Great! Your suggestion has more thought behind it than mine, so I'm closing this. Contrary to what I originally suggested though, I don't see the point of serializing the Case, since the fields alone are sufficient for Struct unions. Left a comment on your issue.


FirebaseError: Type does not match the expected instance... different Firestore SDK?

I'm working on an app in Nextjs 12 and everything appears to be working fine but I keep getting this error at build time about a different Firestore SDK:
error - unhandledRejection: [FirebaseError: Type does not match the expected instance. Did you pass a reference from a different Firestore SDK?] {
  code: 'invalid-argument',
  customData: undefined,
  toString: [Function (anonymous)]
}

Everythig compiles and the site works fine aside from this error but I'd like to understand the problem if possible. Sorry I don't have much more to share, the error doesn't indicate much.
Here's more on my env:
    "@react-query-firebase/firestore": "^1.0.0-dev.7",
    "firebase": "^9.9.3",
    "next": "12.2.5",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-query": "3.*"

Edit: Should add that I am working in JS not TS.

I have the same issue

Same here, did someone solve this problem?

relevant: https://stackoverflow.com/a/69242591/10577976
i guess no one is going to update this lib to support project who using the modular firebase sdk.

I ran into the same issue and realized that I was importing collection and docs from firebase lite instead of firebase


Unable to set Name of ebs_volume

EBS Volumes in the AWS Console have a "name" attribute, but the ebs_volume resource doesn't allow it to be set.  This makes it hard ot keep track of the volumes in our account.
The "name" attribute should be added to the ebs_volume resource.

You tag it with resource_tag the volume_id, as documented with an example even ;)

And how do we determine the id of the volume we just created? I have a volume I created with aws_ebs_volume  and would like it to have a friendly name tag, but I can't assign it without knowing the volume id I just created.
It's a chicken and egg issue.

@dreamnite after the volume is created, the volume ID is set back in the configuration. See https://github.com/chef-cookbooks/aws/blob/master/providers/ebs_volume.rb#L46
You can then read it from node['aws']['ebs_volume'][new_resource.name]['volume_id'].
However, note that the volume ID will only be persisted in your configuration if you are running Chef Server.  If you are running Chef Solo, the volume ID will be forgotten as soon as Chef finishes running.


Latest pubsub version breaks dependencies with grpc (doesn't use common-grpc package)

Environment details

OS: Linux
Node.js version: 8.7.0
npm version: 5.4.2
google-cloud-node version:

Steps to reproduce
Try use the latest versions of @google-cloud/datastore and @google-cloud/pubsub together.
Because the latest version of @google-cloud/pubsub includes grpc as a direct dependency instead of using the package which seems to have been created for linking grpc together between libraries (@google-cloud/common-grpc), the versions of GRPC are clashing and causing problems such as #2667
To get my project working I had to revert to @google-cloud/pubsub:0.14.2
It appears to have been changed during this commit: #2627

I can reproduce with the following in my package.json:
"@google-cloud/pubsub": "^0.14.5",
"grpc": "^1.6.6",

Fixing @google-cloud/pubsub:0.14.2 worked for me too.

I think I'm seeing something related using PubSub on GCF with @google-cloud/pubsub:0.14.6:
var Buffer = require("safe-buffer").Buffer;
var pubsub = require('@google-cloud/pubsub')();

exports.publish = function publish(event, callback) {
    var topic = pubsub.topic('outbound-topic');
    var publisher = topic.publisher();
    var message = new Buffer('New message!');
    publisher.publish(message, function(err, data) {
        callback(err, data);
    });
};

Throws the following error:
info: Function crashed
info: TypeError: message.encode(...).finish is not a function
    at BundleDescriptor.getByteLength [as byteLengthFunction] (./node_modules/google-gax/lib/grpc.js:262:36)
    at ./node_modules/google-gax/lib/bundling.js:338:38
    at Array.forEach (native)
    at BundleExecutor.schedule (./node_modules/google-gax/lib/bundling.js:337:16)
    at ./node_modules/google-gax/lib/bundling.js:474:20
    at Canceller.call (./node_modules/google-gax/lib/api_callable.js:110:19)
    at Bundleable.call (./node_modules/google-gax/lib/bundling.js:473:12)
    at ./node_modules/google-gax/lib/api_callable.js:356:17

cc @jsididris who reported this in #2717.

@lostpebble I just cut a new patch release. If upgrading to that package does not fix your issue, feel free to re-open.

@lostpebble RE: #2738, I take it this didn't help anything?
rm -rf node_modules
npm cache clean
npm install

@stephenplusplus I copied my project over to a fresh space and reinstalled all modules and it seems to be working fine now. Thanks!
Although, my actual dev environment is a yarn workspace - which seems to be getting confused about where to place the dependencies. I'll have to look into it a bit more.

@stephenplusplus So, through a lot of trial and error, trying every yarn command known to man and failing, and eventually having to just modify the yarn.lock file directory directly, I eventually got my project to see grpc:1.7.1 as a root dependency and PubSub loads up without that error now.
But I am seeing a new strange error popping up:
TypeError: grpc.forcePoll is not a function

Which I've tracked to this line of code in grpc-node : https://github.com/grpc/grpc-node/blob/2b538ca0217638b3f0f45158b53eb9cd912381fb/packages/grpc-native-core/src/client.js#L805
This happens after setting up and adding listeners to PubSub.
The listeners are working however and everything seems fine otherwise... So going to roll with it for now. Could be the client not initialising properly the first time, but seems to start up anyway after that.

That doesn't sound good.
@callmehiphop any ideas?

@stephenplusplus that definitely looks like an internal grpc error, maybe we should pin grpc to 1.6?

Although, maybe a better move would be to rewrite the IAM sections using GAX and cut the dependency on common-grpc altogether.
@lukesneeringer do we have timing for when PubSub will become its own repo?

To avoid problems for now, pinning would be a welcome, quick fix. Here are the ways grpc enters a project through the Datastore & Pub/Sub modules:

google-gax<EMAIL_ADDRESS>@google-cloud/common-grpc<EMAIL_ADDRESS>
Do we need to pin to ^1.7.1 (the latest at this time) in both projects?

@stephenplusplus I've decided to just go ahead an convert IAM to gax, pinning a version in both modules is a very fragile solution that has the potential to resurface in the very near future.

Why is it fragile?
The problem seems to be when a project has multiple versions of gRPC required through our dependencies. While removing common-grpc from Pub/Sub gets rid of the extra gRPC for that module, we still have it in Bigtable, for example. So if a project uses Bigtable and Datastore, they could hit these weird version mismatches.

It's fragile in the sense that if we have to pin versions on 2 different modules and anytime one gets updated the other will need a similar update, otherwise we run the risk of seeing this issue again.
If removing common-grpc is a more reliable solution, I think its worth the effort (which in this case is minimal).

I think removing common-grpc is a better solution. I'm only concerned about the effort causing a long wait time for the people whose apps aren't working properly. Unless you think I'm over-estimating the amount of affected users / the effort?
I went digging for common-grpc usage:

Bigtable

Operation()
Service.decorateStatus_()
Bigtable extends Service
Cluter extends ServiceObject
Family extends ServiceObject
Instance extends ServiceObject
Row extends ServiceObject
Table extends ServiceObject

Datastore -- will not need it after repo split is complete
Firestore

Firestore extends Service

Logging

Service.structToObj_()
Service.objToStruct_()

Spanner

Operation()
Service.decodeValue_()
Service.encodeValue_()
Spanner extends Service
Database extends ServiceObject
Instance extends ServiceObject
Session extends ServiceObject

Have you guys considered perhaps just making grpc / common-grpc a peerDependency in all those modules? Leave it up to the user to keep a single version of grpc up to date (should get warnings and be pointed out by yarn or npm on which versions are required).
I've used that tactic in my datastore library to prevent multiple versions of datastore being included and causing issues. It's the case in a lot of libraries actually, when you have multiple modules requiring some dependency, things usually get messy and peerDependencies are sometimes the best way to mitigate it.

Ah, got it. Hard to say, we haven't really gotten any issue reports about this being a problem outside of PubSub, so I just assumed they were ok. Maybe fix PubSub for now and if this resurfaces elsewhere we can talk about trying to pin the versions?

That sounds like a good plan. It also wouldn't hurt to update the google-gax and common-grpc dependency ranges to ^1.7.1, so that npm doesn't pull an older version from cache to satisfy either. Having those in sync should be enough to fix this issue.
Also, if anyone is listening in here, let us know if you've had any problems using two @google-cloud modules at the same time.
@lostpebble fortunately, we're heading towards getting rid of the common-grpc module, which will save us from the peerDependencies headaches. 😌

To state simply what the problem is: it's possible to load multiple versions of gRPC. And these versions do not always play nicely together.
That leaves two logical solutions:

Make sure the versions you install are the same version (good)
Only install it once (best)

Someday, we will accomplish #2. @google-cloud/common-grpc will disappear. Until then, we have to do #1.
google-gax will update with the newest gRPC soon (https://github.com/GoogleCloudPlatform/google-cloud-node/issues/2699), and I'm about to release @google-cloud/common-grpc that depends on the newest gRPC as well.

Oh, and one more DIY solution, should this problem arise in the future:
$ npm rm -rf node_modules
$ npm cache clean
$ npm install

This should force npm to install the same gRPC versions, and not pull anything from the cache.

yarn users need to make sure to remove the yarn.lock file before re-installing since otherwise yarn.lock might lock grpc down to an old version. Same might apply to package-lock.json which was introduced by npm5?!
@stephenplusplus I believe that @google-cloud/pubsub will have to be bumped once again to use a new google-gax version as soon as https://github.com/googleapis/gax-nodejs/pull/158 has been merged?


Fix DI lookupDnsLink function

Summary
This PR fixes the following bugs

[x] Fixes the DI lookupDnsLink function

After Merge

[ ] Does this change invalidate any docs or tutorials? No
[ ] Does this change require a release to be made? Yes, we should release a patch with this change

Already merging this to avoid changelog merge conflicts.


removed contributor tag! section  #4601

Description of the change:
removed contributor tag! section
Closes #4601

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thank you so much for your work on this PR! Our policy is to accept the first and best PR for each page, and this PR has already been completed. I am going to post several more issues very similar to this for our new services today - so look for those!


fix(partialstringmatch): allow class components without children

Proposed Changes
It seems the PartialStringMatch was breaking when trying to render class components that had no children such as the Loading.
Potential Breaking Changes
None.
Acceptance Criteria

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

Codecov Report

Merging #1475 into master will decrease coverage by <.01%.
The diff coverage is 93.33%.

@@            Coverage Diff             @@
##           master    #1475      +/-   ##
==========================================
- Coverage   98.99%   98.98%   -0.01%
==========================================
  Files         496      496
  Lines       10281    10290       +9
  Branches     2370     2374       +4
==========================================
+ Hits        10178    10186       +8
- Misses        103      104       +1

Impacted Files
Coverage Δ

...ges/react-vapor/src/components/loading/Loading.tsx
100% <100%> (ø)
:arrow_up:

...onents/partial-string-match/PartialStringMatch.tsx
100% <100%> (ø)
:arrow_up:

...s/partial-string-match/PartialStringMatch.spec.tsx
98.43% <87.5%> (-1.57%)
:arrow_down:

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 2c33292...6fe24be. Read the comment docs.


Use UMD Modules

Currently the wrapper generates a "plain" JS module library, which doesn't play well with webpack. The kotlin standard lib and kotlinx-html both use UMD, which might be a safer choice.
Really this just requires adding
compileKotlin2Js {     kotlinOptions.moduleKind = "umd" }
to build.gradle. I could make a pull request if desired.

I'm only a hobby JS user, so I have no experience with JS package managers.
After adding this, do I have to make changes how I load JS in i.e. https://github.com/markaren/three.kt/blob/master/example/web/hello_world.html ?

You shouldn't have to. In a non-module environment, it should fall back to plain.

Then I'm happy to accept your PR. Target the dev branch

Applied through pull request #11
Included in release ALPHA-5


outdated information

This page In general needs updation. Specifically the SPFX store options now exists so can be included.

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

ID: f553eaa8-5792-3bdf-d9a8-dcbfc92e53ab
Version Independent ID: e16322c4-8793-4f20-bc6a-984b78c1b403
Content: SharePoint Framework (SPFx) enterprise guidance
Content Source: docs/spfx/enterprise-guidance.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Microsoft has not published any plans around SPFx & a store at this time... not sure what you're referring to.


Add onError hook

It would be nice to hook onto and handle situations where a particular action has a validation failure. Perhaps, this can be called onValidationError, and this allows the validation error to be intercepted and processed by the the application. For instance, a use case could look like:
export const config = createSimpleConfig({
    hooks: {
        onValidationError: async ({ client, error }) => {
              client.emit("error", transformErrorIntoMessage(error);
        },
        ...
    },

    emission: {
         error: {
            schema: z.tuple([ErrorMessageSchema]),
        },
     },
     ...
}

yeah, good idea


What if I'd like to use own dataset

Thanks for great sources.
I want to try to implement this with my own dataset, so I'd like to ask you guys which settings or configuration I should change.
What I am thinking of are, config file and dataset path (annotated in Pascal VOC ideally).
Is there any other things that I should take care of?
Thank you.

Hi,
there are a couple of steps needed to do this:

First, please go thru the "dataset catalog", which lists all the
available datasets, annotations and paths

https://github.com/AruniRC/detectron-self-train/blob/master/lib/datasets/dataset_catalog.py
(a new dataset needs to be added to this catalog)
Main things to note are, each dataset consists of an IM_DIR, a root
folder where images are saved, and a ANN_FN or annotation file, in JSON
format, which contains training annotations such as bounding boxes, class
labels and paths to images (these image paths are relative to IM_DIR).

Creating the JSON annotations file (ANN_FN needs to point to this).
The Detectron training pipeline accepts annotations in a particular
JSON format compatible with MS-COCO.
It's best to look at a few examples to get an idea on how to do this:
(i) converting face detection annotations (bboxes) to json:
https://github.com/AruniRC/detectron-self-train/blob/master/lib/datasets/wider/convert_face_to_coco.py
(ii) Converting Cityscapes dataset into COCO format JSON:
https://github.com/AruniRC/detectron-self-train/blob/master/lib/datasets/cityscapes/cityscapes_to_json.py

hope that helps~!
Aruni Roy Chowdhury
http://people.cs.umass.edu/~arunirc/
On Thu, Jan 2, 2020 at 9:15 PM Hyeonsoo Moon<EMAIL_ADDRESS>wrote:

Thanks for great sources.
I want to try to implement this with my own dataset, so I'd like to ask
you guys which settings or configuration I should change.
What I am thinking of are, config file and dataset path (annotated in
Pascal VOC ideally).
Is there any other things that I should take care of?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AruniRC/detectron-self-train/issues/14?email_source=notifications&email_token=AAIBQT5SD3UEORDI3KPOE5DQ32NSPA5CNFSM4KCIX5A2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IDZLN4A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIBQT4TNZQRB2EPBH2FYZTQ32NSPANCNFSM4KCIX5AQ
.

Dataset catalog guides me perfectly.
I will try following this script.
Thanks a lot for quick response!

Which file yaml i need to change to select my dataset? which config i need to run with python?
thanks


Remove all traces of google+

It has been discontinued in 2019, roughly 4 years ago, so there is no need to keep its icon and CSS around.

Good point! Thanks.


[Bug]: CAN ANYONE PLS HELP

Version of the software
0.2.5
Operating system
Windows 11
Browser / Native
Native
What happened?
Please give me the correct WORDLIST TYPE
is it input.USER & input.PASS
or
input.USERNAME & input.PASSWORD
Well i tried many things nothing seems to work, Default, neither Credentials.
What seems to be the ISSUE here
[IDLE] CompilationErrorException: (45,94): error CS1525: Invalid expression term '/'

Pls pass me the correct WORDLIST TYPE
I am using the original, heck i even re downloaded the Native and extract the Environment.ini and replace with the modified i had

Relevant LoliCode if needed
No response

Please refer to the docs https://docs.openbullet.dev/docs/wordlists/general-info


[Question] install related, space in dir name won't work.

There is no merge of Windows install and Mac install, so I want to move the whole project to Google drive. IN this case, I can use my Windows at home and still do bot when I go to library with my Mac laptop. And I don't have to change auth and config every time.
I installed in Google Drive directory. However, terminal does not recognize the space between "Google Drive".
I used ... instead of my actual dir name.
$ pip install -r requirements.txt --upgrade
-bash: /Users/.../Google Drive/bot/bin/pip: "/Users/.../Google: bad interpreter: No such file or directory
(bot) xxxxx:bot ...$ pip install -r ./requirements.txt --upgrade
-bash: /Users/.../Google Drive/bot/bin/pip: "/Users/.../Google: bad interpreter: No such file or directory

This is not about Pokemon Go Bot... This is about "PIP" command btw python's problem.. Google for this issue.
Try to change folders name.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/478 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 9dba806:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in https://SiteHelp and include the URL of publishing report as well as below information: One or more errors occurred..

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


only position bindings if bindings

if you have a query with a '?' mark in it, it is replaced with a numbered param for pg prepared statements.
if you provide no bindings your queries are not run as a prepared statements and ? should be preserved in text fields.
...
trx.raw("insert into table(name) values('foo?');")
...
right  now this will insert a row in your "table" table with a name value of "foo$1"
select * from table;
[name]
foo$1

after this fix "?" is preserved as it should be.
note: you cannot use bindings when you are running batch queries/ multiples statements so you will have a time where you need to pass escaped user input in the sql string.

Hi @soldair. Thanks for the PR. Sounds like a reasonable change. Would you be able to test coverage for the previous problem for posterity?

Sounds like the same issue with #519 and old pull request to fixit, which was never taken in https://github.com/tgriesser/knex/compare/qs-escapement

happy to write the test :)
ill take a peek at the other pull to see if it's better

@soldair Thanks mate. I'm actually not very familiar with the knex code base - just been granted collaborator status because I'm working on Bookshelf. So I have to be cautious with what I let through. Thanks for understanding.

@soldair Just a thought, but this correction could be taken further to make the variable substitution smarter. If I understand correctly this would still break with your fix:
trx.raw("insert into table(id, name) values(?, 'foo?');", [5])

Not sure of the exact rules that would be correct. Perhaps just checking for ?s enclosed in quotes.
Anyway, happy to take the less complete fix of course.

you are correct. it will still break you will have to pass 'foo?' as a bound param.
I'm going to stay away from more complicated parsing for now because i don't have the time to take the security implications into account. I'll ping again when i have the tests.
Hindsight but.. I think raw should build a plain query not a prepared statement and perhaps a prepared statement should be another call on its own because it impacts the kinds of queries postgres allows. Most notably only allowing single statements per call to query.

@soldair Cool. Beyond my code base knowledge, I just wanted to mention that for consideration. Any work here is welcome and I'm happy to merge future PRs. Cheers! :+1:

you know. its an sql error to provide a mismatch in the number of bound params than placeholders i think. so that case should bubble as an error.

i still have to figure out the right way to add tests for this.

I did some digging and wrote new suggestion how to handle this with allowing question mark escape sequence and based on @tgriesser's fix for #519. @soldair will this work for your problem as well?

will be resolved by merging #946

Okay, I'll close this one. Thanks guys.


Render prompt success template once prompt completes

As mentioned in #70 Success template in PromptTemplates is never rendered when prompt completes

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


httpclient usage recommendations for Azure Functions

The documentation currently wraps the instantiated httpclient in a using statement.  Since can be multiple functions running concurrently, what's the guidance going forward now that Microsoft is not recommending directly creating httpclient per request especially in high volume cases (https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/implement-resilient-applications/use-httpclientfactory-to-implement-resilient-http-requests)
using (var client = new HttpClient())
    {
        var response = client.PostAsync(logicAppUri, new StringContent(myQueueItem, Encoding.UTF8, "application/json")).Result;
    }

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

ID: 7743df92-031d-2bbb-6b28-6b43380b6ac4
Version Independent ID: 08ea82c4-1336-98e4-c9d5-48a9242a6187
Content: Scenario - Trigger logic apps with Azure Functions and Azure Service Bus
Content Source: articles/logic-apps/logic-apps-scenario-function-sb-trigger.md
Service: logic-apps
GitHub Login: @ecfan

@Miggleness Thank you for posting your question. We will review this and provide an update as appropriate.

@Miggleness You are right. This doc is meant to be more of a showcase of how you can include Azure Functions in your Logic Apps but not a best practices example.
You can find more details about Managing Connections in Azure Functions in its official doc.

@Miggleness Just following up here... Hope my previous comment helps.

@Miggleness Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Thanks for the confirmation @PramodValavala-MSFT
I've sent a PR to update the docs example to align with Microsoft's recommendation.


Don't bring Catch2 with tests

We should refactor out the copy of the Catch2 library.
We could probably use a find_package(Catch2) in the corresponding cmake or something similar.
I'm going to look for a solution.

Maybe download this library by url?

PR #10


feat: Use target rather than dialect

Closes #1388.
Includes a changelog entry!

It's not that important now, but within sql module and sql::Options, dialect is more appropriate than target, I think.

It's not that important now, but within sql module and sql::Options, dialect is more appropriate than target, I think.

Yes I think you're probably right. I won't do the refactor now in case there are more changes coming there, but happy to step up in the future assuming it's still needed.


fix unique keys for react components

fixes https://github.com/demisto/etc/issues/42605
screenshot:
after fix:

@yonatan-roth can you please review?

@yonatan-roth test added


Update the bump-version.sh script to function correctly

@mohammedzee1000 mentioned that the script in question is not up-to-date and should be avoided to bump the version.

is this be relevant anymore? we use a different release mechanism post GA. We could consider removing all release related scripts also?

is this be relevant anymore? we use a different release mechanism post GA. We could consider removing all release related scripts also?

:+1:


Update Gemfile to the latest versions

Update Gemfile to the latest versions of required gems
Related to the #162 issue (bundle install fails to work)

More details:

https://github.com/dotfiles/dotfiles.github.com/issues/162

Thanks!

Would you be up for automating the dependency updates? I built Dependabot to automatically create PRs like this one and keep everything up-to-date. (Obviously totally free.)

I'm open to it. This repo doesn't get a ton of activity so it is easy for it to get stale.

Sweet! If you go for Dependabot then it's a GitHub app, so you need to click through the auth process and then click to add this repo as a project. Hopefully all obvious but let me know any feedback.
Here's an example of the PRs it generates.


After authentication, app redirects to home rather than previous URL

It appears that during flow refactoring the string variable redirectOnSuccess was changed to a boolean:
https://github.com/conveyal/datatools-ui/blob/a6cb68607877120d4c4a1f753355ccaa1026ac3d/lib/common/containers/App.js#L68-L70
https://github.com/conveyal/datatools-ui/commit/a755e4546a1196b2c585c4f2e20faacbe3d5d77a#diff-12752f290ea607f91209066fb17cb621

:tada: This issue has been resolved in version 4.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update repository after transfer

See https://github.com/senzing-garage/garage-roadmap/issues/3

Pull requests:

https://github.com/senzing-garage/docker-compose-air-gapper/pull/55


TODO Trigger -- new tags for [[DONE]] state not applied retroactively

For example, I changed my old tag #m to #toMail and now I have plenty of old [[DONE]] #toMail blocks, while I want all such blocks, old a new, to be either [[TODO]] #toMail or [[DONE]] #Mailed.

I think there's a Roam hack you could do to fix this:

Create a [[[[DONE]] #toMail]] page
Rename that page to [[[[DONE]] #Mailed]]
Delete the page

Audit: Won't do


Change coverages to coverage in the API

As a results of this discussions:

https://github.com/opengeospatial/WFS_FES/issues/249
https://github.com/opengeospatial/ogc_api_coverages/issues/25

I became convinced that coverages needs to be replaced by "coverage" in the API.
/collecions/{collectionId}/coverage
(simetric to: /collecions/{collectionId}/items)
Reason 1:
Features are too atomic and need to be aggregated in collections for convenience: e.g. to cover a particular extent. Coverages are already an aggregation of data into a coverage structure: a boxel, a point cloud etc. They also have several "attributtes" represented by "rangeTypes" like features.
To me "coverage" is equivalent to "items". They both cover an extent, represent several attributes and can be queried. It is possible to move from items to a coverage by rasterization and for a coverage to items by vectorization. A point cloud can be transformed into a collection of points in a much more direct way.
Reason 2:
In OGC API coverages the collectionId becomes the coverage name in the same way that the collectionId is the feature collection id in OGC API features. Both can be transformed into maps and tiles using:
/collecions/{collectionId}/map
without even knowing the collection type. It becomes symmetric.
They can also be processed in the OPC API processes without caring about the collection type.
Please note that the need for collections of collections is a completely different discussion that also affects features and should be solved in OGC API Common.
So I'm requesting to change the current orientation of the OGC API coverage to use coverage (in singular) and use the {collectionId} and the name of the coverage.
So:
/collecions/{collectionId}/coverage gets the whole coverage
/collecions/{collectionId}/coverage/rangeSet gets the actual values
/collecions/{collectionId}/coverage/domainSet gets the dimensions definition.

After quite some discussions at the OGC TC meetings in Banff on 20190909 and Toulouse on 20191120 the WCS.SWG agreed to adopt the resource path /collections/{collectionId}/coverage and drop the plural version.
In addition there is a proposal to have more concrete resource types like rectifiedGridCoverage in addition to coverage in the path.


Encoding error

Hey!
First of all I really appreciate you for this repository, it has helped me a lot.
So have a little bug here, after I convert PDF to TEXT I have a text with symbols, I think that is a encoding problem, I have tried fix it but i didn`t make.
Can you help me?

Hello!
I think you might be able to solve this by using the the pdftotext enc option as outlined in this answer
You should be able to quickly achieve that by using it in the constructor of the main class like so:
$parser = new \Wrseward\PdfParser\Pdf\PdfToTextParser('pdftotext -enc ASCII7');


Assignment 6 - Mihai Bojescu

Total: 9 points.
Things you can do to improve the results:

Normalizing using better normalization values.
Data Augmentation (Random Horizontal Flips, Random Vertical Flips, Random Rotates).
Modern architectures (ResNet and newer).
Not using clip_grad_norm_, because you don't have exploding gradients.
Changing the Optimizer from Adam to SGD with Nesterov Momentum, or using Adam but with a lower learning rate $\in (0.00001, 0.0001)$.


CNV Signature definitions

Hello,
After performing the signature extraction on a CNV48 matrix, I have now generated the decomposed signatures. Are there definitions for the CNV1-CNV19 signatures? Where were these signatures derived from?
Thanks for all the hard work and a great tool!

Hello,
We don't have definitions for the CNV signatures publicly available till now.
@lalexandrov1018, do have any idea when we can make CNV signatures publicly available?
Thanks,
Mishu

The reference set of CN signatures are currently under development. The provided set of 19 CN signatures in SigProfilerExtractor is preliminary and should not be used until the reference set of CN signatures is officially published.


Unhandled exception on Mopidy startup - OSX 10.10.3

Hi, just installed using homebrew method, doesn't seem to work with mopidy(latest) and OS X (10.10.3) - following error on mopidy launch:
ERROR    Unhandled exception in NotifierFrontend (urn:uuid:c69e0f78-c53d-412b-9944-973873e4ef5b):
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/pykka/actor.py", line 191, in _actor_loop
self.on_start()
File "/usr/local/lib/python2.7/site-packages/mopidy_notifier/frontend.py", line 27, in on_start
self.notify('Starting...')
TypeError: notify() takes exactly 3 arguments (2 given)
Any ideas ?
Thanks.

This seems to be fixed in commit 6ebe9c94a4e7debe02912bc7d618900a52230983, released in version 0.3.3 back in April.
What version of Mopidy-Notifier do you run? You can find the version number by looking in the output of the command mopidy deps.

Only now did I notice the keyword "Homebrew". I updated Mopidy-Notifier in the Mopidy Homebrew tap from 0.3.2 to 0.3.3 right now. Try running brew update && brew upgrade to update it.

All fixed - homebrew update worked - thanks !
Great stuff on this project :)


How used

Is there a front-end page available? How should it be used?

What are you looking to do?

Is there a front-end page available? How should it be used?

Easy to use go to https://v0.dev/
You can make code by write some thing or take screenshot of any website
Put it and press Enter you will get full source code
Some demo public
https://v0.dev/hoanghohotel
This is products of https://vercel.com
So good and free


New Release

Could we please cut a new release to get these changes landed in pypi?

hi @hinthornw,
Sorry for this, but I am still making some changes to the API, so didn't want to push a new release until I get a stable version.
You can always consider building from source.

@hinthornw, New release v1.0.7 pushed to pypi


Update install.md

Use double quotes on windows for those getting "SyntaxError: EOL while scanning string literal python".

I signed it!

CLA bot may get angry when I hit "update branch". Let's see.

Yup. Overruled!


Terminal does not detect failure in activated environments when activated using PS1 script

OS windows
Expected:

Actual:

Repro steps:

Create a virtual environment using python -m venv .venv.
Activate the virtual environment using the PS1 script in powershell  (i.e., > .venv\Scripts\activate.ps1)
Your prompt now will have (.venv) prepended.
Try to run some module that is not installed: python -m ruff
you get a blue dot instead of the red one.

Likely some conflict caused by activate.ps1. I do see exit code being reported, but it's always 0:


Add a basic bash-completion file.

This uses the --generate-bash completion flag to complete commands and
subcommands.
Resolves #4004.
Also see:
https://github.com/keybase/keybase-issues/issues/147
Let me know if there is a preferred place for a file like this.

This doesn't seem to work very well at the moment, as it only seems to generate subcommands but not --option flags.
Of course, this is not the fault of the completion script itself, merely that --generate-bash-completion... doesn't.
...
Generally, it might be nice if keybase could introspect its own available options, then generate a more specific completion file which does not depend on simply running keybase current_options --generate-bash-completion every time you . Or have the keybase team commit to updating a handwritten completion file whenever the CLI interface is modified.

Right, there's tons of room for improvement here, this is just something to get started (I'm finding it to be an improvement over no completion, at least).

Generally, it might be nice if keybase could introspect its own available options, then generate a more specific completion file which does not depend on simply running keybase current_options --generate-bash-completion every time you

Like kubectl?

source <(kubectl completion bash)

I guess? I don't know what the resulting completion looks like, I cannot track down the relevant code, etc.
I guess it might look like:
https://github.com/justwatchcom/gopass/blob/master/pkg/completion/zsh/template.go
https://github.com/justwatchcom/gopass/blob/master/pkg/completion/zsh/completion.go

I just captured the output of gopass completion bash > keybase-completion-bash and ran sed -i -e 's/gopass/keybase/' keybase-completion-bash and then source keybase-completion-bash and I had at least the main commands covered all the way down as it appears they might be using the same cli.go library.
As previously mentioned this doesn't catch any of the advanced options or additional arguments/flags passed to commands, but that might just be a couple lines changed in various methods to expose those options to the bash completion.

Until this is bundled with either keybase or bash-completion itself, might I suggest creating a keybase-completion formula in Homebrew?


Consider passing Options to all Client methods

(filing an issue so we don't forget about this)
We sometimes need to the ability to pass method-specific options to a client function call. For example:
https://github.com/googleapis/google-cloud-cpp/blob/0b2f1e5f5d3c82747259ea7ba3c3b47b060fc7fc/google/cloud/spanner/client.h#L250-L253
Rather than having a bunch of separate options classes, we may just want to pass a google::cloud::Options opts = {} argument as the last argument to all client methods. This would help us be future-proof as it would let us add more options to a method call without breaking existing calls.
We could use something like this to add per-method timeouts.
We may want to call this Context rather than Options if there's a meaningful semantic difference between the two.
We'll need to do this in the generator too.

(mostly repeating what @devjgm, but maybe adding an original thought or two)
Overview
This would offer a general framework for implementing a solution to something like #4926. (In addition to timeouts, it could be used to add Metadata, serve some service specific function, etc.).
The Client calls would all gain an Options parameter:
// calls like:
Status Foo(FooRequest const& request);
// ...become:
Status Foo(FooRequest const& request, Options const& options = {});

The Connection calls would also gain an Options parameter.
Details / Open Questions
Jotting down some thoughts from a previous discussion with the team:

We probably don't want to default a parameter for a virtual member function in Connection.
We should consider making these non-pure virtual functions. This could prevent breaks of Connection mocks when a new RPC is added to a service for users that do NOT use our provided mocks + the Google Mock framework.
Implementing this for GA services constitutes a breaking change. (Maybe the code will compile, but the implementation details will change, making any current mocks useless).

We will need to add a configuration setting to the generator to enable/disable the generation of the Options parameter.
How and when to migrate currently GA libraries to using per-call options is an open question.

While we probably have enough direction to start implementing the API surface, I think we need a clearer picture of what a per-call option implementation looks like.

gRPC configuration

Could be applied to configure the context just before it is passed to the stub layer
Could be applied in our generic loop helpers (e.g. RetryLoop)
Could be applied as another stub decorator. We would need to think about whether this decorator takes effect before or after other decorators (e.g. auth).
Would these Options apply for poll and cancel operations?

REST configuration (currently just Storage)

Has storage::DownloadStallTimeoutOption and storage::TransferStallTimeoutOption
They are applied to the CurlClient. (So all requests with the same client have the same timeouts. Is this a problem? I don't know.)
They set CURLOPT_CONNECTTIMEOUT - (transfer) (download)

Service-specific configuration

Do they exist?
If so, I think they would be handwritten. The developer can decide how to implement them when the time comes.

Appendix
Just to give an idea of what I currently have in mind (setting deadlines) (for gRPC):
/// FILE: google/cloud/common_options.h
namespace google::cloud {
struct DeadlineOption {
  using Type = std::chrono::time_point<std::chrono::system_clock>;
};
}  // namespace

/// FILE: google/cloud/grpc_options.h
namespace google::cloud::internal {
struct GrpcSetupOption {
  using Type = std::function<void(grpc::ClientContext&)>;
};

// TODO : Whether this alters a ClientContext& or returns a new, configured
//              ClientContext can be figured out at a later date.
void ConfigureContext(grpc::ClientContext& context, Options const& opts) {
  // TODO : Which option takes precedence, and whether they are exclusive
  //        can be decided later.
  if (opts.has<GrpcSetupOption>()) {
    opts.get<GrpcSetupOption>()(context);
  } else if (opts.has<DeadlineOption>()) {
    context.set_deadline(opts.get<DeadlineOption>());
  }
}
}  // namespace

For the record, I currently have #7669 out for review, which adds the notion of "call-tree-specific options" (you can call it "context" if you like).  And then I have a PR queued up behind that which adds the Options options = {} arguments to the generated Client ctor and calls (and another in progress behind that to add them to the Spanner data client).

The Connection calls would also gain an Options parameter.

In that world this is no longer necessary, which removes many of the open questions above.

This is implemented for generated libraries, and we have separate bugs for each library.

See #8164


Compiler Error on Angular 5.1.3

I have include your module in my project like descripted.
When I try to run
run build --aot
I get the error

ERROR in @chevtek/angular-spinners/src/spinner.module.ts(6,2): Error during template compile of 'SpinnerModule'
Function calls are not supported in decorators in 'NgModule'
'NgModule' calls a function at @angular/core/core.ts(194,50).

My versions are
Angular: 5.1.3
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

@angular/cli: 1.6.3
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.3
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.5.3
webpack: 3.10.0

@tn0 hi! did you fix that?


enable unconvert and unparam linters

Also fixes an issue where bundle func no longer returns error.
Signed-off-by: Furkan Turkal<EMAIL_ADDRESS>

Welcome aboard!


Instagram Bridge fetching tons of old posts every day

For some strange reason which I could not decipher, for some time now I've been getting old posts mixed with the new ones. Moreover, every day I would get a consistent amount of posts every hour except for the hours of 10 and 11 in the morning, at which time my feed becomes flooded with ~200 posts, almost all of which are old posts from the last few days. Some of them are older than a week or so, and today I even encountered one from last New Year's, which was the last straw that finally made me decide to open this issue.
Would anybody happen to know what might be causing this and how could I go about solving it? I'd really appreciate the help.

Do you have the latest version installed? Can you try installing the latest master branch, there an Instagram fix: 7b63da522fa728811349081a0921f84bb1fa6f19
I have a bunch of feeds and that didn't happen.

@mrodriguezarias Is this still an issue?


Update install instructions for COPR

Disclaimer: I'm the author of this copr repo.
goncalossilva/cli has been up and running for much longer than the official recommendation, and over the years, it's been more reliable with its builds. See:

https://github.com/goncalossilva/rpm-act/actions
https://copr.fedorainfracloud.org/coprs/goncalossilva/act/monitor/

It's also fully automated. This means stable versions of Fedora get new builds quickly (even if builds on rawhide/preview versions tend to fail while the dust settles).
I think this is a better default choice for act users, but other than this PR, it's up to the reviewer. Regardless of it being merged or not, goncalossilva/act will continue to be built. :)

FWIW migrated from: https://github.com/nektos/act/pull/1969


Request add Image Resizing and Image Gaussian Blur

Hi,
I'm wondering if these 2 nodes can be added.

Or if alternatives can be suggested. I really like having the image to have a larger side of 896 so I can do an outpainting pad of 128 pixels to have a nice 1024px image for outpainting.
Thank you so much in advance.

Try ImageResize+ from https://github.com/cubiq/ComfyUI_essentials

ImageGuassianBlur comes from https://github.com/sipherxyz/comfyui-art-venture and is not supported.
Do these modules work?

Hi Fofr, thanks for the response. I'll try them out immediately and see if they work for me. Thanks!

Closing this for now, but feel free to reopen if you still have issues.


Go: Regenerate IAM Admin

This commit reflects the configuration change introduced in
https://github.com/googleapis/googleapis/pull/178 .

@jba I think this resolves most of the outstanding work items for the time being. Once this gets merged, I'll make a larger CL to push into Go Cloud.


Blog post announcing Star Track example app

Would love an eye or two over this as it's my first blog post on the PhoneGap Blog...
@hollyschinsky @mwbrooks etc
@GarthDB - if you have a second to have a look and make sure I did the technical side of this correctly that'd be awesome.

Awesome post Tommy!!! I like the tone, comes across very real. Minor comments left inline.

I'll figure out why the tests are failing. @hollyschinsky could you assign the pull request to me when you're done editing?

@GarthDB There are a lot of failing links in the tests due to my blog intermittently working and slow today which I'm trying to get fixed as well.

@hollyschinsky good to know - I'm getting a couple others locally. It really doesn't have a high tolerance to issues.

@GarthDB My blog issue was due to an xmlrpc.php hack script and is blocked now so those links should all resolve.

Sounds good


[Bug]: git obsidian error: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'args[6]' must be a string without null bytes

Describe the bug
I've updated to the newest version(2.24.1) and this happened!

Relevant errors (if available) from notifications or console (CTRL+SHIFT+I)
git obsidian error: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'args[6]' must be a string without null bytes. Received 'vault backup: 06-04 (11:44)\n' +
  '\n' +
  'Affected files:\n' +
  '.obsidian/plugins/obsidian-git/data.json\n' +
  '.obsidian...

Uncaught (in promise) Error: TypeError [ERR_INVALID_ARG_VALUE]: The argument 'args[6]' must be a string without null bytes. Received 'vault backup: 06-04 (11:44)\n' +
  '\n' +
  'Affected files:\n' +
  '.obsidian/plugins/obsidian-git/data.json\n' +
  '.obsidian...
    at GitExecutorChain.onFatalException (plugin:obsidian-git:26944:79)
    at GitExecutorChain.eval (plugin:obsidian-git:26936:24)
    at Generator.throw (<anonymous>)
    at rejected (plugin:obsidian-git:25805:29)

Steps to reproduce
I dont know how to reproduce it
Expected Behavior
No response
Addition context
No response
Operating system
macOS
Installation Method
None
Plugin version
2.24.1

Tried to reinstall and it's gone!