registration

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/78970
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 1f97226795940004521673cc96ccce78a217f1db
git push origin v0.1.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/79020
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 4adc8c78248e9a2d6da14cbcca51cb49ec4fdb23
git push origin v0.1.1

@JuliaRegistrator register()

Error while trying to register: Version 0.1.0 already exists

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/80321
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" fdfbf270a1d22d0baa918fbc801b937b5e7daff1
git push origin v0.2.0

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/79020
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 91d757aabb70fd371a7719e50d3c73c4b80c11bf
git push origin v0.1.1

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/79020
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 9154d0163d549de123c6af5e7a3ce656a4936776
git push origin v0.1.1

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/79020
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.1 -m "<description of version>" 0f31783cf98ba344b9f509ee93445374b3d408ce
git push origin v0.1.1

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/80323
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.2 -m "<description of version>" e4fb09764413caccfbf9a75444ad6fa08ccd198f
git push origin v0.1.2

Registration pull request created: JuliaRegistries/General/81362
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.3 -m "<description of version>" a1ef98f6f4aa4692098fcdb41ba244ffe1b1fd9c
git push origin v0.1.3

@JuliaRegistrator register()

Error while trying to register: Error in (Julia)Project.toml: Package 'J_Space' with UUID: fd1b0027-9d6f-49b5-97ba-2af5672b046a not found in registry or stdlib

Error while trying to register: Error in (Julia)Project.toml: Package 'J_Space' with UUID: fd1b0027-9d6f-49b5-97ba-2af5672b046a not found in registry or stdlib

@JuliaRegistrator register()

Error while trying to register: Error in (Julia)Project.toml: Package 'J_Space' with UUID: fd1b0027-9d6f-49b5-97ba-2af5672b046a not found in registry or stdlib

@JuliaRegistrator register()

Error while trying to register: Error in (Julia)Project.toml: Package 'J_Space' with UUID: fd1b0027-9d6f-49b5-97ba-2af5672b046a not found in registry or stdlib


clear runtimectx on exit to avoid refcycles

...in particular through frame->runtimectx->framstack->frame
and CURRENT_FRAME->caught exception->frame->f_back...->CURRENT_FRAME
Fixes: #1074
All analysis credit to @kshitij12345 and @lantiga , screwing up the fix is me.

So it seems this is overambitious. Maybe we try to clear the things holding the ctx instead.

Superseded by #1170


How can we use hardhat-ethers 'getImpersonatedSigner' ?

Hello,
I'm trying to use 'getImpersonatedSigner' function :
https://hardhat.org/hardhat-network/docs/guides/forking-other-networks#impersonating-accounts
Here is a sample script that only works with ethers.getImpersonatedSigner :
const usdc = await ethers.getContractAt(
    usdcAbi,
    usdcTokenAddress,
    deployer
  );

  const usdcOwner = await usdc.owner();
  const impersonatedUsdcOwner = await ethers.getImpersonatedSigner(usdcOwner);
  const connectedUsdcOwner = await usdc.connect(impersonatedUsdcOwner);

• If I use the regular ethers.getSigner => I get a ProviderError: HttpProviderError
• If I use ethers.getImpersonatedSigner  => This works
For getImpersonatedSigner to be available I need to remove the NPM alias "@nomiclabs/hardhat-ethers": "npm:hardhat-deploy-ethers",
But then I cant use ethers.getContract in my deployment scripts...
Is there a workaround ?

Ok forget it the alternative from the hardhat doc actually works fine, my bad, sorry for the noise 😅


fix(config): add 11 to ZEN17 parameters 2 & 3

Adds value 11 to parameters 2 & 3 which was added in firmwareVersion 1.4.
Source:
https://www.support.getzooz.com/kb/article/698-zen17-universal-relay-advanced-settings/

@zwave-js-bot help?


Artifacts cannot be downloaded from Jitpack

Within Java project using Maven build dependency like it stated by Jitpack:
https://jitpack.io/#andreypfau/ton-kotlin
most artifacts cannot be downloaded.
For example vesion "adnl-1840f76479-1" is ok, other fail.

Fixed: https://jitpack.io/#andreypfau/ton-kotlin/0868ad55ec


Should we-organize our GitHub pages to a directory on main?

Splitting this out from #3766, to which it is still somewhat related as we should consider the impact on how many PRs to how many different branches are required for a change that spans the spec and the registries.
Originally, gh-pages sites needed to be on a gh-pages branch that (as ours does) typically has a completely different layout than main.  That is no longer required, and it is much more common to deploy from a directory on main.  Or at least from a directory on a branch that is no more different from main than any other working branch.

I totally agree with this one. This might be a personal preference but I usually find it confusing when each branch is a different project completely. I can start with this one after this is closed https://github.com/OAI/OpenAPI-Specification/issues/1823

We should consider having a dedicated repo for spec.openapis.org? As we have now moved to a multi-specification project (and likely more coming - Overlays), nesting the website housing the specs under one of the specification repos is a little confusing.
Each separate specification repo that wants to publish can issue PRs to the repo housing the HTML versions and other information relevant to spec.openapis.org. We could then have the same process in place for both OpenAPI-Specification and Arazzo-Specification repos.

@frankkilcommins Should each spec has its own domain maybe? For example, arazzo.openapis.org, overlays.openapis.org etc. Or a single repo for everyone is the best option?

@Bellangelo We want a unified brand across the different specs, so I think we'll want to stick with spec.openapis.org.

@handrews Fair enough. I see that @darrelmiller invited me to the organization, so now I have access to create a repo. Should I create a spec.openapis.org repo and move there the website?

@Bellangelo I was surprised about repository creation privileges but it looks like a recent change that GitHub made, giving members more abilities.  Let's make sure @darrelmiller or another admin is OK with the separate-repository choice.
There might need to be a bit of work to figure out how the publishing of specs and schemas changes.  Not so much the technical logistics (which I'm sure you can sort out) but the policy side of things.

We are generally in favour. But we will need some process, governance and maintenance setup to enable this change. A good discussion in TDC, but we are not ready to make the change immediately.

Discussed in TSC and agreed that a new repository will be a good home for our web presence and having it separate will give us a few advantages:

people who care about web tooling can help us with it without needing access to any/all of the spec repos
it's really clear that changes there are being published to our official site (currently you can merge something to a branch and it's not at all obvious it will cause a rebuild/deploy elsewhere)
we may be able to get better previews for pull requests with the separate repository setup

@Bellangelo does it make sense to proceed with #3868 to apply the changes you already worked on since I assume we'll use the main branch in a new repo too? Let us know what you think.

@Bellangelo @frankkilcommins I think when moving to a separate repository, we should endeavor to move as much infrastructure as possible out of this repository.  As obnoxious as git submodules are, if we need to run build steps from this or other specification repositories, I think it would be better to pull in the common repo as a submodule rather than have any duplicated build infrastructure.

@Bellangelo does it make sense to proceed with https://github.com/OAI/OpenAPI-Specification/pull/3868 to apply the changes you already worked on since I assume we'll use the main branch in a new repo too? Let us know what you think.

@lornajane Hmm.. that's a good question. Since we want to immediately move to a new repo we might not need to proceed with the https://github.com/OAI/OpenAPI-Specification/pull/3868 as it will require double the work from the Arazzo team since they will have to create a PR for this change and a second one for when we will move to the new repo.
But what is missing from our side is the mechanism that they have implemented in Arazzo that builds the site and opens a new PR in the repo. If we think that this whole progress will take too much time we might want to proceed with https://github.com/OAI/OpenAPI-Specification/pull/3868 just so we can get things moving.
To sum up, I am ok to proceed with both ways. If we go immediately with the new repo I will need someone to create a new repo for me.

I think it would be better to pull in the common repo as a submodule rather than have any duplicated build infrastructure.
@handrews Yes and no. While I agree that we should minimize our infrastructure, the truth is that it is just a coincidence that these 2 specs both use the same building mechanism. I am 100% sure that Arazzo copied our mechanism for a faster release. Other than this, I think there isn't any rule / constraint / limitation for Arazzo to choose whatever site builder it wants.
Perhaps, I might have lost your point and actually what you are suggesting is that they should be handled as a single site instead.

I am 100% sure that Arazzo copied our mechanism for a faster release. Other than this, I think there isn't any rule / constraint / limitation for Arazzo to choose whatever site builder it wants.

