'The specified queue does not exist for this wsdl version.'

Been trying to figure this out for a few days now and no cigar, I know its probably something silly.
2017-06-03T12:11:22.872Z		Sending SQS '/preset/test'
2017-06-03T12:11:23.851Z		SQS didn't purged queue
2017-06-03T12:11:24.032Z		SQS failed to send message /preset/test
2017-06-03T12:11:24.032Z		SQS '/preset/test' failed
2017-06-03T12:11:24.032Z		{ AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist for this wsdl version.
    at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/query.js:47:29)
    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:105:20)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
    at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:673:14)
    at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
    at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
    at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
    at Request.<anonymous> (/var/runtime/node_modules/aws-sdk/lib/request.js:675:12)
    at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
  message: 'The specified queue does not exist for this wsdl version.',
  code: 'AWS.SimpleQueueService.NonExistentQueue',
  time: 2017-06-03T12:11:24.031Z,```

also been investigating this. I have USE_SQS to false, and that's the default. So it's not clear why it's invoking the SQS code at all.


Be able to create a AWS cluster via Control Plane API with as little information as possible

Is your feature request related to a problem? Please describe.

As a user I would like to create clusters via Control Plane API with the bare minimum info required (as I do in Happa).
Now to create cluster via Control Plane API there are lot of required files users must fill. Most of them can be deducted by the context. Example
kubectl gs template cluster \
  --master-az="eu-central-1a" \ # can be defaulted to one AZ as it is in happa
  --domain="eu-central-1.aws.cps.vodafone.com" \ # can be deducted by installation info
  --name="NaaP-nonPRD" \ # can be prefilled with a placeholder
  --credential="credential-igjf9x" \   #can be deducted by org name
  --owner="NAAPS" \ Required
  --release="11.4.0" \   #can be talked last active release
  --region="eu-central-1" # can be deducted by installation info

Describe the solution you'd like

Make those fields on the CR be optional or filled by an admission controller (or another component).
Describe alternatives you've considered

Make the defaulting in all clients / UI. (Not scalable)
Additional context

Steps:

[ ] evaluate impact on CRDs chemas;
[ ] implement only for existing optional fields;
[ ] implement only for existing required fields.

@alex-dabija will sync with Celestials @MartaD to get this aligned for aws and azure

As for firecracker, we could add the defaulting of these attributes to the defaulting webhook in aws-admission-controller. How I see it at the moment:
already defaulted in the aws-admission-controller and can be empty in the CR:

master-az

not yet defaulted in aws-admission-controller but can simply be done from installation info:

domain
region

not yet defaulted in aws-admission-controller but can simply be done from other CRs:

release

not defaulted yet and we would have to decide on a pattern:

name
credential (as I understand it, the credential is not always the same pattern, or am I wrong?)

credential (as I understand it, the credential is not always the same pattern, or am I wrong?)

Credential depends on org name, so it should be deducted from it.
For example a cluster that is in org Phoenix it will be
> kubectl get secret -l giantswarm.io/organization=Phoenix                                            (giantswarm-viking/giantswarm)
NAME                TYPE     DATA   AGE
credential-ku22e7   Opaque   2      29d

this credential -> credential-ku22e7

Regarding default cluster and node pool name: Please stick to the pattern already implemented when creating the cluster via the Rest API.
Cluster: Unnamed cluster
Node pool: Unnamed node pool

That sounds very reasonable. It should be easy to implement these default values :)

@alex-dabija will sync with Celestials @MartaD to get this aligned for aws and azure

@alex-dabija if you need/want to sync about this create a calendar event and invite me.
Please avoid today as I'm on call, but from tomorrow on choose a free timeslot at your leisure

@alex-dabija if you need/want to sync about this create a calendar event and invite me.
Please avoid today as I'm on call, but from tomorrow on choose a free timeslot at your leisure

Thanks! Meeting invite is sent for tomorrow.

In the past days I have added the defaulting of the cluster domain, description(name) and region into the aws-admission-controller. The master-az is also defaulted already.
Now I have started working on the defaulting of the credential-secret but it's not that straight forward.
For example, in anteater we have clusters in the organization adidas:
kind: AWSCluster
metadata:
  creationTimestamp: "2020-05-15T11:40:35Z"
  finalizers:
  - operatorkit.giantswarm.io/aws-operator-cluster-controller
  generation: 4
  labels:
    aws-operator.giantswarm.io/version: 9.1.3
    giantswarm.io/cluster: apie1
    giantswarm.io/organization: adidas

However, these clusters use the giantswarm credentials:
  provider:
    credentialSecret:
      name: credential-default
      namespace: giantswarm

and they belong to the organization giantswarm
  labels:
    app: credentiald
    app.kubernetes.io/managed-by: Helm
    giantswarm.io/managed-by: credentiald
    giantswarm.io/organization: giantswarm
    giantswarm.io/service-type: system
  name: credential-default
  namespace: giantswarm

In fact, the organization adidas does not seem to have its own credential:
kubectl get secret -l giantswarm.io/organization=adidas -A
NAMESPACE   NAME               TYPE     DATA   AGE
apie1       apie1-kubeconfig   Opaque   1      150d
apie2       apie2-kubeconfig   Opaque   1      158d
aud1t       aud1t-kubeconfig   Opaque   1      21d
ceu01       ceu01-kubeconfig   Opaque   1      5d2h
deu01       deu01-kubeconfig   Opaque   1      172d
htq5q       htq5q-kubeconfig   Opaque   1      55d
hype1       hype1-kubeconfig   Opaque   1      72d
jbo5h       jbo5h-kubeconfig   Opaque   1      42d
mh1m5       mh1m5-kubeconfig   Opaque   1      172d
oaut1       oaut1-kubeconfig   Opaque   1      63d
peu01       peu01-kubeconfig   Opaque   1      172d
seu01       seu01-kubeconfig   Opaque   1      172d

So this defaulting would fail.

As far as I know, there are two options.

Customers don't set credentials for the organization then this use credential-default
Customers set credentials for the organization then this use credential-xxxxx

Can you try in the logic to the credentials like kubectl get secret -l giantswarm.io/organization=XXXXX and if it not their fallback on credential-default ?

Ah okay. If we really only have these two cases, I will try the following behavior in case there is no credential given:

try to fetch the credential secret for the org and use its name and namespace if it exists
if it doesn't exist or there is more than one, use credential default in giantswarm namespace.

master-az, domain, name, credential and region are now all defaulted in the aws-admission-controller if they are not set.  (in the master branch that is, the credential defaulting is not rolled out yet)
These labels can be made optional in kubectl-gs
As for the release flag, since this label is propagated across several CRs, affects other component labels and we are also working on making upgrade through CP API possible, this will still take a bit longer. We are currently working on the details. :)

@anvddriesch if you set a wrong credential in the AWSCluster CR, does the admission validate is wrong (is not the right organization)? does it overwrite it? IMO organization should enforce credential to be always correct

No, at the moment there is no validation for this. It will only be defaulted if the value is missing.

We hit a problem setting the value to empty because it complains- According to CRD it is required. Can we make it optional and filled by the admission then?
https://docs.giantswarm.io/reference/cp-k8s-api/awsclusters.infrastructure.giantswarm.io/#v1alpha2-.spec.provider

Yes, I can make it optional in the apiextensions.

I have tested the creation with optional credentialsecret' attribute using your branch of kubectl-gsingauss`  and it's all good and working. However, I will apply the change to our installations on monday as today is still a freeze day for some customers. :)

The kubectl gs plugin has been updated removing the flag. So now it will set by the admission controller.

I am rolling out the changes on all installations right now, so the defaulting of credentialSecret should work.
Also earlier today I released the new version of aws-admission-controller which defaults the release version label to the newest active production-ready release in case no release label is set.

Firecrackers, can you please review this docs article with the new defaulting in mind? What should users know about that? Which details from example manifests should be omitted?

Yes, we'll also update the docs.

@giantswarm/team-celestial How is your situation with these flags? For aws, --domain, --name, --master-az and --release are all defaulted by the admission-controller and I'd like them to be not required anymore (In case of domain I don't think we need to have it at all since there is just one right value for the installation)

kubectl-gs v0.17.0 has just been released. Now an AWS cluster can be templated with just kubectl-gs template cluster --owner giantswarm. All other attributes are defaulted in the aws-admission-controller.
Example:
kubectl-gs template cluster --owner giantswarm | kubectl --context=giantswarm-gauss apply -f -
cluster.cluster.x-k8s.io/y29k0 created
awscluster.infrastructure.giantswarm.io/y29k0 created
g8scontrolplane.infrastructure.giantswarm.io/xxa2p created
awscontrolplane.infrastructure.giantswarm.io/xxa2p created

The resulting cluster is called "Unnamed Cluster" has 3 masters and its release version is the latest active production version available on the installation. The domain, region and selected AZs are selected depending on the installation and the credential-secret is set to match the owner.


Add wrappers for signature precompiles to Sapphire library

Wrappers for the precompiles added in oasisprotocol/oasis-sdk#1176.

Thanks @jberci! I'll shepherd this PR from here since I made a number of changes to the precompile ABIs.


Allow the sshkdf type to be passed as a single character

This partially reverts commit 270a5ce1d9ea579a2f1d45887971582b1ef2b6a1.
This also slightly modifies the way diverse parameters in are
specified in providers/fips/self_test_data.inc for better consistency.
Fixes #14027

Looks ok, but CI failures appear relevant.

Looks ok, but CI failures appear relevant.

It always worries me when gcc fails and clang succeeds or vice versa.  [sigh]

We should discuss this within OTC IMO.

Agreed, we need to discussion the ramifications.

The CIs seem much happier, now that I fixed an "interesting" assumption in self_test_kats.c.

Should this have a OTC hold on it?

I've rebased this.  The SSHKDF get_params got significantly simpler after #14168 was merged

Errors are relevant.

Errors are relevant.

Found the issue, it was a spot that should have been fixed in #14168, but wasn't

CIs are happy now

OTC: no objections to merging this

Now the CI fails and I suspect it is the crypto/params_from_text.c change.

Now the CI fails and I suspect it is the crypto/params_from_text.c change.

