Could not find any matches for com.facebook.react:react-native:+ as no versions of com.facebook.react:react-native are available.

New Version
0.71.0, 0.71.0-rc.3 (tried both)
Old Version
0.68.5
Build Target(s)
android development debug
Output of react-native info
System:
OS: macOS 12.6
CPU: (10) arm64 Apple M1 Pro
Memory: 129.95 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.10.0 - /opt/homebrew/bin/node
Yarn: Not Found
npm: 8.19.2 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
Android SDK:
API Levels: 28, 29, 30, 31, 32, 33
Build Tools: 28.0.3, 30.0.2, 31.0.0, 32.0.0, 32.1.0, 33.0.0, 33.0.1
System Images: android-30 | Google Play ARM 64 v8a, android-33 | Google APIs ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9014738
Xcode: 14.1/14B5033e - /usr/bin/xcodebuild
Languages:
Java: <IP_ADDRESS> - /opt/homebrew/opt/openjdk@11/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.0-rc.3 => 0.71.0-rc.3
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Issue and Reproduction Steps
./gradlew installDevelopmentDebug
FAILURE: Build failed with an exception.

What went wrong:
Could not determine the dependencies of task ':react-native-linear-gradient:compileDebugAidl'.

Could not resolve all task dependencies for configuration ':react-native-linear-gradient:debugCompileClasspath'.
Could not find any matches for com.facebook.react:react-native:+ as no versions of com.facebook.react:react-native are available.

this error fail for all libraries

react-native: 0.71.0-rc.3 => 0.71.0-rc.3

You say you're on 0.71.0 but your environment info says you're on 0.71.0-rc.3
Can you please confirm on which version are you?
Plus can you provide a reproducer of this bug?

We have the same issue

react-native: 0.71.0-rc.3 => 0.71.0-rc.3

You say you're on 0.71.0 but your environment info says you're on 0.71.0-rc.3 Can you please confirm on which version are you? Plus can you provide a reproducer of this bug?

sorry. same issue on 0.71.0 and 0.71.0-rc.3
I have tried both

I'm looking for a repro at this stage as I can't help further

same issues on my side

Hello,
I ran into the same issue after upgrading to RN 0.71 and I found a workaround that worked for me:

Open android/app/build.gradle BE CAREFUL IT'S NOT android/build.gradle!!!
Add apply plugin: "com.facebook.react" like this:

 apply plugin: "com.android.application"
+apply plugin: "com.facebook.react"

 import com.android.build.OutputFile
 ...

Rebuild your application, it should works

However, this warning (shown when building) makes me feel this will break soon...
##############################

Using react.gradle in your project is deprecated! You should move to "apply plugin: com.facebook.react"
react.gradle is going to be removed in a future React Native project and your project will not build anymore.
You can use the template as a reference:
https://github.com/facebook/react-native/blob/main/template/android/app/build.gradle

##############################

Maybe we can completely replace the android/app/build.gradle file by this one, I didn't tested it because...

However, this warning (shown when building) makes me feel this will break soon...

The warning is there because you're still importing react.gradle which you should not.
If you follow the upgrade helper you'll see that you have to use apply plugin: com.facebook.react

@cortinico I'm hitting a similar issue although probably not the same (message slightly different).
However my question applies to both. Is there a way of getting the build to expand out what the dependency graph can see and the places it does check? Surely that would mean individuals can help narrow the problem themselves in the future?

I found a thread to pull on at least. I think this hint should be in the error message as it isn't obvious:
https://stackoverflow.com/questions/42596358/how-to-enable-stacktrace-react-native-run-android-command

@cortinico I'm hitting a similar issue although probably not the same (message slightly different).

@dmg46664 then please open a separate issue, share a reproducer and your environment. This issue is pending feedback from @yanel777. You can get an overview of your dependency tree if you run cd android && ./gradlew :app:assembleDebug --scan and check the Gradle Scan that gets produced.

https://react-native-community.github.io/upgrade-helper/?from=0.68.5&to=0.71.0

Update the package.json and app/build.gradle file according to the changes

I have same error with react native v0.69.6

I also facing same issue, but for my case I think it's because this library react-native-mmkv-storage
Error:
* What went wrong:
Could not determine the dependencies of task ':app:processDebugResources'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not find any matches for com.facebook.react:react-android:+ as no versions of com.facebook.react:react-android are available.
     Searched in the following locations:
       - file:/Users/cryptokun/Documents/react-native/MuloApp/node_modules/react-native/android/com/facebook/react/react-android/maven-metadata.xml
       - file:/Users/cryptokun/Documents/react-native/MuloApp/node_modules/jsc-android/dist/com/facebook/react/react-android/maven-metadata.xml
       - https://dl.google.com/dl/android/maven2/com/facebook/react/react-android/maven-metadata.xml
       - https://www.jitpack.io/com/facebook/react/react-android/maven-metadata.xml
     Required by:
         project :app > project :react-native-mmkv-storage

I also facing same issue, but for my case I think it's because this library react-native-mmkv-storage

Closing as this kind of issues are related to specific libraries. You can find which library is causing the issue in the error message like here:

 Required by:
    project :app > project :react-native-mmkv-storage

Please re-open if you believe this is a bug in React Native core.

@DeVoresyah I am facing the same issue, did you end up finding up a solution?

@DeVoresyah I am facing the same issue, did you end up finding up a solution?

yes by upgrading the react-native version into 0.71.6

I also facing same issue, but for my case I think it's because this library react-native-mmkv-storage
Error:
* What went wrong:
Could not determine the dependencies of task ':app:processDebugResources'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not find any matches for com.facebook.react:react-android:+ as no versions of com.facebook.react:react-android are available.
     Searched in the following locations:
       - file:/Users/cryptokun/Documents/react-native/MuloApp/node_modules/react-native/android/com/facebook/react/react-android/maven-metadata.xml
       - file:/Users/cryptokun/Documents/react-native/MuloApp/node_modules/jsc-android/dist/com/facebook/react/react-android/maven-metadata.xml
       - https://dl.google.com/dl/android/maven2/com/facebook/react/react-android/maven-metadata.xml
       - https://www.jitpack.io/com/facebook/react/react-android/maven-metadata.xml
     Required by:
         project :app > project :react-native-mmkv-storage

I just faced the same issues,
it turns out React Native MMKV Storage > 2.5.1 isn't compatible with React Native below 0.71
Checkout the breaking changes: https://github.com/mrousavy/react-native-mmkv/releases

I have also faced the same problem
react-native: 0.71.8
and I have added apply plugin: "com.facebook.react" to app/build.gradle
and getting this error:
* What went wrong:
A problem occurred evaluating project ':app'.
> Plugin with id 'com.facebook.react' not found.

I have also faced the same problem react-native: 0.71.8 and I have added apply plugin: "com.facebook.react" to app/build.gradle and getting this error:
* What went wrong:
A problem occurred evaluating project ':app'.
> Plugin with id 'com.facebook.react' not found.

I appreciate any help 🙏

Same happened with me, any updates regarding this?

I'm upgrading from react-native 0.70.0 to 0.71.0.
First I was getting a Could not get unknown property 'hermesEnabled' for project ':app' of type org.gradle.api.Project.
which was 'fixed' adding hermesEnabled=true to gradle.properties.
Then I started seeing the Could not find any matches for com.facebook.react:react-native:+ as no versions of com.facebook.react:react-native are available.
to fix it I added the plugin: "com.facebook.react" to app/build.gradle
What I'm now seeing is this > Plugin with id 'com.facebook.react' not found. which I'm not sure how to fix.

My RN 0.64.3 APP fixed it ref to https://stackoverflow.com/a/76521278/6318705

I'm upgrading from react-native 0.70.0 to 0.71.0.
First I was getting a Could not get unknown property 'hermesEnabled' for project ':app' of type org.gradle.api.Project. which was 'fixed' adding hermesEnabled=true to gradle.properties.
Then I started seeing the Could not find any matches for com.facebook.react:react-native:+ as no versions of com.facebook.react:react-native are available. to fix it I added the plugin: "com.facebook.react" to app/build.gradle
What I'm now seeing is this > Plugin with id 'com.facebook.react' not found. which I'm not sure how to fix.

found any solution for this? facing the same issue

@omri81 try this: https://github.com/facebook/react-native/issues/36234#issuecomment-1439770679. Not sure if that was my solution but it's the closest I can get to whatever worked for me.


add .timecard.json to .gitignore

Adds a new argument append to the CLI for appending .timecard.json to an existing .gitignore file in the current working directory.
The append function is also called during the new process after the .timecard.json was successfully created.

thanks for this -- it's a good idea. I will be away from my computer all day tomorrow, but when I return I will test it out and take a closer look.

Overall, I like the feature, so if you don't mind removing that one console.log() and changing the phrasing a little bit in your messages, I will merge this. Thanks!

Great you like it. I don´t mind changing the what you mentioned. Will get back to it tomorrow.

awesome. thanks! :+1:

I´ve changed the message and removed the console.log for logging the current working directory.

Thanks. I just took a look at the new changes, and I caught a bug. Because the .timecard.json file is already in the .gitignore file by default, if you answer "Yes" to .gitignore found: do you want your timecard to be kept in version control? then you get this message:
GITIGNORE: The .gitignore file already contains .timecard.json. Nothing was appended!
...and it leaves the entry of timecard.json inside the .gitignore file.
Instead, if you answer "Yes" to "do you want timecard under version control?" it should remove .timecard.json from the .gitgignore.

Thanks. I just took a look at the new changes, and I caught a bug. Because the .timecard.json file is already in the .gitignore file by default, if you answer "Yes" to .gitignore found: do you want your timecard to be kept in version control? then you get this message:

GITIGNORE: The .gitignore file already contains .timecard.json. Nothing was appended!

I would say that this behavior is correct. If you answer "Yes" you want to add timecard to .gitignore file.

Instead, if you answer "Yes" to "do you want timecard under version control?" it should remove .timecard.json from the .gitgignore and report something like .timecard.json was removed from your .gitignore file

Here I would suggest: if you answer with "No" and .timecard.json exists in the .gitignore file then the entry should be removed.

I would say that this behavior is correct. If you answer "Yes" you want to add timecard to .gitignore file.

But the question is "do you want the timecard to be under version control?", not "do you want to add 'timecard.json' to the .gitignore file?" these are two different things.
So when someone "YES, I want my timecard under version control", then it means that .timecard.json should not be in the .gitignore file, and therefore removed from the .gitignore file (if it exists).

