[android] Inspecting nested text element throws "Expected to find at least one React renderer."

React Native version:
  React Native Environment Info:
    System:
      OS: macOS 10.14.4
      CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
      Memory: 67.12 MB / 16.00 GB
      Shell: 5.6.2 - /usr/local/bin/zsh
    Binaries:
      Node: 10.11.0 - ~/.nvm/versions/node/v10.11.0/bin/node
      Yarn: 1.15.2 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v10.11.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
      Android SDK:
        API Levels: 21, 22, 23, 24, 25, 26, 27, 28
        Build Tools: 23.0.1, 26.0.1, 26.0.3, 27.0.3, 28.0.2, 28.0.3
        System Images: android-19 | Google APIs Intel x86 Atom, android-21 | Google APIs Intel x86 Atom, android-22 | Google APIs Intel x86 Atom, android-27 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842
      Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.3 => 16.8.3
      react-native: 0.59.8 => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-create-library: 3.1.2

Steps To Reproduce

Run a React Native application on Android
Toggle Inspector
Tap on a nested text
Error is shown ⬇

Describe what you expected to happen
Nested text is being inspected. No error is thrown.
Snack, code example, or link to a repository
A basic RN application with nested text: https://github.com/sjchmiela/nested-text-inspector
Possibly related issues
https://github.com/facebook/react-devtools/issues/1032, https://github.com/facebook/react-native/issues/19782
Short investigation
InspectorOverlay, when tapped, finds the view tag of the tapped element using UIManager.findSubviewIn. This method finds native view tag for native ReactTextView properly and then TouchTargetHelper uses public int reactTagForTouch (from ReactCompoundView interface) to find a React tag for that specific touch (it finds it successfully).
https://github.com/facebook/react-native/blob/01abcf0e83fe58757661dcf6cfc0c2843fed570d/Libraries/Inspector/InspectorOverlay.js#L35-L48
Then, this tag is fed into NativeViewHierarchyManager.measure, which cannot find view for this tag, since this tag represents a ReactVirtualTextShadowNode, which is a virtual view and thus can't be found in mTagsForViews of NVHM.
https://github.com/facebook/react-native/blob/01abcf0e83fe58757661dcf6cfc0c2843fed570d/ReactAndroid/src/main/java/com/facebook/react/uimanager/UIViewOperationQueue.java#L484-L496
NoSuchNativeViewException is thrown, FindTargetForTouchOperation catches it, calls the original callback with undefined, with which Inspector.onTouchViewTag is called.
https://github.com/facebook/react-native/blob/01abcf0e83fe58757661dcf6cfc0c2843fed570d/Libraries/Inspector/Inspector.js#L179-L185
This function in turn calls getInspectorDataForViewTag(tag), i. e. getInspectorDataForViewTag(undefined), which throws an error since it can't find inspector data for undefined tag.
https://github.com/facebook/react-native/blob/01abcf0e83fe58757661dcf6cfc0c2843fed570d/Libraries/Inspector/Inspector.js#L47-L63

Same issue. Also related to a View containing a Text. Very frustrating.


Modal message box when Auto Attach failed because process was terminated

1.22 insiders on Mac. Testing #46570.

Enable Auto Attach
Launch Node (v7.10.1) in debug mode: node --inspect hello.js with:

setInterval(() => {
    console.log('hi!');
}, 1000);

Quickly Ctrl+C the Node process
After a while the below message is shown.

It would be better to detect that the process is gone before showing an error message for expected behavior.

node --inspect=foo hello.js also triggers that dialog. It would make sense to not show the dialog in this case either. The user might simply have a typo on the command line and Node will complain and refuse to start.

Since the August 2018 release unsuccessful auto attach attempts are no longer shown.


FindInBatches does not work on []map[string]interface{} objects

GORM Playground Link

https://github.com/go-gorm/playground/pull/422
Description
Originally encountered such misfunctionality using Postgres. But playground showed that it is not a db dependent issue.
I had such case:
Given we have N rows in a DB.
We need to select those object rows in batches using undeclared struct by passing []map[string]interface{} to FindInBatches() function signature.
Expect: rows correctly scanned and mapped in []map[string]interface{}
Received: error "model value required"

hello, FindInBatches  need  use primaryKey sort . if only use Table(), it can't sort, so return err model value required.

you can use find to instead it.

ok, got it, sadly that it is not working out of the box, but anyway, thanks for a response!


New Website Logo: iPushPull

Please fill the following out:

Name: iPushPull
Homepage url: https://www.ipushpull.com
Brand Guidelines/Licensing: Nothing special
Logo: https://ipp-eu-prod-1-4.s3.amazonaws.com/static/folder_assets/1/ipushpull-logo-xxl-transparent.png

Hi, we are using TypeScript for new version of our API as well as with Angular front-end. Would love to be mentioned.

Logo uploaded, should be out in the next site refresh.

@mhegazy Thank  you, and we will keep reporting issues and suggestions and try to improve TS more and more :)

@mhegazy Hi there, not sure if this the best place, we have just had re-branding recently and would be great if logo could be updated to: https://ipushpull.s3.amazonaws.com/static/prd/ipp-logo.png


Stale resource due to terraform provider upgrade

Hello!
First off, for context:
We've been using terraform in adding the ACLs to our Confluent cloud cluster. This has been working well until just recently when we hit some frequent rate limiting issues, similar to the one described in issue 148. Up until then, we were using the confluentinc/confluent  provider version 1.36.0. As suggested, to resolve the issue we upgraded the provider to version 1.47.0 or higher. And so we did, we upgraded to latest version which is 1.55.0
The issue:
After the upgrade, it seems that records or resources that were added using the old version are not removed properly. I could perform some more tests, but in particular, the resource below are having this problem.
# Added using confluentinc/confluent version 1.36.0

resource "confluent_kafka_acl" "acl" {
  kafka_cluster {
    id = confluent_kafka_cluster.dedicated-cluster.id
  }

  # Set to '*' as this is for Confluent Cloud.
  host = "*"

  resource_type = "TOPIC"
  resource_name = "*"
  pattern_type  = "LITERAL"
  principal     = "User:<service_account_id>"
  operation     = "ALL"
  permission    = "ALLOW"
  rest_endpoint = confluent_kafka_cluster.dedicated-cluster.rest_endpoint

  credentials {
    key    = confluent_api_key.app-manager-kafka-api-key.id
    secret = confluent_api_key.app-manager-kafka-api-key.secret
  }

  depends_on = [confluent_api_key.app-manager-kafka-api-key]
}

# resource_name is changed in confluentinc/confluent version 1.55.0 to 'foobar' from '*'

resource "confluent_kafka_acl" "acl" {
  kafka_cluster {
    id = confluent_kafka_cluster.dedicated-cluster.id
  }

  # Set to '*' as this is for Confluent Cloud.
  host = "*"

  resource_type = "TOPIC"
  resource_name = "foobar"
  pattern_type  = "LITERAL"
  principal     = "User:<service_account_id>"
  operation     = "ALL"
  permission    = "ALLOW"
  rest_endpoint = confluent_kafka_cluster.dedicated-cluster.rest_endpoint

  credentials {
    key    = confluent_api_key.app-manager-kafka-api-key.id
    secret = confluent_api_key.app-manager-kafka-api-key.secret
  }

  depends_on = [confluent_api_key.app-manager-kafka-api-key]
}

Result
The ACL with resource_name foobar has been added but the old one (resource_name *) is still present, despite the terraform stating that it had been destroyed.
Am I missing something obvious here? Should I not upgrade straight to latest version right away after 1.36.0?

Thanks for creating this issue @mihdih!

Should I not upgrade straight to latest version right away after 1.36.0?

That definitely should be fine.
We didn't change much on client but there was a non-breaking API update.
In other words, you're saying that after resource_name was updated, TF tried to recreate a resource (delete old one + create a new one) and the creation went OK but deletion was no-op (TF didn't show any errors but ACL wasn't removed from the backend).

Thank you for a swift response @linouk23 .

Just to confirm my understanding, are you saying that after updating the value for resource_name, Terraform attempted to recreate the resource (by deleting the old one and creating a new one), and while the creation was successful, the deletion was a no-op (Terraform did not show any errors, but the ACL was not removed from the backend)?

That is correct. The delete + create is expected. There was no error upon the deletion, in fact terraform reported back that it was destroyed. I can confirm there after that the ACL (old) still exists. I have checked in both Confluent Cloud UI and via CLI.

Hi @linouk23
I did a little bit of investigation and looks like the problem is when passing the User or principal.
In the old version the account id (integer) is used, while in the new one it's the Service Account resource Id. Please check the sample curl queries below.
Working (replicating the call used in version 1.36.0)
curl -u {api_key} --request DELETE --url https://{confluent_kafka_cluster.dedicated-cluster.rest_endpoint}/kafka/v3/clusters/{confluent_kafka_cluster.dedicated-cluster.id}/acls?host=%2A&operation=ALL&pattern_type=LITERAL&permission=ALLOW&principal=User%3A{service_account_id}resource_name=%2A&resource_type=TOPIC

# Where service_account_id is something like 1978961

NOT Working (replicating the call used in version 1.55.0)
curl -u {api_key} --request DELETE --url https://{confluent_kafka_cluster.dedicated-cluster.rest_endpoint}/kafka/v3/clusters/{confluent_kafka_cluster.dedicated-cluster.id}/acls?host=%2A&operation=ALL&pattern_type=LITERAL&permission=ALLOW&principal=User%3A{service_account_resource_id}resource_name=%2A&resource_type=TOPIC

# Where service_account_resource_id is something like sa-xxxxx

Thank you for performing this investigation!
That was my thinking as well and I’ll reach out to the backend team :saluting_face:


uploader.result.listen call twice

  try {
      final result = await InternetAddress.lookup('google.com');
      if (result.isNotEmpty && result[0].rawAddress.isNotEmpty) {
        final taskId = await uploader.enqueue(
            url:
                'https://xxxx',
            files: files,
            data: {
             ....
            },
            method: UploadMethod.POST,
            showNotification: true,
            tag: title);

        final subscription = uploader.result.listen((result) async {
          print("response " + result.response);
        }, onError: (ex, stacktrace) {
          print(ex.toString());
        });
      }
    } catch (e) {
      ...
    }
  }

When first time I call this,  uploader.result.listen will only print one. But if I call this method again,  uploader.result.listen will call twice. Why?

Do u cancel ur subscription before subscribing again 2nd time? Then you are attaching listener twice. You do not need to call listen twice though

How do I cancel listener?

fixed.

@tony123S how this has to be fixed can you please specify the steps ?

@UzairSun93
dispose it
@override
 void dispose() {
   _subscription.cancel();
   super.dispose();
 }

