Todolist

[x] and
[x] bitAnd
[x] or
[x] bitOr
[x] not
[x] compose
[x] nand
[x] nor
[x] nth
[x] noop
[x] apply
[x] pipe
[x] length
[x] inc
[x] dec
[ ] equal
[ ] strictEqual
[ ] lt
[ ] gt
[ ] le
[ ] ge
[ ] bind
[ ] call
[ ] has
[ ] converge
[ ] isString
[ ] isObject
[ ] isBoolean
[ ] isNumber
[ ] isInt
[ ] isPlainObject
[ ] plus
[ ] minus
[ ] times (I don’t like this name)
[ ] by
[ ] isTrue
[ ] isFalse
[ ] isNull
[ ] isUndefined

Function

[x] curry1,2,3,4

Array functions

[x] filter(function, array)
[x] reduce(function, array)
[x] every(function, array)
[x] some(function, array)
[x] reduceRight(function, array)
[x] reduceFrom(function, initialValue, array)
[x] reduceRightFrom(function, initialValue, array)
[ ] forEach(function, array)

String functions

[x] join(string, array)
[x] split(splitStr, string)
[ ] word
[ ] csv

RegExp

[ ] replace(regEx, string)
[ ] match(regEx, string)

I have implemented bit-wise operations ;)

How about renaming them to bitAnd, bitOr...?

@stoeffel Done.

@stoeffel How are you planning to implement deepEqual in one line? JSON.stringify? assert.deepEqual ;) ??

How are you planning to implement deepEqual in one line?

hihi, don't know. This is just a list of things that came to my mind.

How about functionizing string and array functions, like you did with map? I mean:

replace(regEx, string)
match(regEx, string)
split(splitStr, string)
reduce(function, array)
reduceFrom(function, initialValue, array)
join(string, array)
forEach(function, array)
…

That’s what I meant in https://github.com/stoeffel/1-liners/pull/10#issuecomment-95158332.

How about functionizing string and array functions, like you did with map

:+1: Yop that's what I was thinking too. Let's add them to the todolist. I have to sleep now, will have some time tomorrow evening.

How about:

isString
isObject
isBoolean
isNumber
(no need to duplicate Array.isArray)
isInt
isPlainObject

:+1: what is the difference between isObject and isPlainObject?

https://lodash.com/docs#isObject
https://lodash.com/docs#isPlainObject

Thanks for the links.
Let's add this functions to 1-liners.

https://github.com/stoeffel/1-liners/pull/30#issue-72239642
const sum = (numbers) => numbers.reduce((a, b) => a + b);

the (a, b) => a + b would fit into 1-liners well, wouldn’t it?
How about:

plus
minus
times (I don’t like this name)
by

https://github.com/stoeffel/1-liners/pull/31
If these go through, it’d be good to have the following as well:

isTrue
isFalse
isNull
isUndefined

One more idea. How about these:

property:
(object, property) => object[property]

method:
(object, method) => (...args) => object[method](...args)

equal
strictEqual

How about

looseEqual
equal?

The JS community seems to prefer === over == – see for example https://github.com/airbnb/javascript#comparison-operators--equality (the most popular coding style by all means).

This all sounds great.  I hope I will have some time tomorrow to jump in on this.

Haha, thanks :D Take it easy @stoeffel – take your time :)

BTW, I’m just working on another project and whenever I need a little tool I put it here instead of there :)

BTW, I’m just working on another project and whenever I need a little tool I put it here instead of there :)

cool.

I have a tomekwi/1-liners#edge for things I need quick :)

Feel free to just publish to npm.

looseEqual
equal?

Yop, in my opinion this should always be the default.

I will close this in favour of individual issues, to be apple to keep track of development.


Should jsonOf and jsonEncoderOf be implicit?

In all of our JSON support modules, jsonOf and jsonEncoderOf, which create an EntityDecoder or EntityEncoder from an implicit instance of each library's JSON codecs, are not implicit.  Users frequently expect defining a JSON codec for their case class is sufficient for an entity codec.
We historically have not made this implicit, because it's not a given that users want to code case classes as JSON.  But maybe we should: if the user supplied a way to encode it as JSON, without any other available encodings, then it's probably a JSON API.  And if there are multiple codecs for a case class in scope, it should fail due to ambiguous resolution.
Thoughts?
/cc @tskardal

Another vote from a colleague that it should be implicit.

What about
scala> jsonOf[String]
res0: org.http4s.EntityDecoder[String] = org.http4s.EntityDecoder$$anon$2@55dc3bd7

Another item to note is that there currently isn't any way to configure your argonaut PrettyParams for jsonEncoderOf. For example, if you want to drop fields with None values instead of including them as null in the JSON, as far as I can tell you basically need to copy/paste the relevant http4s-argonaut code and replace the PrettyParams.
In addition to the String case from above (which I suspect probably isn't much of a problem in practice due to implicit priorities), this is something that makes these encoders seem less "universal" to me and therefore potentially a reason that they shouldn't be implicit.

Oh yeah, I had to do this. :-/

I left a comment on #690 relating to prioritization that has me leaning toward this being a bad idea again.

I'm surprised that the PrettyParams is an issue.  I have a Chrome extension that pretty prints my JSON, and I either use httpie or pipe into Python's pretty printer from the console.  I think compact JSON is for services and tooling is for human debugging.  But I'm open to making this configurable if it's making people copy and paste.

If we're not going to change this, and good reasons are emerging not to, I want to think about making the best of it and having a solid recommendation vs. the scattered approaches we have now.
https://github.com/http4s/http4s/pull/689#discussion_r76669325

I think compact JSON is for services and tooling is for human debugging.

@rossabaker I agree, and in fact the reason that I wanted to override it is to get a more compact printer via dropNullKeys = true :). The default argonaut printer prints fields with None as a value as "foo": null, whereas generally the services that I've worked on have decided to just not include those fields in the JSON object.

Ah, so it's not just a whitespace issue, it's also a semantic issue.  Okay, I feel less grumpy about making that work.

Closing due to lack of mandate for change.


feat: Implement CEL validation

Thank you very much for this job.
Should I merge this PR and then push it upstream? @jimmidyson

@chaunceyjiang If you merge this PR then it should automatically update the CAPI PR with CEL validation 🤞

@chaunceyjiang If you merge this PR then it should automatically update the CAPI PR with CEL validation 🤞

Ok.

Hello, @jimmidyson, if you're ready to merge, feel free to cc me anytime. I will come and merge this PR. Thank you very much~


Re-submit the Dockerfiles for alpine-maven images

Built both jdk8 & jdk11. Tested the jdk8 image on http://builds-inception.tivo.com:8080/job/udf-model-pgd/view/change-requests/job/PR-112/3/

I would suggest in the future you do at least 10sec sanity test of your PRs.  One like at what you actually proposed makes it clear why this was wrong.


Warrior Id's from the core don't match the UI when warriors are disabled

If we have a list of warriors and I toggle one of them off, I filter the warriors which get passed to the core so passing 2 warriors to core, but there may be 3 files.
The colours I'm using for the icons are based on 3 warriors, but the core assumes the colours based on the warrior index and in the example here will only have two warriors.
As a result it's possible to have colours in the core which don't match the files:
In the below example the colour indexes are blue[0], red[1], yellow[2] which is what the tabs along the top show. But in the core the vampire is toggled off which results in the blur scanner being coloured red when it should be yellow.
The file list shouldn't change but the core colours should use the file indexes not the warrior indexes to determine their colours:

Databag is a solution to this guy

You are databag

Allow an additional data object to be attached to the parse results passed into the Simulator.  The Simulator will store an immutable clone of this data object against the the corresponding loaded 'Warrior' and broadcast it in any pubsub messages which contain the warrior id.


Update loading attribute status

The linked PR has been closed and has been integrated into the living standard.

Can you also mark Firefox 75 as supported? The according issue was just marked as resolved: https://bugzilla.mozilla.org/show_bug.cgi?id=1542784

Can you also mark Firefox 75 as supported? The according issue was just marked as resolved: https://bugzilla.mozilla.org/show_bug.cgi?id=1542784

Done. Thanks for the information! 🙂

Can you also mark Firefox 75 as supported? The according issue was just marked as resolved: https://bugzilla.mozilla.org/show_bug.cgi?id=1542784

Done. Thanks for the information! 🙂

Actually, I had to revert this, because we apparently can't add FF 75 features,  yet.

Thanks!


Following convention for css classes, should we modify the css here to follow BEM?

BEM should really be followed for CSS. (https://css-tricks.com/bem-101/) This ensures a consistant class naming system that would help maintance.
Originally posted by @vandie in https://github.com/nostalgic-css/NES.css/issues/86#issuecomment-445198048

Thanks for your suggestion 🙇
I commented on https://github.com/nostalgic-css/NES.css/issues/86#issuecomment-445212814 📝

Fair enough.


Vite support & example?

Is there an example where we can replace webpack with vite? :)

This is also something that is blocking our migration to Vite as this all relies on CRACO plugins to generate the single-spa parcels.
This would be absolutely awesome! @joeldenning 🙌🏻
Would be super interesting to hear whether you think this is feasible.

I got my Vite+React app working with single-spa by following this example:
https://github.com/stephenwil/vite-single-spa-example/

https://github.com/MilanKovacic/single-spa-vite

Closing due to inactivity. Feel free to reopen the issue if the problem still persists.


Icons in title bar appear wrong

Describe the bug
The icons in the title bar look incorrect
To Reproduce
Steps to reproduce the behavior:

Install Windows 11
Open app RadioGraph
See error

