gpg version

Hello- Thanks again for putting these all together.
I've tried this with a few major releases (Centos, Ubuntu) in docker and gotten:
[root@4d7cd71e57ff yum-packaging-nvidia-plugin]# gpg --generate-key
gpg: invalid option "--generate-key"
Can you tell me what version of gpg you are assuming?
[root@4d7cd71e57ff yum-packaging-nvidia-plugin]# gpg --version
gpg (GnuPG) 2.0.22

Hi @rogerpeaseresi yeah unfortunately the functionality of GnuPG seems to vary a lot from version to version.
CentOS 8 and Fedora 32 come with version 2.2.20 and I have version 2.3.3 on Fedora 35.
Looks like you are trying with CentOS 7, that comes with version 2.0.22 and the option is --gen-key

The instructions for a CentOS7 container are something like this
Build the RPM package
yum install python36 rpm-build rpm-sign git
git clone -b rhel7 https://github.com/NVIDIA/yum-packaging-nvidia-plugin
cd yum-packaging-nvidia-plugin/
mkdir BUILD BUILDROOT RPMS SRPMS SOURCES SPECS
cp nvidia.conf SOURCES/
cp nvidia-yum.py SOURCES/
cp yum-plugin-nvidia.spec SPECS/
rpmbuild --define "%_topdir $(pwd)" --define "debug_package %{nil}" -v -bb SPECS/yum-plugin-nvidia.spec

Create a GPG key with gpg --gen-key

Follow the interactive prompts for: key type, key size, key expiration
Follow the interactive prompts for: real name, email address, comment

