presto-admin documentation updates

Nit: in my opinion, 6 commits for this is a little much. I would squash the smaller changes into one commit and have a bullet point for each item changed.
Brenda should probably proof read this for grammar and style.
Looks good.

Squashed the commits together & updated

Merged

Now continues my unfamiliarity with GitHub comments! I see now that this PR is closed, but I still made comments in the closed files. I'll get with Christina to see what to do!

@BrendaNoonan thanks for the review! I addressed your comments in https://github.com/prestodb/presto-admin/issues/166.

You’re welcome!
From: Christina Wallin<EMAIL_ADDRESS>Sent: Wednesday, March 23, 2016 7:50 AM
To: prestodb/presto-admin
Cc: Noonan, Brenda C
Subject: Re: [presto-admin] presto-admin documentation updates (#149)
@BrendaNoonanhttps://github.com/BrendaNoonan thanks for the review! I addressed your comments in #166https://github.com/prestodb/presto-admin/pull/166.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/prestodb/presto-admin/pull/149#issuecomment-200377487


Added appveyor configuration

Closes https://github.com/elcodi/bamboo/issues/601

@mmoreram this PR should be ready


upgrade --force does not work as described

Output of helm version:
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-05-12T04:12:12Z", GoVersion:"go1.9.6", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
minikube version: v0.27.0

helm upgrade --force release chart should work as
helm delete release && helm install --replace -n release chart but it does not - using the former resources are not redeployed if no change happened.
Steps to reproduce: create some dummy helm chart and then:
INSTALL
helm install -n job-test ./panchenkoinit

NAME:   job-test
LAST DEPLOYED: Tue Jun  5 16:43:27 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                DATA  AGE
job-test-configmap  1     0s

==> v1/Job
NAME     DESIRED  SUCCESSFUL  AGE
example  1        0           0s

==> v1/Pod(related)
NAME           READY  STATUS             RESTARTS  AGE
example-bl4db  0/1    ContainerCreating  0         0s

TRY TO FORCE UPGRADE
helm upgrade --force job-test ./panchenkoinit

Release "job-test" has been upgraded. Happy Helming!
LAST DEPLOYED: Tue Jun  5 16:44:46 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                DATA  AGE
job-test-configmap  1     1m

==> v1/Job
NAME     DESIRED  SUCCESSFUL  AGE
example  1        1           1m

==> v1/Pod(related)
NAME           READY  STATUS     RESTARTS  AGE
example-bl4db  0/1    Completed  0         1m

Note the age of the resources and the fact, that no new pod was started for the job.
DELETE AND REINSTALL
helm delete job-test
release "job-test" deleted

helm install --replace -n job-test ./panchenkoinit
NAME:   job-test
LAST DEPLOYED: Tue Jun  5 16:46:57 2018
NAMESPACE: default
STATUS: DEPLOYED

RESOURCES:
==> v1/ConfigMap
NAME                DATA  AGE
job-test-configmap  1     1s

==> v1/Job
NAME     DESIRED  SUCCESSFUL  AGE
example  1        0           1s

==> v1/Pod(related)
NAME           READY  STATUS             RESTARTS  AGE
example-skzhj  0/1    ContainerCreating  0         1s

Now the resources indeed have been re-deployed - see their age and the new pod for the job

I think I understand why this is happening - @bacongobbler can you confirm the requested behavior in the issue (i.e. delete and recreate) is preferred? If so, I'll submit a pr :)

I have also encountered this issue with jobs.
I have a helm chart that has configmap and a job (that is deleted after success).
The purpose of the job is to download and install some static content filess (web apps) via npm.
However helm upgrade fails to run the job.
My job definition looks like this.
apiVersion: batch/v1
kind: Job
metadata:
  name: {{ template "ui-apps.fullname" . }}
  labels:
    app: {{ template "ui-apps.name" . }}
    chart: {{ template "ui-apps.chart" . }}
    release: {{ .Release.Name }}
    heritage: {{ .Release.Service }}
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-delete-policy": hook-succeeded
```

I've tried even with --install:
```
helm upgrade --install staging-ui-apps --namespace staging ./ --force --debug
```

kubernetes 1.11.0

```
helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
```

To ensure that tiller makes every best effort to do a graceful upgrade, --force first attempts the "gentle" approach first before disrupting services' traffic with an ungraceful upgrade.
If the previous release was in a DEPLOYED state and can be cleanly upgraded, then it will just do a normal helm upgrade. the helm delete && helm install --replace logic doesn't kick in unless the initial attempt to do a graceful upgrade fails.
Does that help clear things up?

@bacongobbler thanks.
I think it works and I have been confused. I expected the Job to run longer but it was over and cleaned inb ~4s so for me it works.

Hi, @bacongobbler. Can you help to find a way to “reinstall” same release if my resource was broken? I  just tried to use helm upgrade --force to “reinstall” same release but it may do a graceful upgrade b/c this reelase didn't have any changes.

Closing as answered.


infinite rejoin when setting up a UDP proxy on iOS devices from agora_rtc_engine 6.2.2

Describe the bug
infinite rejoin when setting up a UDP proxy on agora_rtc_engine 6.2.2.

This occurs lag video/audio stream

To Reproduce
Steps to reproduce the behavior:

Initialize Engine
Set the proxy server to udp
Join the channel
See infinite loop on RtcEngineEventHandler onConnectionStateChanged.

Expected behavior
Just run only one rejoin the action
Screenshots

Smartphone :

Device: iPad Pro 12.9
OS: iOS 16.6
Browser [e.g. stock browser, safari]
Version iOS 16.6
agora_rtc_engine: 6.2.2

Additional context
There is no this issue on agora_rtc_engine: 6.1.1+1
There is no issue on Android devices

I think it's better to raise a new ticket to Agora Support for further investigation of this issue.


pm2 deploy utilize 100% cpu and get crashed.

@ I am deploying my react app on ec2 instance using pm2. I created app using create-react-app.
whenever I run pm2 deploy ecosystem.config.js production sever get crashed and I received error  fork: Cannot allocate memory

Then I am unable to ssh on server. also it doesn't create all required file in build folder. It shows only 3 files in build folder favicon.ico,  favicon.png and manifest.json
when I build in my local with production env build create properly.
Any help is appreciated thanks in advance.

You are probably running out of memory, try creating a swap file or using a more powerful ec2 instance.


publish to openvsx

Please consider publishing the vscode extension to open-vsx.org
The latest version of VSCodium has switched to using openvsx as the extensions provider. (VSCodium is a project which seeks to provide a 100% open source version of VSCode).
You can read more about openvsx here.

Register on open-vsx.org through GitHub OAuth.
Create an access token and copy it.
Run npx ovsx create-namespace  --pat  with the publisher name specified in the extension’s package.json.
Run npx ovsx publish --pat  in the directory of the extension you want to publish.

The publish itself shouldn't be too hard to setup. However I don't know if https://github.com/open-vsx/publish-extensions/issues/41 ([matklad.rust-analyzer] error TS2307: Cannot find module 'vscode' or its corresponding type declarations.) is a problem with rust-analyzer or the specific setup at open-vsx/publish-extensions.

We don't have bandwidth to publish to more than one marketplace. People are encouraged to re-publish from Microsoft's store to open-vsx though.

publishing requires non-trivial amount of maintenance work from developers.

I don't think this cost is very high: Publishing to OpenVSX uses the same tech as publishing to Microsoft marketplace (i.e. both use vsce).
So, you could imagine adding one extra line to your existing Microsoft publishing script, and that line is:
npx ovsx publish

That's it. (It also requires a OVSX_PAT token that you can get from here, but otherwise there is no additional maintenance cost.)

The biggest cost here is maintaining a separate trusted identity (token) for a openvsx store. Some additional smaller costs are:

having one more failure point during release process (if open vsx is down, release process breaks)
having one more npm external dependency (ovsx) which needs to be versioned, updated, etc.

More generally, anything that touches build and/or release process, in my experience, is a big cost, even if the actual diff is small.

Good points, thanks for explaining them.

The biggest cost here is maintaining a separate trusted identity (token) for a openvsx store.

This still doesn't seem significant to me (i.e. visit https://open-vsx.org/user-settings/tokens once, generate a token, save it in GitHub Secrets, done). But maybe you're considering things like regular secret rotations?

having one more failure point during release process (if open vsx is down, release process breaks)

True, but since it's non-critical, npx ovsx publish errors could simply be ignored (e.g. with something like npx ovsx publish || true).

having one more npm external dependency (ovsx) which needs to be versioned, updated, etc.

Actually, npx just fetches the latest release of a NPM package (here ovsx) to run it on-the-fly, so there is no need to add a dependency (other than npx, which comes built-in to npm) or to care about its version.

FYI it's being republished now as a daily job, but that means that updates are reaching users delayed by up to a day.


Print ingress class name while describing ingress resource(s)

What would you like to be added:
Add spec.ingressClassName in the output of kubectl describe ingress <ingressName/no-name-but-list>
Why is this needed:
Now that ingress controllers use spec.ingressClassName to decided weather it should implement that particular ingress or not, It is important for a person maintaining the cluster to know which ingress is being implemented by which ingress controller thus class.

I am willing to work on it once it's triaged
Thank you

I see no reason why we shouldn't do this :)
Also, maybe adding this to the kubectl get ingress is something desired? IMO it is

That makes sense too
It should be added in both get and describe outputs

/triage accepted
/priority backlog
/help
This work would be done here https://github.com/kubernetes/kubernetes/blob/afd254a18f1a3ac44f8cdb7b6f0f1a83d35f3a37/staging/src/k8s.io/kubectl/pkg/describe/describe.go#L2544

/assign @akshitgrover
/remove-help
/remove-good-first-issue
@akshitgrover this gots accepted. As you are willing to work on it, go for it!

Hey not sure if this is still actively being worked on but was poking around. It looks like the class got added in kubectl get ingress at some point. Looks like a simple one(-ish) liner to get this added to the describe output. I can push a PR for it but wanted to make sure I wasn't stepping on anyone's toes.


when use:gorm.Table("xxxx").Where("id in (?)", ids).Find(&object),  can not find record!

i print sql found:
id in ('5d0b31c7a1a8881fbfbc9ace000000ce,5d0b31c7a18881fbfbc9acf000000ce,5d0b31c7a1a8881fbfbc9ad0000000ce')
it should be id in ('5d0b31c7a1a8881fbfbc9ace000000ce','5d0b31c7a18881fbfbc9acf000000ce','5d0b31c7a1a8881fbfbc9ad0000000ce')

db.Error 有看吗？

db.Error 有看吗？

没有ERR错误信息

it's my fault, 5d0b31c7a1a8881fbfbc9ace000000ce,5d0b31c7a18881fbfbc9acf000000ce,5d0b31c7a1a8881fbfbc9ad0000000ce was a element in ids array


fingerprintx: 1.1.13 -> 1.1.14

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/praetorian-inc/fingerprintx/releases.
meta.description for fingerprintx is: Standalone utility for service discovery on open ports
meta.homepage for fingerprintx is: https://github.com/praetorian-inc/fingerprintx
meta.changelog for fingerprintx is: https://github.com/praetorian-inc/fingerprintx/releases/tag/v1.1.14
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.14 in filename of file in /nix/store/2f2ksni8l2f059w8yqnl9a43zab1bvff-fingerprintx-1.1.14

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

fingerprintx

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/1f060539ebee1587b726cc03e40c668fc1554721#fingerprintx

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

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

1 package built:

fingerprintx

Maintainer pings
cc @fabaff for testing.

Add a :+1: reaction to pull requests you find important.

mythical PR number :sparkles:  :sparkles:  :sparkles:


[Needs Review] b07902059 陳君翰

A Pull Request (PR) should explain why we need this PR and how you implement it, so others could understand it quickly.
Since this is just a homework, you do not need to explain why and how.
Do NOT change the status to NeedsReview if you do not want to be graded yet.
Please fill in the following questions as feedback. It is totally optional and would not be graded.
What is the most challenging part in this homework?
git/ github, task5, task8
Is this homework helpful for you?
i think so
Is there any suggestion?
need more help, for instance, reference, lecture and more specified instructure.

PR readiness check list

[O] Did it pass the Flake8 check?
[O] Did you test this PR?
[O] Did you change the title of this PR to the correct format ([status] student_ID)? not yet

Did you come for the TA hours for help?

Did you come for the TA hours for help?

yes, i did go to the first TA hours, but i didn't go to the second one

@b07902059 sure. You already made your submission; the merge deadline is 12/12. You could choose not to fix it as well.

Urrr... i had tried my best to link the user and email account and tried to rebase some of the commits. However, none of them worked... if it is possible and needed, i would like to ask for an appointment to have further understanding regarding to this issue. thank you very much~

@b07902059  Did you force-push it to your forked repo try3 branch? I would probably have extra TA hours today but it's not guaranteed.

@b07902059 Did you force-push it to your forked repo try3 branch? I would probably have extra TA hours today but it's not guaranteed.

no... i didn't...
Is it possible for me the try later? Or is this file already closed, so i can't change anything now?

The merge deadline is 12/12.

@b07902059 Add a comment in task8 would be enough.

I finish adding reference for task 8!
However, I don't know why, after I link the commits to my profile (and force push it), 2 more files pop out and I have more participants. What is going on? How should I fix this?

@b07902059 Your code is from a previous commit and it's outdated now. Please see https://github.com/amjltc295/PythonHomework#update-local-and-remote-repository and rebase to the latest code.

@b07902059 Star if you like :)


wire in fuchsiaApp

Description
Fixes #33691 - but does not really add much in the way of actually validating the project (there are other related TODOs for that).
flutter drive was failing in this case because the Fuchsia branch of this logic was always returning null.
There are other futher errors related to the timeline data that I'll file a separate issue for.
Tests
I added the following tests:
Tests for Fuchsia app creation.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

@dnfield I wonder is Fuchsia an OS to replace Chrome OS or what is Fuchsia app here?

@amorenew - that's not really my area of expertise.  You could read more about Fuchsia in general here: https://fuchsia.googlesource.com/fuchsia/+/master/docs


Hint using '--force' when assignment already exists

Currently when using gto assign to assign a stage to an artifact's version that has already happened, GTO return an error like:
❌ Version 'v3.0.0' is already in stage 'prod'

It might be helpful to include option to use --force in this message, as it might be what a user wants to do, turning the message into something like:
❌ Version 'v3.0.0' is already in stage 'prod'. Use the '--force' flag to reassign the 'prod' stage to version 'v3.0.0'

@aguschin - I think it might be nice to be a bit more verbose about the options available to the user here. Opened #267 - let me know if this is desirable.


Handle Crypto Icon Files with Reserved Names in Windows

Some crypto icon files can have the same names as reserved names on Windows. This causes the file to not write to disk on Windows, so the icon would fail to load for Windows users. It also causes some issues when developing, as the file shows up in Github as having been deleted when you don't want to commit a change to delete it.
The reserved names are:

CON
PRN
AUX
NUL
COM1
COM2
COM3
COM4
COM5
COM6
COM7
COM8
COM9
LPT1
LPT2
LPT3
LPT4
LPT5
LPT6
LPT7
LPT8
LPT9

See also https://msdn.microsoft.com/en-us/library/aa365247#namespaces

Closed by #1423


Adding DKIM signature raises TXT record too long

If I want to add a DKIM signature as a RR for a domain, it raises the following stack trace. In BIND/ NSD, one can separate the TXT record in quotes to accommodate this case. But what's the workaround for this in dnslib?
Traceback (most recent call last):
  File "ddns.py", line 56, in <module>
    D._domainkey.mail: [TXT(DKIM)],
  File "python3.8/site-packages/dnslib/dns.py", line 1114, in __init__
    raise DNSError("TXT record too long: %s" % self.data)

Most likely passing an array of strings to the TXT record constructor solves this issue.


[samples] (Charts) Adding Chart and ChartSeries samples

Addresses #121.

Docs Build status updates of commit 9befbe4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/docs-ref-autogen/excel/excelscript/excelscript.chart.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/docs-ref-autogen/excel/excelscript/excelscript.chartplotby.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/docs-ref-autogen/excel/excelscript/excelscript.chartseries.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/docs-ref-autogen/excel/excelscript/excelscript.worksheet.yml
:white_check_mark:Succeeded
View (office-scripts)

docs/sample-scripts/excel-scripts.yaml
:white_check_mark:Succeeded

generate-docs/json/excel/snippets.yaml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fixed issue with existing ratings not being populated in edit mode - Update form.php

Fixed issue in form.php with incorrect variable being called. Previously, the ratings attribute was not being passed correctly into service.php when output method was called.
Check these before submitting new pull requests

[x] I read the guidelines for contributing linked above

[x] PHP-only files follow our coding style; in order to do that use php-cs-fixer - http://cs.sensiolabs.org/ - as follows:
php-cs-fixer fix --config=<webroot>/.php_cs.dist <filename>

If all the above conditions are met, feel free to delete this whole message and to submit your pull request, and... Thank you, your help is really appreciated!

This looks great, thank you!


Library does not work on MAUI

Describe the Bug
Because of the peculiarity of MAUI data-binding, normal dependency inject syntax will not work, and we have to use a ServiceProvider "shim" which may be part of the problem.
Steps to Reproduce
I've provided a video
(https://youtu.be/CKxHnH2Szc4)

You haven't called the generated builder.Services.AddServices(); to register the discovered services, which is documented in the readme.

Confirmed! I missed that. Thanks! Very helpful lib.

Shipping an update now that will generate a build warning when this exact same scenario happens :). Should make it easier to fall in the pit of success


Please Provide Flutter Examples using RxT<> and other Rx Collections.

First of all, thank you for making this excellent library. I am doing some testing and I struggled to get RxT<> to work with my custom non-primitive objects. The issue I experienced is that the SuperBuilder seemingly did not detect changes to the state of RxT<> observables.  I am not sure if developers are meant to use SuperBuilder with these types... But SuperBuilder did work well with primitives such as "0.rx".
Just a few more examples of this use case could be very helpful.
Thank you again !

Good day, Thank you for taking your time out to try the package!.
To solve the problem you're having, you have to mixin the SuperModel class with your Custom Type. E.g class BoxModel with SuperModel {}.
I am already working on more examples as well as full projects and they will be out soon. 👌

Also if you try any other feature you think should be working but isn't, take a look through that exact package's ReadMe as I have documented 95% of the APIs and how they can be used.

Thank you so much for the reply. I just found the ReadMe and it is very helpful. And may I ask, with something like RxList, does that also require use of a SuperModel or is there a way to use RxList with SuperBuilder without any additional classes/extensions ?

If you're performing operations on the same list e.g myList = [].rx;, myList.add(1);, then no you don't need any extras, but if you intend to change a whole list at a go e.g myList = [1].Rx;, myList = [2] or [2].rx;, what you're doing is reassigning the variable, instead use an RxNotifier, that way you would be able to change the whole List at a go and if the items in the new list do not correspond with the items in the old list it will trigger a rebuild.

Thanks, I'll give that a shot!

I made a mistake with my answer earlier, even when performing operations on the same list, it can not be used with a SuperBuilder and will result in an error, to fix this you should instead make use of the SuperConsumer widget as it allows you to specify the Rx object to watch. This is because the SuperBuilder can only watch Rx objects that have a .state property.

If you're performing operations on the same list e.g myList = [].rx;, myList.add(1);, then no you don't need any extras, but if you intend to change a whole list at a go e.g myList = [1].Rx;, myList = [2] or [2].rx;, what you're doing is reassigning the variable, instead use an RxNotifier, that way you would be able to change the whole List at a go and if the items in the new list do not correspond with the items in the old list it will trigger a rebuild.

I made a mistake with my answer earlier, even when performing operations on the same list, it can not be used with a SuperBuilder and will result in an error, to fix this you should instead make use of the SuperConsumer widget as it allows you to specify the Rx object to watch. This is because the SuperBuilder can only watch Rx objects that have a .state property.


[Patch] Aggregation of several functionalities

If you use this patch you will be able to use several features that have been pull requested.
But as the repo seems abandoned it might be easier that way.
Circle #61
Geojson #36
Custom Marker #21
Polygon #69
fitToCoordinates #56
You can download the file here
react-native-web-maps+0.3.0.patch

If you use this patch you will be able to use several features that have been pull requested. But as the repo seems abandoned it might be easier that way.
Circle #61 Geojson #36 Custom Marker #21 Polygon #69 fitToCoordinates #56
You can download the file here react-native-web-maps+0.3.0.patch

Awesome, thank you


RN 0.62.0 update = 'folly/gen/String.h' file not found

Hi,
I have updated app to RN 0.62.0 and it doesn't build. I got
'folly/gen/String.h' file not found with Flipper-Folly pod
Any suggestions how to fix it?

Workaround:

Add this to postinstall actions:

`cd ios && rm -rf ~/Library/Caches/CocoaPods Pods ~/Library/Developer/Xcode/DerivedData/*; pod deintegrate; pod setup; pod install --repo-update;"

Add this to podfile:

# Post Install processing for Flipper
def flipper_post_install(installer)
  installer.pods_project.targets.each do |target|
    if target.name == 'YogaKit'
      target.build_configurations.each do |config|
        config.build_settings['SWIFT_VERSION'] = '4.1'
      end
    end
  end
  file_name = Dir.glob("*.xcodeproj")[0]
  app_project = Xcodeproj::Project.open(file_name)
  app_project.native_targets.each do |target|
    target.build_configurations.each do |config|
      cflags = config.build_settings['OTHER_CFLAGS'] || '$(inherited) '
      unless cflags.include? '-DFB_SONARKIT_ENABLED=1'
        puts 'Adding -DFB_SONARKIT_ENABLED=1 in OTHER_CFLAGS...'
        cflags << '-DFB_SONARKIT_ENABLED=1'
      end
      config.build_settings['OTHER_CFLAGS'] = cflags
    end
    app_project.save
  end
  installer.pods_project.save
end

Do you see this problem when creating a new project? If this issue doesn't occur in a new project, I recommend you create an issue on the upgrade-support repo instead. Sharing your issues when upgrading on that repo will improve the likelihood that you will find others with the same problem and find fixes. It also helps others find you! 😄

For anyone else coming to this issue, for us it was caused by the gen/ line in .gitignore...!

cd ios && rm -rf ~/Library/Caches/CocoaPods Pods ~/Library/Developer/Xcode/DerivedData/*; pod deintegrate; pod setup; pod install --repo-update;

Thanks, buddy
you saved my day


adding Montana Medicare Exclusions crawler

I'm getting a strange error when trying to run the crawl. Do you know what could it be? @jbothma

Argh, sorry! Can you do a pip install -U followthemoney, please?

Done, it worked!


[Suggestion] Vue 2.0 - Replacement for $broadcast and $dispatch

First of all, thanks for all the great work so far. vuejs is by a great measure the most enjoyable frontend framework I've tried so far.
As for some of the changes that are scheduled for v2, I'd like to know if a replacement with a plugin is possible.
One thing i liked about events is the events scope where all listeners are gathered. With your suggestion for vue2 with a global event-bus, I don't see how I can replace following code:
my comp = {
    events: {
        'overlay:close': function() {
            /* handle event */
        }
    }
}

