Hack ci

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
alisinabh, @supanadit, @huaigu, @seeplayerone, @xremora, @Fogete, @zhchiEarth, @arnold-almeida, @wuyongyi, @wk0, @TheJellyLand, @kokassa, @kamal-ganwani, @ameya-deshmukh, @foxhlchen, @marc23gold, @FIVIL, @eliomain, @roma-glushko, @heathdutton, @farleylai, @MostPow3rful, @mehtaculous, @Sam-Devs, @ethandaya, @kemalcanbora, @alirazacodes, @scibernix, @gityumin, @ca11ab1e, @phanker, @dsimmons, @Yorxsm, @jcortejoso, @escottalexander, @wuxxin, @Rob-Rychs, @LLrber, @Neroysq, @hexrom, @vinta, @thinkhero, @wwens, @mikulas-mrva, @prefer0ne, @nezlooy, @SOSO-eng, @nickbytes, @armathor, @vladyan18

Blastoff.zone: Claim Your Share of 1 Million Tokens and $500,000!
Congratulations! You've just unlocked an exclusive opportunity to claim your share of 1 million tokens and a staggering $500,000 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500,000 bonus.
Use the "Claim Now" option to secure your tokens and cash in on the rewards.

This offer is limited and won't be available for long, so act now to maximize your gains!
Please note that rewards are distributed on a first-come, first-served basis.


Add tag property-based-testing

I was browsing this on GH and I thought it was strange that SwiftCheck wasn't appearing.
But of course it was. It didn't have this tag. I think it could use it, what do you think? :)
PS: sorry for the unfinished posting, it was a misstap. Now it's complete

Done. Thanks for the suggestion!


missing a tip about free space of  /mnt

[Enter feedback here]
This document states that / (root) requires at least 5 GB of free space, but there is no note about /mnt free space.
https://learn.microsoft.com/en-us/azure/machine-learning/concept-compute-instance?view=azureml-api-2#compute-target

The compute instance has 120GB OS disk. If you run out of disk space and get into an unusable state, please clear at least 5 GB disk space on OS disk (mounted on /) through the compute instance terminal by removing files/folders and then do sudo reboot.

However, if /mnt free space is less than 955 MB (1,000,000,000 bytes), a warning message appears and the VM will not boot if you stop it. As shown in the image below, the message indicates that / (root) free space is less than  5 GB, which is incorrect. Please correct the documentation.

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

ID: 5431c3cc-af53-d7d5-4241-cf3d23d8689e
Version Independent ID: 1b7eedd5-e934-aa15-d5c7-32ad82e45bbf
Content: What is an Azure Machine Learning compute instance? - Azure Machine Learning
Content Source: articles/machine-learning/concept-compute-instance.md
Service: machine-learning
Sub-service: core
GitHub Login: @jesscioffi
Microsoft Alias: jcioffi

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

@jesscioffi
Could you please review add comments on this, update as appropriate.

@damochiz
Thank you for bringing this to our attention.
I've delegated this to content author @jesscioffi, who will review it and offer their insightful opinions.

Hello any update on this issue?


Modify index.html page to only contain the app outside drupal

The create-create-app scripts generate multiple files that we need to place in one html document for the Drupal environment.

[x] Generate an html template with the necessary tags
[x] Test pasting in the generated js and css to this template and create a draft in Drupal
[x] Create etc folder at the top level
[x] Create drupal-template.html file with scripts and css

@j-tafoya - this PR is ready for review 🔍


Spidercoordinator: It able to get CIDR from kubeadm-config

If the kube-controller-manager Pod is running as systemd process rather than Pod, In this case, We can't get the CIDR from the KCM Pod. We can get the CIDR from the kubeadm-config configMap.
Thanks for contributing!

What type of PR is this?

release/bug

What this PR does / why we need it:
Kube-controller-pod is running as systemd process rather than a pod, We can't get the cluster CIDR in this case.

We get the clusterCIDR from kubeadm-config ConfigMap first.
If kubeadm-config ConfigMap does exist in cluster, we can get it from kube-controller-manager.

Which issue(s) this PR fixes:

Fixes https://github.com/spidernet-io/spiderpool/issues/3054
Special notes for your reviewer:

there are so many cases already and it is import . Is it possible to design relevant E2E cases to long term test ?
and it could finish https://github.com/spidernet-io/spiderpool/issues/2905 as well recently in another PR

#2927 is some E2E cases for spidercoordiantor, we can also add a case for these changes: delete the kubeadm-config configMap and see if works, but we can't delete kube-controller-manager pod, it's so dangerous. It can be finished in #2905.

do you already have two cases to get CIDR from configmap and pod yaml separately ?

I suggest to finish the E2E together for verification

I suggest to finish the E2E together for verification

is there any update

is there any update

Still working on this

/cc @weizhoublue


[Suggestion] Adding a "new" badge next to latest shadcn-ui things

Hi,
I really appreciate this repository and the wealth of resources it offers on ShadcnUI. However, I often find myself spending a lot of time trying to understand what's new and what's been there for a while. I was thinking that it might be helpful to add a date of addition or a "new" badge to make it easier to identify recent updates. I understand that this would involve extra work, but I wanted to suggest it anyway.

Hi,
I really appreciate this repository and the wealth of resources it offers on ShadcnUI. However, I often find myself spending a lot of time trying to understand what's new and what's been there for a while. I was thinking that it might be helpful to add a date of addition or a "new" badge to make it easier to identify recent updates. I understand that this would involve extra work, but I wanted to suggest it anyway.

I reopened this issue https://github.com/birobirobiro/awesome-shadcn-ui/issues/55 to discuss better how the README layout would look and how to make the new badge disappear after a while.


V2.1+ Upgrade ansi-regex