Sign the RPM package with your private GPG key
$ gpg --list-keys
$HOME/.gnupg/pubring.gpg
------------------------
pub   2048R/BAD21F9B 2021-12-21
uid                  First Last<EMAIL_ADDRESS>
In this example, the shortname for our GPG public key is BAD21F9B.
export gpgKey="BAD21F9B"
gpgArgs="/usr/bin/gpg --force-v3-sigs --digest-algo=sha512 --no-verbose --no-armor --no-secmem-warning"
pkg_sign() { rpm --define "%_signature gpg" --define "%_gpg_name $gpgKey" --define "%__gpg /usr/bin/gpg" --define "%_gpg_digest_algo sha512" --define "%_binary_filedigest_algorithm 10" --define "%__gpg_sign_cmd %{__gpg} $gpgArgs -u %{_gpg_name} -sbo %{__signature_filename} %{__plaintext_filename}" --addsign "$1"; }
for package in RPMS/noarch/*-plugin-nvidia*.rpm; do pkg_sign "$package"; done

Instructions for creating/updating RPM repository metadata can found here:
https://github.com/NVIDIA/yum-packaging-precompiled-kmod#generate-metadata

Thanks! This seems to have gotten me quite a bit farther! If I have any more issues I'll let you know.

Closing. Feel free to re-open if need further guidance.


Get Outlook for iOShttps://aka.ms/o0ukef

From: Sam El-Husseini<EMAIL_ADDRESS>Sent: Tuesday, April 11, 2017 8:15:13 AM
To: Microsoft/pxt
Cc: Peli de Halleux; Author
Subject: Re: [Microsoft/pxt] Lazy loading resources (#1878)
runnertest doesn't need custom.css?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fpull%2F1878%23issuecomment-293296132&data=02|01|jhalleux%40microsoft.com|5474463dd68549defb9808d480ed8e22|72f988bf86f141af91ab2d7cd011db47|1|0|636275205194005343&sdata=kaYVJ%2FUPGF0voljsJ1GBF1hV7HxIQYbkJvEAnIUdivU%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KXCMs6th1_QMowdqCpvg3W6FUdNQks5ru5kBgaJpZM4M5sNx&data=02|01|jhalleux%40microsoft.com|5474463dd68549defb9808d480ed8e22|72f988bf86f141af91ab2d7cd011db47|1|0|636275205194015351&sdata=iR2grtrj2S9Ohqv3FVe%2FKfPkMszTeGKaqfqiXEXwXZo%3D&reserved=0.


Enhancement suggestion: remember cursor position when re-opening existing note

Thanks for the great app.
I think it'd be even greater if opening a saved note returned the cursor to the position it was in when the note was saved.
Keep up the good work!

Just to be clear, what I'm suggesting is that the second tap (to enter edit mode) returns the cursor to the editing position in the note when it was saved.  Currently it defaults to the home position at the head of the note.
Thanks.

Duplicate, suggestion 1 #9


Brave browser support

What problem does this feature solve?
People who want to use brave browser can install Vue-devtool.
What does the proposed API look like?
An identical extension for chrome.

Why my brave can't detect vue.js devtools? I already clicked "Allow access to file URLs"

@moonmirXD  are you using vue 3? If so, you need to install the new beta vue devtools extension, which supports (only) vue 3. https://chrome.google.com/webstore/detail/vuejs-devtools/ljjemllljcmogpfapbkkighbhhppjdbg/related

@moonmirXD  are you using vue 3? If so, you need to install the new beta vue devtools extension, which supports (only) vue 3. https://chrome.google.com/webstore/detail/vuejs-devtools/ljjemllljcmogpfapbkkighbhhppjdbg/related

updating packages
npm update


otice->notice at line 19

Hi,
This is a simple typo fix, namely changing otice with notice at line 19 of the README.
Thanks for your time,
Brenton

Thanks for the hint.
I think a capital N would be more appropriate. Would you like to update your PR?

I don't see a colon in the part above. There's just the HowTo and the heading. The n does indeed begin a new sentence. It's the imperative present form. Notice how quick the update was. is the only version that is gramatically correct..

Can't believe I closed it. You're right mate, I assumed there was a colon, as that's how lists usually start, or at least that's usually how I start them. I edited it because now the list items should be treated as separate sentences, each with their own full stop.


Revenge is now also discontinued, now only Bunny is avilable

Title pretty much says it all, Revenge has bin archived already so only Bunny seems to be the alternative to be used with the theme.

Closed issue since README got updated accordingly


Render Docs from README.md files

The project itself and all the folders and subfolder of src/ contain README.md files. These can be used to generate a structured documentation website.
This website could then be built and hosted by GH pages.
Tasks:

[ ] create build script to collect README.md files and render static HTML
[ ] create GH actions workflow to use that script and prepare GH pages
[ ] configure GH pages to deploy using this workflow

Any ideas?

I've used docusaurus before for this sort of thing...

For TypeScript, I've used typedoc in the past which also creates nice documentation out of JSDoc comments. Here's an example:
https://dbartholomae.github.io/middy-middleware-jwt-auth/
The benefit of getting automated documentation from JSDoc is paid for though by being uglier and less feature-rich than e.g. Docusaurus


[OSD-8947] ocm-agent skeleton code

This is basic skeleton for ocm-agent webserver.
https://issues.redhat.com/browse/OSD-8947

structure looks good for the skeleton also tried running it locally. No makefile or instructions is intentional as these parts have not been decided and we expect the code to change significantly in the near future.
/lgtm

I agree this is good enough for a skeleton client, however it'd be good to see the build components as part of this skeleton too.
I have raised a PR to this branch to add those components: https://github.com/a7vicky/ocm-agent/pull/1
@a7vicky if you could please review and merge that PR if you're happy, make any changes if you want to, and then I'll personally be fine to lgtm this.

Thanks @mrbarge I have run the build  and it's all working without an issue.

/lgtm
/approve


Add init to HTTPClient.Response

Hi there,
I want custom ResponseAccumulator delegate like https://github.com/swift-server/async-http-client/pull/74#issuecomment-518506014 , so can we public init function for HTTPClient.Response? please review it if we can.

@swift-server-bot test this please

@vkill looks good but there are some formatting issues, mind running swiftformat . to fix them? thanks!

@artemredkin I have fixed them.

@swift-server-bot test this please


[Permissions] Support an API to handle the "need settings" for permission

Description
The only way for an app to detect if the user denied the permission permanently during a permission request is to compare the "shouldShowRationale" before and after the permission request itself (I always hated this of the permission API, but it is what it is).
These are the cases for denied requests (boolean before / after are the showRationale value before and after lauching the request, shown indicates if the request has actually been presented to the user, assuming they are all denies):
+--------+-------+----+--------+--------------------------------------------+
| Before | After | -> | Shown? | Interpretation                             |
+--------+-------+----+--------+--------------------------------------------+
|  false |  true |    |   yes  | 1st request, denied                        |
+--------+-------+----+--------+--------------------------------------------+
|  true  |  true |    |   yes  | Nth request, denied standard               |
+--------+-------+----+--------+--------------------------------------------+
|  true  | false |    |   yes  | Nth request, denied with do-not-ask-again  |
+--------+-------+----+--------+--------------------------------------------+
|  false | false |    |   no   | Nth request, denied should send to setting |
+--------+-------+----+--------+--------------------------------------------+

As developers we need to identify the last case so that we know we have to open the settings for the permission.
The 3rd case we do not need to do anything, the user just answered with a deny, so that's a deny, it's next time (4th) that we will have to open settings.
The current API doesn't provide any way to handle this case.
Rationale Flag
A complication: in some occasion you might want to show the user a different Rationale when you know you need to go into settings.
Proposal
Change the current onPermissionResult callback from providing a  granted boolean to a new PermissionResult entity that gives the full picture:

Granted
Denied(doNotAskAgain = false)
Denied(doNotAskAgain = true)
NotAsked

And provide a new launchPermissionSettingRequest() that send the user to settings.
For multiple permission the map would become Map<String, Boolean> --> Map<String, PermissionResult>
This is still not ideal because we, developers, need to manually handle a state to know when we should show the setting rationale, but at present I wouldn't know how to simplify this.

See https://github.com/google/accompanist/pull/990 for the rationale for the current API design.
In your table, the false -> false case also can occur when the user hasn't been asked for the permission before, and then cancels the first permission request (presses the back button, or taps outside the dialog)

Thanks. I've read the rationale but i disagree with it.
As others users pointed out you can't make that decision if you don't know if the user was asked.
I understand there are corner cases but i think a library managing permissions should let me have all the options.
I'm not sure why the last comment say that the library can't handle that. If the library can't how can we?
Inside the result callback we don't even have access to the code that allow us to check the "shouldShowRationale" of that permission.
Overall i think this library is incomplete without something that tell the developer if the permission was shown to the user or not.
I believe the case false -> false, with cancel is detectable by the library but not by the library user.

@alexvanyo I agree wee need to extend permission callback. We also have some case on Android 11

Ask user about permission couple of time (User deny it)
Show Dialog rationaly and ask user to change permission
Choose Ask every time in permissions sesstiongs
We are not able to handle this state at all. The flag shouldShowRationaly === false but we remember previous state (Never ask again) and we are not able to handle this case

I had same issue with this. I want to navigate user to settings if its never ask again but this else case has basically 2 states and there is no way to check it right now.
I guess they knew it as well but were too lazy to implement it.

The "do not ask again" use case cannot be added to this Accompanist wrapper unless the platform APIs support it. There's no way to guarantee this behavior in past and future versions of Android. Any potential workaround we try to add now might not work in the future.

@danielesegato a library managing permissions should let me have all the options
It seems like there's an expectation mismatch here. This library is a wrapper on top of the current platform APIs that makes them easier to consume in Compose apps. This library doesn't aim to be the silver bullet for permissions on Android apps.

I've read the rationale but i disagree with it
It's definitely fine to disagree :D but unfortunately, it is what it is. If you want to support that use case, I'm afraid you'll need to be responsible for it maintain it yourself.

Thanks, I did create my own solution.
What I meant when I said "I disagree" was that I don't think handling those "happy path" is enough for any app with few exceptions. Speaking from an UX perspective having a button that when pressed does nothing is never an acceptable user experience, even if the user caused it with the double deny. I hope we can at least partially agree on this.
I also understand your point about the API not supporting it (always found that very annoying even before compose, maybe you can explain what lead to the decision of not exposing that information?).
Would it help if I create a feature request on the android issue tracker asking to support that case in the API? Basically adding a needSetting boolean or the opposite would be enough. I'm not sure how things works inside Google, hope you can provide feedback to the other departments :-)
I'd rather use a solution provided by you than my own! Thanks for your answer!

@danielesegato Mind sharing your implementation?

@ForceGT  Overall I'm not happy with it and I'm pushing to change the UX so that I do not need that at all. And I would have to go through some legality before I could do it anyway.
After working on it I can second what Manuel said: until the platform expose you the information any kind of heuristic you adopt to detect the situation is just going to be hacky and error prone / not robust.
I still think the platform SHOULD expose that information, but until it does I think it's better to just design an UX that doesn't need to know.
I can narrate how my solution works, but as I said I consider it an unreliable hack for the solo purpose of convincing you that you are better of designing a different UX.

I've created custom ActivityResultContract for permission requests (both single and multiple).
These contracts receive a data class of the request: which permission is being asked and what was the state of shouldShowRationale at the time of asking for the permission.
In createIntent() the request data class is saved in a private static variable store in the contract companion object (ich!) and when getSynchronousResult() or parseResult() are invoked they return the last request along with the result of the permission request.
        companion object {
            private lateinit var lastInput: Map<String, InternalPermissionRequest>
            private var lastInputTag: Any? = null
       }

       // ..

        override fun createIntent(...) {
            lastInput = input.requests.associateBy { it.permission }
            lastInputTag = input.tag
            /// ...
        }

        // ...

This isn't great (the static save part) but it was the quickies way to make it work... I could have done better with some singleton to persist the information in case of process death or to avoid conflicts between concurrent permission requests... But they are both very unlikely situation that can be handled with some fallback...
The "compose" state receive this result and compare compare the initial value of shouldShowRationale with the new one to detect if the permission request was shown to the user...
A problem this have is that if you go from should rationale = false to permission denied + should rationale = false my code currently detect this as a "the request wasn't shown to the user" but it could also mean the user ignored it (back)...
Manuel was right again here.
The user receive this data class instead of the boolean in the result callback:
data class PermissionResult(
    val state: PermissionState,
    val requestShownToUser: Boolean = true, // <--- this is the detection result
    val tag: Any? = null,
)

As you can see I did some more modifications to the library like allowing to tag a request to know where the permission request come from (was it requested when pressing button A or B?). And I provide the full permission state.
My code also keep and expose the information of "needSetting" in the permission State once it is detected, but clear it on resume if the rationale changes.
    data class Denied(
        val shouldShowRationale: Boolean,
        val needSetting: Boolean = false,
    ) : PermissionStatus

There are more things I did with the multi-request. I think overall when the UX will be updated I'll get rid of the needSetting / requestShownToUser and keep the rest of the modifications.

I have implemented an extension of the PermissionState to handle exactly this. Let me know what you think and any improvements are welcome. Manually tested and works well.
Essentially I leverage the onPermissionResult passed to rememberPermissionState and carry out the following logic.

If we can show rationale to the user, don't do anything.
If we could previously show the rationale to the user, but can no longer, then next launchPermissionRequest will invoke the onCannotRequestPermission() callback.
If previously we couldn't show the rationale to the user and we still can't, then we were already at the stage of double denial and invoke the onCannotRequestPermission() callback.

@ExperimentalPermissionsApi
@Composable
fun rememberPermissionState(
    permission: String,
    onCannotRequestPermission: () -> Unit = {},
    onPermissionResult: (Boolean) -> Unit = {},
): ExtendedPermissionState {
    val context = LocalContext.current

    var currentShouldShowRationale by remember {
        mutableStateOf(context.findActivity().shouldShowRationale(permission))
    }

    var atDoubleDenialForPermission by remember {
        mutableStateOf(false)
    }

    val mutablePermissionState = rememberPermissionState(permission) { isGranted ->
        if (!isGranted) {
            val updatedShouldShowRationale = context.findActivity().shouldShowRationale(permission)
            if (!currentShouldShowRationale && !updatedShouldShowRationale)
                onCannotRequestPermission()
            else if (currentShouldShowRationale && !updatedShouldShowRationale)
                atDoubleDenialForPermission = false
        }
        onPermissionResult(isGranted)
    }

    return remember(permission) {
        ExtendedPermissionState(
            permission = permission,
            mutablePermissionState = mutablePermissionState,
            onCannotRequestPermission = onCannotRequestPermission,
            atDoubleDenial = atDoubleDenialForPermission,
            onLaunchedPermissionRequest = {
                currentShouldShowRationale = it
            }
        )
    }
}

@OptIn(ExperimentalPermissionsApi::class)
@Stable
class ExtendedPermissionState(
    override val permission: String,
    private val mutablePermissionState: PermissionState,
    private val atDoubleDenial: Boolean,
    private val onLaunchedPermissionRequest: (shouldShowRationale: Boolean) -> Unit,
    private val onCannotRequestPermission: () -> Unit
) : PermissionState {
    override val status: PermissionStatus
        get() = mutablePermissionState.status

    override fun launchPermissionRequest() {
        onLaunchedPermissionRequest(mutablePermissionState.status.shouldShowRationale)
        if (atDoubleDenial) onCannotRequestPermission()
        else mutablePermissionState.launchPermissionRequest()
    }
}

Here is an example of its use.
      val pushPermissionState = rememberPermissionState(
          permission = Manifest.permission.POST_NOTIFICATIONS,
          onCannotRequestPermission = { launcher.launch(context.buildNotificationSettingsIntent()) }
      )

      if (pushPermissionState.status.isGranted) {
          onPushesEnabled()
      } else {
          GraphicInfo(
              customisation = customisation,
              state = state,
              onEnablePushesPressed = {
                  pushPermissionState.launchPermissionRequest()
              },
              onSkipped = onSkipped
          )
      }

Completed? Isn't this "won't fix"?

As I mentioned in previous comments, the "do not ask again" use case cannot be added to this Accompanist wrapper unless the platform APIs support it, we cannot guarantee the same behaviour in current and future Android API versions. Also, the Android team doesn't consider sending people to the settings screen to grant a permission a good practice / UX experience.
This library is extensible enough for you to provide those use cases if you wanted to. But for now, we aren't going to implement them in the library.
Thank you for the discussions!


What is the meaning the fields in the database: lft, rgt, pid, pos?

What is the meaning the fields in the database: lft, rgt, pid, pos?

The PHP / mySQL part is not supported, it just serves as a demo - keep that in mind.
As for the fields - I believe they are described in the source, they are: the left / rights indexes (nested set model), the parent id / position (adjacency model).

"modified preorder tree traversal algorithm"  will be helpful for you~!


funding: add new field

Co-Authored-By: Marco Vidal García<EMAIL_ADDRESS>

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/1358


Map tile bug

I get the stack trace below when i finish my activity:
Error downloading MapTile: /15/16189/15841
java.lang.IllegalArgumentException: Problem decoding into existing bitmap
at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:600)
at org.osmdroid.tileprovider.tilesource.BitmapTileSourceBase.getDrawable(BitmapTileSourceBase.java:150)
at org.osmdroid.tileprovider.modules.MapTileDownloader$TileLoader.loadTile(MapTileDownloader.java:233)
at org.osmdroid.tileprovider.modules.MapTileModuleProviderBase$TileLoader.run(MapTileModuleProviderBase.java:296)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

Does this happen all the time, or every now then or not that often? what tile source?
this can occur for a number of different reasons

@AlfredAfutu ping

Just once it has happened. Bitmap tile source

@AlfredAfutu did the app crash? what version of osmdroid? what api level is the device?

Yes, the app crashed. Version of osmdroid was 5.6.2 i think and API level
of device is 17
On Tue, Jan 24, 2017 at 11:14 PM, spyhunter99<EMAIL_ADDRESS>wrote:

@AlfredAfutu https://github.com/AlfredAfutu did the app crash? what
version of osmdroid? what api level is the device?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/547#issuecomment-274970090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFTMTEkn-Di_7jQhsOfMcZSpHMT6wkyAks5rVoXWgaJpZM4Ln61l
.

--
Alfie

source: https://github.com/osmdroid/osmdroid/blob/osmdroid-parent-5.6.2/osmdroid-android/src/main/java/org/osmdroid/tileprovider/tilesource/BitmapTileSourceBase.java#L150
well, that's a new one. it'll be fixed in the next version

Sure. Ill be waiting for the fix :). Thanks a lot
On Thu, Jan 26, 2017 at 12:09 PM, spyhunter99<EMAIL_ADDRESS>wrote:

source: https://github.com/osmdroid/osmdroid/blob/osmdroid-parent-
5.6.2/osmdroid-android/src/main/java/org/osmdroid/tileprovider/tilesource/
BitmapTileSourceBase.java#L150
well, that's a new one. it'll be fixed in the next version
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/osmdroid/osmdroid/issues/547#issuecomment-275373871,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFTMTJGAO0tahXtL60Vanizw_X_Rnx_lks5rWIz9gaJpZM4Ln61l
.

--
Alfie


Add builder option to Tracker which allows DEBUG_MODE to be set

Should this be configured to allow the Tracker to have:

No logging
Info level
Error level
Debug level
Verbose level

Or just an on/off switch for logging and not logging?

I like the log level idea...

Me too!  Will need to go through everywhere that I am logging and make sure the levels make sense but would be a nice touch.

Putting a note here to flesh out logging throughout the application still.


upgrade to maven-surefire-plugin 2.22.1

Description of the issue:
upgrade to maven-surefire-plugin 2.22.1
Expected behavior:
upgrade to maven-surefire-plugin 2.22.1
Steps to reproduce:
n/a
Environment:
n/a
jib-maven-plugin Configuration:
PASTE YOUR pom.xml CONFIGURATION HERE

jib-gradle-plugin Configuration:
PASTE YOUR build.gradle CONFIGURATION HERE

Log output:
Additional Information:

Fixed by #1174


Fix UselessCallOnNotNull rule

Fixes https://github.com/detekt/detekt/issues/4236
This considers that each actual parameter of a listOfNotNull call can be a spread expression, so it correctly handles a mix of spread + non-spread elements (by making sure at least one is nullable).

It seems that snippet codes that you provided didn't compile. Could you fix them? You can test it on your end using this command: ./gradlew test -x ":detekt-gradle-plugin:test" -Pcompile-test-snippets=true

Sorry, the parameters on the snippets should have been arrayOf, not listOf. Can't spread-operator lists.
Having a command to compile all the test snippets is a really awesome setup! I will definitely keep that in mind :)
I think I am green now:
BUILD SUCCESSFUL in 5s
175 actionable tasks: 1 executed, 15 from cache, 159 up-to-date


lazy blob error with s3 exporter and context directories

Error: input: goreleaser failed to set call inputs: failed to load contextual arg "source": failed to load contextual directory "/": failed to get dir instance: failed to get blob descriptor: failed to solve blobsource: failed to load ref for blob snapshot: missing descriptor handlers for lazy blobs [sha256:391afdd16053cec967706502836ef1516804a1f0e7550d824c9b08b61eac13b9]

Currently in a broken state. @sipsma let me know what information will help to debug this

_EXPERIMENTAL_DAGGER_CACHE_CONFIG="type=s3,mode=max,use_path_style=true,prefix=*******/,access_key_id=*****,secret_access_key=*****,bucket=*****,region=us-east-1"


