Add HHVM >= 3.8.0 support in the artisan serve command

With the help of the Proxygen Web Server.
Now we can run Laravel development server with HHVM, like this:
hhvm artisan serve

Does comparing versions like that work?

@taylorotwell Yep: http://3v4l.org/FSQVX.

I think this feature can be easily backported for older versions of Laravel.

I think this feature can be easily backported for older versions of Laravel.

No need. We only intend to fix bugs on the 5.1 branch.

Don't we need to error if we're using a version of HHVM less than 3.8.0?

Since serve doesn't work at all.

@GrahamCampbell OK.
So for older versions of Laravel you can put this hhvm_serve file in the root of your application:
#!/bin/sh

hhvm -m server -v Server.Type=proxygen -v Server.SourceRoot="$(pwd)" -v Server.IP=localhost -v Server.Port=8000 -v Server.DefaultDocument=server.php -v Server.ErrorDocument404=server.php

Don't we need to error if we're using a version of HHVM less than 3.8.0?

Why not.

@GrahamCampbell Should I need to update this pull request to add a artisan error message?

Should I need to update this pull request to add a artisan error message?

Just throwing an exception would be fine tbh.

:sunglasses:


Fixes issue #234

Appends default.nix to path if it is a directory. Note that this requires a cache clear.

Fixed, sorry about that.


link instructions to enable managed identities on a VM

I would suggest to add a prerequisite. The VM must have system-assigned managed identity already setup. It was mentioned in the introduction, but didn't know how to do this on a VM. Then I have found this other link that describes how to enable "system-assigned management identity" on a VM: https://docs.microsoft.com/en-US/azure/role-based-access-control/role-assignments-portal.

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

ID: 0767c7b6-16b1-c687-6190-9c7eb2776826
Version Independent ID: d4f9ccd2-6673-31bc-f72b-cbf061b942d8
Content: Tutorial: Use managed identity to access Azure Resource Manager - Windows - Azure AD
Content Source: articles/active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-arm.md
Service: active-directory
Sub-service: msi
GitHub Login: @barclayn
Microsoft Alias: barclayn

@mpalmier74
Thanks for your feedback! We will investigate and update as appropriate.

Thank you! I made a pull request to add the reference and update the prerequisites. https://github.com/MicrosoftDocs/azure-docs-pr/pull/139553


peerDependencies are ignored while creating dependency graph

What version of Turborepo are you using?
1.4.0
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Mac
Describe the Bug
The peer dependencies are not considered part of the dependency graph. This issue has roots in #813 where they are ignored while creating the graph because of some dependency cycle issues mentioned in the PR.
Expected Behavior
Construct dependency graph including peer dependencies. Peer dependencies are one of the complementary tools which are used in monorepos, and simply ignoring them doesn't seem a good solution.
To Reproduce

Suppose the following monorepo structure:

/app
  /some-app
/packages
  /dependent-a
  /dependent-b
  /c

Suppose that dependent-a and dependent-b has c as  peer dependency, and some-app has all packages (dependent-a, dependent-b and c) as dependency.

Suppose turbo.json looks like this:

{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "build": {
      "dependsOn": ["^build"]
    }
  }
}

When you run turbo run build on some-app (using --filter=some-app), it triggers build for all of the packages concurrently, completely unable to build c first and clearly causing issues.

I think this is a common scenario for plugin based apps, as the plugins may include other plugins as peer dependency (and not a regular dependency).

Any solutions?

Would it make sense to always copy the peer dependencies to also be dev dependencies?  It seems like if you have the dependency it should at least be part of your test suite?

No. If peerDependencies were meant to be copied to devDependencies or dependencies, they were useless. They have their own use case. They are just peer dependencies.

peerDependencies that are mirrored in devDependencies are not useless.  If your code directly references the dependencies you will have to ensure they are installed during development in order to test your code.  You have to add them to devDependencies to do that, no?
If you are just passing through the peerDependencies of another package without using them in your own package you can skip adding them to devDependencies, that makes sense.
I suppose there might be some odd cases where you want to be able to import something by name but you don't have any automated tests that reference it, so you add it to peerDependencies but not devDependencies ?  What are the details of your use case here?

Still, no. 😄
I think you are missing the point of peer dependencies utterly.
If you want to test a package containing has some peer dependencies in isolation (without using it in the host package), you can do something like forcing your package manager to install peer dependencies for you somehow.
I haven't seen a real project which duplicates peer dependencies to dev dependencies. It may have some use cases in some special scenarios, but I don't know one.

React libraries with unit tests have to put react as a dev dependency for the tests, and a peer dependency for users of the library.

I think @dobesv is correct - std practice is to make peer dependencies also dev dependencies.

Confirmed, peerDeps mirrored in devDeps is common practice.

I'm still not getting the point. I have seen many (standard) monorepos whose packages don't copy their peer dependencies to dev dependencies. I think it's not correct to ignore them just because the mirroring is a common practice.
Check out react-dom, for example.

IIUC peer dependencies are intended to be provided by the environment / platform where the code is running. As such, turbo doesn't consider them to be dependencies that need to be built. The typical example is plugins, they expect whatever environment they are in to already have the package that they plug into, rather than depend on it directly.
If you don't want to mirror peer dependencies in dev dependencies, you can make the dependency explicit in turbo.json by adding my-peer-dep#build to dependsOn for your package that has a peer dependency on my-peer-dep.

I think it's not correct to ignore them

If they aren't marked as a dependency or dev dependency of that specific project, then they won't affect it's build or execution, so they are not a dependency of THAT package.  The project that provides the dependency would be the one that should rebuild if the package changes.

May I please ask what would happen if a 3rd party dependency (i.e:react), is a dev dependency under root/package.json of the monorepo but a peer dependency under /root/apps/example/package.json,
Would updating react to the latest version on the root, not trigger a new build since the child repo only uses react as a peer dependency rather than a dev dependency?
Under /root/apps/example/package.json, I would believe that semantically, if we don't want to keep versioning (hence, duplicating) dependencies, which are then managed by the root, it makes sense to add it in the format of
"peerDependencies": {
   "react": "*" // uses any version available: inherited by root (not-installed by default)
}

while the following would mean
"devDependencies": {
   "react": "*" // install latest version of react regardless what's declared on the root
}

Just to weigh in in this old ticket and to urge to reopen this:
Duplicating dependencies in both devDependencies and peerDependencies will lead to inconsistencies and user errors. Currently it's possible to install only from peerDependencies with pnpm with it's auto install peers configuration option.
Sure, there is additional tooling like Syncpack to try to address versioning inconsistencies but fixing the root cause would be preferable.

Are there any workarounds to get depdendsOn to work with peers?

is this documented?


Use Elm-CSS for styling

elm-css enables the styling of a component via union types in Elm, and guarantees compile time class name checks. An example with this working on the new 0.17 version will help consumers build their apps in a more explicit manner.

So, after looking more at elm-css, it seems a helper function producing an Html.Attribute is used to generate the appropriate attribute rather than a list of classes. Their class function allows the passing in of union types. All that needs to be done there is provide a configuration function for defining a custom html attribute on the sub views. This would be a minor update, so it's not necessary while elm-css is in self-described beta for 3.0

With #26, the configuration will take a List Html.Attribute for list items and the list. So, Elm-CSS will work fine

Already possible with new API


Install Guide

I'm getting an import error when I try to install and use this module.  Is there any chance you could provide a fuller install guide?

Could you post some code? How did you try to use it? What error did you get?

So I've:

downloaded the source.
run the following to build:
> npm install
> bundle install --path vendor/bundle
> npm run build:webpack

In my html I have:

But when I run:
Quill.register('modules/smart-breaker', SmartBreaker);
I get an error that SmartBreaker is not defined.
I realize I'm probably doing this all wrong ;-)

Could you post full code of html file you import the script and initialize quill?
Did you first load quill, then smart breaker, then initalize?


[*] MO : blockwishlist : Added rel="nofollow"

"my wishlists" are not for crowlers ;)

Hi,
Thank you for your contribution.
Best regards


How to use root median squared error as objective function?

Hi!! Sorry if this is not the place for this comment but I couldn't use the google group. I'll like to know how to define a customized objective function for a regression problem in R. I'm interested in using root median squared error, instead of RMSE, or some other meassures using percentiles. I tried defining objective function using numerical derivatives through numDeriv R package, but couldn't make it work. Any help is greatly appreciated.
Thanks!

Check the documentation. Closing


Add fio2_percent and oxygen_flow_rate

@sadiekelly would you mind checking the guinea parser particularly? It seems like it was merged before your review changes were applied, so it's worth going back and double checking I caught everything.

@sadiekelly would you mind checking the guinea parser particularly? It seems like it was merged before your review changes were applied, so it's worth going back and double checking I caught everything.

@pipliggins thank you! looks ok - I just added a comment regarding the oxygen_therapy supertype to include all variables that indicate any oxygen therapy was given. I noted from my review the addition of mapping palpitations and edema but these attributes don't seem to be present in the version of the parser I'm looking at - are these attributes still being mapped?

@sadiekelly would you mind checking the guinea parser particularly? It seems like it was merged before your review changes were applied, so it's worth going back and double checking I caught everything.

@pipliggins thank you! looks ok - I just added a comment regarding the oxygen_therapy supertype to include all variables that indicate any oxygen therapy was given. I noted from my review the addition of mapping palpitations and edema but these attributes don't seem to be present in the version of the parser I'm looking at - are these attributes still being mapped?

Thanks Sadie - these two attributes certainly aren't currently being mapped, I'm not actually sure they ever were? I've added those Guinea changes here, it's bit confusing with changes being made to the same parts of the same parser on two different branches!

Leaving this open until the difference between fio2 and o2_flow is resolved (should O2_flow be mapped as fio2_Lmin?) and we've decided whether fio2 should be included in the oxygen_therapy super type.

@sadiekelly would you mind checking the guinea parser particularly? It seems like it was merged before your review changes were applied, so it's worth going back and double checking I caught everything.

@pipliggins thank you! looks ok - I just added a comment regarding the oxygen_therapy supertype to include all variables that indicate any oxygen therapy was given. I noted from my review the addition of mapping palpitations and edema but these attributes don't seem to be present in the version of the parser I'm looking at - are these attributes still being mapped?

Thanks Sadie - these two attributes certainly aren't currently being mapped, I'm not actually sure they ever were? I've added those Guinea changes here, it's bit confusing with changes being made to the same parts of the same parser on two different branches!

