[OoB 5.15] Cannot clone the repository using the given command

This issue is related to Mbed OS 5.15 OoB campaign.
When I tried importing project with this command given in README
$ git clone git@github.com:armmbed/mbed-os-example-blinky

I got this error
$ git clone git@github.com:ARMmbed/mbed-os-example-blinky
Cloning into 'mbed-os-example-blinky'...
Enter passphrase for key '/Users/osakoi01/.ssh/id_rsa':
<EMAIL_ADDRESS>Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

This happens both macOS Catalina and Windows 10.
(macOS)
$ git --version
git version 2.15.1

(Windows)
> git --version
git version 2.18.0.windows.1

Do I need any setting before clone the repository?
I can import the same repository with this command given in README
$ mbed import mbed-os-example-blinky
[mbed] Working path "/Users/osakoi01/mbed/20191204_MbedOS5.15_OoB" (directory)
[mbed] Importing program "mbed-os-example-blinky" from "https://github.com/ARMmbed/mbed-os-example-blinky" at latest revision in the current branch
[mbed] Adding library "mbed-os" from "https://github.com/ARMmbed/mbed-os" at rev #cf4f12a123c0
[mbed] Auto-installing missing Python modules (pywin32, wmi)..

Internal Jira reference: https://jira.arm.com/browse/IOTCORE-1455

@coisme One is using ssh another one https. For ssh (the first case), you don't have ssh agent running (I assume).
We should check other examples, github recommends using https (a user can always use ssh, easy to switch).

@coisme https://help.github.com/en/github/authenticating-to-github/connecting-to-github-with-ssh this should be of help

Hi @0xc0170 and @adbridge Thank you for your information. I followed Generating a new SSH key and adding it to the ssh-agent in the above link. Then the command ran successfully.
$ git clone git@github.com:armmbed/mbed-os-example-blinky
Cloning into 'mbed-os-example-blinky'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
remote: Enumerating objects: 10, done.
remote: Counting objects: 100% (10/10), done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 716 (delta 1), reused 5 (delta 1), pack-reused 706
Receiving objects: 100% (716/716), 292.50 KiB | 860.00 KiB/s, done.
Resolving deltas: 100% (214/214), done.

If we keep the first command, it is better to mention this SSH stuff.

@coisme Glad that helped. As this is pretty much Git 101 I don't think it's something we should necessarily be adding to our READMEs .....I will close this now then.


QuickStart directions

I'm game to help with this project - can we get some basic setup instructions in the readme?

My apologies - the mobile github view cutoff most of the readme but now I see the info I requested is already there.


We are getting Race and age but incorrect gender from the code

I have done analysis for 12 year old baby and I get 19 years and gender male which is worng.
Can you fix this issue?

deepface can predict ages ±4.6 years, and it can predict gender 97% accuracy, 96.29% precision, 95.05% recall. This is not wrong because this level error is acceptable for machine learning studies.
Tutorial: https://sefiks.com/2019/02/13/apparent-age-and-gender-prediction-in-keras/


store .ethslurp files in all lower case

grabABI for example does not, which makes it confusing if the file exists or not.

Moved to https://github.com/Great-Hill-Corporation/quickBlocks/issues/60


Fix Strapi admin panel

:tada: This PR is included in version 1.5.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Tag command name from the subcommand

my question is...
At using {{.Name}} at the 'CustomHelpTemplate' field of a subcommand, I get the subcommand name, but I also need the command name.
Which is the tag name to get the command name?
And the program name?

@tredoe I don't know the answer to your question offhand, but https://github.com/urfave/cli/issues/783 is related here 👀

While it may not be exactly what you need, {{ .HelpName }} includes the full "lineage" of the current subcommand, e.g.:

source code in here
package main

import (
        "log"
        "os"

        "github.com/urfave/cli/v2"
)

const (
        cmdHelpTmpl = `Name: {{ printf "%q" .Name }}
HelpName: {{ printf "%q" .HelpName }}
`
)

func main() {
        app := &cli.App{
                Commands: []*cli.Command{
                        {
                                Name: "woof",
                                Action: func(c *cli.Context) error {
                                        log.Println("woof")
                                        return nil
                                },
                                Subcommands: []*cli.Command{
                                        {
                                                Name: "arf",
                                                Action: func(c *cli.Context) error {
                                                        log.Printf("woof arf")
                                                        return nil
                                                },
                                                CustomHelpTemplate: cmdHelpTmpl,
                                        },
                                },
                        },
                },
        }

        if err := app.Run(os.Args); err != nil {
                log.Fatal(err)
        }
}

$ go run .local/tmp/1064.go woof arf --help
Name: "arf"
HelpName: "1064 woof arf"


Athlinks uses different controls for selecting races

Fix Athlinks to work again.
Athlinks used to use <select> to choose the year and race. Now it uses a <span> within a <div>. As such, events that we used to be able to scrape are no longer working.