design main page draft

No problem Flavio, at 2o clock we meet in the course and we do change what
is needed.
On Thu, 2 Feb 2023, 11:24 Flavio Oliveira, @.***> wrote:

@francostroff https://github.com/francostroff, what do you think about
creating an external div container?

 <!--PAGE CONTENT-->

—
Reply to this email directly, view it on GitHub
https://github.com/fl4viooliveira/find-your-movie/issues/2#issuecomment-1413583578,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3VJVPVVEQ523KCAV27R5R3WVOKPDANCNFSM6AAAAAAUMXZKXA
.
You are receiving this because you were mentioned.Message ID:
@.***>


examples of https://beta.reactjs.org/reference/react-dom/client/createRoot

Can we get examples on how to use https://beta.reactjs.org/reference/react-dom/client/createRoot ?
Thanks!

Hi @zeroexcuses
There're currently no bindings for React 18 APIs under this repository.
If you really need it I recommend taking a look at how is defined https://github.com/ml-in-barcelona/jsoo-react/blob/main/lib/core.mli (It uses gen_js_api)


@Required property validation on referenced model throws 500 instead of 4xx

Information

Version: 5.x
Type: Issue

Description
Required decorator is not working when model class referenced in a  model with Property decorator set.
It works correctly on the model.
Note: This is the first time i am making an issue, so please let me know if something is missing.
Example
@Model()
export class Calendar {
  @PropertyName("id")
  _id: string;

  @Property()
  @Required()
  name: string;

  @Property()
  owner: string;
}

@Model()
export class CalendarEvent {
  @PropertyName("id")
  _id: string;

  @Ref(Calendar)
  @Description("Calendar ID")
  calendarId: Ref<Calendar>;

  @Property("name")
  @Description("The name of the event")
  name: string;

  @Property()
  @Description("Creation's date")
  dateCreate: Date = new Date();

  @Property()
  @Description("Last modification date")
  dateUpdate: Date = new Date();

  @Property()
  @Description("Beginning date of the event")
  dateStart: Date = new Date();

  @Property()
  @Required()
  @Description("Ending date of the event")
  dateEnd: Date = new Date();

  @Property()
  @Description("Description the event")
  description: string;
}

Request
curl -X POST "http://localhost:8000/rest/calendars/5d7a110c1ac20d05d821a6a8/events/5d7fa45441d1be35004bc60d" -H "accept: application/json" -H "Content-Type: application/json" -d "{ \"id\": \"string\", \"calendarId\": { \"id\": \"string\", \"owner\": \"string\" }, \"name\": \"string\", \"dateCreate\": \"string\", \"dateUpdate\": \"string\", \"dateStart\": \"string\", \"dateEnd\": \"string\", \"description\": \"string\"}"

Response
500 Error: Internal Server Error

Conversion failed for class "CalendarEvent" with object => {"id":"string","calendarId":{"id":"string","owner":"string"},"name":"string","dateCreate":"string","dateUpdate":"string","dateStart":"string","dateEnd":"string","description":"string"}.
For calendarId with value [object Object]
Property name on class Calendar is required.

Acceptance criteria

400 Bad Request

Reference
https://github.com/TypedProject/tsed-example-mongoose

Hello @dileepgopal
I'll take a time to fix this example :)
See you

@dileepgopal In case of calendarId, it's not really a bug. This prop is decorated by @Ref decorator. It's specific decorator for mongoose. This field doesn't valid the nested calendar because, the field can be a mongoose ObjectID or a Calendar. Currently validation over this specific usecase isn't supported and maybe isn't a needs.

@Romakita Thanks for the quick turn around in the ticket.  The same error I am getting with @PropertyType() decorator using the below model definition
@Model()
@ModelStrict(true)
export class FormEntity {

  @PropertyName("id")
  @IgnoreProperty()
  _id: string;

  @PropertyType(FormAttributeEntity)
  @Required()
  attributes: Array<FormAttributeEntity>;

}

@Model()
@ModelStrict(true)
export class FormAttributeEntity {

  @Property()
  @Required()
  name: string;

  @Property()
  @Default(false)
  required: boolean = false;

  @Property()
  @Default("string")
  type: string = "string";

}

Ok I'll fix this problem. It have to works, so it's problaby a regression. I'll fix that asap

The decorator @ObjectID must be used to declare an ObjectID field


added chat module

#615
Hope this works

Will look at it soon! btw, do not add PRs to the projects page, but instead link them to the issue that is on the project. you should see a "Development" section the right sidebar where you can do that. I've done this for you this time


currently-selected editor tab is saved in the scene file

The currently-selected editor tab get saved into each scene. Example:
diff --git a/jstest.xscn b/jstest.xscn
index f38d216..6507dbb 100644
--- a/jstest.xscn
+++ b/jstest.xscn
@@ -165,7 +165,7 @@
                                <resource  resource_type="Script" path="res://jstest.gd">  </resource>
                                <dictionary  shared="false">
                                        <string> "__editor_plugin_screen__" </string>
-                                       <string> "Script" </string>
+                                       <string> "2D" </string>
                                        <string> "__editor_plugin_states__" </string>
                                        <dictionary  shared="false">
                                                <string> "2D" </string>

If you save the file on the Script tab, it changes the scene file, but it doesn't automatically return you to the Script tab when you re-open the scene in the editor.
What is the intended behavior?

yeah, all this code will be rewritten in 1.2 though

I would much prefer that this information was not stored in the scene file.  I would like to be able to version-control a scene, and .gitignore the separate file that the editor layout is stored in.

+1 for not registering the currently-selected editor tab (or currently selected script file in the Scripts tab) in the scene. It's annoying when trying to have clean git commits that this info gets stored in the main scenes that you load to edit your code.

The feature discussed here has been removed in e9bbb97a, so the bug report can be closed IMO.


standalone-cinder: provision with existing cinderVolumeID

@aglitke I found when creating a number of PVCs, there will be multiple provision() operations, and sometimes error occurs in reserveCinderVolume step and deleteCinderVolume step in provision function, caused a lot of available cinder volumes not being used and cleaned, I have to clean the volumes manually, so I added retry here, how do you think?

@wenjun93 The reserve errors are usually due to the volume not yet becoming available.  Shouldn't this be solved by proper polling for the volume available status?

@aglitke Right, I add wait.poll() for the volume available status and it works,  it' better than add wait poll in each volume operation, thanks.

@aglitke would you mind review the changes? Thanks.

/area openstack/standalone-cinder
@aglitke are we good to go on merging this?


sqlite3-parser: replace debug! with trace!

Attempts to resolve #617

I think it would be less intrusive to just filter them out by default here: https://github.com/tursodatabase/libsql/blob/main/libsql-server/src/main.rs#L504-L510

@MarinPostma I personally prefer the current patch because then there's the option to see the tracing if needed. But I'll let you decide which way to go because you're going to suffer more from the decision than me :)

I kind of like this approach too - these messages just look like trace-tier

... and we already pulled the whole source code inside our repo, so we might just as well get intrusive :sweat_smile:

alright, the crowd has expressed their opinion 😄


Add GithubCredentialsProvider for start of GitHub Apps support

Hey, I just made a Pull Request!

This PR introduces a GithubCredentialsProvider which requests and caches tokens based on the repository url.
GithubUrlReader is configured to use the GithubCredentialsProvider which will default to the hardcoded token in configuration if no matching apps are found.
fixes #4006
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

You got a bunch of octokit type errors - we really need to get this https://github.com/backstage/backstage/pull/4024 through the door and to use that pattern

You got a bunch of octokit type errors - we really need to get this https://github.com/backstage/backstage/pull/4024 through the door and to use that pattern

This should be ready for review/merge now. Please take another look

This should be ready for review/merge now. Please take another look


fix(pbft): do not return early from state operations when syncing

Purpose

For reviewers

Related Github issues

Changes

Tests

Deployment Considerations
Version Notes
{ major | minor | patch }

NOTE: Include the version notes in the squash commit message

prnet cleaned-up successfully


github wiki VS godotengine.org wiki  = which one is main wiki? should you get rid of one?

There are 2 wikis but which one is the main one? Which one has the freshest information and gets updated the most?
From what I understand the godotengine.org wiki was made later to give more editing access to  everyone because the github one only main devs have access to.
I prefer github one but  I can see how godotengine.org one would be more accessible to editors. should you get rid of github one? I would personally prefer the github one. Or if possible another github account could have the documentation. I am not sure. Or maybe even using a wiki site.

Actually the most recent one is a third wiki: http://docs.godotengine.org/ ;)
We'll soon get rid of both the GH and OpenProject wikis.

thanks @akien-mga  I will try and use that docs one . looks ugly but if that's what you guys use fine with me

looks ugly but if that's what you guys use fine with me

Matter of taste I guess :-D

ugly? looks awesome! simple, fast and to the point. its a doc page, not a css demo playground :P

@nunodonato Agreed, it's great

haha come on guys  i know this is not about looks. i personally find it ugly so what. is it functional? does it have the information i need? then is good. is not meant to be pretty but to be useful

For the reference, I've added a header to all GitHub wiki pages saying that they are deprecated. This will all get cleaned up in a couple of days, but we won't need this issue to remember about it, so closing.


Document how to authenticate to a GitHub Repo using a token