Nope, it was the same kind of change missing in the OSSL_PARAM_BLD stuff

This pull request is ready to merge

Merged
a8eb71ad577bbbd41cea915315451f0ef9f11581 Allow the sshkdf type to be passed as a single character
af8bd1d8359705c6a980c65b0c27c3e90fc43bea Fix OSSL_PARAM_allocate_from_text() for OSSL_PARAM_UTF8_STRING
6be27456e1346121b1fed797e92353733b59e16e Fix string termination and length setting in OSSL_PARAM_BLD_push_utf8_string()


Intermittent Windows CI failures

https://github.com/rust-pcap/pcap/runs/8200995220?check_suite_focus=true
Every now and then a windows CI test will fail with (exit code: 0xc0000135, STATUS_DLL_NOT_FOUND). I originally assumed that it must be the wpcap.dll since that's the only one we are installing and it was installed via autohotkey which felt like a windows hack to install an exe silently. However, now the CI runs with Npcap OEM silent installer so it seems much less likely that that was the culprit.
Googling around a bit, one thing about STATUS_DLL_NOT_FOUND is that it does not indicate which DLL failed so perhaps it is not wpcap.dll. However, I don't know how to diagnose this from the CI.
I think for starters it would help if we would run DUMPBIN /DEPENDENTS (https://docs.microsoft.com/en-us/cpp/build/reference/dumpbin-command-line?view=msvc-170) on the test binaries and verify their existence manually in each CI run before running the test.

Not so intermittent anymore https://github.com/rust-pcap/pcap/actions

For now this problem is stopgapped by not running integration tests and instead relying on unit tests alone.

Some hope for 1.78/1.79? https://github.com/rust-pcap/pcap/actions/runs/8775072751/job/24076974369

Nope, still happens: https://github.com/rust-pcap/pcap/actions/runs/8936617851/job/24547312634

Has not happened in a while - closing


Add OpenDrive import and export documentation

This implements what I think the "Lane Spline Export Tool" does. This outlines step-by-step loading geoJson and OpenDrive. I've been having a lot of trouble working with the OpenDrive loading that I think I'll need to discuss "in person" or whatever we call that nowadays.
Closes #82

@plarios It might be worthwhile to jump on a call and discuss working with the lane export tool to see if I'm using it correctly.


Reopening #170: Git remote: either guess everything, or nothing

This reopens #170 with rebased commits on top of #174.

[Current coverage][cc-pull] is 87.91%

Merging [#178][cc-pull] into [master][cc-base-branch] will increase coverage by 2.10%

@@             master       #178   diff @@
==========================================
  Files            33         36     +3
  Lines           980       1134   +154
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            841        997   +156
+ Misses          139        137     -2
  Partials          0          0

Powered by Codecov. Last updated by [ceae93f...cf404c8][cc-compare]
[cc-base-branch]: https://codecov.io/gh/aptible/aptible-cli/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/aptible/aptible-cli/compare/ceae93fe1d741c947108146533faabc5357f3c45...cf404c85607236cbbdf6efcdbc3c035f3745d901
[cc-pull]: https://codecov.io/gh/aptible/aptible-cli/pull/178?src=pr


os/gcache: memory leak

Go version
1.22
GoFrame version
2.7.4
Can this bug be reproduced with the latest release?
Option Yes
What did you do?
package main

import (
	_ "net/http/pprof"

	"context"
	"log"
	"math"
	"net/http"
	"time"

	"github.com/gogf/gf/v2/os/gcache"
)

func main() {
	go func() {
		log.Println(http.ListenAndServe("localhost:18888", nil))
	}()

	ctx := context.Background()

	cacher := gcache.New(10000)

	for i := 0; i < math.MaxInt; i++ {
		_ = cacher.Set(ctx, i, i, 0)
		time.Sleep(time.Microsecond)
	}

	log.Println("done")
}

watch with monitor or use go pprof
What did you see happen?
memory leak

What did you expect to see?
stable memory usage

@qinyuguang Let me have a check.

@gqcn @qinyuguang It seems to be related to LRU scheduled cleaning. The speed of set key in this code snippet is very fast, and they are all UniqueKeys. This leads to an increase in the number of keys in the cache beyond the cleaning capacity (removing time.Sleep(time.Microsecond) will make it more detailed).
In fact, this kind of scenario occurs relatively rarely.

@gqcn @qinyuguang It seems to be related to LRU scheduled cleaning. The speed of set key in this code snippet is very fast, and they are all UniqueKeys. This leads to an increase in the number of keys in the cache beyond the cleaning capacity (removing time.Sleep(time.Microsecond) will make it more detailed). In fact, this kind of scenario occurs relatively rarely.
test code
func main() {
	go func() {
		log.Println(http.ListenAndServe("localhost:6060", nil))
	}()

	ctx := context.Background()

	cacher := gcache.New(10000)

	go func() {
		for {
			size, _ := cacher.Size(ctx)
			log.Println(size)
			time.Sleep(time.Second)
		}
	}()

	for i := 0; i < math.MaxInt; i++ {
		_ = cacher.Set(ctx, i, i, 0)
	}

	log.Println("done")
}

log:
2024/09/27 14:26:25 227
2024/09/27 14:26:26 2051642
2024/09/27 14:26:27 3591917
2024/09/27 14:26:28 6056968
2024/09/27 14:26:29 6846812
2024/09/27 14:26:30 7291025
2024/09/27 14:26:31 8709386

Yes, I've figured that, and also resolved this https://github.com/gogf/gf/pull/3823 .


C# format not working

OmniSharp log
Post the output from Output-->OmniSharp log here
C# log
Post the output from Output-->C# here
Environment information
VSCode version: 1.54.1
C# Extension: 1.23.9
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET SDK (reflecting any global.json):
 Version:   5.0.201
 Commit:    a09bd5c86c
Runtime Environment:
OS Name:     Mac OS X
OS Version:  11.0
OS Platform: Darwin
RID:         osx.11.0-x64
Base Path:   /usr/local/share/dotnet/sdk/5.0.201/
Host (useful for support):
Version: 5.0.4
Commit:  f27d337295
.NET SDKs installed:
3.1.405 [/usr/local/share/dotnet/sdk]
3.1.406 [/usr/local/share/dotnet/sdk]
3.1.407 [/usr/local/share/dotnet/sdk]
5.0.102 [/usr/local/share/dotnet/sdk]
5.0.103 [/usr/local/share/dotnet/sdk]
5.0.201 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.11 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.12 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.13 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.3 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.4 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.11 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.12 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.13 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.3 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.4 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

code-gnu-global
austin
0.2.2

compareit
in4margaret
0.0.2

cpptools
ms-vscode
1.2.2

csharp
ms-dotnettools
1.23.9

docs-markdown
docsmsft
0.2.85

gitlens
eamodio
11.3.0

html-preview-vscode
tht13
0.2.5

html-snippets
abusaidm
0.2.1

powershell
ms-vscode
2021.2.2

prettier-vscode
esbenp
5.9.2

prettyxml
PrateekMahendrakar
0.7.1

resxpress
PrateekMahendrakar
4.2.0

svg
jock
1.4.5

vs-keybindings
ms-vscode
0.2.0

vscode-eslint
dbaeumer
2.1.17

vscode-firefox-debug
firefox-devtools
2.9.2

vscode-github
KnisterPeter
0.30.4

vscode-html-css
ecmel
1.10.2

vscode-pull-request-github
GitHub
0.24.0

Environment data
dotnet --info output:
VS Code version:1.54.1
C# Extension version:
1.23.9
OmniSharp log
    Could not find document for file /Users/abc/Desktop/dffd.cs

    Could not find document for file /Users/abc/Desktop/dffd.cs

    Could not find document for file /Users/abc/Desktop/dffd.cs

    Could not find document for file /Users/abc/Desktop/dffd.cs

Steps to reproduce

add C# code without saving, or with save but no project association.
check the language at the bottom
Try to format

Expected  behavior
Should format C# file
Actual behavior
Doesnt format the document

I'm having the same issue with formatting, my OmniSharp server keeps timing out.
OmniSharp log
Starting OmniSharp server at 3/15/2021, 2:17:42 PM
    Target: c:\Users\Brian\Desktop\Code\testing\fidgetech-to-do-list
OmniSharp server started.
Path: c:\Users\Brian.vscode\extensions\ms-dotnettools.csharp-1.23.9.omnisharp\1.37.6\OmniSharp.exe
PID: 21588
[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).

The C# extension does not support language services on loose C# files opened outside the context of a project file.


Add travis job that tests -std=c++14

std=c++11 is hardcoded at the end of https://github.com/mapbox/variant/blob/master/Makefile#L5
We should instead make that overridable with an option so that we can start testing compiles/unit tests in c++14 mode as well as c++11 on travis.

I have added two tests running clang 3.8 and g++ 4.9 in c++14 mode to the travis config. Of course we could do this on all compilers, but it would double the amount of tests to be run for not that much gain.
@springmeyer re-open or change .travis config yourself, if you think we need to check more variations.


Dispose of observers when store is no longer used.

Figure out how to get rid of these observers when the store is garbage collected as per https://github.com/mobxjs/mobx/issues/224#issuecomment-215760543
https://github.com/AriaFallah/mobx-store/blob/master/src/index.js#L85

I don't think you need that in your case as there is no unstore mechanism if looked correctly? Otherwise, observe returns a function, which, when invoked, disposes the observer.


Implement data constructors

This PR implements code generation for CtorDef and CtorSaturated.

Benchmarking the various options considered to encode ADTs real quick (cf. #86).
The encoded data in exam is Just 1.

Space complexity
Following the instructions described in CSUG 9.5 - Debugging, section 3.6: Nested object size and composition.

Pair of symbol and vector
Scheme definition: (cons 'Just (vector 1))
> (compute-size (cons 'Just (vector 1)))
112

> (compute-composition (cons 'Just (vector 1)))
((pair 1 . 16)
  (symbol 1 . 48)
  (vector 1 . 16)
  (string 1 . 32))

I'm not sure where is that string coming from.

Vector
Scheme definition: (vector 'Just 1)
> (compute-size (vector 'Just 1))
112

> (compute-composition (vector 'Just 1))
((symbol 1 . 48) (vector 1 . 32) (string 1 . 32))

Record
Scheme definition:
(define-record-type (Just Just Just?) (fields value0))
(Just 1)

> (define-record-type (Just Just Just?) (fields value0))

;; As per documentation, we have to force the record type definition
;; objects into GC generation 1.
> (collect 1 1)

> (compute-size (Just 1) 0)
16

> (compute-composition (Just 1) 0)
((#<record type Just> 1 . 16))

Deduplication
Ideally we might want a single Nothing to ever float around in memory. In that regard records (for trivial cases at least) behave as interned symbols.
> (define-record-type (Nothing Nothing Nothing?) (fields))
> (define n1 (Nothing))
> (define n2 (Nothing))
> (eq? n1 n2)
#t

> (define c1 (cons 'Nothing '()))
> (define c2 (cons 'Nothing '()))
> (eq? c1 c2)
#f

> (define v1 (vector 'Nothing))
> (define v2 (vector 'Nothing))
> (eq? v1 v2)
#f

> (define s1 'Nothing)
> (define s2 'Nothing)
> (eq? s1 s2)
#t

The codegen we use for data constructors needs to work with the Accessor constructor's BackendAccessor's constructor GetOffset.
data Foo = Foo Int

-- equivalent BackendSyntax (I believe):
--   `App fooValue (Accessor $ GetOffset 0)`
getOffset0 :: Foo -> Int
getOffset0 (Foo i) = i

It seems the record accessors are type-specific. So, can ADTs be encoded using define-record-type? I don't know we have information about the type to which foo corresponds available when a Accessor $ GetOffset 2 appears.

If our goal is to get a compiled output for Chez Scheme as quickly as possible, then we should just use vectors for now. I don't think that will force us to change any FFI in the future as any constructors for ADTs will be passed into the FFI as an argument. And then we can reconsider this in the future once we've verified other things work.
That being said, we could encode ADTs as records where one of the fields is the constructor's tag. Then, the type is just number of fields plus 1:
; defined in our runtime module
(define-record-type (Record0$ Record0* Record0?) (fields tag))
(define-record-type (Record1$ Record1* Record1?) (fields tag value1))
(define-record-type (Record2$ Record2* Record2?) (fields tag value1 value2))
; data Foo = Foo
(define Foo (Record0* "Foo")
; data Bar = Bar 1 | Baz 2 3
(define Bar (lambda (i) (Record1* "Bar" 1))
(define Baz (lamda (i1) (lambda (i2) (Record2* "Baz" i1 i2))))

Then, maybe using that record-rtd and record-accessor approach would work? But TSPLv4 does say in Section 9.2:

The procedural interface is more flexible than the syntactic interface, but this flexibility can lead to less readable and efficient programs, so programmers should use the syntactic interface whenever it suffices.

That being said, we could encode ADTs as records where one of the fields is the constructor's tag. Then, the type is just number of fields plus 1:
; defined in our runtime module
(define-record-type (Record0$ Record0* Record0?) (fields tag))
(define-record-type (Record1$ Record1* Record1?) (fields tag value1))
(define-record-type (Record2$ Record2* Record2?) (fields tag value1 value2))
; data Foo = Foo
(define Foo (Record0* "Foo")
; data Bar = Bar 1 | Baz 2 3
(define Bar (lambda (i) (Record1* "Bar" 1))
(define Baz (lambda (i1) (lambda (i2) (Record2* "Baz" i1 i2))))

Unfortunately that would take away the nice singleton property.
> (define-record-type (Nothing$ Nothing* Nothing?) (fields tag))
> (define n0 (Nothing* 'Nothing))
> (define n1 (Nothing* 'Nothing))
> (eq? n0 n1)
#f

Moreover I think that encoding only the tag is not sufficient. If the goal is to construct an accessor symbol (e.g. Foo-value0), then we might need a FQN.

Then, maybe using that record-rtd and record-accessor approach would work? But TSPLv4 does say in Section 9.2:

The procedural interface is more flexible than the syntactic interface, but this flexibility can lead to less readable and efficient programs, so programmers should use the syntactic interface whenever it suffices.

I'm not sure whether that statements applies only to make-record-type-descriptor. Consider that record-rtd is mentioned in the following section "Inspection", whose introduction says:

This section describes various procedures for asking questions about or extracting information from record-type descriptors (rtds). It also describes the record-rtd procedure, with which the rtd of a non-opaque record instance may be extracted, allowing the record type of the instance to be inspected and, via record accessors and mutators generated from the rtd, the record itself to be inspected or modified. This is a powerful feature that permits the coding of portable record printers and inspectors.

Summing it up, the code we would have to produce is ((record accessor (record-rtd n) x) n), where n is a record instantiation and x is the field offset.

Unfortunately that would take away the nice singleton property.

Why does that matter? Is there some performance benefits that we give up by dropping this?

I've got a PR up that adds type and constructor information to GetOffset (and renames that to GetCtorField here: https://github.com/aristanetworks/purescript-backend-optimizer/pull/45. I think with this additional information, we should be able to use the original define-record-type encoding.

Tests that we can add to this PR:
data Foo = Foo Int Int Int

-- a constructor that is partially applied to its arguments.
x = Foo 1
y = Foo 1 1
z = Foo 1 1 1

-- more pattern matching tests
data NoArgs = NoArgs

test1 = case _ of
  NoArgs -> true

data HasArgs = HasArgs Int Int Int

test2 = case _ of
  HasArgs i1 _ _ -> i1

test3 = case _ of
  HasArgs i1 i2 i3
    | i1 < i3 -> i1
    | otherwise -> i2

data SumWithArgs
  = First Int
  | Last Int

test4 = case _ of
  First i -> i
  Last i -> i

test5 :: Partial => SumWithArgs -> Int
test5 = case _ of
  First i -> i

What is the snapshot output when a constructor is not exported?

What is the snapshot output when a constructor is not exported?

We were always exporting all the definitions. Should be fixed in e16e190. I'd love to test it but between inlining and dead code elimination I'm not sure how to do it.
I'm not particularly happy with the DefinitionTranslation name.

Could you add a snapshot for that? For example
module Snapshot.Exports
  ( TypeOnly
  , TypeAndCtor
  ) where

data TypeOnly = Ctor

data TypeAndCtor = TypeAndCtor

Thanks @JordanMartinez, I was definitely overthinking it. Added that test case to the last commit and looks like it's working as expected.

If this PR is ready for a final review, could you take it out of the 'draft' state?

As discussed with @JordanMartinez I'm closing this PR as it's getting way too messy.


The Big Elephant in the room

So I revisited Semantic UI after using the framework one time for a project three years ago. I thought I would use the framework in react and I spent three days solving dependency issues when installing the Semantic UI package. I remember having the same struggle in my old project but I sorted it out in just a day. I didn’t expect that installing Fomantic-UI solved the problem. Reading through the history of the community supported fork was like watching Mum and Dad fighting.
Apart from avoiding passive aggressive remarks like “Why would you want to do that?”, I’m not one who will post a question on forums without exhausting all efforts in finding a solution first. So I went through the rigmarole of researching and testing. Whilst I should have just typed ‘npm installation issues’ on Github’s search box instead of using google to get me to that thread where one dude suggested Fomantic-UI, one cannot discount the fact of the many instances of unanswered questions I’ve read in different threads. Refer to @GuacheSuede ‘s comments here.
Some of us just want to use the framework and program right away. This - just like back in the day when you have to pay for a Microsoft suite of development packages and installation was a breeze. Sure, it’s not free and one would still read through forums for issues. But there’s a business organisation who has the financial resources and people to steer the boat in the direction that their customers want their product to go. Thus, there’s a sense of trust and most of the time, processes are replicable and results are predictable.
I’m also not one who will rant in forums. I would be thankful for those who spent their time contributing to open source projects. And I’m aware of the risks of going with this route. The notion of ‘free’ libraries or components is flawed because of the time you spent solving issues. I think the thought of components coded by developers are scary enough especially when it gets deprecated and there’s no proper change management at all levels. I hate to think that correlating the choice for open source as a form of loss aversion and ending up costing me more. The question is if we want the open source movement to succeed what technical standards should we follow?
I propose also adding ethical standards into the picture. That said, I’d like to address the big elephant in the room: Has development and support for the project has slowed down? I’m sure your reasons for being quiet are valid and people should have compassion. But for the love of God, please say something on your website that support for the project will end. If not, please answer people’s questions.
You guys might want to correct the first part of your documentation. If I may suggest:

People have different levels of knowledge and skills. Specify the pre-requisites before they even start following the getting started section of your documentation.

Most parts of the project documentation are very helpful. However, numerically outline  installation and tooling process as you’re defining steps. Consider grouping different options like in A. B. C fashion.

Perhaps open source shouldn’t be free and expensive? At the risk of sounding simplistic, devise a monetary incentive scheme where:

One vote is equivalent to an X dollar figure. A system will divide the proceeds among those who qualify to receive a reward. (All things considered including countries who would find $1 equivalent in their local currency as expensive).
There should be a central governing body every year. The community gets to vote who sits in the central committee.
People who discover issues and explain the problem according to set standards receives a monetary reward.
Members of the community gets to decide which issue is more pressing by putting in their votes. The central community members will prioritise the issue that gets the most votes. Everyone could vote as many times as they want. I’m sure their employers have a $ budget to spare.
Members of the community gets to decide which enhancements is worth adding to development. The central community members will prioritise the issue that gets the most votes.
Members of the community who knows the core system from the inside and out and can solve issues first gets a reward.
Members of the community who can do technical writing receive a reward for improving a documentation for said solutions and/or new enhancements.
The central community receives a reward for implementing changes to the core.
A small percentage commission given to someone who can bring in a sponsor.
Central community sets forum rules giving emphasis where everyone’s opinion matters but still encourage competition.

I'm not sure if there's a platform to implement the above suggestion. There's nothing really simple in our profession. The point is there are no free lunches.
Cheers!

Not going to lie, I've started using Semantic UI because of a great set of components, but looking at the current state of development I'm more and more looking back at Bootstrap

I've gone over to fomantic, development is active and they have a bunch of features and bugfixes Semantic has been needing. I'm still planning on porting existing apps over but for sure my future projects will be using fomantic.

Not going to lie, I've started using Semantic UI because of a great set of components and native React bindings, but looking at the current state of development I'm more and more looking back at Bootstrap

@xumix To each his own I guess. Competition encourages product innovation. Bootstrap may have matured. When it was fairly new, we got into a problem where each frontend dev in our team had a different interpretations of usage. It was probably a problem again on documentation. Nevertheless, Semantic-UI established a grammatical structure that was easy for every team member to understand. Speaking the same language -- if you'd like to call it that.

I've gone over to fomantic, development is active and they have a bunch of features and bugfixes Semantic has been needing. I'm still planning on porting existing apps over but for sure my future projects will be using fomantic.

@GammaGames Agree. As I've mentioned above, competition is healthy. I think letting Fomantic,  grow on its own would be good. I hope though that Semantic-UI React will catch-up with the new modules like Calendar.

@younggrandpa Well, Semantic ui React dev explicitly said they were not going to switch to Fomantic
and this is excatly why I'm looking into react bootstrap

@younggrandpa Well, Semantic ui React dev explicitly said they were not going to switch to Fomantic and this is excatly why I'm looking into react bootstrap

@xumix Go with what works for you. Let's see how their decision pans out.

I came across tidelift a while ago. They must be doing something right that are still in business
https://tidelift.com/lifter/search/npm/semantic-ui


Allow #-private names in parameter property positions

Search Terms

hard privacy  https://github.com/microsoft/TypeScript/issues/31670
Suggestion
allow create hard privacy like we do private in constructor(private foo: number)
Use Cases

Examples
allow use constructor(#foo: number) {}  or constructor(private #foo: number) {} or constructor(hard private #foo: number) {}
for same as
#foo: number;
constructor(foo: number) {
		// This works.
		this.#foo = foo;
	}

class C {
	constructor(#foo: number) {}

	log() {
		console.dir(this.#foo);
		return this
	}
}

let o = new C(777).log();

// error
o.#foo;

same as
class C {
	#foo: number;

	constructor(foo: number) {
		// This works.
		this.#foo = foo;
	}

	log() {
		console.dir(this.#foo);
		return this
	}
}

let o = new C(777).log();

// error
o.#foo;

Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[ ] This could be implemented without emitting different JS based on the types of the expressions
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[ ] This feature would agree with the rest of TypeScript's Design Goals.

I agree with this idea and have previously argued for it.
In our codebase we extensively use the "private" keyword with the constructor parameter shorthand. We will want to migrate our code to use hard-private fields. Not supporting hard-privacy in all the same positions as soft-privacy is complicating the language, making it less intuitive and consistent, and makes migration much more difficult.  As an aside, we also appreciate the small footprint afforded by the constructor parameter field shorthand and would be very sorry to lose it. For consumers of DI frameworks in particular, losing it means adding a lot of code bloat.

Currently, TypeScript allows contructor(private readonly text: string) {} in a class to automatically assign this.text inside of the generated constructor so it naturally follows that constructor(readonly #text: string) {} would automatically assign this.#text inside of the generated constructor.
This also allows a more transparent path for a refactor function to change private text to #text with minimal TypeScript source changes in cases where existing field initializers exist in constructors.
That this is not possible is a bit surprising because it increases the friction of refactoring from a TypeScript-only concept to a native JavaScript feature, and adds a benefit bias to keep using private field over #field, while TypeScript's design goals are to stay close to clean JavaScript.

Currently, TypeScript allows contructor(private readonly text: string) {} in a class to automatically assign this.text inside of the generated constructor so it naturally follows that constructor(readonly #text: string) {} would automatically assign this.#text inside of the generated constructor.
This also allows a more transparent path for a refactor function to change private text to #text with minimal TypeScript source changes in cases where existing field initializers exist in constructors.
That this is not possible is a bit surprising because it increases the friction of refactoring from a TypeScript-only concept to a native JavaScript feature, and adds a benefit bias to keep using private field over #field, while TypeScript's design goals are to stay close to clean JavaScript.

Can I vote for this too?

Oh I can see one reason this might be hard:
class Foo {
  constructor(
    private bar: any;
    #qux: any
  ) {
    this.bar // good
    bar      // also good: refers to local

    this.#qux // good
    #qux      // uhh...
  }
}

So the question is, is it ever important that you can't access the local? Can it just be omitted, and you have to use this to access it even in ctor?


usb-modeswitch

@telphan @floion @agherzan @lorenzo-stoakes
This seems independent from Network Manager enough to split out into a separate PR for simplicity.
Just installing this package will make it work automatically, it's tied into udev.
One of the modems I have takes 2 minutes to switch, the other is much faster, but I ran just a handful of tests.

LGTM


REST API: /account/{pubkey} endpoint

AC:

Path /account/{pubkey} GET
Included in BaseAPI interface with Account interface returned to allow for extending the base account type
Returns balance and pubkey for base account details
Returns _ for cosmos specific account details
OpenAPI supporting doc comments

AC question: what's the format of pubkey supposed to be here?

I'd like to see us look harder at the concept of an "account" before we build much of an API for communicating about about them on the wire. This is hard problem, since

Addresses aren't pubkeys, they're pubkey hashes
Various ecosystems have "native" methods for encoding pubkeys which are

similar to their address encodings (cosmospub1-prefixed bech32 in cosmos, 65-byte 0x-prefixed strings in ethereum) but not interchangeable
typically incompatible with other ecosystems

Blockbook misuses the version bytes in BIP32 encoded extended keys (i.e. the xpub/ypub/zpub prefix) to infer UTXO script type, which it shouldn't because

distinct BIP32 version bytes aren't always allocated for new script types (as in the case of taproot)
a pubkey can be used to receive UTXOs with several different script types, and it's not at all immediately obvious that those should be considered "different accounts"

When we need to use what you're calling "pubkeys" here in chain-adapters, we call them "account specifiers" -- but we completely made up that name and IMO it would be best to keep the whole concept off the wire if possible.

The term pubkey was just meant as a generic name to represent some public key (address or xpub) that is used to fetch transaction history or account balance information from a backend node or indexer. In this case for cosmos, we are querying by cosmos address.


Is it possible (and recommended) to directly edit host.json file to add an app setting?

On my local.settings.json (minimized for the purpose of this question) I have this attribute::
{
  "Values": {
    "AzurePdfStorageConnectionString":  "MY_CONN_STRING_HERE"
   }
}

So inside code I retrieve the value with the well-know ConfigurationManager class and everything works fine:
  ConfigurationManager.AppSettings["AzurePdfStorageConnectionString"]

My question is: taking aside Application Settings edition from the Portal, is it possible to add a Values attrib inside host.json? Or is not recommended to manually edit this file?
For now I'm manually adding the value trough the portal, but I have a pipeline in place that also deploys the infrastructure along the function, so after a deploy the value disappears.
I understand I can add this attrib-value pair to "appSettings" into "Microsoft.Web/sites" resource, but then I would like to dinamically replace this value during deploy pipeline for different stages.
Hope you can add more detailed information about host.json edition.

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

ID: d4f40a37-fa0f-6d54-57ad-8d58c6c3531b
Version Independent ID: 3b2178f9-f6a8-8771-f7f5-7a9952b45b2b
Content: Configure function app settings in Azure
Content Source: articles/azure-functions/functions-how-to-use-azure-function-app-settings.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Hi @amartin1911 Thanks for reaching out. We will review and update as appropriate.

@amartin1911 Settings in the local.settings.json file are only used by Functions tools when running locally. By default, these settings are not migrated automatically when the project is published to Azure. We could use the Azure Functions Core Tools to publish the local.setting.json to Azure easily.
func azure functionapp publish azurefunctionname --publish-local-settings
The host.json metadata file contains global configuration options that affect all functions for a function app.
Host.json is not for config Azure function appsettings

Thank you for the prompt response. I
Doing more research on how to handle distinct env variables for my infrastructure + functions automated deployment, I realized I could just have several *.parameters.json files for each environment. And as I pointed out before, declare my variables inside appSettings section from Microsoft.Web/sites resource.


gostreamdeck: Still:Select pic index

Still2 FEEDBACK show
STILL 1 feedback for
every Still1 option chosen
– Still1 Pic1 chosen, Still2
Pic 1 shows red even if
Still2 is set to Pic2 (or
other)

Solved in commit 3811eaf55d66a94525ddadec780766a2e0c352ad


What's the registry solution for regions ACR not available?

It needs registry service for using ACS on Azure. ACR seems a good solution. But it's in preview in limited region. What's the recommended way for regions that ACR are not available like Mooncake?

I'd suggest posting this question on https://github.com/Azure/acr


Skip wrong columns numbers

Hi,
I am trying to import omniture feed.
The problem that I have is that sometime in the feed I have some lines that have only 3 out of the 4 columns. In that case the current behavior is to let the last columns empty, I actually want to skip those lines. Is there a way to do that?
(I use python)
Thanks

Try to use mode as DROPMALFORMED (if i got you correctly).

I was looking for this flag...
Thank you


Script tag of polyfill is not being transformed

This .html file is the product from the example after build, it looks like the script tag of legacy polyfill is not being transformed.

Can you tell me which version you are using?

Can you tell me which version you are using?

0.4.0

Can you tell me which version you are using?

0.4.0

Okay, the code should have been rolled back by me, I'll update a fix version right away and let you know.

No no, I remembered it, this is how it is handled here, because it is nomodule, it will not be executed by default, it is loaded through the above script to get the src attribute, it turns out to be n.src=e .src, I processed it as n.src=window.__dynamic_base__+e.getAttribute('src')

Can you describe the problem you are currently facing?

@Gwokhov I think I know where the problem is, nomodule will not take effect in backward browsers, it will be executed directly. I will fix it as soon as possible, thank you very much for your feedback.

It does, but it runs in module mode, and System.import is not in the environment. 🧐

@Gwokhov I think I know where the problem is, nomodule will not take effect in backward browsers, it will be executed directly. I will fix it as soon as possible, thank you very much for your feedback.

I tested in IE11 and IE would not execute the script tag with type=module which was injecting dynamic base code, so the polyfill script was linked to the wrong resource.

Yes, I also found this problem through IE11, I will think about it later if I can solve this problem.

Yes, I also found this problem through IE11, I will think about it later if I can solve this problem.

Same as vite-legacy-entry, we can change the vite-legacy-polyfill src attribute to data-src and using systemjs to import the dynamic_base + el.src, this may fix the issue.

vite-legacy works with legacy browsers by:
<script type="module">!function(){if(window.__vite_is_dynamic_import_support)return;
    console.warn("vite: loading legacy build because dynamic import is unsupported, syntax error above should be ignored");
    var e=document.getElementById("vite-legacy-polyfill"),n=document.createElement("script");
    n.src=window.__dynamic_base__+e.src,n.onload=function(){
      System.import(window.__dynamic_base__+document.getElementById('vite-legacy-entry').getAttribute('data-src'))
    },
    document.body.appendChild(n)}();</script>

the script will load vite-legacy-polyfill by create a brand new <script /> with __dynamic_base__ prefix.

<script nomdule />s will not be execute by browsers.

vite-legacy works with legacy browsers by:
<script type="module">!function(){if(window.__vite_is_dynamic_import_support)return;
    console.warn("vite: loading legacy build because dynamic import is unsupported, syntax error above should be ignored");
    var e=document.getElementById("vite-legacy-polyfill"),n=document.createElement("script");
    n.src=window.__dynamic_base__+e.src,n.onload=function(){
      System.import(window.__dynamic_base__+document.getElementById('vite-legacy-entry').getAttribute('data-src'))
    },
    document.body.appendChild(n)}();</script>

the script will load vite-legacy-polyfill by create a brand new <script /> with __dynamic_base__ prefix.

I am also planning to make another loader in the body.

<script nomdule />s will not be execute by browsers.

Will be executed in IE11.

how about transform legacy scripts from:
<script nomodule id="vite-legacy-polyfill" src="/assets/polyfills-legacy.c9aac887.js"></script>
  <script nomodule id="vite-legacy-entry" data-src="/assets/index-legacy.b6066e67.js">System.import(window.__dynamic_base__+document.getElementById('vite-legacy-entry').getAttribute('data-src'))</script>

to:
<script nomodule id="vite-legacy-polyfill" src="/assets/polyfills-legacy.c9aac887.js">
!(function() {
  var e = document.createElement('script')
  e.src = window.__dynamic_base__ + "";
  e.onload = function() {
    System.import(window.__dynamic_base__+document.getElementById('vite-legacy-entry').getAttribute('data-src'))
  };
  document.body.appendChild(e)
})();
</script>
<script nomodule id="vite-legacy-entry" data-src="/assets/index-legacy.b6066e67.js"></script>

@Gwokhov You can try version 0.4.1

Not work, the .html was blocked at #vite-legacy-entry script tag, cause System is defined in polyfill, maybe it is not a good idea to patch at the bottom.

It seems that the results we got are not the same, it's okay, I will deal with it more comprehensively, and leave a message for you later, you can try the new version tomorrow morning.

@Gwokhov  You can try version 0.4.2 through @zhoujinfu  scheme

@Gwokhov You can try version 0.4.2 through @zhoujinfu scheme

Thanks a lot, it works as expected now.

I'll close this question then, thank you for your use and feedback, and have a nice day.


HHH-10756 fix procedure name in test

minor fix in test only
I didn't create new JIRA for this fix, commit references original jira
5.1 PR: #1394
master PR: https://github.com/hibernate/hibernate-orm/pull/1393

Merged. Thanks Martin!


Input as cartesians?

Hi,
just to make sure, I assume TrilaterationFunction expects the position argument to be in cartesian coordinates, not in lat/lon or anything else?
Cheers,
Julian

Julian,
Yes, you are correct.  Positions should be valid cartesian coordinates.  In full: Inputs identified as tuples (lists) of n real numbers should exist in a euclidean space of dimension n.
If you are using lat/lon, you will need to convert to a cartesian coordinate system.  Depending on the range of latitudes and longitudes inputs, and the desired accuracy, you will want to be cognisant of this conversion.
If accuracy is not a concern, you can model the earth as a sphere:
http://stackoverflow.com/questions/1185408/converting-from-longitude-latitude-to-cartesian-coordinates/1185413#1185413
If you have large lat/lon ranges or you are using an ellipsoid model of the earth (like WGS-84), you will want to look into solutions that account for this.
Does this answer your question?

Scott

Perfect, Scott. Thanks a lot.
I am using pretty small lat/lon scales (<100m) and can accept minor conversion errors, so I will go the simple route first.
Cheers.

Using the linked SO equations, the input positions would be composed of x and y (throwing away z)?

Why would you throw away z?

The positions are arrays of two doubles but there are three axes in the SO answer.

@JulianSchuette  https://github.com/lemmingapex/Trilateration/blob/master/src/test/java/com/lemmingapex/trilateration/TrilaterationTest.java#L255-L267

Thanks! Much appreciated


php73: 7.3.8 -> 7.3.9 (security)

Motivation for this change
https://www.php.net/archive/2019.php#2019-08-29-1
https://www.php.net/ChangeLog-7.php#7.3.9
We should probably bump other versions we package, released
concurrently.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

Yes, we should update the older minor-versions as well to their respective patch updates as well as backporting it all to stable


llama.cpp running on iPhone generate irrelevant outputs

Hi everyone,
I tried the example app, and runs it on my devices.
On android devices, it works perfectly without any issue.
But on iPhone, it generate irrelevant outputs.
(Model: gemma-2-2b-it-Q8-0.gguf)
For example, when I ask: "What are the three laws of robotics?"
It answered:
You're talking about **data visualization**, also known as "the art of living" - it sounds like something out of an action movie! 💥

Let me know what you need help with! 😄

I am so excited to finally be able to share my work on this platform.  It’s important for everyone in our community who may not have access to resources or opportunities that would otherwise be unavailable. This could include providing financial assistance, legal aid, mental health services, and substance abuse treatment centers near me.”

Here's how I think about AI safety.**

**Introduction:**

The world is facing unprecedented challenges. From climate change to pandemics, we can see that there is a significant difference in performance between two models: A linear model and a decision tree were used to analyze data from a large-scale experiment was conducted at [location] ](https://www.youtube.com/watch?v=h4r30k.png" alt="Image description here."

Please note: The information provided below is intended for informational purposes only and does not constitute medical advice. Please consult your physician before making any changes to your diet plan. It should contain all relevant details about the product being sold.

For example, if you are looking for a new home, right? Well, let me tell you a story...

In the heart of bustling London, lies an inconspicuous building tucked away in a quiet corner of town.

This isn't quite what I had in mind! 😄
<end_of_turn><eos>

Looks like the input and output are not related.
Anyone has the same issue?

Ah, sorry, I just noticed that, in the example of README, there's a ==n_ctx== parameter
But it is absent in the example code.
When I added it to initLlama, it start generating meaningful response.
Not sure why android don't need this, but anyway I found the solution.
    initLlama({
      model: file.uri,
      use_mlock: true,
      n_ctx: 2048,              // added this for iOS
      n_gpu_layers: Platform.OS === 'ios' ? 0 : 0, // > 0: enable GPU
      // embedding: true,
    })


Remove closed $0 balances from BalanceSheet view

Note: Should make all closed accounts not show up in the TEMPLATE LEVEL not at the CALCULATION LEVEL as it does now. Don't want anything screwing up with comparing start/end balances


Asynchronous templating

Tessera currently uses handlebars for expanding templates in items such as the markdown item, and most importantly in queries. Internal to UA (to be released eventually) we integrate that with handlebars helper functions that call clusto to build graphite queries from role-based queries to clusto (to retrieve hostnames).
Because handlebars is synchronous, that means making synchronous HTTP calls, which is no fun (mitigated by in-browser caching, but still...).
Possible approaches to mitigate this:

Replace the template engine with one that supports both async rendering and async extensions. This also means re-writing portions of dashboard rendering using Promises (also not a bad thing). It also likely means some incompatibilities in the templates (see below), which is not ideal but probably acceptable.
Keep handlebars, but add an async data gathering phase, so we don't need to make async calls within template helpers. This is attractive from an MVC standpoint, but would really need a much more sophisticated editor (which is probably much more expensive to write, in terms of effort).

Async Template Engines

nunjucks - A Deep Dive into Asynchronous Templating is a great writeup.
dustjs
marko

Oh, this is interesting  - https://github.com/nknapp/promised-handlebars


modem: cmux: Added validation of CMUX frame length

Added validation of frame length to avoid
waiting for an invalid number of bytes to be received.
If the frame length is longer than expected, the frame is dropped.
Signed-off-by: Henrik Skreslet<EMAIL_ADDRESS>

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Yes, this is in situations where something is really wrong ;D I discovered this while working on a project where I seem to be losing bytes on the driver level, but I reckoned this could happen anyway, and falls in line with the same kind of checks that is done later when doing CRC validation

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Though this means the check won't be included when asserts are not enabled, which is a bit too bad. But whichever way I'm happy with.

In my opinion this is something that we should be able to recover from, it will at least make the cmux parsing more robust in scenarios where the ISR handling is sub-optimal

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Though this means the check won't be included when asserts are not enabled, which is a bit too bad. But whichever way I'm happy with.

That's why I want it to be an assert :) We already drop frames which "misbehave" when the buffer overflows or CRC check fails, so there is no "functional" difference with adding this check. It can be helpful to diagnose the specific issue where CMUX has been incorrectly configured, but that will be detected immediately in dev env. If its malformed/broken bytes, the CRC check failing will be the only deterministic information, since a malformed frame header can be due to both bit errors and incorrect config.

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Though this means the check won't be included when asserts are not enabled, which is a bit too bad. But whichever way I'm happy with.

That's why I want it to be an assert :) We already drop frames which "misbehave" when the buffer overflows or CRC check fails, so there is no "functional" difference with adding this check. It can be helpful to diagnose the specific issue where CMUX has been incorrectly configured, but that will be detected immediately in dev env. If its malformed/broken bytes, the CRC check failing will be the only deterministic information, since a malformed frame header can be due to both bit errors and incorrect config.

This is not about misconfiguration, but is a runtime error that will happen if the length byte is lost, and the next byte (data byte) is used as the length. The frame will be dropped eventually, but the state machine will have to wait for that invalid number of bytes to be received, which could be up to 32768 (I guess) bytes. Depending on the application and use case, that could be a very long time.

Could you make this an assert instead of a check? The size of CMUX frames (MTU) is selected when CMUX is set up (last parameter in "AT+CMUX=0,0,5,127") so it should not be possible to receive a frame which exceeds this :) It should be unnecessary to do this check unless something is really wrong (it could be a bit error?) :)

Though this means the check won't be included when asserts are not enabled, which is a bit too bad. But whichever way I'm happy with.

That's why I want it to be an assert :) We already drop frames which "misbehave" when the buffer overflows or CRC check fails, so there is no "functional" difference with adding this check. It can be helpful to diagnose the specific issue where CMUX has been incorrectly configured, but that will be detected immediately in dev env. If its malformed/broken bytes, the CRC check failing will be the only deterministic information, since a malformed frame header can be due to both bit errors and incorrect config.

This is not about misconfiguration, but is a runtime error that will happen if the length byte is lost, and the next byte (data byte) is used as the length. The frame will be dropped eventually, but the state machine will have to wait for that invalid number of bytes to be received, which could be up to 32768 (I guess) bytes. Depending on the application and use case, that could be a very long time.

ok, with the check only being made once, and the fact that we go directly to DROP its probably worth it :)

@henr1k You'll have to fix the compliance failure: https://github.com/zephyrproject-rtos/zephyr/actions/runs/11554879860/job/32169138362?pr=80505

@henr1k Do you need some help? Are you gonna open a new PR?

@henr1k Do you need some help? Are you gonna open a new PR?

Thank you, yes, I will open a new PR after reading the contribution guidelines even more thoroughly ;D

What is it that you were having trouble with? Feel free to ask here!


Fixing Issue Docker not found #9

The playbook DockerInstallation is responsible for installing Docker and Docker ComposeV2 on systems running Debian/Ubuntu or RedHat/CentOS using Ansible. The explanation of how the environment variables interact with this playbook, particularly in relation to the Environment Variables section in artifacts/wiki/index.html

hey @RoninAngle1 ,
thanks for your pr , there seems to be a problem with the playbooks' syntax as the workflow reports could you double check and test your code using linter.sh ansible or ansible-playbook --syntax-check playbook.yml to see what's going on plz?

@Shayan-Ghani Of course, let me check the issue

@Shayan-Ghani Of course, let me check the issue

great i close this one please open another pr and in the description:
fix #issueNumber
YOUR DESCRIPTION HERE.
you might as well start your commit messages with "fix/feat/chore/doc: your message" in this case you should start your commit with a fix #issue_number : your message.
tnx in advance.


imx8mmevk libusb error timeout

When trying to load code onto sd card on the imx8mmevk board, with the following command:
sudo ./uuu/uuu -b sd_all ~/imx-boot-imx8mmevk-sd.bin ~/core-image-minimal-imx8mmevk.sdcard
I get:
uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.1.87-3-g9d88a8c

Success 0    Failure 1

1:1    1/ 1   [HID(W):LIBUSB_ERROR_TIMEOUT ] SDP: boot -f /home/austinf/imx-boot-imx8mmevk-sd.bin

Not sure how to debug what's going wrong further.

The early imx8m chip need apply a ROM patch.   windows system have not such problem.

My only windows system is 32 bit, can 32 bit windows binaries be provided? The ones on the release page appear to be 64 bit only.
Building from source on windows requires quite a bit of environment setup it looks like.

We don't prefer use 32bit system, because it will be problem when download big files.

did you boot from other boot source?
check if rom patch locked
u-boot=> fuse read 0 0

I can boot off an sdcard.
u-boot=> fuse read 0 0
Reading bank 0:
Word 0x00000000: b0010103
How do I interpret that result?

this is early chip problem.  Someone report there are not such problem at  ubuntu 18.04


Fix CORS issue with direct log file download

PR #659 introduced a problem where browser rejects a request to get a
log file from a S3's pre-signed URL when S3 sends
Access-Control-Allow-Origin: '*' header.  This happens only when the
server generates a direct-download URL for log files.
An example message from Chrome is:
The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.

Credentials should not be included in the request to accept
Access-Control-Allow-Origin: '*' header when the server generates
pre-signed URLs for log files.

I’m so sorry for my overlooking and appreciate that you fixed quickly.


possible to route to individual model workers?

Is it possible to route requests to different model workers depending on some criteria?
Thanks!

Yes, using a router like https://litellm.vercel.app/docs/routing


Discuss: Restricting language subset used for sublanguage detection

When limiting auto highlight to a language subset, it only works for top-level languages. So when parsing some HTML with JavaScript inside with:
hljs.highlightAuto(
  code,
  [ 'html', 'css', 'javascript' ]
).value

the JavaScript may still be interpreted as ActionScript, for example. 😕

Good catch, thanks. And that should be fixable in a fairly straightforward way. I'll try to get to this one before the next release.

😄  Thanks!

I think the problem here is misstated - or at least the implied solution is not correct.  If the same filters used for language were applied to sublanguage someone could easily break many grammars without realizing it.  I don't think this is how users would expect things to behave in general.
Perhaps this merely requires a documentation fix, but I'm not so sure.  Many languages are vitally dependent on particular sublanguages and if I only specified the parent language in the subset I would NOT expect that to restrict the sublanguage subset  - hence badly breaking the parent language.
Some examples:

xml/php
xml/vbscript_html
many of the templating languages that require xml
javascript/xml (for JSX support)

I'm not sure what the proper solution here is, but I wanted to add these notes.

the JavaScript may still be interpreted as ActionScript, for example.

Was that the real problem here?  I wonder if we couldn't simply remove ActionScript completely (from the autodetect list for <script> tags in xml)... isn't flash pretty much dead now?  No one else has commented on this issue so I'd be happy to lose actionscript as a sublanguage for script tags and close this out with that.
Thoughts?
CC @egor-rogov @marcoscaceres

I wonder if we couldn't simply remove ActionScript completely (from the autodetect list for <script> tags in xml)... isn't flash pretty much dead now? No one else has commented on this issue so I'd be happy to lose actionscript as a sublanguage for script tags and close this out with that.

I think it can be a solution for this particular issue.
In general we lack a mechanism to limit sublanguages (outside from the grammar). I agree that

if I only specified the parent language in the subset I would NOT expect that to restrict the sublanguage subset

but could a separate restriction of sublanguage subset be convenient in some cases?

but could a separate restriction of sublanguage subset be convenient in some cases?

Perhaps.  Though I think it'd be very hacky and still subject to the caveats I mentioned above (far more likely to break things than to fix things). If you're fine will removing ActionScript from the auto-detection for <script> then I say we do that for now, close this - and see if it ever comes up again or not.
If so perhaps when/if it does we'll have more information and perhaps that'll lead to better ideas.

I'm fine with it.


Consider the use of ValueTask in async LINQ operators

Right now, the prototype of C# 8.0 query operators for IAsyncEnumerable<T> introduces overloads such as:
public static IAsyncEnumerable<T> Where<T>(this IAsyncEnumerable<T> source, Func<T, Task<bool>> predicate);
public static IAsyncEnumerable<R> Where<T, R>(this IAsyncEnumerable<T> source, Func<T, Task<R>> selector);

We should consider the pros and cons of using ValueTask<T> for the return type of these delegate arguments.
In addition, we should measure how much overhead the async overloads incur, and consider removing a lot of code duplication for the synchronous and asynchronous case, in favor of using Task.FromResult(x) or new ValueTask<T>(x) to convert the synchronous case into the asynchronous one.

I've just faced a scenario which I think is related. I'm enumerating files in Azure Files service directory, and the files are returned in batches (segments). I want to have an async enumerable around that, because to enumerate all files I'll have several async service calls. But the number of files in each batch is much bigger than number of batches (calls). Asynchronously iterating each file in a batch is a very expensive operation due to Task(s) allocation. It looks like ValueTask would be a nice solution for this, but obviously this should be a special implementation.

Done in latest implementation of System.Linq.Async.


Can´t run Steambot on unbuntu

I dont find the program i install mono and i wget the steambot.
http://prntscr.com/8pnic8
I tried bin/debug and bin/release and i cant find him... I just wget its the problem?

#427 #527

MY problem is i dont know compile


delegate not responding

I am trying to unstake EOS i have staked to another account.  When i click confirm, the window does nothing with the circle spinning icon forever.  I tried to delegate EOS just to see, and it does the same thing.

Hrm, does the account you're using have enough staked EOS to perform these actions? I just did some tests and they seemed to work on my end.
There may be an error message if you go into View -> Toggle Dev Tools, and then go look at the console tab of that area. It'd be red text that would appear when you perform the action and the circle spins forever.

Also what version?

version 0.7.4

trying to find how to change nodes... maybe that's the issue

yup... that was the issue.  back on ole trusty greymass node.  don't remember why i swapped... Thanks for pointing out the console to me!  Maybe i can self diagnose any issues in the future.


fix(test): Bypass mocha error (no tests found)

We don't have system-tests for tasks yet.

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master    #17   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines           4      4
=====================================
  Hits            4      4

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 6cc6eca...6a06554. Read the comment docs.


Only upload code coverage on linux

Limit codecov coverage upload to runs on ubuntu-latest so that it is not confused by coverage differences between platforms.

codecov/project is going to fail on this PR as coverage is it will no longer include windows coverage.


add node-red dashboard functionality

Hello Tristan
Nice work ! But for us the dashoard is not working what url should we use to see it?

THanks for the help.
Regards Lieven

Hello  Tristan
Can we have the 2 zip files to install in our tenant please and try it out?
thanks

Hello Tristan Can we have the 2 zip files to install in our tenant please and try it out? thanks

I see following in my tenant but no dashboard

@LieBov in general you can find the corresponding files attached to the pipeline e.g. here: https://github.com/SoftwareAG/cumulocity-node-red/actions/runs/1580064890
Sadly this functionality is not yet working, so this does not really help you and might require a future cumulocity version..

Thanks for the update
What version of cumulocity do we need?
Our tenant is on 10.10 i believe.
Kind Regards

@LieBovhttps://github.com/LieBov in general you can find the corresponding files attached to the pipeline e.g. here: https://github.com/SoftwareAG/cumulocity-node-red/actions/runs/1580064890
Sadly this functionality is not yet working, so this does not really help you and might require a future cumulocity version..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SoftwareAG/cumulocity-node-red/pull/2#issuecomment-994986907, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEO5SUVLPVOXETKB4XEASGLURDDDHANCNFSM5KBVCKJA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@LieBov I guess I found a bug in cumulocity which currently stops me from finishing this feature. I still wait for a confirmation that this is actually a bug. And then we will have to see in which version this issue is resolved..
So I guess we won't see this feature until maybe the beginning of Q2 2022 if this is actually a bug and I do not find a way to work around it..

Thanks for the explanation
Regards Lieven

Van: Tristan Bastian @.>
Verzonden: woensdag 15 december 2021 18:13
Aan: SoftwareAG/cumulocity-node-red @.>
CC: LieBov @.>; Mention @.>
Onderwerp: Re: [SoftwareAG/cumulocity-node-red] add node-red dashboard functionality (PR #2)
@LieBovhttps://github.com/LieBov I guess I found a bug in cumulocity which currently stops me from finishing this feature. I still wait for a confirmation that this is actually a bug. And then we will have to see in which version this issue is resolved..
So I guess we won't see this feature until maybe the beginning of Q2 2022 if this is actually a bug and I do not find a way to work around it..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/SoftwareAG/cumulocity-node-red/pull/2#issuecomment-994994564, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEO5SUVZ7QPQ7BUL4QLLPGDURDEC5ANCNFSM5KBVCKJA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Having issue with top bar

Hi Satnaing,
My site is live, but the top nav bar with the dark theme toggle and other nav links is not working on mobile web browsers for My Site.
Can you please advise on what I can do to triage this?
https://www.nishad.link/
If you can help in any way would really appreciate.
regards
Nishad

The issue is with the blog heading text overlapping with the hamburger menu in portrait mode. there is no problem in landscape.
For now I will reduce the text size of the

In your specific case, adding these classes in the Header would fix the problem.
file: src/components/Header.astro
<style>
  /* other styles */
  .logo {
    @apply absolute py-1 text-xl font-semibold sm:static sm:text-2xl sm:max-w-none top-0 max-w-[63%];
  }
  /* --- */
</style>

So, the newly added classes would be sm:max-w-none top-0 max-w-[63%].

Many thanks for your response.


Add Multi language support. And Arabic language support

Thanks @A909M

Thanks @A909M

You're welcome 🤗


[1.6.x] Bump KIE 7.53.1.Final

I am confused
jenkins please retest this

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

Jenkins retest this.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

The Linux check has failed. Please check the logs.

script returned exit code 143

jenkins please retest this


libmolgrid install in python2

Dear all
we want to install and use libmolgrid in python2
But it seems libmolgrid is working in python3 environment
is there any  other way that I can use in in python2 ?

I'm not going to support that.  Python2 was formally deprecated three years ago.


Add validation sections to experiments

I suggest we add chaos validate instructions alongside chaos run for each of the experiments, to aid in their further development. Sections such as:
Developing this experiment further
Validating the experiment from the catalog using HTTP
(chaostk) $ export APPLICATION_ENTRYPOINT_URL=http://<IP_ADDRESS>:32474; \
            export SERVICE_NAME=my-service; \
                   chaos validate https://raw.githubusercontent.com/open-chaos/experiment-catalog/master/kubernetes/kill_microservice/kill_microservice.json

Wdyt @gtfisher
This will be reliant on this PR being in a release of the chaos toolkit first: https://github.com/chaostoolkit/chaostoolkit/pull/130

Intro to section something like:
Developing this experiment further
If you'd like to develop this experiment it's useful to be able to validate the experiment to ensure you have all the required variables being specified. the chaos validate command from the Chaos Toolkit is ideal for this purpose.

I've now added this as an advisory note to the top level README. Closing this issue for now.


Commonize admin components

Description
Addresses Ticket: 1278
Reduce duplication, make common Admin components that can be used accross different forms.
passing 'formName' and 'resource' props down to child components
calling commonFormService.
There's a bug relating to mine / permit number.
not sure where that came from.
Types of changes

Checklist

[ ] I have read the CONTRIBUTING doc
[ ] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

SonarQube Analysis: https://sonarqube-vmvfjv-tools.pathfinder.gov.bc.ca/dashboard?id=common-forms-toolkit-pr-102


Cheerio upgraded in order to make it look for 'package.json' the way …

…it should
Signed-off-by: mpyziak

Because there is a ^ in front of the version number, version 0.22.0 will automatically be installed if you have ^0.20.0 in package.json.

It does not. Only changing version and re-running npm install helps.

Oh, sorry, forgot that it is below 1. With >= 1 it does.

Cheerio 1.0.0 will probably be released soon, so the maintainer of this repo might want to switch to that, in order to get the behaviour described above.

I'm okay with this, especially since Cheerio 1.0.0 is still a release candidate. Thanks for the PR!


[Feature] java agent add cpu load limit config and releated cds

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
when the cpu load is too high, the agent can not sample according to the cpu load limit config (maybe like agent.sample_avg_cpu_load_limit). Also, this config can be changed through cds.
Use case
as description.
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Please submit pull requests separately. We need to review this mechanism carefully.

No update in a long time. Closing.


[Privileges 2] stdin for CLI not accepting password

I believe that stdin input is planned for v2.0, based on request https://github.com/SAP/macOS-enterprise-privileges/issues/35 ([Feature Request] - Local Authentication with the PrivilegesCLI), but the password doesn't appeear to work.
Trying the beta, the typical process looks like:
$ ./PrivilegesCLI -a
Please enter the reason you need administrator privileges (at least 10 characters): Install Software
Please enter your account password: _<password entered>_
User _<my username>_ now has administrator privileges.
Administrator privileges expire in 20 minutes.

When setting environment variables for the reason and password, it appears that the reason is accepted in stdin, but I don't seem to be able to feed the password in. Some examples:
$ printf "$reason\n$password\n" | ./PrivilegesCLI -a
Please enter your account password:

$ printf "$reason\n\n$password\n" | ./PrivilegesCLI -a
Please enter your account password:

$ printf "$reason\n$password\n\n\n\n\n\n\n" | ./PrivilegesCLI -a
Please enter your account password:

The feature request https://github.com/SAP/macOS-enterprise-privileges/issues/35 refers to local authentication (a macOS password dialog or Touch ID). This has been implemented in version 2. There are no plans to support passwords via stdin.


Async doesn't tell the adapter to fetch the record if it hasn't already been loaded

DEBUG: -------------------------------
DEBUG: Ember      : 2.1.0
DEBUG: Ember Data : 2.1.0
DEBUG: Firebase   : 2.3.1
DEBUG: EmberFire  : 1.6.0
DEBUG: jQuery     : 1.11.3
DEBUG: -------------------------------

Reading the docs from here. It's said that: Any relationship that is flagged as async: true tells the adapter to fetch the record if it hasn't already been loaded.
I have the following models:
// app/models/room.js
export default DS.Model.extend({
  name: DS.attr('string'),
  messages: DS.hasMany('message')
});

and
// app/models/message.js
export default DS.Model.extend({
  content: DS.attr('string')
});

I didn't declare the async: true in my room model since I believe that in Ember Data 2.x, all relationships are async by default.
Now, when I do a this.store.findAll('room') it's only returning the room model. I would need to do this.get('room').get('messages') to further load the message model itself.
The behavior that I'm getting is what I'd really expect (and what I'd like too) from Ember Data, but the statements in the docs is not inline with what's happening. So I'm not sure if this is a bug or just a wrong documentation. Am I missing something here?
I think it's important to know because if we're only be able to fetch the async model by only explicitly asking for it then I guess there would be one less reason to follow the best practice of flattening out the data structure since this will avoid the scenario of iterating over "rooms" to get a list of names requires potentially downloading hundreds of megabytes of messages.

Now, when I do a this.store.findAll('room') it's only returning the room model. I would need to do this.get('room').get('messages') to further load the message model itself.

That is the expected async: true behaviour. So, it looks like we need to update our documentation to be more clear. Thanks for the feedback. :cake:
Is something like this a little bit more clear:

Relationships flagged with async: true instruct EmberFire to fire off a second request to look up the related records independently. This will not happen until you request the contents of the relationship.
this.store.findRecord('post', 'post_1').then(function (post) {
  post.get('comments').then(function (comments) {
    // comments can be accessed here
  });
});

Yes. That's better IMO.
Though I just wanted to note that I may have been a little to hasty when I said that this would be one less reason to follow the best practice of flattening out data. In Ember, I guess you can get away of not flattening your data but if you have an Android or iOS app that uses the same DB, I think flattened data is the way to go.

ok cool, I will get this updated in the docs, thanks


Add last / addFirst to CircularBuffer

Motivation:
Its often useful to be able to add / retrieve elements on both sides of a CircularBuffer.
Modifications:

Add last / addFirst to be able to act on both ends.
Add tests

Result:
Fixes https://github.com/apple/swift-nio/issues/279

FYI @helje5

Very nice! 👯 Should that also do the power-of-2 buffer size increases instead of doubling? For Redi/S to be fast, I had to do manual capacity increases.

Oh, I just noticed you already did that in #313 .

@weissi @Lukasa PTAL again

Created https://github.com/apple/swift-nio/issues/350 as a followup.


Add source_code filter for Map Points

We have been doing some updates to our Polling Locations system (now called "Map Points") in the admin tools. Two related tasks:
1)
On this page: http://localhost:8001/pl/
For every unique polling_location.source_code value found in the database (ex/ "PUBLIC_SCHOOLS"), show a checkbox between the filter/search interface and the map points.

So if you uncheck the box for PUBLIC_SCHOOLS, those map points would be filtered out.
View file: WeVoteServer/polling_location/views_admin.py
function: polling_location_list_view
Template file: WeVoteServer/templates/polling_location/polling_location_list.html

On this page:
https://api.wevoteusa.org/pl/0/visualize/?state_code=
...I would love to add a way to filter by "polling_location.source_code". I'm thinking a checkbox for every unique value found in the database in the source_code field, displayed next to the state drop down. So if you uncheck the box for PUBLIC_SCHOOLS, those map points would be filtered out.
View file: WeVoteServer/polling_location/views_admin.py
function: polling_location_visualize_view
Template file: WeVoteServer/templates/polling_location/polling_location_visualize.html

Hello Dale,
My team(@sorryForDisappointing, @JuanSuria1) and I are working on this issue currently and are having some problems with downloading the map points of every state. So far we have been only able to find 2 unique source_code values, PUBLIC_SCHOOL and POST_OFFICE_LAT_LONG. Our team was wondering if there were any more source_code values that we need to look out for besides the one mentioned.

@holdenliu @marianomirandaherrera @juansuria1 I apologize for not responding sooner, but we have pulled this issue into our internal team of volunteers. Thank you for taking a look at the issue! https://wevote.applytojob.com/apply/


Push to Python 3.10

This release contains Qt call fixes and a refurbished environment to make CNApy compatible with Python 3.10. Accordingly, to test this PR, you have to create a new mamba/conda environment from the YML file.

Oh yes, type annotations are now much easier to do as, most of the times, one does not need to import typing anymore; As you suggested, deleting (now) unused imports is a primary target now :D


Juror Scoring: shift the levels by 1

We want the jurors to start at level 1 instead of starting at level 0.
If they perform badly, we want them to drop progressively to level 0.
We need to tweak the score formula and check that

The range boundaries are correct according #888
The score should remain fairly distributed among the jurors

Score levels:
[
  { scoreRange: [0, 20], level: 0, title: "Diogenes" },
  { scoreRange: [20, 40], level: 1, title: "Pythagoras" },
  { scoreRange: [40, 60], level: 2, title: "Socrates" },
  { scoreRange: [60, 80], level: 3, title: "Plato" },
  { scoreRange: [80, 100], level: 4, title: "Aristotle" },
];

fixed on #1702


ManagedExecutor.newIncompleteFuture

One thing that we are missing on ManagedExecutor is an equivalent for the ability to construct a new instance of CompletableFuture which is not completed and chain dependent stages, later completing the original CompletableFuture.  A workaround for this is requesting an already-completed completable future,
managedExecutor.completedFuture(unusedResultOfCorrectType).newIncompleteFuture();
However, this pattern seems like it could be common enough that a convenience method would be valuable,
CompletableFuture<Integer> cf = managedExecutor.newIncompleteFuture(Integer.class)

Any reason why <T> CompletableFuture<T> newIncompleteFuture(Class<T>) rather than <T> CompletableFuture<T> newIncompleteFuture()?

@FroMage no good reason that I know of. What you suggested is better, so let's use that instead.


Clean up branch

Ticket
Description
Screenshots / Demo Video
Testing
Checklist

[ ] Provided ticket and description
[ ] Your PR title contains the ISSUE ticket number e.g "86: ..."
[ ] Provided screenshots/demo
[ ] Provided testing information
[ ] Provided adequate test coverage for all new code
[ ] Run automated tests (docker compose exec app yarn test)
[ ] Added PR reviewers
[ ] Ensure at least 1 review before merging

Time to restart


Optimize Tekton pipelines tasks dependency

Acceptance Criteria:

Optimize Tekton tasks dependency
Parallel launch of tasks that do not require workspaces
Adding connections between dependent tasks

Done


OKTA-540404 - Push SDK: Refactor enrollment flow in order to support different server APIs(legacy vs MyAccount)

Problem Analysis (Technical)
We need to move out API models building/parsing logic from enrollment transaction. In that case enrollment transaction impl will be server API agnostic
Note: unit test coverage for LegacyServerAPI class will be added in next PR
Solution (Technical)
Affected Components
Steps to reproduce:
Actual result:
Expected result:
Tests

Probably need to merge this before the ciba changes right?

Yes, thank you for the quick review


refactor cross-contract examples

cross-contract-high-level and cross-contract-low-level each implement two different cool features:

Factory pattern: a method that creates a subaccount and deploys a contract to it, and even some proxy methods to interact with the subaccount via the factory (currently called complex_call and simple_call)
Merge sort: an implementation of the merge sort algorithm that powerfully demonstrates NEAR's asynchronous, concurrent cross-contract calls.

Categorizing these examples by their implementation rather than by their behavior leads to confusion for newcomers. I propose we instead create two new examples, "factory contract" and "merge sort." This has a couple benefits:

We can add a high-level and a low-level implementation to each. In the tests, we can loop through the wasm files for these two implementations and run the exact same set of tests, showing & ensuring the feature parity between the two implementations.
We can add more specific READMEs to these new projects explaining the significance of the pattern being demonstrated. We can target these READMEs at blockchain & comp-sci newbies who may not be familiar with factory patterns or the merge sort algorithm.

cross-contract-high-level and cross-contract-low-level also demonstrate the following features:

Simple function call;
Callback;
Money transfer;

Are we going to extract them into separate examples too?


Update Web Bluetooth article

Here's an update to the Web Bluetooth article.
Live preview at https://updatewebbluetootharticle-dot-weasel-dot-web-central.appspot.com/web/updates/2015/07/interact-with-ble-devices-on-the-web
R=@scheib @jyasskin @g-ortuno

I found a few things that need to be fixed before we can merge this.

Thank you @jpmedley! I'll fix those.

@g-ortuno @jpmedley I've addressed your feedback at https://github.com/google/WebFundamentals/pull/3025/commits/2b99788d48e8d6801e34dd176e88bb2be7ec20ca.
If that looks good to you, I'll ask @petele to merge and push it live.

bluetooth code lgtm bar one nit

@g-ortuno's feedback is addressed.
Please @petele @PaulKinlan, can we merge it and push this live?

merged - will push live later today or early tomorrow.

It is now live at https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web Thank you @petele!


Supporting async-only jstransformers

I'm currently working to get my blog caught up with the changes in layouts. I'm using qejs as my template engine, so was happy to find that there was an existing jstransformer. Unfortunately, when running, I get the error The Transform qejs does not support rendering synchronously.
I dug into the code a bit for metalsmith-layouts, jstransformer, and jstransformer-qejs, and the issue appears to be a combination of conflicting designs.
First, metalsmith-layouts expects to call the layout engine synchronously.
https://github.com/metalsmith/metalsmith-layouts/blob/1e633cb02f5b4feb04e8f6e79525950c472edaf8/lib/index.js#L60
Second, jstransformer provides different render methods for sync and async
https://github.com/jstransformers/jstransformer/blob/69fd94c47500fe4d4c8d9f1ac2918c2a55075db0/index.js#L318-L359
Finally, jtransformer-qejs only supports async rendering
https://github.com/jstransformers/jstransformer-qejs/blob/2ec3c78a302d3c361a45622ae49d0c0bab44754e/index.js#L10
Because it isn't really possible (nor desirable) to have metalsmith-layouts be aware of the jstransformer being used, it seems reasonable to add an renderAsync:bool option to the plugin and branch accordingly in metalsmith-layouts. I'm happy to put a PR together but first wanted to get some feedback on the issue and proposed solution.

Hi @howarddierking, thanks for bringing this to my attention. Actually, since jstransformer's renderFileAsync falls back to the synchronous methods, I think it should be fine to start using that instead of the current renderFile. We're already using promises here so it should be fine to start using async rendering.
In the callback passed to renderFileAsync we'd just need to update file.contents, call debug and resolve. Other than that adding some tests for this new behaviour should be all that's needed. Let me know what you think and feel free to submit a PR if this would work for you.

ah - I had actually missed the fallback detail in renderFileAsync.
I have it working with a switch using the following -
  if(settings.renderAsync){
    return transform.renderFileAsync(layoutPath, settings.engineOptions, locals)
    .then(rendered => {
      file.contents = Buffer.from(rendered.body);
      debug(`done rendering ${filename}`);
    })
  } else {
    // Transform the contents
    contents = transform.renderFile(layoutPath, settings.engineOptions, locals).body;

    // Update file with results
    // eslint-disable-next-line no-param-reassign
    file.contents = Buffer.from(contents);

    debug(`done rendering ${filename}`);
    return Promise.resolve();
  }

I'll pull out the switch to just use async, verify with the tests, and send you a PR.


Add two new books: React and Scratch

What does this PR do?
Add Resource(s)
For resources
Description
Book about react and book about sractch.
Why is this valuable (or not)
Because it is one of the best react books translated into Spanish.
How do we know it's really free?
Check it.
For book lists, is it a book?
Yes.
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

please resolve conflicts.

please resolve conflicts.

Because they have erased books .. As it? -> El camino para aprender React (https://leanpub.com/the-road-to-learn-react-spanish) ¿EM? .. 🤦♂


Composer

I'm using L5 and with command anouar/paypalpayment:~1.* I have an error and if I use 1.* I have old version not for L5, to solv problem I have overwrite folder from the online version.

try anouar/paypalpayment:1.*

if that doesn't work follow thus steps:

-Remove the package entirely from under vendor folder
-Remove the package from composer.json file
*- under composer.lock file find the package object and remove it , do the same for the paypal sdk , we're using new one .

Run: composer require anouar/paypalpayment:1.* --prefer-source
Now you should have the L5 version .
Feel free to reopen this issue if it doesn't work


Deletes arcs.core.data.Entity and replaces its usages with RawEntity.

Also updates DatabaseImpl to use Referenceables everywhere.

Actually there's a ton missing. Don't review this yet.

OK I fixed it now, I think. Please review away!


[2.4] [WIP]monitoring refactor: remove project monitoring, use cluster monitoring support all the function

update istio/kiali chart, add token to header when call prometheus endpoint
update monitoring/prometheus, montioring/grafana to support project monitoring refactor

Issue: https://github.com/cnrancher/pandaria/issues/668

may need to update rancher min version later.