I don't miss the actual hierarchy of $broadcast and $dispatch within the component tree, but I'd really love to keep a global event bus that works together with the events object. If this is possible through a plugin, that would fit my needs. Maybe it could be possible to make $emit emit globally with an additional attribute?

Did you see this? https://github.com/vuejs/vue/wiki/2.0-features#how-to-deal-with-deprecation-of-dispatch-and-broadcast

Yep, I've seen this. My concern is, how to implement the global event bus with events registered in the event object. Is this possible?

@Nirazul something like the following in one of the lifecycle hooks may work
for (var evt_id in this.options.events)
            bus.$on(evt_id, this.options.events[evt_id])

I haven´t looked close enough to the new API but you may be able to use it as a mixin
// ...
var auto_events = {
    created: function () {
        for (var evt_id in this.options.events)
            bus.$on(evt_id, this.options.events[evt_id])},
    destroyed: function () {
        for (var evt_id in this.options.events)
            bus.$off(evt_id)}
}

// ...

new Vue({
    // ...
    mixin: [auto_events],
    events: {
        'id-selected': function () {
            // ...
        }
    }
    // ...
})

@indus
This sounds like a plan. I'll try it out when the first alpha of vue 2 is released 👍

This all sounds :+1: for application components where I control the bus that my components use. My concern here is 3rd party components. How do I listen to events emitted by an arbitrary component?