We in general want to get everything on the same infrastructure.  This is really one big project, and we should be releasing all of our specifications the same and managing our web sites the same (although I realize that might not be immeidately apparent... it's aspirational 🙂 )

Info from PR #3868, which we are closing simply because the whole structure has changed too much and the PR will need to be re-visited:

What [@Bellangelo did]:

Go to gh-pages and move all files under the docs folder which Github supports.
Go to main branch and run git merge gh-pages --allow-unrelated-histories. This merged the 2 branches even if they had unrelated histories.
Updated scripts and references. There are some references in the spec.js files but I think they are unused.

What we need to do after merge:

Go to Settings>Pages and under the Branch section select the main branch and the docs folder`.

After you update the settings, an action will run to deploy the site again.
We keep the gh-pages for a few weeks, just to be able to quickly change in case of a bug in the process, and then we delete it.

How to review
To quickly skip and verify the updated files, just follow the What I have done section and then you can just git diff to distinguished what files have been moved and what files contain actual changes.


Reporting Enhancements

Having recently implemented YAP our helpline chair asked about more/improved reporting.
Some of this would be for presenting data to the service body. And some would help to improve volunteer scheduling.

The ability to set a date range for viewing/printing report logs
The ability to see at a glance the number of calls to volunteers received for a given date range
The ability to see at a glance the number of meeting sms requests for a given date range
The ability to see at a glance  the number and time of day of missed calls for a given date range

Going to add a date-picker as the first step here.

+1 to this request.

I've had a lot of areas (FL Region) requesting this as well.  Especially "the ability to see at a glance the number of meeting sms requests for a given date range"
Thank you!

Rough version of summary

This will be useful for us as well!  One small but helpful addition to this summary would be to report the number of completed calls to a volunteer, and the number of attempted calls to a volunteer that went unanswered.

I'm sure there are number of other metrics that could be added over time.  Everyone will want their pet metric!

Agree with @alanb2718 those are metrics our Area are interested in. Also, part of the original ticket. No rush, just something we'd like to see. Thanks for adding the custom range. That's a huge help for us!

mine too, I currently use some crazy php script i wrote to parse and get those metrics

First pass at reporting metric summaries.  I've included two basic ones here:

Currently (as of the latest stable release 4.0.4), no events are captured as to whether a meeting was searched by phone or SMS, so historical data will be difficult if not impossible to find.  This will be a going forward metric point.

SMS Metrics + Reporting included now

Almost all of these are Available in 4.1.0-beta2 if you want to test.
https://github.com/bmlt-enabled/yap/releases/tag/4.1.0-beta2

I'll install and let you know if there are any issues. Thanks for the work on this

After initial look seems to working as expected. I'll get with our Helpline chair to go over the specifics. Am getting one "error" but can't tell if it's having any practical effect on reporting.
Remote Pagination Error - Server response missing 'last_page' property

O._parseRemoteData | @ | yap-reports.min.js:formatted:12841
-- | -- | --
  | (anonymous) | @ | yap-reports.min.js:formatted:12829
  | Promise.then (async) |   |
  | (anonymous) | @ | yap-reports.min.js:formatted:12828
  | O._getRemotePage | @ | yap-reports.min.js:formatted:12811
  | (anonymous) | @ | yap-reports.min.js:formatted:12795
  | O.trigger | @ | yap-reports.min.js:formatted:12782
  | (anonymous) | @ | yap-reports.min.js:formatted:12656
  | O.setPage | @ | yap-reports.min.js:formatted:12654
  | u._setData | @ | yap-reports.min.js:formatted:5971
  | u.setData | @ | yap-reports.min.js:formatted:5966
  | updateCallRecords | @ | yap.min.js:1
  | updateAllReports | @ | yap.min.js:1
  | (anonymous) | @ | yap.min.js:1
  | dispatch | @ | yap.min.js:1
  | g.handle | @ | yap.min.js:1

I also got this same error and wasn't sure what to make of it

Was there any repro steps?
From: Kevin Grimley @.>
Date: Monday, August 1, 2022 at 4:40 PM
To: bmlt-enabled/yap @.>
Cc: Danny Gershman @.>, Comment @.>
Subject: Re: [bmlt-enabled/yap] Reporting Enhancements (Issue #574)
After initial look seems to working as expected. I'll get with our Helpline chair to go over the specifics. Am getting one "error" but can't tell if it's having any practical effect on reporting.
Remote Pagination Error - Server response missing 'last_page' property
O._parseRemoteData | @ | yap-reports.min.js:formatted:12841
-- | -- | --
| (anonymous) | @ | yap-reports.min.js:formatted:12829
| Promise.then (async) |   |
| (anonymous) | @ | yap-reports.min.js:formatted:12828
| O._getRemotePage | @ | yap-reports.min.js:formatted:12811
| (anonymous) | @ | yap-reports.min.js:formatted:12795
| O.trigger | @ | yap-reports.min.js:formatted:12782
| (anonymous) | @ | yap-reports.min.js:formatted:12656
| O.setPage | @ | yap-reports.min.js:formatted:12654
| u._setData | @ | yap-reports.min.js:formatted:5971
| u.setData | @ | yap-reports.min.js:formatted:5966
| updateCallRecords | @ | yap.min.js:1
| updateAllReports | @ | yap.min.js:1
| (anonymous) | @ | yap.min.js:1
| dispatch | @ | yap.min.js:1
| g.handle | @ | yap.min.js:1
—
Reply to this email directly, view it on GitHubhttps://github.com/bmlt-enabled/yap/issues/574#issuecomment-1201697311, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOD3OZYO32CNHCAH7DY5QTVXAY2RANCNFSM5JNMIEMQ.
You are receiving this because you commented.Message ID: @.***>

for me with firefox this happens just by clicking on reports tab then selecting a service body no additional steps

Same for me in Chrome

resolved in beta3.

fixes released in 4.1.0

Split off the missed call count feature to it's own ticket https://github.com/bmlt-enabled/yap/issues/611

This will be useful for us as well!  One small but helpful addition to this summary would be to report the number of completed calls to a volunteer, and the number of attempted calls to a volunteer that went unanswered.

This is essentially addressed in 4.1.1

Split off the missed call count feature to it's own ticket https://github.com/bmlt-enabled/yap/issues/611

Addressed in 4.1.1 which was released a few moments ago.


Switch OS packages to pkgbase.

It is becoming more challenging to maintain OS ports. Now that the FreeBSD package base is up and running. It is a more viable solution since FreeBSD will maintain the package base.
The os-generic-userland ports won't be built anymore, as changes were made last December in freebsd-ports.
Initial Task:

[x] #153

Infrastructure task:

[x] #158
[x] #157
[x] #159
[x] #156
[x] https://github.com/ghostbsd/ghostbsd-build/pull/195

related software

[x] #160
[x] #161
[ ] #154
[x] #155

Fix #2


Documentation site

I've just deployed swagger-ui with the current yaml file on my github pages : https://axlbonnet.github.io/CARMIN/
I've not tuned anything, this is just swagger-ui out of the box with our OpenAPI file.
I think we could quickly show it on the CARMIN account without many modifications.

I created a CARMIN organization on Swagger Hug and added version 0.3 of the spec: https://app.swaggerhub.com/apis/CARMIN/carmin-common_api_for_research_medical_imaging_network/0.3


2.3 docs updates

Closes #
What's Changed

Screenshots

TODO

[ ] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example App Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

@lampwins Do you plan to do a second separate PR to handle any updates to the module and cloud docs for 2.3? In particular I'm thinking of https://github.com/nautobot/nautobot/pull/6035#discussion_r1704479043 for the cloud docs.


Enable ONNX test in circle CI

The PR disable onnx test since it is failing since 11/14/2020. I did a test locally and find that onnx need update to 1.8.0. So This PR aims to enable onnx test by pulling latest onnx==1.8.0.
The root cause is that onnx_shape_inference is enabled on 11/13/2020, but the shape inference PR (committed 9/30/2020) does not handle invalid dynamic axes input well. In torch vision CI, there are some invalid axes, so we fixed it in this PR, and enable onnx test. In a separate pytorch PR, we add exception handling for invalid axes input, then it will give meaningful failure msg rather than seg fault here.

@fmassa I try to enable onnx test, it works in my local machine, but fails in the Ci build here, it shows
free(): invalid next size (fast)
which is a memory issue. Do you have any ideas on why this happen? thanks!

Hi @jiafatom
Thanks for the PR!

Do you have any ideas on why this happen?

I don't know what could be the issue. This looks like something inside ORT might be problematic?

@fmassa Just fixed the issue, and test_onnx passes in CircleCI, could you please sign off? Thank you!

@jiafatom I think the test broke again, possibly due to upstream changes. Could you have a look on your side and confirm?

@datumbox
Could you please show me the link of test broken? I am checking https://travis-ci.org/github/pytorch/vision/builds
The last time the master branch runs is 12/8/2020, that is 3 days ago, before this commits checked in.
The latest job failure is https://travis-ci.org/github/pytorch/vision/jobs/748808277
but this is a v0.8.2 branch, not related to this PR.
v0.8.2 did pip install -q --user -i https://test.pypi.org/simple/ ort-nightly==1.4.0.dev202008122
I cannot find this ort-nightly in pytorch/vision master.
This ort-nightly cannot be fetched, the possible explanation is that onnxruntime 1.6.0 released on 12/10/2020 (yesterday),
so some old ort-nightly is removed.
Try to use pip install --user -i https://test.pypi.org/simple/ ort-nightly==1.5.2.dev202012031 instead.
Please let me know if you have other questions. Thanks.

@jiafatom check https://github.com/pytorch/vision/pull/3123 for example, where the only failing job is an ONNX test job.

@datumbox @fmassa
There is a PR merged in pytorch at 12:30 pm 12/10/2020 (yesterday). That PR changes pytorch-onnx exporter API for a special case when the last input is a dictionary. So we need fix our unit test here.
The fix is here, please sign off, thank you!
cc @spandantiwari

Hi @fmassa  - thank you for your help with this. @jiafatom is working with our team. This latest PR https://github.com/pytorch/vision/pull/3160 should fix the test. It was broken because of a commit that went into PyTorch recently (just yesterday). It seems like there was a bit of difference in test running in PyTorch CI which is why this wasn't immediately detected for the PyTorch commit. We are going to update the version of tests running in PyTorch CI so that it matches vision tests with priority.
Thanks again for your help.

@spandantiwari @jiafatom I confirm that the PR #3160 fixed the issue. Thanks a lot for your speedy response and support. We just merged the fix into master. Have great weekend.

Thanks @jiafatom and @spandantiwari for the help!


News Feed shows "Loading" if RSS feed is empty

I found a bug in MagicMirror
Platform: Raspberry Pi 4 with Raspberry Pi OS with desktop
MagicMirror Version: 2.17.0
Description: If the subscribed RSS feed is empty (I use a traffic warning message feed), then "Loading ..." is displayed, although "hideLoading: true" is set.
Steps to Reproduce: The RSS feed is empty or you set the time after which the news is outdated to a very short one.
Expected Results: The news feed module should be hidden. Because I have set hideLoading: true.
Actual Results: "Loading ..." is displayed and refreshed after the updateInterval.
Configuration:
{
	module: "newsfeed",
	position: "bottom_center",
	config: {
		feeds: [
			{
				title: "Verkehrswarnmeldung",  // = Traffic warning message
				url: "https://www.polizei.sachsen.de/vwd/LMSSN-Bestand.RSS_STD.xml",
				encoding: "ISO-8859-1" // default is "UTF-8"
			}
		],
		hideLoading: true,
		showSourceTitle: true,
		showPublishDate: true,
		broadcastNewsFeeds: false,
		broadcastNewsUpdates: false,
		showDescription: true,
		ignoreOldItems: true,
		ignoreOlderThan: 24 * 60 * 60 * 1000,  // 1 day
		updateInterval: 15 * 1000, // 15 seconds default is 10
		prohibitedWords: ['A9', 'A38', 'A72']
	}
},

can reproduce this but have no idea how to solve this at the moment ...

I created a PR that displays a message if the newsfeed is empty ATM. Maybe later we can make it configurable (show info message OR hideCompletly)?


Pause icon won't change

I've not installed the background mode, and I'm using native media plugin as you recommended.
I'm waiting for the event running to create controls, but then if I pause the music, the notification icon wont change.
    this.music = this.media.create(trackSrc)
      this.music.onStatusUpdate.subscribe(
        (status) => {
          switch (status) {
              case this.media.MEDIA_STARTING:
              break;
              case this.media.MEDIA_RUNNING:
                this.loadMusicControls() // LOAD MUSIC CONTROLS
              break;
          }}
       )
      this.music.play()

And this is how I create the controls:
loadMusicControls()
  {
    MusicControls.destroy()

    // Music Controls
    MusicControls.create({
      track       : this.currentlyPlaying().title,
      artist      : this.currentlyPlaying().author,
      cover       : this.bookCover,

      // hide previous/next/close buttons:
      hasPrev   : false,		// show previous button, optional, default: true
      hasNext   : false,		// show next button, optional, default: true
      hasPause   : true,		// show pause button, optional, default: false
      hasClose  : true,		// show close button, optional, default: false
    }, (s) =>{},  (error) =>{});

    function eventsReader(playListService, action) {
       ...
    }

    MusicControls.subscribe((events) => {eventsReader(this, events)});

    // Start listening for events
    // The plugin will run the events function each time an event is fired
    MusicControls.listen();

  }

I have the same issue, a workaround that works for me is to add following code wherever you hit play or pause button (both in the app and on the lock screen controls).
Every time I hit play, I add:
MusicControls.updateIsPlaying(true);
MusicControls.updateDismissable(false);

Every time I hit pause, I add:
MusicControls.updateIsPlaying(false);
MusicControls.updateDismissable(true);

When the user of my app come to the screen with audio, I use following code to initialize music controls:
      window.MusicControls.create(
        me.musicControlsConfig,
        () => {
          window.MusicControls.updateIsPlaying(false)
          window.MusicControls.updateDismissable(true)

          function events(action) {
            const message = JSON.parse(action).message
            switch (message) {
              case 'music-controls-next':
                // Do something
                me.next()
                break
              case 'music-controls-previous':
                // Do something
                me.prev()
                break
              case 'music-controls-pause':
                // Do something
                window.MusicControls.updateIsPlaying(false);
                window.MusicControls.updateDismissable(true);
                me.pause(me.my_media)
                break
              case 'music-controls-play':
                // Do something
                window.MusicControls.updateIsPlaying(true);
                window.MusicControls.updateDismissable(false);
                me.play(me.my_media)
                break
              case 'music-controls-destroy':
                // Do something
                me.stop()
                break
            }
          }

          window.MusicControls.subscribe(events)
          window.MusicControls.listen()

          console.log(
            'music controls created:\n' + JSON.stringify(window.MusicControls)
          )
        },
        (e) => {
          console.log(
            'fail to create music controls, err: ' + JSON.stringify(e)
          )
        }
      )

@AEiosApp  Thanks! That's actually the workaround I'm using but I read the author mentioning that should be automatic while using cordova media plugin.

changing whether the controls are dismissable is entirely up to your preference, whether they are dismissable or not is not tied in any way to the media state, it's up to your app to decide.  Personally I give people the choice if they want to dismiss the notification that's fine.
For the isPlaying status, I have just doublechecked one of my own apps.  What I have done is in the mediacontrols creation bound isPlaying to a variable.  Native media events will update this for system generated changes, like end of track etc and for manual intervention (user pressed button, remote controls event etc) I will update this in my play/pause functions.  This is in angular which has change detection.
Having the update to a variable in your play/pause function let's you only add that code once and have it work regardless of what triggers the change in status.
So you are right it does need to be updated, I just completely missed it due to the way I have always implemented this in my own code, apologies for any confusion there.

changing whether the controls are dismissable is entirely up to your preference, whether they are dismissable or not is not tied in any way to the media state, it's up to your app to decide.  Personally I give people the choice if they want to dismiss the notification that's fine.
For the isPlaying status, I have just doublechecked one of my own apps.  What I have done is in the mediacontrols creation bound isPlaying to a variable.  Native media events will update this for system generated changes, like end of track etc and for manual intervention (user pressed button, remote controls event etc) I will update this in my play/pause functions.  This is in angular which has change detection.
Having the update to a variable in your play/pause function let's you only add that code once and have it work regardless of what triggers the change in status.
So you are right it does need to be updated, I just completely missed it due to the way I have always implemented this in my own code, apologies for any confusion there.


Combine worker executors and allow request queues

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9792/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9789/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9791/
Test FAILed.

alluxio-bot, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9796/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9797/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9798/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9803/
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9805/
Test FAILed.

jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/9812/
Test PASSed.

@ZacBlanco Do you mind adding some description explaining what this PR is trying to solve?

@ZacBlanco Is this parked?

Would prefer that this PR gets closed in favor of this one instead: https://github.com/Alluxio/alluxio/pull/11517
The PR above has all these changes + metrics for the queues


feat(transformer/class-properties): transform private field expression which refers to private method

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#8102  👈 (View in Graphite)
#8100
#8099
#8098
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.


disable test for zk which fail on windows for the time being

this must be merged so that window test can succeeed


How to describe an array of objects

My message payload is array of objects. How I can describe it in yaml? What I tried:
message:
    payload:
        type: array
        items:
            type: object
            additionalProperties: false
            properties:
                id:
                    type: string
                name:
                    type: string

Is it true?

Yes, that seems correct. For this type of questions, you may want to use the Slack channel. It's faster and more people will see your question :)


Problems with Nextcloud Push

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image? Yes, updated every 6hrs with watchtower.
Are you sure you're not using someone else's docker image? Yep.
If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network? Not a problem w/ LE.

Describe the bug

A clear and concise description of what the bug is.
The X-Forwarded-For header is not forwarded. Nextcloud thinks I am connecting from the outside IP, not the Proxy IP.

What version of Nginx Proxy Manager is reported on the login page?
2.8.0

To Reproduce
Steps to reproduce the behavior:
Adding the following to the "Advanced" config does not forward the IP of the Proxy itself:
location /push/ {
    proxy_pass http://<Nextcloud-IP>:7867/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "Upgrade";
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

This also happens when I add the following to the "Locations" tab, just without the last one and the first two lines.
The Proxy is using Host Networking, Nextcloud is running on another machine.
Running
./occ notify_push:setup https://cloud.<MY-DOMAIN>.<MY-TLD>/push

returns the following:
✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
🗴 push server is not a trusted proxy, please add '<PUBLIC-IP>' to the list of trusted proxies or configure any existing reverse proxy to forward the 'x-forwarded-for' send by the push server.

Expected behavior
Forward the X-Forwarded-For to Nextcloud
Screenshots
If applicable, add screenshots to help explain your problem.
Operating System
RPI
Additional context
My Nextcloud config.php:
...
  'trusted_proxies' =>
  array (
    0 => '<NPM-IP>',
  ),
);

Hello,
have you tried to add the line below in nextcloud's config.php file ?
'overwriteprotocol' => 'https'

Yes, that's my default config whenever I deploy one.
I found another solution, which is described after updating the notify_push app and executing the command again. It skips the nginx proxy entirely.

Yes, that's my default config whenever I deploy one.
I found another solution, which is described after updating the notify_push app and executing the command again. It skips the nginx proxy entirely.


fix(docs): missing a necessary step and fixed broken links

Fixed broken links and added a step needed to avoid an error.

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


Use unLoc instead of reimplementing it

Thanks! Cc @zilu41. Also feel free to comment on other people's PR's at any point - the more reviewers the better.


feat: deployment of v3.5.3 to Arbitrum One

Description
Add a description of your changes here.
Is this PR related with an open issue?
Related to Issue #
Types of changes

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

Checklist:

[ ] Follows the code style of this project.
[ ] Tests Cover Changes
[ ] Documentation

Funny gif

https://artifacts.nevermined.network/42161/public/contracts_v3.5.3.json


Fix typo in WallVisitorUtils

WallVisitorUtils#checkSelelct 修正为  WallVisitorUtils#checkSelect，同时标记 WallVisitorUtils#checkSelelct 为 deprecated

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


Create a logic for decoding of provided TomlNode

To boost the performance some users can parse Toml one time and after that decode it to their class.
In this case they need to deserialize only one class

This logic was called a Partial Decoding and was supported in https://github.com/akuleshov7/ktoml/commit/2f20e5f83a10dcdef0262dd30756becf91d4d844


[Feature Request] An option to remember opened hover edit windows after closing

An option to remember opened hover edit windows after closing

+1，There was this before, I don't know why it seems to have been canceled later,


iptables: always do SNAT for access from other nodes to nodeport with external traffic policy set to Local

… external traffic policy set to Local

[x] Make sure you have followed Kube-OVN Code Style.

What type of this PR

Bug fixes

Which issue(s) this PR fixes:
Fixes #(issue-number)
WHAT

🤖 Generated by Copilot at 323e198
Add ipset and iptables rule for gateway mode routing and masquerading. This enhances the cross-node traffic handling for pods accessing services or external IPs.

🤖 Generated by Copilot at 323e198

To route packets across nodes with ease
We added a new ipset and iptables
This improves the gateway mode
And reduces the load
Of pods reaching services or external IPs

HOW

🤖 Generated by Copilot at 323e198

Add a new variable nodeMatchSet to store the name of the ipset for other nodes' IPs (link)
Add a new iptables rule to mark packets from nodeMatchSet to ipset for masquerading by ovn-kube-gw0 interface (link)

We need a e2e for this case


nixos/systemd/nspawn: Add missing nspawn unit options

A few options have been added to the systemd.nspawn unit type are missing from systemd.nspawn.*.*Config. See systemd.nspawn(5).
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/839


Question: Is there a way to extract info from .db file?

I was interested in extracting information from an existing .db file using pyansys, such as node position or the node/element numbers of a given component. Is there a way to do parse this directly from the .db file using pyansys, similar to the way you can parse the frequencies from the .rst file with
result=pyansys.read_binary(path)
freqs = result.time_values
Or would the best way to do something like this be to use
ansys = pyansys.Mapdl(run_location=path)
ansys.nlist(arguments)
ansys.cmlist(arguments)
I would rather parse the data from the .db file directly, since that would save the time of invoking ansys. Is there a method to do this?

The binary format of the *.db file is different from the *.rst file, and ANSYS doesn't publish the headers of the database file like they do with the result files.  I'll ask around and see if they're fine with exposting that sort of functionality.
It actually won't be too long until there's a better interface that allows for more direct extraction of data via MAPDL directly to Python.  With luck it will be released by 2020R1/2020R2.  For now, I'll look into the feasibility of a database reader.

Ok, please let me know if you are able to figure out the .db headers, I think it would be very beneficial to be able to parse the .db information into python without having to use an APDL macro.
Thanks!

Probably won't support this since ANSYS doesn't plan on directly parsing/reading database files.  I'm limited by what's placed in the header files in the unified install (i.e. public interfaces).


TypeId limit

Hi, I try to use this library for my project but I see that there is a limit about typeId for registered adapter. Please can you explain me if now I start to use this lib why there is this limit?
If in the future I need to define more than 224 typeId, how can I bypass this problem?
My best regards.

I have a project with more than 1,000 different "tables" and we're using SQLite... We have made some tests with Hive and it looks very good! But with this typeId limit, we can go any further! Guys... it is 2021!! We got memory, we got processing power, we got devices with so much "room".... but some ppl insist in living in a world of 8 bit limits! You can NEVER (I mean "EVER") impose a limit of at least 65536 of something like this! It is so frustrating! Wake up!

What do you do into an app with more than 1000 tables???
Are you sure that you need all of these?

This is the only reason why I didn't choose Hive for my project

I'm still not entirely convinced to increase the limit. I have never seen an app that came even close to the limit.

Please consider increasing the limit at least now. I love how simple Hive is to use but the limit of 256 TypeIds is very much a disadvantage for my app since i have a lot of nested objects and the 256 Ids limit will be of no use. Please consider changing it

Can anyone help me on how i can overcome the TypeId limit?
It seems i cannot access HiveImple for creating multiple instances so that workaround is not working for me!!!


Gatsby Develop > ERROR #98123  WEBPACK

Bug report

What is the current behavior?
I am getting two WEBPACK ERROR #98123 when I am building a Gatsby site.
 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer

File: .cache/app.js

 ERROR #98123  WEBPACK

Generating development JavaScript bundle failed

You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer

File: .cache/polyfill-entry.js

failed Building development bundle - 3.044s
ERROR in ./.cache/app.js
Module build failed (from ./node_modules/@pmmmwh/react-refresh-webpack-plugin/loader/index.js):
Error: You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer
    at readWasm (/Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/read-wasm.js:8:13)
    at wasm (/Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/wasm.js:25:16)
    at /Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/source-map-consumer.js:264:14
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object._loader (/Users/benjamins/Sites/whatsgatsby/node_modules/@pmmmwh/react-refresh-webpack-plugin/loader/index.js:81:9)

ERROR in ./.cache/polyfill-entry.js
Module build failed (from ./node_modules/@pmmmwh/react-refresh-webpack-plugin/loader/index.js):
Error: You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer
    at readWasm (/Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/read-wasm.js:8:13)
    at wasm (/Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/wasm.js:25:16)
    at /Users/benjamins/Sites/whatsgatsby/node_modules/source-map/lib/source-map-consumer.js:264:14
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object._loader (/Users/benjamins/Sites/whatsgatsby/node_modules/@pmmmwh/react-refresh-webpack-plugin/loader/index.js:81:9)

develop compiled with 2 errors

If the current behavior is a bug, please provide the steps to reproduce.

Run gatsby develop from the terminal
Get Webpack errors

What is the expected behavior?
I'd expect it to build without failing.

Other relevant information:
webpack: 5.72.0
System:
OS: macOS 12.2.1
CPU: (8) arm64 Apple M1
Shell: 5.8 - /bin/zsh
Binaries:
Node: 18.0.0 - /opt/homebrew/bin/node
npm: 8.9.0 - /opt/homebrew/bin/npm
Languages:
Python: 2.7.18 - /usr/bin/python
Browsers:
Chrome: 101.0.4951.54
Safari: 15.3
npmPackages:
gatsby: ^4.13.1 => 4.13.1
gatsby-plugin-gatsby-cloud: ^4.13.0 => 4.13.0
gatsby-plugin-image: ^2.13.0 => 2.13.0
gatsby-plugin-manifest: ^4.13.0 => 4.13.0
gatsby-plugin-offline: ^5.13.0 => 5.13.0
gatsby-plugin-react-helmet: ^5.13.0 => 5.13.0
gatsby-plugin-sharp: ^4.13.0 => 4.13.0
gatsby-source-filesystem: ^4.13.0 => 4.13.0
gatsby-transformer-sharp: ^4.13.0 => 4.13.0
npmGlobalPackages:
gatsby-cli: 4.13.0

Please open an issue in gatsby, thanks


Patch interface tracking issue

Ping @whilei @sudachen who might be interested in this issue.
The patch interface, basically, is to use generic types (in Rust, it's trait, and in Go, I think interface is a similar concept) for representing different rules across hard forks. Here I will use the ECIP1017 as an example to explain the design difference between sputnikvm/etcommon and geth/parity.
The geth one implements ECIP1017 as a parameter, so we have something like this:
In post-processing of a block {
  // Apply block rewards
  Do something;
  If (ECIP1017 is enabled) {
    Do something else;
  }
}

This has the advantage that those parameters can be easily represented as a json file. However, it adds code complexity and consider if another ECIP9999 is built on top of ECIP1017, we would have another nested if statement, so forth and so on. It also makes it so that if geth is used as a library, it is not possible to extend it with ECIP9999 without changing code in the library.
The sputnikvm/etcommon way is to get this into a generic type:
In post-processing of a block < based on a generic type > {
  // Apply block rewards
  Do something;
  Do something else based on the generic type (which the implementation is in the generic type);
}

So with ETC we call In post-processing of a block < ECIP1017 > and for ETH we call In post-processing of a block < Frontier >.
This has the advantage that it is easily extensible if used as a library. I can add any new block reward rules by implementing this generic type. However, it suffers the problem that those Patch will not be able to easily represented as a JSON file -- the main rules must be specified in Rust code.
The implementation detail is that there will be several patches, one for VM, one for transaction signing, one for block rewards, etc. Those patches will then be joined together by an overall patch using Rust's associate types. They will then be used in a block Processor whose rules is based on the patches. A Client struct, after given a block number, will return (using Rust's trait dynamic dispatch) the corresponding Processor under the current hard fork. You can see this makes it a little bit easier to implement dynamic hard fork numbers.

Thanks for the explanation! I do like the interface pattern in the code, and think it definitely warrants at least some experimental refactoring in geth to adopt it too.
Shifting complexity from code to configuration, ie from (simpler JSON/configuration + more complex code) -> (more complex JSON/configuration + simpler code), seems to me to be a significant issue. How to make a generic interface/trait configurable and extensible, particularly given that future required fork functionalities will be varied and are unpredictable (like block reward calculation vs. required hashes vs. gastables, etc.)? Hmm.
I will keep thinking about it.

I realizeI should first ask What do you imagine (or already know?) the JSON config (if indeed it is JSON) would look like for the "generic-able" pattern?

Oops

@whilei I don't imagine it will be JSON config. JSON config might always have trouble to be generic enough. For one thing, Parity was never able to support Ubiq due to its slightly modified difficulty algorithm. We might also have chains that want to change the reduction rate of ECIP1017, which the current config will also not support. We also see that Parity usually have some minor problems on a non-foundation chain, like its UI price indicator, among other things. So as I see it, (which might actually be a good feature) JSON config cannot support chains that the developer does not foresee.
Instead the sputnikvm/etcommon way might look like this -- You have small basic building components like the VM, Block, Transaction, etc. Each of the components supports a number of Patch that allows it to be of customization. The joining components (like Client, Processor, etc) also have similar joined Patch structures. So for chains that is closely similar to Ethereum, it will only need to create a new patch. The difference here is that now "patches" have the ability to run code. This makes it so that it can support chains like Ubiq without knowing it in the first place. If a chain is not similar to Ethereum, it can selectively use any of the structs/traits it wants and then rewrite Client for its own chain.
So in this way, chains, instead of needing to fork parity/geth to modify JSON spec for an "official" support of its own, will mark sputnikvm/etcommon/etclient as a dependency, and build a small wrapper executable on top of it. From there it can build its own UI and other components without worrying about any other chains.

The new patch interface finally propagates to the client level. If you're interested in helping out the design or want to know how it works, have a look at https://github.com/sorpaas/etclient/blob/master/src/patch.rs and https://github.com/sorpaas/etclient/blob/master/src/validator/mod.rs#L114


failed to save bookmark: constraint failed: UNIQUE constraint failed: bookmark.url

After a first bookmark save, all subsequent ones fail because the update query does not include an identifier and the update is done on all rows.
Introduced by 05fee53bd0b7e81b5e74c4ae9efcbe213b563744

Fix f2643cc3ffbec7f6500f7e75dcca0e99f75f792d


[Bug] betterdiscord installer keeps crashing

Before Reporting

[X] I found no existing issues matching my bug
[X] My issue is not caused by a plugin or theme

Describe the Bug
everytime i have tried to open the betterdiscord installer it instantly crashes after a few seconds. it suddenly happened a few months ago and it wasn't really a problem until the new update where i just can't update now at all. i've tried running the installer on several virtual machines and it works just fine but on my main computer it just doesn't work at all. any way to fix this?
Expected Behavior
betterdiscord installer works and installs to 1.9.4
Steps To Reproduce

run betterdiscord installer
try to update via the updater on the betterdiscord menu on discord

Operating System
Windows
Discord Version
Stable
BetterDiscord Version
1.9.3
Anything else?
No response

Me too today, right now in czech republic.  Last few hours with no problems.  But 1.9.4 version


configure bundle-size github action to track install size of a minimal nuxt project

Would be nice if we could see a report of bundle size of a new Nuxt install for PRs. It doesn't need to be a pass/fail but info is good enough.
https://github.com/nuxt/nuxt/issues/23380

so basically measuring the size of the '.output/' directory?

We already have a test/snapshot for that.
I'm thinking of simply the installed node_modules size of a new Nuxt project.

Hey,
I created a very simple GitHub Action in my repo that:

installs pnpm and all dependencies (I'll take a look on pnpm caching afterwards)
comments the disk usage of node_modules in every PR.

An example is here.

I am not very fond of the nuxt repository and therefore not sure which node_modules directory should be checked.
I'll create a PR as soon as I found out 👀


Server crash

This happens on 1.10.2 when you do peripheral.playNote(15,20)
http://hastebin.com/cabevugaru.md

I'll look at it tomorrow. I found this when testing earlier but it didn't
seem to cause a crash. I thought I fixed it, but maybe not.
On Sunday, November 13, 2016, inklit<EMAIL_ADDRESS>wrote:

This happens on 1.10.2 when you do peripheral.playNote(15,20)
http://hastebin.com/cabevugaru.md
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/justync7/MinimalPeripherals/issues/1, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACKIyiHoMffC8K3xqY6abrt8AFwd7LUEks5q99-xgaJpZM4Kw8A0
.

It takes a ton of server ticktime, not an immediate crash but the server watchdog kills the server while it's frozen.

Ah. Although, you're using playNote incorrectly anyways so if you use it in
the correct range for the instrument it will work fine. ;P
On Sunday, November 13, 2016, inklit<EMAIL_ADDRESS>wrote:

It takes a ton of server ticktime, not an immediate crash but the server
watchdog kills the server while it's frozen.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/justync7/MinimalPeripherals/issues/1#issuecomment-260245071,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACKIyjunfbf3BSXfd9pvgWqcMzkGEPgPks5q9-BggaJpZM4Kw8A0
.

Didn't seem to work correctly. Playnote didn't play noteblock sounds. which is why I decided to try something out of the instrument range.

Fixed in a7b89c1bfd1f0adf72c8d6258b9192f004a7cf65


azure-sdk-bom Release Fails on Version Check

I attempted to release the azure-sdk-bom using our unified pipelines and it failed on validating versions.

Here's an example of the failing pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=432922&view=logs&j=adf1d365-c641-58b5-a58e-90f029aca966&t=88386d81-ae0f-5985-8936-932e8d36617e


Add client support for dates and the wait command.

Closes #4 but needs server modification to be fully functional. This is retro-compatible with the current server implementation, but is ready to receive a date parameter for file listings.

Incompatible with #23 don't merge both at the same time.


[How-to guide]: Configure proxy to watch your own API

In v0.3 release we introduced the ability to use the proxy with any API, we need to provide a guide to explain how you can inspect traffic from your own custom API.

This can be closed, we provide this as part of the getting started tutorial.
https://github.com/microsoftgraph/msgraph-developer-proxy/wiki/Using-the-proxy-for-the-first-time#4-intercept-requests-to-any-api

Done recently


Better way to set default headers in server middleware

This issue pertains to the following package(s):

[ ] GraphQL Playground - Electron App
[ ] GraphQL Playground HTML
[ ] GraphQL Playground
[x] GraphQL Playground Express Middleware
[x] GraphQL Playground Hapi Middleware
[x] GraphQL Playground Koa Middleware
[x] GraphQL Playground Lambda Middleware

To save time in development, I made a wrapper middleware so that when I navigate to /graphql?username=jimbob in dev mode, it calls the GraphQL Playground Middleware with the authorization header for jimbob (i.e. {tabs: [{headers: {authorization: `Bearer ${generateToken(jimbob)}`}}]}).
What's annoying though is that this blows away the previous tabs any time I reload the page.  I really wish I could just pass {defaultHeaders: {...}} and these would get applied to any new tab I open.
Another nice option would be a magic field name in a query that would set headers on the current tab when GraphQL Playground receives the result:
query {
  _setGraphQLPlaygroundHeaders: getHeaders(username: "jimbob") {
    authorization
  }
}

Or is there a better way to do this?

Does that put it in the headers tab of the playground or just add it without any indication to the playground user?

@jedwards1211 Its add it to playground headers.

@Huvik Any ideas how to pass the header to a Playground instance managed by ApolloServer and expressjs based on the request object?
new ApolloServer({
        context: async ({req, res}) => {
            return {...};
        },
        introspection: true,
        playground: {
           tabs: [
                {
                      // Is it possible to define a default header based on the value of the req object?
                }
            ]
        },
        tracing: true,
        typeDefs: NoticeableApiTypes,
        resolvers: NoticeableApiResolvers
    });

Looking back at this, I'm confused what rendering a <MiddlewareApp> React component has to do with graphql-playground-middleware-express.  Is there a way to configure the headers in graphql-playground-middleware-express?


How do I can change stream's resolution in real time?

This my config:
module.exports = {
  logType: 3,
  rtmp: {
    port: 1935,
    chunk_size: 60000,
    gop_cache: false,
    ping: 30,
    ping_timeout: 60,
  },
  http: {
    port: 8000,
    allow_origin: '*',
    mediaroot: '/DIRECT/PATH/rmtp-server/media'
  },
  trans: {
    ffmpeg: /DIRECT/PATH/rmtp-server/ffmpeg',
    tasks: [
      {
        app: 'live',
        ac: 'aac',
        vc: 'libx264',
        hls: true,
        hlsFlags: '[hls_time=2:hls_list_size=3:hls_flags=delete_segments]',
        dash: true,
        dashFlags: '[f=dash:window_size=3:extra_window_size=5]'
      }
    ]
  }
}

This is my client implementation. I'm using his.js
<div>
    <video id="video" muted="muted" autoplay></video>
</div>

import Hls from 'hls.js'

const video = document.getElementById('video') as HTMLVideoElement
const videoSrc = 'http://localhost:8000/live/qqq/index.m3u8'

if (Hls.isSupported()) {
    const hls = new Hls()
    hls.loadSource(videoSrc)
    hls.attachMedia(video)
    hls.startLoad()
}

How do I can implement stream resolution changing? What I need to do on the client and on the server sides to get it done? Thanks in advance.

I checked the documentation carefully and found this. That's the key :)


glTF features beyond PBR

Are there any plans or intentions to extend the support of other glTF features?
This mainly refers to skinning, which will influence the shaders - although fortunately, it should be possible to clearly separate this, meaning that it should only influence the vertex shader and not the fragment shader. (The fact that the vertex shader will depend on the number of joints would make it a bit tricky, though...)
(To a lesser extent, it could refer to other features, like animations or morph targets etc.)
If there are no such plans, this issue can probably be closed immediately, but maybe the goals and scope of the implementation (regarding these features) could then be pointed out in the README.

I'm not sure.  I'd like to see this repo get its basic handling of multiple textures and samplers under control before taking on more complex topics like skinning.  Certainly it would be nice to turn this into a complete working sample implementation of all of glTF, but there's a long way to go, and full support of all of our textured sample models should come before skinning and morphing.

OK, so this is basically about assigning priorities to features, with the focus currently being on the material/texture part itself. OK with that.
(Support for the upcoming https://github.com/UX3D-nopper/glTF/tree/master_lights_blinnphong/extensions/Khronos/KHR_lights would be nice, though...)


57 build stop

https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/57

Codecov Report

Merging #21 into master will increase coverage by 1.31%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             master       #21      +/-   ##
=============================================
+ Coverage     98.68%   100.00%   +1.31%
- Complexity       13        19       +6
=============================================
  Files             3         3
  Lines            76        85       +9
  Branches          5         5
=============================================
+ Hits             75        85      +10
+ Partials          1         0       -1

Impacted Files
Coverage Δ
Complexity Δ

...sion_tracker/sdk_java/VisualRegressionTracker.java
100.00% <100.00%> (+1.47%)
17.00 <11.00> (+6.00)

Continue to review full report at Codecov.

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


[git-info] Remove dependency on git-dir function

from the git module. Also now making all git calls with command.
Fixes #161 (again)

Also now making all git calls with command.

I had wondered if we had other instances of this laying around, I believe I even mentioned it in a thread somewhere where we first encountered the conflict. Ha! Glad to see it resolved! :+1:

LGTM


Direct access to all doc_ids

This is something I was expecting to be quite straightforward (or at least better documented in the API) but it doesn't seem to be.
Say I want to gather all doc_ids from a given corpus (for instance, if I want to use a random negative sampler on run time).
Currently, this is what I do:
data = ir_datasets.load("msmarco-document/train")
all_doc_ids = list(data.docs._handler.docs_store().lookup.idx())

which is fine, but, from what I can get, this triggers an iteration over all docs in the collection (and is also not very intuitive).
Is there a better way to achieve this?

The easiest way to load all doc_ids is:
data = ir_datasets.load("msmarco-document/train")
all_doc_ids = [d.doc_id for d in data.docs]

But, as you say, this iterates over all documents.
I think it would be straightforward enough to add a new API for iterating over just the document IDs, if you think it would be valuable. Maybe exposed as something like: data.docs.doc_ids.

But.... For your particular use case, I think you may not actually need the doc_ids themselves. You can just sample by index instead of by doc_id, eliminating the need for loading doc_ids at all. For instance, you could do:
num_docs = len(data.docs)
idx = random.randrange(num_docs)
data.docs[idx]

Lookups by index are fast (especially on SSD) and do not load corpus into memory, once a docstore is built (which it does automatically, and is needed anyway for lookups by doc_id).

Ok, this also works, iterating by the index of the document!
As for
all_doc_ids = [d.doc_id for d in data.docs]

versus
all_doc_ids = list(data.docs._handler.docs_store().lookup.idx())

The second one seems slightly faster (could be because I was trying the first one before, and I had a tqdm for loop encapsulating it that could be adding some bottleneck).
As for including the API, yes, that shouldn't be very hard. I can do it early next week, if that's ok.

Great, glad the lookups by index work for what you need!
I think the risk of doing:
all_doc_ids = list(data.docs._handler.docs_store().lookup.idx())

is that it's sorted (lexically) by docid, enabling lookups. So the indices will not necessarily align, which users may expect. Maybe this is alright, but we probably want to think a bit more of the design here before pushing this through.
Not all datasets use a lz4docstore (e.g., the ClueWebs) because we don't want to make a copy of huge corpora. So some consideration of these cases should be made.

That sounds awesome, @seanmacavaney. Thanks for letting me know!


algpseudocode comments break

Hi! Thanks for the great package. algpseudocode comments aren't working for me. The following breaks
\begin{algorithmic}
\State $i \gets 10$ \Comment{hi}
\end{algorithmic}

The log shows
Environment align* undefined. \State $i \gets 10$ \Comment{hi}

My current hacky fix involves making a local copy of algorithmicx.sty, and swapping the \( ... \) by $ ... $ in line 579
original
\algnewcommand\algorithmiccomment[1]{\hfill\(\triangleright\) ##1}%

modified
\algnewcommand\algorithmiccomment[1]{\hfill$\triangleright$ ##1}%

Not ideal obviously but at least lets me keep using shorTeX with algpseudocode.

Figured out how to do this from shortex.sty instead of in a local copy of algorithmicx.sty. Just add this line to shortex.sty
\algrenewcommand{\algorithmiccomment}[1]{\hfill$\triangleright$ #1}


Javascript SDK

Description:
Added the first fleshed out version of the Javascript SDK documentation
Test:
View documentation/SDKs/javascript/README.md

@AndyCross,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Looks very promising and reminds me that we need to review out exactly what we should expose in our APIs and what part of the API surface that is interesting for Client development. For the JavaScript SDK ,which would probably be more different than for Unity or iOS SDKs, things get somewhat different. Potentially the JavaScript SDK could/should be used from the server side, meaning it does make sense to have some APIs exposed that otherwise only would be considered "admin-APIs".
This is work in progress and not the final documentation, but I think it looks good so far. The documentation that has been done is more of a "reference documentation", rather than a documentation that tells people how to get started. I guess we need both before we are done.
I'll leave it to @stuartleeks to decide wether we should go ahead and merge this right away or not. For me, it looks like a step in the right direction and will help us collect all documentation for the different SDKs in one place and therefore conform them all in the end.

I've rebased and done some other minor changes to this PR. Thanks @AndyCross I'll merge this PR as soon as build servers confirm nothing else is broken. Hope we can get some more help from you and your team as we go further. Your work has been very appreciated.


Labels not respecting white space

Can this be fixed, am trying to get space between the images and the text and align F keys so it looks nice.
It also be nice if we could add some space between text lines.

    <Program
      label="  Browser          - F1"
      tooltip="Open Default Browser"
      icon="/usr/share/icons/Paper/48x48/apps/browser.png"
        >$JADE_BROWSER
    </Program>
    <Program
      label="  File Manager     - F2"
      tooltip="Browse Your Files"
      icon="/usr/share/icons/Paper/48x48/places/folder_color_pink.png"
        >$JADE_FILE_MANAGER
    </Program>
    <Program
      label="  Software Center  - F3"
      tooltip="Install/Remove Applications"
      icon="/usr/share/icons/Paper/48x48/apps/software-store.png"
        >$JADE_SOFTWARE_INSTALLER
    </Program>
    <Program
      label="  Manjaro Settings - F4"
      tooltip="Configure - Language/Kernel/Users/Time/Date/Keyboard/Hardware"
      icon="/usr/share/icons/Paper/48x48/categories/gnome-settings.png"
        >$JADE_SETTINGS
    </Program>
    <Program
      label="  Terminal         - F5"
      tooltip="Use The Command Line"
      icon="/usr/share/pixmaps/hyper.png"
        >$JADE_TERMINAL
    </Program>
    <Program
      label="  Desktop          - F10"
      tooltip="Launch Desktop Environment"
      icon="/usr/share/pixmaps/jade-logo.svg"
        >jade-desktop
    </Program>
  </RootMenu>```

This is similar to issue #365.  As far as adding space between lines is concerned, I wonder if something like the ability to use the "separator" component with an invisible line would work?

Hi Joe
An invisible separator might work, depending how wide it is or if we can define the heigh, if we could define the height of the line or even a margin bottom in pixels would be better, as the space between lines depends of the font used.

Is this happening even with fixed width fonts?

I could add space to the images, but that would require to edit icon themes, or make separate images.
periods or underscores will kill a UI design to be honest.
I ended up going with this just because it looks a bit better.

There is nothing wrong with this it works, but when you look at it closer, people read from left to right top to bottom, the main focus should be the words first then the keys and icons last, unfortunately i cant do that so this will have to do .for now

How about align="left|right|center"?  I would still put the shortcut info in the tooltip or leave them off and have a separate submenu called "Keyboard Shortcuts" that does your latest version.  The benefit of this is that  it can be "dynamic" in new versions of jwm so it can sync with your keyboard shortcut config tool and integrated into a help menu (which BTW should be the F1 shortcut by convention)

I din'd think about the tooltip for the shortcuts that's a good idea :+1:


Min image size?

Trying with several different sized images, found the following error in some of them:
Padding size should be less than the corresponding input dimension, but got: padding (2, 2) at dimension 2 of input [1, 512, 2, 42]
Can you please elaborate in the minimum image size?
Thank you

[(1333, 800), (1333, 900), (1333, 1000), (1333, 1100)]

Thanks!


Remove appveyor

From now on, the msvc binaries will be produced by the deploy script and the respective tests are run by the GitHub Actions, so the appveyor.yml is no more necessary.
This PR closes #1209 and #2115
Thanks in advance for your review! :)