@tony123S  this isn't enough , my code still call multiple times the same task

@tony123S  this isn't enough , my code still call multiple times the same task

@crsmillan  maybe paste your code?

@crsmillan  maybe paste your code?

@tony123S i'v more than one task, and the result called multiple times for each one  should i cancel each one when i received successful result ??


@instana/collector 1.119.0 does not find module '../../../../../core/src/tracing/cls'

The recently released @instana/collector 1.119.0 does not work for us anymore (1.118.0 did work):
$ npm install --global --only=production<EMAIL_ADDRESS>$ export NODE_PATH=$(npm root --quiet --global)
$ node -e 'require("@instana/collector")'
[...]
Error: Cannot find module '../../../../../core/src/tracing/cls'
Require stack:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>- /tmp/[eval]
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
    at Function.Module._load (internal/modules/cjs/loader.js:725:27)
    at Module.require (internal/modules/cjs/loader.js:952:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at Object.<anonymous> ($HOME/.npm-global/lib/node_modules/@instana/collector/src/tracing/instrumentation/process/childProcess.js:9:13)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Module.require (internal/modules/cjs/loader.js:952:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    '/tmp/[eval]'
  ]
}

Apparently @instana/collector/src/tracing/instrumentation/process/childProcess.js assumes that @instana/core is installed at ../../../../../core instead of simply letting Node.js resolve it using @instana/core/[...].

Apparently @instana/collector/src/tracing/instrumentation/process/childProcess.js assumes that @instana/core is installed at ../../../../../core instead of simply letting Node.js resolve it using @instana/core/[...].

I will take a look. Thanks for the report

Thanks for reporting, @michael42. It also broke my application build and I ended up here and was glad I didn't have to troubleshoot it myself.
@willianpc - what countermeasures are taken to make sure that this kind of failures will be noticed before they make it into a future release? Are additional quality gates needed?
As this has shown, many consumers may flow with the latest patch levels and it'd be good to avoid that they have to spend time debugging an instrumentation library when updating e.g. from 1.118.0 -> 1.119.0 :).

Hi @daka1510 , I am unable to give you exactly what particular counter measures will be taken, but obviously something will be done.
My first guess is that at least adding a new test in the pipeline must be done, but extra checks may become necessary.
The patch is out. Could you folks please check if the problem is gone?

Looks fine on my machine, we'll bump the version in our Docker image soon.

Looks fine on my machine, we'll bump the version in our Docker image soon.

@michael42 great. Can you keep me posted? I will keep the issue opened a little longer, just to be sure.
~ Cheers

Works in our setup, too. Thanks for the quick turnaround @willianpc.

[...] what countermeasures are taken to make sure that this kind of failures will be noticed before they make it into a future release? Are additional quality gates needed?

Looks like we could add https://github.com/sterlingwes/eslint-plugin-monorepo-cop or something similar to be safe from an oversight like this in the future. We'll look into this soon.

For the record: We added the aformentioned rule here: https://github.com/instana/nodejs-sensor/commit/f57c3b8c32dac11c5b1c574c544435510dc7186b.
I'm going ahead and close this one, since it is fixed.


Deployment via Deploy to Azure results in MODULE_NOT_FOUND

Deployed to Azure using the Azure deploy button, which worked flawlessly.
However, the webapp does not boot up, because of an MODULE_NOT_FOUND error:
2023-08-03T08:56:05.959839753Z # Enter the source directory to make sure the script runs where the user expects
2023-08-03T08:56:05.959844653Z cd "/home/site/wwwroot"
2023-08-03T08:56:05.959878853Z
2023-08-03T08:56:05.959885353Z export NODE_PATH=/usr/local/lib/node_modules:$NODE_PATH
2023-08-03T08:56:05.959889553Z if [ -z "$PORT" ]; then
2023-08-03T08:56:05.959893653Z 		export PORT=8080
2023-08-03T08:56:05.959898453Z fi
2023-08-03T08:56:05.959902753Z
2023-08-03T08:56:05.959967353Z PATH="$PATH:/home/site/wwwroot" node server.js
2023-08-03T08:56:06.009684581Z node:internal/modules/cjs/loader:1078
2023-08-03T08:56:06.009740981Z   throw err;
2023-08-03T08:56:06.009745881Z   ^
2023-08-03T08:56:06.009749581Z
2023-08-03T08:56:06.009753381Z Error: Cannot find module '/home/site/wwwroot/server.js'
2023-08-03T08:56:06.009757181Z     at Module._resolveFilename (node:internal/modules/cjs/loader:1075:15)
2023-08-03T08:56:06.009761181Z     at Module._load (node:internal/modules/cjs/loader:920:27)
2023-08-03T08:56:06.009765681Z     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
2023-08-03T08:56:06.009788681Z     at node:internal/main/run_main_module:23:47 {
2023-08-03T08:56:06.009792581Z   code: 'MODULE_NOT_FOUND',
2023-08-03T08:56:06.009795981Z   requireStack: []
2023-08-03T08:56:06.009799181Z }
2023-08-03T08:56:06.009865182Z
2023-08-03T08:56:06.009874782Z Node.js v18.16.0

I got the same error, and seems like the code isn't automatically fetched to the web app with the one click deploy button. This worked for me:
Fork the repository, then add the required Azure secrets to the repository (AZURE_APP_SERVICE_NAME and AZURE_CREDENTIALS). Manually trigger the deploy workflow, then GitHub should deploy the code to Azure and it should boot.

@sophiegonzalez3 AZURE_APP_SERVICE_NAME and AZURE_CREDENTIALS are used in .github/workflows/open-ai-app.yml, so they have to be added as repository secrets.

@sophiegonzalez3 AZURE_APP_SERVICE_NAME and AZURE_CREDENTIALS are used in .github/workflows/open-ai-app.yml, so they have to be added as repository secrets.

@sophiegonzalez3 AZURE_APP_SERVICE_NAME and AZURE_CREDENTIALS are used in .github/workflows/open-ai-app.yml, so they have to be added as repository secrets.

Thank you for updating the documentation and GitHub actions! I've approved and merged it to main!


Save file, after window lose focus.

Hi.
Thanks for plugin.
I need behaviour like vscode or phpstorm, when save works, when window lose focus.
How can i implement this?

Hello! You can configure a set of events which trigger auto-save with g:auto_save_events setting. Look at WinLeave / BufLeave events.

Thansk a lot!!!!!
That solved my problem
let g:auto_save_events = ["FocusLost"]


Velocity estimator is still recommended

Wow, I guess we'd managed to hide this completely for some reason ...


port initialization routines from scarlet1

scarlet1 has very well designed initializations, which we should port as much as possible. In scarlet1, we assumed we took control of the entire source creation and initialized all of its parameters. But the approach of specifying sources is different in scarlet2, where all parameters are exposed to the user:
Source(
        center,
        ArraySpectrum(Parameter(spectrum, constraint=constraints.positive, stepsize=1)),
        ArrayMorphology(Parameter(morph, constraint=constraints.positive, stepsize=1e-1))
    )

We could extend it to something very modular like (following flax/stax style of initialization):
def init_spectrum(obs, center):
    return obs.data[center]

Source(
        center,
        ArraySpectrum(Parameter(None, constraint=constraints.positive, stepsize=1, init_fn=init_spectrum)),
        ArrayMorphology(Parameter(morph, constraint=constraints.positive, stepsize=1e-1))
    )

but then init_spectrum would need to know how to get obs, and center. Much more transparent to the user and enabled by the state-preserving equinox is something like this:
spectrum = init_spectrum(obs, center)
Source(
        center,
        ArraySpectrum(Parameter(spectrum, constraint=constraints.positive, stepsize=1)),
        ArrayMorphology(Parameter(morph, constraint=constraints.positive, stepsize=1e-1))
    )

For the morphology, we would do the same, with the main problem that we don't have a port of the monotonicity operator from scarlet1 (yet). I think we could port if it we don't require it to be jitable.

Working on this slowly, and naively here (https://github.com/pmelchior/scarlet2/blob/initializations/scarlet2/initialization.py)

Can we close this in favor of #33 ?

@SampsonML can we close this issue in favor of #33?

Discussion moved to #47


Use palindrom-dom as the default entry point in Node, do not use the browser field

Right now, the NPM package uses src/palindrom as the main entry point and src/palindrom-dom.js as the browser entry point.
browser is considered legacy and problematic. See:

https://github.com/webpack/webpack/issues/7646 (by @webreflection)
https://github.com/webpack/webpack/issues/4674
https://github.com/gatsbyjs/gatsby/issues/3192

One of the problems is that browser is incompatible with the 3rd alternative entry point module. There is no 4th kind of entry point (module-browser).
Note: this seems to be Webpack's order of preference: browser > module > main.
Several other libraries have also stopped using browser, for example https://github.com/blockstack/blockstack.js/pull/621

WDYT about separating PalindromDom to a separate repo/module? It will make such problems not relevant any more.

Another solution is to keep src/palindrom-dom.js as the entry point, but do not use default exports. Like these guys:

https://humanwhocodes.com/blog/2019/01/stop-using-default-exports-javascript-module/
https://palantir.github.io/tslint/rules/no-default-export/
https://blog.neufund.org/why-we-have-banned-default-exports-and-you-should-do-the-same-d51fdc2cf2ad
https://basarat.gitbooks.io/typescript/docs/tips/defaultIsBad.html

I vote for no "defaults".

Implemented in #261
Released in @6.2.0


Epochs for Azure Connected Mode

Currently Model Builder requests 2 epochs from Azure AutoML.
We should be letting AutoML choose the number of epochs. This lets the intelligence lie within AutoML to train a good model and lets the AutoML team hone the model training overtime.
I expect we can simply not send a value, which will let the defaults of Azure AutoML define the number of epochs. If we need to send a value, 15 is the right answer.
(I pinged folks earlier on internal chat on the same topic)

We do not need to send this parameter, it would default to 15 with early stopping if needed


Beacon : Stability Android,

no beacon after about 3 hours

I am still testing.

i tested after more than 12 hour.. No issue.. Tested once...

Tested 2 hours later with same dApp: pairing not occurring...

also tested with different dapp.. could not pair

tested 12 hours+ later .. altme dapp... sucess
tested 2 hour later... altme dapp.. failed
tested... other dapp... failed
after few minutes... other dapp.... success

Just tested: Success, but took a little bit more time.

it looks ok on build 101


Get unit tests running again in Docker containers

Unit tests were failing after switching the LfMerge build to a Dockerized environment. This PR gets them working again, at least on the FW 9 branch. (A separate PR will be needed for the FW 8 branch, of course).
The main change we had to account for was the change to LfMergeSettings and how it now takes environment variables as settings. The LfMergeSettings test doubles now set the vars they need before calling SetAllMembers().
NOTE: This PR does not run unit tests by default in the build, because they take too long (20+ minutes) to be useful. Instead, I intend to create another PR that divides the tests up into fast and slow tests, then runs the fast tests with every PR and allows us to run the slow tests on-demand.

This change is

This PR's logic was incorporated into https://github.com/sillsdev/LfMerge/pull/284, which has been merged and released. It's no longer needed.


Plugin doesn't work

Unless I misunderstood what it supposed to modify, personal escalators seem to go up and down at the same speed, no matter the multiplier.
Game version <IP_ADDRESS>62 (current test branch)
Plugin installed with Mod Manager. I have a couple other plugins like FastMiner and Duplicationeer installed with the same mod manager and they work flawlessly.
Player.log attached. Not sure if there's anything useful, though.
log.zip

Are you trying to use the escalator mod to speed up elevators?

🤦🏼♂
Yes, that's exactly what I did.
And forgot escalators exists in the first place.
Ok, can this be a feature request, then? :)