ToDO:
Upgrade ansi-regex (in it's own feature branch - called 'ansi-regex-upgrade')
Once tested that nothing broke- push to /develop/

Normally, We can use the npm (node package manager) command to upgrade the project or fix security vulnerabilities in the dependencies list.
In order to find potential vulnerabilities in the repo.
we can use the npm audit command.
Also, the Github security policy can also notify you.
The solution is for such problem:
https://docs.npmjs.com/cli/v8/commands/npm-update


Add BTicino Dimmer switch

Hello,
I am using a cc2531 flashed with CC2531ZNP-Prod from CC2531_DEFAULT_20190608.zip and homebridge-zigbee-nt v1.1.1 (v1.1.2 and 2.0 won't load because of #78). I am trying to pair a Legrand "Dimmer switch with neutral" (BTicino dimmer-interruttore connesso Living light N4411C) which is supported by zigbee-herdsman-converters but somehow doesn't get recognized properly. Event tried shortening the distance (to 10cm) but nothing changed.
Zigbee: allowing new devices to join.
Accepting joining whitelisted device '0x0004740000a2101e'
[1/17/2021, 16:31:15] [ZigBee] Interview progress started for device 0x0004740000a2101e
[1/17/2021, 16:31:16] [ZigBee] Device announce: 0x0004740000a2101e (undefined -  Dimmer switch with neutral
)
[1/17/2021, 16:31:17] [ZigBee] Found ZigBee device:  Device {
ID: 2,
_type: 'Router',
_ieeeAddr: '0x0004740000a2101e',
_networkAddress: 25219,
_manufacturerID: 4129,
_endpoints: [
Endpoint {
ID: 1,
profileID: 260,
deviceID: 256,
inputClusters: [Array],
outputClusters: [Array],
deviceNetworkAddress: 25219,
deviceIeeeAddress: '0x0004740000a2101e',
clusters: [Object],
_binds: [],
_configuredReportings: [],
meta: {}
},
Endpoint {
ID: 242,
profileID: undefined,
deviceID: undefined,
inputClusters: [],
outputClusters: [],
deviceNetworkAddress: 25219,
deviceIeeeAddress: '0x0004740000a2101e',
clusters: {},
_binds: [],
_configuredReportings: [],
meta: {}
}
],
_manufacturerName: undefined,
_powerSource: undefined,
_modelID: ' Dimmer switch with neutral\u0000\u0000\u0000\u0000',
_applicationVersion: undefined,
_stackVersion: undefined,
_zclVersion: undefined,
_hardwareVersion: undefined,
_dateCode: undefined,
_softwareBuildID: undefined,
_interviewCompleted: false,
_interviewing: true,
meta: {},
_lastSeen:<PHONE_NUMBER>363,
_linkquality: 0
}
[1/17/2021, 16:31:17] [ZigBee] Unrecognized device: 0x0004740000a2101e undefined Dimmer switch with neutral
Zigbee: disabling joining new devices.
(while I'm here: the device's manual says it comes out of the box in "switch" mode and needs to be set as dimmer - does anyone know if will this be possible once paired? thanks)

This device is still not supported by the plugin. It is essentially a light with a brightness support. With version 2.0 of the plugin you will be able to configure this device by yourself through the configuration. Please wait some day until 2.0 is out

This device is still not supported by the plugin. It is essentially a light with a brightness support. With version 2.0 of the plugin you will be able to configure this device by yourself through the configuration. Please wait some day until 2.0 is out

v2.0.0 is now out. Can you try adding this to the plugin configuration?
            "devices": [{
                "manufacturer": "BTicino",
                "models": [
                  "L441C/N4411C/NT4411C"
                ],
                "services": [{
                     "type": "bulb",
                     "meta": {
                         "brightness": true
                     }
                }]
            }]

v2.0.0 is now out. Can you try adding this to the plugin configuration?
            "devices": [{
                "manufacturer": "BTicino",
                "models": [
                  "L441C/N4411C/NT4411C"
                ],
                "services": [{
                     "type": "bulb",
                     "meta": {
                         "brightness": true
                     }
                }]
            }]

Installed 2.0.0 and added the devices stanza to the plugin configuration but unfortunately the pairing request doesn't show up anymore (not a range issue since zigbee2mqtt acknowledges the request and accepts it).

Installed 2.0.0 and added the devices stanza to the plugin configuration but unfortunately the pairing request doesn't show up anymore (not a range issue since zigbee2mqtt acknowledges the request and accepts it).

Sorry, maybe the device already paired? Can you check though the Web UI? Also, make sure the permit join switch is turned on when you init the pairing process.
Attach logs of homebridge startup please

Sorry, maybe the device already paired? Can you check though the Web UI? Also, make sure the permit join switch is turned on when you init the pairing process.
Attach logs of homebridge startup please

Will be available in v2.0.2

Will be available in v2.0.2


Please clarify if this is a fork or the same project

Hi!
The original webpage at https://swtch.com/drawterm/ has not been touched in years, and has many broken links, including the link to the source code. I see this repository has more recent changes, but the Readme file still points to swtch.
Is this the new official source for drawterm, or just a private fork?
Thanks

Hi,
Russ Cox maintained drawterm as a Mercurial repository on Bitbucket until 2014. During the last couple of years, I was the only contributor.
In December 2014, Go moved from Mercurial to Git. Consequently, Russ Cox moved most of his projects from Mercurial to Git and from Bitbucket or GitHub. However, drawterm was left in place, probably due to lack of time and interest. Few months later, Google Code was shut down, so it wasn't possible to review contributions on Rietveld anymore.
In my side, I took Russ Cox's Mercurial repository from Bitbucket, converted it to Git, put it on GitHub and continued to contribute to it as I used to. I've also reviewed and merged changes from other contributors.
This drawterm repository is really a continuation of Russ Cox's repository. Russ Cox's repository on Bitbucket isn't maintained anymore and this one is still maintained and accepting contributions.
Recently, the people from 9front forked drawterm to include their own changes (mainly support for the dp9ik protocol) and started from this repository as a reference.
While this repository isn't strictly the official repository, I would now consider it pretty much as the official repository.

@0intro, Thanks for the explanation!
In this case, I will make the Debian package point to this repository, and upgrade to the latest commit. I presume you are not intending to cut releases?

One thing you could do to make this less ambiguous is to change the readme to stop pointing to http://code.swtch.com/drawterm, as that is what made me think this was just a personal fork.

I've removed all references to code.swtch.com from the README.


Bump tokens version

https://github.com/palantir/auth-tokens/releases

This change is

are 1.0.0 and 1.2.0 binary&source - compatible?

ping, is this still needed?

It's not worth the effort for me to determine if they're both binary and source compatible vs trusting semver, so closing.


SimulateLocationUpdate return InvalidService error

hi, I ran the example code of SimulateLocation but return error as below
2021/06/12 01:07:39 receive packet: InvalidService

Here is my code and iOS version is 14.0.1
package main

import (
	"log"

	giDevice "github.com/electricbubble/gidevice"
	"github.com/electricbubble/gidevice/pkg/libimobiledevice"
)

func main() {
	libimobiledevice.SetDebug(true)

	usbmux, err := giDevice.NewUsbmux()
	if err != nil {
		log.Fatalln(err)
	}

	devices, err := usbmux.Devices()
	if err != nil {
		log.Fatalln(err)
	}

	if len(devices) == 0 {
		log.Fatalln("No Device")
	}

	d := devices[0]

	// https://developer.amap.com/tools/picker
	// https://lbs.qq.com/tool/getpoint/index.html
	if err = d.SimulateLocationUpdate(113.925734, 22.511836, giDevice.CoordinateSystemWGS84); err != nil {
		log.Fatalln(err)
	}
}

I tried to debug this program and found it break at this function
func (c *lockdown) startService(service string, escrowBag []byte) (dynamicPort int, enableSSL bool, err error) {
	req := c.client.NewStartServiceRequest(service)
	if escrowBag != nil {
		req.EscrowBag = escrowBag
	}

	var pkt libimobiledevice.Packet
	if pkt, err = c.client.NewXmlPacket(req); err != nil {
		return 0, false, err
	}

	if err = c.client.SendPacket(pkt); err != nil {
		return 0, false, err
	}
        // returned error InvalidService
	respPkt, err := c.client.ReceivePacket()
	if err != nil {
		return 0, false, err
	}

	var reply libimobiledevice.LockdownStartServiceResponse
	if err = respPkt.Unmarshal(&reply); err != nil {
		return 0, false, err
	}

	if reply.Error != "" {
		return 0, false, fmt.Errorf("lockdown start service: %s", reply.Error)
	}

	dynamicPort = reply.Port
	enableSSL = reply.EnableServiceSSL

	return
}

Any Suggestion?

Maybe you didn’t let your device mount first (it only needs to be executed once after the iOS system is started) developer image
Maybe you didn't let your device mount the developer image first.

It only needs to be executed once after the iOS system is started

MountDeveloperDiskImage

Maybe you didn't let your device mount the developer image first.

It only needs to be executed once after the iOS system is started

MountDeveloperDiskImage

Awesome! It works!
Thanks for replying.


Fix HTML-encoded characters (part 2)

@MSDN-WhiteKnight : Thanks for your contribution! The author(s) have been notified to review your proposed change.


fix(links): replace http:// links with https://

While browsing the demo, I noticed that some assets could not be loaded because they were served over http://.
This pull request fixes most of those warnings/errors, except for the following 4 assets which are not available under https://:
http://weloveiconfonts.com/api/?family=zocial
http://web.arjentienkamp.com/codepen/tinder/delete.png
http://web.arjentienkamp.com/codepen/tinder/heart.png
http://web.arjentienkamp.com/codepen/tinder/info.png
You might want to consider including them in the repo or hosting them somewhere where they are accessible through https.
PS: Could you please add the link to your demo to the repo description at the top of the repo? It always takes me some seconds to find the link ;).

Hey @AndreasGassmann, thank you so much for your contribution! Really well noted. I'll solve these issues in no time!
Thanks once again!


Markdown syntax highlighting for text with strikethrough

This PR fixes #43504.

[x] Add strikethrough formatting to markup.strikethrough tokens.
[x] Sync Markdown grammar with microsoft/vscode-markdown-tm-grammar#101.

This was implemented by @mjbvz and more cleanly too

Ah sorry I missed that you also opened this PR. Sorry for duplicating your work here :(

No worries, I'm credited in the other pull(s)


feat: Transfer token in EOA

Feature Request
Describe the Feature Request
When a user (an EOA) sends a transaction with value, we need to send this value...
Describe Preferred Solution
The entrypoint of an EOA triggered tx is the __execute__ function of the EOA contract.

get kakarot native token address IKakarot.get_native_token
get value to be send in tx field, and tx target
call IERC20.transfer(native_token_address, target, value)

Related Code
This issue needs to be tackled after https://github.com/sayajin-labs/kakarot/issues/442 is merged

I will take this one.

I will take this one.

you'd need to wait for the #442 before being able to work on this

@FranFiuba #498 has been merged so you can work on this!

Is this one free ? If so I can take it :)


[BUG]: LLM Providers parameters are not saved consistently

How are you running AnythingLLM?
Docker (remote machine)
What happened?
Running AnythingLLM on hosted version in Railway thanks to the deployment template (thanks!)
Parameters are not saved consistently which is quite an annoyance if you switch frequently LLM models to compare them
For example:

OpenAI : the API key is saved but the other parameters are not
LocalAI : the API key is saved but the other parameters are not
Perplexity: the API key is not saved but the other parameters are
Openrouter: none of the parameters are saved
Groq: perfect, all parameters are saved!

I haven't tried the other LLM providers.
Are there known steps to reproduce?
No response

The parameters are not saved at all? Or are not saved between restarts?

The parameters are not saved at all? Or are not saved between restarts?

For example, I set up parameters for Openrouter and go test the LLM in a workspace.
I go back to the settings to switch to set up Openai parameters and go try the LMM in a workspace.
I go back to the settings to switch back to Openrouter and all parameters are gone.
I just tried Azure OpenAI and all parameters are also not saved when switching back and forth different settings.
My Railway instance is set up to never go to sleep, and I never restart the instance.

Oh, this is actually normal. It ties back to a legacy reason as to why it happens but I agree that it is not an "ideal" behavior. I think we can make this change now given the current state of the codebase. So not a bug, but really a feature that would make toggling between providers not so much of a headache 👍


remove style when output is sent to file

when doing lfs> some-file.txt, the output should be style less.

done in 0.7.4


Feature management samples and docs

Description
Adds Documentation and Examples of Feature Management

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b41a4ab). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #545   +/-   ##
=========================================
  Coverage          ?   55.73%
  Complexity        ?      730
=========================================
  Files             ?      175
  Lines             ?     3147
  Branches          ?      195
=========================================
  Hits              ?     1754
  Misses            ?     1269
  Partials          ?      124

Continue to review full report at Codecov.

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


Update bwc verions for (#2237)

Description
Update the bwc versions for #2237 since it was backported to 1.3.
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] New functionality has been documented.

[X] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@nknize @reta final PR updating bwc versions now that backport was merged


Inconsistent evaluation of unification?

What version of CUE are you using (cue version)?

$ cue version
cue version 0.4.0-beta.1 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
Given the files below

-- test1.cue --
#T: {
  a?: int

  isA: a != _|_
}

d: #T & {a: 56}
e: #T

-- test2.cue --
#T: {
  a?: int

  isA: a != _|_
  valid:  isA & true
}

d: #T & {a: 56}

-- test3.cue --
#T: {
  isa: bool

  valid: isa & true
}
d: #T & {a: 56}

I ran cue export test1.cue, cue export test2.cue and cue export test3.cue, consecutively.
What did you expect to see?
The output of the first export:

{
    "d": {
        "a": 56,
        "isa": true
    },
    "e": {
        "isa": false
    }
}

The output of the second export

{
    "d": {
        "a": 56,
        "isa": true
        "valid": true
    }
}

