Create stress test

Is your feature request related to a problem? Please describe.
Current code is not following RabbitMQ client's recommended usage. There is a risk that in high concurrency scenario, the logs will get corrupted. However, it is unclear whether Serilog itself has any built-in synchronization mechanism that makes synchronizing usage of RabbitMQ client unneeded
Describe the solution you'd like
Create a stress test docker environment to show that the current code breaks, or doesn't
Describe alternatives you've considered
Just follow the recomended RabbitMQ client pattern without test
Additional context
https://www.rabbitmq.com/dotnet-api-guide.html#model-sharing

@huan086 With the knowledge that this Sink is being used in production in a high-volume setting, and not hearing any issues about the scenario that is described, it is my assesment that it is not something that needs to be adressed at this time. It's true that we could prove that the Sink performs in accords with the RabbitMq.Client specifications, but I doubt that has any value with respect to yours and my time.


Page doesn't address scenario for M365 Business Premium users

This scenario works for someone who does not have Windows 10 Pro license at all and needs to purchase a license. This does not work for an Azure AD user with Windows 10 Home device that has a M365 Business Premium subscription that includes Windows 10 Pro licensing. Users would end up paying $99 to upgrade when the license they already have should cover this.  Clicking Buy while logged in to the Microsoft Store as the Business Premium user still shows a $99 price point and attempts to get them to log in to a Microsoft account. This obviously won't work because a Microsoft account is different from an Azure AD account and has no rights to the business premium license that the user logged in to the Microsoft Store has.

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

ID: 4eabafd4-aa2e-d159-dad1-47a0e7d15b02
Version Independent ID: 4a9e22e9-eafb-bac6-851a-b1544dbf0b9b
Content: Upgrade Windows 10 Home to Windows 10 Pro
Content Source: microsoft-365/business-video/upgrade.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@cmcatee-MSFT Please help us in resolving this issue. Thanks

I've removed the table, and added a link to the OECD's site where they include a comprehensive list of TAX ID information.


[C++][Parquet] Remove deprecated IO classes and related functions

These were added almost a year ago, so there has been ample time for users to migrate
Reporter: Wes McKinney / @wesm
Assignee: Antoine Pitrou](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=apitrou) / @pitrou
PRs and other links:

GitHub Pull Request #9792

Note: This issue was originally created as PARQUET-1846. Please see the migration documentation for further details.

Antoine Pitrou / @pitrou:
Issue resolved by pull request 9792
https://github.com/apache/arrow/pull/9792


feat: insert event types experience levels tags and target groups in selectadd components on eventsettingsgeneral

List issues that are affected
see #362, #361 and #345

Closes #345


__dirname in dependency code resolves to .build/lib when the dependency is not listed in package.json

When building CDK code, we set all packages in package.json as esbuild externals. By doing this, __dirname in dependencies' code will resolve to the correct path b/c they are not bundled.
But if a package is package.json of a parent directory, it will be bundled, and __dirname resolves to .build/lib.
In Kujtim's case, he was using @aws-cdk/aws-certificatemanager, but he did not have the package in his package.json. The package is still found b/c it is a dependency of @serverless-stack/resources. The package hence was not bundled, and b/c the plugin creates a custom resource referencing Lambda code relative to __dirname, the code cannot be found.
Solution 1: traverse up the directory and include all packages in all package.json. But what if the package is not explicitly included in package.json? ie. @aws-cdk packages
Solution 2: exclude all modules in node_modules and parent's node_moduels. Does this work? How does this affect local modules?
Solution 3: Dax mentioned we might be able to turn off the esbuild bundle option.

Requested by Kujtim in slack

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Support React v16 when editor is focused after removed from DOM

Summary

calling Style.getScrollParent(editorNode) with null will result in an uncaught error
Ref#focus() is often called within a setTimeout (even in some example IIRC). Ref doesn't get GCd, but the DOM node it points to may no longer exist. Since React v16 is so blazing fast, it's possible that we're trying to focus something that no longer exists.
Without this bit of code, we'd have to call findDOMNode on the ref before calling focus. That's not great since putting findDOMNode is discouraged in application code.

Interesting - Seems like another option would be to release the timeout in componentWillUnmount, and that is generally what I would want to do.
That said, it looks like the main reason we added this invariant was to improve type strictness, and having an early return does the same thing effectively of validating the type before continuing execution.
I'm inclined to accept this, since I can't think of a big difference in effect between cleaning up the timeout on unmount and not throwing when it isn't cleaned up - but this way is more convenient for the engineer.
Adding this to my queue for merging - thanks @mattkrick !

Maybe it would be cleaner to return if !editorNode then keep the invariant? Then we'll notice more explicitly if that's no longer true rather then it silently failing.

Oh - I like that! Will revise this and re-rebase/etc. tomorrow. :)

i'm not sure i understand the change but as long as the function terminates without an error with the editorNode doesn't exist i'm happy!


Slack Block Kit API appears to cause issues in nlopes/slack

Describe the bug
Some Slack teams are starting to receive Slack event messages using the new Block Kit functionality (a WYSIWYG method for user text styling) that is causing issues in the nlopes/slack library (UnmarshallingErrorEvent). It appears that this may require an API breaking change to nlopes/slack in order to accommodate it. Teams have no control over whether or not their workspace has this feature enabled and so there is no suitable workaround today.
I am submitting this bug report to this repo because this issue is effecting matterbridge users and believe that noting the cause and being able to track the upstream issue may save other people time in troubleshooting.
nlopes/slack issue: https://github.com/nlopes/slack/issues/579
To Reproduce
There is currently no method of recreating this behavior on demand. One user (RAF in Discord) is affected and can reproduce at will, however, my own instance seems to be unaffected entirely.
Expected behavior
Messages should be relayed properly from Slack to other bridged destinations.
Screenshots/debug logs
Environment (please complete the following information):
Tested with 1.16.0 and 1.16.1 along with a custom build available at jheiselman/matterbridge which contains just a basic modification that helped to log the raw content of the message causing the issue.
Additional context

I've added a branch https://github.com/42wim/matterbridge/tree/f-slackunknown that contains a PR on slack/nlopes that should fix the issue.


Facebook Authentication button has no action in iOS 13.2.2

Step 2: Describe your environment

Swift 5.1
iOS version: 13.2.2
Firebase SDK version: 4.44.1
FirebaseUI version: 6.2.1
CocoaPods Version: 1.8.3

Step 3: Describe the problem:
Have been using FirebaseUI in my project for several iterations. This includes Google, Facebook and email authentication. Using the same build on iOS 13.2.2 and on iOS 12.4.1. On 12.4.1 I can tap on the Facebook button and properly authenticate using Facebook. On 13.2.2 nothing happens when I tap on Facebook button. No error, no output to debug console, not a single thing. Google and email buttons work as expected.
Steps to reproduce:

Install firebaseUI as instructed on Firebase UI instruction page
Setup Facebook, Google and email authentication
Run app on iOS 13.2.2 and tap on Facebook Button. Nothing happens

Observed Results:
Nothing. Ne error, now activity, no output on debug console
Expected Results:
*expect the app to start process of Logging in with facebook.

I have the same issue.
FirebaseUI version: 7.0.0
iOS version: 13.1.3

Hey, any news about this one? It is blocking my users from registering / logging in into my live app. At least is there any workaround I can apply for a quick fix?

What I tried is adding a FBLoginButton programmatically just to test if it would work but again it doesn't work on iOS 13. You probably saw what XCode prints out when testing on simulator but still:
-canOpenURL: failed for URL: "fbauth2:/" - error: "The operation couldn’t be completed. (OSStatus error -10814.)"

I have not seen any error messages at all.

Looks like that's kLSApplicationNotFoundErr, which either means you haven't installed the Facebook app on the target device or you're missing the LSApplicationQueriesSchemes defined in step 3 of Facebook's documentation.

Thank you fro that response. I do have the Facebook app installed on the device. LSApplicationQueriesSchemes was missing but when I added it, it had no effect. I have a second project that shows the same problem and I will add it there to see if it helps.

Looks like that's kLSApplicationNotFoundErr, which either means you haven't installed the Facebook app on the target device or you're missing the LSApplicationQueriesSchemes defined in step 3 of Facebook's documentation.

Yeah, I have them all set up and nothing. It doesn't make sense as it's working on iOS 12. Do you think there might be a connection between both issues: https://github.com/facebook/facebook-ios-sdk/issues/1067?

I have created a stripped down app that shows the problem. I have added a bunch of break points and when I step through those breakpoints I get the following output:
Connection Event: Remote host connection complete. Initiating SSL handshake.
Status code: 0
 Description: OK
Status code: 0
 Description: OK
SSHStatus: Sending local version: "SSH-2.0-IPWorks SSH Client 2020".
SSHStatus: Read remote version string: "SSH-2.0-OpenSSH_for_Windows_7.7".
SSHStatus: Beginning key exchange
SSHStatus: Preparing algorithm negotiation.
SSHStatus: Sending local enabled algorithm list.
SSHStatus: Local Key Exchange Algorithms:
    Key exchange algorithms:
        curve25519-sha256,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
        diffie-hellman-group14-sha1,
        diffie-hellman-group14-sha256,
        diffie-hellman-group1-sha1,
        diffie-hellman-group-exchange-sha256,
        diffie-hellman-group-exchange-sha1,
        diffie-hellman-group16-sha512,
        diffie-hellman-group18-sha512,
        ecdh-sha2-nistp256,
        ecdh-sha2-nistp384,
        ecdh-sha2-nistp521
    Server host key algorithms:
        ssh-ed25519,
        ecdsa-sha2-nistp256,
        ecdsa-sha2-nistp384,
        ecdsa-sha2-nistp521,
        ssh-rsa,
        ssh-dss,
        x509v3-sign-rsa,
        x509v3-sign-dss
    Encryption algorithms:
        aes256-ctr,
        aes192-ctr,
        aes128-ctr,
        aes256-cbc,
        aes192-cbc,
        aes128-cbc,
        3des-ctr,
        3des-cbc,
        blowfish-cbc,
        arcfour256,
        arcfour128,
        arcfour,
        cast128-cbc,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>    MAC algorithms:
        hmac-sha2-256,
        hmac-sha2-512,
        hmac-sha1,
        hmac-md5,
        hmac-ripemd160,
        hmac-sha1-96,
        hmac-md5-96,
        hmac-sha2-256-96,
        hmac-sha2-512-96,
        hmac-ripemd160-96,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>    Compression algorithms:
        none,
        zlib