Vue components are not instantiated by the user, but by Vue internally
3rd party components are not aware of the bus system that I may or may not be using.

2.0 recommends using Vuex to inject the bus into components where you need to use events, but this seems like overkill for small projects.  I liked that Vue didn't require using Vuex or Router or even Http unless it was needed.  Also as @rpkilby states, there is no longer a universal system for 3rd party components, which will hurt the community as a whole.

@rpkilby 3rd party components still have the ability to directly $emit on themselves, they just no longer have the ability to dispatch events. This essentially ensures that a 3rd party component can only cause side effects in its direct parent, which I believe is a good thing. An isolated component being able to dispatch a event that causes side effects in its unknown parent tree sounds like a recipe for trouble to me.

An isolated component being able to dispatch a event that causes side effects in its unknown parent tree sounds like a recipe for trouble to me.

@yyx990803, totally agree. My concern is how the direct parent of the 3rd party component will be able to listen for those event. I would not want select2 to fire events on a global bus. I would (most likely*) want only the parent to get those events. How do events $emitted on yourself communicate with the parent component? I thought $emit was isolated to the component.
*There may be cases where I'd want the event to propagate beyond the direct parent. Either way, that's an application detail that the parent component would determine.

@rpkilby I guess using v-ref on the component and then listening with this.$refs.component.on('foo',(data) => {}). If the $emitted event had the relevant data sent along with it, or the affected data was .sync'd to the parent, you could handle it accordingly.  With .bind() or with an => function you would be executing the result in the parent scope.

@rpkilby with v-on:
<child @some-event="handleIt"></child>

@yyx990803 Is this correct?
var Child = {
  methods: {
     method: function() {
      var arg = ""
      this.$emit('some-event', arg)
    }
  }
}

with v-on

Holy crap I had no idea that you could do this the entire time. Where is the :facepalm: emoji.

@rpkilby subscribe to vuejs/vuejs.org repo commits :wink:

From my viewpoint of standalone component developer I would need something like

#2507 (v-on working on slot) and
#2648 (directly call function on child - should also work on slot)

to fully replace the communication of two nested, depending components. #2648 was dismissed mainly because of $dispatch and $broadcast - please reconsider.
Use-cases:
vue-card
vue-collapsible
vue-comps-scrollspy

@kaorun343 that is correct.
@paulpflug the communication between slot components and its host can be implemented by calling $parent.$emit('xxx') and listening for that event on the parent. This is tight coupling, but since you are designing tightly coupled components that are meant to be used together, I think it's the most straightforward solution.
Also, in 2.0, complex slot distribution is best handled by using a programmatic render function, which should simplify things a lot.
I'm closing this because I think most questions have been answered, and it seems there are no strong arguments against the deprecation of $dispatch and $broadcast.