Unfortunately the speed of the personal elevator is in native code, so I can't change it.

Thank you and sorry for false reporting a bug.


Investigate how to delete entries from butler.

We have decided not to delete entries from the butler since space usually is not the main issue.


Logs not appearing on GitOps Run session details page when using GitOps Run with a dev HelmRelease

Steps to reproduce:

clone podinfo
change to helm chart dir
gitops run .

Logs did not appear in GitOps Run session details page, error message saying session not found, cluster not found.

Closed and will continue in #3664
cc @katya-makarevich


Extract Table Contents test case

Test case for content extraction completed
Purity, Precision, and Recall assertions currently do not pass since there are issues with the OCR output that will be fixed (along with other bugs/changes) in a pull request later today

Test case for content extraction completed
Purity, Precision, and Recall assertions currently do not pass since there are issues with the OCR output that will be fixed (along with other bugs/changes) in a pull request later today

Looks good in general. I wonder if it might make sense to review this after these other changes have been made?

o

Ping me once that is ready and I'll take another look. Thanks!


Function Expose Codeunit 444.Purchase-Post Prepayments.SumPrepmt function

Hi Guys,
Please Expose the function from Codeunit 444.Purchase-Post Prepayments.SumPrepmt.
thanks!
regards
srinivas

Thank you for your request. We are currently setting up the process around handling of issues in this new GitHub repository and you should hence expect a short delay in the processing of this request. But we will be on your case shortly!

We're happy to inform you, that the requested functions are part of a larger fix pack coming out soon, which aims at exposing safe, public functions in the Base Application. Please expect a resolution to your issue in the coming weeks.

Hi Srinivas
Let me confirm that- your request has been accepted for the next upcoming release.
Best regards.


Support PAC4J security engine

Request details
https://www.pac4j.org:

https://github.com/dzikoysk/reposilite/issues/924
https://github.com/dzikoysk/reposilite/issues/1009

https://github.com/pac4j/javalin-pac4j

Ok, so I've made some research about it and I see some issues related to this topic.
The first one is just the type of authentication form. Currently, Reposilite (and pretty much all microservice-like apps) uses stateless API to communicate between client (e.g. frontend, maven, external apps) and server (one or more instances).

In pac4j it's pretty much represented by direct clients and there are authenticators that works this way:

Speaking of OAuth based services, OIDC and in general all indirect clients:

The indirect mechanism requires session to store authentication related stuff secured:

Because we can't really use session, that's just not an option for us. Of course, the OAuth implementation can expose JWT token and it could be up to the client to properly handle it, but to be honest, what's the benefit of this feature anyway then?
What's the real scenario of using alternative auth method, despite of easier logging to web ui, I guess there is no real benefit of it as it doesn't really work with Maven itself. 🤔

@dzikoysk You could try looking into https://docs.gradle.org/current/userguide/declaring_repositories.html#sub:http-header-auth, since this would allow for PAC4J tokens and credentials to be passed as HTTP headers. This could allow for a custom Gradle plugin that allows for OAuth2-handled Maven publishing!

When we were talking about this feature, Reposilite only had access tokens. In 4.x I'm going to add a regular user system, so it makes sense to provide OAuth - it'll be easier to manage people in the organization. In such case, each user would generate their access tokens in the UI, so I guess it's no longer an issue 😅

When we were talking about this feature, Reposilite only had access tokens. In 4.x I'm going to add a regular user system, so it makes sense to provide OAuth - it'll be easier to manage people in the organization. In such case, each user would generate their access tokens in the UI, so I guess it's no longer an issue 😅

Oh awesome! I still do wonder if with these new user access tokens in 4.x, it would be possible to have a flow where you generate tokens, and then it automatically logs you into any Maven repository provided. Maybe by modifying ~/.gradle/gradle.properties to include the token? Or something more advanced-- not sure


AWS 403 error for prebuilt binaries on node 7.0.0

I am getting this error after upgrading to node 7.0.0:
ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v51-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v51 ABI) (falling back to source compile with node-gyp)

The install works in node 6.9.1.
Tested on Windows 10.

Have the same

me too https://travis-ci.org/thisconnect/nodegit-kit/jobs/173458364 https://github.com/thisconnect/nodegit-kit/issues/19

Nearly the same here, 403ing on ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v45-linux-x64.tar.gz

same here

System: Linux
Node: 7.2.0
Npm: 3.10.10 / Yarn: 0.17.9
Nodegit: 0.16.0
node-pre-gyp ERR! Tried to download(403): https://nodegit.s3.amazonaws.com/nodegit/nodegit/nodegit-v0.16.0-node-v51-linux-x64.tar.gz  node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v51 ABI) (falling back to source compile with node-gyp)
Then it builds successfully and works.

Same here cannot install nodegit because of the missing binaries.

Looks like NodeGit doesn't build on node v7 at all right now. We have to figure out a way to link to OpenSSL better. Fix should be incoming soon. Thanks!

@johnhaley81 ha just hit this myself >_< damn arch linux bumping to 7

Wait, whats the openssl bug?

Yeah, master builds for me on node 7.4 on osx

@maxkorp check latest master, we merged 7.4.0 support ^_^

It's causing problem on alpine linux within a container
exact same cause as : https://github.com/nodegit/nodegit/issues/1039
because it's not using glibc, but musl libc
Would it be possible to do something regarding that?

I'm not sure, but that seems likely.

Thats probably the issue, and it's really probably out of our scope to fix that, unfortunately, unless we wanna custom roll some CI.

Your call :-) But since Alpine kind of became the de facto base image for Docker, you should think about it.
NOTE: It does build from source within the container on 0.16 so it is possible to get 0.17 built within it as well.
I would be happy to be able to help you getting this done. PM me if you are interested.
Thanks for the quick reply!

@cnadeau definitely! i personally don't know how we could support this without bulking up our already large build matrix. if you can find a non-intrusive resolution that would be super ideal :)

I'll see what I can do next week :-)

@tbranyen I have not experience with travis and thought it would not be that complicated, but after reading a bit, aside manually spinning up a container to build it, I don't see a good solution.
My guess would be to define CXX flag to g++ for a new platform
https://github.com/nodegit/nodegit/blob/master/.travis.yml#L49
to get
https://github.com/nodegit/nodegit/blob/master/generate/templates/templates/binding.gyp#L108
used by node-gyp
but again, no travis neither C++ expert.
Any comments/reactions/suggestions are welcomed

The other problem with using a newer gcc is that actually kills a lot of older app builds on LTS ubuntu etc :/

Node 7 is end of life, this issue should be closed.

Yeah we build 6, 8 and 9 now.

I am still getting this error on Node v10.13.0


Recurring Schedule Additions

I have add support for recurring schedules when using MassTransit-Quartz
I know that you have a lot of churn happening for MT3.
I thought this might be useful for the new release.
I have also modified MassTransit-Quartz to support the consumption of the recurring schedule.
I will send a pull request on that project also.  It will require a reference to this compiled branch before it will build.
I hope you can find some of this useful.
There is a gist located here that demonstrates usage
https://gist.github.com/cwooldridge/62c2f9befec2356196c4

Oh, wow, a pull request already to the MT3 branch. Awesome :)

I love the work you’re doing with MT.
I thought you might be able to use some of this, if it aligns with your goals.
From: Chris Patterson<EMAIL_ADDRESS>Sent: Thursday, January 22, 2015 10:34 AM
To: MassTransit/MassTransit
Cc: Chris Wooldridge
Subject: Re: [MassTransit] Recurring Schedule Additions (#265)
Oh, wow, a pull request already to the MT3 branch. Awesome :)
—
Reply to this email directly or view it on GitHubhttps://github.com/MassTransit/MassTransit/pull/265#issuecomment-71049931.

Okay, I think I have this all integration with the latest MT3 branch I'm about to push, thanks for getting it all put together!


Corrected declaration of integer array.

To declare an integer array, the correct way is:
int[] name = new int[] {1, 2, 3};
and not
int[] name = new name[] {1, 2, 3};

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


GENERAL - Database design

Make a database design for our project.

16-12 (AH)
Ik heb op Miro een aantal vragen en comments toegevoegd.

Looks good.
Question on on or many match requests is probably something to discuss as things progress as it'll highly depend on how we choose to implement it.


improve ^F and ^B by handling 'window' and 'wrap' options

Take 'window' option into account when determining how many lines to scroll for ^F and ^B, using the logic described in :help 'window'
Also fix a small bug where ^F and ^B would not scroll the correct number of lines if the 'wrap' option was set and there were wrapped lines visible on the screen
This leaves one small issue unaddressed: in default vim, if you give ^F or ^B a count, and there are wrapped lines in the file, vim will effectively do ^F or ^B multiple times, scrolling a number of lines equal to the number of lines visible after each iteration - 1. This is significant because with 'wrap' set, the number of lines visible at each point in the file might be different, so in default vim, 3^F might not scroll exactly (3 * (line('w$') - line('w0') - 1)) lines like smoothie#backwards() and smoothie#forwards would.

Thanks for your contribution, @misterbuckley! I tested your changes and, unfortunately, found a severe bug in handling Vim folds.
Steps to reproduce:

Open a sufficiently large file (few thousand lines or so)
Create a fold, f.ex. manually with zf1000j
Try to move over folded lines with ^F

Expected result: screen is scrolled about 'window' lines down. When the scrolling animation ends, the cursor is positioned about (1000+'window') lines forward.
Actual result: the cursor is catapulted 2000+ lines forward, far away from its intended position.
I'm not quite sure how to fix this yet.

Note to myself: 'wrap' handling has been fixed via #23, but I'm keeping this one open to investigate whether we could merge the 'window' support bit from here.

