Adds specific text style mixins

cc @andycarrell

Adds mixins for card text. Moved away from h3, h4 etc because it's not really following the structure properly anyways.
Swapped some styling over but realised that you're probably changing the structure quite a bit so happy to remove these changes from this PR

Could maybe even remove the h3 and h4 heading mixins if they aren't being used - Just keep h1 and h2?

Some design feedback - just an opinion tho, don't have to change 🙏

I think the uppercase text should have a heavier font weight (500 in screenshot)
Should we align the text to "baseline" across the term, percentage & doses remaining?

Sorry my bad, this PR was just to add the mixins for you to rebase into your new layout PR, I'm not actually keen to update the production layout design to use these styles 😊
The font-weight change looks ok but I'd be keen to double check with the new layout when you update your PR if that's ok?

@finnclark - yup that makes sense, before we merge we can remove the mixins, then it won't ship 🙏
From an implementation perspective, these classnames are global, but they're very specific - for example vaccine-count, it's pretty clear where that's expected to be used, but it's not that clear how we would style the next piece of text that ultimately has the same size / height / weight - so I don't think these should be mixins.
I think there's two options here either we:

Avoid using mixins for typography and move the specific styling to DosesDescriptionList.module.scss. It might also make sense to create a font-size / weight scale that DosesDescription can reference

Make the mixins more generic, probably by bringing back a scale like we had: heading-1 heading-2 etc in typography, then each component determines which classname it should use. If we're doing that, we probably don't need a mixin since we can just create classNames for each?

Updated per call @andycarrell


make more memory efficient

do not use yaml library but parse "manually"
using only those parts of the input that are needed
allow to use a local copy of the file from ncbi

Thanks @nickeener .. can you release this on pypi?

@bernt-matthias Should be updated now.


Rage Mode

How about adding Rage Mode for HvH? This cheat already inherits Aimbot, Visuals, Anti-Aim and other features needed for Rage HvH.
Will be useful for HvH on HvH Servers.

In my opinion, Rage Mode in an open source is just a mistake.

Negative, Idk ragebot is high priority rightnow

In my opinion, Rage Mode in an open source is just a mistake.
But, who knows.

Then according to your logic, an open-source cheat is a clear mistake. People can configure anti-aim and aimbot for rage in normal competitive too.
Rage Mode is only helpful in HvH.


Rename Vayra's "drone_pd" ship system to vayra_exemplardrone_drone_pd