FWIW, clicking the button that's in the span brings up a modal dialog that has an element that needs to be clicked to then get a <ul> containing <li>s that need to be clicked.
I will take a quick stab at getting this to go, but it's not a great use of my time. If I can't make it go, I may just make some way to bypass this selection and use hard-coded values to get to the landing page based on the other options, since I sort of need to do that for Doggie Dash (#13) anyway and those are the results that I'd like to scrape today.


Dark Mode problem in Manjaro

Hi Thanks for this amazing port
Describe the bug
When I switch to Dark mode (or Black or sepia) icon's & emoji's are unaffected
Screenshots

Technical Info (please complete the following information)

OS: Linux version 5.6.15-1-MANJARO (builder@601a6c674820) (gcc version 10.1.0 (GCC))
Ao Version: 21 May 2019

Thanks in advance

Today I discovered this wonderful application and faced a similar bug (Fedora 31, KDE). It seems that this repository is abandoned and I decided to create my fork with fixes. Please read my note in the readme file.
Hope this helps you. https://github.com/Sonny812/ao

Thanks for your comment
Unfortunately I couldn't follow your guide to install your fork so decided to get along the problem
Thanks again for your contribution

I can't install it either. And I'm also wondering why I can't find an issues tab in the fork.

I can't install it either. And I'm also wondering why I can't find an issues tab in the fork.

This is because for some reason Sonny didn't make any releases and he did all the work I already did in my own fork (by merging the pull requests) but then broke the build in some way.
The most updated version of this app is here. I can't guarantee that it's going to be updated massively because I'm not much of fan of electron and it still requires other people to actively submit commits and create issues. I've considered rebranding the entire app and re-releasing it in the hopes it'll fuel further development but I haven't had time because I have my own projects.
Note that my version does not replace the dark mode with the 'bisque' mode another user made. I tried that myself but I hated it. 🙃

@pythonInRelay I think I managed to install yours in the past but I also can't find an issues tab, I'm curious what's the reason for this.

@pythonInRelay I think I managed to install yours in the past but I also can't find an issues tab, I'm curious what's the reason for this.

Apologies. I accidentally disabled them globally and forgot to change it back. You should now be able to open issues on my repo.


Add syntax statement for proto file

Motivation
In my environment, protoc warns to declare syntax  as below.
$ protoc --go_out=src/pulsar/proto PulsarApi.proto
[libprotobuf WARNING google/protobuf/compiler/parser.cc:546] No syntax specified for the proto file: PulsarApi.proto. Please use 'syntax = "proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to proto2 syntax.)

My protoc version is here.
$ protoc --version
libprotoc 3.3.0

According the Protocol Buffers document, syntax statement is at top of proto file.
proto = syntax { import | package | option | topLevelDef | emptyStatement }
topLevelDef = message | enum | extend | service

https://developers.google.com/protocol-buffers/docs/reference/proto2-spec#proto_file

Modifications
Add syntax statement into proto file.
syntax = "proto2";

Result
protoc doesn't warn.

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:


⚠ St. Lawrence Global Observatory CKAN has degraded performance

In eaad36f, St. Lawrence Global Observatory CKAN (https://catalogue.ogsl.ca/en/) experienced degraded performance:

HTTP code: 200
Response time: 5899 ms

Resolved: St. Lawrence Global Observatory CKAN performance has improved in 00d7258 after 15 minutes.


Updated and renamed upgrading.rst to upgrading.md

Updated and renamed upgrading.rst to upgrading.md. Please review and let me know of any further changes to be done.

Need guidance in hiding (compatible_django_python_versions)= from the file.

Replaced by https://github.com/wagtail/wagtail/pull/8769/


BIP-0044 compatibility

Forgive my ignorance.
I'm using the BitWasp library to work with BIP0032 HD wallets and it's doing great. I want to work with BIP0044 wallets.
They're basically BIP0032 wallets but with deeper hierarchy levels in order to standardize what the different hierarchies mean (coin type, account, account, chain, and address).
Any anticipated problems using BitWasp with this before I dive into implementation? Are there any functions or accessible objects that would make working with BIP0044 easier?
If it does work, you might want to add BIP0044 to the Implemented BIPs list.

It's possible just by using HierarchicalKey::derivePath() - you can pass "m / purpose' / coin_type' / account' / change / address_index" (without the spaces) to the root key.
You can derive step-by-step with derivePath and deriveChild, meaning for example you can keep the $coinType instance around if you need to create several accounts.
$master = HierarchicalKeyFactory::create();
$btc = $master->derivePath("$purpose'/$coinType'");
// Acc 1, hardened derivation using derivePath()
$acc1 = $btc->derivePath("1'");

// Acc 2, hardened derivation using deriveChild()
$sequence = new HierarchicalKeySequence();
$acc2 = $btc->deriveChild($sequence->getHardened(2));

There's nothing to make BIP44 easier specifically, but you'll probably want to persist public keys where possible HierarchicalKey::toExtendedKey([$network = bitcoin]), so HierarchicalKeyFactory::fromExtended($string) will also be useful.
If you're up to it, you might be interested in https://github.com/Bit-Wasp/secp256k1-php - an extension that makes this stuff lightning fast, but until upstream libsecp256k1 makes a release, it's from source only. Any upstream breaks

Yea, I noticed that it's a bit slow, but that's OK for now. I'm using Laravel so it's easy for me to toss the key generation into a queue for processing to prevent any delays to the front-end. I'll look into using the secp256k1-php extension to speed it up.
My sample code works well. Thank you.

Aye - previous versions of phpecc were a bit faster, but that lead to a (timing) side-channel attack. Fixing it made things slower, but worth it IMO


Feat: Edited ADF algorithm to include CapyMoa Drift Detection Classes in its parameters

We can create more PRs to have this functionality applied to other learners

Thanks @DwayneAcosta , I just approved the checks, let's see how it goes

there is an issue with the commit convention, but we can solve that


Add caching response headers?

Should a cache-control header be included on range request responses?

Took a while but it's done.


sysctl disable

The chart currently requires privilege to deploy an elasticsearch. There is no way to disable the sysctl init container even if your hosts have already been preconfigured for it.

Upping this issue -- I am trying to deploy the chart but I am unable to run the containers as privileged. It would have been helpful to me if there was an option to not run the elasticsearch containers as privileged and as a nonRoot user.

@kfox1111 , @Sparkdaddy  yes, currently privileged permission is needed for initcontainers. https://github.com/opendistro-for-elasticsearch/opendistro-build/blob/master/helm/opendistro-es/templates/elasticsearch/es-data-sts.yaml#L65  you can try to disable it to see if it works for you. pls share the result to us

Yes, but we tried disabling the entire block:
      - name: init-sysctl
        image: {{ .Values.elasticsearch.initContainer.image }}:{{ .Values.elasticsearch.initContainer.imageTag }}
        command:
        - sysctl
        - -w
        - vm.max_map_count={{ .Values.elasticsearch.maxMapCount }}
        securityContext:
          privileged: true

Could be updated to be wrapped in something like:
{{ if .Values.elasticsearch.sysctl.enabled }}
{{ end }}

@kfox1111 yes, you are right. we put this into our backlog. And we will appreciate a lot if you could contribute it back as a PR, thanks

Done.
https://github.com/opendistro-for-elasticsearch/opendistro-build/pull/193

Hi @kfox1111, thanks for the contribution.
I have made some comments when reviewing the #193 PR.
Please take a look and resolve them. Thanks.

This issue is now closed by merging PR #193. Thanks.


[python3] Bump to 3.10.7

Bump the python3 port to the latest revision of 3.10.x as a precursor to upgrading to 3.11.0. This front-loads some (but not all) of the tweaks that will need to be made to the patches for 3.11.0.

What does your PR fix?

Updates python to 3.10.7.
Some patch files were diffs masquerading as patch files. Change those to actual patch files so they can be more easily applied onto the cpython repo.
Fixed a compile breakage in the Windows 7 patch introduced somewhere between 3.10.5 and 3.10.7.
Tweaked some of the static building patches to prevent conditional patch content appearing in unconditional context lines. This will be more relevant in 3.11.0, but I'm front loading it now.

Which triplets are supported/not supported? Have you updated the CI baseline?
No change

Does your PR follow the maintainer guide?

Indeed

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Everything is green, so we're ready for review.

@Hoikas, I have reviewed this pr, it is very good, I saw that this pr has a big change to the upstream code, I think it is necessary to let the upstream know. do you think so?

Feature deprecated-win7-support tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

@Hoikas, I have reviewed this pr, it is very good, I saw that this pr has a big change to the upstream code, I think it is necessary to let the upstream know. do you think so?

All of these patches are specific for building Python in the vcpkg environment or in ways that are not particularly supported upstream (eg deprecated-win7-support), so I don't think so.


[Bug] On Mobile Browser the Camera Event not working properly, after capturing the image app will restart itself.

Describe the bug
When we open the camera and taking the image from any position i.e posting an image from the post or setting profile image at profile or setting banner image at the banner or opening video recording camera from the post, the app will restart itself.
To Reproduce
Steps to reproduce the behavior:

Go home
Click on the post button
Select the camera button/video camera post
Open live camera to take pictures/video recorder
Choose the picture to submit/submit the video
The app will restart itself

Expected behavior
App remains the stable not restart itself and the picture or video will post on the feeds
Desktop (please complete the following information):

OS: [MacOs Mojave 10.14.5]
Browser [e.g. chrome]
Version 75.0.3770.100 (Official Build) (64-bit)

Smartphone (please complete the following information):

Device: [android Nokia -2]
OS: [Android 7.1]
Browser [Chrome]
Version [e.g. 75.0.3770.101]

Additional context
Add any other context about the problem here.

@Abhiranjanchaurasia I have not worked on mobile support seriously. Do you think is it necessary to support mobile app in v0.7.0? or I create a new milestone and for this v0.7.0 we just focus on stability of features on desktop browsers?
@kapilip What is your idea?


Issue 9 -- OAuth login

This PR is in a request-for-comments state. It implements Google OAuth handshaking for a properly credentialed application (not checked in here), and attempts to document how others can do the same.
Any / all feedback welcome.

This change is

Coverage remained the same at 90.909% when pulling f793110b8026bc2c5c2f3813f223b72a31dcf3d4 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage remained the same at 90.909% when pulling f793110b8026bc2c5c2f3813f223b72a31dcf3d4 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage decreased (-0.4%) to 90.558% when pulling 42ae35147d266cfcaa7945f98c81d017d9c59010 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage decreased (-0.4%) to 90.558% when pulling 42ae35147d266cfcaa7945f98c81d017d9c59010 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage decreased (-0.4%) to 90.558% when pulling cadee353dd8819aa73771675dac88a5a954480a5 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage increased (+0.08%) to 90.987% when pulling 01d8dfa0f240ba2c976b2f70b309598953c64e44 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage increased (+0.08%) to 90.987% when pulling 01d8dfa0f240ba2c976b2f70b309598953c64e44 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

Coverage increased (+0.08%) to 90.987% when pulling 01d8dfa0f240ba2c976b2f70b309598953c64e44 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

alrighty, I think this is ready for a final pass:

implements two OAuth handlers (Google, Spotify)
introduces conftest.py for reusable pytest fixtures
consolidates configs as YAML

paging @bmcfee 😉

alrighty, I think this is ready for a final pass:

Looks like there are still a bunch of outstanding comments in my previous review?

sorry, all comments have been addressed on recent commits, updated each with some kind of ack., lemme know how it currently looks, and I'll take a look at the request.args declaration.

weird, looks stale to me, but I'm on my phone... will investigate further
shortly.
On Mon, Jan 16, 2017 at 11:21 AM Brian McFee<EMAIL_ADDRESS>wrote:

@bmcfee commented on this pull request.

In backend_server/main.py https://github.com/cosmir/open-mic/pull/42:

CORS(app)

Set the cloud backend
CLOUD_CONFIG = os.path.join(os.path.dirname(file), '.config.json')
app.config['cloud'] = json.load(open(CLOUD_CONFIG))
+OAUTH_CONFIG = os.path.join(os.path.dirname(file), 'configs', 'oauth.yaml')
+app.config['oauth'] = yaml.load(open(OAUTH_CONFIG))
what about context managers on the file opens?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/cosmir/open-mic/pull/42, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4iq_jIblTnY-QUW6-Rosvhhmn7aGXTks5rS5khgaJpZM4LaGUk
.

weird, looks stale to me, but I'm on my phone... will investigate further
shortly.

Annoyingly, it gives the latest version if i click on the "view changes" link instead of the "review" link.  I added some comments.

thx / sorry for the troubles, willfix tonight

Coverage decreased (-1.4%) to 89.54% when pulling 48e5f00bd1e9aeef624e1947fdf59a1cbfa5936f on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

@bmcfee can haz another look? also, I think we shouldn't worry about the drop in coverage ... OAuth adds a bunch of machinery that can only talk to real web services, and I'm not sure there's a meaningful way to test them (or that it's worth the time right now).

Coverage decreased (-1.4%) to 89.54% when pulling 52dbb46166f33ecb5b4a0f90da522b80a87cac15 on ejh_20161229_iss9_oauth_login into b74a454f37bae9e876ef7750074a97e3e82da607 on master.

think we shouldn't worry about the drop in coverage ... OAuth adds a bunch of machinery that can only talk to real web services, and I'm not sure there's a meaningful way to test them (or that it's worth the time right now).

This is what mocking is for.  This thread has some notes on how to do it.
Otherwise, I'll try to look at this one tomorrow.