Update: closing as after f2aaab110b49da21ab7abf4858173e3194109f6a all wraps should be handled perfectly.


cannot add custom plugin for all apis as global plugin

I try to add these custom plugin as global plugin, but the konga do not have entry for that.
By the way, I can do this with the origin kong admin plugins api.
is there any solution for it?

Hi @CarlZhu93,
As I see in your screenshot the plugins are marked blue, therefore already added.
If I understood correctly, you mean that they are not shown in the plugins list?
Are those plugins listed on the dashboard, inside the plugins panel?

Hi @pantsel ,
Actually, there are two kinds of blue. As you can see, the RequestId Allocation plugin is lighter. What is the different ?
I have used the Plugins Admin api (POST :8001/plugins) to add RequestId Allocation plugins as
global plugin, so in the screenshot, it is global plugin already.
By the way, the plus sign did not appeal throughout for those custom plugins when I try to add them as global plugin, but did appeal when I try to add them for single api.

yes, they are inside the plugins panel.

Hi @CarlZhu93 and sorry for the late response. It seems that the plugins are already added globally. The difference between the blues is that the Request Allocation plugin is not activated while the Signature plugin is.


[Event Hubs] Update Samples and README after proposed API changes are in

This issue is to track the work to update the samples and README to include the new features introduced for the Preview

Current proposal

remove the sample for getHubRuntimeInfo. This api is very clear to use. Its right on the client takes no mandatory arguments. It doesnt add any benefits
Have the below folder structure for new and old versions of the library

samples

v2.0.0
v3.0.0

In 3.0.0, have the counterparts for each sample in v2.0.0.

The folder structure proposal above has been rejected. We will be replacing the existing samples with Track 2 ones. The README at the root and samples folder have been updated to link to older samples in case the user was using the older versions.
What is left is adding a 1 line note to the same affect on all the sample files

Done with #4002


Fix MiVideo course ID conversion bug

Fixes #188.
Because the regex wasn't explicit enough, Kaltura categories with hexadecimal values (e.g., "Canvas_UMich>site>channels>5430bafe907cca901a0f11646470dd64244ebd5f") would have all digits following the first non-integer digit stripped and the remaining ones (i.e., "5430") were incorrectly treated as the Canvas course ID.  The regex now specifically looks for integer digits, optionally followed by ">InContext", and the end of the string.
Review
I humbly request that comments on this PR be nested under a single review per reviewer.  It helps me when the comments are organized this way, especially if the comments request changes in the code.
If I've requested a review from you but you are definitely unable to review this PR, please leave a comment saying so (please state why you're unable to review, that would be appreciated), tell the other reviewers that the review will be left to them, and remove your name from the list of reviewers.
Testing
Ensure that no course IDs less than 99 are saved to the DB and neither should course IDs 551, 3704, or 5430.  All of those were erroneously converted from hexadecimal course IDs.
Deployment
During deployment, to eliminate the erroneous courses from the DB, it's best to completely rebuild the mivideo_media_courses and mivideo_media_created tables.  Drop the contents of those tables and the normal process will automatically fill them in again with data from 01 March 2020 onwards.

Thanks for the approval, @pushyamig.  Merging…


file upload - support array of files and better example / docs

realized after reading this question on stack overflow: https://stackoverflow.com/q/74329125/143475

1.3.1 released


Reinterpret fixed-point number

Is there a way I can reinterpret a fixed point number with different number of fractional bits?
In my use case I'm receiving MyHDL intbv objects which are actually fixed-point values with some fractional bits.  If I create a Fxp object like Fxp(int(x), True, 5, 2) then it will modify the bit pattern. For example say I have 2 fractional bits. if x=0b00010 then x actually represent 0.5.  But if I do Fxp(int(x), True,  5, 2) it will become x=0b01000. Is there a way I can keep x as 0b0010 and just change the number of fractional bits so that it can be interpreted as 0.5 or 2?

Hello @udara28
I think you need to load a raw value in Fxp, or I misunderstood your problem.
If I was right, you can do that as following:
x_fxp = Fxp(int(x), True, 5, 2, raw=True)

or you can assign new raw value after creation:
# x_fxp = Fxp(...)
# ...
x_fxp.set_val(int(x), raw=True)

Please, tell me if it solved in this way

@francof2a thanks for your reply. I think the first method can't work since raw is not a parameter in the Fxp init function. The second method did the trick for me. I didn't notice any mention about the raw parameter in the README. So it would be really helpful if it can be added there. Thanks again for the help and I'm closing this issue.

The first method is going to work because raw is passed as kwarg to the init function.
You're right about documentation. It is not updated. I hope update soon. Thank you!


Application using eye-to-hand calibrated arm.

Thanks for your great work, and we met some problems when applying. We calibrate the arm using eye-to-hand way. Also, we record the tabletop scene including a frame from the fixed camera for calibration. We want to compute the NeRF-to-world json file now. As far as we know, the NeRF-to-world means the transformation from NeRF to robot arm base, and the calibration shows the transformation from fixed camera to base. So we need to compute the transformation from the NeRF to the fixed camera now. And it is provided by running colmap, and showed in the transforms.json and data_paser.json. So we first need to recover the indeed pose of the fixed camera using data_paser.json and compute the transformation from the NeRF to the fixed camera using transforms.json. We wonder if this is the correct way.

Hi, we recently replicated F3RM on a new robot with a wrist camera. Here are the steps we took to calibrate the camera and get it working with pose optimization.

Calibrate the wrist camera (eye-in-hand calibration), this gives cam_to_world.
Scan the scene using the robot, and then run COLMAP to get the transforms.json. For the same trajectory, we create a transforms_gt.json using the calibration from cam_to_world.
Determine the scale, rotation and translation to get the colmap_to_world transform.
Train a NeRF/feature field of the scene. Nerfstudio applies it's own scaling, rotation and translation. This is in dataparser_transforms.json which we can use to construct the nerf_to_colmap transform.

When debugging, you can turn off the scaling, rotation and translation and then slowly turn each on one when you get what you expect.

Use the nerf_to_colmap transform with the pose optimization code.

So in total there are 3 coordinate systems you need to deal with:

World
COLMAP
NeRF

Hope that helps! Let me know if you have any questions.

Here is the hacky script we used for computing colmap_to_world from COLMAP transforms.json and real transforms_gt.json. We do not provide support for this script. Hope it is helpful: https://gist.github.com/williamshen-nz/da87ee47a5fc3b5ebc3e0f7f777d7477
Assuming COLMAP has successfully recovered poses and your original eye-to-hand calibration was accurate, you should get translational errors < 0.01m and rotational errors < 2 degrees.

Thanks for your careful guidance, I got colmap_to_world.json now！ but I still met some problems. I don't know how to calculate nerf_to_world.json from colmap_to_world.json and dataparsere_transform.json. I made a few attempts, but it seems to fail.

Our original calibration pipeline didn't use dataparser_transforms.json as we calibrated end-to-end.
Here is one way of getting things working by disabling the auto-orientation and centering during training while keeping auto pose scaling on. That way the dataparser_transforms.json contains only scaling. Note you should enable centering, so everything fits better in the unit cube. The info below does not do that, but it should be easy to figure out the inverse transformation.

Train with these additional flags --orientation-method none --auto-scale-poses True --center-method none. Example full command:

ns-train f3rm --max-num-iterations $TRAIN_STEPS --output_dir f3rm_outputs --timestamp f3rm \
      --viewer.quit-on-train-completion True --experiment-name $DIR_BASENAME \
      nerfstudio-data --data $SCAN_DIR \
      --orientation-method none --auto-scale-poses True --center-method none

Modify the load.py file where nerf_to_world is loaded. Here's some example code you will likely need to modify:

def load_colmap_to_world(dataset: Path) -> Transform3d:
    col2w_path = dataset / "colmap_to_world.json"
    if not col2w_path.exists():
        raise ValueError(f"Could not find colmap_to_world.json in {dataset}")

    with col2w_path.open("r") as f:
        colmap_to_world_dict = json.load(f)

    colmap_to_world = colmap_to_world_dict["transformation_matrix"]
    colmap_to_world = torch.tensor(colmap_to_world).float()
    assert colmap_to_world.shape == (4, 4), f"Expected colmap_to_world to be 4x4, but got {colmap_to_world.shape}"

    colmap_to_world = Transform3d(matrix=colmap_to_world.T)
    return colmap_to_world

# Load colmap_to_world
colmap_to_world = load_colmap_to_world(dataset=config.data or config.pipeline.datamanager.dataparser.data)

# Load dataparser_transforms
dataparser_transforms = Path(exp_config_path).parent / "dataparser_transforms.json"
if not dataparser_transforms.exists():
    raise FileNotFoundError

with dataparser_transforms.open("r") as f:
    dataparser_transforms = json.load(f)

scale = dataparser_transforms["scale"]
inverse_scale = 1 / scale

scale_matrix = np.eye(4)
scale_matrix[0, 0] = inverse_scale
scale_matrix[1, 1] = inverse_scale
scale_matrix[2, 2] = inverse_scale

# Assumes poses are scaled only
# Not implemented: rotation and translation
inverse_transform = np.eye(4)
nerf_to_colmap = inverse_scale

nerf_to_colmap = torch.tensor(nerf_to_colmap).float()
print("nerf_to_colmap =", nerf_to_colmap)

# Need to take transpose as Transform3d uses row vector convention rather than column
nerf_to_colmap = Transform3d(matrix=nerf_to_colmap.T)
nerf_to_world = nerf_to_colmap.compose(colmap_to_world)

Hello, I am currently facing a problem. I used the multi-view reconstruction method (Dust3R) to obtain point cloud data, but the point cloud data is off by a scale relative to the world coordinate system. The scale information is important for my ultimate goal of using the point cloud for measurement. Is there a way to recover the scale using the method you mentioned, or are there any other solutions?

If you know the camera poses in the world coordinate system, you can compute the scale. Similarly, if you have RGB-D you might be able to compute the scale that best matches the depth image. You will need some way of reference what comes out of Dust3R back to the world frame.

Thank you for your response. Are the camera poses obtained from COLMAP in the world coordinate system? Can the scale be calculated using the camera poses obtained from Dust3R and COLMAP?

maybe this is helpful: https://gist.github.com/williamshen-nz/da87ee47a5fc3b5ebc3e0f7f777d7477

Here is the hacky script we used for computing colmap_to_world from COLMAP transforms.json and real transforms_gt.json. We do not provide support for this script. Hope it is helpful: https://gist.github.com/williamshen-nz/da87ee47a5fc3b5ebc3e0f7f777d7477
Assuming COLMAP has successfully recovered poses and your original eye-to-hand calibration was accurate, you should get translational errors < 0.01m and rotational errors < 2 degrees.