Coverage remained the same at 80.713% when pulling a2aa06a5f83f35acfddab98a1fd9b8bdff5b16e5 on Luni-4:remove-appveyor into af7f474fb89f4495b94cc197f7eb0f510e8ed7bf on xiph:master.

I also deleted the webhook in repo settings so we'll no longer get that red X.

This is just a small thing, but probably it's best to also remove the appveyor-shield in the headline of the README.md.

Thanks @shssoichiro! :)
I agree with you @Urhengulas


Remove assume false on inline 0

#933

Can you add a test-case to this PR?

Maybe you can do it? I don't have development environment set up

I don't think we want to land this PR. See my comment on the associated issue.

Maybe this pull request can actually change the options into: Inlining.AssertFalse, Inlining.Requires, Inlining.Spec? All three would be consistent. See #933. What do you think, @shazqadeer?

@petemud : Let us back up a bit. Are you actually blocked on anything here? Specifically, is there a Boogie inline option that you can already use to get your job done?

@shazqadeer I'm not blocked on /inline options. I can just not use {:inline}, or use /inline:spec. It'd just be nice for a verification backend to be sound

Glad to know you are not blocked.
In principle I agree with your comments about soundness. Note though that Boogie is less a fixed verification backend and more verification backend infrastructure. It is typically used by many different tools to achieve custom combinations of "soundness" and "scalability". Mostly, we want Boogie to be predictable and not do surprising things.
For the specific question of what do do with the inline attribute, I find that Boogie documentation is accurate and there are several options available to the user to achieve what they want. It is possible though:

the default option is not well chosen and should perhaps have been been InlineAssert or InlineSpec
another option, in addition to the ones currently provided, is needed

I am happy to hear suggestions/PRs along these lines.
In the meantime, I will focus my attention on the other issue of irreducible graphs because it sounds like you are actually blocked on it.


highway=track

It would be nice if
highway=track
can have
foot=yes and horse=yes by default

Thank you. You are true. I see now access=yes in the default values (visible as grey) in the editor.
I think it was somewhen in the history when this was not visible for me and there was "unknown" for the accesibility (I'm not sure  about the english description texts, because I use ID in czech version).


Need directions

This page has no examples or directions on how to use this in the app.

https://github.com/gordol/cordova-brother-label-printer#usage

pointing to your own project that  has almost no documentation on how to use it is not proof of having documentation. Give us some test samples.

It is pretty well documented, if I say so myself. What more do you want?
There are only 3 methods.
findNetworkPrinters()
printViaSDK()
sendUSBConfig()
findNetworkPrinters must be called before printViaSDK. It takes no parameters and returns two parameters, one is a boolean (whether a printer was found or not), and the other is a list of found printers. To print, all that's needed are the IP and MAC of the target printer.
Currently, the last printer that is found will be the one targetted due to the way we're looping over the netPrinters array. This plugin could be extended to allow the user to select which printer they want to connect with... If this is desired, let me know, and I'll address when I get a chance, or better yet, send a pull request. The best way would either be to pass the printer IP/MAC to the printViaSDK method, or perhaps you could just pass an index to select the desired printer from the netPrinters list.
printViaSDK takes one parameter, which is a base64 encoded bitmap image. The result should be a status code that is passed directly from the SDK. The status codes are documnted in the Brother SDK Appendix in section <IP_ADDRESS>.Error Code. If everything works, the response should be "ERROR_NONE".
sendUSBConfig calls the Brother SDK's printFile method. The expected input is a string containing raw print commands, which is written to a temporary file in the app cache directory, and is then sent to the printFile method and deleted afterwards. You will need a device that supports USB-OTG and a USB-OTG cable. On first run the app will request USB permissions, and it should be saved after that for subsequent prints. As-is, this method is used to send raw commands in PCL (Printer Control Language) to the printer... For example, to configure the network settings of the printer, etc... You will need to reach out to Brother for documentation of the PCL commands. You can probably find them by searching for "Brother Printer Command Reference" and appending your model number. This method could be extended easily to accept other types of file input, so you could, for example, print JPG images, etc...
Seriously, this explanation is considerably longer and more complex than the code, by a large factor.
https://github.com/gordol/cordova-brother-label-printer/blob/master/www/printer.js
Just read the code.

I love reading directions by programmers.

better get used to it haha


Error at 'Define the Entity'

[Enter feedback here]
Running into this error, when pasting this code into SamplesUtils.cs

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

ID: ef1295f9-eab5-8918-ab99-3a20b8723805
Version Independent ID: 0e551ce1-761a-d379-7b6c-4caf49c5bbb2
Content: Azure Cosmos DB Table API using .NET Standard SDK
Content Source: articles/cosmos-db/tutorial-develop-table-dotnet.md
Service: cosmos-db
Sub-service: cosmosdb-table
GitHub Login: @wmengmsft
Microsoft Alias: wmeng

@aditya815 We are assigning this to doc author for further insight.
@wmengmsft @SnehaGunda Can you please check this and help the user.

@aditya815 Please add the below using statements to your namespace
    using System.Threading.Tasks;
    using Microsoft.Azure.Cosmos.Table;
    using Model;

Code for the complete sample is here if you want to clone and run it.
Do let us know if you face any issues.

@aditya815 We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Menubar

I set it to auto-open the menubar window when the app is ready, but we could also set it to NOT open, so that the window only shows when they click the icon. Up to y'all.

Also, closes #6


Pagination is broken in 1.1.16 since 02/12/2016

Hey the pagination doesn't work anymore with your latest 1.1.16 version since you pushed your latest commits, I had to rolleback my prod app to 1.1.15 to have it working. Can you please fix this and be careful when updating the master version.

Same bug here... :-1:

@Scipionh works here: http://valor-software.com/ng2-bootstrap/#/pagination
so provide more details please

Here is the error I had this morning, without changing anything else in my code:
 Template parse errors:
More than one component matched on this element.
Make sure that only one component's selector can match a given element.
Conflicting components: PagerComponent,PaginationComponent

The error doesn't happen when I did revert to 1.1.15 and didn't happen either yesterday with the 1.1.16 version

can you show me a component?

<pagination class="valign-middle" [totalItems]="totalNumberOfItems" [itemsPerPage]="itemsPerPage" [(ngModel)]="page" (pageChanged)="page=$event.page; refreshPaginationQueryParams();"
                            previousText="‹" nextText="›" firstText="«" lastText="»"></pagination>

<EMAIL_ADDRESS>But selectors are different, did you try clean install and clean build?

Yep, I did it several times

need plunker or something to reproduce
we are using v16 without such issues


Activity Group Update

The current Technology activity tags should fall under the following larger 4 categories:
Content: #blogpost,#video,#article,#tutorial,#forumpost,
#techdocs,#book,#translation,#opensourcecode
Speaking: #techtalk
Testing: #bugreport
Pack Leader: #interview, #community
Update the PG AT AG Master List with the required changes
#gdeProgram renamed to #expertsProgram

I am not entirely convinced that we need to use these 4 groups for the app,
front or back, these are more of an internal classification that is being
used by the program group.
The Activity Group was really a method of capturing meta data about the
activities, so we should really try to understand is that is procuring any
value at all to the program?
When I look at the way that the team works, and the reports that they are
really trying to extract, I see none of that data, perhaps because its non
existent for most posts.
Patrick Martinent
On 8 July 2015 at 00:42, Mauro Solcia<EMAIL_ADDRESS>wrote:

The current Technology activity tags should fall under the following
larger 4 categories:
Content: #blogpost,#video,#article,#tutorial,#forumpost,
#techdocs,#book,#translation,#opensourcecode
Speaking: #techtalk
Testing: #bugreport
Pack Leader: #interview, #community
Update the PG AT AG Master List with the required changes
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleDeveloperExperts/experts-app-backend/issues/11.

I understand your point.
I think that the main cause for metadata being missing on most activities, is due to the frontend making metadata input really slow.
Hopefully the new site should be more accessible/usable and faster to jump on the different activities.
I think we could ask in the next meeting if we want to keep tracking metadata in the current format or something different (less fields kind of more descriptive? and almost the same for all the AGs so that they can be aggregated in the reports?)

Discussed this point with Nat and Marie today in the Hangout; Activity Groups are fine as are currently implemented.
Closing the issue


Composer support for pull

It would be nice if composer install could be run if applicable. PR imminent.

Implemented in #44.


Improve test coverage

Improve test coverage

@lovepoem
Hello, I think I can write unit tests to participate in the community and be familiar with the source code. Can I do this task? Can you tell me about some specific modules that need to improve the unit test coverage?
你好，我认为编写单元测试不仅能参与社区而且还能熟悉源码，我可以做这项任务吗，可以说一些具体的模块需要提高单测覆盖率的吗


add_to_builtins in settings.py fails

Hi,
When using the django-uni-form templatetags through add_to_builtins in settings.py (the most logical location for using add_to_builtins) the server fails to start.
This is a new bug since after 0.7.0.
It is caused by the use of get_template in the templatetags modules. Since get_template is called at module load-time and get_template requires settings.py to have been fully loaded your code cannot be imported from settings.py.
An example of a call to get_template at module root (i.e. not inside some function) is:
https://github.com/pydanny/django-uni-form/blob/master/uni_form/templatetags/uni_form_tags.py#L142
But there are more, grepping will quickly reveal them.
A simple solution would be to make the associated variables lazily initialized, i.e. set them as None at module-load time and always access them via some getter that checks their value. If necessary I could provide this code for you.

Confirmed, you are right.
I have to say I didn't know of the existence of add_to_builtins, I wish I had before. Anyway I will do a good use of it, great tip.
get_template calls were done globally to sped up django-uni-form when not using template cache loader, If I recall correctly that happened in version 0.8.0.
django-uni-form is going to be replaced by django-crispy-forms https://github.com/maraujop/django-crispy-forms Although it hasn't been publicly announced yet.
I'm not updating fixes to django-uni-form anymore. Could you please have a look at it, maybe upgrade to it (instructions), latest version is 1.0.0 (tests are passing) and submit the pull request there. I won't have time to fix this myself for a couple days.
Thanks, cheers
Miguel

@marujop, there is a reason why people don't use add_to_builtins more. It is a maintenance nightmare in the making. It is one of the warning signs when you review projects, if they have it, then odds are they are being 'clever' in other places.
"Explicit is better then implicit" is the way to go.

Wow, I see. I found this quote by Carl Meyer:

Note that while you can do this, it's quite likely that you'll regret it at some point (I've done it, and regretted it). It makes your templates non-portable to any other project which doesn't add_to_builtins, and it can break tests which render those templates (unless you make sure the test runner also runs add_to_builtins). All in all, it makes things more brittle for a very small gain in convenience.

It looked like a good idea, to have the tags loaded everywhere in the project. Not meaning django-crispy-forms but the project that uses it. That avoid having to repeat loads everywhere, right?

It's also a performance thing.
'Repeat' loads are a good thing, since all you are doing is adding them into templates manually. Which means those pages that don't use a particular template library aren't being throttled by Django's notoriously slow templatetag library finder (which checks every INSTALLED_APP plus the Django defaults).
Defining them in add_to_builtins means every request loads all the templatetags. Then you'll complain that Django is slow and look to node.js to increase your performance. All for the wrong reasons. :D
Ouch.

You are right, this looks as a performance eater...
I'm convinced not to use it :D I don't want to end up coding node.js no, no, no.


Add Gatekeeper (Source Allowlist) example to docs

Changes
Adds an example Gatekeeper ConstraintTemplate (ShipwrightAllowlist) and Constraint to the docs (and an install script in hack/) to show how one could apply an allowlist to source.urls in the Builds.
The motivation for this is organizations who might only want to build source code from trusted sources, such as their own git servers or specific trusted organizations.
Submitter Checklist

[ ] Includes tests if functionality changed/was added
[X] Includes docs if changes are user-facing
[ ] Set a kind label on this PR
[X] Release notes block has been filled in, or marked NONE

Release Notes
NONE

Thank you, Blair!

Thank you Blair, for your Gatekeeper example!
I don't want to speak for everyone - my initial reaction is that this would be great content for the Shipwright blog.
Gatekeeper is a popular choice for admins to secure their clusters through admission control.
However, it is not the only solution available today, with more likely to come in the future.
In many regards I'd like Shipwright to be neutral when it comes to admission-based security.
I think the gatekeeper markdown doc you provided can be converted directly to a blog post.
Content merged in shipwright-io/website/content/en/blog/posts is automatically published to the website.
All it needs is a little bit of front matter to make Hugo happy.
If you a submit a pull request to shipwright-io/website, I can help you with that.
@shipwright-io/build-reviewers thoughts here?

@adambkaplan PR submitted! https://github.com/shipwright-io/website/pull/49

Finally catching up on things since being away from the office.
Let me echo the thanks from @sbose78 and @adambkaplan @blairdrummond
Quick background:  I am a maintainer in Shipwright as well and teammates with @sbose78 @adambkaplan here at RH.  Among other things, I have had involvement with upstream Tekton as well, and that has included looking at third party policy engines like gatekeeper, kyverno, etc. for policy enforcement in Tekton.  That work currently culminated in the following tekton ehnancement proposal:  https://github.com/tektoncd/community/blob/main/teps/0035-document-tekton-position-around-policy-authentication-authorization.md
Among other things, it calls for documentation for now, and policy engine neutrality, as has already been echoed here.
We were looking at taking the action called out in that TEP and applying it here to Shipwright.  Fortunately for us, you have an interest in this space, and have taken care of starting things off for us :-)
My quick scan of your sample here make sense, seems in line, with some of the things we were considering.  As an FYI, we were also considering items like specific parameters settings that might be set on build strategies, as there are options with the specific image build  tools that require escalated privileges, as I imagine you are already aware.  I remember @SaschaSchwarze0 and I discussing one such item in one of his EPs / PRs, but as my brain is still trying to awake after being away from the office, I'm not finding that ref as I type.
In any event, I suspect we could build off the PR, once it merges, you submitted to the website repo, and go from there.
I'll take a peek at that shortly.
Thanks again.

I remember @SaschaSchwarze0 and I discussing one such item in one of his EPs / PRs, but as my brain is still trying to awake after being away from the office, I'm not finding that ref as I type.

@gabemontero we discussed policy management in the context of build strategy annotation propagation. See https://github.com/shipwright-io/community/blob/main/ships/0010-buildstrategy-annotation-propagation.md#risks-and-mitigations

Blog post is now live at https://shipwright.io/blog/2021/08/02/gatekeeper-policies-with-shipwright/
Should we close this PR, then?

@gabemontero  I think my content here is a little out-of-sync as I only incorporate the PR feedback on the website PR, but if you guys are still interested in this PR I can tidy it up.

Having it in both places might be OK IMO @adambkaplan
Perhaps a discussion point for the next community meeting ?

My vote would be blog post only, but certainly a point we can discuss as community.


Doesn't build on Windows

Tries on two different set ups.
This one with Msys2, CMake 3.28.1, Python 3.8 (installed via Windows installer)
Using library: codal-microbit-nrf5sdk
-- Configuring done (1.0s)
-- Generating done (1.0s)
-- Build files have been written to: /c/workspace/micropython-microbit-v2/src/build
git -C ../lib/codal checkout CMakeLists.txt
Updated 1 path from the index
git -C ../lib/codal checkout CMakeLists.txt
Updated 0 paths from the index
make -C codal_port
make[1]: Entering directory '/c/workspace/micropython-microbit-v2/src/codal_port'
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
(cd ../../lib/micropython && py py/makeversionhdr.py /c/workspace/micropython-microbit-v2/src/codal_port/build/genhdr/mpversion.h)
py make_microbit_version_hdr.py build/genhdr/microbitversion.h
GEN build/genhdr/qstr.i.last
Traceback (most recent call last):
  File "../../lib/micropython/py/makeqstrdefs.py", line 213, in <module>
    preprocess()
  File "../../lib/micropython/py/makeqstrdefs.py", line 83, in preprocess
    for output in p.imap(pp(flags), chunks):
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 86
8, in next
    raise value
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\multiprocessing\pool.py", line 12
5, in worker
    result = (True, func(*args, **kwds))
  File "../../lib/micropython/py/makeqstrdefs.py", line 65, in run
    return subprocess.check_output(args.pp + flags + files)
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\subprocess.py", line 415, in chec
k_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\subprocess.py", line 493, in run
    with Popen(*popenargs, **kwargs) as process:
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\subprocess.py", line 858, in __in
it__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "C:\Users\IEUser\AppData\Local\Programs\Python\Python38\lib\subprocess.py", line 1311, in _ex
ecute_child
    hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
make[1]: *** [../../lib/micropython/py/mkrules.mk:122: build/genhdr/qstr.i.last] Error 1
make[1]: *** Deleting file 'build/genhdr/qstr.i.last'
make[1]: Leaving directory '/c/workspace/micropython-microbit-v2/src/codal_port'
make: *** [Makefile:44: libmicropython] Error 2

Cygwin with CMake 3.14.3, Python 3.8 (installed via Windows installer):
Using library: codal-microbit-nrf5sdk
-- Configuring done
-- Generating done
-- Build files have been written to: C:/workspace/micropython-microbit-v2/src/build
git -C ../lib/codal checkout CMakeLists.txt
Updated 1 path from the index
git -C ../lib/codal checkout CMakeLists.txt
Updated 0 paths from the index
make -C codal_port
make[1]: Entering directory '/cygdrive/c/workspace/micropython-microbit-v2/src/codal_port'
py ../../lib/micropython/py/makeversionhdr.py build/genhdr/mpversion.h
GEN build/genhdr/mpversion.h
(cd ../../lib/micropython && py py/makeversionhdr.py /cygdrive/c/workspace/micropython-microbit-v2/src/codal_port/build/genhdr/mpversion.h)
GEN /cygdrive/c/workspace/micropython-microbit-v2/src/codal_port/build/genhdr/mpversion.h
Traceback (most recent call last):
  File "py/makeversionhdr.py", line 148, in <module>
    main()
  File "py/makeversionhdr.py", line 144, in main
    make_version_header(args.repo_path, args.dest[0])
  File "py/makeversionhdr.py", line 127, in make_version_header
    with open(filename, "w") as f:
FileNotFoundError: [Errno 2] No such file or directory: '/cygdrive/c/workspace/micropython-microbit-v2/src/codal_port/build/genhdr/mpversion.h'
make[1]: *** [Makefile:136: build/genhdr/microbitversion.h] Error 1
make[1]: Leaving directory '/cygdrive/c/workspace/micropython-microbit-v2/src/codal_port'
make: *** [Makefile:44: libmicropython] Error 2

On GitHub Actions:
https://github.com/microbit-foundation/micropython-microbit-v2/actions/runs/8391892458/job/22983253141
Using library: codal-microbit-nrf5sdk
-- Configuring done (38.1s)
-- Generating done (0.1s)
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_BUILD_TYPE

-- Build files have been written to: D:/a/micropython-microbit-v2/micropython-microbit-v2/src/build
git -C ../lib/codal checkout CMakeLists.txt
Updated 1 path from the index
git -C ../lib/codal checkout CMakeLists.txt
Updated 0 paths from the index
C:/mingw64/bin/make -C codal_port
Makefile:140: *** target pattern contains no '%'.  Stop.
make[1]: Entering directory 'D:/a/micropython-microbit-v2/micropython-microbit-v2/src/codal_port'
make[1]: Leaving directory 'D:/a/micropython-microbit-v2/micropython-microbit-v2/src/codal_port'
make: *** [Makefile:44: libmicropython] Error 2

Okay, at least the Msys2 system does work when installing Python internally with Pacman instead of using the Windows system Python. So it's more an issue about with using system Python inside Msys2 (although maybe setting the subprocess shell argument to True would be worth trying).

For the first case:
FileNotFoundError: [WinError 2] The system cannot find the file specified

It's hard to tell exactly what it can't find, but it may be referring to the C preprocessor, named by the variable $(CPP) in the makefile.
In the second case (cygwin) it looks something to do with relative vs absolute paths and the destination build directory.


updateUnreadCount notification object is nil

Describe the bug

When using the code above, in xcode debugging
guard let unreadCount = notification.object as? Data else {                     return                 }
notification.object is always nil
To Reproduce
Steps to reproduce the behavior:

Perform the above snippet
Send or read Intercom message in ios
The notification event listener fires
See notification object is nil

Expected behavior
Update read count receives number
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: iPhone 12 pro
OS: iOS 16.5.1
Browser: Capacitor
Version [e.g. 22]

Additional context
Add any other context about the problem here.

thx for example )