Sorry mixed up timecard and .timecard.json. Will fix it tomorrow.

Just a heads up: I have added some new changes to this project, so if you decide to do more work on this PR, then please remember to pull in the latest changes. The most significant change has been the addition of XO linting which effects every source code file in the project, and I have set things up to start writing unit tests and added support for travis. Thanks!

As you may have seen, a lot of changes have taken place. I ported the codebase over to ES6 and added unit tests. So you will need to pull in the new changes if you still want to work on this feature. Otherwise, if you don't have the time (or desire) we can close this PR, and open an issue and I can work this feature into the codebase when I get some free time.

I saw your changes. Right now I don´t have time to work on my PR.
Next week there is enough free time to work on it. Hope that´s fine for you.

That works for me. No rush. Thanks!

@mpfeil , if you have time to work on this, I will leave this PR open, otherwise, if you don't have time (or interest) I can close this PR and open an issue to add the feature later on.

The fork for this PR has been deleted, so I am closing this PR due to inactivity. If you want to add the feature later on, you are more than welcome. Thanks.


Support new startAudioOnly and startScreenSharing parameters

In the old version 0.3.x, we have URL parameters novideo and noaudio that were used to start a conference in audio only or video only modes. JitsiMeet now supports two new config parameters startAudioOnly and startScreenSharing which can roughly do the same and more.
We need to add this ability to the current version. In my fork, I do the following:
    if (urlParam("audio_only")) config.startAudioOnly = true;
    if (urlParam("screen_share")) config.startScreenSharing = true;

I don't think we need custom code for this anymore. Jitsi Meet has something pretty similar itself now. I'm working on updating the source, so that we can try it out.

I don't think we need custom code for this anymore
I think we do. The requirement is to allow audio only and screen share only to be initiated from the URL on demand. Quite different from an application wide setting in config.js as implemented by Jitsi Meet. I have applications that depend on this to start an audio-conference instead of a video-conference by the URL

I'm not sure about the screen-share option, but the audio-only mode, as well as 'startWithAudioMuted' and 'startWithVideoMuted' settings can be defined in the config.js (as you describe), but, that configuration can now be overridden by supplying a parameter on the URL. Try, for example: https://beta.meet.jit.si/testroom#config.startWithVideoMuted=true
Isn't that what you're after? If so, then we'd only have to apply a similar fix for screen-share (which might be accepted upstream, too).

Yes. The key feature was being able to override config from the url. Really B-)

https://beta.meet.jit.si/testroom#config.startScreenSharing=true
also works

I've added some admin console configuration for configuring ofmeet to start rooms as audio-only, and to make the number of occupants after which a new occupant starts muted configurable (it was hardcoded now). Strictly speaking, this is unrelated to this issue, but it touches on the same subject. :)


react router added

issue solve-Convert Together to React Router #404

Is this ready for review? I'm hitting compile errors in local and with github tests.

which type of error you get sir ?  please send screenshot

Hey there @mandliyarajendra11 just checking in on this, thanks!

Sorry sir, I forgot. Let me check.


[move-only] Fix two small errors around handling capturing of noncopyable self by local functions

Specifically:

[move-only] Do not try to capture self as an immutable box.

The problem here is that the logic was conditionalized on all noncopyable
parameters that are borrowed as having the ValueOwnership::Shared flag set. This
is only true for user written parameters. Implicit noncopyable parameters like
self do not have ValueOwnership::Shared set upon them. We could potentially do
that in Sema, but Sema does not know what the proper convention of self is since
that information is in TypeLowering today.

With that in mind, conditionalize the logic here so we do the right thing.

rdar://112547982

[move-only] Make sure we mark local function inout parameters with mark_must_check.

Originally, we were relying on capture info to determine if we needed to insert
this mark_must_check. This ignored that the way that we are handling
escaping/non-escaping is something that is approximated in the AST but actually
determined at SIL level. With that in mind, rather than relying on the capture
info here, just rely on us having an inout argument. The later SIL level
checking for inout escapes is able to handle mark_must_check and knows how to
turn off noncopyable errors in the closure where we detect the error to prevent
us from emitting further errors due to the mark_must_check here.

I discovered this while playing with the previous commit.

rdar://112555589

@swift-ci test

The reason why we still don't emit the mark_must_check errors is that the  inout usage by closure pass puts a semantic function on the violating closure that says do not emit move only diagnostics in this function.

@swift-ci test

@swift-ci test


Problem: init and test mini provisioning phases fail

Because of newly added validation checks in init and test sections of Hare mini
provisioner, some conf-store keys are required in init and test sections too.
Present templates for init and test sections do not contain any keys with respect
to this.
Solution:

Update init and test section conf-store templates.
Add more nodes information in 3 node config section template.
Add populated sample conf-store files for config, init and test sections.

Signed-off-by: Mandar Sawant<EMAIL_ADDRESS>

The change is about template files only. Does it mean that somebody already use them for validation? If so, do you think it is possible to introduce the same checks into our tests so that we can be sure that we don't break anything?

I added multiple entries in 3-Node template files just to make it more explicit to provisioner as they will be using it populate. But I think we can maintain the template as per storage set size and need include all the all the nodes in the cluster. Having said that, for larger clusters it is good to get it clarified from provisioning team what they really expect from the template.
I think we can add some test cases for multi-node storage-set, e.g. validating the server_node count vs the layout params or actuall number of nodes.

SOME_MACHINE_ID is replaced with SERVER_NODE_{0,1,2}_MACHINE_ID. Does the new name follow some requirement from CI? Can we see the set of conventions and requirements to templates then?

No, even I don't see any specific conventions as such. From conf-store keys it seems to be some UUID. I don't see any specific requirements from CI.

You added .sample files as well. How they differ from .tmpl ones? I just wonder how to maintain so many files properly...

Sample files are just a populated version of .tmpl files. I used them for my testing. Thought they would be a good reference to QA or anyone who wants to test by replacing hostnames and machine-ids as required. Yes, maintenance will be a nightmare but that is an accepted truth nowadays, no? ;)


CLASP RUN PRODUCES ERRORS

(Please search existing issues before creating a new one.)
Expected Behavior
A simple function should run to add text to a cell in a Google Spreadsheet
Actual Behavior
errors
Steps to Reproduce the Problem

clasp create [name]
clasp clone [ScriptId] (This is to download the Code.js)
add following code to Code.js by VIM editor:

function myFunction() {
SpreadsheetApp.openById('1acJRcIGXIYa9YNgO8g3DTrgFRO6Iqk0wNJoxYpsust8').getRange('A1').setValue('set');
}

save and close (in VIM = :x )
clasp push (make sure everything is the same)
clasp run myFunction

Specifications
I am using the GCP with a VM instance with Ubuntu 18 (up to date) with Node 10.2 and<EMAIL_ADDRESS>The errors are in the document attached. I tried the script in a normal manner after clasp open and it worked, so something is off with the clasp run. Maybe something with permissions?
errorclasp.txt

@campionfellin Can you look at this?
It looks like we need to document run a bit better.

Yep, I'll take a look in a little bit.

So after some investigation this is what I've found:
If you follow the instructions in this PR: https://github.com/google/clasp/pull/172 you should be able to use clasp run for simple functions that don't need extra scoping access.
More complex functions (like yours, requiring access to Sheets) are not yet supported by clasp (yet 😉). By following the instructions outlined in the above PR, you should get a response like:
  code: 401,
  errors:
   [ { message: 'Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.',
       domain: 'global',
       reason: 'unauthorized' } ] }

Which indicates that you don't have authorization. Of course this makes sense, because when we logged in we didn't give it the right scopes (for Sheets). Go here: https://github.com/google/clasp/blob/8e1c3fbeca11e06d22554b183b5d43d1c8490808/src/auth.ts#L20
and add this scope https://www.googleapis.com/auth/spreadsheets to the list. Then clasp logout and clasp login and then run your function. You should get a response like:
{ done: true,
  response:
   { '@type': 'type.googleapis.com/google.apps.script.v1.ExecutionResponse' } }

And if you open up the Sheet, you'll see the header has changed like you wanted to do.
Obviously, this is not ideal. There is some discussion to be had about how we want to go about making this easier for the user. I remember @grant had some ideas previously about doing that, so we'll have to discuss.

Makes sense, good report.

We should report better errors. And provide the user a solution.
On clasp login --ownkey, we should auth with both:

The current clasp scopes
The scopes in appsscript.json's oauthScopes array.

Hey, actually, I don't think we even really need --ownkey anymore since we figured out recursively looking for .clasprc.json files. Essentially --ownkey just saves it to the current directory, rather than to ~/. I did not realize that appsscript.json had an oauthScopes array. How do we plan to get the scopes in there? Once the scopes are there, it shouldn't be too bad to add those when we authorize.

We need --ownkey to login non-globally to use script.run.
Let's just manually add the scopes there for now.
Eventually we can have clasp automatically add OAuth scopes to appsscript.json the current way Apps Script's editor implicity adds scopes when you run functions.
How script.google.com Requests Scopes
For example, running this in the Apps Script editor:
function myFunction() {
  SlidesApp.create("test");
}

Will implicity request the https://www.googleapis.com/auth/presentations scope.
How the script.run API Call Requests Scopes
We manually requests scopes when auth'ing clasp (or your OAuth client).
Thus, we need to explicitly add OAuth scopes for clasp's OAuth client.

I don't think that --ownkey is needed anymore for script.run. I think we've changed that since it was originally introduced.

I don't think that we need --ownkey anymore, unless you can find where in the code it is actually needed.

All I see it used for is here:
https://github.com/google/clasp/blob/8e1c3fbeca11e06d22554b183b5d43d1c8490808/src/auth.ts#L155
Where it calls authorize(...) with it.
authorize(...) then uses it to decide whether to save it in the workdir or homedir:
https://github.com/google/clasp/blob/8e1c3fbeca11e06d22554b183b5d43d1c8490808/src/auth.ts#L58
clasp run doesn't care, it just uses await loadAPICredentials https://github.com/google/clasp/blob/8e1c3fbeca11e06d22554b183b5d43d1c8490808/src/commands.ts#L270

