[v0.23.0] ConfigValidatorScanner '_Rendezvous' object has no attribute 'message'

Terraform module v5.0.0 + Forseti v0.23.0 on GCE.
Manual forseti client run command issue on forseti-vm-client finishes successfully but produces single error, \n replaced with line breaks (originally it's single-line), \" replaced with "  for readability:
  "serverMessage": "Error running scanner: ConfigValidatorScanner: 'Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.23.0-py3.6.egg/google/cloud/forseti/scanner/scanners/config_validator_util/validator_client.py", line 199, in reset
    self.stub.Reset(validator_pb2.ResetRequest())
  File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 565, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/usr/local/lib/python3.6/dist-packages/grpc/_channel.py", line 467, in _end_unary_response_blocking
    raise _Rendezvous(state, None, None, deadline)
grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with:
\tstatus = StatusCode.UNAVAILABLE
\tdetails = "failed to connect to all addresses"
\tdebug_error_string = "{"created":"@1572268821.347645953","description":"Failed to pick subchannel","file":"src/core/ext/filters/client_channel/client_channel.cc","file_line":3528,"referenced_errors":[{"created":"@1572268821.347630964","description":"failed to connect to all addresses","file":"src/core/ext/filters/client_channel/lb_policy/pick_first/pick_first.cc","file_line":399,"grpc_status":14}]}"
>

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.23.0-py3.6.egg/google/cloud/forseti/scanner/scanner.py", line 119, in run
    scanner.run()
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.23.0-py3.6.egg/google/cloud/forseti/scanner/scanners/config_validator_scanner.py", line 183, in run
    for flattened_violations in self._retrieve_flattened_violations():
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.23.0-py3.6.egg/google/cloud/forseti/scanner/scanners/config_validator_scanner.py", line 159, in _retrieve_flattened_violations
    self.validator_client.reset()
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/usr/local/lib/python3.6/dist-packages/six.py", line 693, in reraise
    raise value
  File "/home/ubuntu/forseti-security/.eggs/retrying-1.3.3-py3.6.egg/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/usr/local/lib/python3.6/dist-packages/forseti_security-2.23.0-py3.6.egg/google/cloud/forseti/scanner/scanners/config_validator_util/validator_client.py", line 204, in reset
    e.message)
AttributeError: '_Rendezvous' object has no attribute 'message'
'"