How can I obtain the actual transforms_gt.json file? Thank you for your response.

If you know the camera poses in the world coordinate system, you can compute the scale. Similarly, if you have RGB-D you might be able to compute the scale that best matches the depth image (which you could take from Dust3R or backproject). You will need some way to reference what comes out of Dust3R back to the world frame.

Thank you for your response.How can I recover the scale from depth information if I already have the depth map of an image?

This seems to have been discussed here, hope this is helpful to you

If you want metric scaled exports, you need metric scaled poses. To do this, you need to use RGBD SLAM or some other technique that uses depth data when estimating camera poses. If you have a recent iPhone with a depth sensor (time of flight sensor), you can get metric poses using e.g. https://www.spectacularai.com/mapping or other apps like PolyCam

https://github.com/nerfstudio-project/nerfstudio/issues/2924#issuecomment-1950225312

Thank you for your reply, I understand the problem now. Thanks again.

我们最初的校准管道在进行端到端校准时没有使用 dataparser_transforms.json。
这是通过在训练期间禁用自动方向和居中同时保持自动姿势缩放打开的一种方法。这样 将仅包含缩放。请注意，您应该启用居中，以便所有内容都更适合单位立方体。下面的代码没有这样做，但应该很容易找出逆变换。dataparser_transforms.json

使用这些附加标志进行训练。full 命令示例：--orientation-method none --auto-scale-poses True --center-method none

ns-train f3rm --max-num-iterations $TRAIN_STEPS --output_dir f3rm_outputs --timestamp f3rm \
      --viewer.quit-on-train-completion True --experiment-name $DIR_BASENAME \
      nerfstudio-data --data $SCAN_DIR \
      --orientation-method none --auto-scale-poses True --center-method none

然后，in 中的矩阵应该是恒等式。dataparser_transforms.json

修改 load.py 文件 加载的位置。以下是您可能需要修改的一些示例代码：nerf_to_world

def load_colmap_to_world(dataset: Path) -> Transform3d:
    col2w_path = dataset / "colmap_to_world.json"
    if not col2w_path.exists():
        raise ValueError(f"Could not find colmap_to_world.json in {dataset}")

    with col2w_path.open("r") as f:
        colmap_to_world_dict = json.load(f)

    colmap_to_world = colmap_to_world_dict["transformation_matrix"]
    colmap_to_world = torch.tensor(colmap_to_world).float()
    assert colmap_to_world.shape == (4, 4), f"Expected colmap_to_world to be 4x4, but got {colmap_to_world.shape}"

    colmap_to_world = Transform3d(matrix=colmap_to_world.T)
    return colmap_to_world

# Load colmap_to_world
colmap_to_world = load_colmap_to_world(dataset=config.data or config.pipeline.datamanager.dataparser.data)

# Load dataparser_transforms
dataparser_transforms = Path(exp_config_path).parent / "dataparser_transforms.json"
if not dataparser_transforms.exists():
    raise FileNotFoundError

with dataparser_transforms.open("r") as f:
    dataparser_transforms = json.load(f)

scale = dataparser_transforms["scale"]
inverse_scale = 1 / scale

scale_matrix = np.eye(4)
scale_matrix[0, 0] = inverse_scale
scale_matrix[1, 1] = inverse_scale
scale_matrix[2, 2] = inverse_scale

# Assumes poses are scaled only
# Not implemented: rotation and translation
inverse_transform = np.eye(4)
nerf_to_colmap = inverse_scale

nerf_to_colmap = torch.tensor(nerf_to_colmap).float()
print("nerf_to_colmap =", nerf_to_colmap)

# Need to take transpose as Transform3d uses row vector convention rather than column
nerf_to_colmap = Transform3d(matrix=nerf_to_colmap.T)
nerf_to_world = nerf_to_colmap.compose(colmap_to_world)

如果一切正常，您应该会在查看器中预期的世界坐标系中看到采样的点云。

I apologize for bothering you again. I really want to know how to get the correct nerf_to_world without disabling scaling, rotation, and translation.


Implement a game module for 2D movement/maps

https://github.com/codingchili/chili-game-ext/issues/8


GA4 Session Attribution Report Side-Effects due to Measurement Protocol Messages

Observed that GA4 reports are getting affected by the usage of the Measurement Protocol. When session attribution is done correctly (considering the time window etc.), we don't see bounce/discrepancies in the total number of sessions. However, "(not set)" values in the landing page, traffic acquisition, and user acquisition reports increase significantly.
Experimentation environment: We know that the "(not set)" value increase is also a general GA4 issue. Therefore, I created a copy of the original property and sent MP hits only to a copy test property. Then observed report changes by comparing those two properties.
Experienced that those discrepancies in GA4 happen when Measurement Protocol hits include events, and the guaranteed way to not have those effects is just using the user property. The big downside of this approach is monitoring due to the lack of events, but it is a workaround when the only aim is to generate audiences respectively and not have reports.
Sample MP payload for WEB property:
{
  "client_id": "111111111.2222222",
  "non_personalized_ads": false,
  "consent": {
      "ad_user_data": "GRANTED",
      "ad_personalization": "GRANTED"
  },
  "user_properties": {
      "purchase_propensity_score": {
        "value": "0.78"
      }
  }
}

Also considering trying out an automated GA4 data import pipeline via the SFTP server as an alternative (as long as case is batch prediction and not real time), but I have not tried it yet.

Workaround / fix: https://www.simoahava.com/analytics/session-attribution-with-ga4-measurement-protocol/


Fix old_chat result order

At first, thank you for your developing this awesome tools.
I changed a sort procedure to avoid loading duplicate messages.
Message-ids are returned as string not integer,
then negative operator (to reverse sort) of - i['id'] is not effected.
This modification may resolve issue #22 .
I checked it on Windows7, ruby 2.4.1, and gem 2.6.11.
I am sorry but I am not good at Ruby, so if this modification is not a good Ruby's habit,
please give me some feedback.
Regards,

@thatblue
Thank you for your great PR. I apologize for not getting back to you sooner.
You are correct!
I wanna merge this PR. But circleci's test has not been starting.
Mabye circleci.yml is bad.
I'll merge this PR after I fix circleci.
Thanks!

@thatblue
Please commit empty commit with following command
git commit --allow-empty -m "hook of circleci test"

Thank you for reviewing!
Also I apologize for could not immediately response.
I executed git commit --allow-empty -m "hook of circleci test" and pushed this commit,
I am afraid that is not correct... Please notice if I did wrong operation.

@thatblue
I’m sorry I’m late!
mmm...
I'll merge this PR with other PR!

@thatblue I merged this PR with other PR(#26).
Thank you for your greate PR!!


Enable allow-listing source files in Cobertura generation

Even if we want more expansive coverage recording in general, even at the source level, our Cobertura XML reports will typically need to be scoped to a specific repo.
Allow a separate mechanism for enabling a prefix-based allowlist. Permit the use of multiple prefixes, and do not generate XML for any source files that do not match the prefix.
AB#35930

We now have allow lists that are up-stream from the cobertera generation (which seems appropriate). Closing this work item as implementing this is unnecessary.
@ranweiler FYI.


MultiValued attributes are filtered out if provided one time

introduced when implementing https://github.com/camel-tooling/camel-language-server/pull/58
see https://github.com/camel-tooling/camel-tooling-common/blob/c04c32c1c08dc3ddc951393c456ec23cc93339b1/src/main/java/com/github/cameltooling/model/EndpointOptionModel.java#L30

https://issues.apache.org/jira/browse/CAMEL-9472

those values shouldn't be filtered out. also we should provide a hint to users that he can reference a map entry by adding "name.somePropertyKey".


Implement relabeling on cert-manager ServiceMonitor

Related upstream issue  https://github.com/cert-manager/cert-manager/issues/5215
We need the app label on Prometheus metrics. Current upstream chart does not support relabeling through chart values.

Implemented upstream in https://github.com/cert-manager/cert-manager/pull/6110

Done, but parent issue https://github.com/giantswarm/giantswarm/issues/27557 is blocked


Need to Document Environment Setup

For Homework 1, we need to setup the development environment and document this process.

Documented in environment-setup.md


Add specialized CUDA kernel for fill function

I added  specialized CUDA kernel to avoid ufunc overhead.

jenkins, test this please.

Jenkins CI test (for commit 066fbd7976a46a71fda6cda6129cb0be6ab92d78, target branch master) succeeded!


Implement a Daemon process to take charge of launching Worker processes

Current coverage is 76.61%

Merging #360 into master will increase coverage by +1.14% as of f4862d5

@@            master    #360   diff @@
======================================
  Files           45      45
  Stmts         4673    4673
  Branches       418     416     -2
  Methods
======================================
+ Hit           3527    3580    +53
  Partial        180     180
+ Missed         966     913    -53

Review entire Coverage Diff as of f4862d5

Powered by Codecov. Updated on successful CI builds.

LGTM


remove not used plugin heartbeat.lua

Pre-submission checklist:
Please answer each of these after submitting your pull request:

[x] Did you explain what problem does this PR solve? Or what new features have been added?
#1776 Says that heartbeat is no longer needed, we can remove this.
[x] Have you added corresponding test cases?
Checked that there is not test cases related to heartbeat.
Removing this file does not break existing test suit.
[x] Have you modified the corresponding document?
Link to document including heartbeart.
There are three instances, two of them in the change log, and last one discussing in general service discovery.
No need to modify any one of them.
[x] Is this PR backward compatible?
Not sure how to check this.

@mtx2d please take a look at the output of CI, eg: https://github.com/apache/incubator-apisix/pull/1845/checks?check_run_id=871655239#step:6:272

@mtx2d please take a look at the output of CI, eg: https://github.com/apache/incubator-apisix/pull/1845/checks?check_run_id=871655239#step:6:272

Cannot run the test locally, so running this with CI.
In the meantime, could you please say more on why we no longer need heartbeat?
I can read the test failure and all, but design wise understanding the motivation will help me to create the correct PR.

Trying to figure out how to trigger CI.

@moonming @membphis , is it possible to force trigger a CI?
I made new commit to my local repo mtx2d/incubato-apisix, but the CI still looks at the old states.(my master should be 11 commits ahead but the CI still believes I am only 5 commits ahead).
How can I force trigger a CI?

@moonming @membphis , is it possible to force trigger a CI?
I made new commit to my local repo mtx2d/incubato-apisix, but the CI still looks at the old states.(my master should be 11 commits ahead but the CI still believes I am only 5 commits ahead).
How can I force trigger a CI?

Seems like the CI picks it up now.

The CI fails due to CI server network issue: https://github.com/apache/incubator-apisix/pull/1845/checks?check_run_id=874200614#step:3:68
Will make a small change and trigger another CI run.

According to this doc, we can close and reopen, which will trigger a new CI run without making changes.

Hi @membphis,
Do we think this is PR good to move forward :D?

@mtx2d many thx, merged already


Using deprecated settings in config/helm chart

When running up opendistro-es-1.13.1 with Helm using the chart - I get this output in logs:
│ elasticsearch [2021-03-16T12:08:12,257][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.data] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for th │
│ elasticsearch [2021-03-16T12:08:12,257][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,258][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,258][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,260][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,541][INFO ][o.e.t.TransportService   ] [opendistro-es-master-0] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}                                                                               │
│ elasticsearch [2021-03-16T12:08:12,542][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.data] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for th │
│ elasticsearch [2021-03-16T12:08:12,542][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,542][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,543][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.data] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for th │
│ elasticsearch [2021-03-16T12:08:12,543][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,544][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,544][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,649][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,748][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.data] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for th │
│ elasticsearch [2021-03-16T12:08:12,749][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.ingest] setting was deprecated in Elasticsearch and will be removed in a future release! See the breaking changes documentation for  │
│ elasticsearch [2021-03-16T12:08:12,749][DEPRECATION][o.e.d.c.s.Settings       ] [opendistro-es-master-0] [node.master] setting was deprecated in Elasticsearch and will be removed in a future release! See