I think removing $dispatch was a terrible idea. This wasn't the first ui framework/library to implement the notion of bubbling actions/events up a visual tree. It's a well established idea. Why take away this functionality on the premise that " being able to dispatch a event that causes side effects in its unknown parent tree sounds like a recipe for trouble to me"? You need to leave this responsibility to the users. I'm sure most have the common sense to use this feature appropriately. It is not a new concept!
I really can't see the benefit of this change when this library is built upon long time established web technologies/concepts such as the DOM and DOM events that do in fact bubble up the visual tree and have been doing so for years with no one complaining. Isn't the idea of components something that has been recently embraced thanks to the W3C proposal for web components? In my opinion, It only makes sense that Vue components behave similarly to regular DOM elements in regards to how event handling is done.
The proposed alternative to use a global event bus seems illogical to me when something more practical, effective, and easier to understand (due to it being a well established concept for years) already existed.
Other proposals in this thread remind me of how EmberJS wants to do it. Passing closure actions as properties to the components down each level of the hierarchy. So tedious and unnecessary! Vuejs was the reason i wrote https://www.npmjs.com/package/ember-component-action-bubbling!
Aside from this, I really like your library. But seriously, I think this was a terrible change.

Feels like I'm back in Backbone. :)
I think this change is a bit painful, but for simple apps that don't use Vuex managing on and off of events is not that difficult. If you are doing it a lot... then its possible your app benefits from Vuex anyways.
We did a huge project at work that relied on Marionette, I can attest from that that having a lot of views listening to and emitting events is not great. Making the event listening pattern less "magic" and more explicit is fine IMHO.

I have implemented a pretty simple global event bus for vue. I was developing a vue ui kit for fun and wanted to be able to open any modals from anywhere.
https://github.com/vouill/vue-geb

when using var bus = new Vue();  for replacement of $broadcast and $dispatch
there's a problem:
the child components will still process $on event after it has been destroyed !

@toby1991
https://vuejs.org/v2/guide/migration.html#dispatch-and-broadcast-replaced

// It's good to clean up event listeners before
// a component is destroyed.
beforeDestroy: function () {
eventHub.$off('add-todo', this.addTodo)
eventHub.$off('delete-todo', this.deleteTodo)
},

@fnlctrl Thks. But I've tried the $off method with add-todo, it will discard all the events in the channel add-todo .
Finally, I've found my way to solve this:
Simply make a determination of the this._isDestroyed in all situations of $on method, that would solve my problem.
I think what caused this is the method $destroy,
In vuejs 1.x, the $destroy method has a parameter which will remove the DOM completely.
In vuejs 2.x, the $destroy method remove the parameter. And in the official document, it suggest we shouldn't destroy the component by this method, and suggest us to use v-if or v-for. OR we could use this method and remove the DOM ourselves.
BUT! the $destory method cannot destroy the mixins, so, in order to avoid the component which has been destroyed processing the $emit from the bus, we should do this.

Simply make a determination of the this._isDestroyed in all situations of $on method, that would solve my problem.

@yyx990803

Sorry but you're completely off the point. $destory has nothing to do with this. Event hub is a global instance which has nothing to do with the lifecycle of components that use it.

Thks. But I've tried the $off method with add-todo, it will discard all the events in the channel add-todo .

No, that's not the case. You simply forgot to pass the second parameter. Please refer to the docs: https://vuejs.org/v2/api/#vm-off


Seperate carbon config from core to provide non-OSGi access

Resolves #1285

Closing this pull request since opening a new pull request


Writer skips fields of case class if they have default value and none was provided

Hello,
I have a case class:
case class Been(id: Int, name: String = "sample")

When I start export to json:
implicit val beenRW: ReadWriter[Been] = macroRW[Been]
val b1 = Been(1) // please note that for second field the default is used
println(write(b1, 2))

I get the following output:
{
  "id": 1
}

As you can see the other field (name) was skipped.
How to force it to produce all of the fields regardless whether the default value was used to instantiate the given field or the concreate value was provided during initialization?

You know when you usually import upickle.default._ – that's object default extends AttributeTagged.
Instead of using the default bundle, you can do:
object SerializeDefaults extends upickle.AttributeTagged{
  override def serializeDefaults = true
}

and then:
implicit val fooDefaultRW: SerializeDefaults.ReadWriter[Been] = SerializeDefaults.macroRW

I haven't done this myself but I would guess that you would generally want to use your new SerializeDefaults bundle instead of upickle.default across your codebase, otherwise you'll be dealing with two bundles and I don't know if that's a good idea.
I see the docs haven't been updated for this new(-ish) feature. If this works for you as expected, please let me know, I can send a PR to update the docs.