Sometimes organization-level admin access is needed for certain GitHub repos, and that can be challenging to get. We have a workaround using GitHub tokens. Technical details are here, but it would be nice to document this in a digestible How To.

I think I missed this issue when making the PR, @q0rban - should this be closed by the PR we merged recently?
https://github.com/TugboatQA/docs/pull/244/

Closed in #244


[ZEPPELIN-2880] - Fix username output when OIDC is enabled

What is this PR for?
When OIDC is enabled, user's roles/permissions/tokens are sent to Zeppelin's client via websocket and appears in the web browser when running a paragraph in a notebook.
What type of PR is it?
[Bug Fix]
What is the Jira issue?

ZEPPELIN-2880

How should this be tested?
Enable OIDC , login to Zeppelin and run a paragraph.  Check the text "Last updated by".
Questions:

Does the licenses files need update?  N/A
Is there breaking changes for older versions?  N/A
Does this needs documentation?  N/A

this is possible since this PR from @volumeint to bujiio:
https://github.com/bujiio/buji-pac4j/pull/63

Yes, I have now added a JUnit test.

ping @felixchang

should we consider returning/displaying more than just the principal name?
now the name field is configurable via shiro.ini, basically you can return different values in that field depending on configuration (e.g. look at tests https://github.com/bujiio/buji-pac4j/pull/63/files)

I see, it would be great to add some example in /docs/setup/security?

@felixcheung I think that docs improvements have sense in this case only on top of #2552 , could post-pone them?

ok, how about this question
https://github.com/apache/zeppelin/pull/2551/files/cb6ec7047a8abc1a79da3c1261178e1a9e0b4f17#diff-0d6ccf388c8aa67062870388536ed274

LGTM
any more comment?

ping, probably this is good to merge

merged, do you have a JIRA user on ASF JIRA, @byamthev ?


[Interpreter mode] Integer overflow when do each loop.

Code here:
class InsertionSort
  def self.sort(arr)
    (1..arr.size - 1).each do |i|
      (0..i - 1).each do |j|
        debugger
        arr[j], arr[i] = arr[i], arr[j] if arr[i] < arr[j]
      end
    end
  end
end

arr = [4, 8, 7, 2, 6, 5, 3, 0, 9, 1]

InsertionSort.sort(arr)
p arr

 ╰─ $ 1  cr i 1.cr
From: 1.cr:21:44 InsertionSort.class#sort:

    16: class InsertionSort
    17:   def self.sort(arr)
    18:     (1..arr.size - 1).each do |i|
    19:       (0..i - 1).each do |j|
    20:         debugger
 => 21:         arr[j], arr[i] = arr[i], arr[j] if arr[i] < arr[j]
    22:       end
    23:     end
    24:   end
    25: end
    26:

pry(InsertionSort.sort)> i
=> 632700968
pry(InsertionSort.sort)> j
=> 0

After typing Ctrl + d
pry(InsertionSort.sort)> Invalid memory access (signal 11) at address 0x8
[0x556a75ecfa06] *Exception::CallStack::print_backtrace:Nil +118 in crystal
[0x556a75ea5776] ~procProc(Int32, Pointer(LibC::SiginfoT), Pointer(Void), Nil) +310 in crystal
[0x7f782ee51a00] ?? +140154159569408 in /usr/lib/libc.so.6
[0x7f782ef6c804] ?? +140154160728068 in /usr/lib/libc.so.6
[0x556a75ec3997] *Pointer(UInt8) +103 in crystal
[0x556a75ec3921] *Pointer(UInt8) +17 in crystal
[0x556a75ec3901] *Pointer(UInt8) +17 in crystal
[0x556a76ddd27f] *Crystal::Repl::Interpreter#interpret<Crystal::ASTNode+, Crystal::Type+>:Crystal::Repl::Value +388687 in crystal
[0x556a76d7da1c] *Crystal::Repl::Interpreter#interpret<Crystal::ASTNode+, Hash(String, Crystal::MetaVar)>:Crystal::Repl::Value +2284 in crystal
[0x556a7735102d] *Crystal::Repl#interpret<Crystal::Expressions>:Crystal::Repl::Value +109 in crystal
[0x556a77350d66] *Crystal::Repl#interpret_and_exit_on_error<Crystal::Expressions>:Crystal::Repl::Value +38 in crystal
[0x556a77351832] *Crystal::Repl#run_file<String, Array(String)>:Crystal::Repl::Value +194 in crystal
[0x556a772910cb] *Crystal::Command#repl:(Crystal::Repl::Value | Nil) +1451 in crystal
[0x556a7728b9b1] *Crystal::Command#run:(Bool | Crystal::Repl::Value | Nil) +1393 in crystal
[0x556a7728b2bb] *Crystal::Command::run<Array(String)>:(Bool | Crystal::Repl::Value | Nil) +43 in crystal
[0x556a7728b22e] *Crystal::Command::run:(Bool | Crystal::Repl::Value | Nil) +46 in crystal
[0x556a75e80909] __crystal_main +2457 in crystal
[0x556a760747c3] *Crystal::main_user_code<Int32, Pointer(Pointer(UInt8))>:Nil +19 in crystal
[0x556a7607472a] *Crystal::main<Int32, Pointer(Pointer(UInt8))>:Int32 +58 in crystal
[0x556a75e8dec6] main +6 in crystal
[0x7f782ee3c290] ?? +140154159481488 in /usr/lib/libc.so.6
[0x7f782ee3c34a] __libc_start_main +138 in /usr/lib/libc.so.6
[0x556a75e7fe95] _start +37 in crystal
[0x0] ???

 ╰─ $ 11  cr version
Crystal 1.6.0-dev [c502c77d8] (2022-09-16)

LLVM: 14.0.6
Default target: x86_64-pc-linux-gnu

Reduced:
class Foo
  def each
    yield 1
  end
end

def sort
  foo = Foo.new
  foo.each do |i|
    debugger
    puts i
  end
end

sort

crystal i foo.cr
From: foo.cr:11:10 <Program>#sort:

     6:
     7: def sort
     8:   foo = Foo.new
     9:   foo.each do |i|
    10:     debugger
 => 11:     puts i
    12:   end
    13: end
    14:
    15: sort

pry(sort)> i
=> 376464528

This one is also tricky to fix. I think someone else will have to take over the interpreter as I won't have time to work on these things 😊

If someone wants to send a PR with this, go ahead:
diff --git a/src/compiler/crystal/interpreter/interpreter.cr b/src/compiler/crystal/interpreter/interpreter.cr
index bf9fbef71..ea53294e4 100644
--- a/src/compiler/crystal/interpreter/interpreter.cr
+++ b/src/compiler/crystal/interpreter/interpreter.cr
@@ -167,7 +167,7 @@ class Crystal::Repl::Interpreter
     compiled_def = @compiled_def

     # Declare or migrate local variables
-    if !compiled_def || in_pry
+    if (!compiled_def || in_pry) && @local_vars.block_level == 0
       migrate_local_vars(@local_vars, meta_vars)

       # TODO: is it okay to assume this is always the program? Probably not.

That fixes this issue. The remaining problem is that defining new variables inside a block while doing pry won't work reliable (it doesn't work reliably even without that patch, so that simple patch might be an improvement)

This one is also tricky to fix. I think someone else will have to take over the interpreter as I won't have time to work on these things blush

I remember you said you were the only one working on the interpreter, but it seem like no time to fix some issue of them.
i just curious, are we still working on making interpreter mode enabled by default? are you still working full-time at crystal lang?

are you still working full-time at crystal lang?

No, I do it as a hobby. I work on things that I like. If I work on something that frustrates me I drop it.

No, I do it as a hobby. I work on things that I like. If I work on something that frustrates me I drop it.

Kind of sad to hear this, i know you left Manas, but I always thought you were still working full-time at Crystal somehow.

"As a hobby" he created a wonderful programming language (that's how it started).
"As a hobby" he created its REPL.
Let that sink in for a moment... 😮
Anyway, I want to make the point that the Manas team has the capacity to handle such issues, even if at a slow pace.

It works!


Embedded Calendar (Codename)

Lot's of web-sites (#18) need  to show so-called event calendars so other people know when events will take place. We can deliver better and more consistent experience for the site owners and for the users.
Value for us
This would also allow us to have non-racing events as a self-updating thing, since site owners will maintain them.
Value for site owners

they have a nicer looking calendar
they have a better adding/editing experience
potentially we can bring more people, since all events become public by location
if site owner need to maintain their event in multiple places (e.g. RedKite web-site and NCNCA) this is getting reduced to just one place if both use Embedded Calendar

Value for the user

if they already use RCN and logged in they would see their planned events right in the context of site owners web-site (like SJBC winter series page)
they can interact with the calendar like they would with RCN

How it's done

we create a special type of events "Owned by Somebody" (name tbd)
we don't allow everybody to change them (mb just suggest changes like send a PR kind of thing)
we deliver polished experience for site-owners to put their events (with preview, etc)

so they login, grab HTML code, paste it to their web-site
start hacking around right in the context of their site

we provide "embed html" code to be included as an iframe
it can be one event (looks like a tweet, just a card with an event) or whole calendar

Potentially this can be big if done right. Since it brings "Disqus for Events" (Disqus is de-facto for comments, this can be a de-facto for Event Calendars). Can be used on NCNCA and USAC (we would require some trust and credentials for that)

"Owned by Somebody" - maybe "Powered by ..."?

@Me4ta "Powered" usually means "on steroids" or "with the help of", while we need to emphasize ownership, that it's not "community owned/edited event".
This can be done with simple Text or Logo and different style of cards, no need to figure out exact wording now.

Ok, I see @Restuta

Example of how similar thing is done at http://booking.timekit.io/:
Widget for availability

And configurator to  build your own

I like the whole idea with embedded calendar and showing events, design, but it's too simple and let you just easier way to add this events in you google calendar, not more.


Docker file needs to be optimized

Docker file is quite a bit bloated. Needs to start from a better base image, like IBM DB2 database which is very lightweight.

Agreed, dockerfile should be optimized

Way too many layers 😬


Fixed composer.json to work with oauth2-php

Thanks, but this is not required anymore since Thom has already submitted oauth2-php to packagist:
https://packagist.org/packages/thomseddon/oauth2-php


NotApplicable tests appear first in a CIS scan v2 report

Verified on 2.5-head - commit id: 9d3882175

Deploy CIS v2 app in Dashboard
Navigate to CIS benchmarks on the top left menu.
Run scan. Wait for the scan to finish.
Click on the scan (which might show Pass/fail)
Tests are sorted. But the NotApplicable tests appear first and then the tests that have "Passed"

Can we have the tests in "Pass"/Fail/Skipped state to appear first ? Not Applicable tests can be available in the end of the report.

State order should be Fail, Pass, NA

On 2.5-head - commit id: f6712924

Add repo https://github.com/mrajashree/charts and branch cis16
Install CIS v2 charts
On a custom cluster, run Hardened rke profile scan. The tests are sorted in order - Fail, Warn, Pass and N/A
The tests are NOT sorted - logging a separate bug to track this - https://github.com/rancher/dashboard/issues/1901


Code released

Congratulations on your amazing results and acceptance for Neurips 2022,  I wonder what is your code releasing plan, eg. when will you release the code? Can't wait to use your amazing projects! Thank you.

Thank you for your attention, we will release the code soon.

Hi, I understand that you may be busy with other work, therefore I try to reproduce your work, since it seems not hard based on NeuS. Here summarize a few detail questions, and I hope you can give me some quickly reply :
1).Your paper did not mention about the background modeling as NeuS use a nerf++ for background modeling.  I wonder how you deal with the background in the dataset as DTU at training time.
2).You have implement 2 MLP for SDFnetwork for displacement, I wonder how you deal with them when you implement feed them into the color network for volume rendering. Which density you choose for volume rendering? Or make some combination with both of them?
3). For the sampling strategy, As you mentioned in your paper "then adaptively update the weight according to the gain and sample an additional 64 points". Are these 64 points sampled as Neus did? eg. construct the pdf, and sample the points near the surface. Does it mean you just have changed the Transparency weights using the eq.16 in the paper while other is the same as neus did.
4).  In the eqution 14, why there is a scale term 4 at MLP_d, what will happen if it become larger or smaller, I guess you may try other scales, could you share the design about that?
Sorry for asking so many problems, Since I am following your work and try to extend it for Scene-level reconstruction, I wish you can give me some quick advice.
Looking forward to your