that's ok, the oxygen_therapy additions look ok, I guess pending any FiO2. I'm not sure where those attributes came from, but will gladly ignore!

Leaving this open until the difference between fio2 and o2_flow is resolved (should O2_flow be mapped as fio2_Lmin?) and we've decided whether fio2 should be included in the oxygen_therapy super type.

@pipliggins I've spoken with Laura and Felipe about these queries and have some answers, as below;
Regarding including FiO2 in the oxygen_therapy supertype, this can be done as any indication of supplemental oxygen in a boolean question can be considered as oxygen therapy. If we don't have the boolean question and just a value for FiO2 in either % or fraction of 1, then it should only be mapped to oxygen therapy where the value is greater than 0.21 or 21 % (these entries would be considered data entry errors as they indicate oxygen as at room air rather than supplemental treatment).
FiO2 captured in L/min is equivalent to other variables capturing oxygen flow volume in L/min so these can be combined into one attribute such as oxygen_flow_volume. FiO2 in L/min is not really an FiO2 measurement but can be converted, the conversion depending on the method of oxygen therapy used. So I think best to label these as oxygen flow volume rather than FiO2. We may need to consider adding a context note where we have different variables capturing oxygen flow volume relating to different oxygen therapy methods e.g. invasive, noninvasive as you picked up in the french database

@sadiekelly with the 2 new definitions here (oxygen_flow_rate and fio2) - do you think the presence of either/both should be used as an indicator of oxygen therapy in the visit table? Or just one?

Hi @sadiekelly, would you mind doing a final check through this? I think I've done everything we've discussed, but a second pair of eyes before I merge would be great!

Hi @sadiekelly, would you mind doing a final check through this? I think I've done everything we've discussed, but a second pair of eyes before I merge would be great!

hi @pipliggins! I've added a few comments on the updated files - let me know if something is not clear - thanks!


PetaLinux boot stuck after chang the device tree of dpu

I used the Vivado flow in DPUCZDX8G_VAI_v3.0 to run DPU. During the process of building the PetaLinux image, I used the device tree information generated by Vitis (obtained from the xsa file) to modify the project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi as follows:
/include/ "system-conf.dtsi"
/ {
};
&amba{
    hier_dpu_DPUCZDX8G: dpuczdx8g@8f000000 {
        /* This is a place holder node for a custom IP, user may need to update the entries */
        clock-names = "s_axi_aclk", "dpu_2x_clk", "dpu1_2x_clk", "m_axi_dpu_aclk";
        clocks = <&zynqmp_clk 71>, <&misc_clk_0>, <&misc_clk_0>, <&misc_clk_1>;
        compatible = "xlnx,dpuczdx8g-4.1";
        interrupt-names = "dpu0_interrupt", "dpu1_interrupt", "sfm_interrupt";
        interrupt-parent = <&gic>;
        interrupts = <0 89 4 0 90 4 0 91 4>;
        reg = <0x0 0x8f000000 0x0 0x1000000>;
    };
    misc_clk_0: misc_clk_0 {
        #clock-cells = <0>;
        clock-frequency = <249975000>;
        compatible = "fixed-clock";
    };
    misc_clk_1: misc_clk_1 {
        #clock-cells = <0>;
        clock-frequency = <124987500>;
        compatible = "fixed-clock";
    };
};

The modified PetaLinux startup is stuck (it can start PetaLinux normally before modification), and the stuck information is as follows:
U-Boot 2022.01 (Sep 20 2022 - 06:35:33 +0000)

CPU:   ZynqMP
Silicon: v3
Model: ZynqMP ZCU106 RevA
Board: Xilinx ZynqMP
DRAM:  4 GiB
PMUFW:  v1.1
PMUFW no permission to change config object
EL Level:       EL2
Chip ID:        zu7e
NAND:  0 MiB
MMC:   mmc@ff170000: 0
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment

In:    serial
Out:   serial
Err:   serial
Bootmode: LVL_SHFT_SD_MODE1
Reset reason:   EXTERNAL
Net:   FEC: can't find phy-handle
...
    3.060046] usbcore: registered new interface driver usbhid
[    3.065448] usbhid: USB HID core driver
[    3.072153] ARM CCI_400_r1 PMU driver probed
[    3.072769] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    3.080305] usbcore: registered new interface driver snd-usb-audio
[    3.086838] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    3.094266] Initializing XFRM netlink socket
[    3.097868] NET: Registered PF_INET6 protocol family
[    3.103145] Segment Routing with IPv6
[    3.106384] In-situ OAM (IOAM) with IPv6
[    3.110317] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.116449] NET: Registered PF_PACKET protocol family
[    3.121167] NET: Registered PF_KEY protocol family
[    3.125930] can: controller area network core
[    3.130265] NET: Registered PF_CAN protocol family
[    3.134999] can: raw protocol
[    3.137941] can: broadcast manager protocol
[    3.142095] can: netlink gateway - max_hops=1
[    3.146483] Bluetooth: RFCOMM TTY layer initialized
[    3.151269] Bluetooth: RFCOMM socket layer initialized
[    3.156376] Bluetooth: RFCOMM ver 1.11
[    3.160085] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.165363] Bluetooth: BNEP filters: protocol multicast
[    3.170556] Bluetooth: BNEP socket layer initialized
[    3.175487] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.181369] Bluetooth: HIDP socket layer initialized
[    3.186323] 8021q: 802.1Q VLAN Support v1.8
[    3.190552] 9pnet: Installing 9P2000 support
[    3.194707] Key type dns_resolver registered
[    3.199058] registered taskstats version 1
[    3.202997] Loading compiled-in X.509 certificates
[    3.208782] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no
[    3.222818] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 62, base_baud = 6249375) is a xuartps
[    3.231850] printk: console [ttyPS0] enabled
[    3.231850] printk: console [ttyPS0] enabled
[    3.236144] printk: bootconsole [cdns0] disabled
[    3.236144] printk: bootconsole [cdns0] disabled
[    3.245679] ff010000.serial: ttyPS1 at MMIO 0xff010000 (irq = 63, base_baud = 6249375) is a xuartps
[    3.258874] of-fpga-region fpga-full: FPGA Region probed
[    3.266395] xilinx-zynqmp-dma fd500000.dma-controller: ZynqMP DMA driver Probe success
[    3.274469] xilinx-zynqmp-dma fd510000.dma-controller: ZynqMP DMA driver Probe success
[    3.282542] xilinx-zynqmp-dma fd520000.dma-controller: ZynqMP DMA driver Probe success
[    3.290611] xilinx-zynqmp-dma fd530000.dma-controller: ZynqMP DMA driver Probe success
[    3.298675] xilinx-zynqmp-dma fd540000.dma-controller: ZynqMP DMA driver Probe success
[    3.306742] xilinx-zynqmp-dma fd550000.dma-controller: ZynqMP DMA driver Probe success
[    3.314812] xilinx-zynqmp-dma fd560000.dma-controller: ZynqMP DMA driver Probe success
[    3.322872] xilinx-zynqmp-dma fd570000.dma-controller: ZynqMP DMA driver Probe success
[    3.331009] xilinx-zynqmp-dma ffa80000.dma-controller: ZynqMP DMA driver Probe success
[    3.339078] xilinx-zynqmp-dma ffa90000.dma-controller: ZynqMP DMA driver Probe success
[    3.347150] xilinx-zynqmp-dma ffaa0000.dma-controller: ZynqMP DMA driver Probe success
[    3.355218] xilinx-zynqmp-dma ffab0000.dma-controller: ZynqMP DMA driver Probe success
[    3.363287] xilinx-zynqmp-dma ffac0000.dma-controller: ZynqMP DMA driver Probe success
[    3.371350] xilinx-zynqmp-dma ffad0000.dma-controller: ZynqMP DMA driver Probe success
[    3.379416] xilinx-zynqmp-dma ffae0000.dma-controller: ZynqMP DMA driver Probe success
[    3.387481] xilinx-zynqmp-dma ffaf0000.dma-controller: ZynqMP DMA driver Probe success
[    3.395767] xilinx-zynqmp-dpdma fd4c0000.dma-controller: Xilinx DPDMA engine is probed

Does anyone know how to solve it?

Closing FPGA Manage in the petalinux configuration can solve the problem while ensuring the correctness of the device tree

Hi,  I'm having the same issue. Petalinux ver 2022.2 DPU IP 4.1 VAI 3.0.
When DPU is added to the design, Petalinux boot up stops at the above point. FPGA manager is not selected in the petalinux configuration.
Any ideas why this issue happens ?
Thanks


status/processes page missing all "niced" processes

@jow-
I noticed that the status/processes page is missing all "niced" processes (which currently includes e.g. collectd and nlbwmon) as well as ntpd.
I think that the reason is lua pattern matching, as the niced processes are still in the busybox top output, but not in the final LuCI page. That does not look purposeful to me, as currently some "normal" monitor-style processes have been niced, but they should still be visible here as they are normal use processes.

The pattern used for matching has been the same since 6 years ago in Jan 2013 by
https://github.com/openwrt/luci/commit/a52a6a4f22861bbb1b7676b91b1f873e09bdbdfd#diff-cb4cb2401e6e43cf74a54523b8da5f02
I am no lua expert but the current pattern "[RSDZTW][W ][<N ]" looks like it rejects processes where there is no W or space before N or <.
I wonder if the middle part of the pattern should include also "<N", so that it would be something like "[RSDZTW][<NW ][<N ]".
Making that change brings collectd, nlbwmon and ntpd visible on the LuCI page.
Does that logic and change sound correct?

Sounds about right. Can you make a PR for it?

while at it we could maybe remove the top process itself from output!?
Change line 438 to 	local ps = luci.util.execi("/bin/busybox top -bn1 | grep -v 'top -bn1'")

Please filter in Lua code, otherwise you'll have another grep process to filter out ;)

@hnyman it might be better to add some logic in line 450, e.g:
		if idx and not cmd:match("top %-bn1") then

Thanks for feedback and suggestions.
Fixed with 1c80eb1962


Table

Codecov Report

Merging #33 (97a4207) into main (b9891a9) will increase coverage by 3.37%.
The diff coverage is 97.87%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   53.69%   57.07%   +3.37%
==========================================
  Files          10       10
  Lines         568      615      +47
==========================================
+ Hits          305      351      +46
- Misses        263      264       +1

Impacted Files
Coverage Δ

rct/src/table.rs
93.78% <88.88%> (-0.27%)
:arrow_down:

rct/src/styles/borders.rs
98.27% <100.00%> (+3.27%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Add new tests


Error "Cannot read property 'show' of undefined"

Hello, guys!
What am I doing wrong here?
I have my controler like this:
angular.module('myapp.controllers')

.controller('CustomerCtrl', function($scope, $cordovaDatePicker) {

     var options = {
		date: new Date(),
		mode: 'date', // or 'time'
		minDate: new Date() - 10000,
		allowOldDates: true,
		allowFutureDates: false,
		doneButtonLabel: 'DONE',
		doneButtonColor: '#F2F3F4',
		cancelButtonLabel: 'CANCEL',
		cancelButtonColor: '#000000'
	};

	$scope.showDatePicker = function() {
		$cordovaDatePicker.show(options).then(function (date) {
			$scope.display.completionDate = $filter('date')(new Date(date));
			alert(date);
		});
	};

});

And I am always getting an error on the ng-cordova.js, particularly in this function:
angular.module('ngCordova.plugins.datePicker', [])
  .factory('$cordovaDatePicker', ['$window', '$q', function ($window, $q) {
    return {
      show: function (options) {
        var q = $q.defer();
        options = options || {date: new Date(), mode: 'date'};
        $window.datePicker.show(options, function (date) {
          q.resolve(date);
        });
        return q.promise;
      }
    };
  }]);

That says "TypeError: Cannot read property 'show' of undefined... the undefined thing it is refering is "$window.datePicker", that's not defined.
I'm doing something wrong but I can't see it.
Can somebody help me, please?
Thank you!

Nevermind... that only happens on the browser, not when it is an actual application... The only thing is that I though that those plug-ins would be supported by the ionic view also, but it seems that it is not supported by the ionic view either. What a pity.
Sorry about that.
:-)

@supermarcos  hi, i use your code , but the simulator dont popup the datepicker window,  can you tell me something ? Thanks!

What simulator are you using? I mean, is IonicView? Because it won't work in that case. You have to use an app, an actual one. For me it worked when I installed the app on the device (I don't know if the device emulator works... it should since it is emulating a real device).
We have to understand that, since it is calling the underneath native libraries, it needs to be on a device.
:-)

@supermarcos Thanks for your reply. I use the iPhone6 emulator in Xcode. Maybe, I should use an actual device to test it.

Very weird, I think it should work if you're using an emulator. I don't remember the place, but Xcode must have a debug console where you probably are getting native errors. Maybe that would give you a hint...

but i cant get any error ,

and, the copy from your code,
var options = {
        date: new Date(),
        mode: 'date', // or 'time'
        minDate: new Date() - 10000,
        allowOldDates: true,
        allowFutureDates: false,
        doneButtonLabel: 'DONE',
        doneButtonColor: '#F2F3F4',
        cancelButtonLabel: 'CANCEL',
        cancelButtonColor: '#000000'
    };

  $scope.display = {};
  $scope.showDatePicker = function() {
    console.log(',,,$cordovaDatePicker.show,,,', $cordovaDatePicker.show);

    $cordovaDatePicker.show(options).then(function (date) {
        $scope.display.completionDate = new Date(date);
        alert(date);
    });
  };

Confused!

OK, two things to test:
1.- I wrapped the function "showDatePicker" inside "$ionicPlatform.ready(function() {...});" to guarantee the platform is ready to use native elements. They recommend to do so. But I don't know where are you actually invoking the function, maybe it doesn't have anything to do here... When you uses "device ready observer", you have to add "$ionicPlatform" at the controller signature like this: ".controller('CustomerCtrl', function($scope, $ionicPlatform, ..." at the top of your controller.
2.- and my html is something like this:
do not forget to declare your controller at the top:
and the button that invokes the function is something like this:
select
That's all... I assume you added the plugin to your project.

Fail,  always! Anyway, thanks so much!

Very weird... I think it must be something related with the plugin in itself.
Have you tried, just for testing if the plugin is actually working, to put the show function directly on the ready event?
I mean, something like this:
angular.module('myapp.controllers')