SSHStatus: Reading remote enabled algorithm list.
SSHStatus: Remote Key Exchange Algorithms:
    Key exchange algorithms:
        curve25519-sha256,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
        ecdh-sha2-nistp256,
        ecdh-sha2-nistp384,
        ecdh-sha2-nistp521,
        diffie-hellman-group-exchange-sha256,
        diffie-hellman-group16-sha512,
        diffie-hellman-group18-sha512,
        diffie-hellman-group14-sha256,
        diffie-hellman-group14-sha1
    Server host key algorithms:
        ssh-rsa,
        rsa-sha2-512,
        rsa-sha2-256,
        ecdsa-sha2-nistp256,
        ssh-ed25519
    Encryption algorithms:
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
        aes128-ctr,
        aes192-ctr,
        aes256-ctr,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>    MAC algorithms:
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
<EMAIL_ADDRESS><EMAIL_ADDRESS>,
        hmac-sha2-256,
        hmac-sha2-512,
        hmac-sha1
    Compression algorithms:
        none
SSHStatus: Selected key exchange algorithm: "curve25519-sha256".
SSHStatus: Selected server host key algorithm: "ssh-ed25519".
SSHStatus: Selected client encryption algorithm: "aes256-ctr".
SSHStatus: Selected server encryption algorithm: "aes256-ctr".
SSHStatus: Selected client MAC algorithm: "hmac-sha2-256".
SSHStatus: Selected server MAC algorithm: "hmac-sha2-256".
SSHStatus: Selected client compression algorithm: "none".
SSHStatus: Selected server compression algorithm: "none".
SSHStatus: Algorithm negotiation complete.
SSHStatus: Sending ECDH key exchange initialization request.
I get a crash after the last line above.
Thread 1: EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
I will zip up and send the test app when I have finished cleaning it up.
Regards,
<EMAIL_ADDRESS><EMAIL_ADDRESS>On Nov 14, 2019, at 9:48 AM, Morgan Chen<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
Looks like that's kLSApplicationNotFoundErr, which either means you haven't installed the Facebook app on the target device or you're missing the LSApplicationQueriesSchemes defined in step 3 of Facebook's documentation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
http://schema.org

@SAPIENTechnologies If you can share the stack trace of the crash that would also be helpful. It looks like it's a different issue than the one @flashadvanced is describing.
To clarify if it's a FirebaseUI issue, are you able to sign into Facebook without using the Firebase SDK?

Sorry. I posted that to the wrong location. That is another problem that is unrelated.

To clarify if it's a FirebaseUI issue, are you able to sign into Facebook without using the Firebase SDK?

Yeah, as I posted I tested with creating a Fb button (FBSDKLoginButton) programmatically and it behaved the same way as the fb button added automatically by FirebaseUI. So I guess this have to be a Facebook issue. I disabled the Fb login for now.

Thanks all, we'll keep this open to track the Facebook issue and then update our podspec when a fix is released.
In the meantime you can also try testing older versions of the FBSDKLoginKit framework to see if the issue isn't reproducible on an older version.

Still broken
Real Device with iOS 12.3.2 = OK
iOS Simulator 13.3 = Failed

What Facebook SDK versions are you using? For me, same error was resolved when I updated Facebook SDK to 5.13.1.
I was using Facebook SDK 5.4.0 version which worked fine until iOS 13, and I had to update SDK in order for facebook button to work again.


Path to build file after unzip

Need to resolve the issue where the package manager is hard coding the current working directory as /home/USRPRF. You should use https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/getpwnam.htm (getpwnam() API) to retrieve the working path for the user profile and set accordingly. A number of people have stumbled over this already.

Liam, here is some c code I use when building profile create strings.
pd = getpwnam(New_Prf);
if(pd == NULL) {
/* no directory just return */
sprintf(msg_dta,"%s",strerror(errno));
snd_msg("GEN0001",msg_dta,strlen(msg_dta));
return 1;
}
else {
strcat(Command," HOMEDIR('");
strcat(Command,pd->pw_dir);
strcat(Command,"')");
}

Hi @ChrisHird - thanks for raising this.
I understand that it had caused an issue with a few people now (you and @getfoundational), but it should be fixed.
All I had to do with remove the hard-code of the users home directory - then it will work with whatever the users real current directory is.
The relevant commit is fc8960321e5256bd01c319aa9c6e3a7b4710d163.
You can either rebuild from the master of the repo, or this patch will be available in Relic 0.006
Please close when you feel necessary. :)

Liam
My preference would be to allow the root to be set, not force it into the users home directory. That way if you are required to install Open Source in a specific root you can manage that without going to your profile and setting it there before running the commands then changing it back.  Make sense?

Another thought, think about the consequences of deleting a user profile, you could delete all of the downloaded source??

Okay @ChrisHird
Perhaps we could add an extra parameter so the user could chose where to store the ZIP and source?

Looks like this issue has been fixed for a while.
You can now simple change your current directory and the package will be downloaded and unzipped there.
I will now close this issue.


Persistent tethering state when reboot

In this feature i was added the Hotspot state when boot, in last version u did always turn on hotspot when Comma reboot, now the comma boot with last state of tethering.
The code try bring the very simple solution to this feature.
Thx

Thanks for the PR!
0.8.14 branches are no longer maintained. I'll have this feature implemented in the latest test-c3 branch with credits.


syz-ci: optionally publish GCS objects

Earlier syz-ci: don't publish uploaded files commit completely disabled the GCS object publishing after each object.
However, it turns out that otherwise the objects quickly lose the public to internet flag.
Make the option configurable.

Thank you!

Seems like I still see 403's when trying to fetch
ci-qemu-upstream-corpus.db (haven't done exhaustive testing for all bucket
objects). Is the change going to reflect from the next deployment, i.e
tomorrow?
Palash
On Mon, May 15, 2023 at 1:45 AM Aleksandr Nogikh @.***>
wrote:

Merged #3894 https://github.com/google/syzkaller/pull/3894 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/google/syzkaller/pull/3894#event-9243843881, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABRCDXEX7457UQPH2HH6ULLXGHUI5ANCNFSM6AAAAAAX7NFYS4
.
You are receiving this because you commented.Message ID:
@.***>

Yes, syz-cis need to restart and we also upload the corpus only after several hours of running.


How to use feature DrillDown in Apache Superset?

I am trying to use the DrillDown feature of superset without knowing how to install it? Anyone who knows the answer or has already used this feature, please give feedback for me. I would like to thank you.

There was a webinar this week that covered everything you'd want to know about drilling in Superset: https://www.youtube.com/watch?v=GrlRuOELJRw

I am trying the "Drill to detail" feature in 2.1.0 release candidate 2 and it's nice.  You might also be interested in cross-filtering: https://preset.io/blog/cross-filtering-in-Superset-and-Preset/.
To install you'd install 2.1.0 once it's released (soon), then enable the DRILL_TO_DETAIL feature flag.

I am trying the "Drill to detail" feature in 2.1.0 release candidate 2 and it's nice. You might also be interested in cross-filtering: https://preset.io/blog/cross-filtering-in-Superset-and-Preset/.
To install you'd install 2.1.0 once it's released (soon), then enable the DRILL_TO_DETAIL feature flag.

Thanks for your answer. But I want to use Superset's Drilldown and the two features you say, I have finished setup and use it ok.

It sounds like this answered your question about drilling.  If you have a question related to installation and usage, I'd suggest posting that as a Github "discussion" post or joining the Slack chat and asking there.


Warning: Failed prop type: Invalid prop transKey of type object supplied to SlideTransition, expected string.

Environment

Tech
Version

material-ui-pickers
1.0.0-rc.13

material-ui
1.5.1

React
16.4.2

Browser
Chrome  68.0.3440.106 64bit

Platform
Windows 10 client pc, linux centos server

Peer library
Moment 2.22.2

babel
@babel/runtime 7.0.0-beta.54 and 55

Steps to reproduce

Copied date picker code for keyboard input
Load site and clicked on the icon button.
The warning appears only once. At every refresh.
Note: this doesn't occur if I pass openToYearSelection to true.

Expected behavior
No warnings.
Actual behavior
Warning: Failed prop type: Invalid prop `transKey` of type `object` supplied to `SlideTransition`, expected `string`.
    in SlideTransition (created by WithStyles(SlideTransition))
    in WithStyles(SlideTransition) (created by CalendarHeader)
    in div (created by CalendarHeader)
    in div (created by CalendarHeader)
    in CalendarHeader
    in WithUtils(CalendarHeader) (created by WithStyles(WithUtils(CalendarHeader)))
    in WithStyles(WithUtils(CalendarHeader)) (created by Calendar)
    in Calendar
    in WithUtils(Calendar) (created by WithStyles(WithUtils(Calendar)))
    in WithStyles(WithUtils(Calendar)) (created by DatePicker)
    in DatePicker
    in WithUtils(DatePicker) (created by RenderPropsComponent)
    in div (created by DialogContent)
    in DialogContent (created by WithStyles(DialogContent))
    in WithStyles(DialogContent) (created by ModalDialog)
    in div (created by Paper)
    in Paper (created by WithStyles(Paper))
    in WithStyles(Paper) (created by Dialog)
    in Transition (created by Fade)
    in Fade (created by WithTheme(Fade))
    in WithTheme(Fade) (created by Dialog)
    in RootRef (created by Modal)
    in div (created by Modal)
    in Portal (created by Modal)
    in Modal (created by WithStyles(Modal))
    in WithStyles(Modal) (created by Dialog)
    in Dialog (created by WithStyles(Dialog))
    in WithStyles(Dialog) (created by ModalDialog)
    in ModalDialog (created by WithStyles(ModalDialog))
    in WithStyles(ModalDialog) (created by ModalWrapper)
    in ModalWrapper (created by RenderPropsComponent)
    in RenderPropsComponent (created by withHandlers(RenderPropsComponent))
    in withHandlers(RenderPropsComponent) (created by lifecycle(withHandlers(RenderPropsComponent)))
    in lifecycle(withHandlers(RenderPropsComponent)) (created by withState(lifecycle(withHandlers(RenderPropsComponent))))
    in withState(lifecycle(withHandlers(RenderPropsComponent))) (created by BasePicker)
    in BasePicker
    in WithUtils(BasePicker) (created by DatePickerWrapper)
    in DatePickerWrapper (created by ForwardRef)
    in div (created by PageHome)
    in PageHome (created by Route)
    in div (created by Mutation)
    in div (created by Mutation)
    in div (created by Mutation)
    in Mutation (created by CompNav)
    in CompNav (created by WithStyles(CompNav))
    in WithStyles(CompNav) (created by WithTheme(WithStyles(CompNav)))
    in WithTheme(WithStyles(CompNav)) (created by Connect(WithTheme(WithStyles(CompNav))))
    in Connect(WithTheme(WithStyles(CompNav))) (created by Route)
    in Route (created by withRouter(Connect(WithTheme(WithStyles(CompNav)))))
    in withRouter(Connect(WithTheme(WithStyles(CompNav)))) (created by withCookies(Component))
    in withCookies(Component) (created by Route)
    in div (created by Route)
    in Transition (created by Fade)
    in Fade (created by WithTheme(Fade))
    in WithTheme(Fade) (created by Route)
    in Route (created by PrivateRoute)
    in PrivateRoute (created by AppRoutes)
    in Switch (created by AppRoutes)
    in AppRoutes (created by Route)
    in Route (created by withRouter(AppRoutes))
    in withRouter(AppRoutes)
    in App (created by WithRoot)
    in MuiPickersUtilsProvider (created by WithRoot)
    in MuiThemeProvider (created by WithRoot)
    in WithRoot (created by Query)
    in Query (created by Apollo(WithRoot))
    in Apollo(WithRoot) (created by Connect(Apollo(WithRoot)))
    in Connect(Apollo(WithRoot)) (created by Route)
    in Route (created by withRouter(Connect(Apollo(WithRoot))))
    in withRouter(Connect(Apollo(WithRoot)))
    in I18nextProvider
    in CookiesProvider
    in Router (created by ConnectedRouter)
    in ConnectedRouter
    in ApolloProvider
    in Provider
    in Provider