Thanks for your interest,
1). We use the same way as NeuS to model background,
2). Eq. 14 is used for the combination of two SDFs.
3). Sec. 3.1 shows the difference between others.
4). The term 4 is applied for normalizing the maximum constraint to 1.
We are going to release the cleaned code next week. Cheers.

Thanks for your quick reply and your code releasing, It made me clear to understand,  And now I will closs the issues, Thank you very much.

Hi there,
Will you code be released this week?
Since my reproduced quality is not very well, I need your implementation for refrence, thank you !
Looking forward to your reply

Following your details in your paper, here is my reproduced results on blended MVS man.

Here is the results from NeuS:

The back of the head is not well reconstructed, I think it's some of my missunderstanding for your work, Therefore, I am looking forward to your implementation.

Hi, today I am preparing some important materials to complete neurips requirements. I have cleaned up the code and will release the code tomorrow evening.

Thanks for your code releasing.


NA/NaN/Inf in foreign function call (arg 10)

when I use the copycat,it made a issue:
rpy2.rinterface_lib.embedded.RRuntimeError: Error in hclust(d, method = "ward.D2") :
NA/NaN/Inf in foreign function call (arg 10)
how can I solve it?

Any chance there are NA values in your gene expression matrix.
If that's not the issue that sounds more like a problem with copykat itself -- infercnvpy just provides a thin wrapper that executes the R code from python. You may be better off asking for help in their repository.