.controller('CustomerCtrl', function($scope, $cordovaDatePicker) {

     var options = {
        date: new Date(),
        mode: 'date', // or 'time'
        minDate: new Date() - 10000,
        allowOldDates: true,
        allowFutureDates: false,
        doneButtonLabel: 'DONE',
        doneButtonColor: '#F2F3F4',
        cancelButtonLabel: 'CANCEL',
        cancelButtonColor: '#000000'
    };

    $ionicPlatform.ready(function() {
        // this next line should be invoked just when the device is ready (or emulator), no need to press anything and it would show the native date picker:
        $cordovaDatePicker.show(options);
    };
});

I hope this helps at least to identify if the plugin is actually working.
Cheers!

I have the same error, it works on Android but fails on iOS 9.2. $window.datePicker is undefined.

I have it too when using ionic. Nothing here solves the problem as of yet.

Several months ago while building and Ionic app I dealt with all these sort of problems with this date picker, by far the most problematic plugin I have used. I took a lot of time, guesses and time to make it work more less stable. I will take a time to check my tweaks and send them to you for tests. my app has 1 year old with no updates so far and until today the date picker is still working on both latest Android and iOS. Not sure if latest cordova versions are breaking things in the process for this plugin.
I have also though if we need to start a new date picker plugin from scratch, the problem is that still I do not know much about developing them.

This seems to work for me on Android using Ionic. I still can't get it working with Desktop though unfortunately.
.controller('ExampleCtlr', function ($scope, $window, $ionicPlatform, $cordovaDatePicker) {
if (!$window.navigator.userAgent.match(/(iPhone|iPod|iPad|Android)/i)) {
    $window.datePicker = {
        show: function(options, callback) { callback(new Date());}
    };
}

$scope.openDatePicker = function () {
    var options = {
        date: new Date(),
        mode: 'date', // or 'time'
        minDate: new Date() - 10000,
        allowOldDates: true,
        allowFutureDates: false,
        doneButtonLabel: 'DONE',
        doneButtonColor: '#F2F3F4',
        cancelButtonLabel: 'CANCEL',
        cancelButtonColor: '#000000'
    };

    $ionicPlatform.ready(function () {
        $cordovaDatePicker.show(options).then(function (date) {
            //alert(date);
        });
    });
};

This plugin needs to be updated to support the browser platform - at minimum the plugin should gracefully fail, not throw errors like it currently is.


Save ucj data on granted bug fix

In SaveUcjDataOnGranted, use oldObj argument instead of getting the "old obj" from dao find. If the rule is an after rule, the dao find returns the new object not the old object, and this causes the save not to happen.

Update the predicate - remove a space after/before the opening/closing bracket to fix parsing error

lgtm，this doesnt break anything？

lgtm，this doesnt break anything？

Nothing I noticed. Anything you are concerned of?

lgtm，this doesnt break anything？

@jinn9 This flow is tested during the PaymentRequestSubscriptionFeeTest.

Yeah all the tests passed for me except the bank holiday bank service test. But this test failed before I made the update.


Store system contract address inside UniversalContract

We're still using system contract to get WZETA/Uniswap contracts addresses:
https://github.com/zeta-chain/example-contracts/blob/main/universal/swap/contracts/Swap.sol#L20-L22
Ideally, it's inherited from UniversalContract until we deprecate and remove it in favor of a contract registry.

I think we should rename it, registry or something like this

I've removed system contract from example contracts, so it's no longer going to be used, we don't need to add it anywhere.


VR Example (and other community ideas)

Hi Vatro!
Thank you for your incredible work with bringing Svelte into the web graphics forefront! It would be great to see this project gain more traction and I'd love to help out however I can. I understand that things are still very much in development and pie in the sky ideas probably don't help much, so I'll keep it brief:
In my opinion, most people would benefit from additional examples provided by the docs, especially newcomers to Svelte or Three.js, and also help ease migration from other frameworks for experienced users. A-Frame might be the ideal framework to imitate in terms of docs (and some of the API) and I think a VR example would be paramount. If you have any kind of VR capability ready, I'd really love to give it a try.
Also, maybe we could set up a Discord server? I'd be happy to help people with questions as much as I can, which could be the fastest way to a community effort around the project.
Looking forward to hearing from you,
Jasper

Hi Jasper,
thanks for your feedback / input, I'm glad you like svelthree! 🙂
documentation: there will be a new basic examples page incl. various starter-templates with the (or right after) svelthree 1.0.0-next.1 release. For people new to Svelte and / or Three.js I would strongly recommend diving into those first. My current focus is on providing decent JSDoc comments / documentation.
XR features: see e.g.:

svelthree xr tweet 1
svelthree xr tweet 2
svelthree xr tweet 3
svelthree xr tweet 4

... XR features were removed from the project / basic screen (desktop / mobile) version with the last major refactor, but will be added again in some other form (as an extension / plugin or as a standalone svelthree-xr project). Changing some core concepts of the basic version simply got too messy with all the "xr-stuff" logic being included.
Discord: I am not a big fan of discord-channel-like support, but I don't reject the idea generally. The project is imo currently way too "undone" for it. If at all, then it would make sense at some more mature point in future.
I hope / think a lot of things will develop in a more "open" (more contributors etc.), community-like direction with the project becoming more and more stable.
Cheers,
Vatro

That makes sense. The XR side of things is already a bit of a mess in the Three.js API.
The demos look great though! If you get a chance to create a fork for them, I could help polish things out.
Is there anything else I could help with in the meanwhile? I wouldn't mind writing some of the docs, but I understand if you'd like to keep things uninvolved for now.

One of the things I haven't touched yet, but I feel will become very important soon, are tests. The main reason for this was the heavy prototyping / refactoring svelthree situation, but beside that I have no clue which testing-setup to use and how to use it with all the things involved: three.js, Svelte (being actually svelte-accmod) and svelthree itself 🤯.
Currently I have a bunch of scenes (pages / routes of a SvelteKit app) which I'm using for prototyping and testing of different features, and while this is okay it isn't automated, means I have to check if each one of those is running as expected interacting with them by myself, which is getting more and more cumbersome as the number of test scenes grows.
Thoughts:

Newest create-svelte@next versions propose [Playwright][https://playwright.dev/] for browser testing... I'm not familiar with it yet, is it cool / how cool is it? How to use it with the svelthree-setup?
We would also need something to test correct rendering / state of scenes, means comparing each pixel of the actual scene-state (image / screenshot) at animation-frame X to corresponding goal scene-state (image / screenshot), kind of "simple" scene-state image comparison.
...

I could (will) provide you (to the public) asap my current SvelteKit-test-app-setup before svelthree 1.0.0-next.1 release with a simple scene as a good starting point for everything else concerning testing. It would be really cool to make some progress in this area.

There's some eye-catching videos about Playwright on Youtube - I'll be seeing into it, but first impressions are good! Seems to be a Puppeteer-like API with an "expect" constructor, which checks that the page elements are displayed correctly, under specified conditions.
Question is though: If Svelthree doesn't use DOM elements, can we bind the tests to custom JavaScript functions? And if we're going to do that, is there really a point in using another framework for testing when we could just run our own tests?
What are the current limitations in automating your tests?
I imagine it's hard to ensure the consistency of the visuals and keeping different components working together. In a dynamic system (such as automated testing), each frame is rendered stochastically. So, I don't imagine there's currently any JavaScript tooling available for that.
Components however, should trigger a console error if the experiment is a failure. Perhaps we could rig up Puppeteer to run a Svelthree app with procedural configurations and log errors with their specific conditions?
Possibly I'm somewhat misunderstanding your concerns regarding testing, so I look forward to playing with your test repo.
Hope you're having a great week


Add metric implementation and snapshots

This series of commits adds implementations of counters, gauges, histograms, and their vectorized variants. It also adds the ability to snapshot metrics for unit tests. Coming in a subsequent PR:

Push to Tally.
Prometheus-compatible scraping.
A more full-featured testing package (building upon the snapshotting functionality included here).

This PR should definitely be reviewed commit-by-commit: I've tried to make the commit messages a useful guide to reviewers.

Appreciate the thorough review of a lot of code, @willhug - comments addressed in separate commits (so you can just review the changes, instead of re-reviewing the whole diff).


Bump to v0.9.10

Updated to latest polkadot/substrate/cumulus v0.9.10.
Rust toolchain also updated to 1.55.0-nightly.
Disabled xcmp messages currently by using feature enable-xcmp.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
97

Relevant Lines:
159

💛  - Coveralls


Suggestion: add assert.string to the assert package

(Filing here per @erights request since the assert package is apparently migrating to this repo).
I just got done rewriting a bunch of what-we-decided-were-inappropriate type coercions into type checking asserts (long story), and after the tedium thought to check our usage, and it turns out that outside of tests of the assert package itself, all but 3 occurrences of assert.typeof in Agoric SDK are assert.typeof(thing, 'string').  I'm wondering if a small ergonomics improvement might be to add an assert.string(thing) (or maybe assert.isString(thing)) function to the assert API.

Done.


generator.py: fix PVector subcategory, travis-ci

Closes #128

Finally! Had to fix the Travis config, conform the generator.py tests to the PVector change, and remove bad image generations from fullScreen -- but the site is now building and passing on Travis-CI again with this pull request.
Closes #128

Noice

@kazimuth  -- once this is merged then I have a couple more pull requests against open issues ready to submit. It is much easier to those pulls are passing once master is passing.


R5RS support

Is there a (partial) port to R5RS Scheme? I am interested in Schemes with efficient compiled programs, like Bigloo.

For R5RS, it'd be much more difficult than supporting R6RS or later as it doesn't have any standard module/library feature. So, it'd be almost impossible to make portable code for R5RS implementations. I'm not familiar with Bigloo, but if it supports R7RS library syntax, I might be able to port it.

Thanks for your explanation. Unfortunately, there is no R7RS library support in Bigloo, yet. So, your project is another example showing the strengths of R7RS :-)

Your code has been ported to bigloo: https://github.com/donaldsonjw/bigloo-concurrent .


Discuss: 'all' JavaScript should not auto initialise, and export individual components

At the moment if you import 'all' it'll initialise automatically.
Should it instead do the following:
<script src="all.js"></script>
<script>
  govukFrontend.initAll()
</script>

and
<script src="all.js"></script>
<script>
  govukFrontend.Checkboxes.init()
</script>

Adam has an interesting article on this: https://adamsilver.io/articles/dont-initialise-javascript-automagically/

Here's something I wrote about initialising behaviour automagically.
Unfortunately, it's me sharing my article ( :) ) but it documents quite a few of the problems I've faced in the past.
https://adamsilver.io/articles/dont-initialise-javascript-automagically/
I spoke with @nickcolley about potentially have the best of both worlds—sensible defaults, with the ability initialise manually/programmatically, so that's something to consider. I think the current approach allows for that.

After integrating the JavaScript into the design system, I think this is definitely something we should consider.

Closed with https://github.com/alphagov/govuk-frontend/pull/759


PDF doesn't work when uploading

This PDF gives an error when uploading:
ASS_042_Krishna_Yajurvediya_Taittiriya_Samhita_Part_6_-_Kasinath_Sastri_Agase_1949 - excerpt.pdf

But when I re-saved the PDF using Preview, the PDF now works when uploading:
ASS_042_Krishna_Yajurvediya_Taittiriya_Samhita_Part_6_-_Kasinath_Sastri_Agase_1949 - two.pdf

Tried uploading the first PDF on localhost, and the upload succeeds (albeit slowly):
./cli.py create-project --title "Test" --pdf-path ~/Downloads/ASS_042_Krishna_Yajurvediya_Taittiriya_Samhita_Part_6_-_Kasinath_Sastri_Agase_1949.-.excerpt.pdf
 * [OK] Ambuda database check has passed.

Fetching project and status (slug = test) ...
Creating 36 Page entries (slug = test) ...
Succeeded. Project is at test.

Will try on prod in the morning.

Yes, it worked on localhost for me too, but doesn't work on prod.


Feature/didx request with public did

Introduces an optional flag use_public_did in /didexchange/create-request
Enabling the flag will create a DIDX request with the public DID of the requester.
The approach is not ideal since the did doc will still be attached to the request instead of just setting the did property as suggested in the RFC (but not required :) ).
Setting only the did property leads to issues because of inconsistencies in ACA-Py's DID Doc class and the DID Doc class returned by the resolver.

Codecov Report

Merging #1220 (1042b90) into main (1c7bc86) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1220   +/-   ##
=======================================
  Coverage   98.47%   98.47%
=======================================
  Files         456      456
  Lines       25428    25437    +9
=======================================
+ Hits        25039    25048    +9
  Misses        389      389

This would be useful for BPA 2 BPA connections @ianco


Documentation issue: Cyclomatic Complexity Rule

The documentation for the Cyclomatic Complexity Rule states that:

A starting value of 20 is assigned and this value is then incremented for every statement which can branch the control flow within the function

From my experience here, the starting value is actually 1.
You can see from the bug report below that I'm using a threshold of 3 in the configuration, and tslint is correctly complaining that my function has a cyclomatic complexity of 4. So the default starting value is definitely not 20.
Bug Report

TSLint version: 5.3.2
TypeScript version: 2.1.0
Running TSLint via: CLI

TypeScript code being linted
export class Test {

    test(term: string): boolean {
        if (term) {
            if (term.length > 0) {
                if (term === 'test') {
                    console.log('test');
                }
            }
        }

        return true;
    }
}

with tslint.json configuration:
"rules": {
    "cyclomatic-complexity": [true, 3]
}

Actual behavior
severity: 'Error'
message: 'The function test has a cyclomatic complexity of 4 which is higher than the threshold of 3 (cyclomatic-complexity)'
at: '20,5'
source: 'tslint'

You're right, it's not the starting value. 20 is used as default if not threshold is provided by the config


Person Mention API

@jgrim there's something weird going on with this feature in https://discuss.online

@8ullyMaguire discuss.online is not running Sublinks (yet).  It's still on Lemmy


Create DeclaraCAD.enaml

Thanks @frmdstryr.
It's really concise.

Thanks @frmdstryr.
It's really concise.


FacebookUIParams interface requires href property

Trying to set the href property of the FacebookUiParams object, this error is returned while building: Object literal may only specify known properties, and 'href' does not exist in type 'FacebookUiParams'

Sorry, my bad: had an old version of ng2-facebook-sdk in cache


added support for custom progress-bar blank character

Pull Request Test Coverage Report for Build 930884467

8 of 8 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 91.994%

Totals

Change from base Build 930216258:
0.09%

Covered Lines:
586

Relevant Lines:
637

💛  - Coveralls

Pull Request Test Coverage Report for Build 930884467
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

8 of 8 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 91.994%

Totals

Change from base Build 930216258:
0.09%

Covered Lines:
586

Relevant Lines:
637

💛  - Coveralls

Pull Request Test Coverage Report for Build 930884467
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

8 of 8 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 91.994%

Totals

Change from base Build 930216258:
0.09%

Covered Lines:
586

Relevant Lines:
637

💛  - Coveralls


Getting an error on mentalBart model

Thanks for that I have one more querry I have then used the model using pipeline to generate text but it is generating some random one

Firstly, make sure your code and padding sides are correct. As BART model is small in size, we expect it to be somehow overfitting. Please use the same prompt templates we provided when making inferences.

Ok
On Wed, 27 Dec 2023, 2:49 pm SteveKGYang, @.***> wrote:

Firstly, make sure your code and padding sides are correct. As BART model
is small in size, we expect it to be somehow overfitting. Please use the
same prompt templates we provided when making inferences.
—
Reply to this email directly, view it on GitHub
https://github.com/SteveKGYang/MentalLLaMA/issues/4#issuecomment-1870109229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A62HX4NG2S36QCC63J4SWU3YLPR2VAVCNFSM6AAAAABBD4T2GOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGEYDSMRSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

But I have checked out that templates too that are provided as examples on
hugging faces and there also to output seems quiet off
On Wed, 27 Dec 2023, 2:51 pm pranjal rana, @.***>
wrote:

Ok
On Wed, 27 Dec 2023, 2:49 pm SteveKGYang, @.***>
wrote:

Firstly, make sure your code and padding sides are correct. As BART model
is small in size, we expect it to be somehow overfitting. Please use the
same prompt templates we provided when making inferences.
—
Reply to this email directly, view it on GitHub
https://github.com/SteveKGYang/MentalLLaMA/issues/4#issuecomment-1870109229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A62HX4NG2S36QCC63J4SWU3YLPR2VAVCNFSM6AAAAABBD4T2GOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGEYDSMRSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


about error map comparison on MICC

Hello, thanks for your great work, I want to know how to do the experiments like Figure 7 in your paper, can you give me some advice or share your test code?
Thanks a lot!

Hi,
I used Matlab "colorbar" to plot the error map, you can also find some plotting package in Python.


[Bug]: BadRequestError after chatting with AgentRunner

Bug Description
Chatting with an AgentRunner() leads in my case to an BadRequestError.
The LLM is "Llama3.1 70B Instruct" hosted on a VLLM Docker instance. To connect to said instance the OpenAILike() class is used.
llm = OpenAILike(
            api_base=BASE_URL,
            api_key="dummy",
            api_version="dummy",
            is_chat_model=True,
            is_function_calling_model=True,
            model="/data/models/Meta-Llama-3.1-70B-Instruct/"

        )

The AgentRunner is build upon an agent Worker which is using an ObjectIndex.as_retriever() as the tool retriever.
The specific Error message is: " ValueError('Currently only named tools are supported.')".
If you use a list of QueryEngineTools insetead of an ObjectIndex, this issue doesn't seem to appear. This however, is not scalable with a huge amount of tools.
If you use the OpenAI() class and connect to the OpenAI API this issue doesnt seem to appear, so it seems like there is an issue with the OpenAiLike class or my usage of it.
Thankful for any tips or ideas.
Version
llama-index-core==0.12.0
Steps to Reproduce
llm = OpenAILike(
            api_base=BASE_URL,
            api_key="dummy",
            api_version="dummy",
            is_chat_model=True,
            is_function_calling_model=True,
            model="/data/models/Meta-Llama-3.1-70B-Instruct/"

        )

space_name = ["testspace"]
def _get_node_tools(nodes, space_name:str)-> QueryEngineTool:

    summary_index = SummaryIndex(nodes)
    vector_index = VectorStoreIndex(nodes)
    summary_query_engine = summary_index.as_query_engine(
    response_mode="tree_summarize",
    use_async=True,
    llm=llm
    )
    vector_query_engine = vector_index.as_query_engine(llm=llm)

    summary_tool = QueryEngineTool.from_defaults(
        query_engine=summary_query_engine,
        description=(
            f"Useful for summarization questions related to the Wiki Space: {space_name}"
        ),

    )

    vector_tool = QueryEngineTool.from_defaults(
        query_engine=vector_query_engine,
        description=(
            f"Useful for retrieving specific context from the Wiki Space {space_name} "
        ),
    )
    return summary_tool, vector_tool

for space in space_names:
      vector_tool, summary_tool = _get_node_tools(space_nodes, space)
      space_to_tools_dict[space] = [vector_tool, summary_tool]

all_tools = [t for space in space_names for t in space_to_tools_dict[space]]

obj_index = ObjectIndex.from_objects(
       all_tools,
       index_cls=VectorStoreIndex,
)

obj_retriever = obj_index.as_retriever()

agent_worker = FunctionCallingAgentWorker.from_tools(tool_retriever=obj_retriever,
            llm=self.settings["llm"],
            system_prompt=self.settings["system_prompt"],
            verbose=True,)

agent = AgentRunner(agent_worker)

agent.chat("What can you tell me abot the Administration Wiki Space?")

Relevant Logs/Tracbacks
openai.BadRequestError: Error code: 400 - {'object': 'error', 'message': '[{\'type\': \'value_error\', \'loc\': (\'body\',), \'msg\': \'Value error, Currently only named tools are supported.\', \'input\': {\'messages\': [{\'role\': \'system\', \'content\': "you are an AI chatbot that helps students. You have access to \'Our Wiki\', which includes a large amount of \'Spaces\' in wich documentation and other relevant information "}, {\'role\': \'user\', \'content\': \'what is the Administration WIKI about?\'}], \'model\': \'/data/models/Meta-Llama-3.1-70B-Instruct/\', \'stream\': False, \'temperature\': 0.1, \'tool_choice\': \'auto\', \'tools\': [{\'type\': \'function\', \'function\': {\'name\': \'query_engine_tool\', \'description\': \'Useful for retrieving specific context from the Wiki Space Administration \', \'parameters\': {\'properties\': {\'input\': {\'title\': \'Input\', \'type\': \'string\'}}, \'required\': [\'input\'], \'type\': \'object\', \'additionalProperties\': False}, \'strict\': False}}, {\'type\': \'function\', \'function\': {\'name\': \'query_engine_tool\', \'description\': \'Useful for retrieving specific context from the Wiki Space Administration \', \'parameters\': {\'properties\': {\'input\': {\'title\': \'Input\', \'type\': \'string\'}}, \'required\': [\'input\'], \'type\': \'object\', \'additionalProperties\': False}, \'strict\': False}}]}, \'ctx\': {\'error\': ValueError(\'Currently only named tools are supported.\')}}]', 'type': 'BadRequestError', 'param': None, 'code': 400}

To resolve the "Value error, Currently only named tools are supported" issue with the objectRetriever as the tool_retriever in the FunctionCallingAgentWorker class, ensure that you are not specifying both tools and tool_retriever simultaneously when initializing the FunctionCallingAgentWorker. The class constructor raises a ValueError if both are provided.
Here is the relevant part of the code that checks for this condition:
if len(tools) > 0 and tool_retriever is not None:
    raise ValueError("Cannot specify both tools and tool_retriever")

To fix the issue, you should either provide a list of tools or a tool_retriever, but not both. For example:
# Correct usage with tools
worker = FunctionCallingAgentWorker(
    tools=[tool1, tool2],
    llm=my_llm,
    prefix_messages=my_prefix_messages
)

# Correct usage with tool_retriever
worker = FunctionCallingAgentWorker(
    tool_retriever=my_tool_retriever,
    llm=my_llm,
    prefix_messages=my_prefix_messages
)

Ensure that you are following one of these patterns to avoid the ValueError [1].
To continue talking to Dosu, mention @dosu.

@dosu
In the Class FunctionCallingAgentWorker only the tool_reciever is defined, not tools.
agent_worker = FunctionCallingAgentWorker.from_tools(tool_retriever=obj_retriever,
            llm=self.settings["llm"],
            system_prompt=self.settings["system_prompt"],
            verbose=True,)

When connecting to the VLLM Docker instance with the OpenAILike Class a "BadRequestError, 400" is thrown with the explenation:  'Value error, Currently only named tools are supported.'. However if one uses the OpenAI Class, everything works fine. Try again.


fix(query): fix missing unique field in query builder template

when a query gets cloned the unique field doesn't get cloned
#2331

Thanks, @MrParano1d for the contribution. It's appreciated 🙏 ❤

@all-contributors please add @MrParano1d for code


Parameters of a function are not displayed if the are in a newline

private function function_with_many_params(
  $param1='Default of param1',
  $param2='Super default for the second',
  $param3=null, $param4='Why did you not put this param on a separte line?',
  $param5='maybe even another parameter'
){
  return 0;
}

Resulting in:

This depends on pretty-printing support in the parser.


learning from missing data

[x] Forward Pass with missing_mask to compute marginals  https://github.com/Juice-jl/pyjuice/pull/1
[x] Backward Pass with missing_mask and update params when there is missing values (using missing_flow, etc)

Closing this issue as it is supported in the latest version.


rename wokers_subdomain to workers_scope and remove workers_path as an option

The path is just too much of a pain to deal with when the user can simply correctly require the workers before launching.

This was closed in the previous linked commit :octocat: Sent from GH.


added a variable to recognize if a country is blocked or not

fixed #3833.
with the fixed, any country having been deactivated could no longer make it possible to be selected. I took advantage of this opportunity and added the case a multiple selection:

Codecov Report

Merging #4199 (63f5b3e) into master (bb2db59) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4199   +/-   ##
=======================================
  Coverage   99.75%   99.75%
=======================================
  Files         180      180
  Lines        3241     3242    +1
=======================================
+ Hits         3233     3234    +1
  Misses          8        8

Impacted Files
Coverage Δ

src/modules/Dropdown/Dropdown.js
100.00% <100.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 ff70355...63f5b3e. Read the comment docs.


Renaming Packages to Supported Languages for more clarity

Renamed "Packages" to "SupportedLanguages". Packages was very
restricted name which may not be clear for majority customers. This
change is to make it more standard for saying mxnet supported languages
and help users find appropriate docs.
Moved all files in packages/ to supported_languages/.
Hyperlinks are updated throughout the documents.
Build the changes locally and verified.

I couldn't create a change on existing PR for same change. Here is already created PR that has some correspondence - https://github.com/dmlc/mxnet/pull/3489
@piiswrong

Re-based to master.
I would say having "API" section within a specific supported language page will be very easy for users. Because within a language specific guide we will have tutorials, examples, code docs etc.. along with APIs. For example users click on "Supported  Languages" -> "Python". Then he will click on "API" to see Python specific API.
Please do let me know if this sounds reasonable.

please rebase to master

Rebased to master. Let me know any pending action items from my side.


[Feature]: Add ttl policy that takes a Func(Value, Timestamp) to resolve timestamp from value

Add ttl policy that takes a Func(Value, Timestamp) to resolve timestamp from value would allow users to have a dynamic TTL based on each item. It would be a few modifications to TLruLongTicksPolicy

You can implement this as follows:
    public readonly struct CustomTLruLongTicksPolicy<K, V> : IPolicy<K, V, LongTickCountLruItem<K, V>>
    {
        private readonly Func<K, V, TimeSpan> timeToLiveFactory;

        public CustomTLruLongTicksPolicy(Func<K, V, TimeSpan> timeToLiveFactory)
        {
            this.timeToLiveFactory = timeToLiveFactory;
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public LongTickCountLruItem<K, V> CreateItem(K key, V value)
        {
            return new LongTickCountLruItem<K, V>(key, value, Stopwatch.GetTimestamp());
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public void Touch(LongTickCountLruItem<K, V> item)
        {
            item.WasAccessed = true;
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public bool ShouldDiscard(LongTickCountLruItem<K, V> item)
        {
            if (Stopwatch.GetTimestamp() - item.TickCount > this.timeToLiveFactory(item.Key, item.Value).Ticks)
            {
                return true;
            }

            return false;
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public ItemDestination RouteHot(LongTickCountLruItem<K, V> item)
        {
            if (this.ShouldDiscard(item))
            {
                return ItemDestination.Remove;
            }

            if (item.WasAccessed)
            {
                return ItemDestination.Warm;
            }

            return ItemDestination.Cold;
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public ItemDestination RouteWarm(LongTickCountLruItem<K, V> item)
        {
            if (this.ShouldDiscard(item))
            {
                return ItemDestination.Remove;
            }

            if (item.WasAccessed)
            {
                return ItemDestination.Warm;
            }

            return ItemDestination.Cold;
        }

        [MethodImpl(MethodImplOptions.AggressiveInlining)]
        public ItemDestination RouteCold(LongTickCountLruItem<K, V> item)
        {
            if (this.ShouldDiscard(item))
            {
                return ItemDestination.Remove;
            }

            if (item.WasAccessed)
            {
                return ItemDestination.Warm;
            }

            return ItemDestination.Remove;
        }

And
    public sealed class CustomConcurrentTLru<K, V> : TemplateConcurrentLru<K, V, LongTickCountLruItem<K, V>, CustomTLruLongTicksPolicy<K, V>, HitCounter<K, V>>
    {
        public CustomConcurrentTLru(int capacity, Func<K, V, TimeSpan> timeToLiveFactory)
            : base(Defaults.ConcurrencyLevel, capacity, EqualityComparer<K>.Default, new CustomTLruLongTicksPolicy<K, V>(timeToLiveFactory), new HitCounter<K, V>())
        {
        }

        public CustomConcurrentTLru(int concurrencyLevel, int capacity, IEqualityComparer<K> comparer, Func<K, V, TimeSpan> timeToLiveFactory)
            : base(concurrencyLevel, capacity, comparer, new CustomTLruLongTicksPolicy<K, V>(timeToLiveFactory), new HitCounter<K, V>())
        {
        }

        public double HitRatio => this.hitCounter.HitRatio;
    }

But note that the IPolicy.ShouldDiscard method is invoked on every cache read - so this will have a large influence on read latency.

I've updated the example code above. Functionality is fairly easy to add as a custom policy. It would also be possible to implement a custom LruItem with the TTL as a data member, and have the policy write the TTL to the item within CreateItem avoid repeated evaluation of the func from ShouldDiscard (which is perf critical). This would give equal read perf to fixed TTL at the cost of increasing the size of all cached items, so there is a tradeoff.
I do not want to add this to the default implementation because at runtime it would be necessary to choose between the fixed TTL or calling the func, depending on which is initialized. In my tests this degrades perf a few %. Therefore, it seems better to use either fixed TTL or custom per value policy and save those % rather than have a flexible but slower single policy. User then retains fastest version by default, and can choose to customize and build the policy that is best for their scenario.
I will add this to the docs as an example customization and keep it updated.


Investigate cost of adding metadata

Possibly add one or all of:

Changeset ID
User ID
Object version number
Timestamp

We would ignore metadata for nodes that have no tags.

Hi @bdon. I'm a big fan of OSMExpress and the Protomaps extract service. At my company we have some internal tooling that relies on the object version number for caching. We don't need the changeset/user/timestamp. Would you consider adding version numbers to Protomaps extracts? Thanks.

are you working with a .osmx locally or just a .pbf extract? If an .osmx is it a region or the whole planet? I'm wary to implement this because it will probably double the total db size.
Ideally: metadata is optional, and you won't pay the storage cost for it if you don't use it. but I think this depends on migrating from capnproto to flatbuffers because of how empty fields are stored.

We are just working with .pbf extracts for now.

added version, timestamp, changeset, uid, username to database
currently working on a new planet import to confirm the expansion in size is reasonable

untagged nodes are ignored
still using capnproto

on an AWS i3.xlarge instance, osmx expand planet.osm.pbf planet.osmx took exactly 7 hours and resulted in a 643G planet.osmx file. The expansion in size when adding all metadata (ignoring untagged nodes) should be less than 10% total, so i'dp refer to always include metadata.

download server at http://protomaps.com/extracts now includes version and timestamp information
@invisiblefunnel let me know if this is working for you; I'm working on the ecosystem around these tools so I'm interested in what people are building!

Thanks @bdon! This is great news. I'll take a look this week and reply back.

I just grabbed an extract from protomaps, loaded it into josm, fixed a road's name, and uploaded the change. This demonstrates that the extract had the required meta-data (version). I also manually verified that elements had edited at and edited by attributes.
However... I cannot use this as a source to change the shape of a road, since most of the way's nodes are tag-less, and you don't provider them with a version.
Please reconsider including meta-data (or at least version) on tag-less points. That would allow the extract to be used for any type of edit.

Please reconsider including meta-data (or at least version) on tag-less points.

FWIW this is also a blocker for my use cases which rely on the ID and version to uniquely identify objects in time.

just to confirm - to make this work for your use cases only version is needed and no other metadata?

Confirmed, version would make exports usable for editing projects. I can't think of a reason I'd want other meta-data on tag-less nodes, and I'm sure any reason I eventually think of won't justify the cost.

Here's my test region:
osmx extract planet.osmx benchmark.osm.pbf --bbox 38.462,-77.519,41.0130,-73.333

first run on versionless planet: 943 seconds
second run: 919 seconds
version planet: 873 seconds
version planet 2nd time: 773 seconds
echo 3 > /proc/sys/vm/drop_caches can be used to clear the page cache, but the extract is probably big enough so that it doesn't make a difference. This isn't a very controlled experiment because the versionless planet has been being updated for a few weeks and might be more fragmented. In any case, it doesn't look like adding versions to locations negatively affects the speed by that much.

@blackboxlogic @invisiblefunnel new planet with versions is now online - can you try on https://protomaps.com/extracts/ ?

Works perfectly for me. Many thanks @bdon.

Every element has a version number, so the extracts are usable for editing.
Tag-less nodes don't have edited at, which is expected. However, I'm noticing that edited by and changeset are both 0 for all objects. Is that intentional?

Yes, the data is stored but I intentionally am excluding it. That seems to be the convention for GDPR compliance. Is that needed for any of your applications?

I definitely don't need it but it could be plausibly useful* and if you're storing it already then there isn't much to gain by withholding it. Other services handle GDPR by offering the "pii" only to OSM users who have signed in with oAuth, since they have agreed to terms of service. That would, of course, complicate your service by involving oAuth.
*Possible use-case: A vandal changes all buildings into parks, I want to remove all leisure=park where [vandal's name] was the last editor. I've had to do this sort of thing a few times.

I have an auth system built which is separate from osm Oauth. I could make PII only available to logged in users.
Can you describe your editing workflow in more detail ? I’d like to include it in my SOTM talk and I can mention your username if that’s ok.

Re: "Describe your workflow"
Short version: "I've build up a collection of scripts which can be chained together" but I think that's just called "programming"?
Here's a recent example of my work, but I plan to do more and there are two parts of my pipeline I'm rewriting (pulling data from OSM, and schema translation). One of the more cumbersome parts was retrieving up-to-date large regions of data from OSM. It was awkward for multiple reasons and my future projects will benefit from your work.
If you want a longer description shoot me an email [blackboxlogic at gmail dot com] with your phone number and best time to call, I'd love to chat.

Great, we can discuss over email.


Sanitize srt passphrase from showing up on the streams listing table

We managed to get passphrase SRT streaming working and overlooked that the passphrase will show up in the stream listing table. The passphrase argument will need to be sanitized on this view.

Relates to https://github.com/eluv-io/elv-live-stream/commit/c8ce752eea288ae3f292f17a8cb57961098daa46
Deployed to demo

Verified. I no longer see the SRT arguments printed out on the stream listing table.


feat: add connection monitor

Adds a connection monitor that periodically ensures remote peers are still online and contactable by trying to send a single byte via the ping protocol, and sets the .rtt property of the connection to how long it took.
If the remote responds that the ping protocol is not supported, it tries to infer the round trip time by how long it took to fail.
If the remote is unresponsive or opening the stream fails for any other reason, the connection is aborted with the thrown error.
It's possible to configure the ping interval, how long we wait before considering a peer to be inactive and whether or not to close the connection on failure.
Closes #2643
Change checklist

[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation if necessary (this includes comments as well)
[x] I have added tests that prove my fix is effective or that my feature works

This was discussed on the maintainers call and there was a suggestion to make this a service that the user would have to configure.
I'm having a hard time thinking of when you wouldn't want this so it's implemented as part of libp2p and on by default.
Happy to talk about this further before merge.

LGTM. This will eliminate the complexity of managing this at the application layer which is a major improvement.

I'd like to see this be disable-able

@wemeetagain a flag has been added:
const node = await createLibp2p({
  connectionMonitor: {
    enabled: false
  }
})


Add more checks for managed processes

A .nettrace file collected for an Asp.Net 6 app running on Azure App Service for Linux does not have coreclr as part of its loaded modules list.

@WilliamXieMSFT, this makes sense.  Some of the existing analyzers won't work, since they look for mscorlib, but you can fix this in any of the analyzers you own directly.  I have this as a follow-up to address in the analyzers.


Questions about FSRSDataset

@L-M-Sherlock I have a question about FSRSDataset before I refactor it.
Currently there are ::train() and ::test() methods that return the same dataset. Is there a plan to make them return separate data in the future? Or would one method be enough?
Likewise with dataloader_train/_test - will they differ in the future? Or should they always have the same source data?

Test dataset will be empty in real optimization for users. FSRS will all data in the training.

Sorry, I may need an ELI5 here :-) Are you saying that when users train their real data, we'll pass in the full vec of FSRS items to dataloader_train, and an empty vec to dataloader_test? What advantages are there in passing in the full data to dataloader_test when developing?

Yeah. We will pass an empty vec to dataloader_test. I haven't test that, so I passed full data to dataloader_test like the example provided in burn when developing. Please feel free to remove it.

Sorry, one more question: is config.seed supposed to be random in actual use (outside of tests)?

And one more :-) Is requestedRetention relevant for the training process, or something that only applies after the weights have been generated?

Sorry, one more question: is config.seed supposed to be random in actual use (outside of tests)?

I recommend making it fixed. Because I don't want the user complain that the optimized parameters are always different over each training.

Is requestedRetention relevant for the training process, or something that only applies after the weights have been generated?

The requestedRetention is unrelated for the training. Users should set it by themselves.


✨ Implement "upgrade plan" support

What this PR does / why we need it:
This PR implements upgrade plan support for the plugin
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #129

/hold

/retest

/retest

/retest

/area plugin

/hold cancel

/lgtm
Will leave hold in case Mike wants to re-add removed test, otherwise everything looks good. Thanks!

/hold cancel

/retest


feat: Add configuration for main menu item separation

Adding a new configuration parameter to control the vertical distance of menu items in the main menu. This configuration can be used to support large fonts by decreasing the menu_item_separation configuration.
Fixes https://github.com/deep-entertainment/issues/issues/33

Thanks a lot. 🎁


[Feature] Start, Pause, Stop Recording/Capturing GUI

As seen on this screencast:

It would be awesome to be able to first select a screen region, so you can set-up everything and begin recording accordingly! starting, pause, starting again and stopping it.

Start, stop and pause is not going to be possible (at least not that I know of it), as I am simply triggering ffmpeg and haven't heard that you could stop/resume on that. It only shows q for quit :-)
I will close it, as it won't be possible.
The partial screen capture however might be possible (#5)

Got ya!
Op do 19 mei 2016 22:28 schreef cytopia<EMAIL_ADDRESS>
Start, stop and pause is not going to be possible (at least not that I
know of it), as I am simply triggering ffmpeg and haven't heard that you
could stop/resume on that. It only shows q for quit :-)
I will close it, as it won't be possible.
The partial screen capture however might be possible (#5
https://github.com/cytopia/ffscreencast/issues/5)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/cytopia/ffscreencast/issues/10#issuecomment-220438983

--
Dimitrie Hoekstra, UI & Interaction Designer
dhesign.com  |<EMAIL_ADDRESS>| LinkedIn
https://www.linkedin.com/in/dimitrieh | Twitter
https://twitter.com/strages33/


PLAN-556 indesign publications

uses code from the conclar branch as well

I would like to get this into staging so more tests can be done


What does "requires root" mean?

What are root privileges in the context of a Windows OS? Do you mean Admin privileges?

Do you mean Admin privileges?
I am not on win but i would assume you are right.


[BUG] Can't export using FromView on 3.0

I am following the instructions outlined in the readme, but get an error during export.
Package version, Laravel version
3.0, 5.6.5
Expected behaviour
Export the view
Actual behaviour
Throws error
Exception stack trace
Declaration of ...\Exports\PartsExport::view() must be compatible with Maatwebsite\Excel\Concerns\FromView::view(): Illuminate\Contracts\View\View

PartsExport class
use App\Part;
use Maatwebsite\Excel\Concerns\FromView;

class PartsExport implements FromView
{
    public function view()
    {
        return view('exports.list', [
            'parts' => Part::all(),
        ]);
    }
}

As the error indicates, you are missing the return type:
public function view(): \Illuminate\Contracts\View\View
I wouldn't suggest using 3.0 in production-ready code yet. It might still change (and break your code) on each composer update.

Thanks, I guess the readme will be fleshed out as you go.

Adding use Illuminate\Contracts\View\View; to the top of your export will fix this error too.


[Feedback] Fixed deprecated messages

Perhaps @stof can provide some feedback?

I don't like the SecurityLegacyLayer service. Instead, I suggest inject the new services when available and injecting the SecurityContext otherwise, as done in FrameworkBundle. Classes needing it would only have 2 properties tokenStorage and authenticationChecker which they would use (both properties would contain the SecurityContext on Symfony 2.3)

@stof PR has been updated.

@stof PR is updated again.

Hold on a minute, I forgot something.

@stof Check again :)

When will this go into a new release?


bug<EMAIL_ADDRESS>~3x faster than<EMAIL_ADDRESS>when waiting for tx confirmation

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.0.5
Current Behavior
When testing on Arbitrum, using waitForTransaction wagmi action, based on my limited batch of testing (10 txs for each wagmi@1 and wagmi@0), wagmi@0 using ethers, was ~3x faster.
Test setup:
function useDeposit() {
  const { config, error: prepareError } = usePrepareContractWrite({
    address: WETH_ADDRESS,
    abi: WETH9_ABI,
    functionName: 'deposit',
    value: 1n,
  });
  const { writeAsync, error: writeError } = useContractWrite(config);
  return async () => {
    const startTime = performance.now();
    const tx = await writeAsync();
    const wroteTime = performance.now();
    await waitForTransaction({
      hash: tx.hash,
      confirmations: 0,
    });
    const endTime = performance.now();
    console.log({
      endTime,
      wroteTime,
      startTime,
      waitTime: endTime - wroteTime,
    });
  };
}

After 10 tries, average for viem was 3242ms, while for ethers it was much more reasonable 1020ms.
wagmi@0 stackblitz: https://stackblitz.com/edit/new-wagmi-jalzmn?file=src/App.tsx
wagmi@1 stackblitz: https://stackblitz.com/edit/new-wagmi-tvmzct?file=src/App.tsx

Raw data
// ethers
1196.0049999952316
1022.2550000101328
847.0850000083447
1654.765000000596
881.6150000095367
876.1299999952316
889.6200000047684
937.8499999940395
1003.7449999898672
893.265000000596
// viem
1478.220000013709
1677.4950000047684
4882.155000001192
1451.719999998808
4862.840000003576
5738.280000001192
1310.8700000047684
1295.8849999904633
4853.734999999404
4875.469999998808

Expected Behavior
Would love to see viem actually faster, not slower

Interesting. Looks like this has to do with how viem handles confirmations: 0. Have you tried setting confirmations to 1 (default) or more? Setting confirmations: 0 should return immediately (need to update this on viem's end) with the result of eth_getTransactionReceipt (which will fail if the transaction is still pending).

confirmations: 1 seems to be even worse, with 5 tries, wagmi@0 averages ~1s and wagmi@1 averages ~5s


Add Waveshare ESP32C3-Zero to GPIO-Viewer

Can you please add the Waveshare ESP32C3-Zero to GPIO-Vierwer?

Thank you for your work
Greetings
Tom

The board is now available.

Thank you, that was really quick. Now I have to figure out, why the model is not shown in the Tasmota GPIO-Viewer section...

If you use Tasmota v13.3.0 you won't see it as this version uses a different hosted version of gpio_viewer for legacy reasons. Just change to the current live hosted gpio_viewer using command gpurl or install current tasmota dev release.


Update email feature to list contents of job search in email body

Current Behaviour
Job search results is sent as a file attachment to the email.
Changes Requested
Update to send the job search results in the email body.

hi! I resolve this issue, I want to make a pull request

hi! I resolve this issue, I want to make a pull request

@feriodismo Sure go ahead and make a PR!

@feriodismo Sure go ahead and make a PR!


test: Add unit test for warn_error argument in DbtRunOperator

Add a test for #103
Also includes some assorted random fixes as apparently our hooks started misbehaving for no apparent reason. Hopefully I'm not hiding any issues.

Well, now it worked, guess it's not bad to use it as an excuse to bump readthedocs to Python 3.11 :shrug:


Add support for .NET 3.5

It appears that ClosedXML is holding off on taking a dependency on the latest versions because support for .NET 3.5 is dropped (see https://github.com/ClosedXML/ClosedXML/issues/225). Is there interest for a .NET 3.5 build of the library?

We can take a look at this after #175 is merged so we can be up to date with the project system.


Added groups info call

Would be awesome if you merged and released this

Thanks, very long delay on this, sorry. I'll try to test all there pull requests and make a new release shortly.

@qbanguy @alanshaw
This is in 0.3.0 that was released to npmjs.com a couple of hours ago.
Thanks again!

@RexMorgan Thanks!

@RexMorgan Thanks!


Issues with "make test-tidy" and "make docker-tidy"

Describe the bug

make test-tidy asks me to run make tidy to fix my go.mod even though I have the "wrong" go version installed
make docker-tidy does not work when go 1.13 is installed locally because of breaking changes in GOPROXY between 1.12 and 1.13

To Reproduce

Install go 1.13 locally
Run go mod tidy
Run make test-tidy: it will fail and ask you to run make tidy, which is bad advice
Run make docker-tidy: it should fail with the following logs

go<EMAIL_ADDRESS>invalid $GOPROXY setting: cannot have comma
go<EMAIL_ADDRESS>invalid $GOPROXY setting: cannot have comma
go<EMAIL_ADDRESS>invalid $GOPROXY setting: cannot have comma
...

Versions:
Antrea version:
===> Version information <===
VERSION: v0.2.0-dev
GIT_SHA: a66c8cc
GIT_TREE_STATE: dirty
RELEASE_STATUS: unreleased
DOCKER_IMG_VERSION: v0.2.0-dev-a66c8cc.dirty

Go version:
go version go1.13.4 linux/amd64

Proposed solution for the GOPROXY issue: do not set the GOPROXY environment variable in the Docker unless it was set explicitly by the user (i.e. do not default to the output of go env GOPROXY).

@antoninbas , In CL #148 :

Run go mod tidy

go.mod changed.

Run make test-tidy: it will fail and ask you to run make tidy, which is bad advice

It fails and asks you to run make docker-tidy.

Run make docker-tidy: it should fail with the following logs

It finishes successfully. go.mod is polished.


在flutter2.5中use a deprecated version of the Android embedding.

The plugins flutter_tencentplayer use a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if these plugins support the Android V2 embedding. Otherwise, consider removing them since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration.
作者可以看一下 这个 帮忙解决一下吗

是的，我也遇到啦


dataUrlToBlob ignores type parameters and assumes base64-encoding

As remarked in #61:

a quick look at this library’s dataUrlToBlob() implementation reveals however that it throws away all of the media type parameters! And blindly assumes base64 encoding.

Current implementation:
export function dataURLToBlob (dataURL: string): Blob {
  var type = dataURL.match(/data:([^;]+)/)[1]
  var base64 = dataURL.replace(/^[^,]+,/, '')

  var buff = binaryStringToArrayBuffer(atob(base64))
  return createBlob([buff], { type: type })
}

Issues:

A data url without ;base64 appended to the media type should just percent-decode the data.

The type should include its parameters; for example, in text/plain;charset=iso-8859-5 (used with or without the base64-encoding), dropping the charset parameter might result in problems when decoding the blob’s data.

Yep, this is true! I assumed base64 encoding for data URLs (for both input and output).


Rename puppet_name to shortname

shortname is the terminology used in the Release app, where exactly the same values have been provided there as they have here, e.g. licence-finder => licencefinder:
https://release.publishing.service.gov.uk/applications/licencefinder/edit
An app's 'shortname' is used for several things, all of which will probably go away at some point:

name of the app in Puppet, e.g. https://github.com/alphagov/govuk-puppet/blob/603dc08f1a0e9148c844590d006ad22d0bc21737/modules/govuk/manifests/apps/licencefinder.pp
Sentry DSN configuration, e.g. https://github.com/alphagov/govuk-saas-config/blob/ba6a612caa61920a57d388013b0a7968b51c60fd/sentry/Rakefile#L32
For use in Graphite metrics
Colloquially, e.g. "Contacts" shortname as opposed to "Contacts Admin" application name. (But not always, e.g. "Mainstream Publisher" term used by GDS people instead of "Publisher", but not represented as such in any of our config).

Renaming puppet_name to shortname reflects the fact that we're retiring govuk-puppet soon, but that we may still need to keep these values for the other reasons above. It is also more descriptive.

Gives rise to https://trello.com/c/PUsKqIyq/2996-remove-shortname-field-from-release-app.


Silently fails to log redirected post request by Safari if npm module 'connect-pg-simple' is used with 'express-session'

If pino-http is used in an express app that uses npm modules express-session and connect-pg-simple to handle sessions, pino-http fails to log redirected HTTP request made from the Safari web browser. The problem does not occur then using Chrome or curl.
I have produced the following minimal example, that reproduces the problem stated above. Removing the store object from the session configuration, and thereby remove the usage of connect-pg-simple, does solve the problem of missing log entities.
No error message what so ever is given.
import { default as express } from 'express'
import { default as pinoHttp } from 'pino-http'
import { default as session } from 'express-session';
import { default as sessionStore } from 'connect-pg-simple';

import { default as pg } from 'pg';
const Pool = pg.Pool
const pool = new Pool()

const reqLogger = pinoHttp({
	level: 'info',
	enabled: true,
})

const app = express()

app.use(session({
	secret: 'secret',
	name: 'sessionId',
	resave: false,
	rolling: true,
	saveUninitialized: true,
	store: new (sessionStore(session))({
		pool: pool
	}),
	cookie: {
		secure: 'auto',
		maxAge: 30 * 24 * 60 * 60 * 1000
	}
}))

app.use(reqLogger)

app.get('/', (req, res, next) => {
	const html = `
		<form method="POST" action="/">

				Username
				<input name="username" type="text" id="floatingInput">

				Password
				<input name="password" type="password" id="floatingPassword">

			<button type="submit">Log in</button>
		</form>`
	res.send(html)
})

app.post('/', (req, res, next) => {
	res.redirect('/')
})

app.listen(8081, () => {
	console.log('Server running')
})

I'm not that familiar with express-session, but I guess your problem is that you do not register the middleware as first thing:
const app = express()

app.use(reqLogger)

app.use(session({
	secret: 'secret',
	name: 'sessionId',
	resave: false,
	rolling: true,
	saveUninitialized: true,
	store: new (sessionStore(session))({
		pool: pool
	}),
	cookie: {
		secure: 'auto',
		maxAge: 30 * 24 * 60 * 60 * 1000
	}
}))

It makes no differens, pino-http still fails to log post request to / if Safari is the requester. If the same request is make with curl or Chrome, the request is being logged.

Unfortunately I have no time to debug this. I would be ok to review a PR with a fix if you understand what the problem is.


Add LodeWallet Showcase

Checklist

[x] I have read the How to Contribute.
[x] I have read the Showcase Requirements
[x] I have run yarn build after adding my changes without getting any errors.

Showcase addition

Title: LodeWallet
Description: The functional Cardano wallet. LodeWallet exists to provide the simplest possible experience for Cardano deFi users and a familiar experience for deFi users from other ecosystems. We are the first native Haskell light wallet for Cardano, making direct use of existing open-source Cardano Haskell libraries.
Website:  https://lodewallet.io/
Source: null
Tags:

metadata
nftsupport
wallet

Reasons for not approving for me:

While they might be true, I am not sure if phrases built with haskell or first native Haskell light wallet for Cardano, making direct use of existing open-source Cardano Haskell libraries should be placed in description on showcase, these cannot be verified due to project being closed source. The contributing guidelines certainly ask to stay clear of "first ABC"
For a showcase addition - the overall UI feels a bit unpolished than minimalistic (compared to typhon/flint/nami/eternl..), but that might just be me personally.
In case it does not get approvals, the wallet is already on support-faq and may also be added to https://essentials.cardano.org instead

Reasons for not approving for me:

While they might be true, I am not sure if phrases built with haskell or first native Haskell light wallet for Cardano, making direct use of existing open-source Cardano Haskell libraries should be placed in description on showcase, these cannot be verified due to project being closed source. The contributing guidelines certainly ask to stay clear of "first ABC"

As an alternative for Description, how about:
"Produced by Obsidian Systems, LodeWallet exists to provide the simplest possible experience for Cardano deFi users and a familiar experience for deFi users from other ecosystems."

For a showcase addition - the overall UI feels a bit unpolished than minimalistic (compared to typhon/flint/nami/eternl..), but that might just be me personally.

Yes, seems too subjective to block inclusion or warrant further discussion.
Thanks.

@chobbins: Yes, seems too subjective to block inclusion or warrant further discussion.

There is never going to be a case when a reviewer's subjective statement blocks discussion. By the same token, if a reviewer comes forward with a subjective opinion it means they're prepared to justify it according to their understanding of industry best practice & the content guidelines for the Portal. As I see it @rdlrt's statement was an invitation to further discussion rather than a closure, as is my own review... and I'll tag a few more reviewers to ensure this opportunity. 😎

Fair enough! I could have said what I meant better: I disagree with the general statement that LodeWallet lacks polish relative to all other light wallets currently included here. It is unclear what limiting principles would exist for such a conversation and how a fair/objective decision would be made.
In terms of the description, we're happy to change it. Though, it isn't clear how an 'aim to provide the simplest possible experience' (also subjective, to be fair) is different in kind from some of the existing entries including descriptions like:
"Aims to add features most requested by the Cardano community."
"The ultimate wallet experience for the Web, with native NFT and token features, powered by Cardano and third party applications."
Cheers

Hello, regarding "first this and that" there was a long discussion about this here: https://github.com/cardano-foundation/developer-portal/pull/167 and an extended discussion here: https://github.com/cardano-foundation/developer-portal/discussions/176  which ultimately resulted in the rule for adding projects:

Describe what makes your project special, avoid phrases like "the first this and that". Granular details like which project was first is tribal attribute known to cause rift and conflicts.

Source: Guidelines for adding showcase projects


graphql endpoint uri in production

I made project with default kit files -> npm run build -> npm run server
When I visit page at mydomain.com all graphql queries from client go to "http://localhost/graphql"
I can fix this by setting "defaultHost" to my mydomain.com in env.js. Is it proper behavior?

I have the same problem. Is there any proper way to set host for production (with nginx as a web-proxy) without changing kit's files?

Setting SERVER_DEV_HOST and SERVER_PROD_HOST is supposed to update the endpoints in each environment, but I'm running into issues locally too.
I'll refactor kit/lib/env today to work as expected.


how to hide tree-node-expander when there are no children

PLEASE READ CAREFULLY!
Just a question about how I can NOT show the node expander when there is no children for a node.
Reproduce
Please reproduce here if reporting a bug, or requesting help:
https://stackblitz.com/edit/angular-wxansn
Additional Info

paste your package.json
which browser
paste your code

Use the Slack Channel
The fastest way to get an answer is via the slack channel:
https://angular-tree-component.herokuapp.com/
You will also get updates on releases, bugfixes and other announcements.
Search Docs First
Please look for an answer in the docs before submitting an issue:
angular2-tree.readme.io.

NM, my issue was that I was passing a children array that was empty,  when I null it out the tree-node-expanders go away.


USPS Sensor errors

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.46
Python release (python3 --version):
Python 3.4.2
Component/platform:
sensor.usps
Description of problem:
USPS Sensor should show Informed Delivery as well as Packages. Only Informed Delivery shows, generally requires deletion of usps_cookies.pickle in between restarts now as well.
Expected:

Should show USPS Informed delivery & USPS packages. I do have scheduled packages in my my.usps.com dashboard with valid tracking, including one out for delivery right now.

Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: usps
  username: !secret usps_username
  password: !secret usps_password
  name: 'USPS'

- platform: template
  sensors:
      packages_in_transit:
        friendly_name: "Packages in Transit"
        value_template: >
          {% macro in_transit(sensor) %}
            {{sensor.state|int - delivered(sensor)|int}}
          {% endmacro %}
          {% macro delivered(sensor) %}
            {% if 'delivered' in sensor.attributes %}
              {{sensor.attributes.delivered}}
            {% else %}
               0
            {% endif %}
          {% endmacro %}
          {{in_transit(states.sensor.usps_packages)|int + in_transit(states.sensor.fedex)|int}}
      deliveries_today:
        friendly_name: "Today's Deliveries"
        value_template: >
          {% macro delivered(sensor) %}
            {% if 'delivered' in sensor.attributes %}
              {{sensor.attributes.delivered}}
            {% else %}
               0
            {% endif %}
          {% endmacro %}
          {{delivered(states.sensor.usps_packages)|int + delivered(states.sensor.fedex)|int}}

Traceback (if applicable):
2017-06-05 12:14:11 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.usps_mail, new_state=<state sensor.usps_mail=4; icon=mdi:mailbox, friendly_name=USPS mail, attribution=Information provided by www.usps.com @ 2017-06-05T12:14:11.648612-05:00>, old_state=None>
2017-06-05 12:14:12 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 368, in async_process_entity
    new_entity, self, update_before_add=update_before_add
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 198, in async_add_entity
    yield from self.hass.async_add_job(entity.update)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/sensor/usps.py", line 78, in update
    for package in myusps.get_packages(self._session):
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/myusps/__init__.py", line 155, in wrapped
    return function(*args)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/myusps/__init__.py", line 188, in get_packages
    'tracking_number': _get_tracking_number(row),
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/myusps/__init__.py", line 118, in _get_tracking_number
    return row.find(TRACKING_NUMBER_TAG, TRACKING_NUMBER_ATTRS).string.strip()
AttributeError: 'NoneType' object has no attribute 'strip'

Additional info:

Relevant forum thread

Paging @happyleavesaoc Thank you for all that you do, please advise as to how I might be able to fix this whenever you have a chance.

@brianjking Appears to be a bug in python-myusps. It will need to be fixed and updated in HA.

@happyleavesaoc Ok, thanks. I guess it's not just broken for me then. Let me know if you fix it in python-myusps and I can manually update without waiting for 0.47 HA.

It's broken because one of your tracked packages probably doesn't have a tracking number. Check for that if you can and just delete that one. See if that helps.

@happyleavesaoc Both of my packages are both valid tracking #'s.

I also have to delete the usps_cookies.pickle everytime I restart HA all of the sudden.

@happyleavesaoc -- It now shows the packages after I deleted the custom names. However, it's still not showing that one is out for delivery (has been since 9:00am and it's currently 13:19hr).

@brianjking Ah! The custom name is not accounted for in python-myusps. I have fixed this locally.
I'm not sure yet about your other two issues.