Hello,
I confirm that this solves the issue.
However I think that a better approach would be to alter:
trait MacrosCommon {
  def serializeDefaults: Boolean = false

to change this to true.
If someone export some object to json, then the most natural expectation is to have all the fields exported regardles of how they were initialized. Of course - in my opinion.
Best wishes,
Tomek

BTW - you can close this ticket.
Thanks for the support.


HSTS default max-age parameter update

Updating default max-age parameter of the Strict-Transport-Security header to 1 year.
1 year is the industry standard. IETF is using 1 year in the sample (https://tools.ietf.org/html/rfc6797#section-6.1.1) and sonarwhal is throwing an error if it is shorter than 18 weeks (https://sonarwhal.com/docs/user-guide/rules/rule-strict-transport-security/#what-does-the-rule-check).

 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.:x: mark-szabo sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@blowdart

A sample doesn't make it an industry standard (and the following sample indicating 1 year is another indicating 6 months). Furthermore section 11.2 of the RFC says we can consider setting the default to zero,

Additionally, server implementers should consider employing a default max-age value of zero in their deployment configuration systems. This will require deployers to willfully set max-age in order to have UAs enforce the HSTS Policy for their host and will protect them from inadvertently enabling HSTS with some arbitrary non-zero duration.

OSWAP has a sample with a very short max-age in case there are problems during rollout.
So, the "industry standard" varies, according to circumstances, or the maturity of the roll out. So my feeling is 30 days is a compromise, one which the developer can override once they're confident in their configuration.

@blowdart in this case we should update the ASP.NET Core project templates to include the configuration code (or a comment at least) as that's not that straightforward IMHO and with this default setting we are just encouraging developers to leave it on 30 days which is not that great...
// Change this to a longer period after you are confident with your configuration
services.Configure<HstsOptions>(options =>
{
    options.MaxAge = TimeSpan.FromDays(30);
});

That's fair enough, do you want to open a bug in the templating repo for it?

Yeah, sure!


Create a starter workflow

See https://github.com/actions/starter-workflows
There is also an old PR (https://github.com/actions/starter-workflows/pull/1200) which should be replaced by using this action now.

It turns out, the original PR (actions/starter-workflows#1200) has been updated (thanks @abirismyname !) and also merged.
To use in your projects, go to "Settings / Security & analysis" and set up "Code scanning". There you can choose now PMD:

I've created another PR to update to the latest v1.1.0 -> https://github.com/actions/starter-workflows/pull/1324
Seems like this needs to be updated for every release as well (see also #3), as GitHub states: "We require that these actions be referenced using the full 40 character hash of the action's commit instead of a tag".


⚠ Auth has degraded performance

In e383ad7, Auth (https://auth.k2lin.com) experienced degraded performance:

HTTP code: 200
Response time: 2103 ms

Resolved: Auth performance has improved in 7a8afc5 after 15 minutes.


No such module 'IBAnimatable' in common.swift

This is the bug I have when I compile the IBAnimatable Framework in the demo project. I have the same bug on my project. I run both projects thought despite this error.
![screenshot 2016-09-28 17 13 44]
(https://cloud.githubusercontent.com/assets/1647328/18900586/521e8e4e-859f-11e6-8a3c-741f9d0ac73e.png)
Any idea ?

@nico75005 sometimes, Xcode is not very stable. Can you clean and build again?

Yes I did. Indeed, Xcode is unstable most of the time...


Update tvpassport.com.channels.xml

Restoring my additions from #1646 that were removed by #1662
(add CBETDT.ca, WADLDT1.us, WMYDDT1.us, WHNELD9.us)

@DerpyMcDonuts Good Catch. I tried to sort thing alphabetically and thing my text editor messed up.


More cloud storage examples

Sample for making GCS object public-read
Add sample for moving blob.
@mziccard FYI

Coverage increased (+0.4%) to 84.246% when pulling f308eddcb5dfcaed89d607661cd3873deb3b9abf on jerjou:more-examples into 81278dc3cb13ec9073e4fb4bb65bb3afe7502952 on GoogleCloudPlatform:master.

PR updated - PTAL

Coverage remained the same at 84.246% when pulling d1ca2e0da4fabafc18e49521b178debf78dce541 on jerjou:more-examples into 6383cc123036214a9170f8da6d9dfa42fdb3dbc5 on GoogleCloudPlatform:master.

Coverage remained the same at 84.246% when pulling d1ca2e0da4fabafc18e49521b178debf78dce541 on jerjou:more-examples into 6383cc123036214a9170f8da6d9dfa42fdb3dbc5 on GoogleCloudPlatform:master.

Coverage increased (+0.005%) to 84.25% when pulling d1ca2e0da4fabafc18e49521b178debf78dce541 on jerjou:more-examples into 6383cc123036214a9170f8da6d9dfa42fdb3dbc5 on GoogleCloudPlatform:master.

@jerjou thanks for this!


Is there a way to make this work with Google Home?

Can someone point me to a Google home version? Or some documentation on the subject?
Or consider a feature request for this I guess.

Google is different - not a feature request but a new project. Interested in programming yourself, of just costless consuming?
Best regards
Sascha
Am 01.01.2018 um 19:39 schrieb atomi <notifications<EMAIL_ADDRESS>Can someone point me to a Google home version? Or some documentation on the subject?
Or consider a feature request for this I guess.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/25, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-_SNSeeimISPiW6LVk5NJKgEsGcGks5tGSZ0gaJpZM4RQI9E.

I was just curious. Do you have some links on similar Google Home projects for esp8266?

Well, just use Google. 1st entry http://tinkerman.cat/using-google-assistant-control-your-esp8266-devices/
But I seriously think I‘ll not use Google to get results for you. Or - again -  be a programmer and share 😉
Best regards
Sascha
Am 01.01.2018 um 22:11 schrieb atomi <notifications<EMAIL_ADDRESS>I was just curious. Do you have some links on similar Google Home projects for esp8266?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/kakopappa/arduino-esp8266-alexa-wemo-switch/issues/25#issuecomment-354677566, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKwM-5DuvvpDP0AFL8gu6OHRDZ3ojMQ2ks5tGUoSgaJpZM4RQI9E.


Error on npm run start

I mapped my existing app to this project and now when running npm run start I get the following error:
 70% 3/3 build modulesevents.js:154
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE <IP_ADDRESS>:8080
    at Object.exports._errnoException (util.js:856:11)
    at exports._exceptionWithHostPort (util.js:879:20)
    at Server._listen2 (net.js:1231:14)
    at listen (net.js:1267:10)
    at net.js:1376:9
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:63:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:82:10)

Any ideas as to what might cause this error is highly appreciated

as the error states Error: listen EADDRINUSE <IP_ADDRESS>:8080
you have a running process that is using that port.
to find the PID on linux:
$ netstat -tulpn
to kill the process:
$ kill -15 <PID>
or
$ killall <NAME>
for more information:
$ man netstat
$ man kill
$ man killall


go get instructions produce an error

$ mkdir foo && cd foo
$ pulumi new -s temp -n temp -d temp -g --secrets-provider passphrase go
$ go get github.com/pulumi/pulumi-okta/sdk/go/...
go: downloading github.com/pulumi/pulumi-okta v1.6.0
go: downloading github.com/pulumi/pulumi-okta v2.1.3+incompatible
go get github.com/pulumi/pulumi-okta/sdk/go/...: module github.com/pulumi/pulumi-okta@upgrade found (v2.1.3+incompatible), but does not contain packages matching github.com/pulumi/pulumi-okta/sdk/go/...
$ echo $?
1

However, navigating to the Okta intro page shows a package with v2 in the URL, which works much better:
$ go get github.com/pulumi/pulumi-okta/sdk/v2/go/...
go: downloading github.com/pulumi/pulumi-okta/sdk/v2 v2.1.3
go: found github.com/pulumi/pulumi-okta/sdk/v2/go/... in github.com/pulumi/pulumi-okta/sdk/v2 v2.1.3
go: downloading github.com/pkg/errors v0.9.1
...etc etc...

Looks like since our switch to the new module structure, we probably need to do this across all provider repos.

Hi @mdaniel
My apologies here - I have fixed this now in master - thanks for bringing this to my attention
Paul


ReloadLibraries command

See this conversation: https://community.graphisoft.com/t5/Developer-forum/archicad-additional-json-commands-please-recompile-it-for-AC-26/td-p/372854

Merged, it will be available in the next release.

Thank you for merging, this helps a lot.
Best
c


error when train

When  I input python experiments/fcis/fcis_end2end_train_test.py --cfg experiments/fcis/cfgs/resnet_v1_101_coco_fcis_end2end_ohem.yaml, It made an error

Apparently, you didn't download the annotation file which stated in the README

@Oh233 thanks for your answer. I have download COCO dataset ,minivaland val2014 minus minival (val35k) ,but  I didn't download VOC 2012 dataset. I don't know how to download the instances_train2014.josn.

@sifengyang http://images.cocodataset.org/annotations/annotations_trainval2014.zip

@Oh233 Thank you very much. when I read train_end2end.py , I find that I just have download train2014  and There is  a lack of valminusminival2014. I cann't find the link of downloading valminusminival2014.

Then please read README carefully.

@Oh233  I have solved the problem. But I meet anther problem.

I don't know how to get it. please help  me .


feat(nexus): adding support for disabling nexus reset logic

In response to initiator timeout, nexus could be reset. This seemed to cause issues, so nexus reset logic is now temporarily disabled by default.
Reset logic can be re-enabled by setting env var ENABLE_NEXUS_RESET=1.

bors merge


ORC-1146: Float category missing check if the statistic sum is a finite value

What changes were proposed in this pull request?
This pr is aimed at checking whether the float category statistic sum has a finite value.
Why are the changes needed?
When the orc float category is written with NaN, pushing down is not supported.
How was this patch tested?
Added unit test.

Hi, @guiyanakuang .

Could you make a backporting patch to branch-1.7, please?
This works in main branch but not in branch-1.7. We need to pass CI.

I deleted my previous comment about the branch-1.7 test result.
At a clean build, I verified this patch in branch-1.7 and backported. Thank you again, @guiyanakuang .
Could you re-run your integration tests, @williamhyun ?

BTW, @guiyanakuang . Could you check branch-1.6 too when you have a time? We backported the following in branch-1.6. I guess we might have the same issue there.

https://github.com/apache/orc/pull/1055

Thanks @dongjoon-hyun . I checked the branch-1.6 and confirmed it has the same problem. This pr can just cherry pick and fix it without any conflicts.

Thank you, @guiyanakuang .


MAC OS X receiver

hi, I don't know where to put this, but I was able to brew install pulseaudio and use pulseaudio receiver on mac os x... hope that helps someone

Can I add this here? A feature request for a macOS transmitter/sender. It will only easily support network mode. It can be a user mode driver, similar to the BackgroundMusic driver, so it won't need kernel signing.

Sorry to bother everyone :(
could anyone explain to me how that works? I managed to brew install pulse audio, but I can't get the dev things for obv. reasons,
when trying to run scream-pulse after make I just get
> devy@devys-iMac pulseaudio % ./scream-pulse -p 4011 -i en0
> W: [] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
> Unable to connect to PulseAudio. Connection refused

It seems that pulseaudio is not running, open another terminal and run pulseaudio then run again scream-pulse. I've just tested on MacOS Catalina and it does connect to pulseaudio (I didn't stream anything, I don't have a windows pc here).
You can also run pulseaudio as a daemon with pulseaudio -D.

I have this working great, however my the latency of pulseaudio on the receiving end (osx / macos) is fixed at 250ms.
Pulseaudio is very new to me and i'm currently pulling my hair out trying to lower the PA fixed-latency of all my audio devices.
I know this probably isn't the correct or most appropriate forum to ask, but does anyone have any idea of how to lower the fixed latency?
@kourindouhime how is the latency for you?
Below is the output from pacmd list-sinks
index: 1 	name: <Out_1__Out_2__Out_3__Out_4> 	driver: <module-coreaudio-device.c> 	flags: HARDWARE DECIBEL_VOLUME LATENCY FLAT_VOLUME 	state: RUNNING 	suspend cause: (none) 	priority: 9000 	volume: mono: 65536 / 100% / 0.00 dB,   mono: 65536 / 100% / 0.00 dB,   mono: 65536 / 100% / 0.00 dB,   mono: 65536 / 100% / 0.00 dB 	        balance 0.00 	base volume: 65536 / 100% / 0.00 dB 	volume steps: 65537 	muted: no 	current latency: 12.17 ms 	max request: 0 KiB 	max rewind: 0 KiB 	monitor source: 1 	sample spec: float32le 4ch 48000Hz 	channel map: mono,mono,mono,mono 	             Mono 	used by: 1 	linked by: 1 	**fixed latency: 250.00 ms** 	card: 1 <UMC404HD_192k> 	module: 8 	properties: 		device.string = "UMC404HD 192k" 		device.product.name = "UMC404HD 192k" 		device.description = "UMC404HD 192k" 		device.access_mode = "mmap" 		device.class = "sound" 		device.api = "CoreAudio" 		device.buffering.buffer_size = "8192" 		device.vendor.name = "BEHRINGER" 		device.icon_name = "audio-card"

@jollybully  did you manage to reduce the latency?

By implementing support fore coreaudio, the latency should be very low.

By implementing support fore coreaudio, the latency should be very low.

Someone can make a guide to how to connect macOS receiver with Windows server?

I was able to use the raw output function in conjunction with ffplay to get audio output with decent latency.
./scream -o raw  | ffplay -f s16le -ar 44100 -ch_layout stereo -fflags nobuffer -


Update 99designs/gqlgen and regenerate GQL code

Description
Bump 99designs/gqlgen to v0.17.5 to fix the following error:
make generate
GO111MODULE=on go generate ./...
internal error: package "github.com/vektah/gqlparser/ast" without types was imported from "github.com/99designs/gqlgen/graphql/introspection"

The errors seems to have been first reported here: https://github.com/99designs/gqlgen/issues/1675

This PR updates from 0.10 to 0.17, which introduces some breaking changes (as can be seen in the build error logs).
It looks like most of the breaking changes came in 0.11. There's a migration guide that can offer some help: https://gqlgen.com/recipes/migration-0.11/


Question: update key

Is it possible to somehow modify objects keys themself (not their values)?
// I have this object
 let object = {
    name: 'foo'
  };

// and I want to traverse all nodes and update their key names
  let updatedObject = {
    updatedName: 'foo'
  };

I think below is what you are looking for, since reference of object is passed to forEach, we can perform any operation on it and actual object will be changed.
const object = { name: 'foo', value: { name: 'bar' } };
traverse(object).forEach(function modifyKey() {
if (this.parent && this.parent.node.name !== undefined) {
this.parent.node.updatedName = this.parent.node.name;
delete this.parent.node.name;
}
});
// Output
{ updatedName : 'foo', value: { updatedName : 'bar' } }

thanks @yashpatelyk, it works perfectly


Update bluz71/vim-nightfly-colors & bluz71/vim-moonfly-colors

Hello, author of nightfly and moonfly colorschemes speaking. Both these colorschemes, which have long supported Tree-sitter, have been listed here (for quite a while). Many thanks for that.
This PR simply updates the existing section with more appropriate taglines and well as taking into account that the nightfly theme has been slightly renamed from vim-nightfly-guicolors to vim-nightfly-colors.
Also note, don't let the vim- prefix trick anyone; both these themes fully support Neovim (e.g. Treesitter, Diagnostic, Telescope, NvimTree, etc).
Checklist:

[x] If it's a colorscheme, it supports treesitter syntax.

Thanks for the PR!

Hello! I am using AstroNvim. Connected theme bluz71/vim-nightfly-colors.
I want to enable transparency.
I found this information in the description of the thread:
The nightflyTransparent option specifies whether to use an opaque or transparent background in GUI versions of Vim. By default this option is disabled. If you would like a transparent background then add the following to your initialization file:
-- Lua initialization file
vim.g.nightflyTransparent = true
I do not understand where to insert and how to do it correctly. Please help me.
Thanks in advance!


Slow tf.hessians slicing

Hi, I'd like to calculate the diagonal matrix of some hessian:
I've got some variables a, b of shape (5, <num_features>) and I'd need for each feature the hessian's diagonal:
>>> [self.a, self.b]
[<tf.Tensor 'Linear_Batch_Model/a/concat:0' shape=(5, 10000) dtype=float32>,
 <tf.Tensor 'Linear_Batch_Model/b/concat:0' shape=(5, 10000) dtype=float32>]

>>> tf.hessians(self.full_loss, [self.a, self.b])
[<tf.Tensor 'Reshape_1:0' shape=(5, 10000, 5, 10000) dtype=float32>,
 <tf.Tensor 'Reshape_3:0' shape=(5, 10000, 5, 10000) dtype=float32>]

>>> [tf.diag_part(t) for t in tf.hessians(self.full_loss, [self.a, self.b])]
[<tf.Tensor 'DiagPart_3:0' shape=(5, 10000) dtype=float32>,
 <tf.Tensor 'DiagPart_4:0' shape=(5, 10000) dtype=float32>]

However, this calculation seems to run infinitely:
The full hessian matrices are huge, but since I only take the diagonal elements, they should never be calculated explicitly.

I can calculate the diagonal by hand (gradient(gradient(loss, [a,b]), [a,b])), but I always expected tensorflow to optimize such operations implicitely...
Also, this trick does not work if I'd need other parts of the Hessian matrix, e.g. if I need for each independent gene the parm x parm-shaped hessian:
TF does not allow to differentiate only slices of a and b (e.g. tf.hessians(loss, [a[:, 0], b[:,0]]))

.
The problem
Tensorflow seems to explicitly calculate the full hessian matrix
What I'd expect
Fast calculation since I only request the diagonal

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.9.0
Python version: 3.6.5
Bazel version (if compiling from source): none
GCC/Compiler version (if compiling from source): none
CUDA/cuDNN version: none
GPU model and memory: none
Exact command to reproduce: none

Nagging Assignee @tatianashp: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 44 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 59 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 74 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 89 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 104 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 119 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @tatianashp: It has been 137 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@Hoeze,
Sorry for the delayed response. Please find the example code for Diagonal Hessian and let us know if this is what you are looking for. Thanks!


MM-12354 Add ability to remove profile image

Summary
Add ability to remove profile image
Ticket Link
https://mattermost.atlassian.net/browse/MM-12354
Checklist

[ ] Added or updated unit tests (required for all new features)
[x] Has UI changes
[x] Includes text changes and localization file updates

Device Information
This PR was tested on: iPhone 6 Simulator, iOS 12.1
Screenshots

@bradjcoughlin any progress on this? If we don't merge this by tomorrow it will need to wait until the next feature release which is in January

Not at all a problem. It's totally fine to just release it a bit later

I'm going to close this and submit and new PR if that's ok.


Get back resumed property in ARTChannelStateChangeParams along with the removed test (for RTL2f)

It was introduced as part of no-connection-serial PR. But was erroneously removed during review process.
It was used in the test which was removed since the claimed spec (RTL2f) is vague on this ("A test should exist to ensure that resumed is always false when a channel first becomes ATTACHED, it is true when the channel is ATTACHED following a successful connection recovery, and is false when the channel is ATTACHED following a failed connection recovery"), and the test wasn't testing connection recovery mentioned. I've created an issue in the specs repo for this.
┆Issue is synchronized with this Jira Task by Unito

Related issue https://github.com/ably/ably-cocoa/issues/1812


Improve documentation of Optional<@NonNull E>

In the documentation an example shows this method
Optional<@NonNull E> maybeFirst();

The explanation says:

An Optional object can hold only non-null values

This is not necessarily true, because Optional.empty() or Optional.ofNullable(null) both return an Optional that holds a null value.

No, they return an empty optional. A non-empty optional (one that holds a value) can only hold a non-null value.

Yeah, if you think of Optional.empty() as the more fundamental operation, with ofNullable as just a shortcut that uses empty() when appropriate, then that is more in line with the language used by the documentation of Optional.
It does turn out to be true that an empty Optional is implemented (well, assuming we're talking about the JDK one and not Guava's :)) as an object with a possibly null value field. But that is more of a performance optimization in the implementation than it is a fact about the Optional API.
Even beyond that, though, there's a more general principle: There aren't "two kinds" of Optional instances in quite the same way that there are "two kinds" of List instances.
I suspect that different approaches to explaining the different facets of this will work better for different people. What we'll ultimately want is probably to compile them all together, clean them up, promote them out of the wiki, and then link to them from the much shorter text that you're referencing.

This is not necessarily true, because Optional.empty() or Optional.ofNullable(null) both return an Optional that holds a null value.

That is an internal detail and the API does not say that. That is one thing I like that checker stresses that I think maybe should be added to the JSpecify doc as well:
Library annotations should reflect the specification, not the implementation

No, they return an empty optional. A non-empty optional (one that holds a value) can only hold a non-null value.
For those interested this is why Optional does not fully adhere to the Monad laws.
Also Optional is not an ADT. That is ideally it would have been a sealed interface with two subclasses representing both states so you can pattern match on it. I believe Guava does this but not public and in theory there is possible performance gains by this as it avoids conditions/branching. That is I'm not sure if it holding null as empty is faster over what Guava does especially given there is only two subclasses (shiplev had some article I recall about this that I can't seem to google).

In theory we could address this by adding "(unless the value is absent)", but this doc is already a complex enough wall of text imho. There are a few misconceptions about Optional out there but I believe the text is okay as it is.


Data model add data to cope with unknown licenses

The data model shall be extended to cope with not yet evaluated licenses aka. unknown licensess

a solution to cope with this can be an associated class between License and Constraint named Assessment with member attribute status and possible values completed, inEvaluated, notEvaluated


OpenQueryStoreDashboard - SQL 2008 R2 - Cannot run Report

As Enrico had written in one of my last issues... "Please use SSMS 2016 or 2017"
I'd just installed SSMS 2016 (Details below) and fixed all upcoming errors (lower/upper cases of ColumnNames)... after that my server needs some seconds to display the following message.
Problem signature:
Problem Event Name:	APPCRASH
Application Name:	Ssms.exe
Application Version:	2015.130.16100.1
Application Timestamp:	583f1f23
Fault Module Name:	clr.dll
Fault Module Version:	4.6.1055.0
Fault Module Timestamp:	563c0f73
Exception Code:	c0000005
Exception Offset:	0000c2c1
OS Version:	6.1.76<IP_ADDRESS>.272.7
Locale ID:	1031
Additional Information 1:	b2ed
Additional Information 2:	b2ed12303fbccd9cddd7799604c15a15
Additional Information 3:	c27e
Additional Information 4:	c27eb1bcfd0ec5a7f395adc60f7c28da
Report with fixed columnnames => https://github.com/sql-aus-hh/OpenQueryStore/blob/dev/crashed_Report.rdl

This is interesting:-).
Can you download the latest report from GitHub by clicking on the file and then the "raw" button and copy/paste the text inside a new .rdl file locally on your machine?
I had some issues in the past with GitHub and XML documents and I want to make sure this isn't the case.
Thanks!

I'd started with the last raw version of the report to be sure to have the actual one... I'd followed the issues from chrisgraef (?)
So I don't think that that might be the problem...

Von: Enrico van de Laar<EMAIL_ADDRESS>Gesendet: Dienstag, 27. Juni 2017 16:43
An: OpenQueryStore/OpenQueryStore
Cc: SQL_aus_HH; Author
Betreff: Re: [OpenQueryStore/OpenQueryStore] OpenQueryStoreDashboard - SQL 2008 R2 - Cannot run Report (#23)
This is interesting:-).
Can you download the latest report from GitHub by clicking on the file and then the "raw" button and copy/paste the text inside a new .rdl file locally on your machine?
I had some issues in the past with GitHub and XML documents and I want to make sure this isn't the case.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/OpenQueryStore/OpenQueryStore/issues/23#issuecomment-311380557, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATfjETr5pXFTaacX4fmtAez7ftBSAozGks5sIRUZgaJpZM4OGtiJ.

Ok perfect thanks!
I'll  see if I can reproduce the issue.

@sql-aus-hh I would like to close this issue, because I think the latest release of OQS should show that the issue is no longer there. Can you test and let us know? We will close this in a week if we hear nothing back from you.

Hello William
Actually I'm on vacation and will be back in the office on 4th September... I'll download and install the newest report version and check it.
BR
Bjoern
Outlook for Androidhttps://aka.ms/ghei36 herunterladen

From: William Durkin<EMAIL_ADDRESS>Sent: Tuesday, August 29, 2017 12:31:45 PM
To: OpenQueryStore/OpenQueryStore
Cc: SQL_aus_HH; Mention
Subject: Re: [OpenQueryStore/OpenQueryStore] OpenQueryStoreDashboard - SQL 2008 R2 - Cannot run Report (#23)
@sql-aus-hhhttps://github.com/sql-aus-hh I would like to close this issue, because I think the latest release of OQS should show that the issue is no longer there. Can you test and let us know? We will close this in a week if we hear nothing back from you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OpenQueryStore/OpenQueryStore/issues/23#issuecomment-325623643, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATfjEdZ4lFieeX-EwhUWGaErwZRjVAHzks5sc-iRgaJpZM4OGtiJ.

Hi Bjoern,
Did you have time to check out of this problem still exists?

Closing this issue as general cleanup. If the issue persists, please contact us again


OSX can't update as non-admin user

When an update is available, Code tells me to restart to apply the update.  When I restart, Code is not updated and the "restart to update" message is displayed again. I suspect this may be due to the fact that I'm using a non-administrator account.  I haven't done anything to confirm that though.

@steelheaddigital Sorry for the long silence. Is this still a problem nowadays with the latest versions?

No problem, thanks for taking a look.  Yes, it's still an issue with the last upgrade I just did from 1.2.1 to 1.3.0.

Do you by any chance use another application with automatic updates, like Atom? Does it work for you there?

Yes, other auto updates seem to work.  I'm not using Atom, but Sublime Text auto update works. The difference seems to be that other apps display the popup asking for admin credentials to install the update. Code doesn't do that, so I'm guessing it probably can't write to the Applications directory since I'm using a non-admin account.

Oh. What if you move Code to a folder your user controls?

I can try that. I don't have my Mac with me right now, but I'll give it a shot later. That would at least let us know if it is indeed a permissions thing. Still, it would be nice to have it ask for Admin credentials when updating like other apps so that it can stay in the Applications directory.

I'm having the exact same problem and have for a while. I run as a non administrator account on my Mac and have VS Code in the Applications folder. I second the notion about asking for Admin credentials.

We should get this from Electron. electron/electron#6345 ?

Or Squirrel: Squirrel/Squirrel.Mac#157

I was having the same issue but happened to install macOS Sierra (10.12) last night and after doing so the update worked fine (still in /Applications).

I'm seeing this same behavior but I am signed in with an admin account.

still fails, example:  Im stuck with 1.7.0  says update, restart now but nothing happens i have to manyally download and install

+1, issue persists, Version 1.7.1, macOS Sierra 10.12.1, extensions update without issues, admin account, visual studio code located in user\applications. After clicking restart to update Visual Studio Code closes and doesn't restart or update

I began running into this bug as soon as I upgraded to macOS Sierra from OS X Yosemite.

Same Issue for me

A possible fix, as @farfromrefug found out in #7426, is to run:
xattr -dr com.apple.quarantine "/Applications/Visual Studio Code - Insiders.app"

Does this help anyone?

The xattr trick did not help. I also have had the same problem for many, many releases of code and for different mac os x versions incl. Sierra. It is the single most annoying problem with visual code. Really need fixing.

Happens to me now with VScode, and happened with Atom in the past.
The xattr thing didn't work for me though.

This continues to happen to me. I'm on MacOS 10.12.2, running as non-admin. I was stuck on VS Code 1.7.2 until I manually updated it to 1.8.1.

Same issue on macOS Sierra 10.12.2
I get this error every 2 seconds in system.log
Dec 28 14:23:45 Ivolution com.apple.xpc.launchd[1] (com.microsoft.VSCode.ShipIt): Service only ran for 0 seconds. Pushing respawn out by 2 seconds.
Dec 28 14:23:47 Ivolution com.apple.xpc.launchd[1] (com.microsoft.VSCode.ShipIt[7291]): Service could not initialize: 16C67: xpcproxy + 11765 [1475][286733C4-18D9-396D-B01B-A096BE5B1DC1]: 0xd

same issue on macOS Sierra 10.12.2
insiders asks to update every day -- need to manually download and copy into Applications each day to update.
Jan 17 11:09:05 xxxxxxx com.apple.xpc.launchd[1] (com.microsoft.VSCodeInsiders.ShipIt): Service only ran for 0 seconds. Pushing respawn out by 2 seconds. Jan 17 11:09:07 xxxxxxx com.apple.xpc.launchd[1] (com.microsoft.VSCodeInsiders.ShipIt[14413]): Service could not initialize: 16C67: xpcproxy + 11765 [1475][286733C4-18D9-396D-B01B-A096BE5B1DC1]: 0xd

Manually install the lateset version of insiders.  After that it should
auto update going forward.  I'm not sure which issue fixed this problems
but it has been working ever since the last couple updates
On Tue, Jan 17, 2017, 9:11 AM Brett Kirby<EMAIL_ADDRESS>wrote:

same issue on macOS Sierra 10.12.2
insiders asks to update every day -- need to manually download and copy
into Applications each day to update.
Jan 17 11:09:05 xxxxxxx com.apple.xpc.launchd[1]
(com.microsoft.VSCodeInsiders.ShipIt): Service only ran for 0 seconds.
Pushing respawn out by 2 seconds. Jan 17 11:09:07 xxxxxxx
com.apple.xpc.launchd[1] (com.microsoft.VSCodeInsiders.ShipIt[14413]):
Service could not initialize: 16C67: xpcproxy + 11765
[1475][286733C4-18D9-396D-B01B-A096BE5B1DC1]: 0xd
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/3520#issuecomment-273214428,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFFsSYb-Vpuxqv9lMYfyjslPW-rvMUyvks5rTOgUgaJpZM4HkVru
.

@rwatts3 confirmed that this does not work. Tried pressing update button today -- same result as before.

I am experiencing the same issue as @brettKgm with version 1.8.0 on OSX 10.12.2.

Definitely #7426

This issue is persistent on my Mac as well.
VSCode 1.9.1
OSX 10.12.3

Guys, read my comment on #7426

same with me

I managed to get ride of this.
I noticed that I used to run code as admin.
So I normally started vs code and updated. After that, everything went well for me.
Here is my context:
OSX El Capitan
Version 10.11.6
Old VS Code version: 10.11
VS Code version after successful update : 10.12
Hope this will help someone.


Universal wheel generation

Setting the universal option for bdist_wheel in setup.py, so a universal wheel will be built.

/morph test


First Element on the '@' is not being selected

I must say this is a good project, here is how to reproduce the issue

Type '@'
When the list appears, move the mouse curser to the second element (Peter john)
Move the curser to the 1st element (Chandrasekhar Ambula V)
Click the 1st element

@sarger  Thank you for reporting the issue, i will fix it this weekend

@sarger yes I reproduce the same issue. @avcs06 thank you for this great lib. Any update to know when this issue will be fixed?

Fixed the issue in v1.2.0-beta
https://github.com/avcs06/AutoSuggest/commit/bf604ba5efd8f4ae447b8ff89cfe5721cc0369a9


Reconsider MapVisitor::missing_field

Out of all the Serde deserializers on GitHub, there are exactly four distinct behaviors for missing_field:

Unconditionally an error
For options treat it as None, otherwise error
Treat it as unit
Whatever serde_xml is doing

Ideally I would like to standardize on one of these (my preference is None/error) and remove the ability for deserializers to modify the behavior. This would improve consistency and predictability across the ecosystem.
@oli-obk can you explain the various cases that serde_xml needs to handle in missing_field and whether you can think of any alternative ways to accomplish this?

mwhaha, serde_xml should not be a benchmark of good Deserializer design. It's what you'd get if you wrote a test-suite and threw a neural network against it that gets encouraged to pass more tests.
What we do at the location you linked is to rename a field to $value, and in case a tag like <tag>content</tag> comes along, you end up triggering missing_field for the $value field and extract "content" to be the value of that field. One would think that a string-newtype or similar could also suffice, but we can also have <tag attr="foo">content</tag>, where we need a field named attr.
Mapping xml schemata to Rust types is a nightmare, the experiment is a failure in my opinion. It's not serde's fault, it's just that xml schemata have many weird things that basically only work with object oriented systems with inheritance.

What would serde_xml do if we take away missing_field?

Probably match on an error

And use a seed

Let's do that then. I think this would be a net benefit for every other use case except serde_xml. We replace the three different behaviors with one consistent approach and no longer need this awkwardly placed API. What do you think?
We would still need to settle which behavior to use:

For options treat missing field as None, otherwise error
Treat missing field as unit

In practice this matters most for collection types like Vec<T>. The first one makes it an error, the second one makes it empty vec. I prefer the first approach and if you want the second behavior you can either put #[serde(default)] on the vec field or use Option<Vec<T>>.
In theory we could also unconditionally make missing field an error, and require #[serde(default)] on Option<T> fields to make it None. That seems excessive to me. Option is already a special case in the Serializer and Deserializer traits and it seems pretty intuitive that if your field is optional and it isn't there then it is None.

In theory we could also unconditionally make missing field an error, and require #[serde(default)] on Option fields to make it None. That seems excessive to me. Option is already a special case in the Serializer and Deserializer traits and it seems pretty intuitive that if your field is optional and it isn't there then it is None.

I agree, let's make Option special and require #[serde(default)] for everything else. If we notice certain types getting excessive use of #[serde(default)], we can revisit this.


Add support for sound pitches

As it stands now, with the new sound feature, we can provide an array of sounds from which scribble will pick one. I think another feature where you could also provide a pitch range for the played sound would be great.
Something like audio_sound_pitch(sound_index, random_range(range_lower, range_upper)) should be pretty simple and could be incorporated great into scribble_autotype_set_sound, e.g. scribble_autotype_set_sound(element, sound_array, overlap, pitch_array) or even scribble_autotype_set_sound(element, sound_array, overlap, pitch_lower, pitch_upper). Or maybe even a pitch_offset which would generate a range +- the offset, e.g. [0.8, 1.2] from offset 0.2.
I can provide a PR in the following days if you are too busy to implement that. Thanks!

Thanks for the suggestion, I'll definitely put this in for the next version!
I think I'll go for an lower/upper bound for pitches as that feels most transparent.

Planned for v6

In v6


Bug: createContext only works in Client Components. Add the "use  client" directive at the top of the file to use it

Describe the bug and the steps to reproduce it
Developers are reporting the following issue:
node_modules/[@coinbase](https://t.me/coinbase)/onchainkit/lib/OnchainKitProvider.js (7:45) @ createContext
 ⨯ createContext only works in Client Components. Add the "use
client" directive at the top of the file to use it.

When attempting to add a new page with Frame metadata (i.e. yourappname.vercel.app/newPage) outside of the original root page, as described in this tutorial:
https://docs.base.org/tutorials/farcaster-frames-transactions#the-first-frame-and-page
What's the expected behavior?
No error is thrown.
What version of the libraries are you using?

"@coinbase/onchainkit": "0.13.0"

@taycaldwell can you share details on what code they used? Also this tutorial https://docs.base.org/tutorials/farcaster-frames-transactions/#the-first-frame-and-page seems outdated.
Like
import { getFrameMetadata } from '@coinbase/onchainkit';

is not the right import anymore, as they should import from @coinbase/onchainkit/frame.
top level is reserved only for the OnchainKitProvider.
@taycaldwell can you work in updating the docs?

In version 0.14.1 we are going to remove getFrameMetadata from the top level import, so there is no more confusion going forward.
@taycaldwell @briandoyle81CB but we still need to update the docs in Base.org


C++0x with GCC 4.6 is not supported

This ticket is just to record the fact that C++0x mode might not ensure successful compilation due to use of the #include <codecvt>.
For instance, on Ubuntu 12.04 with default GCC 4.6 the compilation will fail:
cmake ..
-- The C compiler identification is GNU
-- The CXX compiler identification is GNU
-- Check for working C compiler: /usr/bin/gcc
-- Check for working C compiler: /usr/bin/gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++
-- Check for working CXX compiler: /usr/bin/g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Performing Test COMPILER_SUPPORTS_CXX14
-- Performing Test COMPILER_SUPPORTS_CXX14 - Failed
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Failed
-- Performing Test COMPILER_SUPPORTS_CXX0X
-- Performing Test COMPILER_SUPPORTS_CXX0X - Success
-- ODBC Version Override: Turned off
-- Unicode support: Turned off
-- Boost string convert: Turned off
-- Handle SQL_NO_DATA bug: Turned off
-- Target install: Enabled
-- Boost version: 1.46.1
-- Found the following Boost libraries:
--   unit_test_framework
-- Target test: Enabled
-- Configuring done
-- Generating done
-- Build files have been written to: /home/mloskot/nanodbc/build
$ make
Scanning dependencies of target nanodbc
[100%] Building CXX object CMakeFiles/nanodbc.dir/src/nanodbc.cpp.o
/home/mloskot/nanodbc/src/nanodbc.cpp:23:23: fatal error: codecvt: No such file or directory
compilation terminated.
make[2]: *** [CMakeFiles/nanodbc.dir/src/nanodbc.cpp.o] Error 1
make[1]: *** [CMakeFiles/nanodbc.dir/all] Error 2
make: *** [all] Error 2

Yep, this was a conscious decision on my part as I didn't need it and didn't want to have to support it. Good to have the issue documented in multiple places.

Sure, understood. I think we can close it then.


Not working

Could you please explain more about the issue you're experiencing

Could you please explain more about the issue you're experiencing

All responses are "[ERROR] No Cloudflare challenge detected."

This issue was recently fixed, therefore you can just clone the repository again to fix this issue.

Ok, just cloned the latest repository. Now I get:
[ERROR] Failed to retrieve the Cloudflare clearance cookie.
Tried 3 sites that give cloudflare challenges on first visit.

This program currently will not be able to solve turnstile challenges due to an issue with Playwright. For more information, see https://github.com/microsoft/playwright/issues/21780. As a temporary solution, pass the -d flag and solve the challenge manually.

This program currently will not be able to solve turnstile challenges due to an issue with Playwright. For more information, see microsoft/playwright#21780. As a temporary solution, pass the -d flag and solve the challenge manually.

I passed it with the -d flag and it didn't lead me to a turnstile challenge but just to a click to "Verifiy you are human" type verification. After clicking manually on the newly opened browser, the CLI responded with the cookie.
Running the command without -d right after failed again.

Should be fixed in the latest commit.

Should be fixed in the latest commit.

Cloned the latest commit and ran "python main.py -v https://nowsecure.nl":
[22:01:55] [INFO] Launching headless browser...
[22:01:56] [INFO] Going to https://nowsecure.nl...
[22:01:57] [INFO] Solving Cloudflare challenge [Managed]...
[22:02:27] [ERROR] Failed to retrieve the Cloudflare clearance cookie.

This program currently will not be able to solve turnstile challenges due to an issue with Playwright. For more information, see https://github.com/microsoft/playwright/issues/21780. As a temporary solution, pass the -d flag and solve the challenge manually.

^

This program currently will not be able to solve turnstile challenges due to an issue with Playwright. For more information, see microsoft/playwright#21780. As a temporary solution, pass the -d flag and solve the challenge manually.
I passed it with the -d flag and it didn't lead me to a turnstile challenge but just to a click to "Verifiy you are human" type verification.

^

Yes, I just fixed that. What I cannot fix is the inability to solve turnstile challenges.

on Firefox 115.0 (playwright build v1419),  the frame url return  is empty

`def _get_turnstile_frame(self) -> Optional[Frame]:
"""
Get the Cloudflare turnstile frame.
    Returns
    -------
    Optional[Frame]
        The Cloudflare turnstile frame.
    """
    for frame in self.page.frames:
        logging.info(frame.url)
        if (
            re.match(
                "https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/[bg]/turnstile",
                frame.url,
            )
            is not None
        ):
            return frame

    return None`

i tried printing out the frame.url but it always loads the site im accessing and not "https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/[bg]/turnstile" regexp.

i keep getting [05:42:05] [ERROR] Failed to retrieve the Cloudflare clearance cookie.
`def _get_turnstile_frame(self) -> Optional[Frame]: """ Get the Cloudflare turnstile frame.
    Returns
    -------
    Optional[Frame]
        The Cloudflare turnstile frame.
    """
    for frame in self.page.frames:
        logging.info(frame.url)
        if (
            re.match(
                "https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/[bg]/turnstile",
                frame.url,
            )
            is not None
        ):
            return frame

    return None`

so i tried printing out the frame.url but it always loads the url of the site im trying to access and not the challege urls "https://challenges.cloudflare.com/cdn-cgi/challenge-platform/h/[bg]/turnstile"

https://github.com/microsoft/playwright/issues/21780


Update return type for call method example pipeline for text_classification

Currently doc string types for text_classification pipeline in docker_image/commmon have
A :obj:`list`:. The object returned should be a list of one list like [[{"label": 0.9939950108528137}]] containing:

It should be
A :obj:`list`:. The object returned should be a list of one list like [[{"label": "blah", "score": 0.9939950108528137}]] containing:

see https://github.com/huggingface/api-inference-community/pull/276#discussion_r1203001474

Indeed. Would you like to open a PR for this?

Indeed. Would you like to open a PR for this?

will do :)