Live example
https://codesandbox.io/s/v3n19r93z3

I have exactly the same issue

I have the same Issue,
On my end, openToYearSelection does not actually fix it once you select a year.

I have the same problem, but in my setup it says ‘date’ instead of ‘object’.

I am getting the same error after update to rc13.

Same issue after updating.

Same, fresh install and copied example straight from docs.

resolved warning by setting prop openTo="date"

Unless I'm missing something more fundamental, the error seems pretty clear: the transKey prop on the SlideTransition components in Calendar.jsx and CalendarHead.jsx are Date objects(the currentMonth var) when they should be strings. Can be fixed by setting the transKey values with .toString() since the prop-types require strings. Not sure that this is the "proper" resolve though!
Also, I am having difficulty with changing the format value that the date returns. It returns a Date object no matter what where previously I was able to return a string or custom format. Possibly related to this issue?

Could there be a fast fix? I think the toString() fix should be sufficient.

I'm waiting for this to be solved as well, . Do you think this can be included soon on a release candidate? Or should I go for a fork for now?

@andres-amor This will be fixed in the next release. Tomorrow I hope

Fixed in rc.14

@mberneti impossible.
Can you reproduce that on code sandbox?

@dmtrKovalenko thank u, that's fixed in rc.14 👍
some sort of caching of the rc.13 version was the reason of my application error.


Issue with func named get

Godot version:
3.2.3
OS/device including version:
PC / W10
Issue description:
If using a function named 'get' in script extending Reference, the parser throws an error unless an arg exists.
error(4,1) Parser Error: Function signature doesn't match the parent. Parent signature is: "Variant get(String)".
Steps to reproduce:
using test.get("nothing") with func get(nothing): works fine, but using test.get() with func get(): throws an error.
Minimal reproduction project:
get_bug_maybe.zip

That's because get is a name of a built-in function of Object, which each class extends. And it expects a single argument of the type String.
https://docs.godotengine.org/en/stable/classes/class_object.html#id1

That's because get is a name of a built-in function of Object, which each class extends. And it expects a single argument of the type String.
https://docs.godotengine.org/en/stable/classes/class_object.html#id1

Closing per @pycbouh's comment.

Closing per @pycbouh's comment.

That's because get is a name of a built-in function of Object, which each class extends. And it expects a single argument of the type String.
https://docs.godotengine.org/en/stable/classes/class_object.html#id1
When reimplementing built-in functions you must use the same signature.

According to the docs only _get() can be overridden, so surely the fact it's letting me override get() as long as I pass a variable is a bug. The editor should throw an error and stop me.

That's because get is a name of a built-in function of Object, which each class extends. And it expects a single argument of the type String.
https://docs.godotengine.org/en/stable/classes/class_object.html#id1
When reimplementing built-in functions you must use the same signature.

According to the docs only _get() can be overridden, so surely the fact it's letting me override get() as long as I pass a variable is a bug. The editor should throw an error and stop me.

@dt192 Every method can be overridden. _get() is a virtual method and can be implemented, which is not the same. You can override get(), but you need to give it the same signature as the original method. You can then call the original method from within your reimplementation by using the parent class accessor .:
func get(property_name : String):
  return .get(property_name)

This can be used to preserve the default functionality while extending it, instead of replacing it. Virtual methods, on the other hand, are used to implement specific functionality within each individual class with no relation to the parent. Usually, the engine itself calls them in a very specific way.

@dt192 Every method can be overridden. _get() is a virtual method and can be implemented, which is not the same. You can override get(), but you need to give it the same signature as the original method. You can then call the original method from within your reimplementation by using the parent class accessor .:
func get(property_name : String):
  return .get(property_name)

This can be used to preserve the default functionality while extending it, instead of replacing it. Virtual methods, on the other hand, are used to implement specific functionality within each individual class with no relation to the parent. Usually, the engine itself calls them in a very specific way.


EDFI-2342 Upload all the 5x and 6x Data Import Templates into Exchange

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing this PR because the commit wasn't signed, see comments in https://tracker.ed-fi.org/browse/EDFI-2342 for details on how to set up commit signing


Integration ROS/ROS2 agents

This PR adds beta support for the usage of ROS1/ROS2 agents in the leaderboard. Currently, the supported ROS versions are:

ROS1 melodic
ROS1 noetic
ROS2 foxy

The integration uses the CARLA ROS bridge package to manage the creation/destruction of sensors and the sensor data publication.
Code structure

ROSBaseAgent: This is the base ROS agent. User should not inherit from this class. This base agent contains shared functionality between ROS1 and ROS2 agents.

ROS1Agent: ROS1 agents should inherit from this class. It uses roslibpy and rosbridge-server to communicate with the ROS environment.

ROS2Agent: ROS2 agents should inherit from this class. It creates a node using rclpy to communicate with the ROS environment.

ROSAgentWrapper: Agent wrapper for ROS agents. This wrapper is responsible for calling the /carla/spawn_object and /carla/destroy_object ROS services to spawn/destroy the agent sensors.

Additionally, the scenario/agent setup code has been reorganized to avoid ticking the CARLA server once the agent is initialized.
Dockerfile
A new dockerfile (Dockerfile.ros) has been provided to build ROS based images. Also, the make_docker.sh has been updated to this end. To create a ROS based image use:
./make_docker.sh --ros-distro melodic

with the desired ROS distribution. If no distribution is provided, the "normal" pipeline is applied.
Team code
For ROS agents, it is assumed that the team code root folder is a ROS workspace containing all the necessary packages.
<TEAM_CODE_ROOT>
|__ src
    |__ pakcage1
    |__ package2
    |__ ...

Additionally, ROS agents must provide a ROS entry point to executed the agent.
class MyRosAgent(ROS1Agent):
    ....
    def get_ros_entry_point(self):
        return {
            "package": "my_ros_agent",
            "launch_file": "my_ros_agent.launch",
            "parameters": {}
        }

This change is

Hello,
I have some questions:
Q1:

when using ros, I export the 2.7 carla egg , then I have to modify the run_evaluator.sh
I replace python3 with python2 , otherwise it crashes , when submitting my docker file, will that be a problem ?

Q2:

ros_base_agent and ros1_agent initializes and uses carla_ros_bridge, what if I don't want to use carla_ros_bridge at all

Q3:

I would like an agent example such as ros_agent.py , that enables ROS1 and Python 2.7, and runs the team_agent using the "start.sh" file.

Comment: Related to the LIDAR reading frequency.

rotation_frequency of the sensor is "10" by default. and points_per_second is "600000"
when data is read at 20hz, only half scan is returned.
I fixed this by increasing rotation_frequency to "20" and points_per_second to "1200000"

if you want to check my modifications:
https://github.com/hatem-darweesh/leaderboard
Regards,

Hi @hatem-darweesh ,
Thank you for the feedback!

Q1:

when using ros, I export the 2.7 carla egg , then I have to modify the run_evaluator.sh
I replace python3 with python2 , otherwise it crashes , when submitting my docker file, will that be a problem ?

The leaderboard is only targeting Python3. Even if you modify the leaderboard, it will be replaced with the original one once it is submitted. Therefore, your original issue will appear on the cloud, even if you upload a docker image with a modified version of the leaderboard.
In order to support agents based on ROS melodic (which is targeting Python2), the current ROS-leaderboard integration is using roslibpy for ROS1 based agents. This library allows to interact with ROS without requiring the creation of a specific ROS node and therefore avoid the Python2-Python3 problem.
ROS melodic based agents can still be programmed normally using Python2. Moreover, the CARLA PythonAPI is available for Python2 and Python3 in the resulting Docker image (https://github.com/carla-simulator/leaderboard/blob/glopez/initialization_reordered/scripts/Dockerfile.ros#L97)

Q2:

ros_base_agent and ros1_agent initializes and uses carla_ros_bridge, what if I don't want to use carla_ros_bridge at all

I would like to receive some more feedback about this. In which situations you would want to avoid the usage of the CARLA ROS bridge? In the end, the CARLA ROS bridge is doing nothing but publishing the sensor data and managing the creation and destruction of sensors.

Q3:

I would like an agent example such as ros_agent.py , that enables ROS1 and Python 2.7, and runs the team_agent using the "start.sh" file.

The way to execute ROS based agents on the ledearboard has slightly changed. Here you can see a dummy agent for the leaderboard using ROS melodic: https://github.com/joel-mb/leaderboard-ros-agent

Comment: Related to the LIDAR reading frequency.
rotation_frequency of the sensor is "10" by default. and points_per_second is "600000"
when data is read at 20hz, only half scan is returned.
I fixed this by increasing rotation_frequency to "20" and points_per_second to "1200000"

Yes. This is already known and these values are fixed for the leaderboard.

Thanks @joel-mb ,
That was really helpful.
I tried the dummy agent, and I get the system to work. still need to source my ros agent correctly. but no python issues :)
I will wait until this PR is accepted and will submit my agent.
Thanks again,