Expected behavior
Icons look correct
Screenshots

Desktop (please complete the following information):

OS: Windows 11
.NET: Net 6

I actually was able to reproduce this by accident on Windows 10, not sure if it's the same root cause.
Steps:

Create an empty WPF window
Set style to UiWindow
In code behind, after InitializeComponent(), add Background.Manager.Apply(BackgroundType.Acrylic, this)

I'm not quite sure where this is happening since I can't step into the DLL code on my current application. My best guess is somewhere around when the handler that gets assigned to OnLoad, some of that logic is stepping on a style with the window chrome or something. No evidence to support that, just a quick guess.
This is using nuget package WPF-UI 1.2.2-prerelease136.


Fix function calling, repetition and local action calling

The local model could be dramatically better. Currently it struggles with repeating forever, getting action names wrong something and not structuring JSON format properly (although usually its just the repeats that kill it)
This could be dramatically improved as an experience through a combination of model and prompt setting optimization, although an advanced researcher may also have a model-side approach.

@lalalune is it resolved? what's the fix?
I am still facing the same issue on my AWS VM


Broken Connection from Homebridge to Home Kit

Describe The Bug:
I'm not a developer by any means, but I believe this started with the update to 18.2 with Apple and specifically likely an update to Home Kit. Everything works as expected from Alexa to Homebridge- I can control accessories in Homebridge. But Apple Home is showing accessories as "No Response" ONLY from this plugin. My other Homebridge plugins are working as expected.
And as I was troubleshooting, I noticed it first started from my apple watch. I could not control devices from siri on my watch, but my phone still worked. This lasted several hours and I was able to restart Homebridge and it fixed the issue temporarily. Then my phone stopped controlling devices through Apple Home consistently. Then finally, "No Response". Additionally, the "this plugin is slowing down homebridge" error has started, but that's new, only when this started yesterday.
To Reproduce:
Use siri or the Apple Home app to try to control devices- no response.
Use Homebridge to control devices- expected response
Expected behavior:
Apple Home/Siri should control all devices from this plugin seamlessly, which was the case up until 12/15/2024
Logs:

[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Hue' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Saturation' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Current Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Hue' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Saturation' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Brightness' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Hue' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Saturation' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Color Temperature' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Current State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] This plugin slows down Homebridge. The read handler for the characteristic 'Lock Target State' was slow to respond! See https://homebridge.io/w/JtMGR for more info.
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Theater Rear_1 - Get power result: OFF
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Theater Rear_1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Nursery Ceiling - Get color temperature result: 2700 K
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom Toilet Light using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Theater Rear_1 - Get brightness result: 0
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom Toilet Light using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Bathroom Toilet Light - Get power result: OFF
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom Toilet Light using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Bathroom Toilet Light - Get brightness result: 0
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom Toilet Light using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Bathroom Toilet Light - Get hue result: 180
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom Toilet Light using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Bathroom Toilet Light - Get saturation result: 100%
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Kitchen using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Bathroom Toilet Light - Get color temperature result: 7000 K
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Kitchen using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Kitchen - Get power result: ON
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Theater Front_2 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Kitchen - Get brightness result: 15
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Theater Front_2 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Theater Front_2 - Get power result: OFF
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Dining Room_Dot temperature using query getTemperatureStates
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Theater Front_2 - Get brightness result: 0
[12/16/2024, 8:46:11 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Dining Room_Dot temperature - Get current temperature result: 18.2 Celsius
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Bathroom using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Bathroom - Get power result: OFF
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Laundry 3 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Bathroom - Get brightness result: 0
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Laundry 3 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Get power result: OFF
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Laundry 3 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Get brightness result: 0
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Laundry 3 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Get hue - InvalidResponse(State not available)
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Service communication error
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Laundry 3 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Get color temperature result: 4000 K
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Nursery Lamp 1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Get saturation - InvalidResponse(State not available)
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Laundry 3 - Service communication error
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Nursery Lamp 1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Nursery Lamp 1 - Get brightness result: 0
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Nursery Lamp 1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Nursery Lamp 1 - Get power result: OFF
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Nursery Lamp 1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Nursery Lamp 1 - Get saturation result: 100%
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Nursery Lamp 1 using query getPowerBrightnessColorColorTempStates
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Nursery Lamp 1 - Get hue result: 120
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Desktop using query getPowerState
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Nursery Lamp 1 - Get color temperature result: 2700 K
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Front Door using query getLockState
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Desktop - Get power result: OFF
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Querying for changes to Front Door using query getLockState
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Front Door - Get lock state result: LOCKED
[12/16/2024, 8:46:12 AM] [homebridge-alexa-smarthome] Front Door - Get lock target state result: 1
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Launched child bridge with PID 727636
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loaded homebridge-alexa-smarthome v2.2.1 child bridge successfully
[12/16/2024, 11:47:34 AM] Loaded 29 cached accessories from cachedAccessories.0E33C15EA6CE.
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Nursery Switch
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Nursery Lamp 2
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Speakers
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Laundry Switch
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Christmas Tree
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Patrick’s Sink
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Dining Room_Switch
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Theater Rear_2
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Laundry 1
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Bathroom shower
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Lisa’s Sink
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Sink Light
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Patrick's Echo temperature
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Bathroom Shower Light
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Laundry 2
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Theater Front_1
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Bathroom Tub
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Nursery Ceiling
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Theater Rear_1
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Bathroom Toilet Light
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Kitchen
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Theater Front_2
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Dining Room_Dot temperature
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Bathroom
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Laundry 3
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Nursery Lamp 1
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Desktop
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Front Door
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Loading accessory from cache: Front Door
[12/16/2024, 11:47:34 AM] Registering platform 'homebridge-nest.Nest'
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Alexa-Remote: cookie was provided
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Alexa-Remote: former registration data exist, try refresh
[12/16/2024, 11:47:34 AM] Loaded 0 cached accessories from cachedAccessories.0E5EAB4EDDAE.
[12/16/2024, 11:47:34 AM] Loaded 1 cached accessories from cachedAccessories.0E416BEFABB9.
[12/16/2024, 11:47:34 AM] [homebridge-alexa-smarthome] Alexa-Cookie: Refresh Token
[12/16/2024, 11:47:34 AM] Homebridge v1.8.5 (HAP v0.12.3) (homebridge-hatch-baby-rest) is running on port 43001.
[12/16/2024, 11:47:34 AM]

Plugin Config:
{
    "excludeDevices": [
        "Family Room",
        "Bedroom",
        "Office",
        "Hue Play 1",
        "Patrick",
        "Lisa",
        "Couch",
        "TV",
        "Living Room Light 1",
        "Living Room Light 2",
        "Outside Lights",
        "Porch Light 1",
        "Porch Light 2",
        "All Hue Lights",
        "Driveway Light",
        "Garage Light",
        "Living room",
        "Hue play 2",
        "Dining Room_Dot temperature",
        "Patrick's Echo temperature",
        "SHIELD",
        "Dresser light",
        "Main Level"
    ],
    "amazonDomain": "amazon.com",
    "language": "en-US",
    "auth": {
        "refreshInterval": 4,
        "proxy": {
            "clientHost": "xxxxxxx",
            "port": xxxxxxx
        }
    },
    "performance": {
        "cacheTTL": 57
    },
    "debug": true,
    "_bridge": {
        "username": "xxxxxxxx",
        "port": xxxxxxx
    },
    "platform": "HomebridgeAlexaSmartHome"
}

Screenshots:

Environment:

Plugin Version: v2.2.1
Homebridge Version:  whatever the latest one is
Node.js Version:  v20.18.0
NPM Version:  no clue
Operating System: Ubuntu Jammy (22.04.5 LTS)

I am experiencing a similar issue as well.

I have a similar issue.  However, I have not received the "this plugin is slowing down Homebridge" message.


Fixed computation of recsize for NC_64BIT_DATA files, fixes #453

I've merged this into the 4.5.0 working branch. I will merge it back upstream into master after I have finished the test, which I'm working on now. This should close at that time.


makefile is not multithreaded make compatible

When I use make -j4 I get a variety of errors indicating that v0100/srclib/c0.asm is used before it is built or is partially built. This is usually because of a missing dependency but I can't figure out where c0 is in the Makefile.
make -j12 shows even more outlandish errors. make -j1 always works.

If you want to (re)compile the library, most of it happens far outside of the makefiles.
The source code files of the library are listed in the various srclib/lc*.txt files.
Each of those lc*.txt files files essentially contains a very long list of arguments for smlrcc.
See Recompiling.

Um... That's how I usually (re)compile it.
I've forgotten about the makefile also doing it but in a somewhat different way and I never tried it multithreaded.

I think, I know what's going on.
The same source files are compiled concurrently into intermediate files of non-unique names.
That is, c0.c is being preprocessed into c0.i that is being compiled into c0.asm that is being assembled into c0.o.
All of these files are written into the same srclib directory.
Gotta figure out how to fix this, somehow give unique paths/names to those intermediate files.


Include basic testing

As a requirement, the project should include some basic testing.
The test approach is:

Using Jest as the test framework
Using React Testing Library as the helper library to test React components

Consider the following test plan which will test React presentation components:

Test the token form used to submit personal access token to the system
Test the issue list where all received issues should be listed
Other basic tests

If time permits, consider adding tests for Redux.

Added the following tests:

[ ] Test for root component App
[ ] Tests for dumb components: TokenForm, IssueList
[ ] Tests for smart components: TokenPage
[ ] Tests for redux actions: issueActions, tokenActions
[ ] Tests for testing redux thunk in issueActions
[ ] Tests for redux reducers: issueReducer
[ ] Integration tests for redux store

Basic testing has been included in the project and merged with the master.

All tests are passed locally. Going forward, when working on new branches, the tests related to the changes should be updated as appropriate and if new features are added, new tests should be created at the same time in the feature branches.


test: Adding Cypress integration testcase for Sensitive input

Description
Please include a brief summary of the change and include the relevant issue(s).
Closes #(issue)
What change does this PR introduce?
Please select the relevant option(s).

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update (changes to docs/code comments)

What is the proposed approach?
Please give a short overview/explanation on the approach taken to resolve the issue(s).
Checklist:

[ ] The commit message follows our adopted guidelines
[ ] Testing has been done for the change(s) added (for bug fixes/features)
[ ] Relevant comments/docs have been added/updated (for bug fixes/features)

Images:

sensitive text

Markup language

LGTM! On a side note, the current integration test approach is not sustainable, reason being we're only relying on a single configuration of settings for testing. Ideally, we should have multiple instances of the chatbot with different configurations to cover more grounds (e.g. markup language should not work if dangerouslySetInnerHtml is false). That's an issue for another time though, thanks for working on this 😊

I agree! , I also had this thought. I was not able to figure out a approach to pass different configurations. using state to load different configuration is one way.

LGTM! On a side note, the current integration test approach is not sustainable, reason being we're only relying on a single configuration of settings for testing. Ideally, we should have multiple instances of the chatbot with different configurations to cover more grounds (e.g. markup language should not work if dangerouslySetInnerHtml is false). That's an issue for another time though, thanks for working on this 😊

I agree! , I also had this thought. I was not able to figure out a approach to pass different configurations. using state to load different configuration is one way.

This can likely be broken down into a few issues:

Create toggle buttons to switch between different chatbot configurations
Create issue for different chatbot configurations (can be 1 issue per config e.g. all settings enabled, all settings disabled etc)

This is not pressing but if you are keen, we can talk more on discord 🙂

LGTM! On a side note, the current integration test approach is not sustainable, reason being we're only relying on a single configuration of settings for testing. Ideally, we should have multiple instances of the chatbot with different configurations to cover more grounds (e.g. markup language should not work if dangerouslySetInnerHtml is false). That's an issue for another time though, thanks for working on this 😊

I agree! , I also had this thought. I was not able to figure out a approach to pass different configurations. using state to load different configuration is one way.

This can likely be broken down into a few issues:

Create toggle buttons to switch between different chatbot configurations
Create issue for different chatbot configurations (can be 1 issue per config e.g. all settings enabled, all settings disabled etc)

This is not pressing but if you are keen, we can talk more on discord 🙂

Yes we can do that.


15 minutes ago - kittyxkum Leaked - kittyxkum Leak Fansly and OF (tutblw)

👉👉👉 kittyxkum Files - CLICK HERE
I’m thrilled to share my world with you and provide exclusive content that you won’t find anywhere else. As a creative individual, I love expressing myself through various forms of art, and my space is an extension of that passion. Here, I aim to build a vibrant community where authenticity and connection thrive.
On my account, you can expect a diverse range of content that reflects my personality and interests. From stunning media showcasing my unique style to behind-the-scenes glimpses of my daily life, there’s something for everyone.
One of the highlights of my media is the personal interaction I offer to my supporters. I believe in fostering genuine connections, so I’m always eager to engage with you through direct messages and comments. Your thoughts and feedback matter to me, and I often take your suggestions into account for future media.


line graph of proportions is wrong

for tagging effort analysis, figure out where discrepancies in tagging locations/ prportions above lisbon originates.  Script = taggingeffort.R

fixed; see TaggingEffortAnalysis.rmd for workup


Add feed from Newspeak House events list

Is there a way to add events from this feed?
https://www.nwspk.com/events

@eghale it doesn't look like they have an api so it's unlikely we can pull the data in programatically, if you like you can enter them via the admin dashboard


fix(input): asterisk color when not focused

Currently the asterisk is still using the warn color when the input is not focused anymore.

Per Material Specs the asterisk should be only red when the input is focused (Specs Video)

Focused
Blurred

Fixes #1395.

LGTM


Small doc edits - first attempt

I made some small tweaks, and am trying this pull request thing out.

I think this was merged already.


Fix sending only text email.

Hi
I found that there is a problem with sending emails that only have text format templates (foo.text.erb).
Previously it was sending pure text as html and mandril converted this "html" into text. After those transformations all formatting was gone.
PR fixes this.

@piotrze fix the tests, please

@kshnurov Done. Sorry I didn't notice rubocops rules run only rake spec

Not sure why it failed at mime-types-data gem for ruby 1.9.3
https://travis-ci.org/spovich/mandrill_dm/jobs/118276282

Seems to be a travis-ci issue http://stackoverflow.com/questions/33855550/travis-ci-fails-to-deploy-to-gihub-mime-types-data-requires-ruby-version-2
@spovich could you, please, look into it? I don't have enough time for that right now.

@kshnurov I'll have a look this weekend.  Buried right now.

@kshnurov @spovich Fixed that by adding dependency to mime-type in specific version.
Inspired by https://github.com/sgruhier/foundation_rails_helper/pull/117/files

@piotrze that's a bad idea, old version is needed only for travis ci and ruby 1.9.3, not for all users.

@kshnurov Since ruby 1.9.3 has been EOL for more than a year now, I've removed it from .travis.yml here in my PR to cleanup rake tasks.

Good! @piotrze you can remove the last commit.

@kshnurov are you ok with this PR?  Looks fine to me.


Feature/upgrade v2 14 1

Update our mustache implementation to align with upstream master.
*This is a precursor to updating the MySql docker image

No way this should be approved.😂😂😂😂
On Thu, Aug 25, 2022 at 5:02 PM, Victor Shih @.***> wrote:

@vshih approved this pull request.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh snap, a ghost of github past!!
--
Victor Shih
@.***
On Thu, Aug 25, 2022, 5:06 PM Jay Pedersen @.***> wrote:

No way this should be approved.😂😂😂😂
On Thu, Aug 25, 2022 at 5:02 PM, Victor Shih @.***> wrote:

@vshih approved this pull request.
—
Reply to this email directly, view it on GitHub,
or unsubscribe.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/myersmediagroup/mustache.php/pull/3#issuecomment-1227871536,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMZJQYOTWLEHGFQWP5JVLV3AC6RANCNFSM57U2Y4PA
.
You are receiving this because you were mentioned.Message ID:
@.***>


dask-expr: DataFrame.map_partitions no longer takes a token keyword

Describe the issue:
The map_partitions method of the dd.DataFrame collection no longer accepts the token keyword in the dask-expr version.
It's certainly not a critical keyword (and with dask-expr you could also create a custom expr subclass instead of using map_partitions if you want to have more fine grained control, I suppose), but I think keep supporting this could be 1) nice for backward compatibility, and 2) useful inspectability of the eventual graph (just removing the keyword gives a generic "mappartitions" key in the task graph).
Minimal Complete Verifiable Example:
import dask
dask.config.set({'dataframe.query-planning': True})

import pandas as pd
import dask.dataframe as dd

df = pd.DataFrame({"a": np.arange(100), "b": np.random.randn(100)})
ddf = dd.from_pandas(df, npartitions=2)
ddf2 = ddf.map_partitions(lambda df: df, meta=ddf._meta, token="test")
ddf2.compute()

gives
...
File [~/scipy/repos/dask-expr/dask_expr/_expr.py:3513](http://localhost:8888/lab/tree/repos/dask-expr/dask_expr/_expr.py#line=3512), in Fused._execute_task(graph, name, *deps)
   3511 for i, dep in enumerate(deps):
   3512     graph["_" + str(i)] = dep
-> 3513 return dask.core.get(graph, name)

File [~/scipy/repos/dask/dask/dataframe/core.py:7387](http://localhost:8888/lab/tree/repos/dask/dask/dataframe/core.py#line=7386), in apply_and_enforce(*args, **kwargs)
   7385 func = kwargs.pop("_func")
   7386 meta = kwargs.pop("_meta")
-> 7387 df = func(*args, **kwargs)
   7388 if is_dataframe_like(df) or is_series_like(df) or is_index_like(df):
   7389     if not len(df):

TypeError: <lambda>() got an unexpected keyword argument 'token'

Environment:

Dask version: 2024.2.1+8.g5abd9daa (dask-expr 0.5.3+6.gdd3c54d)

We can add this back in, but we would still change the behaviour slightly if we do this:
currently tokenisation ignores the func if token is given, that's something we would want to change in dask-expr.


Add custom token to community contributions workflow

The pause-community-contributions workflow makes a call to the
GitHub API to check if the person contributing is a member of
the organization.
However, this call currently fails if the contributor has set their
membership to 'private'.
This is because the default token provided for GitHub Actions only
has permissions for the repository, not for the organization. With
this token, we're not allowed to see private memberships.
We've created a custom, org-wide secret containing a personal token
that has permissions to read organization membership.
Unfortunately the secret cannot be accessed directly by the shared
workflow, it has to be passed in.
We updated the shared workflow to use the token, if it is provided,
and this PR updates the workflow in this repo to pass the secret.
Until this is merged, contributions from people with private membership
in the Exercism organization will be automatically closed.
Note that this PR also removes the workflow_dispatch which fails if
you try to use it.

I forgot I had tested the original workflow by setting my membership to private :)


Add is_writeable check before deleting a directory

Addresses #38

@Gummibeer you mentioned that this fix doesn't solve the underlying problem. Could you give some more context?

@brendt my answer was just related to my issue, which wasn't the /tmp directory used by glide but the medialibrary temp directory - so the exception mentioned a lot of times in https://github.com/spatie/laravel-medialibrary/issues/887 should be solved here.
Even if I don't like the strategy to delete the whole directory, even if it's empty, cause the directory is, in every time, the php tmp directory sys_get_temp_dir(), delete the whole directory isn't the job of this package and could also produce other problems.

@brendt You cant just delete /tmp even if its writable because of some reason.
https://www.tldp.org/LDP/Linux-Filesystem-Hierarchy/html/tmp.html

Good Link, that's what I meant. In addition to it: why do you want to delete the directory? This package doesn't create it. So even if it's not tmp it's a directory you don't know what it's for.

You cant just delete /tmp even if its writable because of some reason.

That's a fair point. I looked further into why $conversionResultDirectory is /tmp in the first place. My understanding is that it should be /tmp/<conversion directory>.
Is anyone able to reproduce the steps required to get plain /tmp as the path?
Another "fix" I could add is the following
if ($conversionResultDirectory !== sys_get_temp_dir()) {}

But that's also still a monkey patch, I'd rather see the plain /tmp never appear again, though I'm unable to pinpoint why it happens at this moment.

@brendt if you want to have another directory you have to add it to the full path.
https://github.com/spatie/image/blob/088540509d8a6c4c2fe786aeb84c8bce3872acc5/src/GlideConversion.php#L50-L53
And everything else you add there depends on the glide configuration itself - this is what makeImage returns:
https://github.com/thephpleague/glide/blob/8077f529a07ded3eed6c5dcf7f688249b626ddf3/src/Server.php#L263-L290
So to be save I would suggest to add any new directory there and it's fine.

Can you merge it at least until you find the problem why its trying to delete /tmp directory.

@ammonkc found the problem: https://github.com/spatie/image/issues/38#issuecomment-381296285
We'll be looking at a permanent solution tomorrow.


Show how to divide a form into tabs

Just realized that there are some additional requirements in https://github.com/vaadin/cookbook/issues/9. Will revise the implementation.

Example updated to have a static button bar and show validation errors in the tabs


Display buttons and loading functions

Added messages and delay on success/error of button.
Added handlers for onSuccess/onError.
Added in examples

Coverage decreased (-87.6%) to 12.389% when pulling 46d0bf5b92e3e16109853ccc9df0f69b98e1434b on NewDark90:Display_Buttons_and_Loading_Functions into 3cd88363ccc4b99d36838b97d465e2d98ad82491 on johannesjo:master.

The failing unit tests are actually because of some issue with karma itself. I pushed a fix to the master branch (which hopefully will fix this issue. Tests are running atm). It would be good if you could execute
rebase origin/master

from your feature branch to have the latest additions

Any update on this one?

I have the functional code if you want it. You should be able to pull from here if you need it. https://github.com/NewDark90/angular-promise-buttons

@NewDark90 It would be really cool, if you could rebase the master branch and commit your changes once again. It should be quite easy to do: https://robots.thoughtbot.com/keeping-a-github-fork-updated
I would implement those changes myself, but then you would loose credit for them.

I appreciate it. I'll give it a go today.
And if I can't figure it out, I don't care that much if you implement the branch yourself.
Thanks.

I successfully got all of your remote changes, so I have that going.

Pushed all of those changes to my github repo, so there's that too.
Trying to repull request that branch, and it isn't cooperating. Probably missing something.

Can't you simply unrevert the branch? Is that a naive question? :)

Don't worry, it's sometimes hard to wrap your head around git :)
There are two possible solutions:

You delete your fork, create a new one and introduce the changes once again manually (the changes.
Looking at your screenshot of your local history it  looks like to me that your changes are gone from your local repository, though I'm not sure how this happend. You can try to roll back to the point when you're commits were still there via git reflog and git reset --hard (probalby just before
See http://stackoverflow.com/questions/134882/undoing-a-git-rebase
and try to do the synch once again: https://help.github.com/articles/syncing-a-fork/

That's probably best to make a new branch anyway. I don't know what's changed in the last several commits, and I should at least make sure that what I did doesn't get in the way instead of blindly commiting some relatively old stuff.
I appreciate the help. 👍


System error 1396 has occurred. The target account name is incorrect.

I received the error below when trying to map the drive on an on-premises device using "net use" cmd. Couldn't find this error code from the troubleshooting page.
"System error 1396 has occurred.
The target account name is incorrect."

"Join-AzStorageAccountForAuth"  ran successfully with Provisioning State shown as Succeeded.
The Computer Account in local AD was already created successfully.
"Get-AzStorageAccountKey -ListKerbKey | ft KeyName" also returned 2 kerb keys.
The RBAC Storage permissions were also assigned to the corresponding Azure AD accounts to access the File Share.

Any idea why "System error 1396" occurred?

Hi @hugohhk - Let us know if you were following a specific MS Doc and needed any assistance.

Yes. I was planning to post the question under this Doc:
https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-active-directory-enable#regional-availability
Sorry for my wrong post. I have already created a new post under that MS Doc.
Thanks!


fix stop when there is not a server

sometimes when you are developing you brake the code and you should allow to stop your component even it has not been started

Thanks!

0.9.0-SNAPSHOT released with your change.


StorageGRID overview dashboard metadata panel missing query

Thanks to Mamoep on Discord for raising and providing a fix!
There are two issues:

The 2nd sum in the percentage query (C) for Panel "Data space usage breakdown" is missing "cluster" to get matching labels
The Metadata panel is missing several columns

Verified on 3ffa2eb5


PLAT-80079: Remove useless code and cleanup code in VirtualList and Scroller

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
We need to cleanup VirtualList and Scroller because we missed some patches and applied uncompleted patches in them.
Resolution

Remove unused findSpottableItemWithPositionInExtent()
Apply the patch for Scrollable in ENYO-5957 to ScrollableNative
Cleanup onAcceleratedKeyDown parameters
Reduce calling `getNextIndex() in VirtualList once
Focus an item immediately when an app mounted and called the cbScrollTo in VirtualList

Additional Considerations

Cleanup Scrollable and ScrollableNative code.
Cleanup VirtualList code.

Links
PLAT-80079
Comments

LGTM


Add "christmas" to inflector ambiguous noun

This PR add the word "christmas" to the ambiguous words of the inflector.

Thanks.


Unknown interface enp0s8

Issue Type

Bug Report / Support Request

Your Environment
Vagrant 2.2.0
VirtualBox 5.2.20r125813
ansible 2.7.0
  config file = None
  configured module search path = [u'/Users/michel/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /Library/Python/2.7/site-packages/ansible
  executable location = /usr/local/bin/ansible
  python version = 2.7.10 (default, Aug 17 2018, 17:41:52) [GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.0.42)]

Your OS

macOS (Mojave 10.14.1)

Full console output
https://gist.github.com/Michel-Settembrino/978b3bb5fa65417774aaa56274d7bc05
Summary
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown 'enp0s8' || true
/sbin/ip addr flush dev 'enp0s8'
# Remove any previous network modifications from the interfaces file
sed -e '/^#VAGRANT-BEGIN/,$ d' /etc/network/interfaces > /tmp/vagrant-network-interfaces.pre
sed -ne '/^#VAGRANT-END/,$ p' /etc/network/interfaces | tac | sed -e '/^#VAGRANT-END/,$ d' | tac > /tmp/vagrant-network-interfaces.post
cat \
  /tmp/vagrant-network-interfaces.pre \
  /tmp/vagrant-network-entry \
  /tmp/vagrant-network-interfaces.post \
  > /etc/network/interfaces
rm -f /tmp/vagrant-network-interfaces.pre
rm -f /tmp/vagrant-network-entry
rm -f /tmp/vagrant-network-interfaces.post

/sbin/ifup 'enp0s8'

Stdout from the command:

Failed to bring up enp0s8.

Stderr from the command:

Unknown interface enp0s8
run-parts: /etc/network/if-up.d/postfix exited with return code 75

The problem could also be related to the VirtualBox version in use. I think my boxes were most recently built with VirtualBox 5.2.20; it could be an issue with the guest addition installation for 5.2.22.

Actually, they were built with 5.2.22. Can you upgrade VirtualBox on your computer to 5.2.22 and then try doing a new vagrant up again?

I upgraded VirtualBox but still same issue.

I was using version 2.2.0 of Vagrant. So I upgraded to the latest version 2.2.2
Still same issue.
And now, I have some warning:

Vagrant has detected a configuration issue which exposes a
vulnerability with the installed version of VirtualBox. The
current guest is configured to use an E1000 NIC type for a
network adapter which is vulnerable in this version of VirtualBox.
Ensure the guest is trusted to use this configuration or update
the NIC type using one of the methods below:
https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type

For that warning, see https://github.com/geerlingguy/drupal-vm/issues/1869
And I'm still not sure what's causing that enp0s8 issue... can you post your full config.yml file? Are you using a different base box?

Yes for sure.
config.txt
No I'm using the default base box.
vagrant box list
geerlingguy/drupal-vm  (virtualbox, 1.0.2)
geerlingguy/ubuntu1604 (virtualbox, 1.2.2)
geerlingguy/ubuntu1604 (virtualbox, 1.2.3)
geerlingguy/ubuntu1604 (virtualbox, 1.2.4)
vccw-team/xenial64     (virtualbox, 20180107)

What is very strange is that this exact same config with an older version of Drupal-vm works! See https://github.com/geerlingguy/drupal-vm/issues/1866#issuecomment-443243770

Can you try running vagrant up --debug and see the exact commands being run which seem to be failing?

So it sounds like this is definitely vagrant or VirtualBox-related, as vagrant up/provision is not good, but after reloading it is working... I would suggest asking further questions in the Vagrant project issue queue, as I don't know how much more I could help as I've only seen this error a couple times (and never on my own computer) :(


Buy Failed Error

Have gotten a consistent "XXXX buy failed" for most items that I am searching for. Rarely get a buy. Is it an error?

It is because some other user bought that card or out bided you. One thing you can do is to increase the max purchase per request to 7 or 10 , to bid on more items to increase the chances of winning more card.
But just be careful as increase the max purchase might result in soft ban.


Room List horizonal scrolling is borderline unusable

Between the room list constantly (and I honestly can't tell how) rearranging itself, and having to scroll horizontally on a portrait-oriented screen, I can officially say that the room list is very, very, very frustrating to use and is ultimately a very confusing UX choice on Android.
Tabs, collapsible labels, almost anything makes more sense to me.
It's bad enough that I've dedicated a page of my homescreen to room buttons that I can rearrange at will... that won't move around.

Both the people list and the room list should be much more compact, ideally with vertical scrolling only.

When I enter a room and return to the list, I expect the scroll to be the same; right now the horizontal scroll is reset to 0 upon return.


Segfault on v action for any issue in Sprints layout

Describe the bug
A crash on the v action in Sprints layout for any issue:
┘panic: runtime error: invalid memory address or nil pointer dereference                                                            ║                                                                                ║
 [signal SIGSEGV: segmentation violation code=0x2 addr=0xa0 pc=0x102d7acd4]                                                                                ║
                                                             ║                                                                                ║
                                                             ║             goroutine 29 [running]:                                                                                ║
                                                             ║                                    github.com/ankitpokhrel/jira-cli/internal/view.Issue.header({{0x14000b4e828, 0x17}, 0x0, {0x0, 0x0, 0x0, {0x0, 0x0, 0x0}, 0x0, ...}, ...})                                       ║                                                                                ║
                      	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/internal/view/issue.go:203 +0x64                                                                                ║
                                                             ║                                                      github.com/ankitpokhrel/jira-cli/internal/view.Issue.fragments({{0x14000b4e828, 0x17}, 0x0, {0x0, 0x0, 0x0, {0x0, 0x0, 0x0}, 0x0, ...}, ...})                  ║                                                                                ║
                                           	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/internal/view/issue.go:127 +0x98                                                                         ║
                                                             ║                                                                              github.com/ankitpokhrel/jira-cli/internal/view.Issue.RenderedOut({{0x14000b4e828, 0x17}, 0x0, {0x0, 0x0, 0x0, {0x0, 0x0, 0x0}, 0x0, ...}, ...}, ...)                                                                                ║
                                                             ║            	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/internal/view/issue.go:76 +0xac                                          ║
                                                             ║                                                                                github.com/ankitpokhrel/jira-cli/internal/view.(*SprintList).Render.func1.2({0x10306db80?, 0x0?})       ║                                                                                ║
                                                      	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/internal/view/sprint.go:66 +0xb4                                                                 ║
                                                             ║                                                                                github.com/ankitpokhrel/jira-cli/pkg/tui.(*Preview).initContents.func1.2.1(0x140001b6690, 0x2, 0x28?, 0x14000a60f50?)          ║                                                                                ║
                                                   	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/pkg/tui/preview.go:255 +0xe4                                                                     ║
                                                             ║                                                                                github.com/ankitpokhrel/jira-cli/pkg/tui.(*Preview).initContents.func1.2()                                                         ║                                                                                ║
    	/Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/pkg/tui/preview.go:259 +0x30═════════════════════════════════════════════════════════════════════════════════════════════════════════════════════╝
 Showing 20 results from board "XXX Kanban" of project "YYY"                       created by github.com/ankitpokhrel/jira-cli/pkg/tui.(*Preview).initContents.func1
                                                                                /Users/ankitpokhrel/go/src/github.com/ankitpokhrel/jira-cli/pkg/tui/preview.go:244 +0x264

Please provide following details

JiraCLI Version:

  (Version="1.3.0", GitCommit="ed84fe74f68ba1b2cf0504a931ca09a03b2c9fed", CommitDate="2023-01-02T09:59:32+00:00", GoVersion="go1.19.4", Compiler="gc", Platform="darwin/arm64")

Happens also on the latest git version: https://github.com/ankitpokhrel/jira-cli/commit/eef7ae96c20a26f16b26f178c07ebe7df11511ab

Are you using Jira cloud or on-premise jira server?

SERVER INFO
-----------

Version: 	 8.20.6
Build Number: 	 820006
Deployment Type: Server
Default Locale:

What operating system are you using? Also mention version.macOS 13.2 ARM64

What terminal are you using? Also mention version. iTerm 2 Build 3.4.19

To Reproduce
Steps to reproduce the behavior:

jira sprint list
Select any sprint and issue, then press v
See error

Expected behavior
No crash

That's strange! It looks like the API is not returning Assignee field. I cannot reproduce this behavior in 8.22.2, are you able to add assignee from the UI?
Also, could you please check what response you get with this cURL request and what you get in the Assignee field?
$ curl --request GET \
  --url 'https://<host>/rest/api/2/issue/<issue-key>' \
  --user "<user>:$JIRA_API_TOKEN" \
  --header 'Accept: application/json'

@ankitpokhrel indeed, in the JSON returned from this curl request there is no 'Assignee' field at all, not even null-valued one.

@XVilka This looks something specific to your installation, are you able to set assignee from the UI? Also wondering if the problem is only with that particular field or other fields are missing as well? (Apologies for late response)

@ankitpokhrel yes, recently upgraded Jira version to 9.4.4 and also pulled latest code from git, the issue is still here. I am able to set assignee from the UI.


[Question] Can I create new items on MWS with this library?

First I'd like to thank you for making this nice library.
My question is does this library allows creating new items on MWS?!
I just created a store, I want to be able to import products from another system on my MWS store, is that possible. If yes can you please link me to the test or class responsible for that. With any kind of advice.
Best,

Yes it can, though doing so is not straight-forward. See #59 for more information.

Seeing as it has been over a week, I am going to assume that the information has answered your question.

@Peardian yep I was able to do it, Thanks.


Add .aoc link command

Description
This adds functionality to the Advent of Code cog for users to "link" their Discord Account with their Advent of Code name on the leaderboard. The cog doesn't explicitly make use of it, but it is necessary to exist and be functional for something I want to do.
This is implemented with a Redis Cache. A user can link their discord account with a name they specify and it's stored as a key-value pair with the Discord ID as the key.
There is no validation that the name they are entering is on our leaderboard. This is an intentional decision as I don't want to rely on the leaderboard cooldown for a user to successfully run this command. If a user fucks up their name, that's on them. It does check if the name they are trying to link is already in the cache and provides the appropriate response.
To test this command you can run the following two commands in different scenarios:
.aoc link
.aoc link aocnamehere
Relevant Issues
Closes #958

Huh, I left a overall message which strangely did not get saved.
I was mentioned that it looks pretty good, but I'd like to see an unlink command. In addition, a way to unlink from a moderator view in case someone adds an account they cannot control. I also do not see an admin/mod or event lead command to be able to force an unlink.


EKF: don't accept GPS data without a 3D lock

This fixes a bug that allows the EKF to try using GPS data when there is no longer a 3D fix. This prevents the timeout reversion back to non-GPS operation that is supposed to occur after 10 seconds of no GPS lock

Checks fail


Static Channel Backup: Backup to local drive and timestamping

see https://github.com/rootzoll/raspiblitz/pull/1305

[ ] edit readme
[ ] change to work with device id
[ ] mount local backup device on bootstrap

Restested and good to go. Will be part of v1.6 final release. Closing issue.


Slow indexing on default import functionality

When we want update the category meta description with 1600 rows. This takes 1.5 hours to process due to slow indexing. Indexing is not always needed as we only update the meta description in this case.
The indexer does do some queries that are very slow (25-40 seconds) and locks the table
For example:
# Query_time: 24.789021  Lock_time: 24.782066  Rows_sent: 0  Rows_examined: 51  Rows_affected: 0  Bytes_sent: 54
SET timestamp=1723713533;
UPDATE `category`  as parent
                LEFT JOIN
                (
                    SELECT parent_id, count(id) total
                    FROM   `category`
                    WHERE parent_id in ('^A��~\08sеaV���/B', '^A��|�^Ps!�3^V�^L�^^O', '^A��~��x���X�^R��9', '^A��~�.~�����^?(2�', '^A��~�1u���치^N�7', '^A��^?^D%y\n��˰^^Ĳ�', '^A��^?^L�zͯD^P�>
                    AND version_id = '^O�^\��jK¾K��u,4%'
                    GROUP BY parent_id
                ) child ON parent.id = child.parent_id
            SET parent.child_count = IFNULL(child.total, 0)
            WHERE parent.id IN ('^A��~\08sеaV���/B', '^A��|�^Ps!�3^V�^L�^^O', '^A��~��x���X�^R��9', '^A��~�.~�����^?(2�', '^A��~�1u���치^N�7', '^A��^?^D%y\n��˰^^Ĳ�', '^A��^?^L�zͯD^P�ױA^', '^>
            AND parent.version_id = '^O�^\��jK¾K��u,4%';

We process the queue with 3 message consumers
Is it possible to make it faster? Only index the categories that are updated. Only index when certain fields are updated that needs an index.
Other idea to have a toggle button to decide if you want to run the indexer on import

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37734.
[created from NEXT-37734, comment 487328]


feat: 4041 - removed redundant and misplaced "user lists"

What

There was an access to user lists from the user preferences.
Now that we have a fast access to all lists, including user lists, we can remove that previous access in order to avoid redundancy and confusion.

Screenshot
There used to be a "My lists" entry there, now redundant.

Part of

#4041

Files
Deleted files:

all_user_product_list_page.dart
user_preferences_user_lists.dart

Impacted file:

user_preferences_page.dart: removed the access to "user lists", who was misplaced here and is now redundant with the latest "lists" tab

Codecov Report

Merging #4303 (9667799) into develop (296a0d2) will decrease coverage by 0.03%.
The diff coverage is 1.69%.

@@             Coverage Diff             @@
##           develop    #4303      +/-   ##
===========================================
- Coverage    10.82%   10.80%   -0.03%
===========================================
  Files          288      287       -1
  Lines        14264    14202      -62
===========================================
- Hits          1544     1534      -10
+ Misses       12720    12668      -52

Impacted Files
Coverage Δ

...ages/smooth_app/lib/database/dao_product_list.dart
4.61% <0.00%> (-0.23%)
:arrow_down:

...p/lib/pages/preferences/user_preferences_page.dart
93.58% <ø> (-0.32%)
:arrow_down:

...pp/lib/pages/product/common/product_list_page.dart
0.00% <0.00%> (ø)

...pages/product/common/product_list_popup_items.dart
0.00% <0.00%> (ø)

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (ø)

...app/lib/pages/product_list_user_dialog_helper.dart
0.00% <0.00%> (ø)

...es/smooth_app/lib/pages/all_product_list_page.dart
2.77% <2.77%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thank you @g123k for your review!

Have you just checked that translations from the old screen are removed?

No I haven't, it's supposedly done in #3856 (and I have never understood how the conflicts are dealt with between flutter and crowdin).


Cannot generate dependency in failure zip for Xerces

There are several no-sources files in the failure zip. Note there are no -M switches in the compilation database.
Failed to generate dependency list for /usr/lib/ccache/c++ -E -M -MT __dummy  -DHAVE_CONFIG_H=1 -DXERCES_BUILDING_LIBRARY=1 -D_FILE_OFFSET_BITS=64 -D_THREAD_SAFE=1 -Dxerces_c_EXPORTS -I. -I../src -Isrc -isystem /usr/include/x86_64-linux-gnu   -Wall -Wcast-align -Wcast-qual -Wctor-dtor-privacy -Wextra -Wformat=2 -Wmissing-declarations -Wno-long-long -Woverlength-strings -Woverloaded-virtual -Wredundant-decls -Wreorder -Wswitch-default -Wunused-variable -Wwrite-strings -Wno-variadic-macros -fstrict-aliasing -msse2 -fPIC   -pthread -std=gnu++14 -c /home/egbomrt/WORK/CodeCheckerProjects/xerces-c-3.2.0/src/xercesc/util/XMLString.cpp

The original output was: c++: error: : No such file or directory
c++: error: : No such file or directory
c++: error: : No such file or directory
c++: error: : No such file or directory
c++: error: : No such file or directory

-E -M -MT __dummy are used by the dependency generator to tell the compiler to actually create a dependency list. (This is valid for both Clang and GCC. -E turns only the preprocessor on, -M enables the creation of a Makefile dependency list to the output, and -MT sets the target name to something we can always recognise.) If there would be -M options in the original compilation commands, they are removed and overridden by the dependency generate options.
Does this issue persist if you are using the compilers natively, and not through ccache? I recall we had issues with the environment and the invocation if ccache was in the loop...

I replaced /usr/lib/ccache/c++ to g++ in the compile db, but the issue is still here.

The strange thing is if I copy the command from the logs and cd into the directory given in the compile entry, then it gives the list of the dependent files.

Found the root cause. there are empty arguments in the executed command, which are handled by the compiler as positional arguments, i.e. it tries to find files with the name which is equal to the empty string.
Hence the strange errors c++: error: : No such file or directory.
This is how the command looks like:
[u'g++', '-E', '-M', '-MT', '__dummy', u'', u'-DHAVE_CONFIG_H=1', u'-DXERCES_BUILDING_LIBRARY=1', u'-D_FILE_OFFSET_BITS=64', u'-D_THREAD_SAFE=1', u'-Dxerces_c_EXPORTS', u'-I.', u'-I../src', u'-Isrc', u'-isystem', u'/usr/include/x86_64-linux-gnu', u'', u'', u'-Wall', u'-Wcast-align', u'-Wcast-qual', u'-Wctor-dtor-privacy', u'-Wextra', u'-Wformat=2', u'-Wmissing-declarations', u'-Wno-long-long', u'-Woverlength-strings', u'-Woverloaded-virtual', u'-Wredundant-decls', u'-Wreorder', u'-Wswitch-default', u'-Wunused-variable', u'-Wwrite-strings', u'-Wno-variadic-macros', u'-fstrict-aliasing', u'-msse2', u'-fPIC', u'', u'', u'-pthread', u'-std=gnu++14', u'-c', u'/home/egbomrt/WORK/CodeCheckerProjects/xerces-c-3.2.0/src/xercesc/util/XMLString.cpp']


Performance test

using Fargate with specific specs

Blocked by https://github.com/api3dao/signed-api/issues/9

Use Nodary pool for the test, not the Nodary API directly.

Also blocked by https://github.com/api3dao/signed-api/issues/84

Use Nodary pool for the test, not the Nodary API directly.

Revisiting this now, I think there was a misunderstanding when we talked about it on the call. We were talking about what data provider API to use. I suggested using Nodary for that. The Nodary pool is basically a signed API.
After https://github.com/api3dao/signed-api/pull/122 is merged I propose doing this:

Deploy Signed API
Deploy Nodary API pusher with quite heavy configuration

The idea is that the pusher doesn't care if the API is a signed API or a regular API, so you can use the Nodary pool as if it's an API. Spamming the actual Nodary API shouldn't be a problem but I don't see why we would risk it.


6/11/2020 Publish

Docs Build status updates of commit 93f7e12:
:clock10: Full build: the average full build time is 7 min(s) 34 sec(s), this is based on the last 646 build(s) for this repository.

Docs Build status updates of commit 93f7e12:
:warning: Validation status: warnings

File
Status
Preview URL
Details

latest/docs-ref-autogen/TOC.yml
:warning:Warning
View (azure-cli-latest)
Details

2017-03-09-profile/docs-ref-autogen/TOC.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/healthcareapis/healthcareapis.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/healthcareapis/healthcareapis/operation-result.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/healthcareapis/healthcareapis/service.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/healthcareapis/index.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2018-03-01-hybrid/docs-ref-autogen/TOC.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis/operation-result.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis/service.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/index.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2019-03-01-hybrid/docs-ref-autogen/TOC.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis/operation-result.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/healthcareapis/service.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/healthcareapis/index.yml
:white_check_mark:Succeeded

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

latest/docs-ref-autogen/acr/scope-map.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/acr/token.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ams/asset.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/healthcareapis/healthcareapis.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/healthcareapis/healthcareapis/operation-result.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/healthcareapis/healthcareapis/service.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/healthcareapis/index.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/TOC.yml

[Warning-EmptyTocItemName] TOC item () with empty name found. Missing a name?
[Warning-EmptyTocItemName] TOC item () with empty name found. Missing a name?

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


os/glog: Does GoFrame support for logging fields?

What do you want to ask?
We are using logrus and logging like this:
log.Info("A simple log")
log.WithFields(log.Fields{
  "event": event,
  "user_id": userId,
}).Info("A log with fields")

And it produce json logs like below:
{
  "log": "A simple log"
}

{
  "event": "event",
  "user_id": "user_id",
  "log": "A log with fields"
}

So we can use the fields to filter our logs such as:
select log
where  user_id = 1 and event = "event"

Do GoFrame support this? Or how can I implement something like this in GoFrame?

The point is the log message is a field in JSON, both logging in a simple way and logging with fields.
We don't make the simple logging being so complex.

@RyoJerryYu Hello, we does not support WithFields like logrus, but you can try function SetPrefix or submit a PR adding Fields/SetFields function to support this.

@RyoJerryYu Hello, we does not support WithFields like logrus, but you can try function SetPrefix or submit a PR adding Fields/SetFields function to support this.

Thank you for answering. But I don't seem to have made my real needs clear.
What we really want is the ability of structured logging, and the simple logging should remain simple and work well with structured logging. We do not care how the codes look like. The logrus-like WithFields method is not important at all.
In fact, we all know there's a bunch of libraries that support structured logging in different styles.
// zap styles
sugar.Infow("failed to fetch URL",
  // Structured context as loosely typed key-value pairs.
  "url", url,
  "attempt", 3,
  "backoff", time.Second,
)

logger.Info("failed to fetch URL",
  // Structured context as strongly typed Field values.
  zap.String("url", url),
  zap.Int("attempt", 3),
  zap.Duration("backoff", time.Second),
)

// zerolog styles
log.Debug().
        Str("Scale", "833 cents").
        Float64("Interval", 833.09).
        Msg("Fibonacci is everywhere")

Obviously we can easily convert to each style by adding a simple adapter layer.
But it seems glog does not provide any method to log with fields? We tried to log with g.Map , but the logs it produced were not what we want. I found a Chinese comment here also complaining about this: https://goframe.org/pages/viewpage.action?pageId=1114186

BTW, we finally found that it seems could be implemented by providing a self-defined Handler, then log fields in zap style. However, since HandlerInput do not provide any support for custom fields, we can only parse the fields from HandlerInput.Values one by one.
It would be much better if glog support structured logging as a first-class feature.

Hello, if your root requirement is just structure logging feature, it is already supported in glogcomponent. You can refer the document here: https://goframe.org/pages/viewpage.action?pageId=17207121
Here's an example:
package main

import (
	"context"
	"net"

	"github.com/gogf/gf/v2/frame/g"
	"github.com/gogf/gf/v2/os/glog"
)

func main() {
	ctx := context.TODO()
	glog.SetDefaultHandler(glog.HandlerStructure)

	g.Log().Info(ctx, "caution", "name", "admin")
	glog.Error(ctx, "oops", net.ErrClosed, "status", 500)
}

When you run it, it outputs like this:
Time="2023-11-23 21:00:08.671" Level=INFO Content=caution name=admin
Time="2023-11-23 21:00:08.671" Level=ERRO oops="use of closed network connection" status=500 Stack="1.  main.main\n    /Users/txqiangguo/Workspace/gogf/gf/example/.test/main.go:16\n"


docs: send rich push using FCM

Not ready to merge until FCM setup docs are added.

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add an option to DepOptimizationOptions to not discover dependencies to optimize

Hey! 👋
I'm currently trying out Vite in an AdonisJS project.
Since it's a Node.js application, I'm following the Backend Integration guide.
When running npx vite, it tries to optimize all dependencies of the project by default.
Those dependencies are not all related to the frontend. Many of them are for the backend application.
After a bit of digging, there's no magic way of making it work.
One solution could be to add an option to the DepOptimizationOptions that let us disable the auto-discovery of packages and only rely on the  optimizeDeps.include.
This issue will only happen in the Node.js world since PHP and Ruby have a different package manager.

You can actually use this:
optimizeDeps: {
  exclude: '**'
}

which will exclude everything (except for include)

You can actually use this:
optimizeDeps: {
  exclude: '**'
}

which will exclude everything (except for include)

Nice one!
Would you mind if I PR the documentation to add this example as a note?

Nice one!
Would you mind if I PR the documentation to add this example as a note?


stream improvment - page splitter

@mariuszs
You captured the lazy Stream idea perfectly.  Let me know when you are done, I will then merge and make some documentation updates to better describe and explain things around the Stream implementation.  If I do the documentation updates in a PR, would you have time to review for me?

Yes, of course. I think my PR is ready now.
niedz., 10 lut 2019, 01:14 użytkownik Greg Messner<EMAIL_ADDRESS>napisał:

@mariuszs https://github.com/mariuszs
You captured the lazy Stream idea perfectly. Let me know when you are
done, I will then merge and make some documentation updates to better
describe and explain things around the Stream implementation. If I do the
documentation updates in a PR, would you have time to review for me?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gmessner/gitlab4j-api/pull/296#issuecomment-462091725,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABjFYbZG21TOfoezz0-0ag2w4hRf2Mp5ks5vL2R3gaJpZM4ayd71
.

@mariuszs
Looks great, thanks for working with me on this.  I'll have a PR for the docs within the next day or so, will let you know when it's ready.


How to autocomplete from empty string?

I use absolute imports in my project––for example to import /src/utils/example.js I will write import example from 'utils/example'. However I can't seem to get autocomplete working from an empty string. This code from the examples works the way it should:
"path-autocomplete.pathMappings": {
        "/": "${folder}/src"
 },

However using an empty string instead of a slash doesn't. Is there any way to get this working?

I don't think we would add this feature. In your use case, you would better just type 'u' to get suggestion from VSCode builtin support.


merge

By submitting this pull request I confirm I've read and complied with the below requirements.

[ ] I have read the Contribution guidelines and I am confident that my PR reflects them.
[ ] I have followed the coding guidelines for this project.
[ ] My code follows the skeleton code structure.
[ ] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.

merge


ImageNet performance

This repo uses fb.resnet.torch for ImageNet experiments. However the performance of ResNet-50 in fb.resnet.torch is 24.01: https://github.com/facebook/fb.resnet.torch. The performance of ResNet-50 baseline reported in the DBN paper is 24.87. Why is that?

@ppwwyyxx , I guess the difference is probably from the different version of cudnn.
I ran the experiments of Res-18/Res-34 on the machine with cudnn-5.0, while I ran the experiment of Res-50/Res-101 on another machine (I don't remember the version of cudnn and I currently have no access to that machine). It seems that Res-18 and Res-34 have similar results with the experiments on  https://github.com/facebook/fb.resnet.torch.

Perhaps.
Another question: in this repo there are resnet_BN vs resnet_DBN_scale_L1 and preresnet_BN vs preresnet_DBN_scale_L1. Which pair was used as the experiments in the paper?

@ppwwyyxx
It's resnet_BN vs resnent_DBN_scale_L1 as described in the paper.  Thanks for your pointing out, I will revise the README.
Actually, we also ran preresnet-18 and preresnet-34 (The same configuration with res-18 and res-34 described in this repo). The respective results are: 30.44 vs 29.97 (preresnet-18 vs preresnet-DBN-scale-L1-18), 26.76 vs 26.44 (preresnet-34 vs preresnet-DBN-scale-L1-34). We also further ran extra 10 epochs with learning rate diving 10 (100 epochs in total), which is the common setups in recent papers), then we get the results: 29.79 vs 29.31 (preresnet-18 vs preresnet-DBN-scale-18), 26.01 vs 25.76 (preresnet-34 vs preresnet-DBN-scale-L1-34).

Thanks. The diff shows that resnet_DBN_scale_L1 has one more convolution layer, which means the comparison between it and resnet_BN is not fair:
$ diff resnet_BN.lua resnet_DBN_scale_L1.lua
13a14
> require 'cudbn'
121a123,126
>       model:add(Convolution(64,64,3,3,1,1,1,1))
>       model:add(nn.Spatial_DBN_opt(64,opt.m_perGroup, opt.eps,_,true))
>       model:add(ReLU(true))
>

There is no big difference, I guess. You can check the model of preresnet.lua and preresnet-DBN-scale.lua (They have the same number convolution). I also did experiments with the original preresnet (without this extra conv, on 18 and 34 layer),  the original preresnet has slightly better performance (30.38 vs 30.44 for 18 layers, 26.66 vs 26.76 for 34 layers). So I guess there is no big deal for the original residual network with this extra convolution.  If you are interested in it, you can validate it. I also can run the experiments, however, I  only have one machine with 8 GPUs available (and shared with other Lab members),  it may take long times to get the results.

thanks for this


Handle exception but force a rollback

As discussed in issue 38839, if we use a try catch block and return a template then the transaction is not rollbacked. In order to force a rollback we need something like this
@Path("login")
public TemplateInstance loginPage(User user)
        try {
            authService.register(user);
        } catch (Exception e) {
            // transaction is not rollbacked
            return AdminTemplate.auth(e);
        }
        return AdminTemplate.auth();
}

I think it should be better to associate Exception with 'error template' and automatically handle by renarde like this
@ErrorTemplate(CustomException.class)
 public static native TemplateInstance authError(CustomException e);

If we manually handle exception that means we must manually handle transaction too.


Stimulus 3.0 support

Hi, I am getting the following error when I try to compile:
ERROR in ./node_modules/stimulus-flatpickr/dist/index.m.js 1:0-38
Module not found: Error: Can't resolve 'stimulus' in '/Users/tabuna/develop/orchid-project/platform/node_modules/stimulus-flatpickr/dist'

This only happens on version 3 of the stimulus package.
Are there any plans to support this for the new version of the package?

Duplicate #83
You can use the 3.0 beta version

Thanks.


17207 - Alterations - add in new payment code for BC -> ULC

Issue #: /bcgov/entity#17207
Description of changes:
Also includes fixes from previous PR's.
Relies on:
https://github.com/bcgov/bcrs-shared-components/pull/190/files
and a new bcrs-shared enums to be pushed out -^
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-521-c5zdlcko.web.app

/gcbrun

Temporary Url for review: https://business-edit-dev--pr-521-c5zdlcko.web.app


Update lua-resty-openidc to 1.7.1-1 and add redirect_uri

Update lua-resty-openidc to 1.7.1-1
Add redirect_uri field to schema and sending it to lua-resty-openidc

@LuanP Can you provide an example of how this would be configured?
Specifically, I'm trying to get this to work with a single redirect endpoint (e.g. https://auth.example.com/callback) for all of my upstreams (e.g. https://app1.example.com, https://app2.example.com). So far I've been unable to get it to work apart from all redirects going to the redirect endpoint, nothing makes the next jump to the upstream.
My assumption is that the redirect endpoint cannot just be a "vanity URL" but needs some smarts such that it can parse the redirect and extract the ultimate endpoint from a request param. Can you confirm?

@jerfer In our application we just created a /callback in one of the routes with the kong-oidc enabled. Also make sure it's the same redirect_uri provided by the OP. But I didn't have to implement anything on that route.

@LuanP In order for the request_uri parameter to be recognized by lua-resty-openidc, I had to make a change to the code in your PR in the utils.lua/M.get_options() function:
function M.get_options(config, ngx)
  local options = {
    client_id = config.client_id,
    client_secret = config.client_secret,
    discovery = config.discovery,
    introspection_endpoint = config.introspection_endpoint,
    timeout = config.timeout,
    introspection_endpoint_auth_method = config.introspection_endpoint_auth_method,
    bearer_only = config.bearer_only,
    realm = config.realm,
--- >>>--- Change start
    redirect_uri = config.redirect_uri,
--- <<<--- Change end
    scope = config.scope,
    response_type = config.response_type,
    ssl_verify = config.ssl_verify,
    token_endpoint_auth_method = config.token_endpoint_auth_method,
    recovery_page_path = config.recovery_page_path,
    filters = parseFilters(config.filters),
    logout_path = config.logout_path,
    redirect_after_logout_uri = config.redirect_after_logout_uri,
  }

  if not config.redirect_uri then
    options["redirect_uri_path"] = config.redirect_uri_path or M.get_redirect_uri_path(ngx)
  end

  return options
end

But even with this change the redirection still doesn't work properly. Here's what's happening:

I point my browser to http://some_service.example.com/some/path;
Kong is correctly redirecting to the OIDC IdP;
I am successfully authenticated and then redirected to my single redirect_uri, http://auth.example.com/cb

The problem is that I am not then again redirected to http://some_service.example.com/some/path, which I assumed would be the case.
Is my assumption wrong that this is a supported configuration?
What I'm trying to do is avoid having to list all my endpoint paths in my IdP configuration since it doesn't support wildcards on the path portion of redirect URLs, only on the domain-name portion (Auth0). This limitation effectively breaks deep-links unless I can work around it with Kong being able to manage the final redirect from http://auth.example.com/cb to http://some_service.example.com/some/path with the correct cookies set for the authentication.

@jerfer You shouldn't have to list all your endpoint paths in the provider. Just having a match between the OP-RP is enough.
Regarding the steps you've mentioned, your assumption is correct.
When you try accessing a protected route on your application (through kong and having kong-oidc enabled on that route/service) you'd be redirected to the configured OP, get the authentication, and redirected to the request you were performing before, not the one in the redirect_uri/redirect_uri_path.
It just looks like to be a misconfiguration somewhere.
Aren't you seeing any errors in the logs?

@LuanP Thanks for the confirmation and for taking the time to respond. I really appreciate the help.
No, I'm not getting any errors anywhere so I'll tear everything down and start fresh to make sure I haven't missed anything or made a mistake somewhere.
Did you see my comment about your PR and the M.get_options() function?
Can you provide your (sanitized) OIDC plugin config as well as the ingress config for one of your routes? Being able to compare my configs to yours would help to identify what I'm doing wrong.
Here's my OIDC plugin configuration, note the redirect_uri:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: oidc
  namespace: kong
  annotations:
    kubernetes.io/ingress.class: kong
config:
  client_id: "<client_id>"
  client_secret: "<client_secrect>"
  discovery: "https://my.auth0.com/.well-known/openid-configuration"
  scope: "openid email profile"
  realm: "example.com"
  redirect_uri: "http://auth.example.com/cb"
plugin: oidc

Here's the config I'm using for testing:
apiVersion: apps/v1beta2
kind: Deployment
metadata:
  name: echoservice
  namespace: kong
spec:
  replicas: 1
  selector:
    matchLabels:
      app: echoservice
  template:
    metadata:
      labels:
        app: echoservice
    spec:
      containers:
        - name: echoservice
          image: gcr.io/google_containers/echoserver:1.8
          ports:
            - containerPort: 8080
          env:
            - name: NODE_NAME
              valueFrom:
                fieldRef:
                  fieldPath: spec.nodeName
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
            - name: POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP

---

apiVersion: v1
kind: Service
metadata:
  name: echoservice
  namespace: kong
  labels:
    app: echoservice
spec:
  type: NodePort
  ports:
    - port: 80
      targetPort: 8080
      protocol: TCP
      name: http
  selector:
    app: echoservice

---

apiVersion: configuration.konghq.com/v1
kind: KongIngress
metadata:
  name: echoservice
  namespace: kong
proxy:
  path: /
route:
  protocols:
    - http
  strip_path: false

---

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: echoservice
  namespace:  kong
  annotations:
    kubernetes.io/ingress.class: "kong"
    configuration.konghq.com: echoservice
    plugins.konghq.com: oidc
spec:
  rules:
    - host: echo.example.com
      http:
        paths:
          - path: "/"
            backend:
              serviceName: echoservice
              servicePort: http
---

@LuanP I figured out the problem. Instead of using the request_uri parameter, I can rely instead on a wildcard subdomain as my Auth0 redirect with a hardcoded path (e.g. http://*.example.com/auth/openid/callback). Kong is then able to successfully redirect from any subdomain/callback to the original request (e.g. http://app1.example.com/auth/openid/callback -> http://app1.example.com/some/path). The clue to all of this was is in #35.
For completeness, here's my working config:
apiVersion: configuration.konghq.com/v1
kind: KongPlugin
metadata:
  name: oidc
  namespace: kong
  annotations:
    kubernetes.io/ingress.class: kong
config:
  client_id: "<client_id>"
  client_secret: "<client_secret>"
  discovery: "https://example.auth0.com/.well-known/openid-configuration"
  scope: "openid email profile"
  realm: "example.com"
  redirect_uri_path: "/auth/openid/callback"
plugin: oidc

On the Auth0 side I configured the Allowed Callback URLs to contain: http://*.example.com/auth/openid/callback, meaning I don't have to add all services and their endpoints to Auth0. The final flow looks like this (simplified):

Unauthenticated request to http://app1.example.com/some/path
Kong redirects to Auth0
User is authenticated
Auth0 redirects to http://app1.example.com/auth/openid/callback
Kong intercepts and redirects to http://app1.example.com/some/path

Thanks again for your help.

Oh, good work on that man, sorry not being more helpful.
About the comment on the changes, thanks for that, I'll update it here ASAP.

No worries! You helped more than you think.
Jerry
On Tue, May 21, 2019 at 8:52 PM Luan Pablo<EMAIL_ADDRESS>wrote:

Oh, good work on that man, sorry not being more helpful.
About the comment on the changes, thanks for that, I'll update it here
ASAP.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nokia/kong-oidc/pull/114?email_source=notifications&email_token=AALMWR3OEEVZO5DJHQ7HZDTPWSKOPA5CNFSM4HA2WN5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV5SVGY#issuecomment-494611099,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALMWR6NI2MECWTFN7YRLJ3PWSKOPANCNFSM4HA2WN5A
.


Add Scikit-HEP badge to README

We tend to have it across all packages ... Your choice, of course.

Splendid, thanks.


Move JS libraries out, separate test suite

move the JS libs out and have a separate test suite for them

not doing this, overall this repo is a convenient location for the JS libs


userParameters . extended documentation with examples

Hello.
Forgive me for contacting you. But unfortunately I did not find the answer in the documentation.
Could you give some examples of how to access the userParameters parameter in AD using your library  ldaptools.
Because we have it in binary format like this and can not decode it.
CtxCfgPresent                                   PCtxCfgPresent㔵攱戰ぢCtxCfgFlags1〰て〲〹 xCtxWFProfilePath挵挵㤶收㐷㔶㈷收ㄶ挶攲ㄶ㐶㔶挶㤶收ㄶ攲㌶昶搶攲㔷ㄶ挵收㔶㐷㜷昶㈷戶挵挴㘷㤶㘷挵〵㈷昶㘶㤶挶㔶㌷挵搶ㄶ收㐶ㄶ㐷昶㈷㤷搲㌷〰"ðCtxWFProfilePathW挵〰挵〰㤶〰收〰㐷〰㔶〰㈷〰收〰ㄶ〰挶〰攲〰ㄶ〰㐶〰㔶〰挶〰㤶〰收〰ㄶ〰攲〰㌶〰昶〰搶〰攲〰㔷〰ㄶ〰挵〰收〰㔶〰㐷〰㜷〰昶〰㈷〰戶〰挵〰挴〰㘷〰㤶〰㘷〰挵〰〵〰㈷〰昶〰㘶〰㤶〰挶〰㔶〰㌷〰挵〰搶〰ㄶ〰收〰㐶〰ㄶ〰㐷〰昶〰㈷〰㤷〰搲〰㌷〰〰〰lCtxWFHomeDir挵挵㤶收㐷㔶㈷收ㄶ挶攲ㄶ㐶㔶挶㤶收ㄶ攲㌶昶搶攲㔷ㄶ挵收㔶㐷㜷昶㈷戶挵挴㘷㤶㘷挵㠴昶搶㔶㌷挵㈷㈶㔶㘷愷㤶㔷戶〰ØCtxWFHomeDirW挵〰挵〰㤶〰收〰㐷〰㔶〰㈷〰收〰ㄶ〰挶〰攲〰ㄶ〰㐶〰㔶〰挶〰㤶〰收〰ㄶ〰攲〰㌶〰昶〰搶〰攲〰㔷〰ㄶ〰挵〰收〰㔶〰㐷〰㜷〰昶〰㈷〰戶〰挵〰挴〰㘷〰㤶〰㘷〰挵〰㠴〰昶〰搶〰㔶〰㌷〰挵〰㈷〰㈶〰㔶〰㘷〰愷〰㤶〰㔷〰戶〰〰〰"CtxWFHomeDirDrive愵愳〰$CtxWFHomeDirDriveW愵〰愳〰〰〰
Please give an example, How to get values from this field userParameters  it in PHP and convert it in php string array or etc readable?
And how to create your own, and put back in Active Directory? it is expected that it needs to be encoded before being put into the domain.
Thank you.
Sorry to bother you.

You need to find how it encode and decode in the forum. If it is AD try to check in microsoft forum
They only convert generic one. You can find supported schema in resource/schema/ad.yml for AD.
If it is not there you need to create your own Converter and attribute. It's editable.