I'm having various problems with my installation and don't know which is contributing to the problems I have (SCC notifier doesn't work, inventory gathering takes very long time to finish) and want to report all anomalies I see in log at the moment.

Thanks for filing this issue, @paskal!
In the Forseti Server VM under /home/ubuntu/forseti-security, can you run: git branch -land let us know what version is outputted?
If it is not v2.23.0, we'd like to reinstall a fresh version of Forseti on the Server VM:

Delete your home/ubuntu/forseti-security directory: rm -rf forseti-security
Clone the forseti-security repo: git clone https://github.com/forseti-security/forseti-security.git
Check out tags/v2.23.0: git checkout tags/v2.23.0
Reinstall Forseti:
pip install -r requirements.txt
python3 setup.py install
Restart Forseti: systemctl restart forseti

And then rerun Forseti inventory, scanner, notifier, etc. to see if this error still persists.

I believe I already have 0.23.0 deployed, I haven't done anything at the machine manually and re-created it multiple times via Terraform already:
ubuntu@forseti-server-vm-xxxxxxx:~/forseti-security$ git branch -l
* (no branch)
ubuntu@forseti-server-vm-xxxxxxx:~/forseti-security$ git log
commit 97be856402a32030144091d49eabeb955ff0db5f (grafted, HEAD, tag: v2.23.0)
Author: Marquis<EMAIL_ADDRESS>Date:   Wed Oct 23 21:53:50 2019 +0200

    feat: send mailjet email with HTML content (#3326)
ubuntu@forseti-server-vm-xxxxxxx:~/forseti-security$ sudo git checkout tags/v2.23.0
HEAD is now at 97be856 feat: send mailjet email with HTML content (#3326)
ubuntu@forseti-server-vm-xxxxxxx:~/forseti-security$ git branch -l
* (no branch)
ubuntu@forseti-server-vm-xxxxxxx:~/forseti-security$ git log
commit 97be856402a32030144091d49eabeb955ff0db5f (grafted, HEAD, tag: v2.23.0)
Author: Marquis<EMAIL_ADDRESS>Date:   Wed Oct 23 21:53:50 2019 +0200

    feat: send mailjet email with HTML content (#3326)

@hshin-g and @paskal  I inadvertently recreated this issue with 2.22.  It looks like the config-validator service failed to start due to a missing path. Investigating.

For me, it was the fact that I had forgotten to add my public SSH key to my hosted Git repository.  @paskal Can you confirm that you've added your your public SSH key to your repository?

@paskal I understand you are syncing from GCS.  I ran into this error there as well.  Can you please confirm your policy library is stored in your server GCS bucket as follows?
gs://forseti-server-SUFFIX/policy-library

I have no policy-library folder in my Storage bucket and here is command output:
user@forseti-server-vm-xxxxxxx:~$ sudo systemctl status config-validator
● config-validator.service - Config Validator API Server
   Loaded: loaded (/lib/systemd/system/config-validator.service; disabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2019-10-29 18:59:06 UTC; 2h 7min ago
 Main PID: 20126 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

If absent policies are the reason of the failure, I would expect error message with this information instead of exception.

Hi @paskal .  The error messaging here can be improved.  Were you able to add your policy-library to your GCS bucket?

Forseti is unusable for me because of https://github.com/forseti-security/terraform-google-forseti/issues/360 (which could be moved to this project by the way), I've disabled this option to prevent errors from appearing in logs.

Hi @paskal, Please reply to @kevensen's comment when you get a chance so we can investigate further.

Sorry if I was not clear: I did not upload any policies but instead disabled config-validator altogether.

Hi @paskal, thanks for this issue. Agree that this error message is not helpful and there are a couple of ways we could let users know that there are no policies for Config Validator to use.

Removing the interrupts label. I have proposed a couple of solutions above in the original comment.


JobImprove Event Publishing with Timeout

Summary:
This PR refines the publishEvent method to improve event publishing reliability by introducing a timeout mechanism and enhanced logging. The changes allow for a more responsive system when attempting to publish events to the disruptor, especially in cases where the ring buffer may not have sufficient capacity at the time.
Timeout Implementation:
A 1-second timeout (in nanoseconds) is set, after which the event publishing attempt will stop if the required capacity is not available. The timeout is tracked using System.nanoTime() for precise elapsed time measurement.
Remaining Capacity Check:
The method checks if the remainingCapacity() of the ring buffer is greater than 1 (this can be adjusted based on your capacity requirements). If enough capacity is available, the event is published; otherwise, it waits and retries.
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Ensure mechanism

Ensure element is visible
Ensure element is on-screen

PR: https://github.com/zarashima/java-test-framework/pull/6


clipse crashes during history search

Thanks for making Clipse, I've been a happy user on Wayland for the last 6 months or so - it's the best :smiley:
Now, sadly it stopped working for me today and I can't figure out why and how to fix it.
Once I open clipse (usually in Kitty) and start a history-search, if I type certain characters (like 's') it crashes immediately:
❯ clipse keep
Caught panic:

runtime error: index out of range [1] with length 1

Restoring terminal...

goroutine 14 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:26 +0x5e
runtime/debug.PrintStack()
	runtime/debug/stack.go:18 +0x13
github.com/charmbracelet/bubbletea.(*Program).recoverFromPanic(0xc000254000)
	github.com/charmbracelet/bubbletea@v1.1.1/tea.go:705 +0x8b
panic({0x5ee72d4a2220?, 0xc00001e8b8?})
	runtime/panic.go:785 +0x132
github.com/sahilm/fuzzy.FindFromNoSort({0xc000015e84?, 0xc000012228?}, {0x5ee72d4bc8d0, 0xc000012228})
	github.com/sahilm/fuzzy@v0.1.1/fuzzy.go:136 +0x945
github.com/sahilm/fuzzy.FindFrom({0xc000015e84?, 0x3e8?}, {0x5ee72d4bc8d0?, 0xc000012228?})
	github.com/sahilm/fuzzy@v0.1.1/fuzzy.go:99 +0x25
github.com/sahilm/fuzzy.Find(...)
	github.com/sahilm/fuzzy@v0.1.1/fuzzy.go:83
github.com/charmbracelet/bubbles/list.DefaultFilter({0xc000015e84, 0x1}, {0xc000362008?, 0x8?, 0x0?})
	github.com/charmbracelet/bubbles@v0.20.0/list/list.go:89 +0x52
github.com/charmbracelet/bubbles/list.(*Model).handleFiltering.filterItems.func1()
	github.com/charmbracelet/bubbles@v0.20.0/list/list.go:1228 +0x1b5
github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1.1()
	github.com/charmbracelet/bubbletea@v1.1.1/tea.go:324 +0x7d
created by github.com/charmbracelet/bubbletea.(*Program).handleCommands.func1 in goroutine 39
	github.com/charmbracelet/bubbletea@v1.1.1/tea.go:318 +0x131
goroutine 1 [running]:
runtime/debug.Stack()
	runtime/debug/stack.go:26 +0x5e
runtime/debug.PrintStack()
	runtime/debug/stack.go:18 +0x13
github.com/savedra1/clipse/utils.HandleError({0x5ee72d4bbc20, 0xc000228980})
	github.com/savedra1/clipse/utils/err.go:11 +0x2c
main.launchTUI()
	github.com/savedra1/clipse/main.go:96 +0x77
main.main()
	github.com/savedra1/clipse/main.go:50 +0xc5

It's probably somehow related to my history-file, since if I delete it, the error goes away. But then my json-parser says the history-file is valid JSON and clipse starts-up just fine. Only after searching for a specific history-entry, it crashes.
I'll try to narrow it down further, but I thought perhaps this is a general issue that should be fixed.

Hi @cjk :wave:
Thanks for the kind words, I'm glad to hear you've been enjoying clipse. Unfortunately this is a known issue that's caused by the fuzzy find algo (within the BubbleTea TUI framework code) crashing when it encounters non-compatible characters in the history file, such as an irregular image binary pattern or a rare non-ascii text character. See issue #148.
As the part of the code that crashes is from the BubbleTea source it's difficult to implement fix but I will be looking into this as part of the next release. The fix in the meantime is to remove the non-compatible characters from the file. I'd recommend pinning anything you wouldn't want to lose and then running clipse -clear.
I'll keep this issue open and update the FAQs. If you do identify the specific characters causing problems, please let me know here as that will be a big help towards finding a fix.
Cheers

Ah, I see, yeah that makes sense.
I'll then take a closer look at my clipboard-history and prune whatever looks suspicious.
Thanks for the tip!
If later there's a meaningful fix then the better, to prevent this from happening again. But I also understand that fixing 3rd-party libs isn't always fun / possible.
I'll keep enjoying clipse anyways! :1st_place_medal:


How can i  do with Uint64 type?

use type adapter?

As you said you can generate custom type adapter then convert Uint64 to Uint8 byte array then write it.

@rizzi37 Uint64 cannot be represented by Dart. Please use a BigInteger instead.

thanks reply~
finally i used fixnum package with fit my protobuf int64 type.
class Int64Adapter extends TypeAdapter<Int64> {
  @override
  final typeId = 0;

  @override
  Int64 read(BinaryReader reader) {
    var len = ByteData.view(reader.readByteList(4).buffer).getUint8(0);
    return Int64.fromBytes(reader.readByteList(len));
  }

  @override
  void write(BinaryWriter writer, Int64 i ) {
    writer.writeByteList(i.toBytes());
  }
}


[third_party] switch OpenOCD to debian mirror

Sourceforge often has reliability issues which cause our CI to fail. Switch to debian source mirror as the primary URL to download it.
Debian only mirrors the bz2 compressed version, so the SHA is changed.

There was a small issue for the GitHub private CI which has been fixed now. Not sure why Azure pipelines don't run though.
Rebased and both seems to be running


bug: @core/llamaindex doesn't allow access to various schemas

Attempting to import the following from @core/llamaindex and getting Cannot find declarations
Document
Metadata
BaseNode
MetadataMode
NodeWithScore
// Doesn't work:
import { Document } from "@llamaindex/core";

// Doesn't work
import { Document } from "@llamaindex/core/schema";

// Works for import but gives `Error: Missing "./dist/schema" specifier in "@llamaindex/core" package`
import { Document } from "@llamaindex/core/dist/schema";

any tips @himself65 ?
P.S. I think this is a good direction, just need to figure out the above

change module resolution to node16 or bundler in your tsconfig

@himself65 thanks! switching to bundler has resolved it

nit: always use bundler if you are not running code like tsc && node ./dist/index.js

@himself65 I'm trying to find a work around right now but setting to bundler might not always be possible
more context: building or azure functions app

@himself65 I'm trying to find a work around right now but setting to bundler might not always be possible
more context: building or azure functions app

I don't have much further idea about this, but this is ts old behavior. But whether you update your tsconfig.json, do some patches to make type check happy, or use a bundler to a single js file before releasing to the Azure function app.
maybe related issue: https://github.com/microsoft/TypeScript/issues/46452#issue-1031817996

@himself65 apologies totally forgot to update you on this.
That's fair and very reasonable not want to support anything below node18.
In the end I managed to work around everything bit by bit to get the build working.
The one thing that was frustrating and I figured out in the end was, prettier had to be re-configured too, renaming it's config from .prettierrc.js to .prettierrc.json forced it to use modules in the end

do you mean cjs to esm?

Yep


Incorrect information regarding FreeBSD

FreeBSD is not a Linux distribution, rather a BSD distribution with its own linage, completly unrelated to Linux.
https://en.wikipedia.org/wiki/FreeBSD
A section regarding BSD custom images should exist as part of the TOC and "Applies to: ✔ Linux VMs" be updated to "Applies to: ✔ BSD VMs"

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

ID: e0cd7ebd-e262-7a75-5c90-abade813d597
Version Independent ID: a5f67d3b-53a7-4e1a-49b3-7674cda60c16
Content: Introduction to FreeBSD on Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/freebsd-intro-on-azure.md
Service: virtual-machines
GitHub Login: @thomas1206
Microsoft Alias: mimckitt

@pjmlp Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate. We will update you accordingly.

@mimckitt Can you please check and add your comments on this doc update request as applicable

The purpose of the applies to section is to show users that docs are applicable to Linux Distros, Windows Distros or scale sets uniform/ flexible. I see you're point but that's not exactly what we are using that section for. So at this point I am not going to add it into the applies to section. I appreciate the feedback and we are continuing to look at improving the applies to section so I will add this to future discussions and planning.
#please-close

Today I learned FreeBSD is a scale sets uniform/ flexible, oh well.


⚠ API - Lens has degraded performance

In cf53ade, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 658 ms

Resolved: API - Lens performance has improved in 41a12be after 6 minutes.


There should be instructions for installing on VS2019

The doc says it is installed by default with a supported workload, but on my install this wasn't true. After looking for the options a while, I realized it wasn't installed and had to manually install the component via the installer. The docs should have some instructions in case other folks are in this predicament.

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

ID: b8906861-1357-0292-ce64-9a8db681a98c
Version Independent ID: 096eea5a-63a3-f6bb-5c7b-5a0ecbf69d37
Content: Share quickstart - Visual Studio Live Share - Visual Studio Live Share
Content Source: docs/quickstart/share.md
Product: visual-studio-family
Technology: live-share
GitHub Login: @Chuxel
Microsoft Alias: clantz

cc @lostintangent

Apologies! Out of curiosity: could you share which workloads you have installed? We’ll update our docs, but we may need to include Live Share in additional VS workloads as well.

I definitely have .net core and asp.net installed, which was why I assumed I should already have it.


golang tools are not updated , getting error

I was trying to download the golang tools in command palette its show some error while i downloading ive been tried unintstall and reinstall but my problem was not solved so please gothrough the error

/extGo

It looks like this is caused by the Go extension. Please file the issue to the Go extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


added handler support

I added handler support in a way that works for me.
I'm not aggregating error messages, instead I provide handler to Validate method and let libxml to call it every time error occurs. I can do logging/aggregating all nasty stuff on application side as I wanted this to be as simple as possible.
every time I use validate I store handler in a map where context instance physical address is the key. when error occurs it will call back handler method which will find the application's handler based on context address and then it will invoke it.
Stupidly simple but it matched my needs

Thanks for your effort on this. Went in a slightly different direction that didn't change the api. Thanks again.


Docker run succeeds even if POSTGRES_PASSWORD is not set

From https://github.com/docker-library/docs/blob/master/postgres/README.md#environment-variables

The only variable required is POSTGRES_PASSWORD, the rest are optional.

one gets the impression that docker run will not succeed if POSTGRES_PASSWORD is not set.
However, I can successfully run:
$ docker run --name bugreport-postgres --publish 5432:5432 --detach postgres:13
8aafe409844a95a933080a70622aa7bfd265066e23113a9812ab95e78fcf1041

and there's nothing in the environment
$ env | grep POSTGRES | wc -l
0

Docker version:
$ docker --version
Docker version 19.03.13, build 4484c46d9d

I think if you check the logs, you'll see your container didn't actually start:
$ docker pull postgres:13
13: Pulling from library/postgres
Digest: sha256:8f7c3c9b61d82a4a021da5d9618faf056633e089302a726d619fa467c73609e4
Status: Image is up to date for postgres:13
docker.io/library/postgres:13

$ docker run --name bugreport-postgres --publish 5432:5432 --detach postgres:13
3f04be54c3b37c2d1a80bd43ae484834d3e7db947446075f1a8970c9b9a0da52

$ docker logs bugreport-postgres
Error: Database is uninitialized and superuser password is not specified.
       You must specify POSTGRES_PASSWORD to a non-empty value for the
       superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".

       You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
       connections without a password. This is *not* recommended.

       See PostgreSQL documentation about "trust":
       https://www.postgresql.org/docs/current/auth-trust.html

As Tianon said; the error is in the docker logs, and that the container exited (seen with docker ps -a). The host's env isn't relevant to the container's environment variables, you'd have to pass them to Docker as a -e option
$ docker run --name bugreport-postgres --publish 5432:5432 --detach postgres:13
0c7a2596e06a4221514833ee5f98be8ba032ae0bbe47e04c42fc1719521ff225

$ docker logs bugreport-postgres
Error: Database is uninitialized and superuser password is not specified.
       You must specify POSTGRES_PASSWORD to a non-empty value for the
       superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".

       You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
       connections without a password. This is *not* recommended.

       See PostgreSQL documentation about "trust":
       https://www.postgresql.org/docs/current/auth-trust.html

$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED              STATUS                          PORTS               NAMES
0c7a2596e06a        postgres:13         "docker-entrypoint.s…"   About a minute ago   Exited (1) About a minute ago                       bugreport-postgres

Thanks for clearing this. I was expecting the command to fail loudly or return an error code.
Looks like neither docker run
docker run --name bugreport-postgres-retval --publish 5432:5432 --detach postgres:13 ; echo $?
bcecfb2dce702947a6e202dd90af81b6f4604e8cbb9af71bf4a701fd7d775bc0
0

nor the combination of docker create and docker start return an error code.
$ docker create --name bugreport-postgres-create-n-start --publish 5432:5432 postgres:13 ; echo $?
95dd44fa2eb270932182a7cf83f5149799a4299b41488af9df292c7a64cc5c15
0
$ docker start bugreport-postgres-create-n-start ; echo $?
bugreport-postgres-create-n-start
0

This is probably expected behavior. It's just that the user may have different expectations. If I wanted to pass this improvement idea to the Docker team, where would you recommend opening an issue?

The host's env isn't relevant to the container's environment variables, you'd have to pass them to Docker as a -e option

Thanks, you're right. I just realized after posting that host environment variables are probably not exported.


Bulk tag multiple services

Bulk tag multiple services
Sample request:
POST /api/services
{
  "action" : "assign_tags",
  "resources" : [
    { "href" : "http://localhost:3000/services/11", "tags" : [ { "category" : "department", "name" : "finance" } ]}
    { "href" : "http://localhost:3000/services/12", "tags" : [ { "category" : "department", "name" : "finance" }]}
  ]
}

Links

Pivotal ticket

@miq-bot add_label enhancement, api
@miq-bot assign @abellotti

😍  this LGTM!!


‘async’ is a reserved word in Python >= 3.7

https://github.com/DragonComputer/Dragonfire/blob/master/dragonfire/__init__.py#L115 is a Syntax Error in Python >= 3.7.
This was fixed in upstream by moving from async to is_async.

Bump on this one...

@cclauss fixed with 49f5ca6eae2ec9be80d3e077182207298522ceb6


Remove arrow on first and last page of help menu

Might not be as good as we thought. Removing and adding reactions takes time and actually leaves the user to have to wait for the reaction.


[image_picker] Bunch of different errors

My app was working just fine on the simulator, until I tried to run it on my iPhone. Then it started giving these errors and now it does not run on the simulator either.
Steps to Reproduce

This is specific to my app. There seems to be something wrong with the image_picker. I'm unsure of how to give steps on how to reproduce the issue.
Expected results:  I except it to run my app (it used to before)
Actual results:
Running pod install...                                              3.1s
Running Xcode build...
Xcode build done.                                            9.2s
Failed to build iOS app
Error output from Xcode build:
↳
    ** BUILD FAILED **

Xcode's output:
↳
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.7+21/ios/Classes/FLTImagePickerPlugin.m:149:20: warning: 'UIAlertView' is deprecated:
    first deprecated in iOS 9.0 - UIAlertView is deprecated. Use UIAlertController with a preferredStyle of UIAlertControllerStyleAlert instead [-Wdeprecated-declarations]
        [[[UIAlertView alloc] initWithTitle:NSLocalizedString(@"Error", nil)
                       ^
    In module 'UIKit' imported from /Users/mrigankdoshy/Documents/Work/Business/Whispering Mule/App/mule-app/ios/Pods/Target Support
    Files/image_picker/image_picker-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIA
    lertView.h:27:12: note: 'UIAlertView' has been explicitly marked deprecated here
    @interface UIAlertView : UIView
               ^
    1 warning generated.
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.7+21/ios/Classes/FLTImagePickerPhotoAssetUtil.m:17:44: warning:
    'UIImagePickerControllerReferenceURL' is deprecated: first deprecated in iOS 11.0 - Will be removed in a future release, use PHPicker. [-Wdeprecated-declarations]
      NSURL *referenceURL = [info objectForKey:UIImagePickerControllerReferenceURL];
                                               ^
    In module 'UIKit' imported from /Users/mrigankdoshy/Documents/Work/Business/Whispering Mule/App/mule-app/ios/Pods/Target Support
    Files/image_picker/image_picker-prefix.pch:2:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.2.sdk/System/Library/Frameworks/UIKit.framework/Headers/UII
    magePickerController.h:62:51: note: 'UIImagePickerControllerReferenceURL' has been explicitly marked deprecated here
    UIKIT_EXTERN UIImagePickerControllerInfoKey const UIImagePickerControllerReferenceURL API_DEPRECATED("Will be removed in a future release, use PHPicker.", ios(4.1, 11.0))
    API_UNAVAILABLE(tvos); // an NSURL that references an asset in the AssetsLibrary framework
                                                      ^
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.7+21/ios/Classes/FLTImagePickerPhotoAssetUtil.m:21:47: warning:
    'fetchAssetsWithALAssetURLs:options:' is deprecated: first deprecated in iOS 11 - Will be removed in a future release [-Wdeprecated-declarations]
      PHFetchResult<PHAsset *> *result = [PHAsset fetchAssetsWithALAssetURLs:@[ referenceURL ]
                                                  ^
    In module 'Photos' imported from /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/image_picker-0.6.7+21/ios/Classes/FLTImagePickerPhotoAssetUtil.h:6:
    /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.2.sdk/System/Library/Frameworks/Photos.framework/Headers/PH
    Asset.h:74:1: note: 'fetchAssetsWithALAssetURLs:options:' has been explicitly marked deprecated here
    + (PHFetchResult<PHAsset *> *)fetchAssetsWithALAssetURLs:(NSArray<NSURL *> *)assetURLs options:(nullable PHFetchOptions *)options API_DEPRECATED("Will be removed in a
    future release", ios(8, 11), tvos(8, 11)) API_UNAVAILABLE(macos);
    ^
    2 warnings generated.
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/PermissionManager.m:69:93: error: expected expression
            BOOL success = [[UIApplication sharedApplication] openURL:options:completionHandler::[NSURL URLWithString:UIApplicationOpenSettingsURLString]];
                                                                                ^
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/PermissionManager.m:69:67: error: use of undeclared identifier
    'options'
            BOOL success = [[UIApplication sharedApplication] openURL:options:completionHandler::[NSURL URLWithString:UIApplicationOpenSettingsURLString]];
                                                                      ^
    /Users/mrigankdoshy/flutter/.pub-cache/hosted/pub.dartlang.org/permission_handler-5.0.1+1/ios/Classes/PermissionManager.m:69:75: error: use of undeclared identifier
    'completionHandler'
            BOOL success = [[UIApplication sharedApplication] openURL:options:completionHandler::[NSURL URLWithString:UIApplicationOpenSettingsURLString]];
                                                                              ^
    3 errors generated.
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Constructing build description

Logs
 Output to large for terminal to show everything

warning • Invalid option specified for 'enable-experiment': Flag "spread-collections" is no longer required • analysis_options.yaml:3:5 • invalid_option
warning • Invalid option specified for 'enable-experiment': Flag "spread-collections" is no longer required • analysis_options.yaml:3:5 • invalid_option
   info • Unused import: 'dart:convert' • lib/config/http_client.dart:1:8 • unused_import
   info • Unused import: 'dart:typed_data' • lib/config/http_client.dart:3:8 • unused_import
   info • Unused import: 'package:mule/models/res/requestedFromMeRes/requested_from_me_res.dart' • lib/config/http_client.dart:19:8 • unused_import
   info • The declaration '_makeGetRequest' isn't referenced • lib/config/http_client.dart:36:20 • unused_element
   info • This function has a return type of 'FutureOr<ImageProvider<Object>>', but doesn't end with a return statement • lib/config/http_client.dart:218:25 • missing_return
   info • The value of the local variable 'number' isn't used • lib/config/http_client.dart:220:9 • unused_local_variable
   info • Duplicate import • lib/models/data/order_data.dart:3:8 • duplicate_import
   info • 'List' is deprecated and shouldn't be used. Use a list literal, [], or the List.filled constructor instead • lib/models/res/errorRes/error_res.dart:14:18 •
          deprecated_member_use
   info • Unused import: 'dart:io' • lib/screens/home/map/map_helper.dart:2:8 • unused_import
   info • The value of the field '_areMarkersLoading' isn't used • lib/screens/home/map/map_widget.dart:43:8 • unused_field
   info • The value of the local variable 'positionStream' isn't used • lib/screens/home/map/map_widget.dart:79:36 • unused_local_variable
   info • Unused import: 'package:flutter_progress_button/flutter_progress_button.dart' • lib/screens/home/slider/match/waiting_to_match_panel.dart:3:8 • unused_import
   info • The value of the local variable 'score' isn't used • lib/screens/home/slider/request/make_request_panel.dart:157:21 • unused_local_variable
   info • The value of the local variable 'currentLocation' isn't used • lib/screens/home/slider/request/make_request_panel.dart:160:30 • unused_local_variable
   info • Unused import: 'package:sliding_up_panel/sliding_up_panel.dart' • lib/screens/home/slider/search/search_panel.dart:12:8 • unused_import
   info • Unused import: 'dart:math' • lib/screens/home/slider/sliding_up_widget.dart:1:8 • unused_import
   info • Unused import: 'package:mule/config/app_theme.dart' • lib/screens/home/slider/sliding_up_widget.dart:4:8 • unused_import
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/ForgotPassword/email_otp.dart:162:30 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/ForgotPassword/forgot_password_email.dart:150:20 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/ForgotPassword/reset_password.dart:154:34 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/login_screen.dart:148:30 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/login_screen.dart:191:30 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/login/login_screen.dart:281:20 • deprecated_member_use
   info • Unused import: 'package:google_maps_flutter/google_maps_flutter.dart' • lib/screens/menu/home_drawer.dart:4:8 • unused_import
   info • This function has a return type of 'ImageProvider<Object>', but doesn't end with a return statement • lib/screens/menu/home_drawer.dart:459:17 • missing_return
   info • Unused import: 'package:get_it/get_it.dart' • lib/screens/orders/orders_screen.dart:2:8 • unused_import
   info • Unused import: 'package:mule/stores/global/user_info_store.dart' • lib/screens/orders/orders_screen.dart:7:8 • unused_import
   info • The declaration '_updateOrders' isn't referenced • lib/screens/orders/orders_screen.dart:28:3 • unused_element
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/profile/Account/change_email.dart:92:20 • deprecated_member_use
   info • Unused import: 'package:get_it/get_it.dart' • lib/screens/profile/Account/change_password.dart:3:8 • unused_import
   info • Unused import: 'package:mule/screens/profile/profile.dart' • lib/screens/profile/Account/change_password.dart:9:8 • unused_import
   info • Unused import: 'package:mule/stores/global/user_info_store.dart' • lib/screens/profile/Account/change_password.dart:10:8 • unused_import
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/profile/Account/change_password.dart:151:34 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/profile/Account/change_phone.dart:105:18 • deprecated_member_use
   info • The value of the local variable 'errRes' isn't used • lib/screens/profile/Account/delete_account.dart:38:16 • unused_local_variable
   info • Unused import: 'package:mule/screens/profile/Account/change_email.dart' • lib/screens/profile/profile.dart:5:8 • unused_import
   info • Unused import: 'package:mule/screens/profile/Account/change_phone.dart' • lib/screens/profile/profile.dart:7:8 • unused_import
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/signup/phone_otp.dart:123:28 • deprecated_member_use
   info • Unused import: 'package:mule/screens/signup/phone_otp.dart' • lib/screens/signup/signup_screen.dart:11:8 • unused_import
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/screens/signup/signup_screen.dart:169:24 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/widgets/alert_widget.dart:15:15 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/widgets/confirm_dialogue.dart:13:11 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/widgets/confirm_dialogue.dart:29:11 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/widgets/order_completion_dialogue.dart:13:11 • deprecated_member_use
   info • 'FlatButton' is deprecated and shouldn't be used. Use TextButton instead. See the migration guide in flutter.dev/go/material-button-migration-guide). This feature
          was deprecated after v1.25.0-8.1.pre. • lib/widgets/order_completion_dialogue.dart:27:11 • deprecated_member_use
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: StylizedButton.callback •
          lib/widgets/stylized_button.dart:4:7 • must_be_immutable
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: StylizedButton.callback •
          lib/widgets/stylized_button.dart:43:7 • must_be_immutable
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: StylizedButton.callback •
          lib/widgets/stylized_button.dart:55:7 • must_be_immutable
   info • This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: StylizedButton.callback •
          lib/widgets/stylized_button.dart:67:7 • must_be_immutable

[✓] Flutter (Channel master, 1.26.0-2.0.pre.401, on macOS 11.1 20C69 darwin-x64, locale en-US)
    • Flutter version 1.26.0-2.0.pre.401 at /Users/mrigankdoshy/flutter
    • Framework revision da5a454d5c (34 hours ago), 2021-01-17 01:24:03 -0500
    • Engine revision 609036f2bf
    • Dart version 2.12.0 (build 2.12.0-236.0.dev)

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.2, Build version 12B45b
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2020.1.3)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 47.1.3
    • Dart plugin version 201.8538.45

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • iPhone 11 Pro Max (mobile) • 173C06F5-D4CA-4450-AEAD-FCA64BB010CD • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-2 (simulator)
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 87.0.4280.88

I got the same issue too. Have wasted 2 days on this. Can you tell me how did you fix it?
What I have done:

Upgrade all dependencies
Make sure all versions are latest one: Flutter (Stable channel), Android studio, SDKs, Xcode
in the Podfile I also have ensured the target version to be 10.12
Flutter clean
delete Pods and Podfile and Podfile lock and reinstall pods
Pod repo update

None of these worked.

I got the same issue too. Have wasted 2 days on this. Can you tell me how did you fix it?
What I have done:

Upgrade all dependencies
Make sure all versions are latest one: Flutter (Stable channel), Android studio, SDKs, Xcode
in the Podfile I also have ensured the target version to be 10.12
Flutter clean
delete Pods and Podfile and Podfile lock and reinstall pods
Pod repo update

None of these worked.

@zenkog I ultimately factory reseted my laptop (to reset my XCode settings) and then reinstalled flutter and everything worked smoothly. So I believe this has something to do with XCode settings. If your codebase is small, I would recommend that you create a project and copy over your code.

@zenkog I ultimately factory reseted my laptop (to reset my XCode settings) and then reinstalled flutter and everything worked smoothly. So I believe this has something to do with XCode settings. If your codebase is small, I would recommend that you create a project and copy over your code.

@mrigankdoshy Thanks for the pointer.
I have done what you said to Factory reset XCode:

Enter in terminal defaults delete com.apple.Xcode
Then delete the settings: rm -rf ~/Library/Application\ Support/Xcode

But it still doesn't work.
Unless there is really no other choice, I want to refrain from factory reset my Mac (which will erase all the hard drive contents). The code base is medium size (about 346 items inside lib folder), but it's almost a year of work.
Hope someone could help me out here.
I'm not sure, but is this related to the MacOS update to Big Sur? Because all these just happened after that update.

@mrigankdoshy Thanks for the pointer.
I have done what you said to Factory reset XCode:

Enter in terminal defaults delete com.apple.Xcode
Then delete the settings: rm -rf ~/Library/Application\ Support/Xcode

But it still doesn't work.
Unless there is really no other choice, I want to refrain from factory reset my Mac (which will erase all the hard drive contents). The code base is medium size (about 346 items inside lib folder), but it's almost a year of work.
Hope someone could help me out here.
I'm not sure, but is this related to the MacOS update to Big Sur? Because all these just happened after that update.

@mrigankdoshy
Are you still facing the issue ? Does it occur in debug or release mode ?
If so, can you provide full logs by running flutter run --verbose or flutter run --release --verbose ?

@mrigankdoshy
Are you still facing the issue ? Does it occur in debug or release mode ?
If so, can you provide full logs by running flutter run --verbose or flutter run --release --verbose ?

@darshankawar I know you didn't ask me, but let me provide my flutter run --verbose in the file attached (too long and it prevent me to post it). Click the file below:
flutter-error.pdf
Thanks for looking into the problem

@darshankawar I know you didn't ask me, but let me provide my flutter run --verbose in the file attached (too long and it prevent me to post it). Click the file below:
flutter-error.pdf
Thanks for looking into the problem

@darshankawar Nope, I got rid of it. I think it occurred when Xcode settings were release mode (I'm not sure tho). My flutter run --verbose output is in the issue description

@darshankawar Nope, I got rid of it. I think it occurred when Xcode settings were release mode (I'm not sure tho). My flutter run --verbose output is in the issue description

@zenkog
Can you provide your flutter doctor -v ? the log you provided is indeed too long (817 pages) and practically impossible to go through each page to look at the error.  I see below which potentially is part of the error:
Command PhaseScriptExecution failed with a nonzero exit but this is very vague and doesn't reveal much.
Also, are you on Big Sur on which you are seeing this ? Is this only happening using image_picker ? If you remove it, does the issue occur ?

@darshankawar Here is my flutter doctor -v:
[✓] Flutter (Channel stable, 1.22.6, on macOS 11.1 20C69 darwin-x64, locale en-US)
    • Flutter version 1.22.6 at /Users/ZK/development/flutter
    • Framework revision 9b2d32b605 (7 days ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Volumes/ZK-R/Applications/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Volumes/ZK-R/Applications/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin installed
    • Dart plugin version 201.9317
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (1 available)
    • ZK iPho (mobile) • b3ebbe93864b12b2d78acd5efecf25 • ios • iOS 14.3

• No issues found!

It is practically impossible for me to remove image_picker from my code. Because it is integrated in many parts of my code (it is a year worth of work).
Yes I'm running on Big Sur. And it all went well exactly before I updated my Mac.
I do not even recognize this Command PhaseScriptExecution I don't think I ever used it.

I just tried to create a fresh new flutter app and run it, it runs well.
But when I added these in pubspec.yaml:
  flutter_form_builder: ^4.2.0
  image_picker: ^0.6.7+21

  # Firebase packages
  firebase_core: ^0.7.0
  firebase_auth: ^0.20.0+1
  cloud_firestore: ^0.16.0
  firebase_storage: ^7.0.0
  firebase_database: ^6.0.0
  cloud_functions: ^0.9.0
  firebase_admob: ^0.11.0+1
  firebase_analytics: ^7.0.1

And of course set the deployment target to 10.12 in the Podfile
There is no modification whatsoever in the main.dart
The app immediately closes. (blink white screen then close).
I'm doing more testing now.

When I'm using only image_picker as dependency then it worked. So it is not from the image_picker itself.
I created another issue here to follow up this problem

@zenkog
Thanks for filing new issue. I am closing this one because the OP is not seeing the issue as their comment above, https://github.com/flutter/flutter/issues/74196#issuecomment-769957925.


Maintain image aspect ratio

tldr;
This PR updates the image logic when only a new width or new height is provided to maintain the original image aspect ratio.
Details
Previously, if only one dimension was provided, the non-specified dimension would fall back to the original image size. For example a 640x320 image that was rendered with only a height of 32 specified would end up with a width of 640 and a height of 32:
render.Image(
    src = SOME_IMAGE,
    height = 32,
)

With this change the new image width would be scaled to match the new height while maintaining the original image aspect ratio. So in this example the image would be rendered with a width of 64 and a height of 32.
Why do this?
The image size is not always known ahead of time so this makes it simpler to resize an image on the fly to properly fit in the 64x32 pixlet/tidbyt screen.
Example
Original Image (323 × 200):

Previous functionality when defining only a height of 32 would output a stretched image:

With this change the image maintains the original aspect ratio:

Hey @rohansingh / @betterengineering apologies for the ping but since this is my first PR to this repo, I'm not sure of the process. Looks like I need someone to approve the workflows.

Hey @btjones, and thanks for the contribution!
Very reasonable change, and we'd be happy to merge it. Just that one question mark around division by zero.

Changed my mind and merged. =)
Thank you @btjones!


Bug: Deploy-stack doesnt wait for a successfull deployment before exiting with a 0 system code

I am currently using the Deploy stack actions to deploy my application stack to an Okteto namespace within a GitHub Action workflow.
After the stack is deployed, I have unit tests that make live HTTP tests against the deployed stack using the namespace URL.
After several runs, I have discovered that the deploy-stack action does not fully wait for the deployment to be successful before exiting. This causes the action workflow to proceed to the next job which runs the API tests against an unready deployment.
To augment, I have employed the use of the nev7n/wait_for_response@v1 which waits for an extra 5s while pinging the deployment URL for a 200 status code to indicate a successful deployment.

Steps to reproduce:
Clone this repository
Enable Github Actions and create a pull request to trigger the actions workflow.

Example failing GitHub Action run without nev7n/wait_for_response@v1
Example passing GitHub Action run withnev7n/wait_for_response@v1

@vickywane have you try with the pipeline action?
https://github.com/marketplace/actions/okteto-pipeline

No.
Would that be a better replacement for the deploy-stack action?

@vickywane https://github.com/marketplace/actions/okteto-pipeline
The automatic pipeline will deploy your compose file:
https://okteto.com/docs/cloud/okteto-pipeline/#automatic-deployment

closing since action is now deprecated


Story: users can checkout -- adds order to their order history:

impl: route to put order and order history react component

Mike and I are working on getting the store to bring in product info from the /api routes based on the products in the cart on the redux store


[Docs] Fix dead links when subsection title have underscore

a minor change on build toc script: add underscore to link instead of replacing with "-". then I re-run the script
also I tested on local server

Need to resolve conflicts before merging.

Need to rerun build_toc.ps1 to update toc.


Port for Firefox?

Are there any current plans to port to Firefox?

None, I suppose it could just work as-is, but I don't have the time to do such a port.
Anyone could contribute one tho, since all the code is here 🙂


ros_gz_bridge support for gz.msgs.EntityWrench

Hello,
I would like to apply external forces to robot links in Gazebo using the apply_link_wrench plugin and exposing its corresponding Gazebo topics to ROS topics.
However, apply_link_wrench uses the gz.msgs.EntityWrench message, which is not included in the correspondence table of ros_gz_bridge.
Desired behavior

Implement a corresponding ROS message type (something like ros_gz_interfaces/msg/EntityWrench) and a bridge mapping between it and gz.msgs.EntityWrench.
Alternatives considered

Considered using the apply_joint_force plugin instead, as it uses the gz.msgs.Double type, which is included in ros_gz_bridge. Specifically for my use case it would be enough, however loading this plugin stops the controller (ros2_control) from working. In contrast, the apply_link_wrench plugin can be loaded (attached to the world) without interfering with the controller.
Implementation suggestion

The new message type can be similar to the already implemented ros_gz_interfaces/msg/JointWrench as follows:
std_msgs/Header header
std_msgs/String entity
geometry_msgs/Wrench wrench

Suggested fields correspond to the gz.msgs.EntityWrench message, enabling ros_gz_bridge to convert between them.
Additional context

As the apply_body_wrench service that was available in Gazebo Classic seems to have no direct replacement in modern Gazebo, I believe the suggested interface together with the already available apply_link_wrench public is a welcome feature.
If all this makes sense, I would be pleased to help with the implementation. Thanks in advance!

#572 adds EntityWrench to the iron branch; upon merging, I can also implement the feature on humbleand ros2 branches.


Snap package install for.cli in Linux.

Describe the proposal
Provide snap package for install on Linux.
snapcraft.io

This issue is essential for Ubuntu Core.

/assign


Really slow

Whenever I select the preview tab, it takes up to 10 seconds to load the thing. What gives?

I've seen this too. I think it's something with versions 5 and 6. Will review.

I saw this in the first version of 6, but since then (I'm using 6.0.4) it's been pretty snappy. I do think there can be a delay at startup, but that's somewhat intentional.


Integrating Changes from Original gh-pages

And added test cases too.

This is great ! Thanks for integrating these ! I see the tests all pass too !


Suggestion to rename the spatial_ directories in content/tutorials

I suggest to prefix the spatial_ directories in content/tutorials with r_, resulting in r_spatial_xxxx. They all relate to R, and we expect non-R spatial tutorials to come which could then use e.g. qgis_xxxx. (An alternative would be spatial_r_ and spatial_qgis_, but the suggested r_spatial_ is more in line with the existing r_ directories)
It's not that important, but it seems more streamlined that way. Feel free to comment.

I'll drop my idea, since it would turn existing links (in other places) non-functional, i.e. links to the affected tutorials. We'll better use spatial_qgis_ or something like that for non-R spatial tutorials.


feat: add summit 2022 banner

This PR brings a banner for the eBPF 2022 summit

@xmulligan I've updated the button text
@qmonnet thanks for the review!
The formatting changes are my bad, I've failed to notice these linter-introduces changes before commiting, won't do so next time (or will add them in a separate PR).
Please note that we have also updated the banner mobile layout, so that the date would still be visible on small screens.


Made tsx/ts files testable with jest by adding config to webpack.

Seems like configuration in webpack.config was missing and "ts-jest" was not installed to while it was been used in package.json.
I have completed both and opened an issue  #116  to add a CONTRIBUTE.md to help future contributors make contribution with ease.

Looks great @thisis-Shitanshu ! Thanks for the PR!


typedef struct in C

I was wondering what is the difference and implications between the following two cases?
typedef struct foo{
int x;
} foo;
and
typedef struct {
int x;
} foo;
Is the first one just needed for linked lists?

I think both the first and second refer (mostly) to the same thing.
struct foo{
    int x;
};
typedef struct foo foo;

This lets you say
foo newvar;

instead of
struct foo newvar;

I think in the second case there is no declaring struct foo something because the struct itself was anonymous. But not totally sure; feel free to play around in godbolt

Just to clarify both methods allow this declaration
foo newvar;
However, if working with linked lists, only the first option works:
typedef struct foo{ int x; foo *next: } foo;
I think I don't really understand the concept of namespace (as I understand 'foo' before the brackets) when there is a typespace ('foo' after brackets) defined?

Ahh I see what you mean. Yes you do need a forward declaration
typedef struct foo foo;
struct foo{
    int x;
    foo *foo;
};

Here's the relevant StackOverflow page
Is this okay to close?

@annehutter I think this issue is resolved; I am closing for now -- please feel free to re-open.


Async Main

Hi! Please let me know if this isn't the right place to ask about this or if it has already been discussed. :)
I wrote a library to create animated drawings in Rust. It's specifically designed to be a great tool for teaching Rust. One of the things I'd like to add a few months from now is a whole set of lessons about Rust and async IO. I plan to refactor the library to return futures and then teach the different future combinators using the drawing methods in the library. It should be really cool!
One of the things users of my library will do a lot is write code directly in the main function. For example, to draw a heart, their code might look something like this:
extern crate turtle;

use turtle::Turtle;

fn main() {
    let mut turtle = Turtle::new();

    turtle.set_speed(5);
    turtle.set_pen_size(3.0);
    turtle.set_pen_color("red");

    turtle.pen_up();
    turtle.forward(-50.0);
    turtle.pen_down();

    turtle.set_fill_color("red");
    turtle.begin_fill();
    turtle.left(50.0);
    turtle.forward(111.65);
    turtle.set_speed(7);
    curve(&mut turtle);
    turtle.left(120.0);
    curve(&mut turtle);
    turtle.set_speed(5);
    turtle.forward(111.65);
    turtle.end_fill();

    turtle.forward(20.0);
    for _ in 0..10 {
        turtle.right(2.0);
        turtle.forward(2.0);
    }

    turtle.set_background_color("pink");
}

fn curve(turtle: &mut Turtle) {
    for _ in 0..100 {
        turtle.right(2.0);
        turtle.forward(2.0);
    }
}

Each of these method calls directs a "turtle" (the pen used for drawing) to perform a certain action.
If I were to start to port this to use futures, I would need to move the entire contents of main into a new function, and replace main with a call to wait(). That's a lot of code to suddenly have to move. I personally understand why I need to do that because I know the mechanics behind it, but for a newer Rust user, I think it's important to remove that friction entirely. If they're able to use async/await syntax everywhere else, I think they would naturally try to use it in main too.
This is a very similar issue to the accepted RFC for allowing ? in main. For the same reason that having ? in main is convenient and important, I think having async and await in main from the beginning is really critical too.  It would be great if we could have that functionality from the beginning when async/await is added to the language.
// Combines async/await syntax with the `?` in `main` RFC
// Example from: https://github.com/rust-lang/rfcs/blob/master/text/1937-ques-in-main.md#changes-to-doctests
#[async]
fn main() -> Result<(), ErrorT> {
    //...Lots of fancy async code here...
    Ok(())
}

Also relevant is that C# 7 has a similar async Main feature.
This could be useful to other Rust tools which also need to use await in their main routine.

You do not need to move your code from main. You can put your async code inside an async_block macro.

@rushmorem My question is actually specifically about being able to use #[async] with main. (See the example at the end of the issue description.) I understand that I could wrap main's body in an async_block! macro, but I'd prefer if main supported the syntax that's already usable for all other functions that return something.
My suggestion/proposal goes hand in hand with the already being implemented RFC that allows returning a result from main. :)

We could perhaps try to allow this! I fear though that we don't have enough of a "default" runtime to know how to run the future returned by main, so we may not have as "easy" of an implementation as other languages perhaps.

The way I was imagining it was that code like this:
#[async]
fn foo() -> Result<(), i32> {
    println!("{}", 1 + await!(bar())?);
    Ok(())
}

#[async]
fn bar() -> Result<i32, i32> {
    Ok(2)
}

fn main() -> Result<(), i32> {
    foo().wait()
}

Would become like this:
#[async]
fn main() -> Result<(), i32> {
    println!("{}", 1 + await!(bar())?);
    Ok(())
}

#[async]
fn bar() -> Result<i32, i32> {
    Ok(2)
}

I think that this fits really well with the RFC that allows returning Result from main.
Is there more to that than just calling wait() on the future? I didn't see much else in the examples I looked at in the README. This feature to me was more about adding a convenient syntactic sugar which would make learning easier. It makes sense to just get it to the point where you can return a future that contains a result, then let the implemention of that other RFC handle the result. What do you think?

@sunjay ah yeah unfortunately wait probably isn't what you want because most applications will want to configure and set up an event loop, which is all sort of "life before main" in this sense unfortunately

@alexcrichton Ah yes you're right. Is there any default behaviour we could support at all? I imagine that there must be simpler cases which don't need the entire main loop in order to function. Are there any?

Well yes my point is we could support something like wait, but it just wouldn't be too useful. I don't think we're at a point yet where there's a "clear and obvious" one-liner to run 90% of async programs.


Open the new Worktree in new Visual Studio Code instance

First, thank you for this wonderful extension!
I tried to add a new Worktree, but after I added it, the existing VSCode restarted with the new folder. I think it is better to open a new instance of VSCode instead.
I use Worktrees for working on several branches to prevent switching. But the extension enforces me to switch between worktrees.
Can it open a new instance instead?

Hi @rhalaly,
Great idea!
I implemented a solution for your needs.
You can add this property "vsCodeGitWorktrees.move.openNewVscodeWindow": true to your vscode settings and will be able to open new vscode instances when you switch or create a worktree.
I hope the implementation suits you!
If you have a better idea, please suggest it.

@alexiszamanidis Thanks for the ultra fast response! This is an amazing solution!
Can't wait to get that release!

It has already been published.
Please let me know if everything goes well!

Works awesome! Thank you for the rapid response!
I'm glad you liked it.
Thank you for your contribution!


Bash Completion script gives error

[X] are reporting a bug others will be able to reproduce and not asking a question. If you're not sure or want to ask a question do so on our Discourse: https://discourse.brew.sh
[N/A] ran a brew command and reproduced the problem with multiple formulae? If it's a problem with a single, official formula (not cask) please file this issue at Homebrew/homebrew-core: https://github.com/Homebrew/homebrew-core/issues/new/choose. If it's a brew cask problem please file this issue at https://github.com/Homebrew/homebrew-cask/issues/new/choose. If it's a tap (e.g. Homebrew/homebrew-php) problem please file this issue at the tap.
[X] ran brew update and can still reproduce the problem?
[X] ran brew doctor, fixed all issues and can still reproduce the problem?
[X] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Adding Bash completion support following the instructions here :
https://docs.brew.sh/Shell-Completion
if type brew &>/dev/null; then
  for COMPLETION in $(brew --prefix)/etc/bash_completion.d/*
  do
    [[ -f $COMPLETION ]] && source "$COMPLETION"
  done
  if [[ -f $(brew --prefix)/etc/profile.d/bash_completion.sh ]];
  then
    source "$(brew --prefix)/etc/profile.d/bash_completion.sh"
  fi
fi

What happened (include command output)
I'm adding the code to my .bash_profile and open a new term.
And then a lot of command not found error is displayed and some syntax error.
Note: the instruction says to add it to .bashrc, but on my freshly reinstalled macbook with Mojave, .bashrc is not read.
See attached file for the output (long output)
Here are some env info :
[21:30] tom@toms-typewriter:~$ brew config
HOMEBREW_VERSION: 2.0.6
ORIGIN: https://github.com/Homebrew/brew
HEAD: 649d1427f5fe41323c436608f5c21513f8f34f71
Last commit: 5 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: b196924abf02be1b43bcfbe5d023a72882648943
Core tap last commit: 31 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_LOGS: /Users/tom/Library/Logs/Homebrew
CPU: octa-core 64-bit ivybridge
Homebrew Ruby: 2.3.7 => /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/bin/ruby
Clang: 10.0 build 1001
Git: 2.20.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.54.0 => /usr/bin/curl
macOS: 10.14.4-x86_64
CLT: <IP_ADDRESS>.1.1552586384
Xcode: 10.2
CLT headers: <IP_ADDRESS>.1.1552586384
[21:30] tom@toms-typewriter:~$

===============================================
===============================================

[21:30] tom@toms-typewriter:~$ bash --version
GNU bash, version 5.0.3(1)-release (x86_64-apple-darwin18.2.0)
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[21:31] tom@toms-typewriter:~$

===============================================
===============================================

[21:31] tom@toms-typewriter:~$ brew info bash
bash: stable 5.0.3 (bottled), HEAD
Bourne-Again SHell, a UNIX command interpreter
https://www.gnu.org/software/bash/
/usr/local/Cellar/bash/5.0.3 (150 files, 9.4MB) *
  Poured from bottle on 2019-03-26 at 16:09:45
From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/bash.rb
==> Options
--HEAD
	Install HEAD version
==> Caveats
In order to use this build of bash as your login shell,
it must be added to /etc/shells.
==> Analytics
install: 30,271 (30 days), 96,825 (90 days), 228,122 (365 days)
install_on_request: 24,250 (30 days), 76,571 (90 days), 180,997 (365 days)
build_error: 0 (30 days)
[21:31] tom@toms-typewriter:~$
[bash_completion.log](https://github.com/Homebrew/brew/files/3024436/bash_completion.log)

===============================================
===============================================

[21:31] tom@toms-typewriter:~$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: The filesystem on / appears to be case-sensitive.
The default macOS filesystem is case-insensitive. Please report any apparent problems.

Warning: Putting non-prefixed coreutils in your path can cause gmp builds to fail.
[21:34] tom@toms-typewriter:~$

What you expected to happen
my new term is opening silently and bash completion is available.
Step-by-step reproduction instructions (by running brew commands)
Paste the code from the documentation in .bash_profile, save, open a new term, notice the errors.

See attached file for the output (long output)

There is no attached file.
We'll accept pull requests to improve this but the instructions work for me and we cannot support every user with figuring this out. I'll adjust the documentation so it says .bash_profile.

Hi Mike,
weird, I've used the drag & drop feature... I must have missed something
Here is another try:
bash_completion.log
In my previous setup (I'm setting up a new mac from scratch), I had only this as instruction.
# brew bash completion
[ -f /usr/local/etc/bash_completion ] && . /usr/local/etc/bash_completion

I don't know what the loop is supposed to do in the current documentation.
Also, I don't understand why this piece of code is not within the script (and detect the current shell)
It's better to have a simple include vs a complex one.
Strangely, the file is also still there:
[13:21] tom@toms-typewriter:~$ file  /usr/local/etc/bash_completion
/usr/local/etc/bash_completion: UTF-8 Unicode text, with very long lines
[13:21] tom@toms-typewriter:~$

I do not see this issue so you'll need to figure it out yourself, sorry.

my system do not have the "have" function or command.
It seems that all files in "/usr/local/etc/bash_completion.d" start with
have command name
Example:
# wol(1) completion

have wol &&
_wol()
...

There's a post on stack :
https://stackoverflow.com/questions/12874920/have-keyword-for-bash-completion
So I'm not sure why I don't have this function, and you do.
For sure, I've got a fresh system, I'm not sure on what you're testing.
Can you check where it is defined on your system ?

Sorry, you'll need to figure this out yourself.

Or our Discourse (https://discourse.brew.sh) may have people who will debug this with you.


refactor: remove redundant logger injection

Motivation
The cache already has a logger and injecting it from other packages is redundant and confusing.
Description
...
Test Plan
tests passing
TODO

[ ] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors merge


docs: modify the content of the article menu and add a video menu

 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.chenkeyao.chenkeya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Gollvm: Some existing defects

What version of Go are you using (go version)?

$ go version
go version go1.16.3 gollvm LLVM 13.0.0git linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN="/home/lyf//workspace/gowork/bin"
GOCACHE="/home/lyf/.cache/go-build"
GOENV="/home/lyf/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/lyf/workspace/gowork/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/lyf//workspace/gowork"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/home/lyf/.local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/lyf/.local/gollvm/tools"
GOVCS=""
GOVERSION="go1.16.3 gollvm LLVM 13.0.0git"
GCCGO="/home/lyf/.local/gollvm/bin/llvm-goc"
AR="ar"
CC="/home/lyf/.local/llvmtools/bin/clang"
CXX="/home/lyf/.local/llvmtools/bin/clang++"
CGO_ENABLED="1"
GOMOD="/home/lyf/workspace/gowork/src/hwprojects/beego/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3381461740=/tmp/go-build -gno-record-gcc-switches -funwind-tables"

What did you do?
I've tested gollvm on a large number of projects and that there are still some bugs in it.
Its robustness makes me uneasy

What did you expect to see?
I want to know if these bugs or defects are likely to be solved in a later version,
or if there is any way to overcome them
What did you see instead?
These bugs and defects include:

go://linkname
Access to private functions in the standard library through linkname is not allowed in gollvm, but this operation is not uncommon.
As discussed in golang-nuts
In addition, go:linkname' is only supported for functions
asm
Many projects rely on assembly functions implemented using plan9 syntax, which is not suppored by gollvm
This causes gollvm to be unavailable on these projects.
Maybe, compile the plan9 asm to an ELF object and add a bridge for it is possible?
error caused by -fsplit-stack
When compiling some projects using gollvm with a clang C compiler，the arg -fsplit-stack is add automatically, which leads to a backend err in llvm
issue 41399 mentioned it
go://embed
It seems that gollvm has not yet been very good support for this new feature
Details about it are here: issue 45880

I'd like to know if the fix of these bugs or defects is in your plan, and whether it is possible to fix them in subsequent versions
Thank you

Hi,
As you are probably aware, we don't use the issue tracker for asking questions -- better to pose your questions on a mailing list or some other forum.

Access to private functions in the standard library through linkname is not allowed in gollvm

Gollvm supports //go:linkname, just in a different way from the main Go toolchain, since its runtime and standard library are implemented somewhat differently.
In terms of using //go:linkname for non-functions, the limitations in gollvm relate to the use of the system linker. Gollvm has to emit ELF object files (in comparison with the main Go toolchain, which uses a custom object file, and which uses its own linker); because of this it seems unlikely that gollvm will support this use case any time soon.
I'll add (once again) that using //go:linkname to "reach into" the runtime/stdlib and access unexported functions is highly non-portable and not covered by any Go compatibility guarantee. Such programs can be broken at any time by a new Go release.

Many projects rely on assembly functions implemented using plan9 syntax, which is not suppored by gollvm

Regarding the assembly syntax, there is no plan to add a "plan 9 to ELF syntax" translator, this would be a major undertaking. I would recommend that when you encounter build problems of this nature that you file bugs with the project hostig the assembly, requesting that they introduce a gccgo/gollvm build tag to pick up an alternate Go version of the function in question.

...

Relating to the other bugs, yes, hopefully someone (myself or another) will try to work on these as time permits. Gollvm is an open source project; things get done because developers contribute their time to help with it.
Thanks.

Thank you for your response and reminder. We've talked about the problem of asm on golang-nuts several times：)
If necessary in my subsequent work, I will remember to add a bridge for ELF from ASM to adapt to different calling conventions.
Thanks~


Create the responsive Nav-Bar

Navbar is not responsive you need to make it responsive
you can use css or material-ui

Please assign me this issue

you are assigned to this issue


systest: fix broken selectors for chaos-mesh

they got broken when i switched systest to use deployment mode, as now pod name is not equal to its identity.

bors merge

bors cancel

need to wait with this fix. partition tests will be at best very flaky, but likely will not even work

bors try

bors merge

bors merge


Adding background image

What would you like to share or ask?
website looks too simple ,adding a background image can make it attractive.

for example,
If want change, do assign it to me under GSSOC 2023 .  :)
Additional information
No response

Please assign me this issue under GSSOC'23

Background image is only appearing to a specific length. It makes the site less attractive. Please make the background cover the the whole height of the site.


Request a channel

if possible, can you add cartoon network japan channel? thanks!

Added.

Closed as complete.

Added.

thank you!


Update PKIXCRLUtil.java

This fixes a NullPointerException in findCRLs, when a CRL does not have the nextUpdate attribute set.

Thanks for the patch, merged. Will appear in 169b05 (and later) on https://www.bouncycastle.org/betas


Review bullet point guidance

Hi,
Just having a conversation with a colleague and we were quite confused about the difference in capitalisations/full stops for bulleted lists (https://guides.service.gov.au/content-guide/content-structure/#bullet-point-lists).
I’m not sure what governed the decision around sentence fragments vs full sentences but wouldn’t it be easier if all bulleted lists followed the same style. Eg. All start with caps, last bullet ends with a full stop.
If not, some more examples might be useful, especially in relation to more complex lists where there’s some ambiguity as to if the bulleted list is a sentence fragment or not.
Thanks,
Danushka
Danushka Silva
Digital Content Advisor
Digital Casey (ViBE)
City of Casey
PO Box 1000, Narre Warren VIC 3805
T. 03 9792 7291
E<EMAIL_ADDRESS>W. www.casey.vic.gov.au

Gary to see if we can add some more examples to help make our guidance clearer.

Now being tracked in Trello


show latency from your location

Probe latencies and show them at db locations

@CodingDoug this PR - if accepted - will show an estimated location from you to each of the locations we support.
I don't know if we want an option to disable it or not, seems to me it should be always on

@athoscouto let's give @CodingDoug a chance to comment before merge.

@glommer The turso db locations command seems to now just hang on my machine with this pull request.

Best explanation I have is some requests hang for you for some reason. I can add a timeout -- which is a good idea anyway - and the failed ones should show a ??? for you, and at least help us debug it.

@penberg try now ?

nevermind, it hangs for me too. It has to do with the change I made late to move the map construction out of a goroutine as athos requested. Investigating

@athoscouto with the loop to retrieve the values after the Wait, the channel fills up =( We can add a channel with higher capacity, but my understanding is that this is an anti-pattern, because as we add more locations, and/or more retries, the channel has to be updated accordingly.
There is no race condition in retrieving the values in a go routine, as far as I can see. There is a single retriever. close() happens after Wait, making sure that the channel is only closed after all latency measurements were taken.

That's doable, but what's wrong with a goroutine that consumes as results are produced? Athos claims it is racy, I don't see a race here.
(btw, tests seem to be failing for some unrelated reason)

First observations:
The latency column is initially a bit overwhelming to take in. I think that's because the numbers are all over the place, and they are not sorted. This column would make a whole lot more sense if sorted.  The prior alphabetical sorting almost seems useless now because it's not helping me find what appears to be the most important items in the list.  In fact, I now realize the old sorting wasn't doing me any real good at all since it was sorting on the code and not a human-relatable name.
I have a concern also that there could be a discrepancy between the recommended default location and the best observed latency. If the latency is measured by the CLI but the recommended location is measured by Fly, that could create some conflict that has no obvious resolution.  Should the user pick the default or the lowest latency?  Or are the latency measurements fundamentally transient and not a long-term indicator of best performance for me?
Also a bit of a concern: we aren't explaining how the latency is calculated, so it could be misinterpreted as some indicator of overall general load at each location, which could make further locations appear unappealing as potential replica locations. The user has to already be thinking about network topology specifically from the perspective of the machine where the command is currently being run in order to make sense of this output.

I'm thinking the latency column would be easier to read if the values were right-aligned, so that the numbers are easier to compare with each other.
Also I'm wondering if maybe the entire column should be optional behind a CLI flag. You can feel the weight of this addition when running old vs. new. And I'm concerned that flakey networks might make this command feel especially sluggish if we have to wait for all these values to come in.

@CodingDoug do you feel like it adds value, behind a cli flag, or just doesn't add value at all ?

@CodingDoug do you feel like it adds value, behind a cli flag, or just doesn't add value at all ?

It adds value, but I think context is necessary to make it easier to understand what's being shown and understand how to make decisions based on it.
I will say that if it doesn't ultimately help someone make a decision, then it's both overhead and noise by default.

Then maybe db locations is not the place to show it?
For the record, I have coded this as a way to show this information somewhere else, in an upcoming PR. We just figured the latencies would be nice to show by default on locations, but if you disagree we don't have to.
(about sluggishness, the latencies are cached, so if you run again it should be fast)

Then maybe db locations is not the place to show it?

This command makes sense. I just question it as default output, which is why I wanted to consider a CLI flag.

For the record, I have coded this as a way to show this information somewhere else, in an upcoming PR. We just figured the latencies would be nice to show by default on locations, but if you disagree we don't have to.

 If the data doesn't address a common use case, then it might be considered noise. Hiding it behind a flag make this all good, and also gives an opportunity to:

Explain in the flag help text what this does
Sort the output by latency

(about sluggishness, the latencies are cached, so if you run again it should be fast)

I saw the cache, but that only really works for the cache duration, which is not that long (15 minutes?). I don't see someone really needing to run this command repeatedly within that time. I consider the main use cases of db locations to be:

Help me understand the locations I have available (and the best location choice for me) when I first get started.
Help me understand the locations I have available for adding a replica

These cases only require a single invocation, and (I imagine) are not highly likely to occur in the same 15 minute window.

Love it. If you can right-align the latency column data, even better.

Unfortunately I didn't find any way to right align it in the table
implementation I am using. That bugs me too ;(
Of course we can do a pass on the strings and pad with spaces ourselves...
or change table implementation.
I will take a quick look
On Thu, Jun 1, 2023, 11:17 a.m. Doug Stevenson @.***>
wrote:

Love it. If you can right-align the latency column data, even better.
—
Reply to this email directly, view it on GitHub
https://github.com/chiselstrike/turso-cli/pull/458#issuecomment-1572251413,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACQ3PLBSLGTEWHVAOIOU7LXJCXAVANCNFSM6AAAAAAYWGEPCE
.
You are receiving this because you were mentioned.Message ID:
@.***>

It will be a bit challenging and error prone to right align this, especially without a very good understanding how the table package works. (They do have an open bug asking for a way to right align)
I'm merging as is and we can revisit later


Threads dont show correctly

Describe the bug
Threads dont show up correctly.
To Reproduce

Create a thread inside a channel
See the bug

Screenshots

Infomation
Discord channel: Stable
OS: Linux
Mod: BetterDiscord
Discord language: English

I just noticed that there already is an issue on this: #24
I am sorry and I should have searched before creating another issue


convert  apiextensions.k8s.io/v1beta1 CRD to v1

apiextensions.k8s.io/v1beta1 does not work on k8s 1.22+
This PR fixes #6
The CRD update enables me to install this chart on AKS 1.22.
I don't know yet if the scheduler is functional.

You can ignore my previous comment - what you have seems to work just fine. Thanks again for the pull request!


Support close/destruct for modifiers

This is useful if a modifier needs to release resources before being replaced and garbage collected.

Alternatively, modifiers that need to clean up can do so themselves using a finalizer.

I think some of the modifiers that have resources to be released already support io.Closer. It needs to be hooked into the JSON API though. Regarding finalizers, see Tragedy of Finalizers.


make compile_redis: Permission denied

when try to make Docker image, I got Permission denied error in make compile_redis.
the output is below
$ make compile_redis
##MASKED##/harbor-arm
cd ##MASKED##/harbor-arm/redis && ##MASKED##/harbor-arm/redis/rpm_builder.sh && cd - ;
--2022-03-05 14:51:11--  http://download.redis.io/releases/redis-6.0.15.tar.gz
Resolving download.redis.io (download.redis.io)... <IP_ADDRESS>
Connecting to download.redis.io (download.redis.io)|<IP_ADDRESS>|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2282471 (2.2M) [application/octet-stream]
Saving to: ‘redis-6.0.15.tar.gz’

redis-6.0.15.tar.gz                                100%[================================================================================================================>]   2.18M  2.42MB/s    in 0.9s

2022-03-05 14:51:12 (2.42 MB/s) - ‘redis-6.0.15.tar.gz’ saved [2282471/2282471]

--2022-03-05 14:51:12--  https://raw.githubusercontent.com/vmware/photon/4.0/SPECS/redis/redis-conf.patch
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 844 [text/plain]
Saving to: ‘redis-conf.patch’

redis-conf.patch                                   100%[================================================================================================================>]     844  --.-KB/s    in 0s

2022-03-05 14:51:12 (4.41 MB/s) - ‘redis-conf.patch’ saved [844/844]

--2022-03-05 14:51:12--  https://raw.githubusercontent.com/vmware/photon/4.0/tools/scripts/build_spec.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3917 (3.8K) [text/plain]
Saving to: ‘build_spec.sh’

build_spec.sh                                      100%[================================================================================================================>]   3.83K  --.-KB/s    in 0.001s

2022-03-05 14:51:12 (7.15 MB/s) - ‘build_spec.sh’ saved [3917/3917]

##MASKED##/harbor-arm/redis/rpm_builder.sh: line 35: ./build_spec.sh: Permission denied
make: *** [Makefile:171: compile_redis] Error 126

modify redis/rpm_builder.sh and the code works well.
in redis/rpm_builder.sh:
@@ -29,7 +29,7 @@
 # step 3: get spec builder script, and replace version to 4, then to build the redis rpm packages
 wget https://raw.githubusercontent.com/vmware/photon/4.0/tools/scripts/build_spec.sh
 sed "s|VERSION=3|VERSION=4|g" -i build_spec.sh
-chmod 655 ./build_spec.sh && cp $cur/redis.spec .
+chmod 755 ./build_spec.sh && cp $cur/redis.spec .

 # step 4: build redis rpm.
 ./build_spec.sh ./redis.spec

I re-executed it on the linux machine according to the guide document, but did not reproduce the problem, can you describe your environment information in detail? Including what is the current executing user.
The execution process is as follows:

I use ubuntu 20.04 in cloud instance, and execute commands in normal user.
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

this is console screenshot.

I think it cause from the user don't have permittion to execute the script. (so I modified from chmod 655 to chmod 755)
The problem may not occured if I execute as group user or other user (because group and other has permittion of execution)

I use ubuntu 20.04 in cloud instance, and execute commands in normal user (default user).
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

this is console screenshot.
I think it cause from the user don't have permittion to execute the script. (so I modified from chmod 655 to chmod 755) The problem may not occured if I execute as group user or other user (because group and other has permittion of execution)

OK, I understand the issue, thanks for your feedback.
I will modify the permission problem in the rpm_builder.sh script
@ryoma310

The issue is still present in v2.10.0. It can be installed with sudo but that would not be what most users would want, to install as priviledged user.


cmd/unity: support for running Go tests for packages that use CUE APIs

Currently, unity only supports running testscript tests that are defined in the project's manifest. However some/many projects that use CUE will do so via the CUE Go APIs.
We should add support within unity for running tests against Go packages that use any of the cuelang.org/go/... packages.
Like the testscript tests, the Go tests would need to be run within a Docker container in safe mode.

cc @rawkode - this is the issue for which I will use blox as a test case for CUE Go API based test support within unity.


[ Gateway ] : Issues observed 2.0

Issue Type

[x] bug report
[ ] feature request

Current Behavior

List of issues observed on the current gateway.

Auto-switching of MM network not working. It always failed with the wrong network modal. we can put this in a better way like  You are on the incorrect network. Please click to switch to Ethereum Network so the user won't get confused.

Once bridging a token from l1 ->  L2 or Vice versa, the actions buttons on the tokens listing page like bridge to l2  and fast Bridge to L2 seems to be disabled for a some time so the user won't be able to perform any actions further. fix : Bridging Modal is getting closed before the completion of the function execution so it should show some loading / in-progress indicator

On completion of transactions L1 -> L2 or L2 -> L1 gateway should have a modal with the link to explorer using tx hash so the user can navigate to BobaScan or EtherScan easily without navigating to the history page.

Api watcher on goerli failing with 502.

Use of the boba fee only works for L2 so we should show the fee switching option in case of layer 2 only.

Stake modal design is not aligned with other models on the gateway.

History Page:

Fix the transactions list design and make it more aligned with other gateway design fonts are not readable.
In case the bridge between l1's tx hash link is broken, navigating the user back to the gateway back, better to remove the link if it's not a valid link or fix the link with LayerzeroScan.

Ecosystem Page:

Complete project description is only visible when the user hovers over the card which is good on a desktop or computer screen but in the case of mobile should show the option to show more and less as it's difficult to hover on the card in mobile.

Mobile View Notes:

Gas Fee is not visible in mobile view, which can be seen at the footer on the desktop.
Fee Switcher Tool tip is not visible
Menu listing style is broken
Menu is not closing on clicking menu item
Alignment of the theme icon is not correct in the case of the menu
History page tabs styling doesn't looks good on mobile, need designer thoughts.
Dao Page Style on Mobile needs to fix, need designer thoughts.

How is this breakind down going?

Added corresponding tasks to project

Closing as completed


propagate title and href by default

Fixes #617.

The locale (https://github.com/observablehq/plot/issues/384) should also apply to "Other".


Too many (700)  warning when building MapboxGLAndroidSDKTestApp

Describe the bug
We have a lot of warning when building MapboxGLAndroidSDKTestApp. The list is attached.
Expected behavior
Some will be trivial to fix, others, like deprecated APIs are more involved. We can fix the easy ones and enter more tasks for more difficult ones. Some I am sure also can be safely ignored.
Platform information (please complete the following information):

OS: Android

MapboxGLAndroidSDKTestAppWarnings.txt

With recent changes, it would be interesting to get an updated log.


Error: PlatformException(error, Expected a value of type 'int', but got one of type 'String', null, null)

Got an exception on web. Launched with Chrome.
Error: PlatformException(error, Expected a value of type 'int', but got one of type 'String', null, null)
    at Object.throw_ [as throw] (http://localhost:61847/dart_sdk.js:5334:11)
    at StandardMethodCodec.decodeEnvelope (http://localhost:61847/packages/flutter/src/services/system_channels.dart.lib.js:792:19)
    at MethodChannel._invokeMethod (http://localhost:61847/packages/flutter/src/services/system_channels.dart.lib.js:956:47)
    at _invokeMethod.next (<anonymous>)
    at http://localhost:61847/dart_sdk.js:39032:33
    at _RootZone.runUnary (http://localhost:61847/dart_sdk.js:38889:58)
    at _FutureListener.thenAwait.handleValue (http://localhost:61847/dart_sdk.js:33875:29)
    at handleValueCallback (http://localhost:61847/dart_sdk.js:34435:49)
    at Function._propagateToListeners (http://localhost:61847/dart_sdk.js:34473:17)
    at _Future.new.[_completeWithValue] (http://localhost:61847/dart_sdk.js:34315:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:61847/dart_sdk.js:34338:35)
    at Object._microtaskLoop (http://localhost:61847/dart_sdk.js:39176:13)
    at _startMicrotaskLoop (http://localhost:61847/dart_sdk.js:39182:13)
    at http://localhost:61847/dart_sdk.js:34689:9

Same issue

The last version 2.0.1 fixed.

Is it possible that the bug is still present in 2.0.1 ? Looking at the last commit, the changelog and version number have been update, but the actual fix seems to be missing.


Made ParameterInfos.cs use object.equals during parameter Add as well

Created a test and fix for ParameterInfos.Add using object.equals so duplicate parameters are handled properly.

Thanks.  Let me know when nuget is updated.

Thank you for your help on this.
I've just published nuget 1.0.7.


Enhance snipe jumplist interaction

from sneak.vim README:

Press ctrl-o or `` to go back to the starting point.
This is a built-in Vim motion; Sneak adds to Vim's jumplist only on s invocation—not repeats—so you can abandon a trail of ; or , by a single ctrl-o or ``.

Can we get this behaviour by leaving :jump t under evil-snipe-def, and setting :jump nil on evil-snipe-repeat and its reverse? After this discussion, I realised that pushing to the jumplist after every small jump is not how vim does it by default either.
edit: maybe making this customisable would be better so those who prefer the current behaviour, or even no jumplist at all can have their way.

Fixed! I thought the default vim-sneak behavior was best. The previous behavior can be done via snipe's repeating feature.


add The Awakened King armors and update labyrinth gauntlets

hiya, I went through and added the two new armor sets "Crimson Guard" and "Zealot's", and updated the Lab gauntlets that the devs accidentally made more powerful than intended and fixed in the dlc patch. I don't know how to add new armor sets but here's the data.ts with all the updated stats, formatted like all the other armor sets are and properly alphabetized.
data.txt

Oh that's awesome, thanks for your work! I'll get that update in when I get home from work tonight.
As a secondary question: are you unable to make pull requests or some other permission issue? Or are you just unfamiliar with the process. (github permissions are weird and I don't know if I have them quite correctly)

I'm not familiar at all no, I made this account just to help get the tool updated so I could use it again. If you'd prefer I can look into how it works and try to do a pull request the next time there's an update?

I totally forgot to do this after work that day, but someone put a helpfulp PR up, so it's merged and I deployed. Tested and all the new stuff seems there.