@hatem-darweesh thanks again for the feeback!

still need to source my ros agent correctly. but no python issues :)
How are you building your image? Are you using the provided Dockerfile.ros file as a template (https://github.com/carla-simulator/leaderboard/blob/glopez/initialization_reordered/scripts/Dockerfile.ros)? The sourcing should be done automatically, assuming that the team code root folder is a ROS workspace containing all the necessary packages. So for the dummy_agent the team code root folder should be something like:

<TEAM_CODE_ROOT>
|__ my_ros_agent.py
|__ src
    |__ dummy_agent
        |__ ...

And your TEAM_AGENT variable ${TEAM_CODE_ROOT}/my_ros_agent.py
We still need to properly document this.


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: LokeshVarman sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


part_of link for new term GO:1905324

I have just added these in TermGenie:
ID: GO:1905323 Label: telomerase holoenzyme complex assembly
ID: GO:1905324 Label: telomere-telomerase complex assembly

I think the second term, GO:1905324, can be part_of GO:0032200 ! telomere organization. I can't imagine the complex forming in any context that isn't connected with telomere organization.
Two has_part links may also work, but I'm less sure:
GO:0032203 telomere formation via telomerase
has_part GO:1905324

GO:0007004 telomere maintenance via telomerase
has_part GO:1905324

I think the complex would need to form for either process.

I'll add this and wait for additional input on the has_part suggestions.
GO:1905324,  part_of GO:0032200 ! telomere organization

OK, thanks. I'll ask a couple of experts (who have just sent in community curation, which prompted all this and some FYPO work) about the has_parts.

Last week I heard back from one of the experts I asked (Forgot to update this ticket) …
me:
We have a somewhat general question about telomere biology: is formation of the complex of telomere and telomerase involved in both the initial formation of a telomere and in any subsequent extension by telomerase? The answer will help the GO curators represent this accurately in the ontology.
Feng Qiao:
YES
so it looks like the has_part links would be OK.

Ok done!


cargo sqlx prepare --check breaks within CI pipeline

I'm trying to build CI pipeline on Gitlab with sqlx build time checks using offline mode. Locally it's working fine and there is no any local db running, but in pipeline I have got this error
error: error communicating with database: Cannot assign requested address (os error 99)
  --> src/database.rs:60:25
   |
60 |         let positions = sqlx::query_as!(DbStoredPosition, "SELECT * FROM positions")
   |                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: this error originates in the macro `$crate::sqlx_macros::expand_query` (in Nightly builds, run with -Z macro-backtrace for more info)

It breaks with this .gitlab-ci.yaml:
image: "rust:latest"

default:
  tags:
    - development

  before_script:
    - rustc --version
    - cargo --version

stages:
  - build
  - test

build-binary:
  stage: build
  script:
    - cargo install --version=0.5.11 sqlx-cli
    - cargo sqlx prepare --check -- --lib

and .env:
SQLX_OFFLINE=true
DATABASE_URL=postgres://postgres:password@localhost:5432/db

offline feature in Cargo.toml also added.
cli and lib versions are the same.
Am I doing something wrong?

I've seen an error like this before. It has something to do with URLs like http://, mysql://, postgres:// that are not recognized on the used image. Maybe the environment variables were not loaded correctly in the CI pipeline? Or try building on an other image image: "ubuntu-latest".

But I believe it should not try to connect to the database anyway

cargo sqlx prepare --check does want to connect to the database; it's meant to ensure that the sqlx-data.json is up to date with the database schema.
If you just want to make sure your project builds in offline mode, just cargo check should suffice.

Ok, thank you for the answer. I just thought that migrations files would be enough for the check.

Here is the error code.
#0 124.7 error: error communicating with database: Cannot assign requested address (os error 99)
#0 124.7   --> src/persistance/answers_dao.rs:34:22
#0 124.7    |
#0 124.7 34 |           let record = sqlx::query!(
#0 124.7    |  ______________________^
#0 124.7 35 | |             r#"
#0 124.7 36 | |                 INSERT INTO answers ( question_uuid, content )
#0 124.7 37 | |                 VALUES ( $1, $2 )
#0 124.7 ...  |
#0 124.7 41 | |             answer.content
#0 124.7 42 | |         )
#0 124.7    | |_________^
#0 124.7    |
#0 124.7    = note: this error originates in the macro `$crate::sqlx_macros::expand_query` which comes from the expansion of the macro `sqlx::query` (in Nightly builds, run with -Z macro-backtrace for more info)
#0 124.7
#0 124.7 error: error communicating with database: Cannot assign requested address (os error 99)
#0 124.7   --> src/persistance/answers_dao.rs:73:23
#0 124.7    |
#0 124.7 73 |         let records = sqlx::query!("SELECT * FROM answers WHERE question_uuid = $1", question_uuid)
#0 124.7    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#0 124.7    |
#0 124.7    = note: this error originates in the macro `$crate::sqlx_macros::expand_query` which comes from the expansion of the macro `sqlx::query` (in Nightly builds, run with -Z macro-backtrace for more info)

As a heads up neither the touch nor env var are necessary. cargo sqlx prepare handles both of those for you

As a heads up neither the touch nor env var are necessary. cargo sqlx prepare handles both of those for you

For me, it did not on ubuntu 22.04 box. Had to run touch.


Determine value of range based loops

Such as for 0..100

Most likely naturally follows #97

for(var i = 0; i < 10; i+=1) could become range (10) {}
and step size being for(var i = 0; i < 10; i+=2) range (10,2) {}
with options for starting value of non 0 being for(var i = 1; i < 11; i+=1) range (1,11,1) {}

Ranges would be fixed count, where loop over native list is dynamic count.

Range will still need to be able to provide a name for the index, so a full delcare might need something like range (i,0,10,1) {} makes this tricky

Yep, hit this enough that it would be nice to simply range 3 {} or repeat spawnCount {}

This would now be sugar that degrades to a for loop.


Slow AdminClient responses leading to timeouts and failures

We have an MSK cluster with ~1750 topics and ~550 consumer groups, as well as a self hosted Kafka Connect deployment using this instance.  Upon enabling MSK IAM Auth within Kafka Connect, Kafka Connect started failing. Via the logs we discovered that the listTopics API call was timing out (the timeout is 30 seconds, which I believe is the default).
I built a small test application to execute listTopics, listConsumerGroups, and describeCluster APIs using the Kafka AdminClient to see if the issue was specific to kafka connect or more generalized.  In the test app I observed the same timeouts, with the listTopic API call needing about 35 seconds to return.
Subsequent executions of these API calls return much faster (if the connection is reused) and leads me to believe there's caching going on internally.
The question is if this behavior expected and typical? I'd prefer not have to monitor and continually increase the timeouts as the number of topics in the cluster increases, to not mask actual underlying issues by setting large timeouts, nor have such slow responses in general.  Further, is there anything I can do on my end config wise to avoid this slow start behavior?
Here's some approximate timing data for reference:

API Call
Duration
Authentication Type

describeCluster
~50ms
Plaintext

describeCluster
2s
MSK

listConsumerGroups
~300ms
Plaintext

listConsumerGroups
10s
MSK

listTopics
~450ms
Plaintext

listTopics
35s
MSK

This is a known issue for which we have a fix in place, currently undergoing deployment. The response time after the fix is applied will be much smaller and therefore unlikely to result in timeouts.
Please open a support case with MSK, so we can apply the fix to your cluster.

Thanks.  I'll open a new support ticket and reference your reply.  FWIW my existing case has been making no progress for ~6 weeks and there's apparently a lack of internal knowledge of this issue/fix.

I'm affected by this issue too. Do you have an ETA for the fix for all customers?

I'm affected by this issue too. Do you have an ETA for the fix for all customers?

We'll try to complete deployment by end of this week (Jul 8th). Please open a support case with MSK, so we can apply the fix to your cluster.

Thanks a lot for your information. We have decided to wait for the fix to be deployed to all customers, instead of raising at ticket.

The deployment is complete. The fix will now apply for new clusters created from this point onwards. For existing clusters, open a support case with MSK, so we can apply the fix to your cluster. FYI @rmetzger.

Oh, good to know. Thank you!

Sorry for going really off-topic: Is there a way to open a support case without buying the Developer support plan?

To close this out, I can confirm that the fix did solve the issue for us.
If anyone else requires this patch, I was requested to supply an update window between 10AM-5PM UK/BST time. It took ~1 week to get to this point, and another for the patch to be applied, so I'd suggest providing this information upfront for faster turn around.
Also, I had hoped the patch would be automatically applied during routine security patching of the clusters. At least for our production clusters, it was not automatically applied and will require another support ticket (we've only updated some non-production clusters thus far).


Delete Item (Vendors inventory)

Mutation made and working

ToDO: ensure users wishlist/carts are refetched whenever logged in. Even with deleted item being successfully removed from the users cart drawer, the cart count (top alert) still shows as if the deleted item is in the cart... until manually refreshed

In vendor inventory, able to delete the selected item from the vendors inventory.

To do:

Ensure users cart (drawer badge) is being updated right away too. At the moment, after logging in to the user, I have to manually refresh in order to see the accurate cart number.
Add ability to delete multiple items selected at the same time.


TCP Access Logging in Telemetry v2

Describe the feature request
Mixer had the ability to report log event with connection state (connection.event - open, continue, close), when moving to Telemetry v2 we lost the ability to get the connection state.
Currently Istio have access log for TCP only on Stackdriver.
The request is to be able to get TCP connection state when Telemetry v2 is on.
Describe alternatives you've considered
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[X ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

@douglas-reid should it be closed?

Hi @mandarjog & @douglas-reid, shall we move this issue to 1.12? or close it?

Moved to 1.12.


Azure OpenAI Support?

I tried to override  openai config the base url like this:
     const configuration = new Configuration({         basePath: "https:/xxx.openai.azure.com/openai/deployments/demo",         apiKey: process.env.AZURE_OPENAI_API_KEY,       });
But no luck. Any suggestions would be appreciated.

This works for me:
{
  basePath: "https://xxx.openai.azure.com/openai/deployments/xxx",
  baseOptions: {
    headers: { "api-key": env. AZURE_OPENAI_API_KEY },
    params: {
      "api-version": "2023-03-15-preview",     // https://oai.azure.com/portal/chat
    },
  },
}


ci: Add pull request template and run commitlint on PR title only

We now ensure the conventional commits format only on PR titles and not on
commits to let developers keep commit messages targeted for other developers
i.e. describe actual changes to code that users should not care about.
And PR titles, on the contrary, must be aimed at end users.
For more info, see
https://linux-system-roles.github.io/contribute.html#write-a-good-pr-title-and-description
Signed-off-by: Sergei Petrosian<EMAIL_ADDRESS>

And PR titles, on the contrary, must be aimed at end users.

Hmm? I don't understand this, can you please describe it?

I am sorry for a lot of noise on this, turned out that how I planned it initially does not work so good, so I am applying more changes. I'll send an email on this soon.
The drawback of the previous approach is that each commit must go to the changelog, but developers write commit messages for other developers, not for end users. You want the commit to state clear why the code was change, and often commit messages include information that end users do not care about. So it makes more sense to keep commit messages for developers, and move the user-aimed information in PR description and title.


⚠ Spryr has degraded performance

In e355703, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3849 ms

Resolved: Spryr performance has improved in b8e4a5d after 7 minutes.


API object head - set status code after headers

Making sure we set the status code after headers before the body

Oh well, maybe the next language will do type-safe I/O correctly.

This will be interesting...
Note that the above change is just cosmetics as the previous function doesn't write any body in case of nil. But when I went over the code I was thinking of adding return because this is what I expected after a call to write response.


"Error parsing date/time value" hiding \DateTime exception.  TimeZone Not Set in php.ini

As a Newbie to Propel.  My second attempt to read from the database threw an exception ""Error parsing date/time value"
The problem is Propel hides the underlying exception from \DateTime.  Which stated to set my php.ini\timezone.   This may be a PHP_unit bug of not printing the underlying exception.  I looked at the code and it is passing the underlying exception but it is not displaying in the php_unit output.  See https://github.com/propelorm/Propel2/blob/master/src/Propel/Runtime/Util/PropelDateTime.php  line 98.
Maybe some other Newbie will read this and save themselves a headache.
Bottom line:  In PHP 5.5 if you are using the base php \DateTime object the timezone must be set either in the php.ini or using date_default_timezone_set() .

I just had this exact same problem.  This exception on line 96 should be handled better.


QAmode for get-offers call

Hi all,
I'd like to ask about NodeJS SDK https://adobetarget-sdks.gitbook.io/docs/sdk-reference-guides/nodejs-sdk/get-offers
I can't find the property field QAmode, but I can find this property for Java SDK simultaneously.
I we look into NodeJS, the type definition for QAmode is presented https://github.com/adobe/target-nodejs-sdk/blob/46c378b17a6533fa93b6652daed0d09a6be35b61/packages/target-tools/delivery-api-client/models/QAMode.d.ts
Is it a mistake and we can wait for the fix in the next version? Or it's a permanent solution to skip QAmode at all
Thank you.

Hi @andrei-svistunou, QAMode is supported in the NodeJS sdk.  It can be used by passing in a qaMode object as described in the Delivery API documentation.
Here is an example:
const client = TargetClient.create({
        client: "myAdobeClientId",
        organizationId: "ABCDEFG@AdobeOrg"
});

const result = await client.getOffers({
              request: {
                id: {
                  tntId: "338e3c1e51f7416a8e1ccba4f81acea0.28_0"
                },
                context: {
                  channel: "web"
                },
                prefetch: {
                  mboxes: [{ index: 0, name: "demo-marketing-offer1" }]
                },
                qaMode: {
                  token: "QCfbJvlzWVIdSjvDOUtz+J7srqQZYj1dadvKwaf8yb8=",
                  listedActivitiesOnly: true,
                  previewIndexes: [
                    {
                      activityIndex: 1,
                      experienceIndex: 2
                    }
                  ]
                }
              }
            });

Using QA mode, this request always returns experience 2 for the activity.


Scoreboard package stuff

Stuff from the scoreboard package from #1956
This is the twentieth of the follow ups from that, dividing into top level packages
#2000 pog

#2000 🚀

#2000 🚀


Use buffering for HTTP responses on chunked requests

For non-chunked requests, the request is performed using the 'urlopen'
method that underlying uses buffering for the HTTP responses (for Python
2.7+ versions). For chunked requests though, the request is made via a
different code path and so the 'getresponse' method is called without
using buffering. So, the response is consumed per single byte via a
recv() call on the underlying socket.
This patch, fixes that issue to mimic the non-chucked request behavior.

This seems like a sensible change to me, I'm :+1:. @sigmavirus24?

What's the benefit?

Without buffering, httplib will issue a lot of 1-byte reads in order to satisfy the constraints of the read call. That's...not good.

Sorry, I was reading the commit message/PR message backwards. LGTM :+1:

Thanks for this @dblia! :cake: :sparkles: :cake:

Thanks for the immediate response @Lukasa and @sigmavirus24!


Add Option  to see user Profile

Is your feature request related to a problem? Please describe.
Currently the app is missing the option of user profile
Describe the solution you'd like
Adding an option to see user profile in the home page
Describe alternatives you've considered
In the profile option user can see user  image, username and his/her email

@diyajaiswal11 Can I work on this issue?


0.1.17 does not work on M5Core2.

Library was updated to 0.1.17 and it no longer works on M5Core2.
Arduino IDE example.
M5Unified - Basic - Displays.ino
https://github.com/m5stack/M5Unified/blob/master/examples/Basic/Displays/Displays.ino
With 0.1.17, the build completes successfully but does not work.
Reverting to 0.1.16 works fine.
Environment:
M5Core2
Arduino IDE 2.32
arduino-esp32 3.0.5

Downgrading arduino-esp32 3.0.5 to 2.0.17 using Board Mnager works fine.
The combination of esp32 3.. and 0.1.17 seems to be the cause.

Same issue here.


Fix helm chart by making some parameters as optional

Fixing issue with helm chart by defining token_secret, ssl_crt_path, ssl_key_path as optional. Also, if db_uri is defined then DB_HOST, DB_PORT, DB_USER, DB_PASSWORD will not be created.
Here is the output with the same values.yaml file as described in #713:
NAME: konga
LAST DEPLOYED: Sat Aug 14 09:58:53 2021
NAMESPACE: kong
STATUS: deployed
REVISION: 1
NOTES:
1. Get the application URL by running these commands:
  export NODE_PORT=$(kubectl get --namespace kong -o jsonpath="{.spec.ports[0].nodePort}" services konga)
  export NODE_IP=$(kubectl get nodes --namespace kong -o jsonpath="{.items[0].status.addresses[0].address}")
  echo http://$NODE_IP:$NODE_PORT

Closes #713

@fabasoad Why was this deleted? I ran into the following error and this was the solution:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [unknown object type "nil" in ConfigMap.data.DB_URI, unknown object type "nil" in ConfigMap.data.SSL_CRT_PATH, unknown object type "nil" in ConfigMap.data.SSL_KEY_PATH, unknown object type "nil" in ConfigMap.data.TOKEN_SECRET]

@fabasoad Why was this deleted? I ran into the following error and this was the solution:
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: error validating "": error validating data: [unknown object type "nil" in ConfigMap.data.DB_URI, unknown object type "nil" in ConfigMap.data.SSL_CRT_PATH, unknown object type "nil" in ConfigMap.data.SSL_KEY_PATH, unknown object type "nil" in ConfigMap.data.TOKEN_SECRET]

Because maintainers didn't reply, so I forked the repo and fixed it there on that moment.


Customizing the multi-select separator

I am using the multi-select for my project, however I have select options as "LastName, FirstName". As such, the comma separator makes it difficult to distinguish users. Is there a way to set the separator type when we initialize the material_select() function?

Can you explain a little more? I'm not sure i'm understanding what you are asking for.

So if you have a select box setup so you can select multiple options, it may show something like: Joe, Mike, David, John. And that is fine in most cases, however I am having a employee list that is lastname, firstname, so it looks like this: Davison, Joe, Barley, Mike, Langston, David, Smith, John. And that is difficult to distinguish each person. It would be nice to be able to set an option such as:
$('select').material_select({
     'separator': '; '
});

And thus get: Davison, Joe; Barley, Mike; Langston, David; Smith, John


Tensorflow serving with Retrained Inception graph

Hello!
Are there any plans to release a tutorial similar to the one to use a checkpointed Inception graph with Tensorflow Serving, but with a Retrained Inception graph as created with the transfer learning tutorial?

In theory it should be possible to reuse the TensorFlow Serving tutorial and just change the name of the output layer to "final_result", as shown in the label_image example:
https://www.tensorflow.org/versions/master/how_tos/image_retraining/index.html#using-the-retrained-model
Unfortunately the TensorFlow Serving code creates its own model from scratch, and then loads in the checkpoints to fill in the variables. This means that it's not obvious how to convert a plain GraphDef with the weights as constant ops into their format. I'm passing this over to @jharmsen to see if he can offer any advice?

@jharmsen Do you have any further information on this topic? I am unfortunately still at a standstill.

I am interested in serving a retrained-inception graph as well. Is there a way to 'serve' the .pb retrained file that is an output of retrain.py and is used in label_image? Or a way to serve label_image pointing at a .pb file?

I'm stuck at this point too. Did anyone find a solution?

@nfiedel can you help with this?

@fangweili and I were discussing offline. Now that SessionBundle is in contrib, the next natural step is to update the inception model / retrain.py to directly use the SessionBundle Exporter. Contributions welcome though we may get to it over the coming weeks.

Trying to do the same.
Would be awesome to see an update to inception / retrain.py!

Also trying to do the same... I think it's safe to say that there are many others who haven't chimed in but would love for this to be added, or documented steps so that we can implement it ourselves.  Are we at least on the right path to use export_meta_graph and Saver.save() to convert the retrained .pb and label files into the metagraph def and checkpoint files needed for TF serving?

@nfiedel is there update to this topic?

Might not totally be related to the original question but what worked for me as a workaround is to fully train the inception model from scratch and then export it to serving. Of course, that involves the extra resources needed for the full training run but might be a suitable way for some seeking to serve their own classification model.

Hello guys, i am stuck at this point. I don't have the resources to train from scratch the inception model, although is something that i want to do soon. Any update on this topic is welcome. Thx

Sorry we don't have the cycles to support that. It's a known problem. It might be worth asking the community on stackoverflow.

Automatically closing due to recent activity.
As we moved models out of core TensorFlow repository, this issue may be a better fit for models or serving repositories.

@petewarden Any walkthrough for the tensorflow serving on custom retrained Inception v3.

Please watch this video tutorial. It might help you.
https://www.youtube.com/watch?v=9l2lkQtinx4&t=14s


Lesch-Nyhan syndrome and hypoxanthine-guanine phosphoribosyltransferase deficiency

"Lesch-Nyhan syndrome" MONDO:0010298 is both a child of "hypoxanthine-guanine phosphoribosyltransferase deficiency" MONDO:0016088 and has "hypoxanthine-guanine phosphoribosyltransferase deficiency" as an exact synonym.
Which relationship is correct?

I excluded the synonyms


Reset Your Password For SpringML Prod App

Hello,
This email has been generated for<EMAIL_ADDRESS>to reset your password for the SpringML Prod App.
Please use the following link to reset your password: Reset Password Here. This link will expire after one hour or after being used once. Afterwards, a new password reset email will need to be generated.
We ask you to start sending data to the SpringML Prod App https://labupload.health.ok.gov/#/login. Please note that this is a slightly different URL compared to the previous SpringML UAT Test App (labupload-uat) and previous login information will not work.
If you have credentials in the SpringML Test App, that account will be disabled and attempts to login or change the password of the account will fail.
If you didn’t ask to reset your password, you can ignore this email.
Thank you,
SpringML Team

https://osdh-labupload-prod.firebaseapp.com/__/auth/action?mode=resetPassword&oobCode=8eiYqX2sbi6Er_tFlzFFG5T1XkE2_RgAJtaV8t--q80AAAGD-wJ9HQ&apiKey=AIzaSyADk5GmBrqiyTGtB7zYK4opsOV9Db_DEiM&lang=en
Link to reset pw.


Can not change default_controller

when i change default_controller then show 404 error every time. My CodeIgniter version is 3.0.4 . i had change all things that i know. but apps not work perfectly. what i can do now?

Open a thread on the forums, this is a bug tracker.


open card (current song playing) doesn't toggle back to small card when clicked again

It instead restarts the song as if clicking it for the first time, with no changes in appearance.

@dannydb My thinking is that clicking the open card doesn't do anything, does that sound right?

Yup! That's what I was thinking as well.

Hey for some reason I'm on this chain and I'm not on this project. How do I get off of the chain? It's sending me like 30 emails a day! Ack!
-LA Johnson
Sent from my iPhone
On Jan 30, 2015, at 10:45 AM, Danny DeBelius <notifications<EMAIL_ADDRESS>wrote:
Yup! That's what I was thinking as well.
—
Reply to this email directly or view it on GitHubhttps://github.com/nprapps/austin/issues/103#issuecomment-72220715.


cmd/go: -buildmode=pie does not build correct PIE binaries for ppc64le

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
latest
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
ppc64le
What did you do?
Tried to run binaries built as PIE.
What did you expect to see?
Correct execution
What did you see instead?
Error messages like this:
./main.exe: error while loading shared libraries: R_PPC64_ADDR16_HA re10f2f8fa4 for symbol `' out of range
2018/09/05 09:53:14 Failed: exit status 127
on newer distros.
The problem is related to issues #27510 and #21954 and can still be reproduced on many distros by passing -pie as a linker option.
The solution to the above issues was to use -buildmode=pie but that doesn't correct all problems. When linking a program with -pie on ppc64le then all code should be built as PIC. When some code is not PIC there could be relocations created like R_PPC64_ADDR16_HA which will fail with the above error if the relocated addresses are too big. On some distros/kernels we get lucky and no failures occur if the addresses stay small enough but on newer distros the runtime relocation errors can occur.
When using -buildmode=pie the -shared option is set to force the compiles to be built as PIC but it still links in stdlib which was not built as PIC. Likewise any library linked in should be PIC. When all the code is has been built as PIC then this relocation would not be generated and the PIE should work.
One further question is whether all code should be PIC if the gcc being used for the link passes -pie by default and stop setting -no-pie.

When you use -buildmode=pie the go tool is supposed to rebuild all dependencies using -shared, including the standard library.  If that is not happening, something is wrong.
As far as a gcc defaulting to PIE, we already have support when using -compiler=gccgo for passing -fno-pie; perhaps we need to extend that support to the gc compiler side.  See gccNoPie in cmd/go/internal/work/.

I'm sorry there's some confusion here. This was reported to me through a bugzilla that even with -buildmode=pie a bad relocation is generated but I was mistaken above about whether stdlib is built with PIC in this case. In my experiments it seems to be. The reported failure is on RHEL8 which I don't have access to so I'm not sure yet where it is coming from.
One related question is whether golang should recognize whether the gcc on the system sets -pie by default when invoking the linker and if so just build it as -buildmode=pie. I'm not sure if that's the right answer but just what was suggested.

I don't think we should change the default of go build to the default of GCC.  That seems like an unnecessary tying that will tend to increase confusion.
Perhaps we should have an easy way for a distro to change the default of go build, but that seems like a different issue.  (For example, we could consider adding another environment variable recognized by src/make.bash.)

@ianlancetaylor Is there a way to build a toolchain for ppc64le so that the default type of executable is always PIE through the use of existing environment variables or other options? Or is it more complicated than that?
I tried to just change the default in cmd/go/internal/work/init.go as a test to see what would happen and got this:
Building Go toolchain2 using go_bootstrap and Go toolchain1.
cmd/cgo
loadinternal: cannot find runtime/cgo
cmd/asm
loadinternal: cannot find runtime/cgo
cmd/link
loadinternal: cannot find runtime/cgo
cmd/compile
loadinternal: cannot find runtime/cgo
Building Go toolchain3 using go_bootstrap and Go toolchain2.
cmd/cgo
loadinternal: cannot find runtime/cgo
cmd/asm
loadinternal: cannot find runtime/cgo
cmd/link
loadinternal: cannot find runtime/cgo
cmd/compile
loadinternal: cannot find runtime/cgo
HASH[build runtime/internal/sys]
HASH[build runtime/internal/sys]: "devel +745ec8b Fri Nov 2 17:56:07 2018 +0000"
HASH[build runtime/internal/sys]: "compile\n"
HASH[build runtime/internal/sys]: "goos linux goarch ppc64le\n"
HASH[build runtime/internal/sys]: "import "runtime/internal/sys"\n"
HASH[build runtime/internal/sys]: "omitdebug false standard true local false prefix ""\n"
HASH[build runtime/internal/sys]: "compile ymJr-uldWHMJ1NKhKQaW X:framepointer ["-shared"] []\n"
HASH[build runtime/internal/sys]: "GO$GOARCH=\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/arch.go: d9b0b7e72538d421b2607acaba60ca49f20ef584b3d1d191c6729e35fbb8101d
HASH[build runtime/internal/sys]: "file arch.go 2bC35yU41CGyYHrKumDK\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/arch_ppc64le.go: d43466ea44c56eba4514ad41e6652168a0ce0dcb720578ea6dadea343266a24a
HASH[build runtime/internal/sys]: "file arch_ppc64le.go 1DRm6kTFbrpFFK1B5mUh\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/intrinsics.go: 8b469a461e1d983706e0b3635715ce70691adc5db7c4e067b88cc59f40cd66f4
HASH[build runtime/internal/sys]: "file intrinsics.go i0aaRh4dmDcG4LNjVxXO\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/stubs.go: 376cb070d0d0d7094a8a5ed372853e00c377c2aba3d8c118dee821dd526a6022
HASH[build runtime/internal/sys]: "file stubs.go N2ywcNDQ1wlKil7TcoU-\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/sys.go: 55e021891200a7e6a5c371c8a1ab71b6c15aeb16ea6c1b192185d17df8c8b18f
HASH[build runtime/internal/sys]: "file sys.go VeAhiRIAp-alw3HIoatx\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/zgoarch_ppc64le.go: 157322cbcc4e3c5d80effef8a81d3d9a480cc2558550fad0df46a10b48af334c
HASH[build runtime/internal/sys]: "file zgoarch_ppc64le.go FXMiy8xOPF2A7_74qB09\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/zgoos_linux.go: 32284a5a70366b56fe207ea3a16ad5d61dd208d425ad28b81cc2fe59db9180e8
HASH[build runtime/internal/sys]: "file zgoos_linux.go MihKWnA2a1b-IH6joWrV\n"
HASH /home/boger/golang/clean/go/src/runtime/internal/sys/zversion.go: a0901e5adb74da30a6a6643ab36cfaa28c4c5136142e9a1fdeec8ca6c30f000a
HASH[build runtime/internal/sys]: "file zversion.go oJAeWtt02jCmpmQ6s2z6\n"
HASH[build runtime/internal/sys]: 664409261b5745f2e0926a0ef91599e67e2adb4a49da5a0b03eef7256f034c44
runtime/internal/sys true
go tool dist: unexpected stale targets reported by /home/boger/golang/clean/go/pkg/tool/linux_ppc64le/go_bootstrap list -gcflags="" -ldflags="" for [cmd/asm cmd/cgo cmd/compile cmd/link runtime/internal/sys]:
STALE cmd/asm: stale dependency: internal/cpu
STALE cmd/cgo: stale dependency: internal/cpu
STALE cmd/compile: stale dependency: internal/cpu
STALE cmd/link: stale dependency: internal/cpu
STALE runtime/internal/sys: build ID mismatch
got a lot of errors showing:
cmd/cgo
loadinternal: cannot find runtime/cgo

This issue is also present on SUSE and openSUSE for ppc64le.
With go1.10.5, the build stops at the following error:
cmd/vendor/github.com/google/pprof/internal/symbolizer
cmd/vendor/github.com/google/pprof/internal/driver
cmd/vendor/github.com/google/pprof/driver
cmd/pprof
/home/abuild/rpmbuild/BUILD/go/bin/go: error while loading shared libraries: R_PPC64_ADDR16_HA re10143fb0c for symbol `' out of range

By ensuring gcc does not use PIE by default, the build can complete, although this is not ideal.
It would be a great improvement to have an environment variable and option to force the toolchain to default to PIE.

@jfkw Now in 1.12 you should be able to use GOFLAGS=-buildmode=pie.

@ianlancetaylor seems now work for 1.12:
# go version
go version go1.12.10 linux/mips64le
# GOFLAGS=-buildmode=pie go build components/cli
-buildmode=pie not supported on linux/mips64le

@daixiang0 This bug report is about a problem with ppc64le.  You are using mips64le.

@ianlancetaylor sorry for mistake, BTW any plan for mips to support pie build mode?

@daixiang0 Sorry, I do not know of anyone working on adding support for PIE for MIPS.

I believe the title is is misleading. -buildmode=pie works fine for most things on ppc64le. The problem happens when trying to build a toolchain that will generate all binaries as pie by default, including those that are part of the toolchain. This came about because of a request from a single user.
No one has asked about this again, so if we want to close it that is fine with me.
I retried the same experiment as I did back in November and got the same result.

If you have an example of a failure when using -buildmode=pie on ppc64le
please provide it.
I'm not sure what libraries you are referring to, my understanding is that
if it is Go code built using -buildmode=pie it will be built as position
independent, and C or C++ code built for ppc64le should be position
independent by default.
On Thu, Oct 17, 2019 at 11:07 AM Michal Suchánek<EMAIL_ADDRESS>wrote:

So now you have to add 'me too' to bugs? It his some web 2.0 thing?
Anyway, the code is just broken.
How do you suppose the code is position independent if the libraries
included in the interpreter are not?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/28531?email_source=notifications&email_token=ACH7BDCEUEUQKTT56QRZISTQPCEV5A5CNFSM4GA2TLN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBQULNY#issuecomment-543245751,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACH7BDGW7BMX7JJBJW54FBDQPCEV5ANCNFSM4GA2TLNQ
.

C or C++ code built for ppc64le should be position independent by default.

Apparently not. Some distributions choose to set this default which breaks go completely.

I'm very sorry. I didn't notice that an earlier comment was made regarding this topic related to SUSE.
@ianlancetaylor I tried a build setting GOFLAGS=-buildmode=pie, and the build finished but that didn't seem to build all the toolchain binaries as PIE.
If I change the default in init.go, I still get the errors that some files are stale.
I cannot reproduce the problem identified earlier on SUSE using go 1.10.5.  Were there any env variables used during the build? What distro was it.

In openSUSE there is a package gcc-PIE which sets the gcc defaults options to PIC and PIE (since Leap 15.0 which is the oldest version still developed). They can still be overridden on the commandline or the package may opt to not install these defaults.
Not using the PIE options was what was done in openSUSE to build go and go packages on ppc64le.
I can look up the current state if there is some interest in debugging this further.

@laboger I don't know why setting GOFLAGS didn't work when building the toolchain.  Does it work when using the toolchain?  That is, does GOFLAGS=-buildmode=pie go build hello.go build a PIE?

@hramrach Please be polite when making comments, and bear in mind the Gopher Code of Conduct (https://golang.org/conduct).  In particular, be patient and be charitable.  Thanks.

What the R_PPC64_ADDR16_HA suggests is you generate direct references which are filled in as  immediates in the code which are only 16bit and you need to generate indirect jumps or loads to be able to link non-trivial ppc binaries referencing code or data more than +-32kb away.

@laboger I don't know why setting GOFLAGS didn't work when building the toolchain. Does it work when using the toolchain? That is, does GOFLAGS=-buildmode=pie go build hello.go build a PIE?

@ianlancetaylor Currently, the openSUSE ppc64le go package builds by not installing the gcc-PIE package. I will do some testing in openSUSE ppc64le using the GOFLAGS=-buildmode=pie used uniformly for building go, go tools and small programs written in go, and report back here in the coming weeks to correlate results with the observations from @laboger.

I suspect this is a bootstrap issue to some extent. You cannot build pie binaries if your stdlib is not PIC. You probably need to rebuild twice, once to build PIC stdlib injecting the PIC flag somewhere, and second time to build the PIE binaries.

@hramrach If I understand you correctly, then the go tool should consistently do the right thing.  Using go build -buildmode=pie will build all Go code, including the standard library, as appropriate for PIE.  Using go build without -buildmode=pie will build all Go code, including the standard library, as appropriate for ordinary executables.

that's not possible in the case when you are trying to build a pie interpreter and all you have is non-PIE interpreter with non-PIC stdlib. The new interpreter will use the old stdlib which is not suitable. So you first need to build an interpreter with PIC stdlib which does not default to PIE and then fully PIE interpreter. Assuming the code generation works and correct relocations are generated.

@laboger I don't know why setting GOFLAGS didn't work when building the toolchain. Does it work when using the toolchain? That is, does GOFLAGS=-buildmode=pie go build hello.go build a PIE?

Yes, if I use -x I can see it uses -buildmode=pie on the final link of the executable for hello.

I'm sorry, I'm not sure what you mean.  When you say "stdlib", what are you referring to?  When you say "interpreter", do you mean the ELF interpreter, also known as the dynamic linker?

sorry, I meant compiler. Looks like interpreter is not standard part of go.

@hramrach When you say "stdlib", what are you referring to?

whatever comes with the compiler that might be linked into binaries.

After I do a normal build, I can do this to make these binaries built as pie:
go install -buildmode=pie cmd/go
go install -buildmode=pie cmd/trace
go install -buildmode=pie cmd/pprof
Does this help?

I would like to find a solution for this in Go 1.15. There are several options but they all have build failures due to the cache. I would need some help from someone who knows more about how the build cache is supposed to work.

It's not clear to me what the build cache is doing wrong.  Can you provide more details?

I tried various combinations to force binaries to pie but could get nothing to work. Back to original example above, if I try to force everything built for ppc64le to -buildmode=pie then I get the stale errors above. Since I'm not sure how the cache is supposed to work, I don't know why it is complaining. I thought I saw a comment somewhere that said the buildmode was not saved in the cache which could be related but I still don't understand how something would get into the cache at one point and then look stale later if the same build options were used throughout.
Assuming we could get it to work using pie as default, then there could be other issues. One would be how this default gets set, and the fact that we now check gcc's default link mode and change it from pie to no-pie all the time. That would have to change, and maybe that should be the indicator as to when to set Go's default buildmode to pie? If gcc wants pie as default then Go's buildmode should default to pie. Otherwise we provide an environment variable, maybe one used at build time to say this toolchain defaults to pie?
Another question is, does this mean everything defaults to pie, even binaries that would have been built as static? I believe static should still work fine on systems that expect pie as the default unless there is some other reason we don't want static in this environment.

The "stale dependency" errors shown in https://github.com/golang/go/issues/28531#issuecomment-436005837 aren't about the build cache.  Those are coming from cmd/dist, and mean that the package installed by go install is stale by comparison to the source files.  When cmd/dist has finished building the tools, it runs a go list command to find all package for which the installed version is considered to be stale.  See checkNotStale in cmd/dist/build.go.  In your case this may have something to with the -gcflags and -ldflags that cmd/dist passes to go list.

I thought the original suggestion was to set the default buildmode to pie and codegenArg to shared in init.go. Doing that gives the output shown above.
Then I tried modifying lib.go to avoid the errors from loadInternal about runtime/cgo. That eliminates those errors but the rest of the error message is still there.
I did spend some time looking at checkNotStale but I don't understand why go list is complaining that these packages are stale because I don't know how it decides that and looking at the code didn't help to figure that out. Even if I look at the go list help documentation, it doesn't say what causes something to be stale.
Are you saying that the -gcflags and -ldflags passed to go list in this function should use flags for pie and shared instead of blank as the output shows?

I'm sorry, I guess I don't understand what is going on.
This issue started as a problem using -buildmode=pie.  Do you still have that problem?
Then there was the separate discussion of changing the toolchain to default to generating a PIE.  I guess the suggestion of changing cmd/go/internal/work may have been wrong.  What was the patch that you have tried?  I don't it above; maybe I missed it.

I'm trying to build a toolchain that generates pie binaries by default, including the binaries that are generated during the build. Then the goal would be to have some environment variable or other switch to indicate that it should be done that way. Sorry for the confusion. This has been requested by more than one user but I personally do not have any specific issues with reproducible directions on how to cause these errors. Based on previous test failures we saw with this error message when building for pie, it is probably related to mixing pic and non-pic code.
I tried a change to cmd/go/internal/work to force buildmode=pie by default, but that causes the errors during the build about runtime/cgo and stale packages coming from checkNotStale in cmd/dist/build.go.
I don't understand why go -list would say the package or binary is stale if it just built it and therefore should be newer than the source. What else would cause it to be considered stale.
Here is an initial patch to set the default to pie and fix up the errors about runtime/cgo. I also added something to remove defaulting to no-pie to see if that made any difference but it doesn't.
golang-pie-simple.diff.txt

go version
go version go1.20.3 linux/amd64
mips64le
release failed after 11s                 error=failed to build for linux_mips64le_hardfloat: exit status 1: -buildmode=pie not supported on linux/mips64le
mipsle
failed to build for linux_mipsle_hardfloat: exit status 1: -buildmode=pie not supported on linux/mipsle


Does custom_environments.prototype work with ppo.flax?

I've fulfilled the prototype code and make the Connect can working, but encounter problem when run below command.
python experiment.py --config.algorithm.name="ppo.flax" --config.algorithm.total_timesteps=10000 --config.runner.save_model=true --config.environment.name="custom_environments.prototype"

What kind of problem do you encounter? Could you provide the exact error message?

[runner.py:68] ERROR - Uncaught exception
Traceback (most recent call last):
File "/home/rl/RL-X/experiments/experiment.py", line 6, in
runner.run()
File "/home/rl/RL-X/rl_x/runner/runner.py", line 111, in run
app.run(main_func)
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/absl/app.py", line 308, in run
_run_main(main, args)
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/absl/app.py", line 254, in _run_main
sys.exit(main(argv))
File "/home/rl/RL-X/rl_x/runner/runner.py", line 155, in _train
model.train()
File "/home/rl/RL-X/rl_x/algorithms/ppo/flax/ppo.py", line 270, in train
processed_action, storage, self.key = get_action_and_value(self.policy_state, self.critic_state, state, storage, step, self.key)
File "/home/rl/RL-X/rl_x/algorithms/ppo/flax/ppo.py", line 117, in get_action_and_value
actions=storage.actions.at[step].set(action),
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/numpy/array_methods.py", line 485, in wrapped
return f(*args, **kwargs)
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/numpy/array_methods.py", line 532, in set
return scatter._scatter_update(self.array, self.index, values, lax.scatter,
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/ops/scatter.py", line 76, in _scatter_update
return _scatter_impl(x, y, scatter_op, treedef, static_idx, dynamic_idx,
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/ops/scatter.py", line 109, in _scatter_impl
y = jnp.broadcast_to(y, tuple(indexer.slice_shape))
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/numpy/lax_numpy.py", line 1144, in broadcast_to
return util._broadcast_to(array, shape)
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/numpy/util.py", line 398, in _broadcast_to
for arr_d, shape_d in safe_zip(arr_shape, shape_tail))
File "/home/klhz/anaconda3/envs/dl39/lib/python3.9/site-packages/jax/_src/util.py", line 71, in safe_zip
assert len(arg) == n, f'length mismatch: {list(map(len, args))}'
AssertionError: length mismatch: [3, 1]

the difference is that I used 2d Box observation_space instead 1d  Box observation_space.

flatten the 2d Box observation_space to 1d will be OK. Does the algorithm support 2D Box observation space?


[CLOSED] Promote edit

 Issue by ericgiovannini
Tuesday Aug 18, 2020 at 19:22 GMT
Originally opened as https://github.com/antalsz/hs-to-coq/pull/163

Adds a new promote edit, which allows the user to specify that a definition that normally would be placed in the set of term-level definitions in the resulting Coq file should instead be "promoted" to the set of type-level definitions.

ericgiovannini included the following code: https://github.com/antalsz/hs-to-coq/pull/163/commits

 Comment by lastland
Tuesday Aug 18, 2020 at 22:53 GMT

Does this change the way code is currently translated? The CI seems to suggest so, as the convenience copy of base, containers, ghc, and transformers seems to be different from what is generated with this patch. Can you try to rebuild the convenience copy? You should be able to do that by running make clean && make in their corresponding directories under examples (some of these may need you to rebuild base-thy as well, I don't remember exactly.) Let me know if you have any questions.

 Comment by lastland
Tuesday Aug 18, 2020 at 22:57 GMT

Oh I forgot, you can also simply run boot.sh from examples directory.

 Comment by ericgiovannini
Thursday Aug 20, 2020 at 00:47 GMT

I tried running boot.sh, but it failed with the error can't find file: base/GHC/Base.hs. So I then tried to build the base library by running make -C base from the root, but this immediately failed with make: *** [all] Error 2. Any ideas as to why this could be happening?

 Comment by lastland
Thursday Aug 20, 2020 at 01:25 GMT

I'm not sure why boot.sh goes wrong, but can you try going to examples/base-src and run make clean && make from there? What base contains is the generated Coq code translated from the Haskell code in examples/base-src.

 Comment by ericgiovannini
Thursday Aug 20, 2020 at 06:12 GMT

Just tried this, and I get a similar error about being unable to find base/GHC/Base.hs. Here are the last few lines that were displayed:
....
stack exec hs-to-coq -- -e module-edits/GHC/Base/edits \
              \
             --midamble module-edits/GHC/Base/midamble.v \
	     -e edits -N -i gen-files -I gen-files -i base -I base/include --iface-dir ../../base --dependency-dir deps --ghc -this-unit-id --ghc base -o ../../base \
	     base/GHC/Base.hs
hs-to-coq: panic! (the 'impossible' happened)
  (GHC version 8.4.3 for x86_64-apple-darwin):
    can't find file: base/GHC/Base.hs

 Comment by lastland
Thursday Aug 20, 2020 at 06:47 GMT

Uh sorry, I forget. The Haskell files are in submodules, you will need to run
git submodule update --init --recursive

The command will download all the submodules (some of them are from ghc).

 Comment by ericgiovannini
Thursday Aug 20, 2020 at 22:28 GMT

Thanks, after running that, I was able to use make clean && make to rebuild the convenience copies for base (in examples/base-src), containers, and transfomers. But for ghc, the latter command failed with
make[2]: *** No rule to make target `../../containers/theories/MapProofs.vo', needed by `IntMap.vo'.  Stop.

 Comment by lastland
Thursday Aug 20, 2020 at 23:00 GMT

It seems like you also need to compile examples/containers/theories to continue. The directory contains our theorems and proofs for the containers library, and it seems that our translation of ghc depends on it.

 Comment by ericgiovannini
Friday Aug 21, 2020 at 01:29 GMT

That seems to have fixed the error, but now a new error occurs:
File "./CoreFVs.v", line 132, characters 58-81:
Error: The reference bndrRuleAndUnfoldingFVs was not found in the current
environment.

However, I repeated the above steps on a fresh clone of the repository and this error did not occur, so I am assuming it has to do with a change I made.

 Comment by lastland
Friday Aug 21, 2020 at 05:37 GMT

I do not recall seeing this error message in the past, so it is possible to be introduced by a change you made. I can take a look at it later (I was going to say tomorrow, but I should probably say during the daytime).

 Comment by lastland
Friday Aug 21, 2020 at 20:42 GMT

Hi @ericgiovannini, I think I see what the problem is. Your PR somehow changes the order that translated definitions appear, and that causes certain function definitions to appear before the functions they use. For example, the error message you get is caused by expr_fvs appearing before bndrRuleAndUnfoldingFVs. There are two ways that you can fix this: (1) modify the code generation mechanisms to keep the original order; (2) use the order edit to guide hs-to-coq to generate code with the right dependency. I haven't taken a careful look at your code yet, so I am not certain which one would be a better design decision. What do you think?

 Comment by ericgiovannini
Friday Aug 21, 2020 at 22:46 GMT

Thanks for taking a look at this. In the latest commit on this branch, I did make a change that could possibly change the order of the translated definitions: In HsToCoq.ConvertHaskell.Module.convertHsGroup, I removed the code that uses topoSortEnvironment to order the named sentences. There was a comment below this line asking if it was really needed, because moduleDeclarations calls topoSortByVariablesBy later on. So it seemed that the line was redundant and I removed it; I will try putting it back and see if this makes a difference.

 Comment by ericgiovannini
Saturday Aug 22, 2020 at 18:29 GMT

I made the change and it seems to have fixed the issue. I have made a commit with the change.

 Comment by ericgiovannini
Monday Aug 31, 2020 at 01:41 GMT

I've added two test cases, one (called Promote) that doesn't require recursive promotes, and the other (called Promote2) that does require them.

 Comment by lastland
Monday Aug 31, 2020 at 20:46 GMT

Thanks @ericgiovannini! It seems that these tests are a bit weak though, as they won't tell the promote edit from a no-op. I have added two midamble.v files to enhance the tests. midamble.v is inserted after type declarations but before value declarations, so it can be used to test if certain declarations have already appeared at this point.

 Comment by lastland
Tuesday Sep 01, 2020 at 12:25 GMT

This looks good. Thank you @ericgiovannini!


Updating docker file

This updates the dockerfile to allow for the base packages to be updated before they get released into the build. Adds an additional layer of security by keeping up to date packages

Accidentally was submitting a pull request to the wrong branch, apologies


Update Docker API hostname

The registry.hub.docker.com domain name has been deprecated, and we should use hub.docker.com now instead.
This PR updates the hostname, so that shields will not break when registry.hub.docker.com is removed in the future.

FWIW, LGTM!

Thanks for your contribution!

@espadrine you're welcome, thank you for the merge :)


MGMT-10204: Add LVMO to the hub

Description
Add LVMO to the hub so that we can stop requesting PV creation in advance
Type of change
Please select the appropriate options:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] This change is a documentation update

Testing
Test Configuration:

Versions:
Hardware:

Checklist

[ ] I have performed a self-review of my own code
[ ] If a change is adding a feature, it should require a change to the README.md and the review should catch this.
[ ] If the change is a fix, it should have an issue. The review should make sure the comments state the issue (not just the number) and it should use the keywords that will close the issue on merge.
[ ] A change should not be merged unless it passes CI or there is a comment/update saying what testing was passed.
[ ] PRs should not be merged unless positively reviewed.

This needs to be documented! I will open a PR for docs once we decide the right approach

/cc @achuzhoy FYI, it's now possible to install LVMO in the hub (separate task for now). This PR shouldn't affect your pipeline but let us know if it does.


[Update] - add papers related to PIXART-Σ

Description
add papers related to PIXART-Σ
project: https://pixart-alpha.github.io/PixArt-sigma-project/
papers and links
PixArt-Σ: Weak-to-Strong Training of Diffusion Transformer for 4K Text-to-Image Generation
https://arxiv.org/pdf/2403.04692.pdf
PIXART-α: FAST TRAINING OF DIFFUSION TRANSFORMER FOR PHOTOREALISTIC TEXT-TO-IMAGE SYNTHESIS
https://arxiv.org/pdf/2310.00426.pdf
PIXART-δ: FAST AND CONTROLLABLE  IMAGE GENERATION WITH LATENT CONSISTENCY MODEL
https://arxiv.org/pdf/2401.05252.pdf

see #318 and #319


Dupes and saves section when ingame (on a map) are broken

The Tabs for the saves and dupes section are broken, if i select currently popular on either it hides the rest of the tags, and if i click on my saves it shows all the tabs, i dont know why it does this

Could you show me a video of the problem ?
I don't understand the problem.

Sorry for long time no reply, but

this is what im on about, it happens in dupes and saves and if i click on my saves its fine?

i am wondering if you have fixed this issue yet?

i am wondering if you have fixed this issue yet?

I'm sorry but as mentioned in "readme" I stopped developing this project because a lot has changed since my first version of the menu and it will be more complicated to merge official menu changes into this version, I don't have much time for that now (and S&box will be coming in a few months I think, so ..)


Image editor button missing

Describe the bug
Since my upgrade the edit buttons for width and height of images is missing. Last version was v0.26.
Steps To Reproduce
Steps to reproduce the behavior:

Edit a page
Insert an image
Select image and see no edit button

Expected behavior
A button for editing width, height, swapping image etc. for an image. Beneath the image or in the toolbar as a dropdown (similar to the Drawing Manager)
Screenshots

Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v0.31.3
PHP Version: 7.2.24
Hosting Method (Nginx/Apache/Docker): Apache

Thanks for reporting @Bolthier, My bad, I removed a plugin I thought was unused.
Will be back in as part of BookStack v0.31.4, To be released shortly.

Thanks for reporting @Bolthier, My bad, I removed a plugin I thought was unused.
Will be back in as part of BookStack v0.31.4, To be released shortly.


Shared Task list issues

I am trying to use the extension with a shared Microsoft To Do task list. As the owner, I am the only one that can add to this particular task list. It isn't showing up as an option for the other people shared to the task list. Is a shared list something that can be made available to other team members?

Fixed in version 0.21.0 (currently in review).