The output of the third export:

{
    "d": {
        "isa": true
       "valid": true
    }
}

What did you see instead?
The output of the first export:

{
    "d": {
        "a": 56,
        "isa": true
    },
    "e": {
        "isa": false
    }
}

The output of the second export

#T.valid: conflicting values true and false
...

The output of the third export:

{
    "d": {
        "isa": true
        "valid": true
    }
}

Which in my opinion is inconsistent, as I will explain in what follows.
Export of test1.cue
Here, on the one hand,  as d provides a value for a, a is not bottom in d, and isa==true, as expected.
On the other hand, as e does not provide a value for a, a is bottom in e, and we get isa==false.
All very intuitive and expected!
Export of test2.cue,
Here, all we introduce is field valid which should be valued as the result of unifying
field isa and value true.
We also remove top-level field e to avoid producing an error.
Thus, the intuitive result is that the unification for field valid will depend
on the value of field isa, which, for top-level field d is true as seen in the export of test1.cue
However we get the error reported above!
It looks like the unification for valid does not wait to evaluate isa!!
This is puzzling,... and, in the light of the next export, inconsistent.
Export of test3.cue
In here, field isa is not computed, which seems to make a huge difference, as now, unification
seems to wait until the value of field isa is available before passing judgment.

But the result of comparing against bottom is always defined

@kumorid I think this is the key statement in @mpvl's response.
One strange thing I have observed however:
a1: {
    a: int
    b: a != _|_
}

a2: {
    a: 5
    b: a != _|_
}

a3: a1 & a2

evaluates to:
a1: {
	a: int
	b: false
}
a2: {
	a: 5
	b: true
}
a3: {
	a: 5
	b: true
}

(playground)

Hi @myitcv,
I assume by defined you mean defined with a concrete boolean value.
Yes, comparing against bottom is always defined, no argument about it, the question is "when" a particular concrete value is committed to.
If it is committed to before even unification happened (which clearly it is not, as my testx.cue exemplify) it would seem to be of dubious use.
Going to your example: yes, it is strange.
Clearly, field b in a1 is defined, albeit only as an int, with no concrete int value, but definitely, not bottom.
So, that looks like a bug to me.
Maybe comparison to bottom is trying to do too many things: report when a field cannot get any value AND report when a field does not exist, and this gives some trouble (just a speculation).
In our application, I believe all cases of comparing against bottom are to check existence of a particular field.
And commitment to a particular boolean value takes into account unifications.

Maybe comparison to bottom is trying to do too many things: report when a field cannot get any value AND report when a field does not exist, and this gives some trouble (just a speculation).

That is indeed the case, which is one of the mains reasons for https://github.com/cuelang/cue/issues/943

@kumorid: solving the processing time for disjunction problem is high on the agenda. It is a bit work, but it will consist of several solutions that each will have a big impact.

In my opinion, the error for test2 should NOT appear, as the value of isa is just bool,

The value of isa is not just bool in test2: it is bool &  a != _|_, where a != _|_ evaluates rightfully to false. Note that the failure does not occur at d.valid, where a != _|_ evaluates to true, but at #T.valid, where it doesn't.
Note that comparison against bottom checks whether the field is present and whether it is concrete. Optional fields (those with ?) are NOT considered to be present, so it evaluates to false. It doesn't matter whether or not the value is concrete. This is perhaps one of the surprising things about optional fields, and one of the reason for the desire to get rid of them (see required field proposal). Note that foo?: bool is a shorthand for ["foo"]: bool, which maybe is more intuitive as to what it means.
Also, the semantics of comparators require that their operands be concrete.
So all in all, it is working as intended, that is not to say it is an ideal interpretation.
The core builtins proposal is supposed to clean up the semantics of comparing against bottom.
Another unfortunate thing: we ignore any errors in definitions that could be resolved by making a definition more specific ("incomplete" errors). So your test case 2 seems to satisfy this condition and thus it could arguably be expected that it does note result in an error. However, in this case, that mechanism does not apply as comparison against bottom is considered completed. Maybe we can find a way to carry the potential incompleteness forward and not fail in this case as well. That would be a language change, but arguably an improvement and not very impactful from a compatibility standpoint.
So leaving this open for now.

Thanks, @mpvl - I've now wrapped my head around where my thinking was wrong. Your explanation above makes sense, and emphasises even more strongly the importance of #943.

@mpvl , Thanks for your post, it explains the behavior observed...
A different question is whether that behavior is the best one could hope for.

The value of isa is not just bool in test2: it is bool & a != |, where a != | evaluates rightfully to false. Note that the failure >
does not occur at d.valid, where a != | evaluates to true, but at #T.valid, where it doesn't.

But, an export is not interested in #T by itself, so, it is not clear to me why cue is behaving as if I wanted #T to be exported.
I suppose this is a consequence of the decision that a bottom produces a fatal error as soon as it shows up as the value of a field.
In that case, I would be very much in favor of acting as I believe you suggest in your last paragraph, as the present behavior is confusing when compared with how everything else behaves, and gives the impression that  CUE's main property (irreversible constraints) is not preserved: the behavior observed seems to indicate that field isa goes from false in #T to true in d, because CUE makes the decision to abort execution because of that!
I assume the proposed builtin, must, does not produce such short-circuit behavior, so that I could use something like

-- test2.cue --
#T: {
  a?: int
  isa: bool
  isa: exists(a)
  must(isa)
}

d: #T & {a: 56}

And get the expected output after cue export test2.cue

{
    "d": {
        "a": 56,
        "isa": true
    }
}

instead of an error  at #T.

This issue has been migrated to https://github.com/cue-lang/cue/issues/964.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Crash when trading with wandering trader on latest version

My game crashes whenever I trade with a wandering trade. attached is the full error log.
Tried reverting to the previous version of the mod. Here my game doesn't crash, but the option to buy claims isn't there.
Modlist. All running their latest versions:

Owo lib (https://www.curseforge.com/minecraft/mc-mods/owo-lib)
Libz (https://www.curseforge.com/minecraft/mc-mods/libz)
Open parties and claims (https://www.curseforge.com/minecraft/mc-mods/open-parties-and-claims)
Cloth Config api (https://www.curseforge.com/minecraft/mc-mods/cloth-config)
Numinasticclaim (https://www.curseforge.com/minecraft/mc-mods/numismaticclaim)
Forge config api port (https://www.curseforge.com/minecraft/mc-mods/forge-config-api-port-fabric)
numinastic overhaul (https://www.curseforge.com/minecraft/mc-mods/numismatic-overhaul)
Fabric api

Top portion of the log:
---- Minecraft Crash Report ----
// Uh... Did I do that?
Time: 2023-03-28 19:28:29
Description: Rendering screen
java.lang.NullPointerException: Cannot invoke "net.numismaticclaim.access.VillagerAccess.isNumismaticClaimTrader()" because the return value of "net.numismaticclaim.access.VillagerAccess.getCurrentOfferer()" is null
at net.numismaticclaim.screen.widget.ClaimTab.shouldShow(ClaimTab.java:22)
at net.libz.util.DrawTabHelper.drawTab(DrawTabHelper.java:41)
at net.minecraft.class_465.handler$zkf000$libz$renderMixin(class_465.java:736)
at net.minecraft.class_465.method_25394(class_465.java:177)
at net.minecraft.class_492.method_25394(class_492.java:177)
at net.minecraft.class_757.method_3192(class_757.java:881)
at net.minecraft.class_310.method_1523(class_310.java:1177)
at net.minecraft.class_310.method_1514(class_310.java:768)
at net.minecraft.client.main.Main.method_44604(Main.java:244)
at net.minecraft.client.main.Main.main(Main.java:51)
at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:462)
at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)
Full log:
crash-2023-03-28_19.28.29-client.txt

Thanks for the report, fixed with https://github.com/Globox1997/NumismaticClaim/commit/a389a666a651a468f2784bd877ae31f68f97b84a


Allow options object for sqlitePlugin

What would be the best way to switch to the recommended method to open a database with the options object?
See: https://github.com/brodysoft/Cordova-SQLitePlugin#opening-a-database
I created a branch and a new method to try it out. Works fine in my project, and I can now use prepopulated databases that are distributed with the app.

Added pull request #653

This issue should be fixed, the current code behaves bad when used as shown in the documentation - passing the object to $cordovaSQLite.openDB leads to using a JSON string built from this object to be used as a filename for the database. This leads to various problems and makes it impossible to open a SQLCipher database properly.


Update 1_lagrangian_mechanics.md

First, thank you for documenting your work online! I've been going through SICM lately, too, and I'm sure these material will be very helpful. I do think, however, that this 'optimisation' to reduce the number of dimensions is a bit quick. A juggling pin spinning around its central axis will behave differently from one which is stationary, just like how a spinning bicycle wheel behaves differently from a stationary one.

The same goes for the answers to questions e and f. I think the top always has three degrees of freedom regardless of its shape.

I took a go at Exercise 1.6 just now. I think your solution does not necessarily fix the endpoint velocities, because the two extra points you added are passed to Lagrange-interpolation-function together with the other intermediate points in the call to make-path, so the resulting path will still have undetermined endpoint velocities. One can still say that the endpoints are 'constrained', but only in a very weak sense.
Below is my code which constructs a piecewise path where the initial and final segments are forced to be straight lines defined by extra parameters t0*, q0*, t1*, and q1*.
(define (((parametric-path-action* win) L t0 q0 t0* q0* t1* q1* t1 q1) qs)
  (let* ((curve (make-path t0* q0* t1* q1* qs))
	 (path (lambda (t) (cond ((< t t0*) (+ q0 (* (- t t0) (/ (- q0* q0) (- t0* t0)))))
				 ((> t t1*) (+ q1 (* (- t t1) (/ (- q1* q1) (- t1* t1)))))
				 (else (curve t))))))
    ;; display path
    (graphics-clear win)
    (plot-function win path t0 t1 (/ (- t1 t0) 32))
    ;; compute action
    (Lagrangian-action L path t0 t1)))

(define (find-path L t0 q0 t0* q0* t1* q1* t1 q1 n)
  (let ((initial-qs (linear-interpolants q0* q1* n))
	(win (frame 0 :pi -1.2 1.2)))
    (let ((minimizing-qs
	   (multidimensional-minimize
	    ((parametric-path-action* win) L t0 q0 t0* q0* t1* q1* t1 q1)
	    initial-qs)))
      (make-path t0* q0* t1* q1* minimizing-qs))))

If I run the new make-path on a free particle
(find-path (L-free-particle 3.) 0. 1. 0.5 1.1 (- :pi 0.5) -1.1 :pi -1. 4)

I get

which shows that the optimiser does not care about jump discontinuities in the velocity.
I also ran this on the L-harmonic Lagrangian and obtained these curves:

@dpgao , somehow I was not subscribed to notifications on my own repository, and missed this! Apologies, I feel terrible for letting this languish for month.
Your answer to 1.6 is way better than mine; you can probably see that I was flailing to justify what I was seeing, instead of understanding this problem.
This is awesome. Do you mind if I incorporate this change into the .org file, with credit to you, of course?

This is awesome. Do you mind if I incorporate this change into the .org file, with credit to you, of course?

Not at all. You’re welcome!

I'll pull this in soon as I tidy up this repository!


League and country rotation checkbox (ENHANCEMENT)

First of all, congratulations and thanks for this tool. It's a great job, and the bot is even better than some paid tools !
If it's possible, i would like the possibility to rotate a filter between the 5 best league (1er league, Ligue 1, Seria A, La Ligua, Bundesligua) and the 8 best countries (France, English, Brazil, German, Italy, Spain, Netherland, Portugal, Argentine) without having to create so many filters for each. Just a checking box to select countries or/and leagues.
Thanks in advance

As you said you need to create different filters for this, having options like these will start confusing other users


Ability to STOP or CANCEL long draw operations

Request from Andy Cook:
Also, a ‘STOP’ button would be useful, when visit gets stuck in an endless calculation with yellow variables.

This is really hard to do. We should remove the button, since it gives the illusion that it's possible.


Fill JWT Claims Correctly

In the Usermgmt Service we create a JWT Token. This Token should contain more claims, which still has to be implemented.
Also we need to use the Spring Mechanism of setting the Authentication for the SecurityContext when we receive a JWT in a Service. In this Authentication Object we somehow have to make the JWT Claims accessible. Then in each request we can autoinject a object coming from the Authentication using @AuthenticationPrincipal
If this is confusing, have a look at the class AuthToken and JWTAuthenticationFilter in the Common Project.

This Issue should be done now. I added FirstName, LastName, UserId and Role to the JWT Claims.
They are automatically "parsed" in the JWTAuthenticationFilter.
If anyone wants to use the provided Claims, just add "@AuthenticationPrincipal UserInformation user" as parameter to an authorized Endpoint. Spring will try to retriev the Information from the Authorization Header of a request. If this header is not provided, an error is automatically returned.
The Claims are added in JWTHelper (service-usermgmt).
If you want to add more claims, just add them there and be sure to also make them available in the UserInformation Class.


feat(scheduling): Price devices distinctively in scheduling

[x] I agree to contribute to the project under Apache 2 License.
[x] To the best of my knowledge, the proposed patch is not based on a code under GPL or other license that is incompatible with FlexMeasures

Based on issue #618 and discussion #615

And the PR title could be more informative, as well :)

Hi @victorgarcia98 . I have made the changes you suggested in the latest PR. I have added the new index dimension 'p' ,denoting the set of price sensors ,to the variables and parameters.
'model.d' and 'model.p' work differently here,according to my understanding and thus added the new index dimension.
After making the changes, I created the schedule using the API endpoint which gave me the following output.
The schedule is successfully made but the model is "infeasible ".
I have also printed the results to give more clarity on the issue.

Hi @rajath-09,

'model.d' and 'model.p' work differently here

Isn't that each device has a different price? The array of prices might repeat the same price for multiple devices that share it.

I have also printed the results to give more clarity on the issue.

I don't see anything here.
Could you please share with us the code + data that you are using to test this? We can do it privately if you wish to.
Cheers,
Víctor

Also, I see that
    model.up_price = Param(model.c, model.j, initialize=price_up_select)
    model.down_price = Param(model.c, model.j, initialize=price_down_select)

require the parameter model.p

I guess i might have missed on that in the PR,but the "infeasible model" issue pertains.

This PR needs an automated test anyway, and I suggest that this is a good time to make that happen. We need a shared coded definition what success is. Otherwise we cannot really help you without a lot of added effort.
You can find tests we wrote to test scheduling in this repo. Copy one and adjust to your case.

Hey @victorgarcia98
Check on the latest commits.It finally schedules the sensor without any error.
I will mail you the data and assets used to test them.
I have added a new index dimension here 'model.u'.

Hi @rajath-09 and @anirudh-ramesh, as I wrote last week, this PR needs an automated test.
Please don't send my team assets and data from your projects to test locally as a habit. It was useful as a one-time approach, so we could help you solve a problem.
But in the end, we will not accept this PR without a reproducible test case.

Hi @nhoening , the data and assets were sent just in case the team needed to test out the new commits. Meanwhile,we understand the need for an automated test in PR and we are working on it and will get back to you with that when we are done.
We will now work on the automated test as we were solving the other issues earlier.

Great, looking forward! The test would have been already useful in demonstrating the error.
But I'm glad this PR can move ahead.

Hi @nhoening  I have my automated test files ready but I am unable to test them because there are some .py files called while running the tests,which have the occurrence of 'list' and 'tuple' instead of 'List' and 'Tuple' respectively,which is throwing the TypeError. How shall i proceed with the test.Also where do you want me to have the new conftest.py and test_solver.py in the repository

Ok sure,will try that out.
Also could you let me know  where should I keep my test files?

I believe in data/tests would be the best pace right now.
conftest entries could be added to the existing conftest file, and your tests can be in their own file.

Hi @nhoening
I have added the test file "test_dict_price_sensors.py" but somehow the timedbeliefs are not getting added despite putting that to the code.Could you help with that?

I don't know which beliefs you refer to. The ones created during the test?

In general, we'd need more details (a better description of what happens and does not happen) to be able to help, but maybe adding the db or even app fixtures to the test function signature would help.

Yes I am talking about those beliefs created in the tests.
In my test I am simply creating my flex context and other parameters from the conftest.py's functions(which returns sensor object) and then parsing it to the .compute() function.In conftest.py.
I will try adding the db and app fixtures.

Thanks for the test - this will make this feature much more robust!
Could you also run flake8 and black?
This works by running pre-commit run --all-files.
Afterwards, by running pre-commit install, you make sure it happens on every commit.

Thanks for adding the tests!!
I have some ideas to simplify the code.
On the other hand, although this test is checking that the schedule is running and that is giving a feasible solution, I think it lacks to test (assert) for the new functionality.
For this, I would compare the optimal value from the scheduler to cost computed from the data. To get the costs, I suggest moving the preparation of constraints and input data into a new method (e.g prepare_data).
And let compute be something like this:
def compute(self, ...):
      device_constraints, ..., ... = self.prepare_data(...)
      ems_schedule, expected_costs, scheduler_results = device_scheduler(
            device_constraints,
            ...
        )

        ...

        return battery_schedule

This way, you can test both self.prepare_data and check the final cost running device_scheduler. What do you think @Flix6x?

I am not quite sure what 'prepare_data' is.I don't find any function with that name.Is that an upcoming feature?How to proceed in that case?

I am not quite sure what 'prepare_data' is.I don't find any function with that name.Is that an upcoming feature?How to proceed in that case?

prepare_data is just a proposal for a function that creates device_constraints, ems_constraints, ... (the inputs of device_scheduler). That way, we would be able to test just this function and get the total costs at the optimizer level.

What is the further procedure?Is there anything else required in the tests or can we proceed with reviewing the PR?

Sure, let's move on. On the test, I'm not sure if you've reacted to all suggestions.
It's good practice to go through previous review  comments and resolve them (with a comment on why in a non-straight-forward cases - either that you followed the suggestion or that for some reason you did not).
then we have a clearer picture from our side.
Also, you can turn off the "Draft" status of this PR if you feel it is functionality-wise ready.
(on that note, is the functionality already tested in your use case? You could make a Docker image if you need that with the docker-compose script)

Sure, let's move on. On the test, I'm not sure if you've reacted to all suggestions.
It's good practice to go through previous review comments and resolve them (with a comment on why in a non-straight-forward cases - either that you followed the suggestion or that for some reason you did not).
then we have a clearer picture from our side.
Also, you can turn off the "Draft" status of this PR if you feel it is functionality-wise ready. (on that note, is the functionality already tested in your use case? You could make a Docker image if you need that with the docker-compose script)

If I am not wrong I have reacted to all of them except for the 'prepare_data' feature which we believe could be part of another PR as of now.Alternatively checking on the 'planned_costs' will give a clear picture.
Let me know if I missed on any other review.
Also yes,the functionality is tested for our test case.

Superglad to hear that this is already tested functionality-wise on your end!
Please hit all "Resolve conversation" buttons that are not relevant anymore.
We should decide who is the best reviewer to go further towards merging.  @victorgarcia98, are you into this PR enough? Feel free to converse in our chat for support.

We should decide who is the best reviewer to go further towards merging. @victorgarcia98, are you into this PR enough? Feel free to converse in our chat for support.

Sure! I can review it.

I have already resolved all conversations but it still shows 2 conversation unresolved.Not sure why though?

This has happened to me before. It might be related to that I'm doing a review.

I have already resolved all conversations but it still shows 2 conversation unresolved.Not sure why though?

This has happened to me before. It might be related to that I'm doing a review.

Ok let me know if something has to be done at my end.

closes #618

Sure @victorgarcia98
Noted your reviews.Will get back to you with the changes.

Hey @Flix6x @victorgarcia98
I have made changed according to the review.A few changes like using the previous index dimension instead of the new ones ,has not been made yet and will do that after we come to a common ground.
Rest of the changes have been made.Please let me know if that works.

Hi @victorgarcia98 and @Flix6x, any chance you got an opportunity to review the latest edits? Could we connect offline to discuss modifications that you think need to be made?
Thanks!

Hey @victorgarcia98 and @Flix6x
As per discussed on call,the code has now reverted back to use the d index dimension itself to fit in the use case.
Also I have tested the backwards compatibility by mapping it to the battery power sensor(as done in the PR). It seems fine to me and scheduling results turn out to be the same.You could check that on your end as well.If you find any discrepancy in the results ,do share the test case please.
Also apart from these, do let us know what other thing has to be done for the PR which we might have missed on.
Thanks

Hi @anirudh-ramesh do you think this PR is still relevant, or should I close it for the time being?


Fix tests that rely on a network connection

The specs excluded in this commit on the cesium.com branch (which changes the Ion default access token) should be fixed to not have to rely on connection to Cesium ion.  Test data should be local to the tests can run offline.

@sanjeetsuhag , I'm noticing that the test runner won't load at all on this branch, regardless of network connection. This issue is limited to this branch though.
I'm going through looking for a root cause now.


How to completerly uninstall powerline on Ubuntu?

Hi.
I installed powerline cloning the repo and running the setup.py script. Now I have to remove powerline and I removed the added line on .bashrc file.
To complete the removal, are there any other commands I have to run?

+1

+1


Wallet values

Not sure exactly what the problem is, but the wallet doesn't show the correct amount  of  tokens , base token for network (eth, rin, etc)  or ocean tokens

Reactivated the balance check in v4 and all working for me against Rinkeby which should be only network working right now:


[PERF-234] User documentation and scripting for 2.0 release

Security scanner found some problems in the old requirements.txt. The workflow file specifies path src/** so I'm surprised that it scanned things in the eng/old directory. Those errors are known and can be ignored. I'm bothered by the fact that it still detected this. Let's think about how we want to approach this before merging this ticket.

Continues to be triggering security problems in the old code, but not in the new code. I am going to rename the requirements file with a .bak extension so that we still have it, but it will be ignored. I hope.


Sending in unencrypted manner

Since timing information can be used to deduce information about internet usage, it should be uploaded to the server over an encrypted TLS channel.

Good point, we are going to add HTTPS to the main data reception host.


⚠ Bofrost.de has degraded performance

In 819e605, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1189 ms

Resolved: Bofrost.de performance has improved in 193017e.


[Pulsar Connector] Discuss State compatibility;

The customer was asking about how to use savepoints after Flink / connector version upgrade. Currently we don't  provide any state compatibility guarantees.

Nope. We have provided.


when run onnx vad example, it showed the error

when run onnx vad example, it showed the error
import torch
import onnxruntime
from pprint import pprint

_, utils = torch.hub.load(repo_or_dir='snakers4/silero-vad',
                              model='silero_vad',
                              force_reload=True)

(get_speech_ts,
 _,_,
 read_audio,
 _, _, _) = utils

files_dir = torch.hub.get_dir() + '/snakers4_silero-vad_master/files'

def init_onnx_model(model_path: str):
    return onnxruntime.InferenceSession(model_path)

def validate_onnx(model, inputs):
    with torch.no_grad():
        ort_inputs = {'input': inputs.cpu().numpy()}
        outs = model.run(None, ort_inputs)
        outs = [torch.Tensor(x) for x in outs]
    return outs

model = init_onnx_model(f'{files_dir}/model.onnx')
wav = read_audio(f'{files_dir}/en.wav')

# get speech timestamps from full audio file
speech_timestamps = get_speech_ts(wav, model, num_steps=4, run_function=validate_onnx)
pprint(speech_timestamps)

Traceback (most recent call last):
File "1.py", line 30, in
speech_timestamps = get_speech_ts(wav, model, num_steps=4, run_function=validate_onnx)
File "/home/gary/.cache/torch/hub/snakers4_silero-vad_master/utils_vad.py", line 112, in get_speech_ts
outs = torch.cat(outs, dim=0)
TypeError: expected Tensor as element 0 in argument 0, but got list
Originally posted by @garymmi in https://github.com/snakers4/silero-vad/discussions/58

@adamnsandle
another but after mini models release

@garymmi
Please check that this solves your problem
https://github.com/snakers4/silero-vad/pull/60

I suppose this issue should be fixed


Update string-split-transact-sql.md

Added clarification and improved sentence structure to improve version compatibility clarity.

@WilliamDAssafMSFT
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@DrDallas This article needs other unrelated changes, so I will include your changes in an internal PR. Thanks for your contribution.


Error with the render method when I run the component

I'm trying to get the component to work, so I just want to see a map on my phone's screen.
Here is the index.android.js code:

     import React, { Component } from 'react';
     import {
         AppRegistry,
        StyleSheet,
        Text,
        View,
        Image,
        TouchableOpacity
     } from 'react-native';

    import {
        MapView
    } from 'react-native-maps';

    class Example extends Component {
        render() {
             return (
                 <MapView
                     style={ styles.map }
                     initialRegion={{
                         latitude: 37,
                         longitude: -122,
                         latitudeDelta: 0.09,
                         longitudeDelta: 0.04
                     }}
                />
            );
       }
  }

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#F5FCFF',
  },
  welcome: {
    fontSize: 20,
    textAlign: 'center',
    margin: 10,
  },
  instructions: {
    textAlign: 'center',
    color: '#333333',
    marginBottom: 5,
  },
  map: {
    position: 'absolute',
    top: 0,
    left: 0,
    right: 0,
    bottom: 0
  },
});

AppRegistry.registerComponent('Example', () => `Example);

I've followed then installation and setup process as described, but when I run the app on my phone (Android version 4.4.4) I get the following error:

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of 'Example'

Any help would be really appreciated.
Thanks a lot in advance!

Use import MapView from 'react-native-maps';
instead of import { MapView} from 'react-native-maps';

Great! Thanks a lot!

@DimitrisHousiadas Don't forget to close the issue if it helped :)

I still have the issue even using import MapView from 'react-native-maps'
import { Text, View, StyleSheet, Platform, Dimensions  } from 'react-native';

import MapView from 'react-native-maps';

const REGION = {
    latitude: 49.439041,
    longitude: 2.796205,
    latitudeDelta: 0.003,
    longitudeDelta: 0.003,
};

const { width, height } = Dimensions.get('window');

export default class MapSite extends Component {
    constructor(props){
        super(props);

        this.state = {
            markers: [
                {
                    title: "toto",
                    description: "va a l'ecole",
                    pinColor:"#7d1f6f",
                    coordinate:{
                        latitude:49.439042,
                        longitude:2.796203
                    },
                    identifier:1
                },
                {
                    title: "tata",
                    description: "va a la garderie",
                    pinColor:"#7d1f6f",
                    coordinate:{
                        latitude:49.439043,
                        longitude:2.796204
                    },
                    identifier:2
                }
            ]
        }

    }

    render() {
        return (
            <View>
                <View style={styles.back}>
                    <MapView
                        provider="undefined"
                        style={styles.container}
                        region={REGION}
                        mapType="standard"
                        followUserLocation={false} //for the moment
                        showsUserLocation={false}//for the moment
                        showsMyLocationButton={true} //only true for android
                    >
                       {this.state.markers.map(marker => (
                        <MapView.Marker
                            key={marker.identifier}
                            coordinate={marker.coordinate}
                            pinColor={marker.pinColor}
                        />
                    ))}
                    </MapView>
                </View>
            </View>
        );
    }

MapView works when i declared it as a component from 'react-native' like :
import { Text, View, StyleSheet, Platform, Dimensions,MapView  } from 'react-native';
but not MapView.Marker
could it be due to the installation? I made a checkup but everything seems to be correct

Any updates / ideas here? I'm in the same boat as piloulac.

Any update on this issue

Any update on this issue

You import the wrong MapView, has to be imported from react-native-maps

Use import MapView from 'react-native-maps';
instead of import {MapView} from 'react-native-maps';

Maybe that's not the right place to ask this but... can you tell me WHY it is like that? I got stuck in this same error, I just want to understand what is the problem behind it, if you don't mind teaching me.


How to change the preheat x509 error

Configure deployment using the default helm
preheat
[root@xxxx ~]# curl  --location --request POST 'http://<IP_ADDRESS>:30175/api/v1/jobs'  --header 'Content-Type: application/json' -d '{"type": "preheat", "args": { "type": "image", "url": "https://<IP_ADDRESS>/v2/release.io/virtnest/system-images/ubuntu-22.04-x86_64/manifests/v1"}}'
{"message":"Get \"https://<IP_ADDRESS>/v2/\": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2024-04-22T08:44:35Z is after 2024-01-02T11:47:53Z"}[root@xxxx ~]#

how to solve

Refer to https://d7y.io/docs/next/reference/configuration/manager, https://github.com/dragonflyoss/helm-charts/blob/main/charts/dragonfly/values.yaml#L176.


Display of portrait pictures in forensic pop-up

There is a bug display while using the GIF / mp4 export of forensic filters on portrait images that

are cut on display.

Display component is generated an infinite loop when using CheckGif after:
app.bundle.js:2 Uncaught TypeError: Cannot read properties of null (reading 'style')
    at M (app.bundle.js:2:2176038)
    at app.bundle.js:2:2176293

To reproduce:
1 - Process any images with forensic
2 - display export result animated Gif
3 - close export window
4 - go to CheckGif
Infinite loop is starting shows in the console


Fixed get_axis_labels for :class:.Axes and :class:.ThreeDAxes

Overview: What does this pull request change?

Moves ~.get_axis_labels() out of CoordinateSystem and into Axes and ThreeDAxes.  This allows for ~.get_axis_labels() to be used with both 2D and 3D axes.  Fixed some documentation in the process.

Motivation and Explanation: Why and how do your changes improve the library?

Closes #2853
Links to added or changed documentation pages

https://manimce--3095.org.readthedocs.build/en/3095/
Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

This seems like a sane approach -- thank you!
I've left a bunch of suggestions to fix some formatting and linking issues, but as soon as the documentation renders correctly this can be merged.

I accepted your changes and the docs look good to me:
https://manimce--3095.org.readthedocs.build/en/3095/reference/manim.mobject.graphing.coordinate_systems.ThreeDAxes.html
But let me know if you spot any issues.  I will be without computer access for a few days, so feel free to make any changes you like.


Receiving a HTTP 409 Conflict response when trying to rename a file with OneDrive Personal

Hi,
We have a OneDrive Personal user who receives a HTTP/1.1 409 Conflict error when our application is trying to rename any file (and set its last modified timestamp) it has just finished uploading to the server.
Below are the request and response packets:
PATCH /v1.0/drive/items/B0E7B9973C67B12B!466303 HTTP/1.1
Content-Type: application/json; charset=UTF-8
Content-Length: 105
Authorization: Bearer xxxxxxxxx
Host: api.onedrive.com
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
User-Agent: Mozilla/3.0 (compatible; Indy Library)

{"name":"Annual Privacy Notice.doc","fileSystemInfo":{"lastModifiedDateTime":"2011-02-22T12:34:08.560Z"}}

HTTP/1.1 409 Conflict
Content-Length: 90
Content-Type: application/json
P3P: CP="BUS CUR CONo FIN IVDo ONL OUR PHY SAMo TELo"
X-MSNSERVER: BN2BAPF0E7098F2
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-QosStats: {"ApiId":0,"ResultType":2,"SourcePropertyId":0,"TargetPropertyId":42}
X-ThrowSite: 0bfa.2610
X-AsmVersion: UNKNOWN; 19.88.1204.2027
X-MSEdge-Ref: Ref A: 06167BAFEC674796B238B7670371BEA9 Ref B: ATAEDGE0622 Ref C: 2018-01-06T18:09:57Z
Date: Sat, 06 Jan 2018 18:09:57 GMT

{"error":{"code":"resourceModified","message":"ETag does not match current item's value"}}

As you can see It's clear that we don't provide any ETag along with the request. We have tried to reproduce this on our side using different accounts but it always works as expected.
We are suspecting the problem is particular to this user's account so maybe you can tell us why it fails.
Thanks,

We have conflict issue too when trying to upload a xlsx file sometimes.
We sending a upload request with "name.conflictBehavior=replace" option, but server reports
http code : 409
error message: ETag does not match current item's value
does the "name.conflictBehavior=replace" option not work?

One of our clients faces the same issue. Our application does the following:

uploads a file to user's OneDrive (PUT)
sets fileSystemInfo to this file's metadata (PATCH)

None of theese uses eTag.
The user processed lots of lightweighted images and sometimes PATCH requests ended up with the error described.
The application executes requests one-by-one.
As I can see, a workaround is just to retry patching.
Can I be helpful in finding the cause?

Is there any update about this issue?
We still hitting this issue when trying to upload  xlsx files.
the server response:
{"error":{"code":"resourceModified","message":"The resource being updated has changed since the caller last read it, usually an eTag mismatch."}

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


add tell and eof functions

When upgrading sming to use the latest version of spiffs I found these functions in the old code. I don't know where they originate from but we use them and they might be handy for others too.

So, back to my old whining. Actually, I'm normally very open to pull requests. Promise! :)
The pull does not conform to latest changes in SPIFFS. Two things missing in spiffs_hydrogen.c:

the file handle should be transformed using macro fh = SPIFFS_UNOFFS(fs, fh), preferably directly after SPIFFS_LOCK(fs) See SPIFFS_close for an example of this.
Also, in the same place, I'd like you to check the result of spiffs_flush_cache(fs, fh) and bail out if it fails, just as in SPIFFS_close

Otherwise, all seems beautiful ;)

Thanks for the feedback, I'll have a look...

Done. In doing it I also noticed that the existing error check was using SPIFFS_API_CHECK_RES instead of SPIFFS_API_CHECK_RES_UNLOCK (I didn't write this original code), so I've fixed that too.

Sorry about the missing res =, very careless. I tried to rush and get it done before I went to work and that's the result! I've squashed it into the previous commit, to avoid cluttering up the logs with unnecessary commits.

Heh, no problem - we're all human ;)
Cheers!


Service crash occurs after sleep/resume

Description:
A service crash occurs after sleep/resume. This did not occur on Develop prior to autowiring update. Stack trace and branch commit hash attached below.
Frequency:
10/10
Found In:
UPD-Autowiring branch: a0c90e87cc9e174272aa3f1150d90810f8c9e97a
Notes:
Stack Trace:

msvcr120.dll!abort() Line 88	C
msvcr120.dll!_purecall() Line 59	C
LeapSvc.exe!autowiring::signal::operator()(enum VigilanceReason &&)	C++
LeapSvc.exe!operator<<(class std::basic_ostream<char,struct std::char_traits > &,enum LEDMode)	C++
LeapSvc.exe!DispatchQueue::DispatchAllEvents(void)	C++
LeapSvc.exe!CoreJob::DispatchAllAndClearCurrent(void)	C++
LeapSvc.exe!std::_Func_impl<struct std::_Callable_obj<class std::_Bind<0,void,class <lambda_21250f153e69945bed5dd5697e2e3945> >,0>,class std::allocator<class std::_Func_class >,void>::_Do_call(void)	C++
LeapSvc.exe!std::_Packaged_state::_Call_immediate(void)	C++
LeapSvc.exe!std::_Func_impl<struct std::_Callable_obj<class <lambda_2cb696077b3339a1ae8328ae0c6c0dec>,0>,class std::allocator<class std::_Func_class >,void>::_Do_call(void)	C++
LeapSvc.exe!std::_Func_impl<struct std::_Callable_obj<class <lambda_76f314ecb5e1c9167539137e0dc2f350>,0>,class std::allocator<class std::_Func_class >,unsigned char>::_Do_call(void)	C++
LeapSvc.exe!Concurrency::task::_InitialTaskHandle<void,class <lambda_781036f848fffa6eb15265e2650f848e>,struct Concurrency::details::_TypeSelectorNoAsync>::_Init(struct Concurrency::details::_TypeSelectorNoAsync)	C++
LeapSvc.exe!Concurrency::details::_PPLTaskHandle<unsigned char,struct Concurrency::task::_InitialTaskHandle<void,class <lambda_781036f848fffa6eb15265e2650f848e>,struct Concurrency::details::_TypeSelectorNoAsync>,struct Concurrency::details::_TaskProcHandle>::invoke(void)	C++
msvcr120.dll!Concurrency::details::_UnrealizedChore::_UnstructuredChoreWrapper(Concurrency::details::_UnrealizedChore * pChore) Line 293	C++
msvcr120.dll!Concurrency::details::InternalContextBase::Dispatch(Concurrency::DispatchState * pDispatchState) Line 1716	C++
msvcr120.dll!Concurrency::details::FreeThreadProxy::Dispatch() Line 203	C++
msvcr120.dll!Concurrency::details::ThreadProxy::ThreadProxyMain(void * lpParameter) Line 174	C++
kernel32.dll!BaseThreadInitThunk()	Unknown
ntdll.dll!RtlUserThreadStart()	Unknown

ENG Requirements:

We should be able to address this with the next Autowiring release.


[Backport 2.0] Introduce new API _plugins/_security/ssl/certs (#1841)

Signed-off-by: cliu123<EMAIL_ADDRESS>(cherry picked from commit dce58266b0242286ff118f8d1360f7867006ad8a)

Codecov Report

Merging #1846 (dce5826) into 2.0 (1932be8) will decrease coverage by 0.00%.
The diff coverage is 73.91%.

:exclamation: Current head dce5826 differs from pull request most recent head 6ab59e5. Consider uploading reports for the commit 6ab59e5 to get more accurate results

@@             Coverage Diff              @@
##                2.0    #1846      +/-   ##
============================================
- Coverage     60.85%   60.85%   -0.01%
- Complexity     3186     3212      +26
============================================
  Files           253      256       +3
  Lines         17921    18005      +84
  Branches       3203     3209       +6
============================================
+ Hits          10906    10957      +51
- Misses         5441     5467      +26
- Partials       1574     1581       +7

Impacted Files
Coverage Δ

...ic/auth/http/jwt/AbstractHTTPJwtAuthenticator.java
55.81% <ø> (ø)

...mazon/dlic/auth/http/jwt/HTTPJwtAuthenticator.java
84.90% <ø> (ø)

...byoidc/HTTPJwtKeyByOpenIdConnectAuthenticator.java
94.11% <ø> (ø)

...azon/dlic/auth/http/jwt/keybyoidc/JwtVerifier.java
85.71% <ø> (ø)

.../dlic/auth/http/jwt/keybyoidc/KeySetRetriever.java
76.82% <ø> (ø)

.../auth/http/jwt/keybyoidc/SelfRefreshingKeySet.java
59.85% <ø> (ø)

...ic/auth/http/kerberos/HTTPSpnegoAuthenticator.java
0.00% <ø> (ø)

...dlic/auth/http/saml/AuthTokenProcessorHandler.java
47.28% <ø> (ø)

...zon/dlic/auth/http/saml/HTTPSamlAuthenticator.java
69.72% <ø> (ø)

...zon/dlic/auth/http/saml/Saml2SettingsProvider.java
61.53% <ø> (ø)

... and 195 more

Continue to review full report at Codecov.

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


Fix typespec for drop option

I forgot to update this in 3fde8304532670af7ebf57cbb041103be8a15774. Now we're using the same keep_fun type for both keep and drop to prevent them getting out-of-sync.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.24%. Comparing base (ab86164) to head (80a656d).
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@             Coverage Diff             @@
##              main     #114      +/-   ##
===========================================
- Coverage   100.00%   98.24%   -1.76%
===========================================
  Files            2        2
  Lines          145      114      -31
===========================================
- Hits           145      112      -33
- Misses           0        2       +2

Files with missing lines
Coverage Δ

lib/telemetry_metrics.ex
98.59% <ø> (-1.41%)
:arrow_down:

... and 1 file with indirect coverage changes

Continue to review full report in Codecov by Sentry.

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

I think it needs a new name entirely then as this feels confusing. I don't have a constructive opinion on what it should be. drop could still be kept and the type signature updated. That's probably the simplest route.

Changing the type names can be a backwards incompatible change. So the easiest is to make it so @type drop :: keep.

@josevalim Didn't realize that about backwards incompatibility, thank you!
@bryannaegele Do you think it would be confusing to implement @josevalim's suggestion (drop being an alias of keep)? I can instead just duplicate the the types like they were before:
  @type keep ::
          (:telemetry.event_metadata() -> boolean())
          | (:telemetry.event_metadata(), :telemetry.event_measurements() -> boolean())
  @type drop ::
          (:telemetry.event_metadata() -> boolean())
          | (:telemetry.event_metadata(), :telemetry.event_measurements() -> boolean())

But I consolidated them to prevent a mistake like the one I made, especially now that they're more complex. I have no issue with this if it's more readable, though.

I think aliasing to keep would be confusing. Copying is the simplest. If I were forced to refactor it, I'd alias the values.
Something like
@type metadata_predicate_fun() :: (:telemetry.event_metadata() -> boolean())
@type metadata_measurement_predicate_fun() :: (:telemetry.event_metadata(), :telemetry.event_measurements() -> boolean())

@type keep :: metadata_predicate_fun() | metadata_measurement_predicate_fun()
@type drop :: metadata_predicate_fun() | metadata_measurement_predicate_fun()

@type drop :: keep is the simplest IMO.

It could be me but I imagine it would be  confusing to see a signature saying drop is a keep lol.

It is a type annotation. The type annotation should mean they both have the same type. It doesn't meant they have the same semantics. :)

Just pushed up a change. I think the predicate_fun type strikes a balances between clarity (mirroring the "predicate function" language from the documentation) and simplicity (just 1 extra type). Let me know if you'd like any more changes!

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


Fix running user when using systemd.

Found out user mesos doesn't exist, was assumed to be created by mesosphere package. Now the user is root by default. Affects only when OS uses systemd.

+1 I have a fork that does this, I know it is useful.


Too many requests

Hi,
iOS 14.5.1.
iPhone 11
Just started using the app and find it quite useful but found that I'm confronted quickly with an error message:
Too many requests - you're sending too many requests or have reached your limit for new alises.
, even when I don't make an action in  the app. So essentially I suspect a bug which either makes that the error message is triggered.
I use anonaddy Pro and therefore I shouldn't hit any limits in terms of new aliases (as the error message suggests).
Any idea how to get around this maybe?

Hi Rapha,
Limitation is coming from AnonAddy's API, which AddyManager utilizes to interact with AnonAddy server, and has nothing to do with account subscription. It's an app issue not account or subscription related.
As a user, you can't get around this as it's out of your reach. Perhaps removing app, when not in use, from recent apps (background) might help.
It looks like AddyManager is exceeding the 120 requests per minute. I'm on it.
Thanks for reporting this issue.

I've managed to implement a way to stop API calls when app is in background (#30) which should help with this error.
Commit link: https://github.com/KhalidWar/anonaddy/pull/30/commits/36dfe745993b16b2743a1ffb2d49b4349d71fa7a
Closing this issue as it's solved. Will reopen if it comes back.


Upgrade timescale to 1.7.1

https://github.com/timescale/timescaledb/releases/tag/1.7.1

Done! v1.1.2 released.


[#4881] improvement(docs): Add documents about PostgreSQL storage backend

What changes were proposed in this pull request?
Change documents accordingly as we have supported PostgreSQL storage backend.
Why are the changes needed?
#4611 lacks related documents.
Fix: #4881
Does this PR introduce any user-facing change?
N/A.
How was this patch tested?
N/A.

LGTM.


[RFC] initial support for ROS2

This is rather a request for comments. If there're no objections I'd like to have ROS2 recipes included in meta-ros. But my reasons are non-technical.

The fastrtps version included here doesn't build correctly, see the fix for libtinyxml2 in:
https://github.com/shr-project/meta-ros/commits/jansa/master

We are interested in this branch being rebased and merged to master. And here is why
LG SVL Lab is working on bringing ROS2 to WebOS OSE. We've cloned and updated recipes to make sure it works on WebOS (https://github.com/lgsvl/meta-ros2)
This effort is a part Bean Bird Bot project, where we use WebOS OSE running on Raspberry PI. There are 2 additional repos we've been using to create a robot:

https://github.com/lgsvl/meta-ros2-lgsvl
https://github.com/lgsvl/duckietown2

You can see final result in this video:

Here is a description of the project we are working on: ros2-on-webos-lgsvl.pdf
@shr-project and @rojkov Please let me know if you have any questions. We'd like to cooperate to make sure it happens. Mentioning @bshin-lge and @martins-mozeiko since they are core developers in Bean Bird Robot.

Closing as the PR got superseded by #607


T265 use and legged_cheater_controller physical use problem

Hello, I see in your video, there is T265, how is this piece added and used, and why the command legged_cheater_controller is not allowed in the actual product, thank you for sharing this project

Rigid attach the T265 to the robot's body
Add the URDF of T265 to the robot.xarco correctly
Remap the T265's output topic to /tracking_camera/odom/sample

The stateEstimator will receive data from T265 and handle all transformations, then overwrite the robot position with data from T265.


Fix Account Exclusion Rules

There was a format issue around the ignore_accounts directive that misformatted the anything-but filter. This should fix it. Focused tests to capture this specific failure.
No changes to the external interface

CI reminded me we already had tests for the ignore filters, I just needed to correct the expectations. Thank goodness for rspec-terraform! Preventing breaking things since 2023.

Released in 0.6.6. @jedschneider ensure you pick up latest version tag where needed.


Configuration/DisableLocalAdminMerge Allowed Values Description wrong

Configuration/DisableLocalAdminMerge Allowed values Description wrong
https://learn.microsoft.com/en-us/windows/client-management/mdm/defender-csp?WT.mc_id=Portal-fx#configurationdisablelocaladminmerge
States the Allowed value Description as Yes or No.
When you look at the policy in intune, your options are these:
Enable Local Admin Merge
Disable Local Admin Merge
Not configured
Pleease correct this.
Thank you,
Blake

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

ID: 4f65802b-f3e2-1c15-d972-b23e53ed7e72
Version Independent ID: cc29ae16-e01e-aad1-3768-d6b8a0b60b1a
Content: Defender CSP - Windows Client Management
Content Source: windows/client-management/mdm/defender-csp.md
Product: windows-client
Technology: itpro-manage
GitHub Login: @vinaypamnani-msft
Microsoft Alias: vinpa

@.***
On Fri, Oct 6, 2023, 11:13 PM BlakeMsft @.***> wrote:

Configuration/DisableLocalAdminMerge Allowed values Description wrong
https://learn.microsoft.com/en-us/windows/client-management/mdm/defender-csp?WT.mc_id=Portal-fx#configurationdisablelocaladminmerge
States the Allowed value Description as Yes or No.
When you look at the policy in intune, your options are these:
Enable Local Admin Merge
Disable Local Admin Merge
Not configured
Pleease correct this.
Thank you,
Blake
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com
http://learn.microsoft.com ➟ GitHub issue linking.

ID: 4f65802b-f3e2-1c15-d972-b23e53ed7e72
Version Independent ID: cc29ae16-e01e-aad1-3768-d6b8a0b60b1a
Content: Defender CSP - Windows Client Management
https://learn.microsoft.com/en-us/windows/client-management/mdm/defender-csp?WT.mc_id=Portal-fx#configurationdisablelocaladminmerge
Content Source: windows/client-management/mdm/defender-csp.md
https://github.com/MicrosoftDocs/windows-itpro-docs/blob/public/windows/client-management/mdm/defender-csp.md
Product: windows-client
Technology: itpro-manage
GitHub Login: @vinaypamnani-msft
https://github.com/vinaypamnani-msft
Microsoft Alias: vinpa

—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/11744, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AVH2N5DX23A56BRKLVB5BH3X6AYMXAVCNFSM6AAAAAA5WCSD6OVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZTANRQGEZDKNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks @BlakeMsft for the feedback. The CSP docs are mostly automated now, drawing content from the DDF and ADMX files directly out of the OS itself. The Intune settings catalog does something similar, drawing from the same DDF source. So we can check to see why there's this discrepancy, which I wouldn't expect. Alternatively, the policy description is in the editable region, so we could always just add a note there to further explain.

Intune UI just has a toggle for this setting now in the Settings catalog, there's no "Not configured" value anymore and it's equivalent to "Yes/No". Closing this issue.


Enable editing configuration settings in CiviForm Admin UI

Is your feature request related to a problem? Please describe.
Add a UI for CiviForm admins to update configuration variables
Describe the solution you'd like
PRD

Related to #4948

Duplicate of #4948


Move Indicators Disappearing

The valid move indicators disappear from the board when you click on an invalid move. You can still move, the indicators just disappear.

Should be fixed now. Closing.


Support a /validate for use with ngx_http_auth_request_module

It would be great to have a /something endpoint that could be used with NGINX https://nginx.org/en/docs/http/ngx_http_auth_request_module.html.
If you can give me some pointers, im happy to do the PR

Hi @pecigonzalo, yes would make perfect sense.
You should make the resource at /login/validate and it should return the token content as JSON, if the Accept-Header for JSON is present. The implementation should share the code with https://github.com/tarent/loginsrv/blob/14651bba903922fccb34776ef16aaf632c2fd878/login/handler.go#L151-L160
Please do not forget the tests and documentation in the README :)

@smancke I was going through the code, and we might not even need the path.
EG: NGINX
server {
    listen 80;

    location /authz/ {
        internal;
        proxy_pass http://auth:8080/;

        proxy_set_header Accept "application/json";
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Scheme  $scheme;

    }

    location /login {
        proxy_pass http://auth:8080;

        proxy_set_header X-Real-IP               $remote_addr;
        proxy_set_header X-Scheme                $scheme;
        proxy_set_header X-Auth-Request-Redirect $request_uri;
    }

    location / {
        auth_request /authz/login;
        error_page 401 = /login;
        error_page 403 = /login;

        root   /usr/share/nginx/html;
    }
}

Seems to work for the most part, except for the fact that

I believe /login should return 401 not 403
Im setting /login json as a separate locaiton, to avoid the client then doing POST /login and getting JWT return.
We might make it cleaner by just doing an @this location.


Agentbaker shouldn't do anything based in ipmasq agent.

Eitehr ip masq-agent or CNI itself should do masqing. Agent baker is a particularly bad place to do it because the vnet value is fixed at nodepool creation time and can never change. ip-masq-agent at least has a chance to reconcile. without reimaging
What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

@paulgmiller @alexeldeib Any commentary on this, or are we good to merge? This is causing a problem for podsubnet v2.

Just forgot about it. Lets go!


switch from commit SHA to v0.1.4 release tag

v0.1.4 of f90wrap has now been released on PyPI with a corresponding tag on the GitHub repo.
I could not immediately figure out how to test this change to the recipe, so it will be interesting to see the CI results...

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I could not immediately figure out how to test this change to the recipe

@jameskermode feel free to ask me anything about conda-forge!
(But the changes here are OK.)

Just to let you know I am still limiting the build to Linux only because I could not figure out how to solve https://github.com/conda-forge/f90wrap-feedstock/issues/1
I don't have a Mac to test it but I will try to debug it using the CIs again soon.

This change looks good to go?
I do have a Mac but didn't make much progress - with gcc/gfortran from homebrew it was fine, but not when the compiler comes from conda.

This change looks good to go?

Perfect!
BTW, version updates like this one, are fair game to self-merge. There is no need to wait for someone else if the CIs are green,

I do have a Mac but didn't make much progress - with gcc/gfortran from homebrew it was fine, but not when the compiler comes from conda.

That is probably a simple detail that I am missing... Maybe @jjhelmus can take a look but I know he is quite busy with the Python recipes.


ManagedFrame.FrameClock should be ManagedFrame.Clock

https://github.com/neurogears/onix-refactor/blob/260149bdfb441c8d49a606bbfd303728cbc42bd0/OpenEphys.Onix/OpenEphys.Onix/ManagedFrame.cs#L18C26-L18C27
Can I make this change and push to main?

I would actually remove ManagedFrame entirely from the package. I don't think it is being used anywhere anymore and is no longer the recommended way to build a data frame type.

Alternatively we could make it the common base type of all data frames, but a slight refactoring would be needed, I can bring up a proposal in a PR for tomorrow.

Its used by the heartbeat. The reason I noticed is because I was looking for a place to document Clock and HubClock which are repeated everywhere in the library.

Re: refactor -- I don't think we need to make a common base class if there is not a good reason, its a minor thing I noticed during documentation.

@jonnew I think there are good reasons to having a common base class for this, as it makes it easier to consistently change the naming conventions, introduce new common properties we may not be exposing right now (e.g. DeviceAddress), and also facilitates documentation efforts since these properties only have to be documented in a single place.
I have opened a PR (#147) with a proposal for this which also refactors the heartbeat data and gets rid of ManagedFrame.


Endless scroll

Make a endless scroll method (add another [n] items).

http://jsfiddle.net/8PkQN/1/


Implement xrefs service directly backed by SQL GraphStore. [phab:D101]

Created by schroederc at 2015-02-26 22:57:02:
This implementation isn't as efficient as the serving implementation,
but the SQL implementation couldn't easily be used directly for xrefs
due the concurrency bug it has (i.e. the call to EnsureReverseEdges will
deadlock).

fromberger commented inline (context lost during migration) at 2015-02-26 23:51:08:
It's up to you, but I'd probably drop some newlines into these string literals for legibility.

fromberger commented inline (context lost during migration) at 2015-02-26 23:51:08:
revChildOfEdge (caps).
Or parentOfEdge maybe.

schroederc wrote at 2015-02-27 20:23:15:
Review changes

schroederc commented inline (context lost during migration) at 2015-02-27 20:23:41:
Done

schroederc commented inline (context lost during migration) at 2015-02-27 20:23:41:
Done

schroederc wrote at 2015-02-27 20:25:46:
Fix copyright year

schroederc closed via commit e654503e767da040ad850c5f477b620dabd2c83e at 2015-03-02 16:47:48

schroederc closed via commit fd6aa13889be4919fe8d1d55cfc6ed6e528f325d at 2015-03-02 16:47:48


[WFLY-18157] Add Jakarta Faces API dep back to BOM

https://issues.redhat.com/browse/WFLY-18157
Add dependency declaration back to BOM

Thanks @jasondlee and @jbliznak


Add github.com/go-errors/errors to CL2 vendor

I stumbled upon this recently, these are go errors with stacktraces. Makes debugging things much, much easier.
See the documentation at https://github.com/go-errors/errors

/assign @pierewoj

/lgtm


GORULE:0000061 violations

Some warnings here:
http://snapshot.geneontology.org/reports/assigned-by-pombase-report.html#gorule-0000061
gorule-0000061: https://github.com/geneontology/go-site/blob/master/metadata/rules/gorule-0000061.md

That was a quicker fix than I thought.  I didn't read this carefully enough:
If the annotation is to "GO:0032991 "protein-containing complex" or a subclass descendant of,
then the gp2term relation should be "BFO:0000050 "part of"; else, it is repaired to "BFO:0000050 "part of".

The code was looking at all ancestors not just the is_a parents.


Use shift click for water in steam generator can lose water

If you click shift click on water to put in steam generator water will be lose if on is in the water slot

Fixed in 3.0.2


Notify users of async errors

Task/Issue URL: https://app.asana.com/0/1149059203486286/1207045332341271/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#4571
#4570
#4569  👈
develop

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

Join @cmonfortep and the rest of your teammates on  Graphite

Sync paused - You've reached the maximum number of (bookmarks|passwords). Please delete some to resume sync.

instructions above differ from actual copy. can you confirm if the actual behavior is right?


ci: improve test workflow performance

This PR does two things. Please have a look at it and tell me what you think.

it speeds up the package and dependency installation by using uv instead of pip
it runs the pytest suite in parallel

Sometimes there are a few hickups during the ci run, especially with the windows runners? It should take more than 2-3 minutes per test run.

looks great, we had a small printout of tested solvers in the log before, https://github.com/PyPSA/linopy/actions/runs/10074914889/job/27852237849#step:10:38
any chance to revive that again or have a logger info statement?


np.loadtxt gives a warning for an empty file and returns shape=(0, 1)

from npreadtext import read, _loadtxt; from io import StringIO, BytesIO; import numpy as np

np.loadtxt(StringIO('''\n'''))
#<ipython-input-9-a3e642b8bbcd>:1: UserWarning: loadtxt: Empty input file: "<_io.StringIO object at 0x7efef5523a60>"
#  np.loadtxt(StringIO('''\n'''))
#Out[9]: array([], dtype=float64)

It also returns assumes a single column:
np.loadtxt(StringIO('''\n'''), ndmin=2)
# <UserWarning>
# array([], shape=(0, 1), dtype=float64)

returning a shape of (0, 1) and not (0, 0)

We need to add a test for this (and the warning for that matter).
I am starting to wonder if we should run a code coverage over the current Python code to write tests :/...

Actually, NumPy may have a test, I noticed yesterday that read just behaved differently from the loadtxt code.  There may be a point to that (i.e. moving the "reshape" to C) and using (0, 0) as the "correct" shape internally.

We have to put the warning back in (it is useful), it could make sense to even escelate to an Error.
Lets leave the shape handling as it was for these empty file cases.

@rossbar can I offload this to you for now as well? This should be done as pure Python post-processing.
(otherwise, ping me)

Should be fixed by seberg/numpy#41


Fix issue with using raw template expression with an intersection type as the contextually-expected type

Purpose
$title
Fixes #39158
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

@lasinicl Can you change the base to master?


Just a minor typo

Under "How can I move my trained models from one environment (like beta) to another (like production)?"
For instance, copying models from the public cloud to the Azure Government clod isn't supported.
The word clod should be "cloud".
It should be: For instance, copying models from the public cloud to the Azure Government cloud isn't supported.

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

ID: 457347ce-c365-5aad-a445-1e2939fc737c
Version Independent ID: bd5f1d3f-b951-c049-c51c-10e600da0a41
Content: Document Intelligence (formerly Form Recognizer) frequently asked questions (FAQ)
Content Source: articles/ai-services/document-intelligence/faq.yml
Service: azure-ai-document-intelligence
GitHub Login: @laujan
Microsoft Alias: lajanuar

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

@MagicPelikan
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!

@MagicPelikan
We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.
#Please-close