[Feature] multi-nodes surpport

Motivation
70B models or more larger modes should be deployed by multi-nodes( A30/L40s ...).
Multi-nodes surpport will be appreciate.
Related resources
No response
Additional context
No response

Sorry, pipline parallelism has a very low priority in lmdeploy.
I will put this feature in our backlog.
Is it possible to use lmdeploy's tensor parallelism?


merge libcurl_vendor build instructions

I tested these changes on the galactic branch on ubuntu 18.04 and they worked fine.  I'm not able to test them on windows or apple. I'm not a fan of pushing in CMAKE_CXX_FLAGS like I am, but am not sure how to otherwise do it.

Thanks!  This is looking great to me now.  I'm going to run a couple more tests on it locally.  Assuming that is happy, I'll give this a run in CI.

CI:

Linux
Linux-aarch64
Windows
Windows Debug
RHEL

All CI seems happy with this, so going ahead and merging.  Thank you for the contribution.


[#180] Improved tests

Closes #180

Codecov Report

Merging #203 into master will decrease coverage by 0.31%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #203      +/-   ##
============================================
- Coverage     42.11%   41.79%   -0.32%
+ Complexity      172      171       -1
============================================
  Files           164      164
  Lines          1256     1256
  Branches         33       33
============================================
- Hits            529      525       -4
- Misses          724      729       +5
+ Partials          3        2       -1

Impacted Files
Coverage Δ
Complexity Δ

...ytebuddy/matchers/atomspec/AllMethodsAreFinal.java
100% <ø> (+14.28%)
4 <0> (+1)
:arrow_up:

...cobjects/oo/atom/tests/AssertAtomsAreNotEqual.java
0% <0%> (-100%)
0% <0%> (-2%)

Continue to review full report at Codecov.

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