Thanks guys. If it were possible, I think the idea would be to be able to stay in the terminal, even if that meant to type in more info at the beginning when beginning clasp. I am trying to get it to where we don't have to leave the terminal and go back to the GAS or the cloud project, which sort of defeats the purpose of using clasp in the first place, I would think.
It would be wonderful, even if it meant adding more info within the terminal at the beginning, if we could just add the scopes we need, when we begin clasp in the terminal, or, ... another suggestion is that you just add the scopes that most people need, like gmail, sheets, slides, docs, drive, scripts, etc. so we can avoid having to go out to specify what else we needed. I don't think most people who use this would have a problem giving permissions to more scopes, if it reduced the steps...
Either way, the goal would be not to have to leave the terminal so that we could run GAS anywhere (like on a cell phone using something like Termius), even if that meant putting in more info at the beginning.

@campionfellin How did you create the .clasprc.json?

@grant I just used clasp login. Did you put in your own clientId and clientSecret here? https://github.com/google/clasp/blob/24c7d1309cde125b7a9db2a7d41f32bab4f5d7d1/src/auth.ts#L12

OK, saw that you guys updated the readme file. (Remotely executes an Apps Script function. This function runs your script in the cloud. You must supply the functionName params. For now, it can only run functions that do not require other authorization.)
Just a quick question, the sendMail doesn't need the Gmail API to send things?
I know you guys must be overworked, but would it be possible to check-in in about a month to see if you had time to add the scopes?
Thanks once again for all your hard work!!!

Hey @jasonjurotich I don't think it needs the Gmail API, but it does need this scope: https://www.googleapis.com/auth/script.send_mail
Definitely check in in about a month and we can update you!
@grant I think this would be a good flow for how it works:
clasp run myFunction .... runs function to find what scopes it needs, if none, then returns value. Otherwise, return something like:
> clasp run myFunction
You need to authorize x scopes, would you like to do that now? (Y/n) Y
Adding scopes and logging you out...
Please run `clasp login` now to re-login with these scopes.

It would add those scopes to the .appsscript.json file, (which /src/auth.ts should use to get scopes) and then log the user out. They could then login again to authorize those scopes.

Setting up .clasprc.json

@campionfellin For .clasprc.json, we probably should add more instructions on how to properly create/set up this file for clasp run. Ideally it would be automatic and you wouldn't modify any JSON.
@jasonjurotich If sendMail requires authorizations (Gmail), then you'll need to login to clasp with those scopes enabled (the Gmail API send scope). Running other APIs isn't currently supported (without hacking the clasp source code).

To be honest, this feature is still experimental in clasp and will be ready at a later state.

If your function is this:
function myFunction() {
  MailApp.sendEmail({ ... });
}

Running on script.google.com will prompt you for a Gmail API scope. ("Send email as you" OAuth dialog.)
Developer Flow
@campionfellin
Ideally, a developer shouldn't modify source code (and build clasp) to use clasp run. The command was added here: #104 as a good first step but I think I missed the bigger picture for the design of clasp run.
I realized that we're missing a way for a developer to use their own OAuth Client Settings (client ID/secret) when creating their own key. A user should really be able to (1) login with their own project credentials as well as (2) read from their own credentials depending on which folder they are in. I believe (2) is implemented (you can read local credentials if you somehow created them), but you must manually change the client settings in order to create your local credentials.
Ideally a user has this flow:
npm i -g @google/clasp
# Download OAuth Credentials to the Apps Script API into creds.json
clasp login --creds creds.json

--creds creds.json would imply --ownkey (so we can remove --ownkey in place of --creds creds.json
This way you get a creds.json would be through https://console.developers.google.com/ and using your script's Project ID (script.google.com/<project> > Resources > Cloud Platform project...). Ideally we have instructions on how to do this. This ensures you meet the requirements (like common Cloud Project) listed here. From there you create an OAuth Client ID/Secret that you can download to creds.json
I am working on an easier way (within Google) to create this creds.json file rather than the above method.
@campionfellin As for the run flow, detecting scopes would be ideal for a v2 run function. I can explain how Apps Script detects scopes in a different discussion, but it's pretty complicated.
Ref: https://github.com/google/clasp/issues/11#issuecomment-370682855

Hey all, two things:

Just wanted to vote for this with my specific use case.  As I'm developing locally and testing it would be awesome if I could basically save what I'm doing and hit clasp push && clasp run main to see how my changes are doing.  Then I could effectively never open the online editor to run my code.

Is it the case that this should work out of the box as long as you don't need any additional authorizations?  I tried with a fresh project but was never able to get it to work.  Just getting the same Requested entity was not found. error as originally reported.

Thanks IanWhalen, I was actually going to send a message to see how this was going. If there were a way to add the scopes and get them approved, that would be awesome, to solve this problem.

Hi! Thanks for all your great work on this. Any updates? What is the smoothest way to use clasp run?

Yes, are there any updates in regards to being able to use other scopes? That would really help a ton to run things from the terminal. Thanks!!

I hope to get some progress on this feature at some point. However, it is complicated to implement and not the highest upvoted feature request (proxy support is high).
Pull requests or design ideas for this feature are also welcome.

Perfectly understood. I have the same problem on a lower level when people ask me for GAS scripts. Thanks for keeping an eye on it.

So theres actually another way in which we can add scopes to clasp run.
If you run a script but it doesn't have permissions, the error actually states the permissions required to run the script in an interesting string within the API response:
{
  "done": true,
  "error": {
    "code": 3,
    "message": "ScriptError",
    "details": [
      {
        "@type": "type.googleapis.com/google.apps.script.v1.ExecutionError",
        "scriptStackTraceElements": [
          {
            "function": "sendMail",
            "lineNumber": 7
          }
        ],
        "errorMessage": "The script does not have permission to perform that action. Required permissions: (https://www.googleapis.com/auth/gmail.send || https://www.googleapis.com/auth/gmail.compose || https://www.googleapis.com/auth/gmail.modify || https://mail.google.com/ || https://www.googleapis.com/auth/gmail.addons.current.action.compose)",
        "errorType": "ScriptError"
      }
    ]
  }
}

Unfortunately it only reports one scope at a time.
We could possibly have the flow:

User tries to run the script.
clasp says we need to auth again with the added scope, then runs again.

 More substatively, and maybe this should be a separate issue, but the whole oauth process is only working with the Chrome browser: on both Firefox and Safari, I'm getting error messages when redirected to localhost.


[DROOLS-1445] make property reactivity to also automatically watch va…

…riables used in patterns different from the declaring one

Replaced by https://github.com/droolsjbpm/drools/pull/1112


metrics settings

Adds a settings struct for [metrics.influxdb] settings
pub struct InfluxSettings {
    /// The URL where InfluxDB is running.
    ///
    /// # Examples
    ///
    /// **TOML**
    /// ```text
    /// [metrics.influxdb]
    /// url = "http://localhost:8086"
    /// ```
    ///
    /// **Environment variable**
    /// ```text
    /// XAYNET_METRICS__INFLUXDB__URL=http://localhost:8086
    /// ```
    pub url: String,

    /// The InfluxDB database name.
    ///
    /// # Examples
    ///
    /// **TOML**
    /// ```text
    /// [metrics.influxdb]
    /// db = "test"
    /// ```
    ///
    /// **Environment variable**
    /// ```text
    /// XAYNET_METRICS__INFLUXDB__DB=test
    /// ```
    pub db: String,
}

Looks good👍
Do you know if we can make these settings optional? I mean for the whole settings object we could use #[cfg(feature = "metrics")] but I think it is nicer if we can just make it optional.
If you like you can also add the fields username and password. Both have the type String. But here it is important that both fields are optional because influx allows communication without authentication.

thanks for reviewing. would you be happy if we postpone the "optionality" of the settings to another PR? because I had in mind other settings (in PET, especially) which should also be optional, so it could all be tackled there.

Looks good👍
Do you know if we can make these settings optional? I mean for the whole settings object we could use #[cfg(feature = "metrics")] but I think it is nicer if we can just make it optional.
If you like you can also add the fields username and password. Both have the type String. But here it is important that both fields are optional because influx allows communication without authentication.

thanks for reviewing. would you be happy if we postpone the "optionality" of the settings to another PR? because I had in mind other settings (in PET, especially) which should also be optional, so it could all be tackled there.

Sounds good to me 👍

Do you know if we can make these settings optional? I mean for the whole settings object we could use #[cfg(feature = "metrics")] but I think it is nicer if we can just make it optional.

I think we shouldn't hide it completely, because that means the config wouldn't parse based on whether the feature is there or not. A more user-friendly approach imo would be to log a warning when there's a metrics section in the config, but the metrics feature is not enabled.


Adding DESTDIR variable to makefiles

This patch is adding DESTDIR variable to the makefiles.
It would make packaging of the libdasm easier. It allows to install
to specified directory instead of the system directories.

Great! We don't really have any automated tests but I verified the following myself:

make works
make install DESTDIR=foo works
python setup.py build_ext and python setup.py install work

LGTM


use RoundRobinPacking algorithm by default

As discussed in today's sync-up meeting, we decide to make the RoundRobinPacking algorithm as the default one.
This can avoid the submission failure problem when using the ResourceCompiliantRRPacking algorithm.
In long-term, there'll be fixes to the ResourceCompiliantRRPacking algorithm.

@nwangtw @jerrypeng

sgtm. thanks


Adding support for readOnly and writeOnly

Note: I create  #136 to address the CI failure. Python 3.4 is no longer supported, the final release was in April.

Closing the PR in favor of #152


Ionicons font display issues and difficulty to locate

Hi guys, first of job all great job on the sketch template, its really nice.
I'm having some trouble resolving the font issues with Ionicons, I've tried to install various versions also mentioned in slack: https://nativebase.slack.com/archives/C25STJTNK/p1519959885000124 as the TTF font download is not simply available on the Ionicons for the latest version (v4).
However these versions lead to design issues in the template file.
https://www.dropbox.com/s/jxty8sug9x5sop6/Screenshot 2018-05-18 12.56.19.png?dl=0
Is it possible to point me to the correct Ionicons version for use with the template? I would also suggest bundling all font dependencies with the sketch download (for instance in a zip).

Had the same problem and found this.
You have to install Ionicons v2. I just tried it myself and it worked 😊


generalization performance

What is the generalization performance of this algorithm's depth estimation? Can it be used to estimate the depth of other endoscope images?

Sorry, we have not tested any of the fine-tuned depth estimation models on other data, so I cannot say. We may however investigate the relationship between pretraining and generalisability in future work.

Ok, thanks, looking forward to your future work.


Webhook Dataset Integrations

Changes Proposed
Ability to enable and disable webhooks for datasets.
List the webhooks enabled for a given dataset.
Checklist

[x] unit tests added and/or verified that tests pass
[x] I have considered any possible security implications of this change
[x] I have considered deployment issues.

The test that failed is
com.pennsieve.api.TestFilesController.File Uploads should be idempotent and not have race conditions with interleaved requests
which is not a new test or one associated with this change. I've manually kicked off another build of the pull request.


[ISSUE-869][REFACTOR] Migrate partition size/sorter related conf to Celeborn ConfigEntity

What changes were proposed in this pull request?
Why are the changes needed?

What are the items that need reviewer attention?
Related issues.
close #869
Related pull requests.
How was this patch tested?
/cc @related-reviewer
/assign @main-reviewer

gentle ping @pan3793 @waitinfuture

how about current? @FMX @pan3793

Ping again


Breadcrumbs broken in California Coast

I wasn't sure whether to post this issue on the California Coast repo or this one. I settled on this one because I figured you're more likely to know what's going wrong and I can relay the solution if need be.
The breadcrumbs in California stack vertically in California Coast for some reason, rather than horizontally, which breaks the navigation UX.

So, the issue is that California Coast changes the titlebar layout to be flex-based, but quick-explorer uses inline block.  I would change it to flex (which works), but then other themes break that aren't flex-based.   So this is going to have to be fixed in California Coast, or any other theme that changes the title bar layout.  :disappointed:

Oh, forgot to mention: the specific fix is to set #quick-explorer { display: flex }.  You can do that in a CSS snippet until there's a fix for the theme, or if somebody can come up with a display I can use for QE that works across all themes.

Also, it seems to work just as well for California Coast to just not use display: flex for the titlebar items, so that's an option too.  As far as I can tell, getting rid of the display on the titlebar-related items makes QE work fine and doesn't break anything that I can tell.

Hey @pjeby, just saw your messages after finding a solution in Discord https://ptb.discord.com/channels/686053708261228577/702656734631821413/883097557197262929
It is indeed as you say.
I'm going to use the following CSS in the snippet layer to correct it until/if California Coast fixes it.
To correct the layout:
.explorable.titlebar-button { display: unset}

#quick-explorer { background-color: var(--background-translucent) !important}

To force visibility:
.titlebar-button-container.mod-left {
    opacity: 1;
    transition: opacity 100ms ease-out;
}

The first two fixes are now in the code base, so only the opacity thing should be needed now, as a specific California Coast thing.

Oh, and thank you for both reporting the issue and sharing the tweaks!


Bring installation guide in line with ecosystem docs

Description
This PR links the installation guide to the new ecosystem docs

Codecov Report

Merging #61 (2703bb1) into main (3e86207) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Renders correctly: https://openff-docs--61.org.readthedocs.build/projects/units/en/61/#installation


The unit test test_shrink make no sense

In the test_shrink, if comment the function call pool.set_num_threads(TEST_TASKS); ,  the test also can pass.  Because after_shrink_size == TEST_TASKS and active threads == TEST_TASKS.
Then I want to try write a test case that can test shrink, but it will test fail sometimes (because the implementation in lib.rs).
The code is as follows, test_no_shrink is for the origin test case I metion above,  test_shrink_in_sleep is my custom test case using sleep.
#[cfg(test)]
mod test {
    use std::{
        sync::{Arc, Barrier},
        thread::sleep,
        time::Duration,
    };
    use threadpool::ThreadPool;

    const TEST_TASKS: usize = 4;
    #[test]
    fn test_no_shrink() {
        let test_tasks_begin = TEST_TASKS + 2;

        let pool = ThreadPool::new(test_tasks_begin);
        let b0 = Arc::new(Barrier::new(test_tasks_begin + 1));
        let b1 = Arc::new(Barrier::new(test_tasks_begin + 1));

        for _ in 0..test_tasks_begin {
            let (b0, b1) = (b0.clone(), b1.clone());
            pool.execute(move || {
                b0.wait();
                b1.wait();
            });
        }

        let b2 = Arc::new(Barrier::new(TEST_TASKS + 1));
        let b3 = Arc::new(Barrier::new(TEST_TASKS + 1));

        for _ in 0..TEST_TASKS {
            let (b2, b3) = (b2.clone(), b3.clone());
            pool.execute(move || {
                b2.wait();
                b3.wait();
            });
        }

        b0.wait();

        // no shrink call, it also can test successfully
        // pool.set_num_threads(TEST_TASKS);

        assert_eq!(pool.active_count(), test_tasks_begin);
        b1.wait();

        b2.wait();
        assert_eq!(pool.active_count(), TEST_TASKS);
        b3.wait();
    }

    #[test]
    fn test_shrink_in_sleep() {
        let test_tasks_begin = TEST_TASKS / 2;
        let shrink_tasks = 1;

        let mut pool = ThreadPool::new(test_tasks_begin);

        for _ in 0..TEST_TASKS {
            pool.execute(move || {
                sleep(Duration::from_secs(1));
            })
        }

        sleep(Duration::from_millis(100));
        pool.set_num_threads(shrink_tasks);

        /*
         *  if TEST_TASKS = 4:
         *
         *  time        tasks
         *  [0-1]       task0, task1
         *  [1-2]       task2
         *  [2-3]       task3
         */

        sleep(Duration::from_secs(1));
        assert_eq!(pool.active_count(), 1);
    }
}

This is the test result:
running 2 tests
test test::test_no_shrink ... ok
test test::test_shrink_in_sleep ... FAILED

failures:

---- test::test_shrink_in_sleep stdout ----
thread 'test::test_shrink_in_sleep' panicked at 'assertion failed: `(left == right)`
  left: `2`,
 right: `1`', src/main.rs:77:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    test::test_shrink_in_sleep

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.10s

Although I know the thread pool does not need such a precise shrink, I want to ask how to write a test case to test whether the shrink really works and the test case can pass everytime.

I have found the test case test_set_num_threads_decreasing ,  I think it's a perfect solution for my question.  But what's the test goal for test_shrink ?

One of the problems is, that we don't have control over the OS and the other tasks on the machine. Depending on the load, sleeping for 100ms may not be enough for the workers to settle down in time.
We used to have tighter tolerances, because personal development machines usually have more resources than CI machines.
I am currently rewriting the crate to make it faster and more flexible, but the focus again is on faster work speeds not faster admin reactions.
May I ask, how did you stumble over this test :)