Issue link:
https://github.com/RkShaRkz/Starsector-IntelliJ-Template/issues/74
Turns out, the 'old' name was just trampling the original/vanilla drone_pd system's file, but used a different ID - vayra_exemplardrone_drone - so that when any other ships tried to use it the game would just crash with a RuntimeException: System with id [drone_pd] not found
This commit should solve the following stacktrace:
ERROR com.fs.starfarer.combat.CombatMain  - java.lang.RuntimeException: System with id [drone_pd] not found
java.lang.RuntimeException: System with id [drone_pd] not found
	at com.fs.starfarer.combat.entities.Ship.<init>(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.loading.specs.oooo.super(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.campaign.fleet.FleetMember.instantiateForCombat(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.combat.CombatFleetManager.super(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.combat.CombatFleetManager.Ò00000(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.combat.CombatFleetManager.deploy(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.combat.ai.admiral.oOoO.if.super(Unknown Source) ~[port_obf.jar:?]
	at com.fs.starfarer.combat.ai.admiral.oOoO.Òo0000(Unknown Source) ~[port_obf.jar:?]
	. . . . .

BEFORE FIX:
When a ship that's still using "drone_pd" ship system would be encountered in-game, the game would apparently crash.
AFTER FIX:
Didn't even test this yet
EXPECTED:
Both vayra's ships and vanilla ships that use the vanilla drone_pd system should work, side-by-side.

Ok, after adding the drone_pd system to vayra_hammer_carrier, vayra_workhorse, and vayra_martyr and trying to add them to my fleet in an already-existing save (made on previous version) i received some LPCs of "them" (?), but when hovering over the LPCs, the game crashed with the following stacktrace:
279564 [Thread-3] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.RuntimeException: System with id [drone_pd] not found
java.lang.RuntimeException: System with id [drone_pd] not found
	at com.fs.starfarer.combat.entities.Ship.<init>(Unknown Source)
	at com.fs.starfarer.loading.specs.oooo.super(Unknown Source)
	at com.fs.starfarer.campaign.ui.trade.D.void.do(Unknown Source)
	at com.fs.starfarer.campaign.ui.trade.D.<init>(Unknown Source)
	at com.fs.starfarer.ui.impl.CargoTooltipFactory$2.createImpl(Unknown Source)
	at com.fs.starfarer.ui.impl.StandardTooltipV2Expandable.create(Unknown Source)
	at com.fs.starfarer.ui.impl.StandardTooltipV2Expandable.beforeShown(Unknown Source)
	at com.fs.starfarer.ui.thissuper.showTooltip(Unknown Source)
	at com.fs.starfarer.ui.O0Oo.super.new(Unknown Source)
	at com.fs.starfarer.ui.O0Oo.processInput(Unknown Source)
	```
which is identical to the one on the issue and in the opening post.
So the fix **IS NOT** save-game compatible, lets see how it runs on a new game.

Turns out, I was testing by adding the drone_pd system to fighter wings, so of course it didn't work...
When I replaced some ship's (vayra_heavy_drone_tender) system with drone_pd and added it, as well as adding vayra_exemplar ship, both work fine, and nothing crashed.
Lemme try them in combat just to verify combat works with both of them before merging this in and closing the issue.

Can confirm the fix is working both on new and old saves, and that zero problems arise during combat. Ship it.


RSDK-2403 Expose disableSessions option in DialConf

RSDK-2403
Exposes a new disableSessions option in DialDirectConf and DialWebRTConf that is passed to the RobotClient constructor.

Really no idea what I'm doing here, so just lmk here or offline if this is totally off, @maximpertsov .


avro schema converted from type=record to type=object when read from asyncapi

Describe the bug
avro schema converted from type=record to type=object when read from asyncapi.

I have an asyncapi with an avro schema pulled from schema registry. The schema type is "record" with a list of fields.
When the payload is extracted using avro-schema-parser, the record type is changed to "object" with a properties list.
The payload format extracted from the AsyncApi should be consistent with the input.
Viewing the asyncapi in studio in this manner is not an issue. However, programmatic usage of the payload defined this way is creating a problem.

How to Reproduce
We are using the avro-schema-parser to build AsyncApis using schema registry as source for payloads. The behavior can be observed using asyncapi/studio.

Using asyncapi/studio at: https://studio.asyncapi.com
Paste the following AsyncApi
Observe type=Object

AsyncApi to enter into Studio
---
components:
  schemas: {}
  messages:
    samples.clickstream.avro.ClickEvent:
      payload:
        name: ClickEvent
        namespace: samples.clickstream.avro
        type: record
        fields:
        - name: ip
          type: string
        - name: eventtimestamp
          type: long
        - name: devicetype
          type: string
        - name: event_type
          type:
          - string
          - 'null'
        - name: product_type
          type:
          - string
          - 'null'
        - name: userid
          type: int
        - name: globalseq
          type: long
        - default: 0
          name: prevglobalseq
          type: long
      name: samples.clickstream.avro.ClickEvent
      contentType: application/json
      schemaFormat: application/vnd.apache.avro;version=1.9.0
    default_name:
      payload:
        type: string
      name: default_name
      contentType: application/json
      schemaFormat: application/vnd.apache.avro;version=1.9.0
channels:
  User_Sessions_Aggregates_With_Order_Checkout: {}
  ClickEvents_UserId_Agg_Result: {}
  __amazon_msk_canary: {}
  _schemas: {}
  Departments_Agg: {}
  ExampleTopic:
    publish:
      message:
        "$ref": "#/components/messages/samples.clickstream.avro.ClickEvent"
asyncapi: 2.2.0
info:
  description: API discovery with avro
  title: api_with_avro
  version: 0.1.0

This is the original schema:
{
	"schema": {
		"type": "record",
		"name": "ClickEvent",
		"namespace": "samples.clickstream.avro",
		"fields": [
			{
				"name": "ip",
				"type": "string"
			},
			{
				"name": "eventtimestamp",
				"type": "long"
			},
			{
				"name": "devicetype",
				"type": "string"
			},
			{
				"name": "event_type",
				"type": [
					"string",
					"null"
				]
			},
			{
				"name": "product_type",
				"type": [
					"string",
					"null"
				]
			},
			{
				"name": "userid",
				"type": "int"
			},
			{
				"name": "globalseq",
				"type": "long"
			},
			{
				"name": "prevglobalseq",
				"type": "long",
				"default": 0
			}
		]
	}
}

This is the output of the avro-schema-parser (schema format extracted from asyncapi)

Note the discrepancy between the type and properties/fields

{
	"type": "object",
	"required": [
		"ip",
		"eventtimestamp",
		"devicetype",
		"userid",
		"globalseq"
	],
	"properties": {
		"ip": {
			"type": "string"
		},
		"eventtimestamp": {
			"type": "integer",
			"minimum": -9223372036854776000,
			"maximum":<PHONE_NUMBER>854776000
		},
		"devicetype": {
			"type": "string"
		},
		"event_type": {
			"oneOf": [
				{
					"type": "string"
				},
				{
					"type": "null"
				}
			]
		},
		"product_type": {
			"oneOf": [
				{
					"type": "string"
				},
				{
					"type": "null"
				}
			]
		},
		"userid": {
			"type": "integer",
			"minimum": -2147483648,
			"maximum":<PHONE_NUMBER>
		},
		"globalseq": {
			"type": "integer",
			"minimum": -9223372036854776000,
			"maximum":<PHONE_NUMBER>854776000
		},
		"prevglobalseq": {
			"type": "integer",
			"minimum": -9223372036854776000,
			"maximum":<PHONE_NUMBER>854776000,
			"default": 0
		}
	}
}

Expected behavior

The payload format extracted from the AsyncApi should be consistent with the input.
Payload type: record
Payload content itemized as fields instead of object properties when input type is "record"

test-files.zip

Note: See here for definition of Avro type record

@dennis-brinley Hi! AsyncAPI document doesn't "understand" the AVRO schemas so every custom parser (this and also for OpenAPI and RAML) converts data to the corresponding data defined as JSON Schema, and due to this fact, you see type: object and properties not type:record, fields:..., In JSON Schema you don't have record type or fields keyword.

@magicmatatjahu Hello - I understand the limits of the AsyncApi regarding Avro. The problem that I've described isn't the representation in the AsyncApi itself. Rather, when the AsyncApi is interpreted by avro-schema-parser. AsyncApi containing an Avro schema will be defined using JSON semantics. However, when an asyncapi containing schema with Avro content type is interpreted by the parser, shouldn't it produce an Avro schema that can be used by an application expecting to use that format?
For example, An application requires an Avro schema. Does AsyncApi provide a mechanism to extract the Avro schema content from the payload definition?
Should be:
Avro Schema --embed--> AsyncApi( JSON Semantics ) --extract--> Avro Schema --> Happy Application
The way it is:
Avro Schema --embed--> AsyncApi( JSON Semantics ) --extract--> Json Schema --X not-happy Application

@dennis-brinley the parser do not remove oryginal info about the payload, these are preserved under:

x-parser-original-schema-format holds information about the original schema format of the payload. You can use different schema formats with the AsyncAPI documents and the parser converts them to AsyncAPI schema. This is why different schema format is set, and the original one is preserved in the extension.
x-parser-original-payload holds the original payload of the message. You can use different formats for payloads with the AsyncAPI documents and the parser converts them to. For example, it converts payload described with Avro schema to AsyncAPI schema. The original payload is preserved in the extension.

I think these could be easily exposed in generated documentation, we could say, payload is avro and provide a way to click and display the original avro schema - is this what you mean?

@derberg - So the intent of extension x-parser-original-payload is to preserve the raw used to generate the spec? If yes, then then exposing that and value of x-parser-original-schema-format would be helpful.
So spec would contain something like:
messages:
  samples.clickstream.avro.ClickEvent:
    payload:
      name: ClickEvent
      namespace: samples.clickstream.avro
      type: record
      fields:
      - name: ip
        type: string
      # more fields
    name: samples.clickstream.avro.ClickEvent
    contentType: application/json
    schemaFormat: application/vnd.apache.avro;version=1.9.0
    x-parser-original-payload: >
{"type":"record","name":"Payment","namespace":"io.confluent.examples.clients.basicavro","fields":[{"name":"id","type":"string"},{"name":"description","type":"string","default":"my description"},{"name":"amount","type":"double"},{"name":"region","type":"string","default":""},{"name":"testSubject","type":"string","default":""}]}
    x-parser-original-schema-format: application/vnd.apache.avro;version=1.9.0

If this is the case then I'll close the issue.
Either way, it's not a bug :-) Thanks for your help!

let's see what others have to say.
might be we move it to react component repo as a feature request 😉

Sounds good. Is that asyncapi snippet that I have in my last comment correct in it's presentation of the x-parser-* fields?

the parser do not remove oryginal info about the payload, these are preserved under:

x-parser-original-schema-format holds information about the original schema format of the payload. You can use different schema formats with the AsyncAPI documents and the parser converts them to AsyncAPI schema. This is why different schema format is set, and the original one is preserved in the extension.

I hadn't noticed x-parser-original-schema-format before - that's really interesting.
I can see this being useful when you first create an AsyncAPI doc, but doesn't it quickly get out of sync after that? I'm thinking that it'd be easy to make changes to the spec in the AsyncAPI doc, without remembering to reflect those changes in the x-parser extension - which sounds like it could lead to confusion.

We found that we can use the originalPayload() method instead of the standard payload() method and retrieve the original Avro schema using avro semantics.
I do think you want to update studio to do the same thing. The schema presented as json based upon avro type is confusing.
Closing the issue. Thanks for your help.

@dalelane x-parser- extensions are added by JS Parser, user should not "touch" these manually.


Updated component

This PR contains several changes to the integration, the most important are:

Building on a custom pytedee_async library now, this allows all functions to be async
pytedee_async contains properties instead of getters and setters to clearly mark where IO is happening, this has been updated in this integration
properties do not do IO anymore, instead updates happen only through the async_update method
added "is_jammed" property for lock
moved platform setup to init.py
added extra sensor for battery
added extra button to pull latch
extended device info and added lock type (pro/go)
allow reloading of integration
added options flow to configure the personal key

@patrickhilker just tagging you for GitHub notifications

Awesome! Thanks for tagging me ..


TkFallback methods should be revised and cleaned up

The current implementation of the methods in org.takes.facets.fallback.TkFallback is a little verbose and should be revised/cleaned up by introducing some private methods that will take care of the following code repetitions:
TkFallback.error(
    ex, req,
    System.currentTimeMillis() - start
)

and:
new RqFallback.Fake(
    req, HttpURLConnection.HTTP_INTERNAL_ERROR,
    TkFallback.error(
        ex, req,
        System.currentTimeMillis() - start
    )
)

@0crat in

@0crat in (here)

@paulodamaso Thanks for your contribution, @simonjenga/z! If you would be a member of the project, you would now earn +15 reputation points, as explained in §29. You can join and apply to it, see §2.

The job #788 assigned to @krzyk/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

@0crat wait I'm busy with other tasks

@0crat wait I'm busy with other tasks (here)

@krzyk The impediment for #788 was registered successfully by @krzyk/z

@simonjenga ping

@krzyk OK :+1:

@ypshenychka/z please review this job completed by @krzyk/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #788 is now out of scope

@0crat quality good (here)

@ypshenychka The project doesn't have enough funds, can't make a payment

@0crat quality good (here)

@ypshenychka The project doesn't have enough funds, can't make a payment

Order was finished, quality is "good": +35 point(s) just awarded to @krzyk/z

Quality review completed: +8 point(s) just awarded to @ypshenychka/z


Add blinding to a DSA signature (1.0.2)

This extends the recently added ECDSA signature blinding to blind DSA too.
This is based on side channel attacks demonstrated by Keegan Ryan (NCC
Group) for ECDSA which are likely to be able to be applied to DSA.
Normally, as in ECDSA, during signing the signer calculates:
s:= k^-1 * (m + r * priv_key) mod order
In ECDSA, the addition operation above provides a sufficient signal for a
flush+reload attack to derive the private key given sufficient signature
operations.
As a mitigation (based on a suggestion from Keegan) we add blinding to
the operation so that:
s := k^-1 * blind^-1 (blind * m + blind * r * priv_key) mod order
Since this attack is a localhost side channel only no CVE is assigned.
This commit also tweaks the previous ECDSA blinding so that blinding is
only removed at the last possible step.
This is the 1.0.2 version of #6522.

I think a note in CHANGES about slower crypto for side-channel protection is worth doing.

Pushed.


Better export to epub

I finally found the time to work a bit on the library and implemented it in LNReader with a few changes for better compatibility.

changed lineheight and textsize to be rem based instead of px
changed epub text to be wrapped in div with id chapter instead of a chapter element, since the epub standard doesn't accept custom elements.
added to id chapter to the readerscreen chapter element.

This PR closes:

#861
#797
#777
#696
#745

works as expected
shouldn't be viewed in the first place
prevents filename duplications

#740

not app/library related

Why should we export reader ui to epub?

Why should we export reader ui to epub?

Where do I export the reader ui?

Why should we export reader ui to epub?

Where do I export the reader ui?

` + (css as string).replace(/chapter/g, '#chapter')

Btw, you could use implemented FileManager.pickerFolder to pick a folder with resolved path.

Bug report:
The numeration of xhtml files is based on the sort order set on the novel entry. Force it as ascending.
Uploading YouCut_20240727_181448669.mp4…
How to reproduce:
-pick an entry, download 10 chapters, set chapter list to descending order, export, check chapter files

Feature request:
Make chapter file numbering start from chapter 1

The majority of webnovels dont have a chapter before chapter 1.

Feature request: Make chapter file numbering start from chapter 1

Not planed, since only a minority of users will open the epub

F-r
Add warning in case the downloaded chapters have hole in between.
chapter 1-8 — downloaded
chapter 9-16 — NOT downloaded
chapter 17-100 — downloaded
It would be nice to know. Not necessary tho.

Performance issue:
Export speed slower in beta(tested on latest)
beta(2:25):
https://github.com/user-attachments/assets/db111b97-305d-4c40-8c79-b7b35d5fa730
Stable(1:10):
https://github.com/user-attachments/assets/2b7bf3f0-3cff-467e-b223-f71c189e9cc9

Bug

Export failed due to missing images in a chapter. The chapter is downloaded but somehow the images werent, maybe an app bug or the plugin failed to pick them.
-Novelfull, Cultivation chat group, chapter 841

Export error:

It comes from an imported EPUB entry.
922k.txt
note: RENAME the extension from .txt to .epub (github doesnt accept epub files)

Flaw
Directory error after 2 min of exporting:

The problem is that I used a path that was picked in the past, and somehow it disappeared, so it gave the error.
Solution:
-Check the directory avaiability first, to make the error pop up immediately and not waste 2 minutes.

Feature request:
Perma-edit chapters content with customJS upon export.
A way to edit the content of downloaded chapter based on customJS. A little checkbox somewhere here:

Suggestion:
Way to inject directly JS or CSS, ignoring the code in customJS and CSS of the app.
It's a little cumbersome to go there, paste the code and then come back to the entry to export.
It's more comfortable.

Suggestion: Way to inject directly JS or CSS, ignoring the code in customJS and CSS of the app. It's a little cumbersome to go there, paste the code and then come back to the entry to export.
It's more comfortable.

Why would you want that? What exactly is the use case to have js/css specific only for the epub. Especially when most epub readers don't support it.

Why would you want that? What exactly is the use case to have js/css specific only for the epub. Especially when most epub readers don't support it.

Just more comfortable. Since js can already be included, allow to directly do it from this place:

Also, IF you have the intention of implementing the Perma-edit feature above, the "especially when most epub readers don't support it" wouldnt matter anymore.

Well it won't come with this PR, for now I need to find the time to finish this one.
A perma edit would be the best solution to it, however this would also need a lot of work.


Inconsistency in required NodeJS versions

This article says that SPFx development requries NodeJS 10.0, but later, when the reader is told to run npm trust-dev-cert, that command give the following error that says 10.0 can't be used:
This tool requires a version of NodeJS that matches >=8.9.4 <9.0.0 || >=10.13.0 <11.0.0

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

ID: 5bee09a8-022e-1b5a-4aab-d6e7c6216808
Version Independent ID: 49edce1e-f2be-e989-917f-c6b389363e2f
Content: Set up your SharePoint Framework development environment
Content Source: docs/spfx/set-up-your-development-environment.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Node 10.13.0 is the first 10.x release tagged LTS https://nodejs.org/en/download/releases/. The docs should either reference 10.13.0 or say 10.x rather than 10.0.

@Rick-Kirkham the docs say to use Node.js v10.x, not Node.js v10.0. Due to how often Node.js ships releases, a while ago we changed the docs to not reference a specific version, rather the docs explicitly state:

Install the latest version of Node.js LTS v10.x.


Update collector to 3.12.3

Description
A rebuild of collector to fix the openssl vuln https://access.redhat.com/errata/RHSA-2023:1405

/retest

/retest


Android: Why are the values reset when I update the app?

Does this library reset its values when the app is updated in the Google Play Store? If so, is there any solution to this issue?
Thanks.

any update on this

Anyone else experiencing this? Seems like a huge deal breaker. @lluisandreu did you manage to confirm if the storage is reset when the app is updated?

I don't get the issue, are you asking a question, immediately assuming that storage IS reset, and then asking for alternatives?
For my app, storage is not reset. I don't know where you have that info from.


Upgrade solution for 2.0

cc @robdmoore

Probably needs an RC first, still only net45

Better to unblock people, let's do it :-)

Is it a problem that there are a bunch of skipped tests? Not sure if that's since been resolved :)

@robdmoore yeah I think that's a problem that hasn't been fixed yet, my bad. I incorrectly assumed it wouldn't be available on AppVeyor

From memory you can define scripts to run to install stuff like that on appveyor. I haven't personally tried though.

On 17 Jul 2016, at 6:00 PM, Adam Chester<EMAIL_ADDRESS>wrote:
@robdmoore yeah I think that's a problem that hasn't been fixed yet, my bad. I incorrectly assumed it wouldn't be available on AppVeyor
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add version: TravisLane.SteamArtManager version 1.4.3

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run

/AzurePipelines run


Scroll to offset

Window object provide method scrollTo with two properties x and y. I just can say Y position and scroll TO. If i want animate scroll behaviour i will use "vue-scrollto", but now i can't do it as before cause plugin interface require DOM element to scroll. Do I realy need to create DOM element for this simple thing?

This lib scrolls to elements, if you only need to scroll to x and y coordinates, you are better of using request animation frame without this library


[Home] Back from home screen or nav drawer shows white screen

Back now closes the app as expected. Thanks @shobhitagarwal1612 for the fix!


Heuristic not disapering whem deleting.

The heuristic only disappears after you press the save button and refresh.
This is happening  on the branch weighTable.

Who is working on this issue? @FernandaCasali

@FernandaCasali @jvJUCA Is this issue related to (or copy of) #278 ?


Live Server Chrome issue

Live server has setting mode 'chrome' but it is not recognised by the browser . Hence it is showing an error .
Solution : There should be an option to select from local browser app by navigation .
Attaching SS for same .

Google chrome issue


fix on:click on doc

A couple of corrections to the documentation

Nice! Thanks for submitting this. It'll be a little bit longer before the changes actually take effect on the main page since we are working on the 1.0 release and it includes doc changes that don't work in 0.19.x


Add update rate option to settings

SceneHook causes my debug capsules in scene view to draw erratically when it invokes the LateUpdateEvent. Same result when using the TMP UI. Commenting out the event in lateupdate and adding the below fixes the problem.
 private void FixedUpdate()
        {
            LateUpdateEvent?.Invoke(Time.fixedDeltaTime);
        }

Adding an update rate option to the settings will allow people to select what rate works for them. Excellent work with this asset.

To replicate, use the (free) Physics Debug Extension by RotaryHeart and draw a debug CapsuleCast during FixedUpdate on a moving object while runtime-monitoring is displaying using the [Monitor] attribute.
Physics.CapsuleCast(capsuleBottom, capsuleTop, capsuleRadius, direction,                                 out RaycastHit hit, maxDistance, GroundLayers.value, PreviewCondition.Editor, 0f, Color.blue, Color.white, false, CastDrawType.Minimal);
At it's core it only uses Debug.Draw when drawing in the editor so it can be an issue outside of this asset also.


ENH: stats: add F-test of equality of variances

Closes https://github.com/scipy/scipy/issues/19646
The F-test of equality of variances is a statistical test for the
null hypothesis that two normal samples have the same variance.
This function has three alternatives to calculate the p-value
corresponding to the lower ('less') or upper ('greater') one-tailed
and two-tailed ('two-sided').
Co-Authored-By: Tomás Silva<EMAIL_ADDRESS>

Thanks for the proposal.
I thought Levene or Bartlett were more powerful. Unless there is a stronger argument, as in not just it's a famous test, I would be -1.

@gnc1999 I agree with @tupui that this would need to be more powerful or have some other advantage compared to our existing tests to warrant inclusion. Please try to find a reference with such a statement, or you can study it numerically using scipy.stats.power (development version) to study it numerically.
The documentation of fligner and bartlett say:

Conover et al. (1981) examine many of the existing parametric and nonparametric tests by extensive simulations and they conclude that the tests proposed by Fligner and Killeen (1976) and Levene (1960) appear to be superior in terms of robustness of departures from normality and power [3].

That reference is:

Conover, W. J., Johnson, M. E. and Johnson M. M. (1981). A comparative study of tests for homogeneity of variances, with applications to the outer continental shelf bidding data. Technometrics, 23(4), 351-361.

Thank you for your feedback, @mdhaber and @tupui. As requested, I have created a new topic on the forum to gather additional support for adding this test: https://discuss.scientific-python.org/t/enh-stats-add-f-test-of-equality-of-variances/1216. My colleague @t-om5 and I chose to add the F-test for equality of variances to SciPy because there was an open issue, and we believed it would complement the existing Levene's and Bartlett's tests.
We are open to making the necessary improvements and feature additions. We will look for references to support the inclusion of the F-test and conduct a numerical study to compare its performance with existing tests. Our primary motivation was to address an open issue and contribute with something useful for the community.

In simulations in which the normality assumption is met, the power of this test and Bartlett are identical.

import numpy as np
from scipy import stats
from scipy.stats._morestats import f_equality_test
rng = np.random.default_rng(2348435924652)
import matplotlib.pyplot as plt

def test(x, y, axis=0):
    res1 = stats.bartlett(x, y, axis=axis)
    res2 = f_equality_test (x, y, axis=axis)
    res3 = stats.levene(x, y, axis=axis)
    return res1.pvalue, res2.pvalue, res3.pvalue

n_observations = (30, 35)
rvs1 = lambda size: rng.normal(scale=1, size=size)
rvs2 = lambda size, scale2: rng.normal(scale=scale2, size=size)
rvs = (rvs1, rvs2)
scale2 = np.logspace(-0.5, 0.5, 20)
kwargs = {'scale2': scale2}
res = stats.power(test, rvs, n_observations, significance=0.05, kwargs=kwargs)

power_bartlett, power_f, power_levene= res.power.T

plt.semilogx(scale2, power_bartlett, '-', label='bartlett')
plt.semilogx(scale2, power_f, '--', label='f_equality')
plt.semilogx(scale2, power_levene, '-.', label='levene')

plt.legend()
plt.xlabel('scale of second distribution')
plt.ylabel('power')
plt.title(f'Power of variance tests, {n_observations=}')
plt.show()

I also tested a case in which the normality assumption was not met, and both seemed equally sensitive to the deviation from normality.
The results only seem to diverge when the sizes of the two samples are quite different.

Thanks Matt. Alright, I think we don't need to spend more time on this then and close this (with the linked issues).
Thanks again @gnc1999. I am sorry that we could not integrate your proposal. There are many open issues and needs still. Feel free to ask us though before putting yourself too much effort into implementing something.

It looks like when the distribution that has more observations has the smaller variance, this test is a bit more sensitve and vice versa.
After a little more investigation, it might at least be worth a note in the documentation of bartlett comparing against this test. Or perhaps one could make an argument about which test to use based on a hypothesized difference in variances.
Another possible advantage of this test is that it does accept an alternative, whereas the natural formulation of bartlett with the chi-squared null does not.

A note in the doc would not hurt 👍 And help with the SEO 😉


add status:state label on asset show pages

@maddalab @Primer42 This makes it easier to see what status an asset is in, even if you are on another menu pill. Nice to have to prevent someone from rebooting the wrong box when clicking through tabs :)
The label has a hover of the status+state description, just to be a fancy pants. It is also right justified to the top+right of the page header, so it looks clean (not terribly obvious from the screen shots).

LGTM :snowman: :clock12: :confetti_ball:

lgtm

Any objections to merging in? Anyone want me to put up a container that has this change in it to try it out?

I built this from source (ya, I'm just old :school: like that) and it worked fine.  Merge away!

Sweet. :boom: :fire: :rice_cracker: :zap: :rotating_light:


added filepush.co

added filepush.co to file transfer sites

@marianopw I've merged it, though filepush.co does not seem to be console oriented.
Compare:
curl https://transfer.sh/
curl filepush.co

Yup, transfer.sh is really focused on console usage, but filepush also allows uploading files using curl and downloading with wget.

@marianopw Yes, but it is true for any service. If you somehow related to filepush.co, could you encourage the authors to add some text help page available from the console where the most important operations are described?


Cluster Auto Scaling

ECS Cluster Auto Scaling is now GA. It would make sense to add that once support is added in CloudFormation.
Cluster Auto Scaling may also remove the need for a dedicated container instance draining lifecycle hook.

Yes, I was about to ask about this, as capacity providers are now generally available.
I was wondering if there are any planned updates for modifying this sample stack to use capacity providers instead.
It would be really cool if we can have an example!
Thank you very much in advance!


test_bot: allow to override HOMEBREW_CURL_PATH

This is necessary for running tests on older Linux systems,
were we provide a newer curl version which is installed in a different path.

Does HOMEBREW_FORCE_BREWED_CA_CERTIFICATES not cover this?

I gave HOMEBREW_FORCE_BREWED_CA_CERTIFICATES, but it did not work.
2022-02-20T10:15:55.6692632Z ##[group]Full fetch binutils --build-bottle output
2022-02-20T10:15:55.6693272Z ==> Downloading https://ftp.gnu.org/gnu/binutils/binutils-2.38.tar.xz
2022-02-20T10:15:55.6693648Z curl: (60) SSL certificate problem: certificate has expired
2022-02-20T10:15:55.6693994Z More details here: http://curl.haxx.se/docs/sslcerts.html
2022-02-20T10:15:55.6694192Z
2022-02-20T10:15:55.6694367Z curl performs SSL certificate verification by default, using a "bundle"
2022-02-20T10:15:55.6694719Z  of Certificate Authority (CA) public keys (CA certs). If the default
2022-02-20T10:15:55.6695162Z  bundle file isn't adequate, you can specify an alternate file
2022-02-20T10:15:55.6695669Z  using the --cacert option.
2022-02-20T10:15:55.6696003Z If this HTTPS server uses a certificate signed by a CA represented in
2022-02-20T10:15:55.6696568Z  the bundle, the certificate verification probably failed due to a
2022-02-20T10:15:55.6696961Z  problem with the certificate (it might be expired, or the name might
2022-02-20T10:15:55.6697295Z  not match the domain name in the URL).
2022-02-20T10:15:55.6697717Z If you'd like to turn off curl's verification of the certificate, use
2022-02-20T10:15:55.6698099Z  the -k (or --insecure) option.
2022-02-20T10:15:55.6698334Z Trying a mirror...
2022-02-20T10:15:55.6698966Z ==> Downloading https://ftpmirror.gnu.org/binutils/binutils-2.38.tar.xz
2022-02-20T10:15:55.6699368Z curl: (60) SSL certificate problem: certificate has expired
2022-02-20T10:15:55.6699700Z More details here: http://curl.haxx.se/docs/sslcerts.html
2022-02-20T10:15:55.6699903Z
2022-02-20T10:15:55.6700080Z curl performs SSL certificate verification by default, using a "bundle"
2022-02-20T10:15:55.6700445Z  of Certificate Authority (CA) public keys (CA certs). If the default
2022-02-20T10:15:55.6700891Z  bundle file isn't adequate, you can specify an alternate file
2022-02-20T10:15:55.6701239Z  using the --cacert option.
2022-02-20T10:15:55.6701541Z If this HTTPS server uses a certificate signed by a CA represented in
2022-02-20T10:15:55.6701913Z  the bundle, the certificate verification probably failed due to a
2022-02-20T10:15:55.6702608Z  problem with the certificate (it might be expired, or the name might
2022-02-20T10:15:55.6702962Z  not match the domain name in the URL).
2022-02-20T10:15:55.6703395Z If you'd like to turn off curl's verification of the certificate, use
2022-02-20T10:15:55.6703743Z  the -k (or --insecure) option.

I don't see ca-certificates being installed, I need to investigate that.

It worked a few months back for the Portable Ruby CI. That should be a good indication whether it still works.

On 20 Feb 2022, at 14:01, Michka Popoff @.***> wrote:

I gave HOMEBREW_FORCE_BREWED_CA_CERTIFICATES, but it did not work.
2022-02-20T10:15:55.6692632Z ##[group]Full fetch binutils --build-bottle output
2022-02-20T10:15:55.6693272Z �[34m==>�[0m �[1mDownloading https://ftp.gnu.org/gnu/binutils/binutils-2.38.tar.xz�[0m
2022-02-20T10:15:55.6693648Z curl: (60) SSL certificate problem: certificate has expired
2022-02-20T10:15:55.6693994Z More details here: http://curl.haxx.se/docs/sslcerts.html
2022-02-20T10:15:55.6694192Z
2022-02-20T10:15:55.6694367Z curl performs SSL certificate verification by default, using a "bundle"
2022-02-20T10:15:55.6694719Z  of Certificate Authority (CA) public keys (CA certs). If the default
2022-02-20T10:15:55.6695162Z  bundle file isn't adequate, you can specify an alternate file
2022-02-20T10:15:55.6695669Z  using the --cacert option.
2022-02-20T10:15:55.6696003Z If this HTTPS server uses a certificate signed by a CA represented in
2022-02-20T10:15:55.6696568Z  the bundle, the certificate verification probably failed due to a
2022-02-20T10:15:55.6696961Z  problem with the certificate (it might be expired, or the name might
2022-02-20T10:15:55.6697295Z  not match the domain name in the URL).
2022-02-20T10:15:55.6697717Z If you'd like to turn off curl's verification of the certificate, use
2022-02-20T10:15:55.6698099Z  the -k (or --insecure) option.
2022-02-20T10:15:55.6698334Z Trying a mirror...
2022-02-20T10:15:55.6698966Z �[34m==>�[0m �[1mDownloading https://ftpmirror.gnu.org/binutils/binutils-2.38.tar.xz�[0m
2022-02-20T10:15:55.6699368Z curl: (60) SSL certificate problem: certificate has expired
2022-02-20T10:15:55.6699700Z More details here: http://curl.haxx.se/docs/sslcerts.html
2022-02-20T10:15:55.6699903Z
2022-02-20T10:15:55.6700080Z curl performs SSL certificate verification by default, using a "bundle"
2022-02-20T10:15:55.6700445Z  of Certificate Authority (CA) public keys (CA certs). If the default
2022-02-20T10:15:55.6700891Z  bundle file isn't adequate, you can specify an alternate file
2022-02-20T10:15:55.6701239Z  using the --cacert option.
2022-02-20T10:15:55.6701541Z If this HTTPS server uses a certificate signed by a CA represented in
2022-02-20T10:15:55.6701913Z  the bundle, the certificate verification probably failed due to a
2022-02-20T10:15:55.6702608Z  problem with the certificate (it might be expired, or the name might
2022-02-20T10:15:55.6702962Z  not match the domain name in the URL).
2022-02-20T10:15:55.6703395Z If you'd like to turn off curl's verification of the certificate, use
2022-02-20T10:15:55.6703743Z  the -k (or --insecure) option.
I don't see ca-certificates being installed, I need to investigate that.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.

I tested locally in the current wheezy container, and I can checkout the current binutils PR, and run either brew fetch/brew install, and no need to do anything special, it will just work. I don't understand why it's different when run in the homebrew-core CI. Except if test-bot is doing something fancy.

Not sure what exactly you mean by not having to do anything special, but installing ca-certificates only works automatically on macOS. We probably need to fix install_ca_certificates_if_needed in lib/tests/formulae.rb to check the environment variable.

What I mean is that you can run:
docker run -it --rm homebrew/debian7
cd /home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/homebrew/homebrew-core/
git remote add pt https://github.com/pthariensflame/homebrew-core
git fetch pt
git checkout binutils-2.38-only
brew fetch -sv binutils OR brew install binutils -svd
and it will just download the source file without complaining.
But doing the same with test bot will complain about broken certificates.

Interestingly if I run brew test-bot binutils inside the wheezy container on my computer, it works. But not on the CI machine.

I had a look at the code, HOMEBREW_FORCE_BREWED_CA_CERTIFICATES is set in wheezy, ca-certificates are pre-installed by our wheezy container. The curl shim in brew are correctly used. I am going to roll back the curl changes we made, I think the issue is elsewhere.

What probably happens is --cleanup removes the ca-certificates installation. We probably want to adjust https://github.com/Homebrew/homebrew-test-bot/blob/master/lib/tests/formulae.rb#L45 to be something like return if DevelopmentTools.ca_file_handles_most_https_certificates? && !Homebrew::EnvConfig.force_brewed_ca_certificates?

Or alternatively adjust DevelopmentTools.ca_file_handles_most_https_certificates? to return false when ca-certificates is needed. This is better, but trickier to do in a generic way.

Do you mean the brew test-bot --only-cleanup-before step that is run on CI? Interesting, did not think about that.
But I tried locally in the wheezy container, and  ca-certificates stays installed.

If you are running locally, I think you need to pass --cleanup for it to actually do destructive cleanup. It is automatically enabled on GitHub Actions.

On 21 Feb 2022, at 18:51, Michka Popoff @.***> wrote:

Do you mean the brew test-bot --only-cleanup-before step that is run on CI? Interesting, did not think about that.
But I tried locally in the wheezy container, and ca-certificates stays installed.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.

Haaa. Ok this was surprising, https://github.com/Homebrew/homebrew-test-bot/blob/261e5e276066e1ec72776111cc60f4df0731678f/cmd/test-bot.rb#L104-L116 is maybe still doing too much magic, and we might want to be more explicit and remove some of these implicit additions. Especially that you don't see in the logs that --cleanup was passed, so it's harder to debug when you don't know what you are doing.
If you want me to cleanup stuff a little bit here, I can do it (will need to adjust some build pipelines but that's fine).
I confirmed with brew list in homebrew-core that the certificates were uninstalled.
I've opened a PR to force the usage/installation of ca-certificates on Debian 7: https://github.com/Homebrew/brew/pull/12907

is maybe still doing too much magic, and we might want to be more explicit and remove some of these implicit additions. Especially that you don't see in the logs that --cleanup was passed, so it's harder to debug when you don't know what you are doing.

I'd rather we leave this as-is, it's more useful to adjust this behaviour rather than have the defaults not make sense on GitHub Actions' ephemeral runners.
Definitely game for having more output that clarifies this behaviour, though.


Test suite created real stuff

I have been having encapsulation issues with Moto on Python 3.7.0.  When I run the test suite with make test and the AWS environment variables set (AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY), I ended up with ~18 ELBs created on my account (though it could have been more, we hit our limit).~ quite a few things created on my account:

ELBs
DynamoDB tables
ECR repos
Subnets, vpcs, etc.
CloudFormation
SES
SQS
SNS

This is with Python 3.7.0 in a virtualenv.
pip install -r requirements-dev.txt

The following packages were installed:
asn1crypto==0.24.0
atomicwrites==1.2.1
attrs==18.2.0
aws-xray-sdk==0.95
backports.ssl-match-hostname==<IP_ADDRESS>
backports.tempfile==1.0
backports.weakref==1.0.post1
beautifulsoup4==4.6.0
boto==2.49.0
boto3==1.9.24
botocore==1.12.24
certifi==2018.10.15
cffi==1.11.5
chardet==3.0.4
click==6.7
configparser==3.5.0
cookies==2.2.1
coverage==4.5.1
cryptography==2.3.1
docker==3.5.0
docker-pycreds==0.3.0
docutils==0.14
ecdsa==0.13
enum34==1.1.6
flake8==3.5.0
Flask==1.0.2
freezegun==0.3.11
funcsigs==1.0.2
future==0.16.0
futures==3.2.0
idna==2.7
inflection==0.3.1
ipaddress==1.0.22
itsdangerous==0.24
Jinja2==2.10
jmespath==0.9.3
jsondiff==1.1.1
jsonpickle==1.0
lxml==4.2.3
MarkupSafe==1.0
mccabe==0.6.1
mock==2.0.0
more-itertools==4.3.0
-e git+https://github.com/spulec/moto.git@2bb3d07e113931df96b98f16be6e4336863509f4#egg=moto
nose==1.3.7
pathlib2==2.3.2
pbr==4.3.0
pluggy==0.8.0
prompt-toolkit==1.0.14
py==1.7.0
pyaml==17.12.1
pycodestyle==2.3.1
pycparser==2.19
pycryptodome==3.6.6
pyflakes==1.6.0
pytest==3.8.2
python-dateutil==2.7.3
python-jose==2.0.2
pytz==2018.5
PyYAML==3.13
requests==2.19.1
responses==0.9.0
s3transfer==0.1.13
scandir==1.9.0
six==1.11.0
sure==1.4.11
urllib3==1.23
wcwidth==0.1.7
websocket-client==0.53.0
Werkzeug==0.14.1
wrapt==1.10.11
xmltodict==0.11.0

I ran (because I knew it would take a while and I wanted a log of failed tests):
make test 2>&1 | tee ~/moto-test-log

I've attached the log.
moto-test-log.txt

Sorry about that. I believe this is a duplicate of https://github.com/spulec/moto/issues/1793. We are still working on a long-term fix. The short-term fix is to downgrade boto3 versions.


refactor: removes double loop of pdml transaction

Refactors the PDML transaction class to have a single loop for resumes / retries.
I tried to simplify as much as possible on the retry logic we were doing on the transaction.
<rant>
Unfortunately with Java 7 it is hard to improve this logic by not using exceptions for that without having to write lots of code. I could not also come up with a good immutable approach that would have better readability.
</rant>

Since this contains a fix for retrying InternalException - EOS, we will wait until the spanner team has reviewed the code before merging.
@skuruppu I could also remove this fix, so that we can merge this right away.

Do you mean that this also contains the change from #360? If that's the case, yeah it would be ideal if we decouple the two fixes.

@skuruppu will remove the fix from here

@skuruppu the fix is removed from this PR


'GepettoVisualizer' object has no attribute 'viewer'

when I run the examples in crocoddyl, this error appeared. But without viewer, it works.

Did you launch the Gepetto viewer in another terminal (with gepetto-gui)?

Oops! Thanks for your help! I forgot to launch Gepetto viewer. It is working now. Thx!


feat: run java process from no-isolated workers

From Gradle 6.0, we can inject ExecOperations to WorkAction instance so we can run java process in worker thread.
This feature needs one consideration: If we launch a process by ExecOperations#javaexec(), we cannot touch its stdout and stderr. So in case of failure, it could be difficult to identify the root cause. I'll keep investigating for workaround.
close #416

#430 will fix the broken build. See  https://github.blog/changelog/2021-01-21-github-actions-short-sha-deprecation/ for detail.


ClickHouse Client Assembly

How to build ClickHouse client? I tried
cmake --target clickhouse-client .
make clickhouse-client

It turns out that target is static library libclickhouse-client.a. As I understand there is no executable target except clickhouse-server and test executables.

clickhouse-client is a symlink to clickhouse binary.
You could create symlink with name clickhouse-client an run it.
clickhouse will decide by program name, what do you want to run.
Also you could run ClickHouse client as clickhouse --client.

@alexey-milovidov Wow! This is very unexpectedly and is not obvious. Thanks.
Is it possible to split clickhouse binary into clickhouse-client and clickhouse-server. The reason is sometimes one needs either client or server but both.

Recently clickhouse-client was separate binary. But it links most of ClickHouse codebase and size of that binary was almost the same as size of clickhouse-server.
Then we needed to add few more binaries - clickhouse-benchmark, clickhouse-local, and decided to make single binary to avoid duplication.
Now we are going to allow to build lite version of clickhouse binary without some parts - for example, without functions, aggregate functions, table engines, etc. It will allow to build more lite binary to use solely as client.


Very interesting

I am guessing you have a patched version the Emporia Energy android app which bypasses certificate issues to be able to inspect the traffic done by the app via a proxy ?

Pretty much. Specifically I have used HttpCanary on a rooted phone. There was some extra work required to get the details needed for authentication.

Thx for the info, I didn't know about HttpCanary, I will give it a try.
I thought a modified apk would be needed - I did that with the Mysa smart baseboard thermostat android app (which also uses AWS Cognito for auth).


iOS Safe Area Bottom Drawer Fix

Attempted to fix this issue: https://github.com/nativescript-community/ui-drawer/issues/9 and updated the Vue demo.
Not sure how proper this fix is.
I created an additional height offset that is Application.ios.window.safeAreaInsets.bottom that adds to the height if it is iOS. Also forced rounding up with ceil because if it rounds down you will see a little bit of the view.

@keerl that actually sounds really nice! could you try in landscape before i merge and release this?

Good call, the same issue happens in landscape mode but now with right/left drawers not bottom. The interesting thing is that there are 2 different landscape modes (top of left side and top on right side) and the safe area offset will be different depending on the way the device is being held. I'll have to experiment with this and figure out the best solution.

That turned out to be easier than I thought. The left/right safe area size are the same when in landscape mode which isn't obvious to see visually with a notch on the phone. Anyways, used the left offset value in landscape mode. Let me know if that works for you.

okay how does that look? checking the orientation now

seems good !


Support for Corsair Glaive

My Corsair Glaive is partially supported as two of the three RGB zones (logo and front) light up, the stripes don't. It would be nice to have it fully supported!

Duplicate of #679


Fix typos and create a version of the tessellator optimization that no-ops on web

This would be required in order to compile to JS

I don't know if there's some nice way to handle this kind of thing when compiling offline so that your web bundle gets paths and your mobile/desktop bundles get vertices...

We need to ship the tessellator too, but I don't think that would be worth doing online  - since the only benefit is that it makes the first render faster


Add functionality to get vision data for the Visual Mesh

This PR

adds the ball directly into our repo from Webots source, and modify it to add segmentation (red)
modifies the field proto, so field lines and green grass are wrapped in separate Solids with segmentation (white and green respectively)
modifies the goal proto, so all posts are wrapped in a Solid with segmentation (yellow) - small poles and large poles are separated into different shades of yellow.
modifies NUgus proto so it has segmentation (blue)
adds the Darwin proto and its controller and modifies the Darwin proto to have segmentation (blue)
adds more robots: Darwin-OP3 and Bit-Bot's Wolfgang robot
Adds a world specifically for collecting vision data
New collect_vision_data controller with some functionality from teleport_controller plus collection of vision data.

Current issues

Need to output Hoc to Lens.yaml
Stop robots intersecting when teleporting (slows down sim a lot)

@LachlanCourt did you mean to remove all of that code and the config file?

@LachlanCourt did you mean to remove all of that code and the config file?

We're moving to use the new teleport controller, but the world file (worlds/vision_collection.wbt) needs to be changed still.

@LachlanCourt did you mean to remove all of that code and the config file?

The teleport_master_controller handles setting the position and rotation now so this controller doesn't need to set it anymore, just needs to grab the current position and rotation when it is set, and then grab the image data

@LachlanCourt did you mean to remove all of that code and the config file?

The teleport_master_controller handles setting the position and rotation now so this controller doesn't need to set it anymore, just needs to grab the current position and rotation when it is set, and then grab the image data. @ysims do you want me to set the world file up so that it will run with the master controller straight away?

Yes, that will need to be done and tested so that it still works as intended. Make sure you are changing vision_collection.wbt not kid.wbt.

Okay I think we done :sweat_smile:


Fix the view logs command

The command was opening the old log path.

I think maybe we can flag this as something an E2E test would have caught?

I think maybe we can flag this as something an E2E test would have caught?

Definitely!


Intermittent Spec failure

Because external_tenant was not being set in the specs we have intermittent failures
Failures:

  1) Portfolio when different tenants try to create portfolios with the same name will pass validation
     Failure/Error: let(:tenant2)           { create(:tenant) }

     ActiveRecord::RecordInvalid:
       Validation failed: External tenant has already been taken
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/evaluation.rb:18:in `create'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/strategy/create.rb:12:in `block in result'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/strategy/create.rb:9:in `tap'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/strategy/create.rb:9:in `result'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/factory.rb:43:in `run'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/factory_runner.rb:29:in `block in run'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/factory_runner.rb:28:in `run'
     # /Users/madhukanoor/.gem/ruby/2.4.4/gems/factory_bot-5.0.2/lib/factory_bot/strategy_syntax_method_registrar.rb:20:in `block in define_singular_strategy_method'
     # ./spec/models/portfolio_spec.rb:3:in `block (2 levels) in <top (required)>'
     # ./spec/models/portfolio_spec.rb:55:in `block (3 levels) in <top (required)>'
     # ./spec/models/portfolio_spec.rb:59:in `block (3 levels) in <top (required)>'

Finished in 3.46 seconds (files took 3.68 seconds to load)
187 examples, 1 failure

Failed examples:

rspec ./spec/models/portfolio_spec.rb:57 # Portfolio when different tenants try to create portfolios with the same name will pass validation

Randomized with seed 2904

Closed via https://github.com/ManageIQ/catalog-api/pull/269


adds middleware support for editor

Proposed changes

Types of changes

[ ] Bugfix (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)

Checklist

[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Closing issues

Fixes #
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

thx @hb90dev for your contribution
some things:

something is wrong with your commits, it removes a lot of file. please rebase it to one, clean commit
what kind of middleware is this? redux i assume? I think its ok to add that api, altough i would consider redux to be an internal detail and we might remove it at some point, so keep that in mind.
maybe you can add proper types for the middleware property

close as it staled


Update local deployment instructions for Kubeflow

Previous instructions included deployment of the entire
Kubeflow stack which ate up system resources. These instructions
will only deploy components necessary to run Kubeflow Pipelines.
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

NOTE: URL in readme is pointing to the PR for testing purposes and must be updated to
github.com/elyra-ai/elyra/etc/kubernetes/kubeflow-pipelines?ref=master prior to merge.


Checkbox validation not working

input data-val="true" data-val-required="There are errors in this field" type="checkbox" name="rules"
Did not find information how to add AddRule for checkboxes...

I had a problem where I needed to use the reverse logic. Specifically, I wanted to check if the user had not checked a checkbox, and if so, add an error class.

@karlisfeldmanis this is possible, you would need to write a custom validation rule, i would take the required rule as a starting point.
for example  you could create something like this:
  addRule('valUnchecked', function (field) {
    return {
          type: 'boolean',
          required: true,
          message: field.dataset.valRequired,
          validator: (rule, value) => !field.checked
        }
    }

I'll put some time aside for updating the docs with some radio/checkbox examples.
Thanks,

Overall, great work!


[sqllogictets] Remove postgres container orchestration

Which issue does this PR close?
Closes https://github.com/apache/arrow-datafusion/issues/5009
Rationale for this change
#4834 added a way to run sqllogictests using postgres 🦾 (kudos to @melgenek )
However, it currently orchestrates the postgres containers with rust test code which means running these tests requires docker to run the (full) datafusion test suit locally
What changes are included in this PR?

Remove container orchestration logic
Implement special support for COPY so it can be run from the postgres tests
Postgres connection configuration is specified by<EMAIL_ADDRESS>environment
Add documentation on how to run with existing postgres container

PG_COMPAT=true<EMAIL_ADDRESS>cargo test -p datafusion --test sqllogictests

Are these changes tested?
Yes, in CI
Are there any user-facing changes?
Not really -- only to other devs

cc @melgenek


Accumulate instructions for inclusion in app for how to record output monitors

For Linux users with PulseAudio we can just say to run this:
pactl \
  load-module module-remap-source \
  master="$(pactl list | grep -A2 '^Source #' |  grep 'Name: .*\.monitor$' | awk '{print $NF}' | tail -n1)" \
  source_name=systemout_monitor \
  source_properties=device.description=System_Audio_Output

For Mac we can consider Black Hole, or hopefully BackgroundMusic, which seems simpler to manage: https://github.com/kyleneideck/BackgroundMusic#recording-system-audio
For Windows we can adapt this tutorial: https://www.howtogeek.com/howto/39532/how-to-enable-stereo-mix-in-windows-7-to-record-audio/

For Background Music we should recommend installing version 0.4.0 https://github.com/kyleneideck/BackgroundMusic/releases/tag/0.4.0-SNAPSHOT-b38f6dd

For Android we can recommend using this app to record a file and then importing it: https://play.google.com/store/apps/details?id=io.sbaud.stereomix
We'll need to note the caveat that some apps prevent any other app recording their audio output, including Spotify and Chrome. Other apps, like VLC, do work.

For iOS we can include instructions for doing this with garage band

This is good for Windows: https://allthings.how/how-to-enable-missing-stereo-mix-option-in-windows-10/


Add an option to list events to Exclude from sending to Customer.io

Currently there's an option to list events to send to Customer.io. Would be great to have another field where we can list events to be excluded from getting sent to Customer.io, including also the option exclude the Identify event (this is good for cases where the person needs to be created using the API).

@davidgreyme walk me through the use case here please?
If you don't want identify events to make it through, doesn't excluding them from the list of events to send to customerio work?


Send invalid token as json object

Send invalidToken as json object

@EmDee I'm not sure what the plugin does internally but it expects a dictionary. I've now adjusted the response to be an json object instead of a plain dictionary. That's how we handle the getNearbyStations call as well

@EmDee I'm not sure what the plugin does internally but it expects a dictionary. I've now adjusted the response to be an json object instead of a plain dictionary. That's how we handle the getNearbyStations call as well

Sounds good. I will play around with it on Android.

@patrickniepel It doesn't seem to work correctly yet. The received data is not a valid JSON:

Works for both Android and iOS now.


Convert another instance of Into impl to From in the macros

An addition to #8900. There was another instance of an Into impl there.
UPD: found two more instances.
This time I checked the branch, and am sure the linter is happy.

bot merge

bot merge


DeleteBehavior Enum Documentation Appears To Be Incorrect

This documentation is unclear.

Cascade and ClientCascade have the exact same definitions.
ClientSetNull NoAction Restrict and SetNull all have the exact same definition, going all the way back to EF Core 2.2.

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

ID: 2df9f508-7992-183c-a909-5b27316e3efd
Version Independent ID: 8e25c165-0abc-9990-ef58-f0ac29c130e3
Content: DeleteBehavior Enum (Microsoft.EntityFrameworkCore)
Content Source: dotnet/xml/Microsoft.EntityFrameworkCore/DeleteBehavior.xml
Product: ef-core-api
GitHub Login: @dotnet-bot
Microsoft Alias: avickers

Duplicate of https://github.com/dotnet/efcore/issues/29261


Bump kernel and framework versions

$subject

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2195674777

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2195674777
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2195742922

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2195742922
Status: failure

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2195742922
Status: success


Runs integration tests with Travis

Running integration test with Travis (bin/build -i)

Merging this without review to unblock travis failures


TypeError: 'undefined' is not an object (evaluating 'Function.prototype.bind.apply')

Hi, when running grunt htmlSnapshot, I'm getting this
Running "htmlSnapshot:all" (htmlSnapshot) task
running html-snapshot task...hold your horses
Warning: error: Error: [$injector:modulerr] Failed to instantiate module ng due to:
TypeError: 'undefined' is not an object (evaluating 'Function.prototype.bind.apply')
...

I searched why I'm getting this error and it was apparently due to the version of PhantomJS, but Function.prototype.bind should work with PhantomJS 2
How can I solve this ?

Hi, I have the same problem...
Running "htmlSnapshot:dist" (htmlSnapshot) task
running html-snapshot task...hold your horses
Warning: error: Error: [$injector:modulerr] Failed to instantiate module ng due to:
TypeError: 'undefined' is not an object (evaluating 'Function.prototype.bind.apply')
Any idea?


Can I also obtain loss while testing and mAP when training

I found that no loss is returned in testing set and no mAP is returned in training set. Are there any apis to modify it?

Please refer to the doc https://mmdetection.readthedocs.io/en/latest/tutorials/customize_runtime.html#customize-workflow


tests: Check return value of settings_runtime_set in ll_settings test

Make sure errors returned by settings_runtime_set are caught.
Fixes #30191
Signed-off-by: Wolfgang Puffitsch<EMAIL_ADDRESS>

@jhedberg @Vudentz Maybe you can have a look at this? Shouldn't take more than 5 minutes to review.

@jhedberg @Vudentz Maybe you can have a look at this? Shouldn't take more than 5 minutes to review.


Test labels in the new GUI

Here is how labels look like in the old GUI:

We should test that these labels are shown in the new GUI.

Superseded by #134


Source code not distributed with library artifacts

Hi 😄 When I import the Serial dependency with gradle, I'm not getting source code included. IDEA shows decompiled bytecode when browsing a class.
Can you add this? Helps when debugging, also when the IDE generates code it's nice to have the real parameter names populated instead of p0 p1 p2 etc.
Thanks!

Hey @damien5314, I tried to reproduce your issue, but couldn't. Can you share a screenshot of the library setup inside Android Studio/IntelliJ? It should look something like this

@amandeepg Can you tell me how to access that window? I couldn't find "Configure Library" but I found "Library Properties" which shows me Sources+Javadoc for other libraries, but not Serial.

I thought it might be that I was using jcenter() instead of mavenCentral() in my build.gradle, but after adding mavenCentral() as my first repository and invalidating caches, it doesn't seem to change anything.
repositories {
    mavenCentral()
    jcenter()
    ...
}

dependencies {
    ...
    implementation("com.twitter.serial:serial:$SERIAL_VERSION") {
        exclude group: 'io.reactivex', module: 'rxjava'
    }
    ...
}

Hmm, coming back to this again, I managed to find sources in my local gradle directory and point the IDE to the right place. So I think there must have been some Android Studio bug causing sources to not be automatically linked. Sorry for the trouble!


Add google sheet link option in settings

Make the google sheet link dynamic so that the user can just update it from settings page which will be created as part of #28

also, if you are following a particular format for time table, then mention it in the settings tab


tooltip can not be 'false'

The tooltip validator only returns true for 'always' and 'hover'. You can't set the tooltip to 'false' as stated in the readme.

It's already updated at https://github.com/xwpongithub/vue-range-slider/pull/9
use :tooltip=false instead of :tooltip="false" or tooltip="false"

Yes. I have the same problem. Temporary solved it by set tooltip-style: {display: "none",}


Redis fetch value issue

Oct 14 08:04:03 debian python[3531]: ERROR:uvicorn.error:Exception in ASGI application
Oct 14 08:04:03 debian python[3531]: Traceback (most recent call last):
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/uvicorn/protocols/http/h11_impl.py", line 404, in run_asgi
Oct 14 08:04:03 debian python[3531]:     result = await app(  # type: ignore[func-returns-value]
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
Oct 14 08:04:03 debian python[3531]:     return await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/applications.py", line 269, in __call__
Oct 14 08:04:03 debian python[3531]:     await super().__call__(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/applications.py", line 124, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.middleware_stack(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 184, in __call__
Oct 14 08:04:03 debian python[3531]:     raise exc
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 162, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, _send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/cors.py", line 84, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 93, in __call__
Oct 14 08:04:03 debian python[3531]:     raise exc
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 82, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, sender)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
Oct 14 08:04:03 debian python[3531]:     raise e
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 670, in __call__
Oct 14 08:04:03 debian python[3531]:     await route.handle(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 418, in handle
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/applications.py", line 269, in __call__
Oct 14 08:04:03 debian python[3531]:     await super().__call__(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/applications.py", line 124, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.middleware_stack(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 184, in __call__
Oct 14 08:04:03 debian python[3531]:     raise exc
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/middleware/errors.py", line 162, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, _send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 93, in __call__
Oct 14 08:04:03 debian python[3531]:     raise exc
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/exceptions.py", line 82, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, sender)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
Oct 14 08:04:03 debian python[3531]:     raise e
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 670, in __call__
Oct 14 08:04:03 debian python[3531]:     await route.handle(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 266, in handle
Oct 14 08:04:03 debian python[3531]:     await self.app(scope, receive, send)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 65, in app
Oct 14 08:04:03 debian python[3531]:     response = await func(request)
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/routing.py", line 231, in app
Oct 14 08:04:03 debian python[3531]:     raw_response = await run_endpoint_function(
Oct 14 08:04:03 debian python[3531]:   File "/usr/local/lib/python3.9/dist-packages/fastapi/routing.py", line 160, in run_endpoint_function
Oct 14 08:04:03 debian python[3531]:     return await dependant.call(**values)
Oct 14 08:04:03 debian python[3531]:   File "./app/routers/setup.py", line 31, in get_status
Oct 14 08:04:03 debian python[3531]:     setupPhase = await redis_get("setupPhase")
Oct 14 08:04:03 debian python[3531]:   File "./app/utils.py", line 64, in redis_get
Oct 14 08:04:03 debian python[3531]:     return v.decode("utf-8")
Oct 14 08:04:03 debian python[3531]: AttributeError: 'str' object has no attribute 'decode'

Originally posted by @benjamin-wilson in https://github.com/rootzoll/raspiblitz/issues/3262#issuecomment-1278925370

In some circumstances redis db does return a string object which can not be decoded. This try except will catch it
https://github.com/fusion44/blitz_api/pull/159

Fixed with #159 - Thanks @ChuckNorrison!


master → main

I've pushed osbuild-composer's main branch (exact copy of master). Once this lands, I'll switch the default branch to main.

I think there is one more place to fix:

Indeed! Thanks for the catch. Pushed a fix.


Problem in downloading via ClipClient

ClipClient not working with num_images more than 1000
I tried this code
client = ClipClient(     url="https://knn5.laion.ai/knn-service",     indice_name="laion5B",     aesthetic_score=9,     aesthetic_weight=0.5,     modality=Modality.IMAGE,     num_images=1000, )

What's the error?
On Thu, Jun 30, 2022, 05:55 Deadsec69 @.***> wrote:

ClipClient not working with num_images more than 1000
I tried this code
client = ClipClient( url="https://knn5.laion.ai/knn-service",
indice_name="laion5B", aesthetic_score=9, aesthetic_weight=0.5,
modality=Modality.IMAGE, num_images=1000, )
—
Reply to this email directly, view it on GitHub
https://github.com/rom1504/clip-retrieval/issues/164, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437QWHAJSKBGUELPN7DTVRULBHANCNFSM52H3THNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This is the error
JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Please share the full error
On Thu, Jun 30, 2022, 09:34 Deadsec69 @.***> wrote:

This is the error
JSONDecodeError: Expecting value: line 1 column 1 (char 0)
—
Reply to this email directly, view it on GitHub
https://github.com/rom1504/clip-retrieval/issues/164#issuecomment-1170871603,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR437WGNM7QMTPBAORHBLTVRVEYLANCNFSM52H3THNA
.
You are receiving this because you commented.Message ID:
@.***>

https://colab.research.google.com/github/rom1504/clip-retrieval/blob/master/notebook/clip-client-query-api.ipynb#scrollTo=iMNCv6Nch652.   I was using this notebook
from IPython.display import Image, display
from clip_retrieval.clip_client import ClipClient, Modality
IMAGE_BASE_URL = "https://github.com/rom1504/clip-retrieval/raw/main/tests/test_clip_inference/test_images/"
`
def log_result(result):
id, caption, url, similarity = result["id"], result["caption"], result["url"], result["similarity"]
print(f"id: {id}")
print(f"caption: {caption}")
print(f"url: {url}")
print(f"similarity: {similarity}")
display(Image(url=url, unconfined=True))
client = ClipClient(
url="https://knn5.laion.ai/knn-service",
indice_name="laion5B",
aesthetic_score=9,
aesthetic_weight=0.5,
modality=Modality.IMAGE,
num_images=100000,
)
  cat_results = client.query(text="an image of a human")
log_result(cat_results[0]) `
` ---------------------------------------------------------------------------
JSONDecodeError                           Traceback (most recent call last)
/usr/local/lib/python3.7/dist-packages/requests/models.py in json(self, **kwargs)
970         try:
--> 971             return complexjson.loads(self.text, **kwargs)
972         except JSONDecodeError as e:
6 frames
JSONDecodeError: Expecting value: line 1 column 1 (char 0)
During handling of the above exception, another exception occurred:
JSONDecodeError                           Traceback (most recent call last)
/usr/local/lib/python3.7/dist-packages/requests/models.py in json(self, **kwargs)
973             # Catch JSON-related errors and raise as requests.JSONDecodeError
974             # This aliases json.JSONDecodeError and simplejson.JSONDecodeError
--> 975             raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
976
977     @property
JSONDecodeError: Expecting value: line 1 column 1 (char 0)
`

ah yes this is a duplicated of #160
you currently can't get 100000 items
if you disable safety and violence and query laion400m it'll be faster
I'll fix it in #160

I met the same error when I use num_images=100. Like this:
client = ClipClient(url="https://knn.laion.ai/knn-service", indice_name="laion5B-L-14", num_images=1000)
Who knows how to solve this ? Thanks!!!


Decide if Python 3.4 is really necessary

Hi there,
Python 3.4 is very bleeding-edge and hard to find pre-packaged. As most or all of your required modules may be already backported (for example enum from Python 3.4 is backported for all version down to 2.7 and found as pip package name enum34 ) it may not be needed, yet.
Setup and therefore adoption would be much easier with more stable and well-established releases of Python3.0+

Python 3.4 is available for all major distributions through their package management system and out for at least 18 months. I would call Python 3.5 bleeding-edge but not 3.4.
This thread contains some details why Python 3.4.

On raspbian you need to compile it from source - but that's pretty simple.
Thanks for the explanation. I see this is well-thought :+1:

Depends on the distribution you are using.


Workspace - More features: Distance rates are not updating on a second device

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: Y
Reproducible in production?: Y
**If this was caught during regression testing, add the test name, ID and link from TestRail:**N/A
Issue reported by: Applause - Internal Team
Action Performed:
Preconditions: Be part of a Control workspace with WS chat enabled

Log in as the admin
Navigate to Settings - Workspace - More features
Navigate to Settings - Workspace - More features on a secondary device with the same account
On the main device, toggle Distance rates on
Refresh the page or navigate back and to the More features again on the secondary device

Expected Result:
It should be updating
Actual Result:
More features: Distance rates are not updating on a second device
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/aa0db9fb-7138-4b16-a626-94c2ad6b2164
View all open jobs on GitHub

We think that this bug might be related to #wave-collect - Release 1
CC @trjExpensify

@CortneyOfstad  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

@lanitochka17 I checked out the video and i don't see the second device. Can they provide a secondary video showing the updating not happening between both devices using Safari? The uploaded video only shows the tail end of the process and only one device. Thanks!

Popping it in with no status while you investigate that, Cortney! CC: @mountiny for vis

@lanitochka17 can you provide an update on the comment here by EOD? Thanks!

Its internal I can handle it, I see where the problem is we changed the name of the variable last minute

PR is up

Updated the flag in all places missed in the Doc too

Thanks @mountiny!

PR is merged, this can be closed


Added CultureInfo.InvariantCulture to the ParameterReader for doubles…

… and integers so the Iges file is read correcly independent of the users systemsettings

@RSchwarzwald-Hexagon I've tagged you on issue #7, when you get a minute can you comment on that?  Thanks!


Getting TypeError: Cannot read properties of undefined (reading 'LANGCHAIN_TRACING')  when using with Nuxt

I followed the docs from here https://js.langchain.com/docs/getting-started/guide-chat to integrate langchainjs with Nuxt 3 client-side website but getting TypeError: Cannot read properties of undefined (reading 'LANGCHAIN_TRACING') error.

I tried adding process.env.LANGCHAIN_TRACING = "true" but this is not working in Nuxt 3
I pushed a test repo to https://github.com/naveennaidu/langchain-text for other members to reproduce the bug.
Please add OPEN_AI_KEY to the .env file to run.
Did anyone else run into a similar issue?

This issue is resolved in v0.0.62. Thanks to @nfcampos
In Discord, He mentioned

Note this seems to be an issue with nuxt, see eg https://github.com/nuxt/nuxt/issues/13264, but in 0.0.62 ive added a workaround for this


Right-alignment of description

This website uses Jekyll theme: minima.
In _config.yml file, a field "description" is mentioned which is shown across all pages.
Issue:
Being a .yml file, how to right-align the contents of the description field?
P.S. If possible, I would like to avoid overriding Jekyll "minima" features.

Solved by updating minima footer.html.
Refer here


Raise MSRV to 1.76

Description
Raise MSRV to 1.76
1.76 is (almost*) 6 months old so this change brings Yew's MSRV to the same as Tokio and Hyper.
* It will be 6 months old by first week of August so not a huge deal at the moment
Checklist

[x] I have reviewed my own code
[x] I have updated tests

I had no major reason other than the fact that this includes lints that use/suppress (cause of unknown lint warning from previous code) and is newer than any before/after rustversion checks that we had

@WorldSEnder another reason for update is allow dependencies to update. Yew takes quite a few dependencies and having those outdated could cause problems


Exclusive min/max schema properties are numbers in OAS v3.1

In OAS v3.1 (via JSON schema 2020-12) the exclusiveMaximum and exclusiveMinimum schema properties are numbers [1] rather the booleans used by the draft included in OAS v3.0 [2].
[1] https://json-schema.org/draft/2020-12/json-schema-validation.html#section-6.2.3
[2] https://datatracker.ietf.org/doc/html/draft-wright-json-schema-validation-00#section-5.3

@EricWittmann , changing this would probably qualify as a breaking change. Do you agree it should be done and can/should it be included before 2.0 is GA?


Only set CompatiblitySocketFactory once

Fix Stackoverflow exceptions due to number of sockets created
@spyhunter99 This should be considered a hotfix as it fixes a critical bug on API <= 19 with encrypted connections.

i'll get a release out asap


Is there a need for something like PreviousValueIndicator?

At the moment there is a PreviousPriceIndicator that returns the previous close price of the time series, but there are no indicators for the previous min, max or open price. I think to receive previous values  (not just regarding prices) is an important thing for building a strategy.
Because of that, I want to discuss if there is a need for an indicator that returns the previous value of another indicator. For an application I have written a similar indicator that returns the nth value of another indicator:
PreviousValueIndicator(Indicator<E>, n)
So for example the previous open price would be:
PreviousValueIndicator prevOpen = new PreviousValueIndicator(openPriceIndicator, 1)
Or the value of an ema indicator two tick ago:
PreviousValueIndicator prevEMA = new PreviousValueIndicator(emaIndicator, 2)
Does such an indicator make sense and is needed or did I not notice another way to get those values?

What about indicator.getValue(index - 1);?

I think this does not work while building a strategy.
E.g. how could i define a rule that is satisfied if close price is higher than previous ticks max price?

Hum I see. Ok for your PreviousValueIndicator(Indicator<E>, n). Please make a PR. Don't forget to document it and add unit tests.

Added in #185


Rework solution api

Renamed the run function to lazy_run
Added tests for lazy_run

While adding them I realized that App may need to be in the library and that these tests cannot run in CI because they depend on the clash dir, which inspired #72
I made another commit to delete the tests which I will revert when we have a way to run these tests in CI

Made all the params and return types as generic as possible.
Removed SuiteRun and replaced it with a call to map() :facepalm:
Refactored App.run slightly

Regarding App
I suggest

Moving App to lib
Moving all the helper functions (functions that do not have a corresponding command) into App
Removing the functions that have commands corresponding to them from App and just having them as regular functions in main.rs (or as part of a Cli type)
Making the App constructor to take a single package_name parameter:let app = App::new("dev.CoCtus.coctus");

This would then separate the responsibility between calling the commands and the helper functions which we could use in tests. It would also prepare for #61 by allowing configuration to be stored in App and be used by users of the lib.

I don't know if the unable_to_run and get_result functions are particularly useful as they can only ever be called from one place but it's whatever.

The purpose was more to make each function easier to skim + group and document what those lines of code were doing.

The behavior change in --timeout needs fixing though.

Done, sorry about that.


Make a new release?

Hello, can you make a new release for PR #7, so other projects can depend on it? Thanks!

I'll publish 0.7 on the next Monday.

0.5.4 is now released sorry for delay 😅


Feature/fix images injection

Add PNG images for easy reading

Maybe we should migrate doc/README.md into the root directory?

Ehm... Makes it pretty bad in pdf. And formulas are still not rendered by github if you want to use its preview

with images injection as PNG directly into the readme without calling PDF images then it's fine and REAME can be placed into root directory.

 I'd just put pdf there

Like, this reads way better to me: https://github.com/curvefi/curve-dao-contracts/blob/master/doc/readme.pdf
Maybe can name it more prominently and put in root

Closing as stale


Whatsapp new code login

With the new update, whatsap web is also using the code for login, is there an update for it? Thank you 💐❤

Waiting for the new update from you 👍

Added in new Version 2.1.1, To login with code, set linkWithPhoneNumber and get code in onPhoneLinkCode callback


Gamut mapping according to Color Level 4

The CSS spec has finally posted their gamut mapping algorithm https://drafts.csswg.org/css-color/#binsearch.
It comes from an approach of SDR colors. What this means is that any colors that exceed 100% lightness or are below 0% lightness are set to white or black respectively. This changes the algorithm some from how we currently implement things.
You no longer have to wait for low and high chroma to converge as you know going into the binary search that all colors will have a suitable lightness and reducing chroma will always get the color into gamut. Before, a lightness out of the 0% - 100% range could produce a color still out of gamut meaning you wanted to continue searching until the low and high chroma converged and the clip the result to be sure you were "in gamut". This is probably more of an HDR gamut mapping approach.
Essentially, we are performing something more of an HDR approach currently, while the CSS spec is keeping things currently as an SDR approach until at some time they deem they've found suitable HDR color spaces with equally suitable gamut mapping.
We should probably provide this SDR gamut mapping approach for those who wish to mimic what browsers do. The differences are significant, but they can be a little different. Basically, if we use the SDR approach, we simply have to return white or black if the color is too light or too dark, and if not analyze the difference between the clipped color (a clipped form of the chroma reduced color) and the current chroma reduced color. If we are able to get the JND below the limit, we can return the clipped color, if not, we continue using the binary search to adjust the chroma until we find an optimal reduction. If we are in gamut, we can try to raise the chroma and if we are out of gamut, we try and reduce the chroma.
In general, using the SDR approach will keep the hue a little more consistent as you never land in a situation where you can't quite reach the JND and have to clip. I'm playing with it right now and will have to make a decision. We may or may not just use SDR for now or may provide both.

So, I've evaluated the SDR algorithm in the CSS spec, and generally, I'm pleased with the results, but there is one thing we are probably skipping, the JND check.
The CSS algorithm requires that when doing the binary search, the chroma compressed color is diffed with a clipped version of that color any time the color is out of gamut when searching for the best chroma. If the JND is less than 0.02 (for Oklch), the algorithm should kick out of the search.
It appears this JND check is supposed to get you out of the loop whenever you get close enough to the best chroma. The reality is that the extra conversions and delta checks add a good deal more overhead. Simply letting the binary search bounds (low and high chroma) converge is not only faster but gives you more accurate colors as sometimes the Oklch color is maybe not quite as close even when it meets this < JND criteria.
Granted, our library naturally has a bit of overhead that the Color class adds with its abstraction and such, so a much leaner approach could maybe shave that down a bit, but I frankly see no real benefit to the JND check. In a gradient, you can see some spots where the colors just aren't as close as they should be, and then unnecessary additional conversions and clipping on every iteration coupled with a delta E check adds very little as removing them is faster and gives better colors.
I'll admit that when I'm talking about more accurate colors gradient, this stands out in some examples where we generate color gradients. But, I'll admit that the disparity is quite subtle and that many eyes may not notice the difference. With that said, considering the algorithm is slower and doesn't seem to offer any improvements related to better gamut mapping, I see no real reason to include the related delta E/JND portion.
Anyways, it is likely we will adjust the default algorithm to follow closer the CSS 4 spec, just minus the JND check.

Correction. I was able to clean up the algorithm and make it much faster. So, using the JND is actually faster, just not that much faster, and the colors are still not mapped as smooth as I'd like.
So, the old algorithm was a bit slow and ran about 3.04 ms on my machine. Though I was able to clean it up and get it down to 2.86 ms.
The CSS 4 algorithm is clocking in at about 1.05 ms, so almost three times faster. Taking out the JND check it clocks in at about 1.14 ms. So slower, but only about 8%. But the colors are a lot closer to the intended color and produce smoother gradients.
So, if having JND was 3X faster like it is compared to the old algorithm, or even 2X faster, maybe it would be worth leaving in, but I'm currently not seeing a massive reason to keep the JND check. I'd rather have colors that produce the best results in this case.

Was able to optimize the JND case down to 930 us, which is a bit better, but still not massive.
You can see how we get some harder transitions with the JND.

But when we let the low and high chroma converge, we get smoother results:

It's possible if we increase the resolution maybe the JND case would smooth out more, but then you are adding back in a performance cost.
So we are weighing better colors vs performance, where the performance increase is now about ~19% per mapped color he main point is that we get better mapping without JND with a difference in speed roughly 930us vs 1.14ms

e


When reducing its radius, the particules might ignore the colliders

Hey,
I'm trying to implement this to have some kind of snow sphere, so I just tried to reduce the gravity and the sizes of the particles; but the particles seems to ignore the wall colliders when its radius is less than 1.
How can we reduce a particle size ?
Best regards,
Sylafrs
(I think I will use a different 'Translation' component to scale the simulation positions)

@sylafrs Did you ever manage to find a way to reduce the size of the particles? I'm running into the same problem.

No, I gave up the idea to use physics for my experience.
Since I wanted a lot of little particles in a sphere, having simple hand-made collisions and gravity made the trick, the particles doesn't have to collide on each other, it still does the trick visually.

No, I gave up the idea to use physics for my experience.
Since I wanted a lot of little particles in a sphere, having simple hand-made collisions and gravity made the trick, the particles doesn't have to collide on each other, it still does the trick visually.

Thank you for your reply.


[Enhancement] Do checkpoint on follower node to relieve memory pressure on leader

Why I'm doing:
What I'm doing:

The current Leader has a Checkpoint daemon thread that continuously checks for new journal dbs. If a new journal db is detected, the following steps are performed:

Create a new GlobalStateMgr and load the local image into the new GlobalStateMgr.
Replay the journal in the new GlobalStateMgr.
Call saveImage to write the metadata in the GlobalStateMgr to disk. At this time, a new image will be generated.
Push the newly generated image to other FE nodes.
Delete the journal that has been replayed in step 2 from the bdb.

The main differences of the optimized process are as follows:

The Leader node is changed from the previous Checkpoint daemon to the CheckpointController daemon, which is responsible for controlling the entire checkpoint process. The check of the new journal db and steps 4 and 5 in the current process need to be completed in the CheckpointController daemon.
A new CheckpointWorker daemon is added to the Follower node, which is responsible for executing the checkpoint tasks sent by the leader, that is, 1, 2, and 3 in the current process.

What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.3
[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@mergifyio rebase