[resolves #542] Add client side arquillian log for examples

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/393/
Test PASSed.


19 provider template

ticket #19
Please do not merge yet. Documentation missing.

Hi! I have finished this branch with the following features:

FastApi Template for provider
Test setup
Debugger setup
Dockerfile
Github Actions to run tests on push and pull request to the branch main

Please comment if problems or merge if agree


:rocket: Send logs to Splunk in JSON

:rocket: deployment of nhsuk/profiles succeeded (http://profiles-pr-200.dev.beta.nhschoices.net)

:rocket: deployment of nhsuk/profiles succeeded (http://profiles-pr-200.dev.beta.nhschoices.net)


Allow the passing of a function as the component definition

If a function is passed as the component definition, it should be used as the created callback. https://github.com/w3c/webcomponents/wiki/Custom-Elements:-Contentious-Bits#constructor-vs-createdcallback.
The rest of the API should not change (e.g. return value). When this is natively supported, we can still wrap the returned constructor so that it allows it to be called like a function (and can accept props).

Unfortunately we'll have to wait for native support because you can't call native constructors as functions. If you try and new them and you're transpiler has transpiled the es6 -> es5, it will try and call the native constructor as a function. The only scenario this would work for is passing a user defined constructor. We must wait for better native support at this time, I believe.

Re-opening because this will need to be done. Adding a link to the W3C issue about authoring guidance  for reference: https://github.com/w3c/webcomponents/issues/409.

Actually, I think that this isn't very relevant unless we decide to mimic the spec verbatim. It may be better to keep the created callback and to do automation stuff in the constructor. Closing this for now until we come up with a good reason to use constructor directly.


Disambiguate the battle medicine immunity and treat wounds immunity effect icons

Currently, the icons for Effect: Battle Medicine Immunity and Effect: Treat Wounds Immunity are the same, making it harder for party members, specifically the healers, to see at a glance what is available. For my group, it requires us to stop game flow and have each player read out the current immunities, which is a little frustrating
Could we change the icons for either treat wounds and its immunity or battle medicine and its immunity?

To add to that, I think it would be more interesting to propose that Battle Medicine Immunity be generated by actors, and have the symbol use the picture of the character, so as to discern from which friend's battle medicine you're immune.

that would be cute! I think it's definitely scope creep for this issue but we could split this into two separate things. I believe the Treat Wounds & Battle Medicine macro from pf2e workbench handle this in the meantime :)


fixed trailing white-space causing incorrect argument error

A simple change that could trim the trailing white-space brought by auto-completion, and allow the console to ignore blank lines.
The PR is mainly aimed to address this #3 issue.

Looks good to me. Will merge Soon (TM). (Haven't got the time to work on modding right now.)


[python] remove outdated code

Isn't just 2.0.11 now? I think it should be pushed to a 2.0.12 developing branch?

@wxchan
@guolinke removed max_bin which had the same warning: https://github.com/Microsoft/LightGBM/pull/1083#issuecomment-346927947

@wxchan 2.0.11 was realased.  the master brach is going to 2.0.12

ok, got it.

what about the max_bin parameter?


Enable CONFIG_FTRACE

I work on a tool ( https://github.com/draios/sysdig ) that provides excellent visibility into containers and it would be nice if it could work with boot2docker. Unfortunately tracepoints aren't fully enabled in the kernel configuration, which is surprising since it's harmless and have been enabled by default on almost every linux distribution released in the last 6 years. Thank you.

Seems sane to me. :+1:
LGTM

FYI This has been enabled on Debian since at least Squeeze/6.0 from 2011 :)


Skip conversion of shape.shapeof with 0-ranked tensor operand

Currently --shape-legalize-to-stablehlo fails on the following code:
func.func @test1() -> tensor<0xindex> {
  %0 = arith.constant dense<0> : tensor<i32>
  %1 = shape.shape_of %0 : tensor<i32> -> tensor<0xindex>
  func.return %1 : tensor<0xindex>
}

at stablehlo/dialect/TypeInference.cpp:1700:
// concatenate_c5
auto elementType = inputTypes[0].cast<ShapedType>().getElementType();

as inputTypes.size() is zero.
I have checked how it works on non-0 ranked tensor type:
func.func @test2() -> tensor<2xindex> {
  %1 = arith.constant dense<0> : tensor<2x128xi32>
  %3 = shape.shape_of %1 : tensor<2x128xi32> -> tensor<2xindex>
  func.return %3 : tensor<2xindex>
}

produces:
func.func @test2() -> tensor<2xindex> {
  %cst = arith.constant dense<0> : tensor<2x128xi32>
  %0 = stablehlo.get_dimension_size %cst, dim = 0 : (tensor<2x128xi32>) -> tensor<i32>
  %1 = stablehlo.reshape %0 : (tensor<i32>) -> tensor<1xi32>
  %2 = stablehlo.get_dimension_size %cst, dim = 1 : (tensor<2x128xi32>) -> tensor<i32>
  %3 = stablehlo.reshape %2 : (tensor<i32>) -> tensor<1xi32>
  %4 = stablehlo.concatenate %1, %3, dim = 0 : (tensor<1xi32>, tensor<1xi32>) -> tensor<2xi32>
  %5 = builtin.unrealized_conversion_cast %4 : tensor<2xi32> to tensor<2xindex>
    return %5 : tensor<2xindex>
}

I suggest considering an alternative approach instead of simply bailing out; one option could be generating a constant tensor with zero dimension:
func.func @test1() -> tensor<0xindex> {
  %cst = arith.constant dense<0> : tensor<i32>
  %0 = stablehlo.constant dense<> : tensor<0xi32>
  %1 = builtin.unrealized_conversion_cast %0 : tensor<0xi32> to tensor<0xindex>
  return %1 : tensor<0xindex>
}

but i am not entirely certain in semantic equivalence.

Both seems fine to me.
LGTM on the current resolution as it avoids the crash. We can wait  till we have a better use-cases to improve on it, maybe be, by generating the 0-D index constant.

@mlevesquedion Sure, added zero dimension constant generation when applying shapeof to a scalar operand.


fixes and enhancements to the usage documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.297%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3247

Relevant Lines:
3755

💛  - Coveralls


runtime: objcpp ftplugin

Just inherits the base objc ftplugin

I suppose this should source the corresonding ftplugin instead of the syntax file?


Locale for UNITS alt

Hello! Thanks for this great library, it's helped me a lot! But I faced a little problem.
I'd like to use locale prop with humanizeLabels and I can't override these labels.
Is there any way to use custom localisation for months and week-days constants alt values?
May be You can add this feature?

Hi,
I'm happy people can use this library!
Oh, yes it's true, it's because I wanted to keep a valid Cron syntax for the ALT values. (cf: https://en.wikipedia.org/wiki/Cron#CRON_expression)
But you want to humanize labels with a translation system only right? And not the value?
So I will provide a way to translate the labels when using "humanizeLabels", but values will not be translated when using "humanizeValue".
The value will always be a valid Cron syntax but what is displayed inside the dropdown can be translated.
Is this way good for you?

Didn't wait for your answer 😉
I just released a new version v1.2.0 with the possibility to translate alternative labels 🥳
There are two new properties for the "locale" object: "altWeekDays" and "altMonths".

Don't forget that the order is important for these properties too

Go check out the story with the French example: https://xrutayisire.github.io/react-js-cron/?path=/docs/reactjs-cron--french-locale
Don't hesitate to tell me if you find a problem with the new release.
If it's good for you, let me know, so I can close the issue 😉

Oh, excellent!
Yep, of course it's enough to translate only labels.
Thank You very much for such fast response and new version!


refactor: make stricter database trait bounds for user ergonomics

Two quick ergonomics changes for downstream users. Intended to simplify bounds writing
This is a breaking change, as downstream implementors of these traits will need to be update

Error bounds for database errors
Adds an error bound for Database::Error and DatabaseRef::Error, and the async versions. This closes #1674. This prevents propagation of complex bounds for upstream wrapper structs, particularly error types that might wrap EVM output.
Before:
use revm::{primitives::EVMError, Database};

pub struct Error<Db: Database<Error: core::error::Error>>(EVMError<Db::Error>);

impl<Db: Database<Error: core::error::Error>> From<EVMError<Db::Error>> for Error<Db>
{
    fn from(e: EVMError<Db::Error>) -> Self {
        Self(e)
    }
}

impl<Db: Database<Error: core::error::Error>> core::error::Error for Error<Db> {
    fn source(&self) -> Option<&(dyn Error + 'static)> {
        Some(&self.0)
    }
}

After:
use revm::{primitives::EVMError, Database};

pub struct Error<Db: Database>(EVMError<Db::Error>);

impl<Db> From<EVMError<Db::Error>> for Error<Db>
where
    Db: Database,
{
    fn from(e: EVMError<Db::Error>) -> Self {
        Self(e)
    }
}

impl<Db: Database> core::error::Error for Error<Db> {
    fn source(&self) -> Option<&(dyn Error + 'static)> {
        Some(&self.0)
    }
}

Add Database as a supertrait of DatabaseCommit
This does not close a current issue, but I'm happy to make one. This causes some bounds changes in the database_components examples
Code before:
use revm::{Database, DatabaseCommit};
pub fn make_writable_evm<Db: Database + DatabaseCommit>(db: Db) -> Evm<'static, (), Db> { ... }

Code after:
use revm::{DatabaseCommit};
pub fn make_writable_evm<Db: DatabaseCommit>(db: Db) -> Evm<'static, (), Db> { ... }

Add WrapBlockHashRef to example
Add a wrapper struct like WrapDatabaseRef to BlockHashRef to allow relaxing the bounds on the database components in the database_components example

Drive-by:
The asyncdb is cfged out when running cargo c --all-features. And running cargo c -p revm-database-interface --features asyncdb produced compilation errors due to disabled tokio features. I have enabled the necessary features. When running with --workspace it appears some other package enabled the features, and covered up the dep specification issue

hmmmm. for some reason it seems not all packages are building on my local. so this may be more invasive than it appeared 🤔

Ok it seems to be mostly an example that was broken, so I've updated that :)
I think this is ready for consideration

CI failure seems to be related to #1844


Add test for macro expansion in various expressions

cc @edwin0cheng

r? @edwin0cheng

Perfect, bors r+

bors r+


Model layer architeture doubts - Mithril 1.x

I'm creating a new application and would like to use Mithril 1.x, however, I have some doubts about the architecture.
Which of the following architectures would be most appropriate?
1-
/model
user.js

	var model = {
		getUsers: function() {
			return m.request...
		}
	}

/views
user.js

	var state = {
		users: []
	}

	var user = {
		oninit: function(vnode) {
			model.getUsers().then(function(users){
				state.users = users
			})
		},
		view: function(vnode) {
			return m("div", [
				state.users.map(function(user){
					return m("p", user.name)
				})
			])
		}
	}

2-
/model
user.js
	var model = {
		users: [],
		getUsers: function() {
			return m.request().then(function(users) {
                              model.users = users
                        })
		}
	}

/views
user.js
	var user = {
		oninit: function(vnode) {
			model.getUsers()
		},
		view: function(vnode) {
			return m("div", [
				model.users.map(function(user){
					return m("p", user.name)
				})
			])
		}
	}

I'm a fan of 2. I have several apps in production which all use a global state object coupled with stateless components.

Considering you can reuse the already fetched users in others components I would stay with 2.

I do 2 myself

I'd vote against both of them. In both 1 and 2  model is a singleton. While component being a singleton is OK in a lot of situations, making model a singleton will make tests much more complex. You will have to mock server requests. Some tests will require one response, others will require another. You will have to modify parts of model in every tests you will write. This will inevitable cause problems.
Why not to pass the model instance via vnode.state?

While component being a singleton is OK in a lot of situations, making model a singleton will make tests much more complex

it really depends on what type of tests you want to write. a singleton model/state makes it very easy to write Acceptance Tests [1], which are really the critical tests for an app. Unit Tests [1] are better for a deliverable library or app internals that has explicit API contracts that cannot regress. A singleton model makes Unit testing more challenging since there's less purity/isolation and more side-effects. All arguments I encounter seem to miss this distinction. As always, the answer depends on what you're building and for whom.
[1] http://softwaretestingfundamentals.com/acceptance-testing/

@chebum thank you for the reply!
I could not understand very well, could you give me an example?

@leeoniya good point. Did you mean that overriding model is basically simpler when it's a singleton? Why not to make it a factory ("virtual" function) that creates a model and injects it into components. It will be almost as easy to override for end-to-end tests while still allow writing unit tests. What do you think?

@marciomunhoz for tests you will need to override the model like that:
model.getUsers = function() {
    return [1,2,3];  //Fake collection to prevent server request
}

There are several problems with this approach when writing unit tests:

The fake collection we're returning here will change from test to test.
getUsers method may have important side effects that we will need to replicate in test overloads.
You may forget to restore the component state and thus break other tests in the suite. The same may happen due to the side effects of getUsers method.
There may be several singleton components which will make mocks even harder to write.

@marciomunhoz did this help? Please close it out if this isn't generating useful discussion.

@tivac ok! thanks!


Add license clause

Keeps npm quiet.

Ah, I just spotted that npm complains because it has an old-style license that npm no longer supports, will correct.

@Synchro please sqash it together thanks.

I just did that and force-pushed - not sure why it kept the old commits.

Git only adds live but cant remove old data live ;)

Thanks

NP


Add Go script to process CHANGELOG files before releases

This is a new script I wrote to simplify writing the CHANGELOG ahead of
a release. It takes care of automatically generating links for PRs and
PR authors.
Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

/skip-all


the travis build takes a while to run

Builds look like they currently take 18-20 minutes:
https://travis-ci.org/domokit/sky_engine/builds
I haven't looked at where most of the time is spent, but it would be great to get the build times down to a few minutes. Some things you can do with travis:

if your build does not require sudo, you can run on travis' new containerized build infrastructure. I believe it'll schedule the builds onto machines with slightly more resources (cpu+memory). There is much reduced latency in your build starting up. Generally, travis promises faster builds when using their containerized infrastructure.
you can cache some directories between builds if it's helpful (see https://github.com/dart-lang/dartdoc/blob/master/.travis.yml#L13)
you can shard builds if that's useful. So, if building and testing two configurations, you can do that in two parallel builds instead of sequentially in the same build. It's just a matter of setting and then checking env variables (https://github.com/dart-lang/dartdoc/blob/master/.travis.yml#L6)

The underlying problem is that we build C++ code on Travis.  Some of the Ubuntu packages we need to build the C++ aren't available in the containerized world.  Also, the bulk of the time is spent building the C++ code.
One way to make the build cycle faster is to split the C++ and Dart code into separate repos so that people who work on the Dart code can get a fast cycle using pre-built binaries from the C++ repo.

There's also a lot of runtime-dead C++ code being built right now, deleting that would also speed things up.

fixed!


Remove FRAMEWORK_SEARCH_PATHS setting from podspec altogether

After getting the latest podspec, my xcconfig contains this line:
FRAMEWORK_SEARCH_PATHS = $(inherited) "${PODS_ROOT}/Paddle" "$(PODS_ROOT)/Paddle-MAS"

It looks like you can remove the xcconfig line altogether. Having a vendored_framework seems to automatically add it to the search path. When I remove it locally, I end up with this, which is correct:
FRAMEWORK_SEARCH_PATHS = $(inherited) "$(PODS_ROOT)/Paddle-MAS"

The unnecessary line in question:
  s.xcconfig            = { 'FRAMEWORK_SEARCH_PATHS' => '"${PODS_ROOT}/Paddle-MAS"' }

Looks good now, thanks.


component.NewMarkdownText() renders badly in Table + SummarySection

using the Markdown text component is a nice way to add formatted text, external links to documentation/github and whatnot and render clarity badges to improve the UX.
However when switching from Text -> MarkdownText the table/summary sections render with an extra line of whitespace. Am guessing this is CSS related rather than intentional?
e.g. here's a SummarySection with 2 fields; one Text, one MarkdownText. The same happens if using these 2 components in a Table:

I guess another option is to have a HTMLText component which allows some HTML markup inside (e.g. bold/italic/clarity badges and some external <a> tags with no JavaScript or extra magic?

it looks like <p> inside of <div class="markdown"> has a margin-top of 24 px which cause the layout issue. Haven't figured out a good scss PR yet, I'm a bit rusty on scss + angular

aha - figured out the CSS fix; PR on its way shortly


Users Rating

Task title
Users Rating
Task description
Add Users Rating, add a field to firestore, create a simple logic and u can use the already built stars component to display it.

this feature is postponed for later versions.


Allow to build with Debug against a Release environment

This cherry-picks the required changes to Harfbuzz from upstream.

LGTM! Thank you!


Update textinput autocomplete

Docs update for 26003
PR 26004

Closing this as the change has been abandoned.

Reopening as per discussion in  https://github.com/facebook/react-native/pull/26010


[DOC] useDataGrid - mistake in the docs

Documentation issue
https://refine.dev/docs/api-reference/mui/hooks/useDataGrid/#resource

There is a mistake in this place. Should be useDataGrid instead of useTable because this whole page is about useDataGrid.
Describe the thing to improve
Typo should be fixed.
Describe the solution (optional)
No response

Sorry for the issue @Mikilll94, that's overlooked 🤦 Do you want to create a PR for this? 🙏

Just opened a PR to fix it. We'll merge it soon 🚀


Publish 7.1.1-20210706020012+0000

Publish 7.1.1-20210706020012+0000

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.


@Shared(.appStorage) updates are triggered whenever any UserDefaults key changes, not just a specific key

Description
It looks that AppStorage should migrate from NSUserDefaultsDidChangeNotification to key-value observing for specific keys. According to Apple's documentation.

You can use key-value observing to register observers for specific keys of interest in order to be notified of all updates, regardless of whether changes are made within or outside the current process.

Checklist

[X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
AppStorage triggers updates only when specific key changes.
Actual behavior
AppStorage triggers updates whenever any change occurs in NSUserDefaults.
Steps to reproduce
Check the sample project
The Composable Architecture version information
1.11.1
Destination operating system
iOS 17.5.1
Xcode version information
Version 15.4 (15F31d)
Swift Compiler version information
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx14.0

Hi @larryonoff, this will be fixed in #3186.
We can't subscribe to the changes for just a single key in UserDefaults because KVO treats "compound" keys (i.e. "foo.bar") in a special way, and it that breaks observation if you were ever to do .appStorage("feature.count"). We have no choice but to subscribe to the firehose of all user default changes.
However, because user defaults can only store very basic data, we can implement some simple remove duplicates logic.

Hi @larryonoff, this will be fixed in #3186.
We can't subscribe to the changes for just a single key in UserDefaults because KVO treats "compound" keys (i.e. "foo.bar") in a special way, and it that breaks observation if you were ever to do .appStorage("feature.count"). We have no choice but to subscribe to the firehose of all user default changes.
However, because user defaults can only store very basic data, we can implement some simple remove duplicates logic.

Thanks for the fix.
PS. Sad that it's not possible to fix the issue in an optimal way.


MINOR: Fix typo in mapper parameter of flatMapValues

The parameter is already called mapper in the KStreamImpl class. I think it was probably named processor here because it was copy/pasted from some other signature. This sees trivial enough to not require a jira as per the contribution guidelines.

Thanks @cddr, LGTM. Can you please change the title to be "MINOR: ..." thanks

Merged to trunk


Apply extra patches to M118 - 2

Related PR

https://github.com/GetStream/webrtc/pull/32

Was merged wrongly


fix: AVM / aztec-up CircleCI issues

Fixes avm-transpiler multi-arch image
Fixes aztec-up terraform apply & only publishes on tagged releases

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:mint_public): 68.4 (-88%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 227 (+205%)
avm_simulation_time_ms (Token:transfer_public): 34.1 (-34%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,739
1,545
693 (-1%)
762 (+2%)
775 (+1%)

proof_construction_time_sha256_30_ms
11,408
3,063
1,374
1,408 (-1%)
1,456

proof_construction_time_sha256_100_ms
43,954
11,796 (+1%)
5,444
5,391
5,349

proof_construction_time_poseidon_hash_ms
78.0 (-1%)
34.0
34.0
58.0
86.0 (-2%)

proof_construction_time_poseidon_hash_30_ms
1,520
416
200
219 (-4%)
267 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,748
1,567
726
796 (+2%)
787 (-1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
1,412
1,412
1,412

l1_rollup_calldata_gas
9,452
9,448
9,452

l1_rollup_execution_gas
610,273
610,269
610,273

l2_block_processing_time_in_ms
750 (-1%)
1,405 (-1%)
2,673 (-1%)

l2_block_building_time_in_ms
22,972 (-1%)
45,607 (-1%)
90,105 (-1%)

l2_block_rollup_simulation_time_in_ms
22,876 (-1%)
45,313 (-1%)
89,760 (-1%)

l2_block_public_tx_process_time_in_ms
19,597 (-1%)
41,888 (-1%)
86,350 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
6,402 (-1%)
9,255 (-1%)

node_database_size_in_bytes
10,530,896
14,409,808

pxe_database_size_in_bytes
9,242
15,127

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms

GasToken:_increase_public_balance
71.2 (+2%)

GasToken:set_portal
16.9 (+2%)

Token:constructor
94.8 (+1%)

FPC:constructor
63.5 (-1%)

GasToken:mint_public
53.8 (-2%)

Token:mint_public
:warning: 68.4 (-88%)

Token:assert_minter_and_mint
:warning: 227 (+205%)

SchnorrAccount:approve_public_authwit
32.6 (+3%)

FPC:prepare_fee
75.4 (+2%)

Token:transfer_public
:warning: 34.1 (-34%)

FPC:pay_refund
65.9

Benchmarking:increment_balance
2,396 (-1%)

Token:_increase_public_balance
68.1 (-5%)

FPC:pay_refund_with_shielded_rebate
51.2 (+1%)

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.179 (+1%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.4
16.8 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.604
0.516
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.4
75.4 (-1%)
130 (-1%)
243 (-2%)
467

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
288
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.495
0.464 (-1%)
0.448
0.441 (-1%)
0.435

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
59.6
111 (-1%)
180 (-1%)
350 (-1%)
687

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
208
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.505
0.497 (-1%)
0.478
0.475 (-1%)
0.472

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
74.3 (-1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
135
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.519 (-1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
83,854
676,749

Transaction size based on fee payment method
| Metric |  |
| - |  |


Get user input from budget entry.

What feature are you asking for
Get data from the user from budget entry and apply it to the budget category scene.
Describe the solution you'd like
Get information from currently signed in profile.
Reason
It makes more sense to show the user the budget value they set.

Think this may be a duplicate

It is quite different since I need to gather information to correctly show the budget value in the budget category sence

approved,
CurrentProfile.getInstance().getCurrentProfile().getBudget(); will return you the total budget anywhere in the app. Think this might be helpful, cause I used for total budget value in the piechart


zls download fails

Description
Downloading zls failed. Returns 404
Neovim version
NVIM v0.8.1
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
No response
Operating system and version
debian 11
Affected language servers
zls
Steps to reproduce

nvim
:LspInstall zig
press 1 to select zls and press Enter

Actual behavior
Returns this Error
   ➜ zls (failed)         Downloading file "https://github.com/zigtools/zls/releases/download/0.10.0/x86_64-linux.tar.xz"...         ...taller/lua/nvim-lsp-installer/core/managers/std/init.lua:61: Failed to download file "https://github.com/zigtools/zls/releases/download/0.10.0/x86_64-linux.tar.xz".         spawn: curl failed with exit code 22. curl: (22) The requested URL returned error: 404
when looking at the zls releases page

downloader looks for *.tar.xz file while at release page has *.tar.zst
Expected behavior
No response
Minimal config
N/A

LSP log
N/A

nvim-lspconfig does not have LspInstall command. I think you used the mason or something else .

Lspinstall is not part of this project its this https://github.com/williamboman/nvim-lsp-installer/
And just so you know its deprecated and the the maintainer suggest moving to https://github.com/williamboman/mason.nvim

Oh, my apologies. I thought this was the repo for that.
Thank you


Issues with the Geometry File

Hi Everyone, I am new to coding and doing my best to learn it. I am having issues understanding the Cactus geometry file. I want to simulate a straight-bladed rotor with three blades (Like RM2 tow-tank Experiment Sandia Lab). I don´t know how to calculate the blade unit tangent vectors for my simple geometry to modify the cactus geometry file.
I would appreciate it if you can provide any document to understand this geometry file. So far I have the Cactus and the Cactus development Manual Only.
Thank you.
@whophil

Here, you can say (X, Y, Z) =(2, -4, 1)  are the coordinates at elements ends.

@Satyamshk2 Thank you


When we resize cropper and move cropper browser is crashed or sometimes its hangs too much. Cropper is not working smoothly at all

I am using vue2 and vue-cropper version is 4.2.0

@kaushikmakholiyanls Have you solved it yet?


AddressParser initialisation error

I'm facing the following issue while trying to initialise AddressParser.
>>> parser = pypostalwin.AddressParser()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: AddressParser.__init__() missing 2 required positional arguments: 'address_parser_path' and 'libpostal_path'

Can you please tell me where am I going wrong here?
I'm using the latest version. i.e. 0.0.4.

Sorry didn't follow the first step I guess. :(

i think there is an issue in the recent release ,can you please use this below ,
Please uninstall and reinstall the updated package and enjoy the address expansion feature !!
pip uninstall pypostalwin
pip install pypostalwin==0.0.3

Hi,
Thanks for the comment.
However, while downloading and unpacking the libpostal.7z, it says "No files to process". Is there any updated file of libpostal that I can check?
Your help will be appreciated :)


It might be better to completely reject empty submissions

RT.

You are right, I'll transfer this to the backend repository.


Unit tests for django_get_or_create

For issue https://github.com/rbarrois/factory_boy/issues/297

Merged (adapted) as b81b2d2f95ba5f3446404d8be0c942a412036baa, thanks !!


✨ Introduce doc vars for releases

Summary
This PR introduces some new documentation variables that align with our current release concepts of "latest regular release" and "latest release". This replaces several self-references with just one (the definition of ks_latest_release).
Related issue(s)

Preview at https://mikespreitzer.github.io/kcp-edge-mc/doc-release-vars/

/cc @ezrasilvera
/cc @clubanderson

@MikeSpreitzer I'm a little bothered with the "latest-regular-release"  Vs "latest-release" . Why do we need references for  release candidates ?   It also implies that the "latest-release" is somehow "irregular" or "special" ?
Maybe we should adopt the "stable"  ?  For us, we always said that for now regular==stable (as we don't have stable tests for "stable" )  - I think that having "latest" Vs "latest-stable"  is better

I thought KS already has two release types: official releases and RC releases, and latest simply points at the most recent official release. Is that no longer the case? Is latest-regular another name for "latest non-RC release"?

@ezrasilvera: @eaepstein guessed the answer. Because candidate releases (RCs) are releases, we have established the term "regular" release to distinguish a release that is not an RC from one that is an RC (or alpha or anything else irregular). Thus: "latest regular release" is the latest release that is not an RC (or alpha or...), while "latest release" is the latest release of any sort (including RC or alpha or ...). This is the terminology that we discussed earlier and have been using.
The self references need to refer to self --- even when that self is an RC or alpha --- so the most commonly used variable is ks_latest_release.

What is the difference between RC and alpha releases? May there could just be "releases" and RC-releases", with "latest" pointing at the most recent "release"?

"alpha" is something that @francostellari cajoled me into doing. It is a development snapshot that falls short of the goals for the next regular release. @francostellari's new Helm chart can only use a release, so we needed a release of some sort in order to be able to test and continue developing the Helm chart.
A candidate release is one that, as far as we know, meets the goals for the next regular release.
It will be linguistically confusing if we say that an "RC-release" is not a "release".
Do we really need to re-litigate the terminology right now, as we are trying to get the next regular release out?

@eaepstein: The mike alias named "latest" points to the latest regular release. And the mike version warning banner says "latest release" where it means "latest regular release". This is admittedly inconsistent with the rest of our terminology. This is the result of our historical development path and general hurry.

Do we really need to re-litigate the terminology right now, as we are trying to get the next regular release out?
Seems like "alpha" and "regular" are terms introduced without discussion.

@eaepstein: I definitely remember discussing "regular". The "alpha" was something that we had earlier, then agreed that we do not need any more, then was re-introduced in a rush with only a few people involved.

I believe we agreed that Latest should always point to a "regular" release.   there is no such thing as "latest RC" or "latest Alpha"

@ezrasilvera: you may be referring to the mike alias named "latest". We have a terminology snafu here. The mike alias "latest" points to the "latest regular release", as you observed. If we were completely consistent then we would rename that mike alias from "latest" to "latest_regular". The name of this alias was established long ago, before our current thinking about releases, and nobody has bothered to change it. Also, the mike banner warning about version is also outdated, speaking of "latest release" when it means "latest regular release".
I really do not think we want to have to tell people that "a candidate release is not a release". We needed an explicit word to distinguish candidate releases from non-candidate releases. That is why we agreed to call the non-candidate releases "regular". This was when we expected no "alpha" releases. Now that we also have had some "alpha" releases, this still does not change the need for an explicit word to distinguish the regular releases from the other kinds of releases.
The mkdocs variables that we define are not connected to mike aliases. I chose to introduce variables consistent with our latest thinking and terminology. If anything, I think that the outdated stuff in mike should be updated.

In plain English, since we have candidate releases, one of them is always the latest. So we do have a latest candidate release. Same for alpha. In plain English, the latest release would be the latest release of any kind.

The force-push to c1c306125 is a rebase onto main.

The force-push to 533216965 is a rebase onto main.

Just a note that the "latest release" message is in the main.html file and therefore easily edited:
(this is from kproche.github.io/ )

@MikeSpreitzer Let's merge this and continue the discussion elsewhere
/lgtm
/approve


'Open' stream example ?

The package contains examples of creating ArrayStream objects given a schema and a vector or list of arrays.  That helps for chunks returned via, say, RecordBatchReader as this may not require the contiguous memory an unchunked approach would need.  But as we instantiate with the whole vector (or list) we still require a similar total amount of memory at instantiation.
But can we create, say, a RecordBatchReader is a more 'streaming' fashion?  Could be hand this back to the caller with only the initially-known list of Arrays and also support further data ?  So say the first call of next() would be covered but thereafter a more 'lazy' approach is used and RecordBatchReader supplies updates in true batches.  Obviously a more complicated setup, but is something like this feasible / supported / planned / ... ?
I may be explaining myself poorly here but are there other references in the Arrow context that handle this is as a more 'open' subscription (in the sense of 'total payload unknown at instantiation') with a later callbacks to provide chunked updates?   Or do I have the wrong mental model and should rather think about, say, a pub/sub model where a 'middle man' holds on to the data and passes is along?  (I have done such things with Redis.)
Thanks in advance for any pointers, and apologies for posting such a vague and rambling issue.

Dang, now that you show it to me in narrow I think i recall having seen it there.  And nice and elegant use of environments and function callbacks.  (But we also have to think about how it could be done in Python off the same C level base layer.)
Overall seems like a good thing for say, a database wrapper (and when I briefly played with the adbc packages I noticed how they return a RecordBatchReader from queries but I have yet to dive in there and so more closely what they do).
Appreciate the quick and thoughtful reply.

Thanks for the links to these, and for doing them -- they are well done.  Now, I have (much) more of an R / C++ focus so I am not exactly your target audience on the Python output. That said, I am trying to get my Python-using colleagues to pay more attention to nanoarrow and your videos may be perfect as an intro (if they can sit down and watch these -- I was fading a little at the end).
(I have been doing a lot of similar obs videos for a class I teach a term a year, but I have not 'spliced' pieces together.  Can you recommend an equally-easy piece of software?)
Again, thanks a lot for these. Well done. I'm also quite jealous about your languageserver integration into Emacs which is slicker than what I use (esp in mixed-language projects).

Thanks! Yea some of the videos are long (especially the third...). Hoping to make them more succinct going forward.
For the video I use OpenStudio. I am not very skilled at video, but it seems pretty easy to use.
For Emacs I use eglot with the clangd language server

Did you mean obs studio there?  I am happy with that (on Linux/Ubuntu) to record and even stream, I have not looked into 'combining' different snippets.  You managed to 'splice' when waiting for sum() or with the inr32() / int64() error in the third.  Can one do that editing in obs as well?

Sorry for the typo. It's openshot - https://www.openshot.org/

Perfect.  Just got there or thereabouts via a quick google search.


Add Files UWP

Microsoft Reviewers: Open in CodeFlow

Duplicate of #925, tho yours looks correct, could suggest changes

@OfficialEsco go for #925 👍


Program's github link is incorrect

Correct link:
https://github.com/Malin001/Legilimens-Hogwarts-Legacy-Collectible-Finder
Link found inside program

Good catch! It should actually be https://github.com/Malin001/Legilimens-Hogwarts-Legacy-cpp, since the C++ and Python versions have separate GitHub pages. Either way, it's fixed now.


Fix for LLVM 12 compatibilty

Description
This patch fixes a compatibility with LLVM 13 and up based on this change and the possible removal of StackAlignmentOverride.
Tests
Available resulting test

Patch:
osl-llvm12.diff.txt
diff -Naur OpenShadingLanguage-Release-<IP_ADDRESS>.orig/src/liboslexec/llvm_util.cpp OpenShadingLanguage-Release-<IP_ADDRESS>/src/liboslexec/llvm_util.cpp
--- OpenShadingLanguage-Release-<IP_ADDRESS>.orig/src/liboslexec/llvm_util.cpp	2021-09-01 00:26:06.000000000 -0700
+++ OpenShadingLanguage-Release-<IP_ADDRESS>/src/liboslexec/llvm_util.cpp	2021-09-03 17:14:01.840127907 -0700
@@ -1228,7 +1228,9 @@

     options.NoZerosInBSS = false;
     options.GuaranteedTailCallOpt = false;
+#if OSL_LLVM_VERSION < 120
     options.StackAlignmentOverride = 0;
+#endif
     options.FunctionSections = true;
     options.UseInitArray = false;
     options.FloatABIType = llvm::FloatABI::Default;
@@ -2989,7 +2991,7 @@
 LLVM_Util::write_bitcode_file (const char *filename, std::string *err)
 {
     std::error_code local_error;
-    llvm::raw_fd_ostream out (filename, local_error, llvm::sys::fs::F_None);
+    llvm::raw_fd_ostream out (filename, local_error, llvm::sys::fs::OF_None);
     if (! out.has_error()) {
         llvm::WriteBitcodeToFile (*module(), out);
         if (err && local_error)
@@ -3051,7 +3053,9 @@
     options.AllowFPOpFusion                        = llvm::FPOpFusion::Fast;
     options.NoZerosInBSS                           = 0;
     options.GuaranteedTailCallOpt                  = 0;
+#if OSL_LLVM_VERSION < 120
     options.StackAlignmentOverride                 = 0;
+#endif
     options.UseInitArray                           = 0;

     llvm::TargetMachine* target_machine = llvm_target->createTargetMachine(

Checklist:

[x] I have read the contribution guidelines.
[x] I have previously submitted a Contributor License Agreement.
[ ] I have updated the documentation, if applicable.
[ ] I have ensured that the change is tested somewhere in the testsuite (adding new test cases if necessary).
[x] My code follows the prevailing code style of this project.

I'm not sure what's going on with this, but can you please rebase on the top of the current master for this PR?

I think I see. These ARE changes on top of master, but somehow when you submitted the PR, you told GitHub you were submitted it against release rather than against master, so this makes it think the patch consists of EVERYTHING it would take to turn release into master. Are you able to edit that on your end? If not, then I suggest closing and file a new PR, but this time be sure GH knows that you're intending for it to be a patch against master.

Ping!
Can you please either alter the PR so that you are submitting to release instead of to master? Or rebase your changes on the current master?

Ping!
Can you please either alter the PR so that you are submitting to release instead of to master? Or rebase your changes on the current master?
I am closing this pull request as it is now moved to #1412


Training is not using 100% CPU

I am running the examples on my Ubuntu machine Intel® Core i7-4770K CPU @ 3.50GHz with 4 cores. During the entire training, only ~25% of the CPU is used. Which means it is running on only one core. Am I missing something?

I know this is necro, but I figure since we're kicking new life into this, may as well revisit some of these open threads.
I could be wrong, but my understanding of why this seems to happen is that you'd need to use an async agent like A3C or async DDPG or whatever to make use of all possible threads on your processor. If you're using the cpu version of tensorflow, it should utilize most of your CPU to train the neural networks, but unlike with traditional machine learning, the neural networks only get updated after your environment takes a step, and that training is only for a sample size of 1, so that part can run pretty quickly and may just show up on your CPU load as a quick peak. The environment you're using may be rather CPU intense (like mine has to a ton of math each step), and unless your environment is multi-threading somehow, that's just going to run on one CPU.  A3C and other asynchronous algorithms will create multiple actor/critic pairs that will run in parallel with one another, so with those, you can use your full CPU (and GPU) potential. That's why they're so popular, and why I want to get async DDPG built here.


Hotfix/issue 750

Added SHA256 as a hashing option.
New configuration setting: SSO_SIGNING_ALGORITHM:

if not present, default is SHA1
correct values are either SHA1 or SHA256

This change is

Reviewed 11 of 11 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Google Maps Travel Time rounding

Make sure you run the latest version before reporting an issue. Feature requests should go in the forum: https://community.home-assistant.io/c/feature-requests
Home Assistant release (hass --version):
1.9.4
Python release (python3 --version):
3.4.3+
Component/platform:
Google Mapts Travel Time
Description of problem:
Seems some issues with rounding the travel time number, I get results such as: 31.31666666667 minutes :)

Technically you can use a template sensor to get a rounded version, but I'd also prefer the minutes be rounded directly in the component. I can't think of an argument for having that much precision!

Yeah there is no need for any decimals for minutes, a PR would be welcome.

Fixed by PR #2086


cob_driver: 0.7.3-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cob_driver to 0.7.3-1:

upstream repository: https://github.com/ipa320/cob_driver.git
release repository: https://github.com/ipa320/cob_driver-release.git
distro file: melodic/distribution.yaml
bloom version: 0.9.3
previous version for package: 0.7.1-1

cob_base_drive_chain

No changes

cob_bms_driver

No changes

cob_camera_sensors

No changes

cob_canopen_motor

No changes

cob_driver

No changes

cob_elmo_homing

No changes

cob_generic_can

No changes

cob_light

No changes

cob_mimic
* Merge pull request #413 <https://github.com/ipa320/cob_driver/issues/413> from fmessmer/remove_mimic_python
  remove cob_mimic python driver
* remove cob_mimic python driver
* Contributors: Felix Messmer, fmessmer

cob_phidget_em_state

No changes

cob_phidget_power_state

No changes

cob_phidgets

No changes

cob_relayboard

No changes

cob_scan_unifier

No changes

cob_sick_lms1xx

No changes

cob_sick_s300

No changes

cob_sound

No changes

cob_undercarriage_ctrl

No changes

cob_utilities

No changes

cob_voltage_control

No changes

laser_scan_densifier

No changes

Holding for sync


Replace references to zetam with sourceforge

The README.md page refers to https://clover-wiki.zetam.org/. The https://cloverdb.com/ page also refers to zetam. That site is no longer available.
It appears that the wiki on Sourceforge (https://sourceforge.net/p/cloverefiboot/wiki/Home/) is the new "best place" to link to. (See https://sourceforge.net/p/cloverefiboot/discussion/1726372/thread/74b0d82226/) Thanks.

This is now fixed.


Filter by username doens't work

Affects: logevents.php
The filter by username filter doesn't work.

Fixed in 588c37b17bbd9989041654b7692108245040898c.

The issue was that usernames were written with parentheses in the database. So old log events are still affected, but new ones will not be.

Fixed in 588c37b.