chart/docker images - should be updated to not use deprecated config options :)

Thanks @KlavsKlavsen for spotting this issues.
As you might know we have announced OpenSearch the other day.
When we migrate the helm chart there would you mind sending a PR to help fix this?
Thanks.

Gladly. Tell me when you have done so :)


Ghost squadron unimplemeted/not working

Classes not showing in the picker, also.
Log: http://pastebin.com/MN4BrAeg
Version: Snapshot affe5c3

This is because Cardinal does not yet support


snake and ladder

🚀 Problem
Add code for snake and ladder problem
Have you read the Contributing Guidelines on Pull Requests?
yes.
Motivation
Asked in interviews.
Pitch
Given a snake and ladder board of order 5x6, find the minimum number of dice throws required to reach the destination or last cell (30th cell) from source (1st cell).

I would like to work on this problem in CPP language. Could you please assign me?

can you assign me this

i would like to work on this with python please assign this to me

i would like to work on this with python please assign this to me


Another small writer fix

From the commit:
another fix to the writer: the open function only accepts one argument.  How
did this ever work?

Coverage remained the same at 63.13% when pulling bc12dcafbfd249f0b734d71db1d6be7a05105f74 on keflavich:another_writer_fix into 1ed46731eedffcb52910b0574b2a4e7a8cc99a7d on astropy:master.

@keflavich - Thanks!
Merging this now.
I don't know if this was always broken or if a regression happened.
This is for the case of an empty shapelist, so probably very rarely executed by users.
And the whole write method as well as very large parts of pyregion/core.py are not covered by tests:
https://coveralls.io/builds/11110671/source?filename=pyregion%2Fcore.py#L160
Of course more tests would be important / welcome, see #44.


Where the code?

Six month passed, it's still an empty repository

Sorry, This is an abandoned project.


Q: Integrate MetroUI (meta tag)

Hi,
from the MetroUi docs (https://metroui.org.ua/vuejs.html):

Add meta tag of late initialization Metro 4
Initialize Metro 4 in the hook mounted

I have added it to the index.ejs:
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8">
    <meta name="metro4:init" content="false">
    ...

and used the mount-hook to init Metro:
new Vue({
  components: { App },
  router,
  store,
  template: '<App/>',
  mounted: function () {
    Metro.init();
  }
}).$mount('#app');

But this gives me:
[Vue warn]: Error in mounted hook: "ReferenceError: Metro is not defined"
Q: Is it possible to use the meta-tag stuff together with electron/vue?
Thx

@KingKnecht did you import metro? you need to import metro before referencing it.

I think I don't know how to import Metro. I thought the <meta name="metro4:init" content="false"> stuff would import it somehow.
I tried to import Metro directly (something like import Metro from './foo/bar/Metro' ), but I wasn't able to get it work.
I checked the sources of Metro for a file I could import, but without success.

@KingKnecht Try including the metro css and script in index.html in head section before any webpack imports.

Okay, one step done.
I'm able to run the electron-vue-metro combination:

Next problem is, that when I build a setup (exe) it looks like CSS is not included:

How do I include all the stuff needed into my build/setup?
Thx,
Sven

Solved!
Instead of <link rel="stylesheet" href="../node_modules/metro4/build/css/metro-all.min.css">
I imported it like:
@import '../../../node_modules/metro4/build/css/metro-all.min.css';
in the vue component (landing page)
tataa! :-)

@KingKnecht Yep and you can just import them in main.js with
import<EMAIL_ADDRESS>


MINOR: rename optimizer rule to ScalarSubqueryToJoin

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Just renames optimizer rule DecorrelateScalarSubquery to ScalarSubqueryToJoin to more accurately reflect what it's doing. Per request of @avantgardnerio during discussion of #3287.
Are there any user-facing changes?

No

Codecov Report

Merging #3306 (990b191) into master (fcd2275) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #3306   +/-   ##
=======================================
  Coverage   85.74%   85.75%
=======================================
  Files         294      294
  Lines       53738    53749   +11
=======================================
+ Hits        46080    46092   +12
+ Misses       7658     7657    -1

Impacted Files
Coverage Δ

datafusion/core/src/execution/context.rs
78.24% <100.00%> (ø)

...atafusion/optimizer/src/scalar_subquery_to_join.rs
93.07% <100.00%> (ø)

datafusion/optimizer/tests/integration-test.rs
84.00% <100.00%> (ø)

datafusion/expr/src/window_frame.rs
92.43% <0.00%> (-0.85%)
:arrow_down:

datafusion/expr/src/logical_plan/plan.rs
78.73% <0.00%> (ø)

datafusion/common/src/scalar.rs
84.71% <0.00%> (+0.06%)
:arrow_up:

datafusion/proto/src/to_proto.rs
51.07% <0.00%> (+0.08%)
:arrow_up:

datafusion/proto/src/lib.rs
93.52% <0.00%> (+0.11%)
:arrow_up:

datafusion/proto/src/from_proto.rs
35.13% <0.00%> (+0.11%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Statistic nav button shows overlaps with the main Screen's content.

while selecting Statistic from the nav bar. It overlaps with the main content and blocks the main screen's content there is no option to get back . Re-clicking Statistic doesn't  unblock the screen and the content of Statistic still remains there. and result in making the problems for the user.

@Itaachime I would be happy to work on this if I may.

is this issue still persist i would like to work on it
new to open source

hi  i m harshad  i would like to work on this issue , can you suggest me ways to get started?

I have fixed this issue, here it is #97


[Python] Table.to_pandas Can't convert date32 to "datetime64[ns]"

Describe the bug, including details regarding any error messages, version, and platform.
This is a follow up from this issue https://github.com/apache/arrow/issues/37545
I'm trying to convert  arrow data of type pyarrow.date32() to pandas, and would like these date to be converted to datetime64[ns]. To do so I provide a types_mapper argument: {pa.date32(): "datetime64[ns]"}
I've noticed it is work with pa.Array, but not with pa.Table:
import datetime

import pyarrow as pa
import pytest

date_array = pa.array([datetime.date(2023, 1, 1)], pa.date32())

assert (
    date_array.to_pandas(types_mapper={pa.date32(): "datetime64[ns]"}.get).dtype
    == "datetime64[ns]"
)

table = pa.Table.from_arrays([date_array], ["date"])

with pytest.raises(
    ValueError,
    match=r"This column does not support to be converted to a pandas ExtensionArray",
):
    table.to_pandas(
        types_mapper={pa.date32(): "datetime64[ns]"}.get
    ).dtype == "datetime64[ns]"

I'm would expect the behaviour to be consistent between pa.Array and pa.Table. I'm happy to submit an MR to fix the bug if pointed in the right direction.
I'm on

pandas==2.1.2
pyarrow==14.0.1

Component(s)
Python

Hey @0x26res, some late comments on this: your observation is fully correct, and I agree that ideally it would be good to be consistent, but so there is some historical context ;)
First, the types_mapper keyword is actually only (at least originally) meant for pandas ExtensionDtypes (to specify to use an extension dtype instead of the default (typically numpy) dtype that pandas uses for a certain type of data).
So it is not a generic way to specify a target schema (firstly it's per type and not per column, and so you also wouldn't be able to say to convert decimals to float, for example).
And datetime64[ns] is not an pandas extension dtype, but a numpy dtype.
(I suppose this is one of the few cases where this would occur, because in most other cases I can think of, we by default already convert to a numpy dtype, and when you want to do something differently you typically want an extension dtype. In this case the default is the sub-optimal object dtype, and it makes sense you want the numpy option)
Secondly, there is the issue that the types_mapper keyword is handled differently in Table.to_pandas and Array.to_pandas, which leads to some inconsistency in this case.
For Table.to_pandas, we have some preprocessing on the python side to pass down to the C++ ConvertTableToPandas indicating which columns of the table will be converted to extension dtypes, and then those columns are left as-is on the C++ side, and the conversion is done in Python afterwards. This conversion happens at:
https://github.com/apache/arrow/blob/d2209582a0ef81c93342183cab3c12d69e79c5be/python/pyarrow/pandas_compat.py#L723-L733
So this uses the pandas_dtype.__from_arrow__ (a method that only exists pandas ExtensionDtypes, not on numpy dtypes).
The preprocessing that I mentioned happens here:
https://github.com/apache/arrow/blob/d2209582a0ef81c93342183cab3c12d69e79c5be/python/pyarrow/pandas_compat.py#L792-L846
and so essentially that determines which columns of the table should use the above mechanism of using dtype.__from_arrow__ to convert itself, and that is determined based on the pandas metadata, extension types in the arrow schema, and the types_mapper parameter.
But so the fact that we call __from_arrow__ for the types specified in types_mapper explains the error you get:
In [5]: table.to_pandas(types_mapper={pa.date32(): "datetime64[ns]"}.get)
...
ValueError: This column does not support to be converted to a pandas ExtensionArray