Sorry for my late reply.
1. The reason for my fail test test_shrink_in_sleep
In my test code, Firstly initialize a thread pool with an initial number of threads of 2. And use the thread pool to run 4 tasks with sleep 1s, assuming t_0,t_1,t_2,t_3.
Let the time to start running the task be 0, then in the [0, 1000ms], the thread pool will run t_0 and t_1.   And t_2, t_3 will be in the queued channel.
At the 100 ms, we set the number of thread pools to 1. therefore:
[0, 100ms]: max_thread_count=2, active_count=2, queued_count=2,
[100ms, 1000ms]: max_thread_count=1, active_count=2, queued_count=2
When task t_0 or t_1 ends, the corresponding thread will continue the next round of the loop. First, determine the value of active_count and max_thread_count, if active_count is larger, stop this thread, which accomplishes shrink.
The code I describe is in lib.rs: L745-L766
judge if (active_count <= max_thread_count )    ==>   recv a job  ==> active_count increases by 1  ==> running the job
As expected, because max_thread_num=1, it will run t_2 at [1000ms, 2000ms] and run t_3 at [2000ms, 3000ms].
So I check assert_eq!(pool.active_count(), 1) at 1100ms.
But!  [L745-L766] this operation is not atomic, maybe both threads are not stopped at the same time because active_count <= max_thread_count is true.
In this situation,
[1000ms, 2000ms]: max_thread_count=1, active_count=2, queued_count=2
So this unit test fails.
The point of the thread pool is to work faster, not a faster management response,  I think so. It is tolerable to have such a situation, so I feel that my test case is unsuitable.
2. The test case test_set_num_threads_decreasing in lib.rs L813
My test case test_shrink_in_sleep is very similar to test_set_num_threads_decreasing, but the key difference is that my test case is new threads < queued tasks,  and in  test_set_num_threads_increasing is new threads == queued tasks
You can try modify the code in lib.rs L821, change pool.set_num_threads(new_thread_amount);  to pool.set_num_threads(new_thread_amount-1);,  then the test case will fail too.
But I think, because in the original thread pool max_thread_count > queued task, even if the set_num_threads function does not work, it can still pass assert_eq!(pool.active_count(), new_thread_amount).
So the test case test_set_num_threads_decreasing does not observe whether set_num_threads works, test_shrink in lib.rs L953 is the same.
So I want to ask if it is necessary to rewrite a better test case to test if thread number decreasing really works.


No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda-10.2'

After I shut down my computer before incompletely killing all model training processes, this problem occurred.
I try to reinstall the cuda driver and the anaconda environment is same as get_started.md, but this problem still occurres?
How can I solve?
Moreover, when I import torch
torch.cuda.is_available=False
我在一次训练模型进程未关闭完就把电脑关闭了，然后尝试重新训练时出现了这个问题，我尝试过了重装cuda驱动，且anaconda下的虚拟环境也是按照教程中的来搭建的，请问为何会出现这个问题?
而且当我导入pytorch时会出现以下问题：
torch.cuda.is_available=False

Please check where the version of your Cuda toolkit is compatible with your PyTorch

Please check where the version of your Cuda toolkit is compatible with your PyTorch

I check it and they are matched. The anaconda environment is built according to those in "get_started.md".

what did you do to solve this issue?

not sure if you still need this. nvidia-smi cmd shows the driver version cuda. nvcc cmd gives you the runtime version cuda. these are two different things. The runtime version is the one needs to match with the pytorch cuda.

Hey! I am also facing this issue!
$ nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Tue_Mar__8_18:18:20_PST_2022
Cuda compilation tools, release 11.6, V11.6.124
Build cuda_11.6.r11.6/compiler.31057947_0