merging now, adding issues for mocking (#46) and refactoring (#47)


[DOC] - Expand backup section to include more info

Preliminary Checks

[X] This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions

Summary
https://nebari-docs.netlify.app/docs/how-tos/manual-backup/ is not complete right now.  We could improve it by adding a few sections.

Backing up the conda store nfs drive will not restore the conda database.  Give info on how to backup and restore the conda store db.
Existing Argo Workflows history and CronWorkflows will be deleted.  You'd need to manually copy CronWorkflows spec down and re-apply.
Custom Grafana dashboards would need to be backed up manually as well.  I'm sure Grafana has some docs on how to do so.
I'm not sure if copying the jupyterhub database would preserve the CDS Dashboards configuration or not.  It also might be important in what order we restore things.  E.g. You might need to restore the keycloak users, then the jupyterhub database, but not sure right now.
I'm not sure if backing up the jupyterhub database is still needed since user info is in keycloak.  CDS dashboards info is the only reason I can think of, and I'm not sure if that would work anyway.
Any custom nebari deployment modifications may require manual steps to re-apply as well

using custom cert, etc.

Consider adding k8s job to file system backup.  Using a k8s job is useful over a simple pod when the file system is large and copying all the data takes a long time. e.g.
kind: Job
apiVersion: batch/v1
metadata:
  name: backup
  namespace: dev
spec:
  template:
    spec:
      volumes:
        - name: backup-volume
          persistentVolumeClaim:
            claimName: "jupyterhub-dev-share"
      containers:
        - name: debugger
          image: ubuntu
          command: ["/bin/bash", "-c", "cd /data && tar -cvpzf 2024-03-08-shared.tar.gz shared && echo 'Backup complete' > backup.txt"]
          volumeMounts:
            - mountPath: "/data"
              name: backup-volume
      restartPolicy: OnFailure

and for restore
kind: Job
apiVersion: batch/v1
metadata:
  name: restore
  namespace: dev
spec:
  template:
    spec:
      volumes:
        - name: backup-volume
          persistentVolumeClaim:
            claimName: "jupyterhub-dev-share"
      containers:
        - name: debugger
          image: ubuntu
          command: ["/bin/bash", "-c", "cd /data && tar -xvpzf 2024-03-08-shared.tar.gz --skip-old-files && echo 'Restore complete' > restore2.txt"]
          volumeMounts:
            - mountPath: "/data"
              name: backup-volume
      restartPolicy: OnFailure


More details required

The page says:

You can submit the remaining options via a non-actionable HTML email, the Power Automate approval center, the Power Automate mobile application, or Teams.

I need to know how to do these and there is no link for them.

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

ID: 75b2c12c-7262-de3d-eb95-410fb6a33df6
Version Independent ID: b316d8da-19ac-6b00-7675-2b9d03d33377
Content: Create approval flows with custom responses - Power Automate
Content Source: articles/create-approval-response-options.md
Service: power-automate
Sub-service: cloud-flow
GitHub Login: @natalie-pienkowska
Microsoft Alias: napienko

@divadnagrom - Thanks for your feedback. We are currently looking into this issue.

Per Natalie, reassign to Harysh.


Added a return type of AFHTTPRequestOperation for AmazonS3Manager methods

This fixes issue #72, allowing clients of the library to easily be able to cancel requests after they were submitted.

Thanks, @abbeycode. AFNetworking made that change at some point in the past, so this brings everything in line. I'll cut a new release now.


No module package available for installation

The releases page has tags for each stage of release but there isn't an installable module package for any of the releases for us to download and install into a website.

Install zips added for each of the existing tags v0.4.0, v0.5.0 and v0.6.0.


Backport/v1.0 2018 05 23

Folks, please review this PR. I saw a conflict on every backport except 4175 and 4107, and I had to figure out how to resolve them.
@aanm: I couldn't figure out how to backport pkg/ip: fix getNextIP for IPv4 (https://github.com/cilium/cilium/pull/4106). Feel free to do it and push to this branch.
@rlenglet: I couldn't figure out how to backport ipcache: Create copies of NPHDS cache resources when updating (https://github.com/cilium/cilium/pull/4167). Feel free to do it and push to this branch.

PR: 4209 -- Test: Fix issues with Ginkgo Kubernetes Job (@eloycoto) -- https://github.com/cilium/cilium/pull/4209
PR: 4203 -- docs: Attempt to use RTD version for GH URLs (@joestringer) -- https://github.com/cilium/cilium/pull/4203
PR: 4201 -- Fix minikube gsg with CNI flag (@aanm) -- https://github.com/cilium/cilium/pull/4201
PR: 4199 -- pkg/bpf: use pointer receiver for GetKeyPtr() (@aanm) -- https://github.com/cilium/cilium/pull/4199
PR: 4194 -- ipcache: Create copies of NPHDS cache resources when deleting (@rlenglet) -- https://github.com/cilium/cilium/pull/4194
PR: 4193 -- bugtool: Add '-a' option to netstat. (@jrajahalme) -- https://github.com/cilium/cilium/pull/4193
PR: 4175 -- K8s: Append rule labels while parsing api.Rule (@ashwinp) -- https://github.com/cilium/cilium/pull/4175
PR: 4173 -- xds: Match the client's version if higher than the server's (@rlenglet) -- https://github.com/cilium/cilium/pull/4173
PR: 4167 -- ipcache: Create copies of NPHDS cache resources when updating (@rlenglet) -- https://github.com/cilium/cilium/pull/4167
PR: 4152 -- Fix image formatting and simplifies app yaml (@ackerman80) -- https://github.com/cilium/cilium/pull/4152
PR: 4150 -- test: Don't gather logs in -holdEnvironment (@joestringer) -- https://github.com/cilium/cilium/pull/4150

test-docs-please

test-me-please

test-docs-please

CI failure appears to be this:
14:10:28 import cycle not allowed
14:10:28 package github.com/cilium/cilium/bugtool
14:10:28 	imports github.com/cilium/cilium/bugtool/cmd
14:10:28 	imports github.com/cilium/cilium/test/helpers
14:10:28 	imports github.com/cilium/cilium/test/ginkgo-ext
14:10:28 	imports github.com/cilium/cilium/test/helpers
14:10:28 Makefile:43: recipe for target 'tests-ginkgo-real' failed

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-docs-please

@aanm I had to remove examples/policies/l4/cidr_l4_combined.json because it didn't pass validation. I can't find where it's used. Is there a reason you backported it? The commit that backported it is the current HEAD of v1.0, which has been broken since last week. The fixup commit is the most recent one on this PR.

test-me-please

test-docs-please

@raybejjani I thought it was being used in the v1.0 docs, it's fine them

test-me-please

test-me-please


Fixed visual bug

What is the context of this PR?
There is small visual bug where the date range type was not correctly displaying the dummy data entry. This Pr fixes that issue by adding an extra prop type that can override the others.
How to review
Tests pass and the date range answer displays correctly and the date properties can also be correctly changed.

 Small visual bug on dateRange answers


How to disable 'reconnect'?

I wanna to excute my script with ttyd, but it excute the script every 10s by default. So, how to disable auto reconnect but when I refresh the web browser ?

--reconnect 0

[root@test-centos7 ~]# ./ttyd_linux.x86_64 --reconnect 0 --readonly ./sample.sh
ttyd_linux.x86_64: invalid reconnect: 0

--reconnect 0 not work in CentOS 7 x86_64.


Fix NavMesh map_update_id returning 0 results in errors.

Note that a similar change is included in https://github.com/godotengine/godot/pull/79577 but I will rebase that now to this version to avoid a duplicated change.

Thanks!

Cherry-picked for 4.1.2.


Not equal operator with empty array

Hello!
I recently was making a lot of work with Spot2. I really appreciate the lightweight syntax, because I need to query database a lot SQL IN (...), NOT IN (...).
Imagine a model (Entity) has some fields with tag_id field, that cannot be null.
For example, I have the following code:
$entities = $entityMapper->where('tag_id !=' => $unneededTagIds);

That works great, generating query (for example)
SELECT * FROM entities WHERE tag_id NOT IN (1,2,3);

But, sometimes I have an empty array of unneeded tags. And when it occurs, Spot2 makes the next query
SELECT * FROM entities WHERE tag_id IS NULL;

I suppose, that is not you may expected. It will fetch 0 records, regardless of the original intent - to fetch all records with tag_id's not contained in specified array. I think the proper query in that specific case would be
SELECT * FROM entities WHERE tag_id IS NOT NULL;

I use MySQL, but as far as I know IS NULL and IS NOT NULL is not vendor-specific.
As I can see, the error can be fixed in \Spot\Query.php file, method parseWhereToSQLFragments, line, the if block starting at line 331.
UPD @vlucas, If you want, I can fork and fix it.

Yes, is should be IS NOT NULL in that case - good catch. I had to make an empty array translate to IS NULL instead of IN(), which produced an SQL error. If you want to patch it and submit a PR, I'd be happy to merge it and publish a new release so you can use it. Thanks!


Cant seem to get any search results

Hi I have set up google custom search and that seem work fine when i test it.
Now when i try to add it to mu laravel app using this package I'm not getting any results returned its just a empty array so i tried to test if it goes into the get results function  by adding a die statement and it doesn't seem to be.
//Code from your pakage
public function getResults($query)
{
die(print('im here')); // die statement to check if it reaches here
$searchResults = [];
    if ($query == '') {
        return $searchResults;
    }

    if ($this->searchEngineId == '') {
        throw new \Exception('You must specify a searchEngineId');
    }

    $client = new Client();
    $result = $client->get('http://www.google.com/cse', ['query' => ['cx' => $this->searchEngineId,
            'client' => 'google-csbe',
            'num' => 20,
            'output' => 'xml_no_dtd',
            'q' => $query,
        ],
    ]);

    if ($result->getStatusCode() != 200) {
        throw new Exception('Resultcode was not ok: '.$result->getStatusCode());
    }

    $xml = simplexml_load_string($result->getBody());

    if ($xml->RES->R) {
        $i = 0;
        foreach ($xml->RES->R as $item) {
            $searchResults[$i]['name'] = (string) $item->T;
            $searchResults[$i]['url'] = (string) $item->U;
            $searchResults[$i]['snippet'] = (string) $item->S;
            $searchResults[$i]['image'] = $this->getPageMapProperty($item, 'cse_image', 'src');

            $searchResults[$i]['product']['name'] = $this->getPageMapProperty($item, 'product', 'name');
            $searchResults[$i]['product']['brand'] = $this->getPageMapProperty($item, 'product', 'brand');
            $searchResults[$i]['product']['price'] = $this->getPageMapProperty($item, 'product', 'price');
            $searchResults[$i]['product']['image'] = $this->getPageMapProperty($item, 'product', 'image');
            $searchResults[$i]['product']['identifier'] = $this->getPageMapProperty($item, 'product', 'identifier');

            $searchResults[$i]['offer']['price'] = $this->getPageMapProperty($item, 'offer', 'price');
            $searchResults[$i]['offer']['pricecurrency'] = $this->getPageMapProperty($item, 'offer', 'pricecurrency');

            ++$i;
        }
    }

    return $searchResults;
}

// My serach method to call the getResults method.
public function search(Requests\SearchRequest $request)
{
$search = $request->all('search');
$searchResults = GoogleSearch::getResults($search['search']);
    //die(print_r($searchResults));
}

Could you tell me what I'm doing wrong!

Are you sure that $search['search' contains a value? Try testing with a simple string just to be sure.

I'm having the same issue, i'm using Laravel 5.2 and can't seem to get it working..
I installed it using composer, set my search engine ID and can never get anything other than empty braces.
`
$searchResults = GoogleSearch::getResults('a');
dd($searchResults);`
The result is always an empty set [] regardless of the content and the query.. Not sure what to do anyone have tips?

I'll put a little note in the readme about this change.


Merge staging into main

feat(signin): New signin route with tests (#56)
fix(case sense): Adds case insensitive name index (#61)
fix(schema): Make name on user_profiles not null (#59)
fix(schema): Increase user_profiles.name length to VARCHAR(36) to allow the use of default uuid if there is no username
chore(actions): Update actions yml to run against staging (#58)
chore(container versions): Pin image tags for local supabase (#57)
chore(renovate): Run renovate against staging branch
chore(eslint): Remove jest/no-hooks rule
chore(wallaby): Configure
chore(housekeeping)
docs(README): Improve and remove traces of device
test(open handles): Trying to find the open handle - still WIP (#60)
test(schema): Add tests for schema that run against constraints

Tests all passed. Last merge into staging (docs only) don't need ci runs


how to save the sdf result?

Hi there,
I have downloaded the code and tried to run with my computer, but I haven't see any code to save the result of the calculated sdf as the picture you put in "readme".

Quite old, but you can serialise the result to disk or cache the pointer if you're interested in doing that.


emacsPackages.map fails due to hash mismatch

Issue description
nixos-rebuild switch --upgrade fails due to hash mismatch
hash mismatch in fixed-output derivation '/nix/store/840nz9r58dw9nqqnp14x8pcfkhmic3k8-map-3.2.1.tar':
  wanted: sha256:1vy231m2fm5cgz5nib14ib7ifprajhnbmzf6x4id48h2491m1n24
  got:    sha256:1zj0y3nvkrd2v43za214xr3h9z6wyp7r5s6nf5g1pj272yb871d1

Steps to reproduce
nixos-rebuild switch --upgrade
Technical details
% nix-shell -p nix-info --run "nix-info -m"

system: "x86_64-linux"
host os: Linux 5.10.98, NixOS, 21.11 (Porcupine)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.16
channels(root): "nixos-21.11.336103.40ef692a55b"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

That's probably something from your config instead of nixpkgs as I can't find a package called map in our repo

@drmrcol In the future, it might be more helpful if you post what you believe may have caused the issue or instead share the part of your config which when included causes the issue.
I got lucky by grepping the hash and it showed up here and can be accessed by emacsPackages.map. Apparently the hash changed since on a recent commit to master  the only change was to the hash (https://github.com/NixOS/nixpkgs/commit/1dc68f203cc0d495dcd271d973590511adb1aaa6). It currently builds on master but not on nixos21.11
Here might be a possibly related issue where emacs packages hashes change. https://github.com/NixOS/nixpkgs/issues/75714  (I dont know if this is something we need to live with)

thank for the help to identify the problem
does it mean that this update will be ported from master to 21.11, or is it better for me to switch to master?

@AndersonTorres a few days ago you have commited a change (https://github.com/NixOS/nixpkgs/commit/1dc68f203cc0d495dcd271d973590511adb1aaa6) that fixes hashes of some emacs packages from elpa.gnu.org to master.  Could you also add the changes to 21.11 so that your fix is included in the stable branch. Thanks!

@AndersonTorres thx :green_heart:

@AndersonTorres, I'm afraid that the issue have not been fixed. https://github.com/NixOS/nixpkgs/pull/161753 did not contain update to the relevant emacs package (map).
See the hashes from both branches:

https://github.com/NixOS/nixpkgs/blob/nixos-21.11/pkgs/applications/editors/emacs/elisp-packages/elpa-generated.nix#L2332 has 1vy231m2fm5cgz5nib14ib7ifprajhnbmzf6x4id48h2491m1n24
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/editors/emacs/elisp-packages/elpa-generated.nix#L2422 has 1zj0y3nvkrd2v43za214xr3h9z6wyp7r5s6nf5g1pj272yb871d1

thx in advance

Perhaps useful: the commit that was referenced (https://github.com/NixOS/nixpkgs/commit/1dc68f203cc0d495dcd271d973590511adb1aaa6) is really quite different from the changes that were merged in an attempt to fix this issue (https://github.com/NixOS/nixpkgs/pull/161753/files)

Yes, I have upgraded Emacs packages and backported it. I will look at it again.

Oh, I have noticed. I put it on release-21.11, not nixos-21.11.

@AndersonTorres , perhaps I misunderstand something, but if I look at your branch that you are trying to merge, it has the wrong hash for emacsPackages.map. Could you confirm? If yes, the your MR will not fix the problem, right?

Original error message

hash mismatch in fixed-output derivation '/nix/store/840nz9r58dw9nqqnp14x8pcfkhmic3k8-map-3.2.1.tar':
  wanted: sha256:1vy231m2fm5cgz5nib14ib7ifprajhnbmzf6x4id48h2491m1n24
  got:    sha256:1zj0y3nvkrd2v43za214xr3h9z6wyp7r5s6nf5g1pj272yb871d1

Hash in your branch: 1vy231m2fm5cgz5nib14ib7ifprajhnbmzf6x4id48h2491m1n24 which is different from "got"

https://github.com/AndersonTorres/nixpkgs/blob/nixos-21.11/pkgs/applications/editors/emacs/elisp-packages/elpa-generated.nix#L2339

https://github.com/NixOS/nixpkgs/pull/161871

Hi @AndersonTorres , I've read the documentation on backporting and saw your merged PR (https://github.com/NixOS/nixpkgs/pull/161871) to release-21.11 branch.
I looked for the mis-matching hash and was not able to find it. Do you think that I've missed it? Like I said, https://github.com/NixOS/nixpkgs/commit/1dc68f203cc0d495dcd271d973590511adb1aaa6 seems to be fixing the hash. Do you think that it somehow did not get into the PR?

The problem is that it does make no sense. The idea of a backport is that the tip of master should be injected onto the release.
However it does not happen automatically, and the merge conflict is not something trivial with a few lines. The machine-generated files are big indeed.

The problem is that it does make no sense. The idea of a backport is that the tip of master should be injected onto the release.

I'm really not that familiar with nixos' release process. That said, from the documentation about backporting that you referenced, I understood that only selected commits are cherry-picked from master and commited to release-*. I'm not sure what do you mean by "tip of master should be injected onto the release", but I'm pretty sure that the documentation does not mean to merge master onto release branch.
I also don't want to loose track of the issue at hand: the problem is that some Emacs packages from NixOS 21.11 are broken due to changes in hash values of source tar balls (which should btw not happen, but that's another issue). It's only about hashes. The logic & versions of those packages don't need to change.
I've pinged you, because I saw that you fixed those hashes in master and asked if you could fix those hashes in release-21.11 too.
Thanks for your effort!

https://github.com/NixOS/nixpkgs/pull/162109/files
Now I declare this fixed!

awesome! nixos-rebuild switch --upgrade finally worked after a few few weeks that it was failing!
thank you!


Can't map to index 0 in immutable record list??

I have checked Stack, and Im not getting much on help on this.  I don't think it's a bug but I can't figure this out and I'm not sure what this is at this point.
What happened
So to keep things simple.  In my react stateless function component  I have 3 console logs, literally in this order, nothing inbetween.
    console.log("PHOTO0::",competitor);
    console.log("PHOTODESC::",competitor.description);
    console.log("PHOTOIMAG::",competitor.imageLink);
    console.log("PHOTOKEY::",competitor.key);

Competitor is a Immutable record with a list.   Here is what the consoles produce.
console.log("PHOTO0::",competitor);
expanded view of the record

and the other 3.
    console.log("PHOTODESC::",competitor.description);
    console.log("PHOTOIMAG::",competitor.imageLink);
    console.log("PHOTOKEY::",competitor.key);

produce this immediately after

So my question is why can I not use the dot notation on description?   Why does is show undefined but clearly it is there in the immutable record when viewing the whole record.
FYI Im React ^15.6.1, redux ^3.7.1, immutable ^3.8.1 using latest chrome browser. Have looked around and haven't been able to find similar issues on net. Any help greatly appreciated.
I have more info in a stack post but i think its unnecessary and I've gotten no help.
https://stackoverflow.com/questions/50306736/cant-read-list-entry-in-immutable-record
There's even a bounty on it there as I said I dont 'think' it's a bug but im starting to wonder what I'm missing.  I have read docs.  Not cover to cover but enough that I think this should work at this point.

So I finally found it. It was a typo where I was instantiating my Record. I was missing a 's' in description in my Record which was messing up this whole thing.
this is what I had that was bad
export const Competitor = new Record({
decription: null,
pic: null,
key: null,
});

It should have been,
export const Competitor = new Record({
description: null,
pic: null,
key: null,
});

From my console log above it was there all along, I had missed it because I was entering into my database correctly and it showed in my list entries correctly.


Add Basis constants and format Transform constants

Add Basis constants IDENTITY, FLIP_X, FLIP_Y, FLIP_Z to core and C#. Fixes https://github.com/godotengine/godot/issues/26682

Core: Format Transform and Basis constants to be declaration statements with constructors. This IMO makes the code clearer and avoids repeating the variable name. Also, rename the local variables to flip_x_transform etc, and add Transform constructor for twelve real_ts.

C#: Move constants above constructors and format just like Vector2/3/etc code.

Thanks!


Fix p tag size

Make p tag text size larger
e.g. Build an API text in below image

I'll do it!

@tombrowndev Go ahead!

#13

Can you share screenshots? So I can confirm?

@tombrowndev Thank you for your contribution and for giving your valuable time to improving this project.

@tombrowndev If you found any bug you can PR for that >

@tombrowndev Thank you again!


Register DataGraphPlots.jl

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/102330
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" ebe7feea4b7cdc13a2b60185f0103206d3ba0d45
git push origin v0.1.0

Renamed package. Will reregister as new issue


ERROR: Failed building wheel for hnswlib

i think this is common for other builds as well.

What Python package is that related to?

What Python package is that related to?

Can one of you guys provide this info?

What Python package is that related to?

Can one of you guys provide this info?

I believe that is related to chromadb:
Collecting mpmath>=0.19 (from sympy->torch>=1.6.0->sentence-transformers>=2.2.2->chromadb==0.3.11->-r requirements.txt (line 9))
  Using cached mpmath-1.3.0-py3-none-any.whl (536 kB)
Building wheels for collected packages: hnswlib, sentence-transformers
  Building wheel for hnswlib (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for hnswlib (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
      running bdist_wheel
      running build
      running build_ext
      building 'hnswlib' extension
      error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for hnswlib

I had problems with pinecone and chromadb so i edited the code and added the JSON settings and i solved all of my problems ahaha

my python is 3.10, yes ,that is the package. I only have 3.7 and 3.10 but i think <3.8 doesn't work with GPT packages.
@novaprod where in the JSON settings?

I just removed the chromadb package from requirements, users will need to install it manually if they choose to use ChromaDB.


Unable to determine neovim windows id for editor viewColumn: 1

I occasionally get an error like this when first trying to open a file:
2020-10-28T15:20:07.854Z BufferManager: Unable to determine neovim windows id for editor viewColumn: 1, docUri: file:///home/xxx/xxx/file.ts

It does not seem repeatable but might point to a problem.

Having the same issue, and it shows everytime vscode start up:
2020-11-11T09:46:04.567Z BufferManager: Unable to determine neovim windows id for editor viewColumn: undefined, docUri: output:extension-output-%234

I have also the same issue.
It happens sometimes when I open diff view from the scm panel.
This is quite random but it does happens quite a lot.
Closing and reopening the file / view is enough in general to get control back.
2020-11-11T15:25:53.581Z BufferManager: Unable to determine neovim windows id for editor viewColumn: undefined, docUri: filePath
I seems to happens to more the faster I change files / views.

Ok since this is rather annoying might as well try to solve this or at least find some clues !
The problem comes from src/buffer_manager.ts
Sometimes syncActiveEditor is called but just before syncLayout actually deleted the TextEditor element from the map editorColumnsToWinId.
syncLayout is called after and set back the correct TextEditor value inside the map.
I'll investigate more when I have more time, but it looks like some kind of side effect bug.

@Nico-Guyon thank you for the investigation. This error is harmless now, so i just downgrade report level
Released 0.0.71 with the fix


Use defines to selectively store delay table in flash

Saves 8 bytes of RAM.

Well, thank you for the effort of writing the basis for a non-bloat lib for the HTU21D, certainly saved me the effort... :)


[Feature Request] Option to download avatars in tag-specific modes

Prerequisites

[x] Did you read FAQ section?
[x] Did you test with the latest releases or commit ?

Description
I only want to download images with specific tags, so I'm usually unable to download only by member id; however, despite the avatar url being fetched in other modes as well, the member avatar only currently seems to be downloaded in mode 1 Download by member_id.
Other modes I tried out without success: 2, 7, 10
Versions
PixivUtil20180726

Avatar is only download by using option 1. This is by design.
It doesn't make sense to enable for other modes, as it just will create a clutter of avatar images (if the filename is unique) or it just will overwrite the current avatar filename in the current folder (by default, it will uses folder.jpg).

Fair enough, but wouldn't it at least make sense to also download the avatar with option 10 seeing as it's basically a filtered version of option 1?
The cluttering or overwriting would happen in either case, if you were to redownload by member id.


Developer flow for onboarding new repos

I'd assume most developers should not have k8s read access to the credentials in the jx-boot secret. To work around this, my internal developer-facing documentation currently looks something like:

set up the git credential helper
run:

jx project import \
 --no-collaborator \
 --git-username=$GITHUB_USERNAME \
 --git-token=$GITHUB_PERSONAL_ACCESS_TOKEN \
 --jx \
 --no-start

Would you like to add a Jenkins server?: Choose No
Choose our custom pipeline catalog
Choose the our-org-gradle-spring pack
review the files in the .lighthouse directory
make any desired changes
git add .lighthouse
git commit
git push to a feature branch
file a PR adding the .lighthouse pipeline folder to the main branch of the git repository

cons:

disjointed and clunky
developers require write access to the dev/preprod gitops cluster repo. the cluster-repo pr logic could optionally use a fork
we have previously chosen to grant our github bot PAT owner permissions over the entire organization. some folks may not be able to do this

What can we do to improve this experience for non cluster-operators?

This issue will not be addressed for several reasons:  it is formulated not as an issue but rather a discussion starter. As such it would fit better in Slack. See https://jenkins-x.io/community/
Also it is in the wrong repository: We use a jenkins-x/jx as a central issue tracker https://github.com/jenkins-x/jx/issues/new

https://kubernetes.slack.com/archives/C9MBGQJRH/p1648166888284829


Add basic email queue viewer page. Add kgrruz/codeigniter4-email-queu…

…e package requirement.

Pretty soon CodeIgniter should have an expanded email library and a Queue system, so I'm holding out on that for these features for now.
This would make a good personal package if you're needing to use it soon, though.

OK. Thanks.


[SCB-821] Add missing dependency management for omega-transport-feign

The project failed to build with -Prelease.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [SCB-XXX] Fixes bug in ApproximateQuantiles, where you replace SCB-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.08%) to 94.216% when pulling 9de1c80843c819a0ce587068986afa3ca3f12417 on yangbor:master into bb3b614409c51adf4a20323e7e6ee7d50d7dd2f3 on apache:master.


Fix f1 score for macro and ignore index

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
Fixes https://github.com/PyTorchLightning/metrics/issues/486
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@Borda have added test now. But we did not have test because its a corner case.


Create separate processors for transcludes-driven rerenders

We could potentially do something programmatically to avoid config copy-pasta, but I think it doesn't worth it, being explicit is cleaner in this case.
Bug: https://phabricator.wikimedia.org/T145804
cc @wikimedia/services

Corresponding change in deploy repo: https://gerrit.wikimedia.org/r/311602

Coverage remained the same at 93.402% when pulling 378d2be4f6a86150aa52e07546e8cd9a8718cdaa on Pchelolo:transcludes_separate into 4d96b67b8abddbc9c6816e369ce4ab6f269d34bf on wikimedia:master.

Coverage remained the same at 93.402% when pulling 378d2be4f6a86150aa52e07546e8cd9a8718cdaa on Pchelolo:transcludes_separate into 4d96b67b8abddbc9c6816e369ce4ab6f269d34bf on wikimedia:master.

Coverage remained the same at 93.402% when pulling 378d2be4f6a86150aa52e07546e8cd9a8718cdaa on Pchelolo:transcludes_separate into 4d96b67b8abddbc9c6816e369ce4ab6f269d34bf on wikimedia:master.

@d00rman done

Coverage remained the same at 93.402% when pulling bdb91c22e615c59ac3869b62e7a3c70a9c1bc94d on Pchelolo:transcludes_separate into 4d96b67b8abddbc9c6816e369ce4ab6f269d34bf on wikimedia:master.


Notes: Resolve with comment requires double click

URL
edit*
How to reproduce the issue?

Open a note.
Write a comment.
Click "resolve with comment". Nothing happens.
Click it again.
(Optionally, exit the note between step 3 and 4, this action is still saved)

Screenshot(s) or anything else?
This does work in one click on the https://mapwith.ai/rapid version.
Which iD Editor versions do you see the issue on?
Released version at openstreetmap.org/edit, Development version at ideditor.netlify.com
Which browsers are you seeing this problem on?
No response

True, I saw that too.

Copying reproduction steps from #9217, for convenience:

How to reproduce the issue?

Open the editor in an area of the map with an unresolved note
Address the note.
Click the "New Comment" box under the note's text
Enter some text
Click the "Close and Comment" button under the text box
The note doesn't get closed, nor the comment added (However, and crucially, the text box loses focus)
Click the "Close and Comment" button again
This time, the note is actually closed.

Screenshot(s) or anything else?
Here's a short recording of the bug. The context is I had written a comment, and was about to close the note with it.

Note that I first hovered the "Close and Comment" button, but didn't click it, because I realized I had lost focus of the text box when I started the screen recording. So to reproduce the issue, I clicked the text box again (notice how its background color becomes a slightly darker gray), and then clicked the button. That didn't have the desired effect (i.e. the bug manifested); then I clicked the button a second time, and the note was closed.

Thanks, it helps. I often had this issue and didn't realise it was a bug.

This error still occurs!

This error still occurs!

Use the development mirror. It will be pushed to the live version eventually.
https://github.com/openstreetmap/iD?tab=readme-ov-file#participate
It works fine on my end.

But it was released with the version 2.29.0 and I'm using this version. I found this topic because of changelog.

Yes, understandable. However, for the current version the change is broken by accident. It has since been resolved for a future version.
https://github.com/openstreetmap/iD/pull/10205#issuecomment-2075052817


[Bug]: Using AzureOpenAI in LiteLLM shows API_version not set.

Bug Description
While creating LLM object using llama_index.llms.LiteLLM,
I am trying to set Azure Open AI model, also structure of the object initialization is as below.
def create_llm_object(**kwargs):
        print(kwargs.get('api_version', None))
        llm = LiteLLM(
            model = kwargs.get('model', None),
            temperature= kwargs.get('temperature', 0.2),
            max_retries=2,
            api_key=kwargs.get('api_key', None),
            api_base=kwargs.get('api_base', None),
            api_type=kwargs.get('api_type', None),
            api_version=kwargs.get('api_version', None)
        )

        return llm

but the error I am getting displayed after retries is
litellm.exceptions.APIError: AzureException - Must provide either the `api_version` argument or the `OPENAI_API_VERSION` environment variable

Not sure if this related to Llama index but api_version is a valid key in litellm.completion()
Reference same Azure Credentials work with litellm package sample code below :
import litellm

# azure call
response = litellm.completion(
    model = "azure/my_sample_deployment",             # model = azure/<your deployment name>
    api_base = "",                                      # azure api base
    api_version = "",                                   # azure api version
    api_key = "",                                       # azure api key
    messages = [{"role": "user", "content": "good morning"}],
)

I don't know if its a bug or my mistake kindly address.
Version
0.9.34
Steps to Reproduce
Create a simple LLM object using LiteLLM in Llama_index.llms and then try the complete method.
Relevant Logs/Tracbacks
No response

Thanks, let me check the source code and get back

@dosu-bot one observation is that the api_base is getting passed properly but LiteLLM is not assigning it to any variable, even tried passing it as an additional_kwargs still fails.

@dosu-bot thanks i will have a look

Hi, if anyone can help in this issue please share an example with LiteLLM class creating an Azure Openai llm instance
thanks

@dosubot I was still unable to implement this .. can anyone please share any sample code for azure


The Google provider won't work after Januar 28, 2019 (I think)

I know this project is deprecated and this is mostly for info. Google is shutting down Google+ and the Google+ API. GoogleProvider is using Google+ APIs (like /plus/v1/people/me) in the RetrieveUserInformation-method. I don't think that this will work after January 28, 2019. Google writes the following:

On March 7, 2019, all Google+ APIs and Google+ Sign-in will be shut down completely. This will be a progressive shutdown beginning in late January, with calls to these APIs starting to intermittently fail as early as January 28, 2019.

When looking at the code, I think that the google provider will break on this day.

That would be lovely @ThomasArdal - i'm not sure what other alternatives there are though. I should also have some bandwidth this 🎄 -> 🎆 to update this, too. maybe even move it to .NET Standard. (maybe ... bandwidth permitting).

You're right. Moving to .NET Standard wouldn't make sense unless you want to revive the package or something like that. Would be great if the google provider worked for projects already using it.
I'll take a look when I have time :smile:

There you go: https://github.com/SimpleAuthentication/SimpleAuthentication/pull/224


cmd/vet: unable to detect unreachable code

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?
go version go1.7rc1 windows/amd64

What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:/work/go/
set GORACE=
set GOROOT=c:\go
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=c:\temp\go-build108228690=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1

What did you do?
go tool vet -unreachable main.go

// main.go
package main
const flag = false
func main() {
	if flag {
		println("<<unreachable code>>")
	}
}

What did you expect to see?
a warning from vet

What did you see instead?
no warnings

I don't think we'd want vet to complain about such code. That's a fairly typical way to add debugging code, particularly in hot functions where you can't accept any runtime overhead when not debugging.

It turns out that it is impossible to determine what code was eliminated?
package main
const erraneous = (1 << 0) - 1
func main() {
	if erraneous == 1 {
            println("dead code")
	}
}

Code is silently eliminated by the compiler. And no warnings from vet.
Maybe it makes sense to add -report-eliminated-code flag to the compiler or vet? Just an idea.

We try fairly strenuously to avoid flags.

Working as intended, as @josharian explained.


QCR2 - Integrate FTC Dashboard

Completed- Imported, and is used by PID tuning. Panopticon is yet to be done, see different issue


Replace Set usage with plain objects

As discussed in https://github.com/FormidableLabs/radium/issues/604#issuecomment-200539952

1.0.4 is out. You should now be able to safely update radiums dep :P

:bow:


Update rg-sidemenu with rg-sidemenu-item tags

To provide greater flexibility of content

This issue was moved to RiotGear/rg#4


Figure 5.3 change

This change includes some details which I think cannot be ignored, including axis, color, description.
Originally, the x axis starts from 0, but this doesn't make sense. So I changed it to start from 1. I also set the y axis limit to 5.
Before:

Now:

And I think the new one is closer to the one in the book:

Thanks a lot for the contribution!

My pleasure. :smile:


Redesigned index preconditions and index step execution

PR for #96
Also adapted unit tests to the changes.

Coverage increased (+1.1%) to 82.112% when pulling 16c1c55217c3e5c1bcaafe3194e9fb7c163ebfa8 on 96 into 41ebcc9fdec6a9360b7c7ce9be24360ab183df55 on master.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/51392

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/56495

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58747

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/61035

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/63777

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/64634

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67159

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86923

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/87198


Remove BronyTunes and EqBeats hourly regular sync

EqBeats is no longer actively in service, so there will be no new changes to the music data already present in the PVL database for it. BronyTunes was largely only included to pull items from the entire MLPMA (which they contained), but with the MLPMA being folded into Pony.fm, it can be used as the sole source for external music records.

Thanks! I'll be on the lookout for more 503's following this change.


Java Libs Project requires Java 1.8, but uses packages introduced in Java 11

Bug Report

Description
java.net.http was introduced to Java with 11, not 1.8. Therefore, the java libs project will not compile.
I tried this code:
./gradlew build
I expected to see this happen: build successfully
Instead, this happened: Webhook.java:3 error: package java.net.http does not exist import java.net.http.HttpHeaders;

I'm able to import and use the library in a Java 8 project to interact with the Svix webhook service API in general, but can't use this Webhook class. This looks to be the only application code which is using Java 11+ features (e.g. java.net.http.HttpHeaders class).
https://github.com/svix/svix-webhooks/blob/58689c8b38d55d085bdfde04b4afbbc5ef5d7e43/java/lib/src/main/java/com/svix/Webhook.java#L43-L56
Could potentially either bump the minimum supported Java version to 11, or update this class and tests to be Java 8 compatible - though unsure of what would be the best way to do that without affecting existing downstream users of the verify() method.


Dremio jdbc plugin

What changes are being made and why?

Added dreamio query task and Trigger using the JDBC drive.
Added Query task using the Arrow Flight SQL JDBC drive.

How the changes have been QAed?
Dreamio query was tested through Dremio Test Drive and Dremio OSS (Docker)
Arrow Flight SQL was tested through Dremio account, adding source that supports Apache Arrow Flight sql
id : dremio-listen
namespace: dev

triggers:
  - id: watch
    type: io.kestra.plugin.jdbc.dremio.Trigger
    url: "jdbc:arrow-flight-sql://localhost:31010/?useEncryption=false"
    username: "dremio"
    password: "dremio123"
    sql: "SELECT * from \"dremio-test\".\"postgres.public\".departments"
    fetch: true
    interval: PT10S

tasks:
  - id: query
    type: io.kestra.plugin.jdbc.dremio.Query
    url: "jdbc:arrow-flight-sql://localhost:31010/?useEncryption=false"
    username: "dremio"
    password: "dremio123"
    sql: "SELECT * from \"dremio-test\".\"postgres.public\".departments"
    fetchOne: true

Setup Instructions

Dremio Arrow Flight Authentication (URL example)

closes https://github.com/kestra-io/kestra/issues/1854


Alias or nickname

This plugin is great. It's right what i was looking for. Our repos are at a gitlab instance and it's far better to review them at gitlab's than at redmine's, so this plugin is very useful, and the option to open them in new window is perfect.
I have a little issue, our domain name is a little long, it would be nice to supply an optional alias to the repo url and show the alias instead of the domain.
Long link:

Short alias:

Glad you link the plugin.  I thought about the ability to add an alias, but wasn't sure if others would want it.
If now added the following:

Custom Link Text configured with each repository.
Global configuration to Replace the Redmine Revision Links completely (instead of adding additional link).

See README for more details.
Thanks for the feedback.

Excellent. Thanks for the solution.

@cheoAlejo, FYI found a few bugs, one if which was significant.  I suggest you update to the latest if you haven't already.


Comment : Works on AMD MI210 GPU with ROCm 5.7

@louity - Love this repository! I was able to get up and running fairly quickly. I also wanted to share that this works with ROCm 5.7 and AMD MI210 GPU. When installing torch you can simply point to the rocm index
pip3 install torch --index-url https://download.pytorch.org/whl/rocm5.6

Currently, rocm5.6 is listed in the pytorch index, but doesn't seem to conflict with ROCm 5.7 .

Thanks, added in Readme


Add Keywords/Descriptors to Metanorma-ISO

ISO flavor doesn't include :keywords: as document attribute. However, ISO 10303-49 includes "Descriptors", which are listed at the end of the paper. This is a single case I encountered while converting ISO 10303 documents, so I was wondering whether keywords should be removed from the source .adoc in this case, or ISO documents can regularly include keywords, making them a needed document attribute.

A number of ISO 10303 documents include them, so we should enhance Metanorma-ISO to accept them.

In HTML, they should not placed in a final colophon, and ICS already isn't. These two are being put at the bottom of the title section instead.

Moving keywords to isodoc from individual flavours


[VkBridge] Double encoding

Describe the bug
Some html entities are double encoded.
To Reproduce
Visit: https://feed.eugenemolotov.ru/?action=display&bridge=Vk&u=english_bookland&format=Atom
First article has double encoded entities: &#39;
Expected behavior
Above entity should be '

Looks fine in html version

What is causing &#39; in the Atom output?

In Atom case it also does not seem to be a bug. http://i.imgur.com/RFwOsGK.png

Feed readers can typically deal with double encoding errors, but they are still errors. Anyone who knows html knows that &#39; is bad html.

Closing this, I no longer use the bridge and this double encoding is handed well by clients.


Improve documentation for K8S config

There is a section in the documentation about K8S. The corresponding XML snippets explain how to configure discovery but there is no mention about the required config for Vert.x distributed data:
<multimap name="__vertx.subs">
 <backup-count>1</backup-count>
 <value-collection-type>SET</value-collection-type>
</multimap>

<map name="__vertx.haInfo">
 <backup-count>1</backup-count>
</map>

<map name="__vertx.nodeInfo">
 <backup-count>1</backup-count>
</map>

<cp-subsystem>
 <cp-member-count>0</cp-member-count>
 <semaphores>
   <semaphore>
     <name>__vertx.*</name>
     <jdk-compatible>false</jdk-compatible>
     <initial-permits>1</initial-permits>
   </semaphore>
 </semaphores>
</cp-subsystem>

This information is only present in the section about clusters created from an existing Hazelcast instance.

Closed by 33ba7bfc42ce7332fae6deb361fe205be38ea7c2


Implement unit conversion for input oxidants in SU component.

This PR implements tentative unit conversion for OH (and potentially other oxidants).
See issue #60

Issue #60 was resolved. This PR is no longer necessary.


feat(version): support for updating pnpm-lock.yaml, expand on #168

Description
takes PR https://github.com/ghiscoding/lerna-lite/pull/168 and addresses all comments provided in the original PR
Motivation and Context

fixed npm lockfile that got broken by original PR, I took the same approach as the pnpm lock file update to fix the npm lock file update. Both updates are now very similar and easier to read
removed preferred-pm since I would prefer to not use any extra dependencies, and I think that also fixed the unit tests since they weren't being detected properly
added a prettier VSCode setting (setup) and also fixed couple of places where prettier wasn't doing a good job
add a new flag no-update-root-lock-file just in case this pnpm update causes issues, at least the user could disable it

How Has This Been Tested?
only local unit tests for now, we might need a bit more testing, need to validate with @JacobSoderblom
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@JacobSoderblom
I took your original PR and addressed all comments I left the first review, I also fixed a bug that you introduced and might have missed with the npm lock file update that was and is now working again (your original PR updated the unit test snapshot with wrong version number). When you have a chance, could you please review this PR? I created this new PR because I couldn't write directly to your branch and didn't hear from you but I still wanted to advance this PR since I'm also moving towards pnpm workspace and I'll need this as well 😉
Thanks for your original contribution

I'll try to manage to test this locally today as well

Any update? This is also for me the only blocker to try out lerna-lite :smile:

@StarpTech it's currently in WIP, I don't think it will be until next week or even the week after, that I ship anything related to that... however you could easily use a temporary workaround for this via lifecycle script post to update your lock file, or use this other workaround shown in this post. Using the postversion with the workaround shown in the post is probably the easiest.... or you can wait a week or two until I can finish it. I just want to make sure not to ship something that might cause more problems than it resolves.

@ghiscoding thank you!

@StarpTech @JacobSoderblom
After searching about the same thing after the workaround that I just posted, it seem that Changesets has the same issue which is still open and funny enough the pnpm maintainer (zkochan) is actually suggesting the exact same thing. I actually wonder if it wouldn't be easier to just call pnpm install --lockfile-only internally instead of trying to trying to modify the lock file (mostly because we never know when they'll decide for whatever reason to change their lock file structure), it should use the correct syntax depending on what the user set as his npmClient in lerna.json and after the install is done then just push it to the git changes list like it currently does. @StarpTech Are there any particular reason you've add the package name as a filter? The other thing that worries me with current PR is that calling writeYamlFile seems to change the file structure by removing all extra lines (it might be because of Prettier or something else) and the developers (you) will see a lot of white space changes the next time you'll run a pnpm install, which is another reason that running pnpm install --lockfile-only internally might be a better approach and will be much faster to implement (maybe 1 day versus a week or more), but again I'd like to know why you filtered by a package name?

Are there any particular reason you've add the package name as a filter?

Yes! If I don't scope it to a single package pnpm might throw an error that another workspace package refers to an invalid version. You can only run pnpm install --lockfile-only after all packages have been bumped. I recommend you to call internally pnpm install --lockfile-only once. It is also required to add the lock modification to git git add ../../pnpm-lock.yaml.

I gave a try with npm i --package-lock-only directly in Lerna-Lite (with --git-dry-run) and I seem to have issues because running this command does search on npm registry and doesn't find the newer versions because it's not yet published (that is when we run lerna version), so this strategy might not work. The only way that this would work, would be to run this command after lerna publish which is much later in the process and I'm not sure that everyone would do both version and publish every time, if they only run version then the lock file would not be updated.. that might be ok though!? I'm not sure...
I'll still look at directly updating the lock file, so perhaps if I get both working then we could also have flags for both ways and let the developer choose.
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

So basically the error comes from trying to retrieve "@lerna-lite/init": "^1.4.1" from the devDependencies however the package version number "version": "1.4.1" inside the same package.json doesn't throw the error.
{
   "name": "@lerna-lite/cli",
   "version": "1.4.1"                   // this line is ok
   "devDependencies": {
     "@lerna-lite/init": "^1.4.1" // this line throws, not found in registry
  }
}

Did you use npm or pnpm?

that was with npm on Lerna-Lite project itself, but I imagine pnpm will do something similar, isn't it?

No, pnpm should really just update the lock :smile:

According to npm docs:

The --package-lock-only argument will only update the package-lock.json, instead of checking node_modules and downloading dependencies.

Looks like a bug.

ahh I didn't know about that offline option, dang there's so many flags... however after trying it over lunch, it doesn't seem to help and I'm pretty much getting the same error (with/without --workspaces is the same too), kinda weird
> npm install --workspaces --offline --package-lock-only
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

@ghiscoding I found a way. If you bump all versions and run pnpm update --workspace it will use only the local version when the version exists.

So finally. I tried on a fresh pnpm monorepo with two packages. No errors.
test.zip
.

As a lerna user, you have to specify npmClient. That means you can provide that fix just for pnpm. I don't recommend playing "package manager" because it's complicated and error-prone.

As a lerna user, you have to specify npmClient. That means you can provide that fix just for pnpm. I don't recommend playing "package manager" because it's complicated and error-prone.

yes the intention is to add a switch case on npmClient for each package manager for that new flag. Internally it would run that lock only command for whatever client you chose and then do a git commit + push, so that it's less work for the developer (you) to use.

Sounds good! Would be happy to review your PR.

@StarpTech I have a draft PR for the package manager client to update the lock file, I only tried within Lerna-Lite itself in dry-run, I did not try pnpm yet (neither yarn) but if you could take a look at the draft PR and provide any feedback then go ahead to PR #199
Note that I'm not sure if I'll keep working on modifying the pnpm lock file ourselves or just use that new PR to do the job, I think that I might keep both flag for at least npm but not sure about pnpm, if this new approach works better and is more reliable then I will just keep 1 approach. I'm not exactly sure how I'll unit test that though

@ghiscoding I have a repro where NPM works fine like pnpm. Again as long as the version constraint match with the local packages, no error is thrown
test-npm.zip
.

@StarpTech
hmm I might not have that npm version installed then, but the repro is simply Lerna-Lite itself, you can clone it and git checkout the draft PR and that is my repro... yeah just checked and I have npm 8.4.1, this npm fix is not very old either. So I could maybe use shrinkwrap when older than 8.5.0 or use regular install on newer npm version. I'll give that a try later after work

just for reference, since PR #199 got merged and is a better way of handling the pnpm lockfile update. I decided to transform the original PR #168 from @JacobSoderblom and keep only the code that adds Prettier to the project. This way I get to keep his great contributions to the project and his effort and contribution are not entirely lost. Thanks for this great contribution.
I'm expecting to do a release in the coming 1 or 2 days.


component update behaviour

Hello. I'm using a third-party package for creating an ui and faced a strange issue with component not being updated properly.
Sandboxes:

https://codesandbox.io/s/zr4nyky2r3
https://codesandbox.io/s/1o099qywv3

The only difference between them is JSON.stringify() call, which triggers mobx-magic
Docs say to not touch sCU/PureComponent as well.
Are there any possible workarounds?

Little update after some digging: found out that wrapping the Tree component in observer() helps.
Basically, it's following the docs statement:

Use @observer on all components that render @observables.

But the next question then is it really that frustrating with the 3rd party? I'm not really sure this is a correct workaround because it looks a little bit ductape-ish. You can face the need to wrap something down the tree at any moment.

@PLSFIX the clue is that if a third party lib doesn't understand observables, you shouldn't give it observables. Since your Tree lib doesn't know the concept of observable data, you should give it plain data, and toJS can be used to convert it, by means of contents={toJS(appState.tree)}. By doing that in the observer based View component, View takes the responsibility of tracking the changes in the entire tree, and converting it to plain data by means of toJS and pass it to the tree.
Once you do that, you can drop the stringify, which, like toJS traverses the whole tree, making View consume everything in the tree, which is why that work around worked.

https://github.com/mobxjs/mobx-react/issues/484#issuecomment-391685354

Hi.
We cannot use conversation... Because tree in callback return changed element and if convert struct we will lost contecst. We try using Autorun and Reaction but this function not have deep reaction. Maby you will add function with deep reaction for like solution situation?

@RussianDragon not sure if I understand correctly, but note you can use toJS(tree) only to subscribe, but pass the original tree to the 3rd party lib (as suggested in the comment above).

@RussianDragon.
Yes. We use this solution, but... Это костыль!
First: this function need using in render function, and meaning of this function is not clear when reading (it is problem, if project havin many people).
Second: Second: This function easy deleting on refactoring or developing and miss this fact on code review.
More better solution have special function with forceUpdate() in constructor or componentDidMount

I would suggest to create dedicated "workaround" component with the same API as the original component:
// sensible commentary
observer(function OserveringTree({ tree }) {
  mobx.toJS(tree); // sensible commentary
  return El(OriginalTree, { tree });
})

That should make it clear enough I think.
To create "deep reaction" you can use the same technique:
class Comp extends React.Component {
  constructor() {
    this.workaroundReaction = reaction(() => mobx.toJS(this.props.tree), () => this.forceUpdate());
  }
}

However I would avoid this as it's even more convoluted and won't work exactly the same way.


fix(instrumentation-http) Added ATTR_HTTP_ROUTE to the new metric attributes

Which problem is this PR solving?
There is no way to create http.route attribute for server metric in "stable-only mode" for http metrics.
Fixes # (issue)
Short description of the changes
Added ATTR_HTTP_ROUTE setup in "stable-only mode" for METRIC_HTTP_SERVER_REQUEST_DURATION in @opentemetry/instrumentation-http
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] switch to stable-only mode in @opentemetry/instrumentation-http
[x] add rpc metadata http route, check that metric attribute exists
[x] remove rpc metadata http route, check that metric attribute does not exists
[x] switch to dup mode in @opentemetry/instrumentation-http
[x] add rpc metadata http route, check that metric attribute exists in both stable and old metrics
[x] remove rpc metadata http route, check that metric attribute does not exists in both stable and old metrics

Checklist:

[X] Followed the style guidelines of this project
[ ] Unit tests have been added
[ ] Documentation has been updated

@pichlermarc hello. Thank you for your attention


Add convention plugins for buildscript setup

This PR reworks the buildscript logic into using convention plugins, as outlined here: https://developer.squareup.com/blog/herding-elephants/
While this project isn't large enough where it makes sense to test the convention plugins, it still nicely separates build logic and avoids the pitfalls of allprojects, subprojects and buildSrc.
No functional changes here, although the cleaned up build script did remove some unnecessary API files (the root project, test projects, etc.)

Thanks @byencho !


Disabling WpnService breaks the WiFi tab in Settings UWP

Disabling WpnService breaks the WiFi tab in Settings UWP
Leave it manual.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Create FUNDING.yml

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 87.71%. Comparing base (c459832) to head (501444a).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #51   +/-   ##
=======================================
  Coverage   87.71%   87.71%
=======================================
  Files          14       14
  Lines         993      993
=======================================
  Hits          871      871
  Misses         99       99
  Partials       23       23

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


CH odbc driver on TS in Kubernetes

Hi. I'm trying to install CH odbc driver on TS in Kubernetes, but I'm getting error when trying to setup data source on TS:
The driver required to connect to the data source isn't installed. Contact your Tableau Server Administrator
Tools:
TS version: 20214.21.1217.2252
CH ODBC Driver version: 1.1.10-1.el7.x86_64
CH Connection version: v1.0.0
CentOS Linux release 7.9.2009 (Core)
Setup:

Build docker image following https://help.tableau.com/current/server-linux/en-us/server-in-container_setup-tool.htm

cat customer-files/setup-script
#!/bin/bash

set -ex;

yum install -y wget openssl libicu unixODBC;

# downloaded from https://github.com/ClickHouse/clickhouse-odbc/releases/download/v<IP_ADDRESS>10822/clickhouse-odbc-1.1.10-1.el7.x86_64.rpm
rpm -ivh /docker/customer-files/clickhouse-odbc-1.1.10-1.el7.x86_64.rpm;

mkdir -p /opt/tableau_connectors;

wget https://github.com/Altinity/clickhouse-tableau-connector-odbc/releases/download/v1.0.0-odbc-unicode/clickhouse_odbc_unicode.taco;

cp clickhouse_odbc_unicode.taco /opt/tableau_connectors/.;

Deploy to Kubernetes & restart TS

tsm configuration set -k native_api.connect_plugins_path -v /opt/tableau_connectors
tsm pending-changes apply

After that when I click on "Clickhouse ODBC by Altinity Inc" to connect to data source I get the above error message, so I'm not sure if I'm doing something wrong.
I've checked if the driver is installed in container with:
sh-4.2$ rpm -qa | grep clickhouse
clickhouse-odbc-1.1.10-1.el7.x86_64

So I guess it is properly installed
Thanks for support!

chmod 755 /opt/tableau_connectors/clickhouse_odbc_unicode.taco
?

I also believe that permissions are correctly set:
sh-4.2$ ls -la
total 28
drwxr-xr-x 2 root root  4096 Feb 23 10:41 .
drwxr-xr-x 1 root root  4096 Feb 23 10:41 ..
-rwxr-xr-x 1 root root 17928 Feb 23 10:41 clickhouse_odbc_unicode.taco

sh-4.2$ ls -la /usr/local/lib64/
total 125552
drwxr-xr-x 1 root root     4096 Feb 23 10:41 .
drwxr-xr-x 1 root root     4096 Aug 22  2021 ..
-rwxr-xr-x 1 root root 64276760 Aug 22  2021 libclickhouseodbc.so
-rwxr-xr-x 1 root root 64271632 Aug 22  2021 libclickhouseodbcw.so

To test that the ODBC driver installation is correct, try using isql to execute a simple query (after definding a driver and DSN sections as described in https://github.com/ClickHouse/clickhouse-odbc#configuration).
For resolving issues with the connector, please ask in https://github.com/Altinity/clickhouse-tableau-connector-odbc/issues

Hi @traceon thanks for input. I've managed to succeded connection to Clickhouse following this steps:
https://github.com/ClickHouse/clickhouse-odbc#configuration-unixodbc
In short, I was missing this in as a last step in setup script:
cat <<EOT >> /etc/odbcinst.ini
# Insert the content of this file into ~/.odbcinst.ini or /etc/odbcinst.ini files,
# and fix the absolute paths to libclickhouseodbc.so and libclickhouseodbcw.so files.

[ODBC Drivers]
ClickHouse ODBC Driver (ANSI)    = Installed
ClickHouse ODBC Driver (Unicode) = Installed

Trace=yes
TraceFile=/docker/user/clickhouse-odbc.log

[ClickHouse ODBC Driver (ANSI)]
Description = ODBC Driver (ANSI) for ClickHouse
Driver      = /usr/local/lib64/libclickhouseodbc.so
Setup       = /usr/local/lib64/libclickhouseodbc.so
UsageCount  = 1

[ClickHouse ODBC Driver (Unicode)]
Description = ODBC Driver (Unicode) for ClickHouse
Driver      = /usr/local/lib64/libclickhouseodbcw.so
Setup       = /usr/local/lib64/libclickhouseodbcw.so
UsageCount  = 1
EOT

cat <<EOT >> /etc/odbc.ini
# Insert the content of this file into ~/.odbc.ini or /etc/odbc.ini files.

[ODBC Data Sources]
ClickHouse DSN (ANSI)    = ClickHouse ODBC Driver (ANSI)
ClickHouse DSN (Unicode) = ClickHouse ODBC Driver (Unicode)

[ClickHouse DSN (ANSI)]
Driver      = ClickHouse ODBC Driver (ANSI)
Description = DSN (localhost) for ClickHouse ODBC Driver (ANSI)

### New all-in one way to specify connection with [optional] settings:
# Url = https://default:password@localhost:8443/query?database=default&max_result_bytes=4000000&buffer_size=3000000

# ...or minimal (will connect to port 8443 if protocol is "https://" or 8123 if it is "http://"):
# Url = https://localhost

### Old way:
# Server = localhost
# Database = default
# UID = default
# PWD = password
# Port = 8123
# Proto = http

# Timeout for http queries to ClickHouse server (default is 30 seconds)
# Timeout=60

# SSLMode:
#   allow   - ignore self-signed and bad certificates
#   require - check certificates (and fail connection if something wrong)
# SSLMode = require
# PrivateKeyFile =
# CertificateFile =
# CALocation =

DriverLog = yes
DriverLogFile = /tmp/chlickhouse-odbc-driver.log

[ClickHouse DSN (Unicode)]
Driver      = ClickHouse ODBC Driver (Unicode)
Description = DSN (localhost) for ClickHouse ODBC Driver (Unicode)
# ...
EOT


Swagger: The Request body includes the header Parameters

Hi sir,
I add [FromHeader] attribute on some property in the Request class.
But in the swagger document, the request body json includes the header Parameters.
How can i remove them? I want to show only the  json of request body.
Thank you!

as of v3.11 if you have the following request dto, then you get the swagger ui shown below:
public class Request
{
    [FromHeader]
    public int FrmHdr { get; set; }

    public string FromBody { get; set; }
}

i think you just need to upgrade to the latest version.
if that doesn't work, pls show me how to replicate the issue so i can debug.

Thank you for response.
I've updated to the latest version, but I have a new question.
The [FromHeader] works like you say in swagger document, but I need that every requests have the same header parameters
So I create a BaseHeader Class. All property in the class has [FromHeader] attribute.
When my request class inherit the BaseHeader class, the swagger doesn't work, it show all propertys in request body includes header params again.
How can I solve this or I have to write the same paramerter in all Request class?
Thank you advance!

for that i need to make a small modification to the swagger code. will do that as soon as i can.
hopefully can do a beta release by tomorrow.

Thank you very much!


Added ifSuccessful and ifUnsuccessful methods to DataTransactionResult

Improves fluency by introducing two handy methods. Just a quality-of-life thing.
ItemStack itemStack = ItemStack.of(ItemTypes.STICK, 1);
itemStack.offer(Keys.AGE, 0).ifSuccessful().orElseThrow(() -> new IllegalStateException("This shouldn't have happened!"));

As an alternative, please also view the previous commit.
I decided to name the method ifSuccessful to be symmetrical with Optional's ifPresent.


Add methods to provide field indices

Closes #960
This change does mean that if you run a new serde_derive with an old serde the build will fail. That seems like an uncommon situation to be stuck in though.

I'd like to update serde_test's Token to be able to store the index, but I'm not sure what the back compat situation is there.

Are there any restrictions that need to be placed on how this is used? In particular, is the following valid and how would Bincode be expected to behave in this case?
rgb.serialize_indexed_field("g", 1, &self.g)?;
rgb.serialize_indexed_field("r", 0, &self.r)?;
rgb.serialize_indexed_field("b", 2, &self.b)?;

https://github.com/serde-rs/serde/issues/960#issuecomment-317225162 proposes a different approach.

Closing in favor of #1022.


Offline Sync for android sdk is not working

Offline Sync for android sdk is not working at all
for server version "azure-mobile-apps": "^2.0.0",
android SDK version com.microsoft.azure:azure-mobile-android:3.3.0@aar

if i run the sync function in main thread it works fine ... but if i run the sync function in background as mentioned in todo sample app, it does not work at all. As threads stuck in waiting. I tried todo sample app.. it does not work even.. if sync is made to run in background

Hi @Navpreet2289
Sorry for the long delay.
I've tested this functionality and found no problem with it.
Please double check that you complete all the setup steps.
Setup tutorials:

Enable offline sync for your Android mobile app
Create an Android app

Feel free to ask additional questions.

@Navpreet2289 We haven't heard back from you. I'm closing the issue for now but please feel free to reach out to us if you have any questions. Thanks!


Blendshapes aren't cleared from MeshInstance3D when mesh is changed.

Tested versions
Reproducible:

v4.4.dev2.official [97ef3c837]
v4.3.stable.official [77dcf97d8]
...Likely earlier too.

System information
Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 4090 (NVIDIA; <IP_ADDRESS>99) - AMD Ryzen 9 7950X 16-Core Processor (32 Threads)
Issue description
When changing MeshInstance3D mesh without clearing it first, the blendshapes of the previous mesh remain.
Before:

After changing:

Thus some errors are spammed:

scene/3d/mesh_instance_3d.cpp:158 - Index p_blend_shape = 0 is out of bounds ((int)blend_shape_tracks.size() = 0).

Edit: As I'm writing this I realized I Forgot to test what happens when mesh is changed to an another with blendshapes will report shortly.
Edit2: As expected changing to an another mesh with blendshapes doesn't work either, the blendshapes of the previous mesh remain.
Steps to reproduce
Create MeshInstance3D, attach a mesh with blendshapes to it, change the mesh to an another (without clearing the mesh property).
Minimal reproduction project (MRP)
meshswapissue.zip

I can confirm this works on the latest (2c136e6170a40f58f2dfb89d32eadfca7156ef37) commit on master.
I'd be interested in taking a look at it, but this would be my first PR/triage. I'll probably work pretty close with the devs in the Godot chat.
Let me know if that sounds alright!

https://github.com/godotengine/godot/blob/2c136e6170a40f58f2dfb89d32eadfca7156ef37/scene/3d/mesh_instance_3d.cpp#L125-L127
Likely enough to move those two out of else, before the if, but do test.
Creating a pr-guide: https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html

That's where I was looking and seems to have fixed it! (for meshes with no blendshapes, and with different blendshapes...)
PR submitted (#96894)
Thanks!

getting this too...


Cleanup on store delete

Status
READY
JIRA Ticket
SPACON-384
Description
Remove all data files associated with store
Todos

[ ] Tests
[ ] Documentation
[ ] License

Steps to Test or Reproduce
Outline the steps to test or reproduce the PR here.
git fetch --all
git checkout <feature_branch>
xctool -workspace SpatialConnect.xcworkspace -scheme SpatialConnect -sdk iphonesimulator -destination 'platform=iOS Simulator,name=iPhone 6 Plus' ONLY_ACTIVE_ARCH=NO test

@boundlessgeo/spatial-connect

👍


create different categories #2

Created a 'Contents' section to create a list of all contents of README.md
Categorized all Examples on the basis of the popular keyword used to describe it.

Good Job @adityathakurxd . Just one thing that you must remember that always create a branch whenever you do some changes. As I can see that you have used your master branch to make this PR, it's not a good practice. overall your work is appreciable. Keep It up.

Thank you Sir. I'll keep it mind always to create a branch. Thank you for this amazing opportunity.