(for this case, the error message is not super clear, though, because it's not becauseof the column but because of the specified dtype in types_mapper. This is something that we could improve)
On the other hand, the Array.to_pandas handling of types_mapper is much simpler (and was added later to let it match in functionality compared to the table conversion).
Here, in case of an extension type or types_mapper, we get the pandas dtype and call __from_arrow__ if it has that attribute:
https://github.com/apache/arrow/blob/d2209582a0ef81c93342183cab3c12d69e79c5be/python/pyarrow/array.pxi#L1790-L1804
but then later in that _array_like_to_pandas helper function, after converting the pyarrow array to numpy, we pass that numpy array to the pandas.Series constructor with a dtype specified:
https://github.com/apache/arrow/blob/d2209582a0ef81c93342183cab3c12d69e79c5be/python/pyarrow/array.pxi#L1824-L1834
and because of this passing of the dtype here (also if that comes from types_mapper), your example of using datetime64[ns] in the types_mapper works for the Array case.
But I think that is actually a left-over from https://github.com/apache/arrow/pull/36314 (which added the __from_arrow__ handling in Array.to_pandas), and could/should be removed, if we want to keep the types_mapper functionality strictly for pandas.ExtensionDtype (which would also make the behaviour consistent for both cases, here)

Thanks for the detailed answer @jorisvandenbossche
I'm wondering what can we we do about it. If effectively types_mapper is for extension dtypes only than probably nothing. Excepted possibly a better error message.
For context, this issue isn't a blocker for me. I was just trying to avoid having to call .to_pandas(date_as_object=False, coerce_temporal_nanoseconds=True) since upgrading from pyarrow==12 to pyarrow==13. But it's only in the interim since eventually I'd like to use types_mapper=pd.ArrowDtype (but this requires some work on my code base and a few bug fixes in pandas)


StarkNet State

After https://github.com/NethermindEth/juno/pull/483 is merged, we can sync state up to a certain block height on mainnet
2022/12/09 18:55:22 Applied 318f0d5e3ac53f380c5303819e59bba0a0208518e70c2ec41618e572bc6394c => 354abe054baa9807f95c2748a59f3a4829602ba746dcbfcfa68ca1480d7f367 4883
2022/12/09 18:55:27 Applied 354abe054baa9807f95c2748a59f3a4829602ba746dcbfcfa68ca1480d7f367 => 1f400b05c9942db7d207321de82e2d038bb8255c106d1a1e36a88981405cf66 4884
2022/12/09 18:55:30 Applied 1f400b05c9942db7d207321de82e2d038bb8255c106d1a1e36a88981405cf66 => 587ff22c6fbe5f3375de1e5b1f34bc0fe113ba62d737ff88b0f881f4e23f795 4885
2022/12/09 18:55:33 mismatched new root

Block 4886 is the height nonces were introduced. So the next step is take nonces in to account when calculating state commitment.


entrypoint and option to choose test command runner for setup.py test

Originally reported by: RonnyPfannschmidt (Bitbucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)

the current mechanism of requiring unittest based tests limits the usage
integrations that use other tools cant easily provide setup.py test without making a strange mess

Bitbucket: https://bitbucket.org/pypa/setuptools/issue/374

I think it makes sense to close this issue now that python setup.py test is deprecated (and users are recommended to use something like tox/nox), right?
If anyone would like to reopen this issue, please feel free to write a new comment with more information or other use cases that we might be missing 😄.


iconic install error

Short description of the problem:
I tried to install iconic on my system and i'm getting this error...see image for error.
Ho do i solve this

Hey thanks for the issue, it looks like a proxy problem with npm: If you are behind a proxy, please make sure that the network 'proxy' config is set properly.  See: 'npm help config'.
Going to close this, but I'd suggest taking a look at the forum: https://forum.ionicframework.com/ if you're still having issues.


Offline applyEdits breaks with "&" in data

When online, edits are applied normally, however in offline mode, if an attribute has an "&" symbol in the data, the JSON breaks before it hits the server.

@flyinb can you please provide a console.log stack trace?

It doesn't produce a console error, the posed JSON data is broken. You can reproduce the error by putting an "&" in an attribute field, going offline (queue edit in offline local database), then going online. The data gets posted, but anywhere there is an "&" symbol, the JSON thinks it's a new posted variable, and not part of a string.

I fixed it by URI encoding
encodeURIComponent(property);
but as i said before, online works fine, it's only offline edits

it has knock on effects (I have to decode via an interceptor)
Uri.UnescapeDataString(HttpUtility.UrlDecode(att.Value.ToString()));
but i shouldn't have to do this!

There is a console error: EDIT REQUEST RESPONSE WAS NOT SUCCESSFUL: {"error":{"code":400,"message":"Cannot perform operation. Invalid operation parameters.","details":["'updates' parameter is invalid","Unterminated string passed in.
This error makes sense because the library doesn't do an encoding when it overrides returning edits after an offline event. Reference OfflineEditAdvanced.js Line 2010
I'll take a stab at adding encoding.

@flyinb this will be fixed in v3.3.0. I'll push the build in just a few minutes. Let me know if you have any other problems with it.

Reference fix: https://github.com/Esri/offline-editor-js/commit/7dee7b03f682dc795b71eff978ff098bcf80b5ee

thanks. :)

arcgis-3.14.min.js:144 Uncaught TypeError: Cannot read property 'setAttribute' of nullb.set @ arcgis-3.14.min.js:144(anonymous function) @ /Scripts/esri/offline-edit-src.js:943transaction.oncomplete @ /Scripts/esri/offline-edit-src.js:2537
/Scripts/esri/offline-edit-src.js:512 All edits done

DIT REQUEST REPONSE WAS NOT SUCCESSFUL: XMLHttpRequest {headers: Object, onreadystatechange: null, readyState: 4, timeout: 15000, withCredentials: false…}headers: Objectonabort: nullonerror: (e)onload: ()onloadend: nullonloadstart: nullonprogress: nullonreadystatechange: nullontimeout: ()open: (type, url, async, user, password)overrideMimeType: (type)readyState: 4response: "{"error":{"code":500,"message":"Unable to complete operation.","details":["No edits ('adds', 'updates' or 'deletes') were specified."]}}"responseText: "{"error":{"code":500,"message":"Unable to complete operation.","details":["No edits ('adds', 'updates' or 'deletes') were specified."]}}"responseType: ""responseURL: "https://gisweb.tauranga.govt.nz/arcgis/rest/services/TreeApp/TreeCapture_AllMaintainenceAreas/FeatureServer/1/applyEdits"responseXML: nullsetRequestHeader: (name, value)status: 200statusText: "OK"timeout: 15000upload: XMLHttpRequestUploadwithCredentials: false__proto__: XMLHttpRequestreq.onload @ /Scripts/esri/offline-edit-src.js:2186
/Scripts/esri/offline-edit-src.js:1782 OfflineFeaturesManager._replayStoredEdits - ERROR!!

What action caused this error? Is there any way to reproduce it?

The error refers to a file named offline-edit-src.js at line 2537. There isn't a file with that name in this repo. Is this a custom file that you created?

What version and which library(s) from this repo are you using?

Please provide a complete copy of both the entire HTTP REQUEST HEADER and the HTTP RESPONSE. You can get this info from Chrome Developer tools in the Network tab or by using a debug proxy such as Charles, Fiddler or WireShark. A 500 error is an error in the server logic and may have nothing to do with the client app.

Here's an example of what I need:
REQUEST HEADER

HTTP RESPONSE
{"addResults":[],"updateResults":[{"objectId":20762,"globalId":null,"success":true}],"deleteResults":[]}

Dang, it appears the previous dev has made his own Angular version of your offline-edit script.
Our bad, sorry.

Ah, oops. I'll disregard unless you find something specific to the main library.


ENH: add NaiveRatioUniforms from UNU.RAN to scipy.stats

Reference issue
gh-14600
What does this implement/fix?
add NaiveRatioUniforms from UNU.RAN
this will replace stats.rvs_ratio_uniforms (a separate PR to deprecate that function will be submitted once this PR is merged)
Additional information
In line with stats.rvs_ratio_uniforms, the bounding rectangle has to be specified. One could make it optional and then UNU.RAN would try to find the boundaries numerically. I think it is better to ask users to compute the boundaries using scipy.optimize outside of this method to keep the interface simpler (for example, mode is not needed) and avoid additional test cases.
The tutorial still needs a bit more work: I will demonstrate how to use r and a mode shift (parameter center). The related test cases are already implemented, so I mainly need to explain the approach.

[x] update tutorial
[x] add benchmarks

Some general feedback on the approach that @tirthasheshpatel  implemented to wrap UNU.RAN: I found it very easy to use. Especially the functionality in test_sampling.py is very nice, e.g., to check invalid PDFs, domains etc

One small tweak of the benchmark code is needed. Lint failures in the files to generate the plots are easy to fix. I hope the rest is in good shape.
@tirthasheshpatel could you take a look at the PR when you have time?

There is a significant difference between the performance of NaiveRatioUniforms and rvs_ratio_uniforms:
In [1]: from scipy.stats import NaiveRatioUniforms, rvs_ratio_uniforms

In [2]: import numpy as np

In [3]: from math import exp

In [4]: class StandardNormal:
   ...:     def pdf(self, x):
   ...:         return exp(-0.5 * x*x)
   ...:

In [5]: dist = StandardNormal()

In [6]: from math import sqrt

In [7]: u_bound = sqrt(dist.pdf(sqrt(2))) * sqrt(2)
   ...: v_max = sqrt(dist.pdf(0))

In [8]: urng = np.random.default_rng()

In [9]: rng = NaiveRatioUniforms(dist, center=0, r=1, u_min=-u_bound, u_max=u_bound, v_max=v_max, random_state=urng)

In [10]: %timeit rng.rvs(100_000)
121 ms ± 4.88 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [11]: class StandardNormal:
    ...:     def pdf(self, x):
    ...:         return np.exp(-0.5 * x*x)
    ...:

In [12]: dist = StandardNormal()

In [13]: %timeit rvs_ratio_uniforms(dist.pdf, vmin=-u_bound, vmax=u_bound, umax=v_max, size=100_000, random_state=urng)
20 ms ± 1.2 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)

In [14]:

UNU.RAN uses the same algorithm as rvs_ratio_uniforms to generate RVs. I think the slowdown is because NaiveRatioUniforms doesn't call the PDF in a vectorized manner like rvs_ratio_uniforms does. This makes me think if we should deprecate rvs_ratio_uniforms. Do you think this method is worth deprecating rvs_ratio_uniforms? Or should we keep both? If not, we could change rvs_ratio_uniforms into a class with a rvs method instead of using UNU.RAN. What do you think?

I think the slowdown is because NaiveRatioUniforms doesn't call the PDF in a vectorized manner like rvs_ratio_uniforms does.

Yes, I also noted the relatively slow performance in the CI benchmark. At this point, we cannot do much about it. Support of  LowLevelCallable should fix this. For now, it probably makes sense to mention the performance issue in the documentation and to keep rvs_ratio_uniforms.

I suppose if we're going to have keyword-only args, I wonder why any of the optional parameters deserve to allow positional args. If it's already been discussed, never mind.

The idea was that center belongs to the distribution. The keyword only args belong to the generation method (in this sense, even domain belongs rather to the method since it can be changed to generated truncated variables of the same distribution). But maybe that is indeed not the right way. Tirth and I spoke about it yesterday and we thought it might be better to follow your suggestion.

Does set_random_state work the same way as creating a new NaiveRatioUniforms with the same parameters and the new random_state, or is there a difference between that and only setting the random_state used by rvs?

Yes, set_random_state works the same way as creating a new NaiveRatioUniforms with the same parameters and the new random_state. A random_state keyword in the rvs method has been introduced in gh-14703 for backward-compatibility reasons.  The current behavior is: If the user provides a non-none random_state argument in the rvs method, use that instead of the random_state passed in the constructor or the last call to set_random_state.

I hope I addressed all comments above. The main changes are:

All parameters but dist are keyword only
the parameters u_min, u_max, v_max are optional

I was also thinking to use LaTeX. I ended up sticking to the inline code formatting: note that there are quite a few instances where we refer to parameters like pdf, center or expressions like area. Of course, one can write text in LaTeX, but I thought the benefits are not that strong and with the current version, one can recognize the parameters easily, e.g., in v_max*(u_max - u_min).
What I will definitely do is to get rid of the inconsistencies you pointed out and I think that A, R and (U,V) do not need to be in italics, just normal text should be fine. Would that be OK from your point of view?

What I will definitely do is to get rid of the inconsistencies you pointed out and I think that A, R and (U,V) do not need to be in italics, just normal text should be fine. Would that be OK from your point of view?

That would be very helpful.

That would be very helpful.

Done!

That would be very helpful.

Done!

Thanks, @chrisb83! I think @mdhaber's points have been addressed too. I will take a final look today and merge tomorrow if there are no new/blocking reviews.

Commented on some typos. Everything else looks good!

Thanks for fixing the typos.


minor: release V2.2.19

Codecov Report

Merging #958 (5b4ac1f) into V2.2.X (8308e54) will increase coverage by 1.10%.
The diff coverage is 87.19%.

@@            Coverage Diff             @@
##           V2.2.X     #958      +/-   ##
==========================================
+ Coverage   71.02%   72.12%   +1.10%
==========================================
  Files         294      303       +9
  Lines       21610    22245     +635
==========================================
+ Hits        15348    16044     +696
+ Misses       6262     6201      -61

Impacted Files
Coverage Δ

apps/adapters/__init__.py
100.00% <ø> (ø)

apps/backend/agent/tasks.py
52.05% <ø> (ø)

apps/backend/subscription/commons.py
79.31% <ø> (ø)

apps/backend/subscription/render_functions.py
33.33% <0.00%> (ø)

apps/backend/subscription/steps/agent.py
57.93% <ø> (ø)

apps/backend/subscription/tasks.py
71.74% <ø> (ø)

apps/core/files/base.py
80.00% <ø> (ø)

apps/node_man/handlers/plugin.py
93.03% <ø> (ø)

apps/node_man/views/job.py
80.00% <ø> (+31.11%)
:arrow_up:

apps/node_man/views/password.py
66.66% <0.00%> (ø)

... and 74 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 33e189c...5b4ac1f. Read the comment docs.


Add JUnit test cases for light/dark commands

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.96 :tada:

Comparison is base (7d4ac88) 59.67% compared to head (f614f34) 60.63%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #170      +/-   ##
============================================
+ Coverage     59.67%   60.63%   +0.96%
- Complexity      532      541       +9
============================================
  Files           108      108
  Lines          2073     2073
  Branches        218      218
============================================
+ Hits           1237     1257      +20
+ Misses          755      735      -20
  Partials         81       81

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/DarkCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...ava/seedu/address/logic/commands/LightCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

... and 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Getting module not found for @uuip/unified-ui-platform-sdk when compiling React

Describe the bug
When trying to compile the React project per the readme, getting the following compilation error:
./src/direflow-component/App.tsx
Module not found: Can't resolve '@uuip/unified-ui-platform-sdk' in '/Users/Ed/Dropbox_Personal/Dev/webex-contact-center-widget-starter/react/src/direflow-component'
^CAssertion failed: (0), function uv_close, file ../deps/uv/src/unix/core.c, line 178.
To Reproduce
Steps to reproduce the behavior:

In the react folder, do yarn
Then do yarn start

Expected behavior
The app compiles correctly.

OS: Mac OSX 12.6.5
Node: v16.19.1
Yarn: v1.22.19

I was able to fix this and other compile issues in #98 #98 https://github.com/CiscoDevNet/webex-contact-center-widget-starter/pull/98


Config json is empty

title

try reading the README.md don't open issues for this kind of issues.
After editing config.example.json rename it to config.json.


Refactor reporting module

Refactor generator functions to functions with callbacks in order to free nodejs event loop.
setImmediate execution when processing consumers

Coverage decreased (-0.2%) to 90.698% when pulling<PHONE_NUMBER>8e1e6bc1d94843f9d6744bb7a525f8 on SAP:refactor-reporting into 6d0efed7813a1e0827ab4390998778391aa960bd on cloudfoundry-incubator:master.

Coverage decreased (-0.4%) to 90.489% when pulling 86210d9ff6c73f252253ecfe0bb6f585f8e92e25 on SAP:refactor-reporting into 6d0efed7813a1e0827ab4390998778391aa960bd on cloudfoundry-incubator:master.

Coverage decreased (-0.3%) to 90.583% when pulling fb425295cd6a83c12cae68fc2739c9e9864fcf44 on SAP:refactor-reporting into d3b14cda7ad79fac60e522a1939a4fb4094e8ae6 on cloudfoundry-incubator:master.

Coverage decreased (-0.3%) to 90.583% when pulling 5010897f69ce447f24f8269512ef5dcfcc8fefba on SAP:refactor-reporting into d3b14cda7ad79fac60e522a1939a4fb4094e8ae6 on cloudfoundry-incubator:master.

Coverage decreased (-0.3%) to 90.583% when pulling 5010897f69ce447f24f8269512ef5dcfcc8fefba on SAP:refactor-reporting into d3b14cda7ad79fac60e522a1939a4fb4094e8ae6 on cloudfoundry-incubator:master.

Coverage decreased (-0.3%) to 90.583% when pulling eec82e5f620602f0f27eca5599b8659dee2f05da on SAP:refactor-reporting into d3b14cda7ad79fac60e522a1939a4fb4094e8ae6 on cloudfoundry-incubator:master.


Is there a way to make a part add 2 objects in the metadata?

I have a part of a hair and a hat but the hair passes the hat, I would like to know if there is a way I can make a specific design for that hat with the hair, it would just be an image containing 2 parts of the metadata example:
Hair1 + Hat1 = HAIR1andHAT1

There is no way to do this at this time.
Two or more images can be combined into one "layer" folder and stacked, but both traits would be present separately in the metadata, for example.
hat: "hat 1",
hair: "hair 1"

depending on the need for this kind of solution, altering the metadata after image generation (custom script) would be the easiest approach.


Question on: mothur's wiki

remove.seqs tool in galaxy doesn`t work at all and the jobs failed every time i running the job , please help

Hi - we have no involvement with galaxy so I'm not much help with
navigating their resources. If you have a question with using mothur, could
you post the command you are trying to run and the result including any
error messages to the mothur forum at forum.mothur.org?
Thanks,
Pat
On Mon, Jan 1, 2024 at 10:32 AM Hadeel1353 @.***> wrote:

remove.seqs tool in galaxy doesn`t work at all and the jobs failed every
time i running the job
—
Reply to this email directly, view it on GitHub
https://github.com/mothur/mothur.github.io/issues/123, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUUBAWUDHZO7V2FSHJGP3YMLJHFAVCNFSM6AAAAABBJDMQLWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3DCNRSGM4DSMA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


ARROW-14584: [Python][CI] Python sdist installation fails with latest setuptools 58.5

This patch should go to the 6.0.1 release.

@github-actions crossbow submit python-sdist

@github-actions crossbow submit -g wheel

Hmm, so this doesn't actually help for the sdist installation. That's because it is already failing in the step of installing numpy in the build environment (it is in this environment that we now install setuptools < 58.5).
One other difference I notice compared to a previous nightly build of python-sdist that still worked (https://github.com/ursacomputing/crossbow/runs/4089110526?check_suite_focus=true) is that it now tries to install numpy from source (   "Collecting numpy==1.16.6     Downloading numpy-1.16.6.zip (5.1 MB)"), while previously it didn't do that? And it's this building of numpy from source that now fails with the latest setuptools.

Yes, just looking at why it tries to install numpy from source.

We have pinned that in pyproject.toml:
[build-system]
requires = [
    "cython >= 0.29",
    "numpy==1.16.6; python_version<'3.9'",
    "numpy==1.19.4; python_version=='3.9'",
    "numpy==1.21.3; python_version>'3.9'",
    "setuptools < 58.5",  # ARROW-14584
    "setuptools_scm",
    "wheel"
]

But the fact that the requirement is "numpy>=1.16.6" seems a bit fishy, since the pyproject.toml clearly indicates "==1.16.6".

Could be due to different setuptools versions.
I wonder what's the exact purpose of build-system definition since numpy 1.16.6 doesn't have wheels for python > 3.7 which makes it pretty inconvenient to compile pyarrow from sdist for those python versions.
Perhaps we should change the numpy constraints to use ">=" instead of "=".

@github-actions crossbow submit python-sdist

@github-actions crossbow submit -g wheel

Perhaps we should change the numpy constraints to use ">=" instead of "=". Going to try it.

No, we shouldn't do that. Numpy is only forward compatible on a binary level, so you need to compile against the oldest version (in the build environment it is not known what will be the numpy version at runtime).

I wonder what's the exact purpose of build-system definition since numpy 1.16.6 doesn't have wheels for python > 3.7 which makes it pretty inconvenient to compile pyarrow from sdist for those python versions.

That's because our numpy / python versions are not detailed enough. We should include another entry for Python 3.8 requiring numpy 1.17.3 (which does have wheels for Python 3.8). That might actually fix the issue here.
(and that's another reason for using oldest-supported-numpy, https://github.com/scipy/oldest-supported-numpy)

@github-actions crossbow submit -g wheel python-sdist

that's another reason for using oldest-supported-numpy, https://github.com/scipy/oldest-supported-numpy)

Let's try that out https://github.com/apache/arrow/pull/11606

@github-actions crossbow submit wheel-windows-cp39-amd64

@github-actions crossbow submit wheel-windows-cp310-amd64