$ python3 mmdetection/mmdet/utils/collect_env.py
/home/ubuntu/benchmarks/cuda_116/lib/python3.8/site-packages/mmcv/__init__.py:20: UserWarning: On January 1, 2023, MMCV will release v2.0.0, in which it will remove components related to the training process and add a data transformation module. In addition, it will rename the package names mmcv to mmcv-lite and mmcv-full to mmcv. See https://github.com/open-mmlab/mmcv/blob/master/docs/en/compatibility.md for more details.
  warnings.warn(
fatal: not a git repository (or any of the parent directories): .git
sys.platform: linux
Python: 3.8.10 (default, Nov 14 2022, 12:59:47) [GCC 9.4.0]
CUDA available: True
GPU 0: Tesla V100-SXM2-16GB
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 11.6, V11.6.124
GCC: x86_64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
PyTorch: 1.12.0+cu116
PyTorch compiling details: PyTorch built with:
  - GCC 9.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v2.6.0 (Git Hash 52b5f107dd9cf10910aaa19cb47f3abf9b349815)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 11.6
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86
  - CuDNN 8.4.1
    - Built with CuDNN 8.3.2
  - Magma 2.6.1
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=11.6, CUDNN_VERSION=8.3.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=1.12.0, USE_CUDA=ON, USE_CUDNN=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=OFF, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF,

TorchVision: 0.13.0+cu116
OpenCV: 4.7.0
MMCV: 1.7.1
MMCV Compiler: GCC 9.3
MMCV CUDA Compiler: 11.6
MMDetection: 2.28.1+

but when I train with mmdet, I get:
RuntimeError: No CUDA GPUs are available
Tried, to train with PyTorch only, everything worked fine.


Docs: Tweak some links

Description
Changed some links to blob from current main.
Motivation & Context
Better convey information to people trying to contribute.
Type of changes

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

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
(N/A) I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-40704--twbs-bootstrap.netlify.app/

Related issues
NA

Sorry, don't like that. I'd rather use the variables.


[FIX #3931] Implement a cop checking for ambiguous block association …

…with a method
This cop checks for ambiguous block association with method when param passed without parentheses.
Example:
It's ambiguous because there is no parentheses around a param:
some_method a { |val| puts val }
With parentheses, there's no ambiguity:
some_method(a) { |val| puts val }
Cop will add warning message:
Parenthesize the param to make sure that block will be associated with method call.

Your code currently produces a ton of false positives. Guess now you have plenty of ideas about new test cases. :-)


🐛 Bug Report: I have been charged $100 by traceloop

Which component is this bug for?
Anthropic Instrumentation
📜 Description
I had subscribed to a $0 plan but my account was deducted by $100 today. How can I claim the refund? I haven't used traceloop for anything except testing. I doubt I have incurred any cost.

I can provide the payment details as well.
I used my google account to sign up for traceloop<EMAIL_ADDRESS>I didn't get any email prior to getting the money deducted.
👟 Reproduction steps

👍 Expected behavior

👎 Actual Behavior with Screenshots

🤖 Python Version
No response
📃 Provide any additional context for the Bug.
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Are you willing to submit PR?
None

What is the contact email for the support team?

Hey @bhattbhuwan13,
If that's the case, we'll definitely make sure that you'll be refunded.
Feel free to contact us through our support widget in our website, or through our community slack. (You can also message me directly there - Gal Kleinman).

@bhattbhuwan13 no need to contact. I found your transaction, and refunded it.
It make take few days to see the refund in your account.
Still, feel free to contact us for any further issue.
Closing the github issue here.


tf error: canTransform: target_frame map does not exist..

Hi ,
when  I run this code, I encountered  this error.
[ WARN] [1531246455.136213972, 45.726000000]: Timed out waiting for transform from base_footprint to map to become available before running costmap, tf error: canTransform: target_frame map does not exist.. canTransform returned after 45.726 timeout was 0.1.
[gazebo_gui-3] process has died [pid 15609, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/gao/.ros/log/9a1c10a8-844f-11e8-98c9-000c2993f013/gazebo_gui-3.log].
log file: /home/gao/.ros/log/9a1c10a8-844f-11e8-98c9-000c2993f013/gazebo_gui-3*.log
[gazebo-2] process has died [pid 15607, exit code 134, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /home/gao/catkin_ws/src/turtlebot_rrt/maps/simple_maze.world __name:=gazebo __log:=/home/gao/.ros/log/9a1c10a8-844f-11e8-98c9-000c2993f013/gazebo-2.log].
log file: /home/gao/.ros/log/9a1c10a8-844f-11e8-98c9-000c2993f013/gazebo-2*.log
Could you give me some advice?

Check whether laser sensor publishing scan data on /scan topic or not. If not fix the laser sensor to publish scan data on topic. Then try


Document the findPlugin Method

docs: document the findPlugin function
document the findPlugin and how to use it
ISSUES CLOSED: #1180
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/main/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Other... Please describe:

What is the current behavior?
There was no documentation for findPlugin

Issue Number: #1180
What is the new behavior?
This provides documentation for findPlugin.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Can you clarify what you mean by that?

I just saw another comment and remembered your gitter message, so I will update this.

@SanderElias I just updated the documentation with the requested changes.


Robot configuration. My configurations item click.

Is your feature request related to a problem? Please describe.
In the list of my saved programs, when a item is clicked anywhere but the action buttons, the program execute the open command. In the "My configurations" list, it doesn't.
Describe the solution you'd like
Replicate the behaviour of "my programs". When a item is clicked, execute the open command.
Describe alternatives you've considered
Remove the behavior in "my programs", so the user experience is consistent in both sides.
Additional context
Robot configuration - > my configuration -> list item selected.

Both open when clicked anywhere now.


[Unit Test] Cannot run unit tests from VSCode when using NUnit's TestFixtureSource

I'm not sure whether this is a C# extension's bug or NUnit, filing here as when running dotnet test everything works.
Environment data
dotnet --info output:

.NET Command Line Tools (1.0.4)
Product Information:
Version:            1.0.4
Commit SHA-1 hash:  af1e6684fd
Runtime Environment:
OS Name:     ubuntu
OS Version:  16.04
OS Platform: Linux
RID:         ubuntu.16.04-x64
Base Path:   /usr/share/dotnet/sdk/1.0.4

VS Code version: Version 1.15.1
C# Extension version: 1.12.1
Steps to reproduce
Extract VSCodeBug.zip and open it in VS Code. After restoring packages click "run test" or "debug test" on method Test.
The project uses NUnit and its TestFixtureSourceAttribute to run the test fixture multiple times with different data.
Expected  behavior
When placing breakpoint at the beginning of the mehod and clicking "debug test" the debugger should hit the breakpoint.
When clicking "run test" the test should be executed 10 times with results in log.
Actual behavior
When I click "debug test" I see:

Debugging method 'AA.UnitTest1.Test'...
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.
VSCodeDebuggerBug -> /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:01.94
NUnit Adapter <IP_ADDRESS>: Test discovery starting
NUnit Adapter <IP_ADDRESS>: Test discovery complete

and nothing happens, no breakpoint is hit, after clicking "debug test" again I get:

Microsoft (R) Build Engine version 15.1.1012.6693
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.
Copyright (C) Microsoft Corporation. All rights reserved.
VSCodeDebuggerBug -> /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll
VSCodeDebuggerBug -> /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll
Build succeeded.
Build succeeded.
0 Warning(s)
0 Warning(s)
0 Error(s)
0 Error(s)
Time Elapsed 00:00:00.98
Time Elapsed 00:00:00.98

Notice the duplicate entries, also a popup with "Failed to start debugger: null" error shows. A new entry is added after every run (after 5 runs, the messages are duplicated 5 times).
When I click ''run tests" I see:

Running test AA.UnitTest1.Test...
Microsoft (R) Build Engine version 15.1.1012.6693
Copyright (C) Microsoft Corporation. All rights reserved.
VSCodeDebuggerBug -> /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.98
NUnit Adapter <IP_ADDRESS>: Test discovery starting
NUnit Adapter <IP_ADDRESS>: Test discovery complete
Total tests: 0. Passed: 0. Failed: 0. Skipped: 0

So VS Code haven't found any test to run.
When executing the same code with dotnet test I see:

Build started, please wait...
Build completed.
Test run for /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll(.NETCoreApp,Version=v1.1)
Microsoft (R) Test Execution Command Line Tool Version <IP_ADDRESS>
Copyright (c) Microsoft Corporation.  All rights reserved.
Starting test execution, please wait...
NUnit Adapter <IP_ADDRESS>: Test execution started
Running all tests in /home/strachu/VSCodeDebuggerBug/bin/Debug/netcoreapp1.1/VSCodeDebuggerBug.dll
NUnit3TestExecutor converted 10 of 10 NUnit test cases
NUnit Adapter <IP_ADDRESS>: Test execution complete
Total tests: 10. Passed: 10. Failed: 0. Skipped: 0.
Test Run Successful.
Test execution time: 0.9933 Seconds

So from command line everything works.
When I remove the TestFixtureSourceAttribute and a ctor from the class and invoke it from VSCode, 1 test is run, so this case is working correctly, the problem is when using TestFixtureSourceAttribute.

Just noting that the duplicate entries in logs and a popup with "Failed to start debugger: null" error on a second try with "debug this" seems to be an unrelated bug as the same happens when the debugger fails to start due to a compilation error or when clicking again "debug this" too fast on working test case.
After this it is impossible to debug again without restarting Visual Studio Code.

Is there any updates on it? It seems I face the same issue now.

This is still a problem and prevents the use of NUnit's TestFixtureSource in combination with Omnisharp. Here is another example (gist) that works with dotnet test but fails with the following error when clicking the debug line in the source code:
{
  "Request_seq": 135,
  "Command": "/v2/debugtest/getstartinfo",
  "Running": true,
  "Success": false,
  "Message": "\"System.NullReferenceException: Object reference not set to an instance of an object\\n  at OmniSharp.DotNetTest.VSTestManager.DebugGetStartInfoAsync (System.String[] methodNames, System.String runSettings, System.String testFrameworkName, System.String targetFrameworkVersion, System.Threading.CancellationToken cancellationToken) [0x00113] in <4f61ed4d73fa416e988571e27def90ec>:0 \\n  at OmniSharp.Endpoint.EndpointHandler`2[TRequest,TResponse].GetFirstNotEmptyResponseFromHandlers (OmniSharp.Endpoint.Exports.ExportHandler`2[TRequest,TResponse][] handlers, TRequest request) [0x00099] in <def28aea2ee84c5d8f408bdb08c9c4ba>:0 \\n  at OmniSharp.Endpoint.EndpointHandler`2[TRequest,TResponse].HandleRequestForLanguage (System.String language, TRequest request, OmniSharp.Protocol.RequestPacket packet) [0x00163] in <def28aea2ee84c5d8f408bdb08c9c4ba>:0 \\n  at OmniSharp.Endpoint.EndpointHandler`2[TRequest,TResponse].Process (OmniSharp.Protocol.RequestPacket packet, OmniSharp.Endpoint.LanguageModel model, Newtonsoft.Json.Linq.JToken requestObject) [0x0024b] in <def28aea2ee84c5d8f408bdb08c9c4ba>:0 \\n  at OmniSharp.Stdio.Host.HandleRequest (System.String json, Microsoft.Extensions.Logging.ILogger logger) [0x000e7] in <bc69fa58846f4d298e971dab810bd026>:0 \"",
  "Body": null,
  "Seq": 254,
  "Type": "response"
}

My configuration:
dotnet --info output:
.NET SDK (reflecting any global.json):
 Version:   5.0.100
 Commit:    5044b93829

Runtime Environment:
 OS Name:     debian
 OS Version:  10
 OS Platform: Linux
 RID:         debian.10-x64
 Base Path:   /usr/share/dotnet/sdk/5.0.100/

Host (useful for support):
  Version: 5.0.0
  Commit:  cf258a14b7

.NET SDKs installed:
  5.0.100 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.0 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 5.0.0 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download

VS Code version: 1.51.1
C# extension version: 1.23.7
NUnit version 3.12.0

I'm currently also experiencing this same issue with the following configuration:
VS Code Version: 1.74.3
C# extension version: 1.25.4
NUnit version: 3.13.3
Has there been any progress on this or at least a work around?

The C# extension has a minimal unit testing experience that may not work with every testing framework feature. The C# DevKit has a more robust unit testing experience.


Feature Request: Combine multiple damage rolls into one

When someone casts a spell like Breathe Fire he can put in multiple FP to increase the damage output.

Multiple dice are rolled - very nice so far.

But when it comes to applying the damage there is no option to apply all the damage in one go.
In the example below there are three dice of damage 2; 5 and 6.
So every dice of damage is compared individually against the DR. Thus the first dice (2) inflicts no damage, the second dice (5) 1 point damage and the last (6) inflicts 2 points damage, 3 points in total.
There should be an option to apply the sum of all dice rolled at once.
So it would be 2 + 5 + 6 = 13.
Than DR would be subtracted only once from the total damage rolled for a damage of 9 points.

This is a good idea.  You probably want two options for "all".

Total sum in one hit
Apply all of them but as single hits

I'd push back on this idea and suggest what you really want is either: multiple OtFs in the attack notes that handle different FP costs (1d-1, 2d-2, 3d-3, etc) or a macro to prompt the user for the number of energy points and then creating a roll with the correct damage.

Makes sense, Jeff.  Sort of relates to #1094 where I haven't quite figured out how to modify the "fireball" macro to do the unmodified skill check to then adjust the FP (or other resource tracker) down (or up) appropriately based on energy used.  If that could be finessed into working you can use it as a template of sorts to cater for different spells with different damage dice, but all driven by "energy" to determine damage and FP or Threshold or whatever tracker is being used in one click (and maybe even trigger animations and sounds, I guess).

Jeff fixed this in 2 ways.

He added a "Combine" button to the "Resolve Damage" dialog (right clicking on any damage button will bring it up).   This will merge all of the rolls into a single damage.
He expanded the OTF damage formula to allow accumulated damage (and FP cost):
[+1d burn *per 1 FP]
Clicking this will accumulate the roll (just above the modifier bucket).   Clicking the accumulator will "fire it off", rolling the appropriate damage (and paying the appropriate cost).


Add my first file

I have created a branch, a file is created and then commit it done.

confirmed


Backport fix for doublestar globbing

Description of Changes
Please check that the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Add a changelog entry (for non-trivial bug fixes / features)
[ ] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4827726
+0.06891608
126.403694
-2.123787

1
5000
5.3107166
+0.36235428
132.7721
-4.5680237

1
10000
9.44822
-1.0174417
143.54216
-0.24784851

1
50000
47.070103
-1.6209488
178.05522
+4.7250824

1
100000
91.518616
-1.2570648
229.63954
-12.122574

10
100
1.913867
-0.05175078
132.74489
+0.974411

10
500
5.6381164
-0.17235184
138.19531
-0.8331146

10
1000
11.25901
+0.12092209
146.06075
-0.77223206

10
5000
55.277473
+3.569767
178.4418
-3.429016

10
10000
100.46849
-3.3467941
219.611
-4.544449


[Bug report] Gravitino Web UI Catalog show no tables when it does have them

Describe what's wrong
Sometimes tables do not show when expanding a catalog.

Error message and/or stacktrace
N/A
How to reproduce
Click on expand/collapse a few times in a row on a schema.
Additional context
No response

I tested based on the description, but the error did not occur.
#1657 This PR optimized the expand and collapse of the treeview.
Please pull the latest code and test again.
If the issue still exists, please open this issue.


Grafana version 0.8.5 fails to deploy dashboards using dashboard-import-job on k8s v1.9.4

Is this a BUG REPORT or FEATURE REQUEST? BUG REPORT
Version of Helm and Kubernetes:
 ~  helm version
Client: &version.Version{SemVer:"v2.4.2", GitCommit:"82d8e9498d96535cc6787a6a9194a76161d29b4c", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.2", GitCommit:"a80231648a1473929271764b920a8e346f6de844", GitTreeState:"clean"}

Kubernetes version: 1.9.4-gke.1
Which chart:
name: grafana
version: 0.8.5
appVersion: 5.0.4
What happened:
Grafana deployment fails when using dashboardImports.dashboard option to import dashboards on the fly when downloading JSON files. Job errors out with  Read-only file system message when wget tries to write JSON file to disk.
What you expected to happen:
Dashboard JSON files should be downloaded and passed to Grafana API for installation.
How to reproduce it (as minimally and precisely as possible):

Update values.yaml file to look like (extract):

dashboardImports:
  ## If true, a Job will be created to import dashboards
  ## Default: false
  ##
  enabled: true

  ## How long should it take to commit failure
  ## Default: 30
  ##
  activeDeadlineSeconds: 30

  ## Docker image to run import process
  ## Default: jgoclawski/wget:1.0
  ##
  image: jgoclawski/wget:1.0

  ## Grafana dashboard files to import as ConfigMap entries
  # files: {}

  ## Grafana dashboard URL to import (this should be a JSON file, not the HTML page)
  # Example:
  dashboards:
     Kubernetes_Cluster_Mon.json: https://grafana.com/api/dashboards/315/revisions/3/download
     NGinx_VTS_Stats.json: https://grafana.com/api/dashboards/2949/revisions/2/download

Run helm upgrade -i monitor-dashboards ./ --namespace management --debug

Job to download Dashboard JSON files fails with:
kubectl logs -n kube-system job/monitoring-grafana-import-dashboards
Found 3 pods, using pod/monitoring-grafana-import-dashboards-dkqf2
+ set -e
+ cd /var/lib/grafana/import
+ wget -O Kubernetes_Cluster_Mon.json https://grafana.com/api/dashboards/315/revisions/3/download
Kubernetes_Cluster_Mon.json: Read-only file system

Anything else we need to know:
Deployment succeeds if I don't try to import dashboards. Note that I got this to work by changing the bash script in templates/dashboards-import-job-configmap.yaml to use /tmp to download JSON files and dashboards were installed in Grafana correctly. Something like (extract of bash script, the rest looks exactly the same as in repo):
 init.sh: |
    #!/bin/sh
    set -e
    # cd /var/lib/grafana/import
    cd /tmp
    {{- range $name, $val := .Values.dashboardImports.dashboards }}

Fix should be simple: we can modify this script to copy any JSON files found at /var/lib/grafana/import to a /tmp/grafana/import dir and then proceed to download any other requested dashboards JSON files to finally pass them over to Grafana API for installation.
Thoughts?

Also faced with the problem using minikube but can't find any specific logs.
values.yaml:
server:
  image: "grafana/grafana:5.0.4"
  adminUser: admin
  adminPassword: admin

  persistentVolume:
    storageClass: standard
    size: 1Gi

  setDatasource:
    enabled: true
    datasource:
      name: prometheus
      type: prometheus
      url: http://prometheus:9090

  dashboardImports:
    enabled: true
    dashboards:
      cluster.json: https://grafana.com/dashboards/315/revisions/3/download

Data source is configured in grafana, but there is no any dashboard. The same thing when I use dashboardImports.files. Looks like import is broken.

@bivas, @jgoclawski does import work for you? Maybe I'm doing something wrong?

I still haven't tried this version (wget). Still using the previous (curl) one I merged.
I know that version works.

The reason you see this bug, is an update in Kubernetes, that has patched a vulnerability in configmaps and now they can't be mounted as volumes for write. See issue: https://github.com/kubernetes/kubernetes/issues/60814
The previous version with "curl" would break as well in newest Kubernetes, because the path /var/lib/grafana/import is a configmap mounted as a volume.
So I guess we should get rid of "dashboards-import-volume" and the problem will be fixed. This volume wasn't ever needed really.
The problem will also go away when either https://github.com/kubernetes/charts/pull/3514 or https://github.com/kubernetes/charts/pull/4713 gets merged so that we can use Grafana's 5 built-in dashboard provisioning.

@jgoclawski Thanks for the detailed comment. Now it's clear :)

@rtluckie
I will close this one out once #4713 is merged. That way I can get the latest updates and try the new method to download/install dashboards.
Thanks.

Can confirm last chart version works

@rtluckie
I confirm I was able to install Grafana dashboards successfully setting up a default Prometheus datasource and a dashboard import config like the following:
dashboards:
 kubernetes-monitoring:
   gnetId: 315
   revision: 3
   datasource: prometheus-backend-stats

The changes in this pull request are no longer needed nor valid given the changes introduced by #4713. Closing this issue now.
Thank you @rtluckie!


x/pkgsite: package removal request for github.com/ca-std/lib

What is the path of the package that you would like to have removed?
github.com/ca-std/lib
Are you the owner of this package?
Yes.
What is the reason that you could not retract this package instead?
It is no longer under development in this location.

Please try https://go.dev/about#removing-a-package first.

Please try https://go.dev/about#removing-a-package first.

The repository no longer exists; I cannot add the retract directive to the go.mod file.


Docstrings for azure-core

Rough draft for azure-core docstrings.
Please provide any feedback on inaccuracies or where more information is needed. Code samples largely came from existing docs.

Can one of the admins verify this patch?

Clicking update branch to bring in my fix for failing management resources build.


Cannot compile the server with the given instructions anymore.

Since commit 84f17fdeab518cbe9f9c1a5fdf7dc50981c01806. Cannot compile with the given instructions anymore.
Apparently, now there's a new requirement libavdevice-dev to install not mentioned in BUILD.md.
I didn't make a PR yet because, even then, I can't compile.
Apparently the version of libavformat is incompatible.
../../scrcpy/app/src/v4l2_sink.c: In function 'sc_v4l2_sink_open':
../../scrcpy/app/src/v4l2_sink.c:183:19: error: 'AVFormatContext {aka struct AVFormatContext}' has no member named 'url'
     vs->format_ctx->url = strdup(vs->device_name);
                   ^~
../../scrcpy/app/src/v4l2_sink.c:184:24: error: 'AVFormatContext {aka struct AVFormatContext}' has no member named 'url'
     if (!vs->format_ctx->url) {
                        ^~

I'll try to figure out how this can be worked with.
I'm leaving here in case someone has an idea.

Thank you for the report.
Could you please test branch fix2382?

Since commit 84f17fdeab518cbe9f9c1a5fdf7dc50981c01806.

Probably since d39161f7539b9d335e38385ffff5c3b4c21c7122 in fact.

Apparently, now there's a new requirement libavdevice-dev to install

Yes.

not mentioned in BUILD.md

On dev, it is mentioned: 8fb5715740e52bcb2ba8d4bac1e53f4ef76ef688.

Oops, no, the fix is obviously wrong for older version. Will fix it later.

Fixed: fix2382.2

Meanwhile, I finished a workaround. I was coming to tell now. I'll keep it just in case.
BTW, Yep. fix2382.2 fixed!
I'll keep my local workaround around, though inactive, just in case.
Thank you!

Yep. fix2382.2 fixed!

Thanks, pushed to dev.


Keep proper data type for JSON arrays between conversions. & Fixed conversions for nested JSON arrays and single element Array

If you convert a JSON array into XML and back to JSON, every data types in the array will be converted to string.
ie., {"k": [34, true, "val"]} -> xml -> json => {"k": ["34", "true", "val"]}
That's fixed in this commit as is done for JSONObjects.
Second commit does proper conversions for following cases (multi array nesting is now possible):
[['val', 32]] -> xml -> json => [['val', 32]]
[32] -> xml -> json => [32]

Second commit fixes a lot of conversion issues where there are JSON arrays (even nested) as mentioned in my comment on #7

Do you have an example for such an problematic scenario?

Transforming from XML (elements with class attribute) to JSON is enough. I think this PR only covers one specific use case (JSON -> XML -> JSON) but may hurt the other ones

:smile: cool.
Please, Write one test case which passes in the current branch but fails in my branch.
We will start from there :wink:


 Use --location=global instead." warning.
"-g" configuration is deprecated. We should use "--location=global" configuration instead of "-g".

Thanks @hknakn , though have you tried these solutions? https://stackoverflow.com/questions/72401421/message-npm-warn-config-global-global-local-are-deprecated-use-loc
maybe try: npm i -g npm@latest


[WIP] fix: retry events happening too close together

Delay the next retry any time there was a sync attempt, even if it wasn't triggered by a retry event. This fixes retry events triggering too close after a sync, full-sync, or namespace event.

 So the max backoff is the effectively the polling period (15s by default, 5s in e2e tests).
When there is a management conflict detected by a sync attempt, and the conflict is later resolved by a 3rd party, the conflict error is never removed, because the remediator is paused, because the sync errored. Then syncs are skipped, because the source didn't change, until there's a full-sync that clears the cache and calls the updater again.

So it turns out this change actually causes those two bugs I discovered. AND the "bug" this PR was trying to fix isn't actually a bug.
It turns out SyncEvents and RetryEvents are safe to happen back to back and interleaved, because the SyncEvents only calls ParseAndUpdate if the source has changed, and ParseAndUpdate is the thing we actually want to delay. SyncEvents still needs to run to do the Read stage that checks the shared volume for new commits/changes/rendering. And RetryEvents need to happen in order to check conflicts and watch updates, even if there's no error to retry.
Follow up with more tests: https://github.com/GoogleContainerTools/kpt-config-sync/pull/1475


update go version to 1.22.7

update go version

What this PR does / why we need it:
https://github.com/helm/helm/issues/13318
Special notes for your reviewer:
If applicable:

[ ] this PR contains user facing changes (the docs needed label should be applied if so)
[ ] this PR contains unit tests
[ ] this PR has been tested for backwards compatibility

@mattfarina, @robertsirc Can you please approve this PR? This PR fixes some of the CVEs https://nvd.nist.gov/vuln/detail/CVE-2024-34156


chore(main): release 0.1.3

:robot: I have created a release beep boop
0.1.3 (2024-07-12)
Features

remove old urls (#21) (2ce038f)
store Kontrol location (#20) (ad42d22)
Take k8s manifest as input instead of docker compose (#30) (4bcda1f)
use install link alias (#28) (40e9d75)

Bug Fixes

image for quick demo (#32) (76d3ff3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kurtosis-tech/kardinal/releases/tag/0.1.3 :sunflower:


Create integration tests

We have a lot of unit tests, but no integration tests. To test the linkage of all different parts, some integration test would be beneficial and could save alot of time in the future.

With PR #158 an happy flow integration test was included. Currently it is placed within unit tests, but it should be moved to integration tests.

Takea a look at https://github.com/integritee-network/worker/blob/master/.github/workflows/build_and_test.yml
there are demo scripts included to do integration tests. I think we should do the same with openfinex, but also do some smaller ones, that are not dependent on openfinex, like https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/happy_path.rs because that's already doable now.

The implemented integration tests should be included into the Github Actions CI

Hey @haerdib,
I identified these module for integration testing:-

https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/polkadex.rs [Polkadex Account Storage]

Stores information related Accounts and their sub accounts.

https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/test_polkadex_balance_storage.rs [Polkadex Balance Storage]

Stores information about accounts and their balance.

https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/polkadex_orderbook_storage.rs [Polkadex Orderbook]

Maintains orderbook storage.

https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/polkadex_gateway.rs [Polkadex Gateway]

Stores gateway related functions. (Create Order, Cancel Order etc)

Let me know, if I missed anything?

Before you're starting with integration tests regarding Polkadex Account Storage, check with @arrudagates nonce update and account storage refactoring (https://github.com/Polkadex-Substrate/polkadexTEE-worker/pull/166).
I think the RPC interface should also be tested if possible: https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/rpc/worker_api_direct.rs#L187 (including the nonce handling, implemented by @arrudagates )
I guess the rpc interface testing could go hand in hand with account storage testing.

Hey @haerdib, do you mean to test this function? (https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/rpc/worker_api_direct.rs#L187-L192)

Not necesarily. It's just the entry point of each rpc call into the enclave. You could also implement an rpc call calling from the outside (from worker side) or test each rpc call separatedly, like from here: https://github.com/Polkadex-Substrate/polkadexTEE-worker/blob/develop/enclave/src/rpc/polkadex_rpc_gateway.rs#L77
It's not that important because evnetually we'll most likely be testing the rpc calls with a demo script for full integration (including the openfinex).

Okay @haerdib, as discussed the acceptance criteria to close this issue is:-

White Box Integration testing with Mocked OpenFinex using Rust in-build testing.
Black Box integration testing with OpenFinex server using Python Script.


Call for the logo of ShardingSphere（征集ShardingSphere的logo）

The former logo is an “S” consisted of two curved lines up and down. Current thought of the logo renewal is: retain the “S” element while add the meaning of “Sphere.” Referring to ecosphere, “sphere” also contains the meaning of ball, so we can see how to combine both of the two meanings. In brief, the product implication should be “S” (sharding) + sphere (ecosphere).
The font of ShardingSphere should be improved to be a more noticeable kind.
Two colors should be provided: transparent background color white, fit to put in black or blue background; and a color fit to put on white background, better to be orange, indicating to be related with database.
Two layouts should be provided: one for square picture, with the font below the logo; the other for long picture, with the font on the right of the logo.
As a result, considering color + layout, there will be 4 kinds of combinations for logo.
Not strange when put together with other Apache logos.

中文翻译：

原logo是由上下两个曲线组成的S。目前对logo更新想法是，保留S的元素，再加上Sphere的寓意。sphere是生态圈，直译是球的意思，可以看看如何结合。产品寓意应该是S（分片）+ 球（生态圈）。
ShardingSphere字体需要美化为高辨识度的字体。
需要提供两种颜色：一个是透明背景的白色，合适放在黑色或蓝色的背景中；另一个是适合放在白色的背景下的，最好是橙色，表示与数据库相关。
需要提供两种样式：一个是字在logo的下方，适用于方图；另一个是字在logo的右方，适用于长图。
因此，颜色 + 样式，是一共4个logo的组合。
与其他apche的logo放在一起的时候没有违和感

1.chinese elemet   Tai Ji :It represents Chinese philosophy.
2.Sphere is the meaning of circle:
3.S meaning of sharding sphere

尝试做的几个一并传上来

Thank you for all the logo designed. I think this one is really good. We want choose this one.
Thank you everybody.


Loads of errors for unity 2019.1

Grabbed the master version for use in unity 2019.1 and i get a ton of errors about namespaces:

How do i fix this?
And why in the heck is it still not in the package manager so its easier to keep up to date .... its only been like 3 years now.. and far more developed than a lot of preview packages out there.

Grabbed the master version for use in unity 2019.1 and i get a ton of errors about namespaces:

How do i fix this?
And why in the heck is it still not in the package manager so its easier to keep up to date .... its only been like 3 years now..and is far more developed than many of the preview packages out there.

First variant. Check your namespace in project. May be VS or your IDE change standart namespace.
Second variant. What the folder architecture looks like in your project?

There is no conflicting namespaces - the folder architecture has not changed from 2018 and 2019 - not sure why that would change on update.

I had this issue as well, just ensure you have the "AI" built-in module enabled in the package manager!

I don't think there is any developer maintaining the repo anymore, it's basically dead since 2 years ago.

You shouldn't be using the master branch with Unity 2019.1, but the 2019.1 branch instead, right?


gtk: Add Orientable subclassing support

Fixes: https://github.com/gtk-rs/gtk4-rs/issues/147

It was not clear to me how to implement this for the Button example. See https://paste.centos.org/view/22d00849

It was not clear to me how to implement this for the Button example. See https://paste.centos.org/view/22d00849

It was not clear to me how to implement this for the Button example. See https://paste.centos.org/view/22d00849

You need to install an orientation property of type gtk::Orientation on your subclass.
Let's maybe also get that example once it works into the examples subdirectory.

It was not clear to me how to implement this for the Button example. See https://paste.centos.org/view/22d00849

You need to install an orientation property of type gtk::Orientation on your subclass.
Let's maybe also get that example once it works into the examples subdirectory.

Added an example, which of course, does not not work hehe.

Added an example, which of course, does not not work hehe.

How does it not work, what happens?

How does it not work, what happens?

I am sorry for the abysmal lack of precision. The two labels appear horizontal.

I am sorry for the abysmal lack of precision. The two labels appear horizontal.

Fixed.

Fixed.

Looks good to me overall, @sdroege mind having a quick look at the various comments written to see if something doesn't really make sense? :)

Looks good to me overall, @sdroege mind having a quick look at the various comments written to see if something doesn't really make sense? :)

Looks good to me overall, @sdroege mind having a quick look at the various comments written to see if something doesn't really make sense? :)

Which comments? Does it work now? :) I have no idea about all the GTK specifics here, that's something for you to check but I guess it's ok if it works

Looks good to me overall, @sdroege mind having a quick look at the various comments written to see if something doesn't really make sense? :)

Which comments? Does it work now? :) I have no idea about all the GTK specifics here, that's something for you to check but I guess it's ok if it works

Comments in the example. The example works just fine, it is just a custom widget consisting of a pair of labels, and a button which changes the orientation of the former.

Comments in the example. The example works just fine, it is just a custom widget consisting of a pair of labels, and a button which changes the orientation of the former.

Thanks @A6GibKm

Thanks @A6GibKm


v 4: Fluent-style API (early preview). feedback welcome!

fluent-style API with "active" domain objects (Issue, User, Membership, etc) which have methods for CRUD operations embedded in them.
this replaces xxManager classes for CRUD operations.
note - not ALL methods are implemented yet. this is more of a demo of the proposed approach.
a few examples of old vs. new API:
old:
    Issue issue = IssueFactory.createWithSubject("test123");
    Version ver = VersionFactory.create(123);
    issue.setTargetVersion(ver);
    IssueCategory cat = IssueCategoryFactory.create(673);
    issue.setCategory(cat);
    issue.setProject(project);
    manager.getIssueManager().createIssue(issue);

new API:
   Issue issue = new Issue(mgr.getTransport(), projectId)
        .setSubject("test123")
	.setTargetVersion(new Version().setId(123))
	.setCategory(cat);
        .setProjectId(projectId)
        .create();

old API:
    Group template = GroupFactory.create("group " + System.currentTimeMillis());
    Group group = userManager.createGroup(template);

new API:
    Group group = new Group(transport)
        .setName("group")
        .create();

old API:
    userManager.deleteUser(123);

new:
    user.delete();

tagging a few people who recently submitted PRs to get early feedback:
@taomWTP  @marob  @likeanowl @christau @albfan @matthiasblaesing

@alexeyOnGitHub seems pretty good! :+1:

Fluent style api looks much better and convenient than old.

released version 4.0.0.preview.1 to OSS Sonatype. It will be auto-synced to Maven Central soon. feel free to try it out!

I'm not sure whether I like it. My first gut feeling is not good.
One pattern that breaks with this fluent approach is:

Create DTO (for example a TimeEntry) on the Swing EDT, so that data from input fields can be directly transfered to the DTO
Dispatch the transfer of the DTO into a background thread.

With the fluent approach, I'll need three steps:

Aquire a redmine transport off the EDT in a background thread and fill the DTO
On the EDT transfer data from input field to the DTO
Dispatch the network interfacing thread again into a background thread

The alternative would be:

Create DTO with a `null' transport
Fill DTO with the data on the EDT
Dispatch the transfer into the background thread, there set the transport and invoke the target method

I see a benefit of the fluent approach, but I see problems, if the above two phases need to be separated.

@matthiasblaesing I see your point. the new API may require separating your internal domain objects structure from the library usage.
this "fluent-style" makes the objects less reusable, but improves discoverability for API operations.
it follows  "OOP" approach it its strict sense (data and operations are combined together), instead of following currently widely used "anemic domain design"  with POJOs and "manager" classes to operate on them.
the obvious downside of this "fluent design" (which realistically we can just call "pure OOP" in this context) is that "active" objects lose a lot of their reusability in various contexts. is better discoverability a good enough benefit to make up for that?..
as much as I like anemic model, my experience of working with somewhat similar Atlassian's JIRA API makes me very averse to this approach for REST API usage due to a large amount of boilerplate and lots of "factories" and "managers".
if you are working on a swing-based app, I assume you perform all network-related operations (like creating issue, creating field, etc) in a separate thread and then later update UI when some "Future" completes.
if you need to add a watcher to an issue, that would mean a network call no matter what. the new API will require calling ".addWatcher()"  or something like that, while the old one requires IssueManager.addWatcher(..). either way you need to keep some object with transport in it, and only use it in a separate thread to make sure your UI does not freeze.
if we were to move the API to the new model, would you have any suggestions on how to make it better for your use-case?

@alexeyOnGitHub the benefit of the old API was, that there was a clear distinction between the passive objects, that were save to operate on in the EDT and the network interaction (the manager calls). With that distinction, I can work and ensure, that network calls are always done outside the EDT.
In an ideal world, redmine would just publish the API as a swagger document and I could generate my data + accessor objects from that. Having worked with WSDLs, generating code from these was always pretty easy.
I have no strong feelings here. My work on the redmine client was always motivated by curiosity, at this time I think I haven't looked at the codebase for at least a year and don't use it myself.

I have been using this api from several months ant it is great. And the fluent style looks better.
Looking for simplicity and code reuse, why not move more to OO using inheritance, and maybe mitigate some of the @matthiasblaesing concerns? This is a proposal:
Convert the FluentStyle interface into an abstract class to encapsulate all common functionality related to transport. This base class would include:

new() and new(transport). Do not specify ant transport in subclass constructors. The transport variable will be protected in this base class.
initCollections() and getId() abstract methods, that should be implemented by the beans that are who know the details of storage.
Public methods create(), update(), delete(), plus versions with the transport parameter that perform the main operations. These methods will check if transport and the id have been set, raising an exception otherwise.
Many methods in *Manager classes have been moved to the beans, but not the GET operations. A set of methods like getById() and getList(), maybe other versions with more parameters, will perform the basic functionality that is currenty in Manager classes.
More complex operations should be implemented in the beans when necessary.

Therefore, the api could be called using alternative ways, eg:
new User(transport).setXXX().setYYY.update()
new User().setXXX().setYYY().update(transport)

The amount of bean’s code would be reduced and transport related operations abstracted as most as possible.

using inheritance would remove a few lines, at the expense of making the code less flexible and much harder to change later.
overall, inheritance looks like a promising concept at first, but it is a  misleading pattern which I prefer to avoid as much as I can. composition over inheritance is all the rage these days, I would say.
inheritance  looks great in "Animal - Cat - etc" samples, but over time it grows into a cludgy monster with multiple methods like "not implemented" , "not relevant - ignore" , etc - because world is rarely strictly hierarchical, relationships between objects may change, and code needs to adapt sooner or later and inheritance model makes it much more expensive than composition approach.


[minor] Add config for concurrent_task in executor

Which issue does this PR close?
Closes #94.
What changes are included in this PR?

Are there any user-facing changes?

@andygrove PTAL 😊


This function px.features(gmt_file, correlationFolder) also throws the below error:

terminate called after throwing an instance of 'std::system_error'
what():  Resource temporarily unavailable
Running it on 20 core HPC.

This was resolved after removing the defined limitation on the user for the number of cores.


make ansible-operator does not download the correct asset

Bug Report
What did you do?
make ansible-operator
What did you expect to see?
bin/ansible-operator binary
What did you see instead? Under which circumstances?
$ cat bin/ansible-operator
Not Found

Environment
Operator type:
/language ansible
Kubernetes cluster type:
vanilla
$ ./bin/operator-sdk version
operator-sdk version: "v1.32.0", commit: "4dcbbe343b29d325fd8a14cc60366335298b40a3", kubernetes version: "1.26.0", go version: "go1.19.13", GOOS: "linux", GOARCH: "amd64"

Possible Solution
The makefile expects a release asset named ansible-operator_$(OS)_$(ARCH) but the assets are tars (example: ansible-operator-plugins_1.32.0_linux_amd64.tar.gz).
Please see the makefile template code:
https://github.com/operator-framework/ansible-operator-plugins/blob/cbc2d46705c5beee42021429630c2e184c1283b6/pkg/plugins/ansible/v1/scaffolds/internal/templates/makefile.go#L169
Cheers

I ran into the same issue. We would need to either change the .goreleaser.yaml file to build binaries for different CPU architectures or update the makefile target to download the tarball and extract the binary from the tarball before placing it in the bin directory in the operator directory.
From my perspective, having the binaries in the releases seems to make more sense. This has been the behavior for a while however, if there is value in changing to tarballs I am open to hear.


fop: clean up, make deterministic

Description of changes
This PR refactors the fop package.

Things done
Drop the explicit version of jdk: it will now use the latest jdk instead of jdk8 only.
Use finalAttrs instead of rec
Use hash instead of sha256 in fetcher
Add a patch, which makes the build deterministic.
Add the missing runHook calls.
Use makeWrapper instead of manually writing the script.
Changes made to meta

remove with lib;
add changelog
add myself to maintainers
use platforms from jre
(mostly) sort attributes alphabetically

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Thanks!


Automatically detect Strings

Instead of the user entering the names, the program should detect the strings in the binary file by itself.

8c4af0d84eae19352ddcb85f8f78b01340e04275 implements detection of names .bin files

.bin file types that still need to be added are the stations.bin and systems.bin.
Info about where those strings are located can be found here https://github.com/Ravernstal/gof2-bin-info

systems and stations bin support added in pull request
https://github.com/KroeteTroete/binmodder/pull/4
Now all that's left are the lang files

https://github.com/KroeteTroete/gofdetect can be used to automatically add lang file contents

agents.bin binTypes added in fe6f1d1