Live playback problem on Safari + Shaka

Hi, I'm experiencing problems with live Shaka playback on Safari. I've tested on Safari 10 Beta and Safari 9 using v1.6 appshot (http://v1-6-5.shaka-player-demo.appspot.com/) and v2.0 appshot (https://shaka-player-demo.appspot.com/demo/).
Attached is the zip file of the sample manifest file, init files, and some segments. The same files play well on Chrome but does not play on Safari. Specifically, what I see on Safari is that the v1.6 appshot demo player will show a frame or two and then suddenly stop playing. The v2.0 appshot will see an infinite spinner.
What could be the issue here? Is there a known case / issue with live Shaka playback on Safari browsers? Or is there some defects in one / multiple of the files I attached below that hinders live playback on Safari?
Thank you in advance!
Safari Shaka not playing.zip

Can you provide a public manifest URL we can use to reproduce?  That will be much easier than trying to use the zip file you attached.  If you can't publish the URL, feel free to get my email address from CONTRIBUTORS and email it to me privately.
Can you provide a debug log of your issue?  Use this URL and open the JS console to collect the log: https://shaka-player-demo.appspot.com/demo/?debug

Hi Joey. I am working with Lucas on this and will send you an email with some more details. Thanks!

So far there appears to be a MediaSource bug or perhaps decoder bug in Safari.  There are hundreds of gaps in the timeline on Safari only a few minutes after starting the stream.  Playback is stalled out and the playhead quickly gets far behind the seek range.  None of these issues show up on Chrome.

@DanielBaulig, @iw1000, were you able to resolve these content issues?  Were any bugs filed with Apple?

Closing due to inactivity.


Allow controls to be created without having a canvas as parent

This would be useful if you don't have the parent you want for a control available at the time you are creating the control.
Currently, if the parent specified at creation doesn't lead to the canvas, the constructor throws an error.

In the current model, the canvas is required for the explicit order of operations to exist for the rendering to be agnostic. Changing this will break that flexibility, so in this iteration it will be required for now.
It may be something we can review later, but the library is designed to be canvas based and a control outside of the canvas is an anti-pattern. Thanks for the idea.


repl: reset tty cooked mode on ^D

Before this commit, pressing ^D twice would exit the REPL but leave
the terminal in raw mode. Fix that by calling exit() directly instead
of closing the SIGINT listener.
That leaves just one reference to the sigint_h variable in repl.js,
the assignment in termInit(), but stepping through the code suggests
that's okay: the garbage collector marks it but doesn't collect it.
Fixes: https://github.com/saghul/quv/issues/18

Cheers Ben!


Upgrade to Scala 3.2.2

This comit updates scalac version to 3.2.2 and resolve resulting errors and warnings.
I think changes except https://github.com/es-meta/esmeta/commit/c8b082aff21a17e13ca2a9f29e1c90b3e1f557ba is not controversial. With https://github.com/es-meta/esmeta/commit/c8b082aff21a17e13ca2a9f29e1c90b3e1f557ba, I think this preserves existing semantics and was the most succint way in doing so.
This is needed for future upgrade to 3.3 which allows support of unused warnings lint.

Thansk, @doehyunbaek! It looks good to me. 👍🏻
I merged your PR after refactoring several parts to remove @unchecked.


Problem with max_inflight configuration

Configured {max_inflight, 10} in emqttd-1.1.2. Dashboard correctly reflects the configured value and shows MaxInflight=10 for all the sessions.
However, I can still publish more than 10 messages with QoS=1 and have ALL OF THEM delivered when the target client reconnects and resumes the previous session. Also, the AwaitingAck value for the session in the Dashboard always reports 0, even while the client is disconnected and all the messages are waiting to be delivered.
Is this a bug, or am I misunderstanding something?
Thanks!

Got it! I didn't realize the meaning of the queue configuration part. Sorry for the false alarm.


Enable callout node in label annotation

This PR enables callout node in the LABEL annotation in order to see the relation between the selected point and the label.
Often applying a label annotation, you can not see to which point is referring to and a simple callout can help.

The callout is  a node of label annotation options:
{
  type: 'label',
  ...
  callout: {
    // callout options
  },
  ...
}

Name
Type
Default
Description

borderCapStyle
string
'butt'
Cap style of the border line of callout.

borderColor
Color
undefined
Stroke color of the pointer of the callout.

borderDash
number[]
[]
Length and spacing of dashes of callout.

borderDashOffset
number
0
Offset for line dashes of callout.

borderJoinStyle
string
'miter'
Border line joint style of the callout.

borderWidth
number
1
Stroke width of the pointer of the callout.

enabled
boolean
false
If true, the callout is drawn.

margin
number
5
Amount of pixels between the label and the callout separator.

position
string
'auto'
The position of callout, with respect to the label. Could be left, top, right, bottom or auto.

side
number
5
Width of the starter line of callout pointer.

start
number
0.5
The percentage of the separator dimension to use as starting point for callaout pointer.

drawPoint
boolean
false
if true, the selected point is drawn.

pointBackgroundColor
Color
undefined
Fill color of the selected point.

pointBorderColor
Color
undefined
Stroke color of the selected point.

pointBorderDash
number[]
[]
Length and spacing of dashes of the border of the selected point.

pointBorderDashOffset
number
0
Offset for line dashes of the border of the selected point.

pointBorderWidth
number
undefined
Stroke width of the selected point.

pointRadius
number
3
Radius of the selected point.

TODO

[ ] test cases
[ ] documentation
[ ] types definition
[ ] waiting for #506 merging

Wondering if point element from core should be used to draw the point.

Wondering if point element from core should be used to draw the point.

This PR is still a working in progress. The answer is yes but, having decided to avoid the inheritance among elements, I have in my todo to create a drawPoint function in helpers. Probably also inRange logic could be common with a specific function in the helpers. More in the next days.
Furthermore (not in this PR), I would like to review the current exported helpers function in order do not use element methods (i.e. getProps) but to enable the usage of that functions by objects... Maybe could be helpful when (but also if) the custom annotation elements will be implemented (I have a prototype also for that but, first, the topic needs a discussion).

Wondering if point element from core should be used to draw the point.

DONE!

@kurkle I'd like to wait for PR #506 approval before giving it ready for review. What do you think?

I was thinking that point could deserve a own node. Going to this direction, this enables the point drawing, also without callout, improving the user experience, seeing the point anyway.
{
  type: 'label',
  ...
  callout: {
    // callout options
  },
  point: {
    // point options
  },
  ...
}

Sample how the point can be drawn without callout:

What do you think? Make sense?

I see the Node.js CI / build (windows-latest)  failed for timeout...

This needs a rebase now.
Some samples would be good btw.

Some samples would be good btw.

I use the samples in that folder as "first" functional test. When I'm coding, it's really comfortable to test by a web page that you can run when you want (with console) instead to use the test cases.

This needs a rebase now.

Done!


Shocked grills are duplicating the damage dealt on a single interaction

Description
Electrifying yourself on a grill is duplicating the initial damage and causing double the damage dealt.
Reproduction
Touch a funni grill built over wires.
Screenshots
This is me walking into the grill once. You can see that the logs show a duplicate issue of the damage being dealt twice at the same instant. A look on a health analyzer confirms that the damage is being duplicated.

Additional context
This might be why grills are so effective at one shotting people.

It looks like there are two collision events raised simultaneously. The contacts in SharedPhysicsSystem.Contacts.cs seem to be duplicated. Might have something to do with the collision/physics changes made 3-4 weeks back? Either way it seems like something for a smart engine person to look at.

The contacts in SharedPhysicsSystem.Contacts.cs seem to be duplicated. Might have something to do with the collision/physics changes made 3-4 weeks back? Either way it seems like something for a smart engine person to look at.

It's not duplicated.
Content is relying upon only 1 collision event being generated when that is not the case in practice when walking into a wall is going to continuously regenerate them (as mover code sets velocity and the solver will solve until the contacts are no longer touching).
Electrocution just needs a cooldown and not assume it can just shock someone every single tick.

Okay so https://github.com/space-wizards/space-station-14/blob/25763e4ace85779bc44c9a5c786df66391886714/Content.Server/Electrocution/ElectrocutionSystem.cs#L84 is doing an update loop on electrocutions so one electrocution is for startcollide and the other is the update loop. This update loop already has very sussy code in it and tbh should be removed.


feat(amp): update promtheusservice rulegroupsnamespace

Signed-off-by: Romain Dauby<EMAIL_ADDRESS>Description of your changes
Updated prometheusservice/amp RuleGroupsNamespace resource with the custom update feature.
Fixes #1480
I have:

[x] Read and followed Crossplane's contribution process.
[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
$ k apply -f examples/prometheusservice/workspace.yaml
workspace.prometheusservice.aws.crossplane.io/example created

$ k get workspace
NAME      READY   SYNCED   EXTERNAL-NAME
example   True    True     ws-651f2dfc-8750-4115-82d9-8d1d2bfa3b9b

$ k apply -f examples/prometheusservice/rulegroupsnamespace.yaml
rulegroupsnamespace.prometheusservice.aws.crossplane.io/example-rule created
$ k get rulegroupsnamespace
NAME           READY   SYNCED   EXTERNAL-NAME
example-rule   True    True     arn:aws:aps:us-east-1:015890463774:rulegroupsnamespace/ws-651f2dfc-8750-4115-82d9-8d1d2bfa3b9b/example-rule

$ k apply -f examples/prometheusservice/5m-rulegroupsnamespace.yaml

The code generation make generate is replacing manually edited code.
I don't know if we should update the code generator or make exceptions in this project Makefile targets. As mentionned in the CODE_GENERATION.md documentation we can make manual edits for Update actions.


Changed the GeneratorActor to send as little messages as possible

Very good.
Doing gods work.
I'll merge it


Update azure-stack-solution-machine-learning.md

fix az provider list command query.

@ebibibi : Thanks for your contribution! The author, @mattbriggs, has been notified to review your proposed change.

#sign-off


scm versionning fails when package is not top-level directory

Hello there,
Say you have a monorepo approach and your top-level .git directory and your pyproject.toml resides in a subdirectory, then it seems pdm buid fails to pick up the version and always sets it to 0.0.0.
I was able to reproduce with a simple project into a subdir of the top-level directory containing the .git directory and using:
[project]
name = "mylib"
dynamic = ["version"]
description = ""
authors = [
    {name = "", email = ""},
]
dependencies = []
requires-python = ">=3.11"
readme = "README.md"
license = {text = "MIT"}

[build-system]
requires = ["pdm-backend"]
build-backend = "pdm.backend"

[tool.pdm]
version = { source = "scm" }

$ cd /tmp/top
$ ls .git
branches  COMMIT_EDITMSG  config  description  HEAD  hooks  index  info  logs  objects  refs
$ cd ./mylib
$ git tag
0.1.0
$ pdm build
Building sdist...
Built sdist at /tmp/top/mylib/dist/mylib-0.0.0.tar.gz
Building wheel...
Built wheel at /tmp/top/mylib/dist/mylib-0.0.0-py3-none-any.whl

As a side, maybe related, question. The code seems to run this command
git describe --dirty --tags --long --match *.*

I was curious why that match pattern?
For instance in that repo, if I run:
$ git describe --dirty --tags --long --match *.*
fatal: No names found, cannot describe anything.

but with a different pattern:
$ git describe --dirty --tags --long --match *.*.*
0.1.0-0-g919ff2e

I'm not sure why this was the pattern you went for?

I was curious why that match pattern?

Wrap the *.* with single quotes to avoid being expanded and you will get the right info. So it isn't the issue.


Warn re:status for official octokit libraries

Why:
https://github.com/github/docs/issues/14926#issuecomment-1031887064

What's being changed:

Adding a warning about maintenance status.

Note: I chose not to mention the announcement bit as it seems there was one of sorts later, and I don't think it's helpful to someone investigating the state of libraries. That said, I'm happy to let someone merge in any content changes they wish.
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@jsoref
Thanks so much for opening a PR! I'll get this triaged for review :zap:


Message displayed in browser on sql integrity error.

Playing with the forms example and added a checkconstraint to first_name (first_name not NULL). When I test this out it fails as wanted but the error message appears in the browser, "Integrity error."
How to catch this error? I think this might have to be caught with a custom validator and do something similar to a len(first_name) > 64 and notify the user correctly. (no blank names)
I am not running Debug=True.

This seems to be my misunderstanding. The error is returned to the browser in a flash from sqla/view.py.  I would rather have it return an error to the user so that's what I need to do.
# Error handler
    def handle_view_exception(self, exc):
        if isinstance(exc, IntegrityError):
            if current_app.config.get('ADMIN_RAISE_ON_VIEW_EXCEPTION'):
                raise
            else:
                flash(gettext('Integrity error. %(message)s', message=text_type(exc)), 'error')
            return True

        return super(ModelView, self).handle_view_exception(exc)


How to use this with PM2?

Title says it all.

We do not currently support pm2, so I can't give you a strong answer. If something as simple as pm2 start isn't working, you'll need to play around with it and get it to work yourself.
I'd strongly advise joining the discord server at https://discord.io/rayzrdevofficial - there's a few developers and some other people that may be willing to work with you on this.

pm2 isn't officially supported, but it should be as simple as running pm2 start src/bot.js from inside the SharpBot folder.


WASM API for Console Pretty Printing

setwidth, precision, align left / right.

Is there a reason iostream can't be used for this?

@wanderingbort @heifner @spoonincode Is this still a desire or can it be closed?

There may be a desire for this however, it depends largely on a complete view of the developer tools we want to support.  Adding this as intrinsics in contracts puts burden on the CDT and the users to compile "proper" wasm for deployment where these intrinsics should not be available.  That usability concern means that we are complicating the development pipeline for something with an unquantified value proposition.
For now we should close this and re-evaluate it in the space of the CDT OR in some higher-level conversation about developer tooling/workflow.


Unable to hear anything after accepting the call / No media/rtp data received

After successfully registering the client and accepting the call using the example code from https://github.com/emiago/sipgox/blob/main/echome/echouas/main.go, I am encountering an issue where I am unable to hear anything after accepting the call. It seems that my remote IP is not declared in a Via header and the rport is missing in the INVITE request. Please note that the network with IP "185.79*" belongs to the external SIP provider that I am using for this setup. I'm behind a NAT.
During the client registration, my remote IP was passed successfully in the via header as shown. However, this does not appear to be handed over afterwards...
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;received=95.88.xx.xx;branch=z9hG4bK.NlG0tZiVmSNMaExY;rport=56985;alias

I suspect that the SIP registrar needs to know my public IP or a connection via a TURN/STUN server, but I am unsure how to proceed from this point.
I would greatly appreciate any assistance or guidance on this matter.
Thank you!
Example code I'm struggling with:
	phone := sipgox.NewPhone(ua, phoneOpts...)
	ctx, _ := context.WithCancel(context.Background())
	dialog, err := phone.Answer(ctx, sipgox.AnswerOptions{
		Ringtime: 1 * time.Second,
	})
	if err != nil {
		log.Fatal().Err(err).Msg("Fail to answer")
	}

	sig := make(chan os.Signal)
	signal.Notify(sig, os.Interrupt)
	// Start echo
	go func() {
		for {
			p, err := dialog.ReadRTP()
			if err != nil {
				if errors.Is(err, io.ErrClosedPipe) {
					return
				}
				log.Error().Err(err).Msg("Fail to read RTP")
				return
			}

			log.Info().Msg(p.String())

			p.Payload = append(p.Payload, bytes.Repeat(p.Payload, *echoCount-1)...)

			if err := dialog.WriteRTP(&p); err != nil {
				log.Error().Err(err).Msg("Fail to echo RTP")
				return
			}
		}
	}()

	select {
	case <-sig:
		ctx, _ := context.WithTimeout(context.Background(), 3*time.Second)
		dialog.Hangup(ctx)
		return

	case <-dialog.Done():
		return
	}

SIP Debug log:
Jan  2 22:46:37.734425 INF REGISTER sip:777636ppms@fpbx.de:5060 SIP/2.0
Jan  2 22:46:37.735118 DBG transportlayer > DNS Resolving host=fpbx.de
Jan  2 22:46:37.759771 DBG transportlayer > Active connection not found addr=<IP_ADDRESS>:5060
Jan  2 22:46:37.759916 DBG transportlayer > Via header used for creating connection host=<IP_ADDRESS> port=0
Jan  2 22:46:37.760419 DBG transport<UDP> > New connection raddr=<IP_ADDRESS>:5060
Jan  2 22:46:37.760419 DBG UDP write to <IP_ADDRESS>:56985 -> <IP_ADDRESS>:5060:
REGISTER sip:777636pxxx@fpbx.de:5060 SIP/2.0
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;alias;branch=z9hG4bK.XRpchG56MkccPuVR;rport
From: "777636pxxx" <sip:777636pxxx@fpbx.de?transport=udp>;tag=Rq4NEOtiBYVJ1DO9
Contact: <sip:777636pxxx@<IP_ADDRESS>:5062>
P-Preferred-Identity<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Call-ID: f05d7ade-094a-4b02-80ff-6ccc793fabfd
CSeq: 1 REGISTER
Max-Forwards: 70
Content-Length: 0

Jan  2 22:46:37.782563 DBG UDP read from <IP_ADDRESS>:56985 <- <IP_ADDRESS>:5060:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;received=95.88.xx.xx;alias;branch=z9hG4bK.XRpchG56MkccPuVR;rport=56985
From: "777636pxxx" <sip:777636pxxx@fpbx.de?transport=udp>;tag=Rq4NEOtiBYVJ1DO9
To: <sip:777636pxxx@fpbx.de>;tag=9c7f98d1e39fa449cebe26efa5526d4e.44f70000
Call-ID: f05d7ade-094a-4b02-80ff-6ccc793fabfd
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="fpbx.de", nonce="ZZSFaWWUhD3tvxRs6/p2gRWTgJUJBq7i"
Content-Length: 0

Jan  2 22:46:37.783244 INF Received status status=401
Jan  2 22:46:37.783748 DBG UDP write to <IP_ADDRESS>:56985 -> <IP_ADDRESS>:5060:
REGISTER sip:777636pxxx@fpbx.de:5060 SIP/2.0
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;branch=z9hG4bK.NlG0tZiVmSNMaExY;rport;alias
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;alias;branch=z9hG4bK.XRpchG56MkccPuVR;rport=56985;received=<IP_ADDRESS>
From: "777636pxxx" <sip:777636pxxx@fpbx.de?transport=udp>;tag=Rq4NEOtiBYVJ1DO9
Contact: <sip:777636pxxx@<IP_ADDRESS>:5062>
P-Preferred-Identity<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Call-ID: f05d7ade-094a-4b02-80ff-6ccc793fabfd
CSeq: 1 REGISTER
Max-Forwards: 70
Content-Length: 0
Authorization: Digest username="777636pxxx", realm="fpbx.de", nonce="ZZSFaWWUhD3tvxRs6/p2gRWTgJUJBq7i", uri="fpbx.de", response="9fe8b5372e69xx0722ed6b25230xxxxx"

Jan  2 22:46:37.806454 DBG UDP read from <IP_ADDRESS>:56985 <- <IP_ADDRESS>:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;received=95.88.xx.xx;branch=z9hG4bK.NlG0tZiVmSNMaExY;rport=56985;alias
Via: SIP/2.0/UDP <IP_ADDRESS>:56985;alias;branch=z9hG4bK.XRpchG56MkccPuVR;rport=56985;received=<IP_ADDRESS>
From: "777636pxxx" <sip:777636pxxx@fpbx.de?transport=udp>;tag=Rq4NEOtiBYVJ1DO9
To: <sip:777636pxxx@fpbx.de>;tag=9c7f98d1e39fa449cebe26efa5526d4e.44f70000
Call-ID: f05d7ade-094a-4b02-80ff-6ccc793fabfd
CSeq: 1 REGISTER
Contact: <sip:777636pxxx@<IP_ADDRESS>:5062>;expires=720;received="sip:95.88.xx.xx:56985"
Path: <sip:<IP_ADDRESS>;lr;received=sip:95.88.xx.xx:56985;r2=on>,<sip:<IP_ADDRESS>;lr;received=sip:95.88.xx.xx:56985;r2=on>
Content-Length: 0

Jan  2 22:46:37.806936 INF Client registered
Jan  2 22:46:37.807439 INF Answer > Listening on addr=<IP_ADDRESS>:5062 network=udp
Jan  2 22:46:37.807439 INF Answer > Waiting for INVITE...
Jan  2 22:46:37.807439 DBG transport<UDP> > begin listening on UDP <IP_ADDRESS>:5062
Jan  2 22:46:41.108158 DBG UDP read from <IP_ADDRESS>:56985 <- <IP_ADDRESS>:5060:
INVITE sip:777636pxxx@<IP_ADDRESS>:5062 SIP/2.0
Record-Route: <sip:<IP_ADDRESS>;r2=on;lr>
Record-Route: <sip:<IP_ADDRESS>;r2=on;lr>
Record-Route: <sip:<IP_ADDRESS>;lr=on;did=e43.6184>
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.1e7484b8e77f14e41cd8ac7d201e0d0b.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.fd297cff1a5451c213cf9a941e5af7ec.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.9f7dafffaef173d08fa4467305cf843a.0
Via: SIP/2.0/UDP <IP_ADDRESS>:7010;branch=z9hG4bK3e1a70fc
Max-Forwards: 67
From: "0151xxxxxxxx" <sip:0151xxxxxxxx@fpbx.de:7010>;tag=as0d473f5a
To<EMAIL_ADDRESS>Contact: <sip:0151xxxxxxxx@<IP_ADDRESS>:7010>
Call-ID<EMAIL_ADDRESS>CSeq: 102 INVITE
Session-Expires: 14400
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Type: application/sdp
Content-Length: 304

v=0
o=-<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>
s=-
c=IN IP4 <IP_ADDRESS>
t=0 0
m=audio 21108 RTP/AVP 9 8 0 18 101
a=rtpmap:9 G722/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv

Jan  2 22:46:41.110160 DBG transportlayer > getting connection addr=<IP_ADDRESS>:5060 network=udp
Jan  2 22:46:41.111224 INF Answer > Request: INVITE sip:777636pxxx@<IP_ADDRESS>:5062 SIP/2.0<EMAIL_ADDRESS>from="\"0151xxxxxxxx\" <sip:0151xxxxxxxx@fpbx.de:7010>;tag=as0d473f5a"
Jan  2 22:46:41.111772 DBG UDP write to <IP_ADDRESS>:56985 -> <IP_ADDRESS>:5060:
SIP/2.0 180 Ringing
Record-Route: <sip:<IP_ADDRESS>;r2=on;lr>
Record-Route: <sip:<IP_ADDRESS>;r2=on;lr>
Record-Route: <sip:<IP_ADDRESS>;did=e43.6184;lr=on>
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.1e7484b8e77f14e41cd8ac7d201e0d0b.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.fd297cff1a5451c213cf9a941e5af7ec.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.9f7dafffaef173d08fa4467305cf843a.0
Via: SIP/2.0/UDP <IP_ADDRESS>:7010;branch=z9hG4bK3e1a70fc
From: "0151xxxxxxxx" <sip:0151xxxxxxxx@fpbx.de:7010>;tag=as0d473f5a
To: <sip:777636pxxx@fpbx.de>;tag=4e82702d-9239-4973-a58c-012e43ac8a5f
Call-ID<EMAIL_ADDRESS>CSeq: 102 INVITE
Content-Length: 0
Contact: <sip:777636pxxx@<IP_ADDRESS>:5062?transport=udp>

Jan  2 22:46:41.112969 INF Answer > Response: SIP/2.0 180 Ringing
Jan  2 22:46:42.120260 INF Answer > Media/RTP session created formats=[0] localAddr=<IP_ADDRESS>:51386 remoteAddr=<IP_ADDRESS>:21108
Jan  2 22:46:42.121787 INF Answer > Answering call
Jan  2 22:46:42.122563 DBG UDP write to <IP_ADDRESS>:56985 -> <IP_ADDRESS>:5060:
SIP/2.0 200 OK
Record-Route: <sip:<IP_ADDRESS>;r2=on;lr>
Record-Route: <sip:<IP_ADDRESS>;lr;r2=on>
Record-Route: <sip:<IP_ADDRESS>;lr=on;did=e43.6184>
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.1e7484b8e77f14e41cd8ac7d201e0d0b.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.fd297cff1a5451c213cf9a941e5af7ec.0
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKf169.9f7dafffaef173d08fa4467305cf843a.0
Via: SIP/2.0/UDP <IP_ADDRESS>:7010;branch=z9hG4bK3e1a70fc
From: "0151xxxxxxxx" <sip:0151xxxxxxxx@fpbx.de:7010>;tag=as0d473f5a
To: <sip:777636pxxx@fpbx.de>;tag=4c942bcb-c645-4165-b8cb-a4b1f6456975
Call-ID<EMAIL_ADDRESS>CSeq: 102 INVITE
Content-Length: 161
Content-Type: application/sdp
Contact: <sip:777636pxxx@<IP_ADDRESS>:5062?transport=udp>

v=0
o=user1<PHONE_NUMBER><PHONE_NUMBER> IN IP4 <IP_ADDRESS>
s=Sip Go Media
c=IN IP4 <IP_ADDRESS>
t=0 0
m=audio 51386 RTP/AVP 0
a=sendrecv
a=rtpmap:0 PCMU/8000
Jan  2 22:46:42.124231 INF Answer > Response: SIP/2.0 200 OK
Jan  2 22:46:54.136843 DBG UDP read from <IP_ADDRESS>:56985 <- <IP_ADDRESS>:5060:
OPTIONS sip:777636pxxx@<IP_ADDRESS>:5062 SIP/2.0
Max-Forwards: 10
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKd13c.ca38689d6214e7d4311b8584371f6af1.0;ping=1
Via: SIP/2.0/UDP <IP_ADDRESS>:5060;branch=z9hG4bK4896857
From: sip:pinger@fpbx.de;tag=uloc-9ea61a-656cf45d-1f0b56-2bb9147-e6f03376-1db9b475
To: sip:777636pxxx@<IP_ADDRESS>:5062
Call-ID<EMAIL_ADDRESS>CSeq: 1 OPTIONS
Content-Length: 0

Jan  2 22:46:54.137097 DBG transportlayer > getting connection addr=<IP_ADDRESS>:5060 network=udp
Jan  2 22:46:54.137600 DBG UDP write to <IP_ADDRESS>:56985 -> <IP_ADDRESS>:5060:
SIP/2.0 200 OK
Via: SIP/2.0/UDP <IP_ADDRESS>;branch=z9hG4bKd13c.ca38689d6214e7d4311b8584371f6af1.0;ping=1
Via: SIP/2.0/UDP <IP_ADDRESS>:5060;branch=z9hG4bK4896857
From: <sip:pinger@fpbx.de>;tag=uloc-9ea61a-656cf45d-1f0b56-2bb9147-e6f03376-1db9b475
To: <sip:777636pxxx@<IP_ADDRESS>:5062>;tag=69ef6717-3050-4c90-b645-14bbd116c668
Call-ID<EMAIL_ADDRESS>CSeq: 1 OPTIONS
Content-Length: 0

Jan  2 22:46:54.137600 DBG transaction.Layer > Server transaction terminating
Jan  2 22:46:54.137600 DBG transaction.Layer > Server transaction destroyed tx=z9hG4bKd13c.ca38689d6214e7d4311b8584371f6af1.0__<IP_ADDRESS>__5060__OPTIONS

@danielchristianschroeter sorry but it seems my replly here got lost.
Here again:
As a client receiver behind NAT after call setup (SIP signaling and rport, received) for media your client needs to start sending some RTP traffic so that your server again understans (relearns) where to send RTP traffic.
NOTE: this must be supported by your server, that is must handle NAT. If not then check STUN and ICE  support.
NOTE2: this is not possible for every NAT so in this case alternative is to have STUN + TURN setup.

Thanks for your reply!
This means, I need to send something with dialog.WriteRTP after the call is answered?
If this is not working, I need to use a STUN, this is not possible within sipgox, right?

correct. Not at the moment.
I am open for discussing your development needs.
sipgox can go many ways, but currently I expect some community support on this regard.
As you are some client focused, I suggest checking can this help. This is already prebuilt sofpthone build on top of sipgo.
https://github.com/emiago/gophone


Update README.md

Took me some time to notice that the suggested npm install doesn't match the branch

Thanks!


mongodb: 3.6.13 -> 3.6.23, 4.0.12 -> 4.0.27, 4.2.8 -> 4.2.17

Motivation for this change
Update releases 3.6, 4.0 and 4.2.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

I'm also working on init of 4.4 and 5.0 releases, will open a separate PR for that.

Result of nixpkgs-review pr 146321 run on x86_64-linux 1

3 packages built:

mongodb-3_6
mongodb-4_0
mongodb-4_2


fixes #848

@tradej @metacosm @Ladicek let me know what you think

@metacosm updated with generic value and explanation. Let me know what you think.

LGTM

thanks @metacosm, merging.


Add Ssqosid.

Add Ssqosid privileged extension,ratified.
https://github.com/riscv/riscv-ssqosid

@pz9115 - this is already integrated into supervisor.adoc but we had commented it out to wait for Priv 1.13 to be released. Once Priv 1.13 is released (should happen in next couple of weeks) - we will uncomment the code. Thanks much for the PR but this can be closed.

Okay, thank you for mention it.


Add an option for hiding placeholder elements

When drafting a paper, one may send the manuscript to collaborators for reviewing. For this, it would be great if one can hide all/specific placeholder elements by using an option when loading the package.
It might be even more helpful if one can choose to hide certain types of placeholder elements, e.g. those created with \skelnote{}.

I just started looking a little bit at this. Not sure what the progress will be, but for now I've added an option (hide-numbers) to hide the numbers in the margin (which would hide \skelnotes, for example, as long as you also avoid \printskelnotes). You can find it in the branch mlh/hiding.
I'm thinking about other hiding, but I'm not sure what would be the way to go. Hiding placeholders would in general change the "shape" of your document, and I'm not sure it seems super useful to me. And if you do wish to hide things, the most likely scenario seems perhaps to just hide everything? (I don't quite see when you'd want, for example, to hide all placeholder bullet lists in your document, but nothing else …)
At the moment I'm sort of leaning toward only having this option to hide the numbers (which would address your specific \skelnote request), but perhaps you have some input?

Looking through my notes, I see that I do have a to-do about hiding all blocks, where the motivation was to get a more stripped-down outline-like document (i.e., if you have only headlines + \skel-elements). But I'm not sure if it's really useful.

Thanks for the update!
Regarding hiding \skelnote and other placeholder elements, my use cases would be as follows:

For \skelnote elements, I may want to hide both the numbers on the margin and the notes at the end of the manuscript at the same time.
For placeholder elements like \skelpar, I may have two use cases:

Sometimes, I may want to hide the numbers on the margin and the notes at the end but keep the corresponding placeholders in the main document. This is mainly because I may want to show that there should be something there, but I do not want to show my personal notes regarding them.
Sometimes, I may want to hide everything, i.e. the numbers, notes and placeholders. This is the same as your use case, i.e. yielding a "more stripped-down outline-like document".

For \skelnote elements, I may want to hide both the numbers on the margin and the notes at the end of the manuscript at the same time.

Right. My thought was that one could hide the numbers and comment out \printskelnotes, but I guess there's really no case in which you'd want to only hide the numbers, and still print the notes. I guess I could change hide-numbers to hide-notes, which would hide the numbers and make \printskelnotes a no-op.

Sometimes, I may want to hide the numbers on the margin and the notes at the end but keep the corresponding placeholders in the main document. This is mainly because I may want to show that there should be something there, but I do not want to show my personal notes regarding them.

Right. That's what would happen with the hide-notes option.

Sometimes, I may want to hide everything, i.e. the numbers, notes and placeholders. This is the same as your use case, i.e. yielding a "more stripped-down outline-like document".

Right. Is this mostly a hypothetical scenario, or something you've had use for?
My thinking is that as soon as you start working on your document, entering some text here and there, hiding the placeholders would quickly produce a rather weird result; i.e., that this would primarily be useful before any such incremental work. (But that could still be useful, of course – e.g., having a document with only headlines and placeholders w/notes.)

I guess I could change hide-numbers to hide-notes

This would be great!

Is this mostly a hypothetical scenario, or something you've had use for?

To be honest, I haven't used this scenario before, and this is a potential use case for me.

hiding the placeholders would quickly produce a rather weird result; i.e., that this would primarily be useful before any such incremental work. (But that could still be useful, of course – e.g., having a document with only headlines and placeholders w/notes.)

I agree with these two points. Therefore, if this is not too difficult or time-consuming to implement, it could still be valuable in the for certain use cases. :-)

I guess I could change hide-numbers to hide-notes

This would be great!

Heh, I just realized this is an automatic consequence of my current implementation, because it suppresses all \endnotemarks (and therefore, no endnotes exist). But I might as well suppress the actual \endnotetext part, too.

Is this mostly a hypothetical scenario, or something you've had use for?

To be honest, I haven't used this scenario before, and this is a potential use case for me.

hiding the placeholders would quickly produce a rather weird result; i.e., that this would primarily be useful before any such incremental work. (But that could still be useful, of course – e.g., having a document with only headlines and placeholders w/notes.)

I agree with these two points. Therefore, if this is not too difficult or time-consuming to implement, it could still be valuable for certain use cases. :-)

Right. No, it shouldn't be hard to do :-) Just looking at how I can avoid cluttering things too much.

I've updated the branch with a tentative implementation of hide-notes and hide-all. It would be great if you could test them out, and see if they match your expectations :-)
(Should just be a matter of downloading skeldoc.sty from that branch into the same directory as your document, for example.)

I've updated the branch with a tentative implementation of hide-notes and hide-all. It would be great if you could test them out, and see if they match your expectations :-)

Great! I will test them in the next days when writing my paper. 😃

Does this seem to work on your end?

Apologies for the delayed response. I was thinking to confirm this together with a few related feature requests, but haven't summarized them yet. 😅

No problem!-D

In the past two months, I have been using these options when writing my papers, and they work like a charm.

Excellent! I'll probably just merge it, then.

Fixed by #5.


python311Packages.aiopvapi: disable failing tests

Description of changes
Fix build (https://hydra.nixos.org/build/246225355)

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 282305 run on x86_64-linux 1

3 packages built:

home-assistant-component-tests.hunterdouglas_powerview
python311Packages.aiopvapi
python311Packages.aiopvapi.dist


Make it more clear how to deploy in README

Questions
Answers

Description?
Make it more clear how to deploy inside README

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?

Sponsor company

How to test?
No need to test

Closing because of https://github.com/PrestaShop/contextual-help-api/pull/20#discussion_r1210415552


Remove double quotes from external table column definition

this is inconsistent with the partition_by field, for example, this generated SQL:
CREATE EXTERNAL TABLE "x"."y"."z" ("partition_date" date AS '2020-01-01')) PARTITION BY ( partition_date ) WITH LOCATION ...

it throws an error because "partition_date" is not the same as partition_date

ℹ upper case on column names solves the issue


generate reports on the fly, without storing in DB

now faster with direct SQL query, and added back sort and filter

Coverage remained the same at 41.53% when pulling 14bb728a8c0a20d96f3cb4221d7d5cf09c847225 on boris/reports_on_the_fly into a65ceb3f0db97fbc6476f4c60a2dc54b572078f0 on master.

Coverage remained the same at 41.53% when pulling 7e80be83a7c5cfd2c0feb062a1c26a56688739ad on boris/reports_on_the_fly into a1439408984f172db11549ebc44086655d901652 on master.

A test is failing for this change.   Not sure why, yet.
# Running:

....................E

Error:
PipelineOutputsControllerTest#test_should_show_pipeline_output:
NoMethodError: undefined method `pipeline_output' for nil:NilClass
    app/lib/report_helper.rb:25:in `compute_taxon_zscores'
    app/lib/report_helper.rb:4:in `external_report_info'
    app/controllers/pipeline_outputs_controller.rb:20:in `show'
    test/controllers/pipeline_outputs_controller_test.rb:29:in `block in <class:PipelineOutputsControllerTest>'

Coverage remained the same at 41.53% when pulling 03bf0e02ef143608efee034ed85fe893a8b13e29 on boris/reports_on_the_fly into a1439408984f172db11549ebc44086655d901652 on master.

Tests now pass.   There were some spurious '@' characters.

Coverage remained the same at 41.53% when pulling<PHONE_NUMBER>fa3ddc8219f7486fc3829b219533eb on boris/reports_on_the_fly into a1439408984f172db11549ebc44086655d901652 on master.

Coverage remained the same at 41.53% when pulling a9b6e5b0f3fb7151641d587e547fbc4fa6b803a0 on boris/reports_on_the_fly into a1439408984f172db11549ebc44086655d901652 on master.


Auth Lambda Triggers and Storage

Which Category is your question related to?
Auth / Storage
Amplify CLI Version
3.12.0
What AWS Services are you utilizing?
Auth and Storage
Provide additional details e.g. code snippets
I want my custom Post Confirmation trigger to have access to my storage arn - how can I do this locally so that it persists and can safely be pushed to other environments?
Is my only option to edit the '...PostConfirmation-cloudformation-template.json' file? Is this safe to do?

@danhumphrey Did you try amplify function update and give it access to your storage resource?

No, I didn't know I could do that - thank you.


Added reader rewind to remote payload processor

Motivation
Addresses https://github.com/kserve/modelmesh/issues/111.
Modifications
Adds a byteBuf readerIndex rewind before payloads are parsed in the RemotePayloadProcessor, which deals with any concurrency issues arising from a too-early read of a queued payload. This is a workaround that mitigates the effects of some unknown race condition in bytebuf reading, which should likely still be addressed, but this works in the interim.
Result
Null response payloads no longer occur in high-process-time scenarios

@ckadner any updates?

Thanks @RobGeada. I've opened another PR  which will hopefully address this properly, would you mind reviewing that?
It would also be useful to have a unit test for this, but the tests included here don't exercise the actual bug. Ideally we'd have a test that actually runs a local modelmesh with an asyncprocessor configured and can trigger the problem (other unit tests already run modelmesh to test other stuff and could hopefully be used as a starting point and adapted).

Should this PR be closed in favor of PR #120 ?

Should this PR be closed in favor of PR https://github.com/kserve/modelmesh/pull/120 ?

@ckadner yes!  @RobGeada would be great if you could review #120


Bug: Check plugin.json fails

Which package(s) does this bug affect?

[x] Create Plugin
[ ] Sign Plugin
[ ] Plugin E2E
[ ] Plugin Meta Extractor

Package versions
5.9.2

What happened?

What you expected to happen
Expected to pass...
How to reproduce it (as minimally and precisely as possible)

Create a new plugin
Run npx @grafana/create-plugin@latest
Push to empty Git repository
Observe ci workflow

Environment
System:
    OS: macOS 15.1
    CPU: (8) arm64 Apple M2
    Memory: 562.53 MB / 24.00 GB
    Shell: 3.2.57 - /bin/sh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v20.11.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 105.0.5195.102
    Safari: 18.1
  npmPackages:
    @grafana/data: ^11.3.0 => 11.3.0
    @grafana/eslint-config: ^7.0.0 => 7.0.0
    @grafana/plugin-e2e: ^1.12.0 => 1.12.1
    @grafana/runtime: ^11.3.0 => 11.3.0
    @grafana/schema: ^11.3.0 => 11.3.0
    @grafana/tsconfig: ^2.0.0 => 2.0.0
    @grafana/ui: ^11.3.0 => 11.3.0

Additional context
No response

Solved by https://github.com/grafana/plugin-tools/pull/1330


Draft Postgresql IT

TBD
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

https://github.com/Azure/azure-sdk-for-java/issues/30763

Updates
There are few steps to run an IT.
Step1: Provision Azure Resources for integration tests.
Step2: Configure environment variables.
Step3: Run integration tests.
In order to test passwordless feature in postgresql flexible server, in step1 it's needed to provision an Azure postgresql flexible server with Azure AD Admin enabled.
To enable Azure AD Admin,
For now, it can be done by

Azure portal.
Azure CLI which needs azure-cli:2.43.0.

The Azure AD Admin is not available in arm template for postgresql flexible server.
We need to use ARM template to provision Azure resource to run IT(include enabling Azure AD Admin).

In ARM template, we can run azure-cli commands, but the highest version of azure-cli supported in ARM templates is 2.42.0, it doesn't contain the function to enable Azure AD Admin.
The ARM templates of postgesql flexible servers don't support Azure AD Admin yet.

So it's blocked here, we need to wait ARM templates support postgresql flexible server Azure AD Admin or ARM templates support Azure CLI:2.43.0.


Drop redundant total time metric from scan

This fixes #972
I am happy to add in documentation for the metrics too if that is what we want #971

build

it would be nice to have documentation for the metrics but I would think that would be across the board not just for scan so a separate issue.

build

build

build

build

build

build

build


Switch Iceberg to CLI in the GT release image and in the development image

Apart from the risk of doing something new, which we should take IMHO, there are two main issues:

(1) it would require git cli to be present where you want to use GT for git, but we could have a fallback/switchback to the old implementation if we detect git is missing
(2) the current build will probably still use the old implementation as well, even though we now have a separate iceberg-git-cli repository meant to be loaded first, but this is untested

A new tool, GitCliEnabler, was added to play with switching/reverting, on a per repository / all repositories level.

WARNING: do not do this when you have repositories with uncommitted modifications !

A new command line handler, GitCliEnablerCommandLineHandler for the option enablegitcli was added.

This enables the git cli iceberg implementation and switches over the implementation of all existing repositories.
This has no effect on the on disk git repositories themselves.
A number of validations are run before starting, some assertions might fail.
You need the git command line executable installed, accessible, configured and working.
Running without --save can be considered a dry run.

Note: to also save the image after enabling git cli, the following command should be used:
./GlamorousToolkit.app/Contents/MacOS/GlamorousToolkit-cli --interactive GlamorousToolkit.image enablegitcli --save

The --interactive flag is needed because the regular build image has already been opened as such.


Configuration methods with Action for @Nested properties

Expected Behavior
If you have a nested property, for example on a task or extension, it would be nice to automatically get a method that takes an Action for that type to configure it, so that you do not have to do
myNested.property1 = "foo"
myNested.property2 = "bar"

or
myNested.apply {
    property1 = "foo"
    property2 = "bar"
}

or
configure(listOf(myNested)) {
    property1 = "foo"
    property2 = "bar"
}

but can directly do
myNested {
    property1 = "foo"
    property2 = "bar"
}

Thank you for your interest in Gradle!
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

The syntax you propose would imply having something like
operator fun invoke(action: this.() -> R)

This might complicate the implementation a bit but, which is more concerning, it may imply extra mental overload.

That's one option. Another would be to have
fun myNested(action: Action<MyNested>)

wouldn't it?
That should then also cover Groovy DSL right away.
Because there is currently also not Groovy DSL magic that makes it work.
There you currently for example have to do
myNested.tap {
    property1 = "foo"
    property2 = "bar"
}

Thank you for your interest in Gradle!
This feature request is in the backlog of the relevant team and is prioritized by them.

This feature makes sense but existence of workarounds makes it less urgent. We're also not sure how to expose nested objects (i.e. Property<Nested> vs. Nested that contains Property), which also affects the design. The Declarative Gradle effort can provide a different perspective too.
In the end, we need to spend some time at the drawing board to figure out how this can look like and how it should interact with other features.


Enrollment data should be written to the block.

Writing Enrollment data to a block determines the height of the block that can participate in the validation as a validator.
Validators needed for the consensus process can be determined and the number of validators between nodes can be set.
Definition of Done:

[ ] The Enrollment data should be recorded only in the enroll start block.

[ ] When writing to a block, it must be sorted in ascending order by UTXOkey of the enrollment data.

[ ] The node store the enrolled block height.

How to implement

create a Query to import the elements from the Enrollment manager.

The conditions for this must be taken in order of the UTXOkey's ascending order with the null height of the block.

Record the target enrollments at block generation.

When the enrollment data is stored in a block, the height of that block must be renewed in the DB of the node.

Done in https://github.com/bpfkorea/agora/pull/620 and https://github.com/bpfkorea/agora/pull/504 and some related PRs.


Remove repeated missing file msg because some games don't require assets

Description
Like title says, some games don't require assets at all so the repetitive messages gets annoying. It would be better if it was moved to when the actual saving happens but I'm not sure how to do that and I don't think it's needed.
(This also means I don't have to press escape if I cargo run from inside helix editor to get rid of the output text whenever I close the game too quickly)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@jjant I just did a --release for windows and the console pops up with those 3 lines, by removing them here would that stop the console from popping up as well?


Unable to use only OffHeap store with JSR107 Cache

Configuring a JSR107 cache with only offHeap store  fails du to "java.lang.RuntimeException: store result must not be null . OnHeapStore has a OnHeapStoreStatsSettings which declares the tag 'store'.
But OffHeapCache does not have one.
Starting the cache with only 0 elements configured as Heap works but I see that statistics are false as it seems to count 1 miss for the heap cache and 1 hit for the offheap one.
Moreover, using on heap cache, even if empty, lookup into the heap cache and it also use synchronisation in internal ConcurrentHashMap implementation, so performances are degraded.

I've tried to not use the JSR107 api, but I did not find a way to get JMX statistics though the native ehcache API.

Hello,
Thanks for your report - there is indeed a bug hiding there.


Best practise to debug shiny

I just switched to VSCode for writing Shiny-Apps with custom JS.
Loving the experience so far 🤩 thank´s for this great package btw as it adds ton of value!
An issue I stumbled upon is that I can´t find any ressources on how to debug shiny using the VSCode-R-Debugger. My own attempts failed.
My question is:

Can shiny generally be debugged?
If so: what is the best way to do it?

Could´nt give up on the idea of using VSCode as my main IDE for R (dark mode, git integration, JS, ... 🥰).
Here is a solution I came up with that seem to work.
Prerequisites

Install/ configure VSCode extensions R (by Yuki Ueda) and R Debugger
Use default shiny app structure (see ?shiny::runApp() for possible setups)
Example:

myProject/
├── app.R
├── R/
│   ├── module.R

Set VSCode workspace to the R projects root (e.g. File -> Open Folder... -> myProject)
Create a debug configuration file (prompted for if opening debug tab in VSCode)

Debugging

Set your breakpoints using browser() (see https://shiny.rstudio.com/articles/debugging.html)
Run Debugger in Launch R-Workspace mode
Run shiny::runApp() in the debug console
Your app should fire up in a browser and the breakpoints pause the execution 🎉


Remove duplicated code in mockVoidMethod

Remove duplicated code. Also a precursor for stub API changes.

Also fixes #25


Improve the SETUP.md documentation

The "Tokens and Installing App" section in the SETUP.md file requires clarity and more information to improve the developer onboarding experience. These are the sections that require improvement:
OAuth & Permissions Section
Include a screenshot and write up to guide a developer on how to enable the OAuth Scope for full functionality. Currently there's no guide for this particular section and it's not clear on how to go about it.
Adding New Functions
Demonstrate how someone can add new functions. Include a screenshot and write up.
Test the "Install App to Workspace" step
Confirm if this step under the "Tokens and Installing App" section actually leads to the Slack OAuth UI. Currently I'm an error of "slack-bot doesn’t have a bot user to install" When I click on the "Install App to Workspace" button

@misspee007 Check out this issue, can you give me permission to assign issues?

This looks great @CatherineKiiru. Just let me know whom you would like to assign it to, and I'll handle that for you.

Thanks. @peculiaruc wanted to work on this project, you can assign this issue to her.

Alright. Assigning it to you now @peculiaruc.

Hi @misspee007


feat(tutorial): complete step 4 [Rohit Sharma]

Closes #
{{short description}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

{{Server url: https://api.eu-gb.bluemix.net/  }}


Simple auth feature

Allows one to use django-storage-swift with just a storage URL and generated token.

Going to refactor the implementation a little more. Not sure why I started this pull request pr-emptively.


Add AuthKeyPair to RBAC

AuthKeyPair is inherited from AuthPrivateKey and then from Authentication. (In CLASSES_THAT_PARTICIPATE_IN_RBAC is list of base classes)
In UI:
Compute -> Cloud -> Key Pairs
@miq-bot add_label bug, rbac
@miq-bot assign @gtanzillo
Links
https://bugzilla.redhat.com/show_bug.cgi?id=1441637

The whole CLASSES_THAT_PARTICIPATE_IN_RBAC approach feels weird to me. Wouldn't an inherited singleton.rbac? method, which subclasses could then override, be easier to hook into?

@djberg96 you are right it is weird, I'll think about it. Maybe there is 'technical reason ' why to model should participate to rbac (that it is using acts_as_miq_taggable)
thank you for your comment 👍

Backported to Fine via https://github.com/ManageIQ/manageiq/pull/16865


ERROR: Net 'etherbone_rst' is multiply driven by cell ports FD1S3BX_1.Q and FD1S3BX_3.Q

Today i followed the guide from http://www.fabienm.eu/flf/15-ecp5-board-kit/ to setup yosys and next-pnr. The blinking example is working. Later i continued with this project.
I used ./colorlite.py --build to build everything. But i get the following error:
3.51. Executing CHECK pass (checking for obvious problems).
checking module colorlite..
Warning: multiple conflicting drivers for colorlite.\sys_rst:
    port Q[0] of cell FD1S3BX_1 (TRELLIS_FF)
    port Q[0] of cell FD1S3BX_3 (TRELLIS_FF)
found and reported 1 problems.

3.52. Executing JSON backend.

Warnings: 2 unique messages, 2 total
End of script. Logfile hash: ab23295401, CPU: user 20.76s system 0.13s, MEM: 335.69 MB peak
Yosys 0.9+3565 (git sha1 da3002e5, clang  -fPIC -Os)
Time spent: 20% 34x opt_clean (4 sec), 14% 32x opt_expr (3 sec), ...
ERROR: Net 'etherbone_rst' is multiply driven by cell ports FD1S3BX_1.Q and FD1S3BX_3.Q
0 warnings, 1 error
Traceback (most recent call last):
  File "./colorlite.py", line 133, in <module>
    main()
  File "./colorlite.py", line 120, in main
    builder.build(build_name="colorlite", run=args.build)
  File "/home/xxx/liteX/litex/litex/soc/integration/builder.py", line 214, in build
    vns = self.soc.build(build_dir=self.gateware_dir, **kwargs)
  File "/home/xxx/liteX/litex/litex/soc/integration/soc.py", line 1048, in build
    return self.platform.build(self, *args, **kwargs)
  File "/home/xxx/liteX/litex/litex/build/lattice/platform.py", line 39, in build
    return self.toolchain.build(self, *args, **kwargs)
  File "/home/xxx/liteX/litex/litex/build/lattice/trellis.py", line 234, in build
    _run_script(script)
  File "/home/xxx/liteX/litex/litex/build/lattice/trellis.py", line 164, in _run_script
    raise OSError("Subprocess failed")
OSError: Subprocess failed

Do you know how i can fix this problem?

I got it working by removing Line 50 from colorlite.py

Thanks @jurkov for the feedback, the design indeed had to be updated, which has been done with https://github.com/enjoy-digital/colorlite/commit/b52aa387910a50932ddb29325eb16e1ab3c598b6.


feat: Add Codespace functionality

This PR adds Codespace functionality to the SciPy2024 devcontainer and closes issue https://github.com/uw-ssec/tutorials/issues/12

superseded by #18


Switch to camunda-community-hub-parent

follow the release process of Camunda Community HUB release...

Already implemented...


When PowerToys is updated, the icon on my taskbar vanishes.

Microsoft PowerToys version
0.70.1
Installation method
PowerToys auto-update
Running as admin
admin
Area(s) with issue?
General
Steps to reproduce
1.Power Toys tells me it has a new version.
2.I click "アップデートする" button.
3.I wait until Power Toys finishes its update.
4.When the update finishes, the icon on my taskbar vanishes.
✔ Expected Behavior
4.When the update finishes, the icon on my taskbar remains.
❌ Actual Behavior
4.When the update finishes, the icon on my taskbar vanishes.
Other Software
No response

It vanishes because it seems that each update creates new taskbar icon to manage and it's disabled by default

@SharakPL's issue is reported in Issue #28435. I'm running Windows 10  (22H2) and see two icons in the notification area (renamed to system tray in Windows 11) after an update, but as soon as I mouse over them, one of the icons disappears and all is well, so that issue may be specific to Windows 11.
However, I believe @binbintaro is reporting a different issue. I just updated to v0.80.0 and the icon for open PowerToys windows is blank in the taskbar (not the notification area/system tray):

If I close all PowerToys windows and reopen them, the icon reappears:


Fix test failures against Django main

Fixes #851 (at least for now).
This is built on top of #850, and with a different approach for #847.

Thank you for the patches, I pulled these changes in (I went for removing Python 3.6 support outright, as its at EOL)


refactor(Error): Rewrite custom derived errors with Object.create()

Description:

This is the alternative proposal to fix https://github.com/ReactiveX/rxjs/issues/2178 with rewriting custom derived errors by Object.create()'s classical inheritance by hand.

This approach is based on TypeScript's definitions for build-in object.
By this change, we can upgrade TypeScript 2.1 or later without dropping support for IE9/IE10 for the future.

This is not a breaking change because this patch creates an inheritance by hand instead of TypeScript's transformer.

Related issue (if exists):
https://github.com/ReactiveX/rxjs/issues/2178

@kwonoj how about this?

Coverage increased (+0.001%) to 97.691% when pulling 579cc4657e6e62b139ac51e5fad079e865f0d43e on saneyuki:rewrite-custom-errors into 6922b16f4a297a4acbe8ad2b086c947b7c0d8315 on ReactiveX:master.

Coverage increased (+0.002%) to 97.692% when pulling 49127be76d1bd587f915dc550fd0155bf62e8aaa on saneyuki:rewrite-custom-errors into 6922b16f4a297a4acbe8ad2b086c947b7c0d8315 on ReactiveX:master.

Personally, I'd like to land https://github.com/ReactiveX/rxjs/pull/2202 (and following PR) prior to any-targeting-master changes to enable type inference-validation on each changes. Though this looks solid (and local verification works), always better to have test supports.

Coverage increased (+0.003%) to 97.693% when pulling 2facaf98c295d876ed2adbf09a5b0e0777864e14 on saneyuki:rewrite-custom-errors into 6922b16f4a297a4acbe8ad2b086c947b7c0d8315 on ReactiveX:master.

I added some test cases for this change.

Coverage increased (+0.003%) to 97.693% when pulling b35e05aca5dca6582208c03dd55dcbfe134abdac on saneyuki:rewrite-custom-errors into 6922b16f4a297a4acbe8ad2b086c947b7c0d8315 on ReactiveX:master.

Interesting. I played around with this same approach for a few minutes and TS 2.1 didn't like it when I tried. Heh. Looks good to me, though.

For the record, you can create an intermediate class that "does the right thing" by not explicitly returning from the constructor itself. You could write it as an ES5-style class (much the same way the old code would be compiled), and then derive your classes from that class. That way, much less of the code actually has to be rewritten.
var __extends = (this && this.__extends) || function (d, b) {
    for (var p in b) if (b.hasOwnProperty(p)) d[p] = b[p];
    function __() { this.constructor = d; }
    d.prototype = b === null ? Object.create(b) : (__.prototype = b.prototype, new __());
};

export interface ShimErrorStatic {
    new (message?: string): ShimError;
}
export interface ShimError extends Error {}

export const ShimError: ShimErrorStatic = (function (_super) {
    __extends(C, _super);
    function C(message) {
        _super.apply(this, arguments);
        // ensure that 'message' gets set correctly - wasn't case with old implementation.
        this.message = message;
    }
    return C;
}(Error)) as any;

The only downside is that if you're compiling to ES2015, this winds up being an extra layer that you may find undesirable.

compiling to ES2015, this winds up being an extra layer

@DanielRosenwasser would you able to share how much will it be? I expect ES15 package will be published eventually, so if those are unacceptable amount probably would better to go with existing changes in this PR.

Well you'd have to add the ShimError function that I posted above, and then add an import for each class that extends Error.

Actually, I wonder if you could get away with this, which doesn't need the helper function:
export interface RxErrorStatic {
    new (message?: string): RxError;
}
export interface RxError extends Error {}

export const RxError: RxErrorStatic = function (_super) {
    function RxError(this: Error, message: string) {
        const err = Error.call(this, message);
        this.message = message;
        this.stack = err.stack;
        return err;
    }
    RxError.prototype = Object.create(Error.prototype, {
        constructor: {
            value: RxError,
            enumerable: false,
            writable: true,
            configurable: true,
        },
    });
    return RxError;
}(Error) as any;

@kwonoj
What should I do about this? I feel the current patch is not different from @DanielRosenwasser proposed one.


Support Verifiable Presentation Request

The legacy VC lookup mechanism relies on an ad-hoc object, and uses the /derive endpoint, which is actually not meant for querying but rather for selective disclosure. This introduces a query function which implements the Verifiable Presentation Request mechanism as described in https://w3c-ccg.github.io/vp-request-spec/. An important note is that we make the assumption that an endpoint supporting Verifiable Presentation Request is available at a /query path, which is outside of the VC API specification scope. This assumption is used to distinguish new endpoints vs legacy endpoints.
Currently, only Query by Example VPRs are supported, which is similar to the legacy behavior in a lot of ways. The legacy getVerifiableCredentialAllFromShape function now supports both legacy and VPR-compliant endpoints.
Checklist

[X] All acceptance criteria are met.
[X] Relevant documentation, if any, has been written/updated.
[X] The changelog has been updated, if applicable.
[X] New functions/types have been exported in index.ts, if applicable.
[X] New modules (i.e. new .ts files) are listed in the exports field in package.json, if applicable.
[X] New modules (i.e. new .ts files) are listed in the typedocOptions.entryPoints field in tsconfig.json, if applicable.
[X] Commits in this PR are minimal and have descriptive commit messages.

@NSeydoux re all replies, okay, I'm not sure tbh, but let's go with it I guess.


Wallet microservice

This one includes creating the microservice with the yarn plop command. The microservice generator lives inside the @aufacicenta/aufaxbot/plop branch.


GD-103: Show less stack trace for failing test when using MSTest assertions

Is your feature request related to a problem? Please describe.
As a future QOL enhancement, consider showing less stack if the user is using assertions from the MSTest.TestFramework nuget package. Currently, having these two methods (fiddling with the i is just to have a few more lines in there)
[TestCase]
public void Test1() {
	int i = 2;
	i += 2;

	Assertions.AssertInt(i).IsEqual(1);
}

[TestCase]
public void Test2() {
	int i = 2;
	i += 2;

	Assert.AreEqual(1, i);
}

Running them from the Visual Studio test explorer gives the gdUnit assertions a nice short stack trace with the actual line of the failing assertion easily found and clickable:

while the MSTest assertion has a few more lines and the user has to do more mental parsing to find the actual line that they should click to get straight to the failing assertion

As a reference, running the test through the normal MSTest runner also gives a nice clean message

Describe the solution you'd like
I would like the gdUnit test runner to cut out the other clickable lines from the stack trace and leave only the one that goes straight to the assertion.
Describe alternatives you've considered
Alternatives are the user moves to using the gdUnit assertions or continues to have to mentally parse a few more lines for every failed test.
Additional context
None

If I understand you correctly, you have mixed GdUnit4 assertions and MSTest assertions?
The GdUnit4 test adapter only shows the stack trace generated by the assertion.
It is not intended to mix different assertion APIs. Is there a particular reason why you are using GdUnit4 and MSTest Assertion here?
What I found out is that the MSTest test adapter performs an additional stack trace trim.
https://github.com/microsoft/testfx/blob/main/src/Adapter/MSTest.TestAdapter/Execution/ExceptionHelper.cs#L101

I don't get your point, you only use MSTest assertions but using the GdUnit4 test framework?
Why?

I was under the assumption that I need the GdUnit4 framework to run tests against Godot? I've adapted my current test setup from your example project. And I use MSTest assertions because I always use them, including professionally.
So I have both the actual Godot script code and the tests under one .csproj which has the following dependencies
<ItemGroup>
 	<PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.9.0" />
 	<PackageReference Include="gdUnit4.api" Version="4.2.3" />
 	<PackageReference Include="gdUnit4.test.adapter" Version="1.1.1" />
 	<PackageReference Include="MSTest.TestFramework" Version="3.3.1" />
 </ItemGroup>

This does skirt around the issue that I think there is a need for a better example project, showing multiple tests, how to use ISceneRunner properly, using a single project for everything or one for the Godot stuff and one for testing, etc. etc. But that's for another conversation.

I was under the assumption that I need the GdUnit4 framework to run tests against Godot?

Yes, the gdUnit4.api provides the test runner and assertions to work with Godot code.

And I use MSTest assertions because I always use them, including professionally.

I understand your point, and it should be no problem to use the MSTest assertions inside the GdUnit4 tests.
Ultimately, the assertions throw an exception that the GdUnit4 test framework catches and reports.
In summary, it therefore makes sense to shorten the stack trace as it is done in MSTest adapter.
Thanks for suggesting these improvements.

@DrMouseInc you can upgrade to 4.2.4-rc3

@MikeSchulze Looks much better, thank you again!


[Graph]Review codesnippets in README

The code-snippets in README for libraries that are auto-generated have also been auto-generated.
This issue is to review these code-snippets and to ensure that they are accurate among the data plane libraries for Azure Graph
Related to #4291

This has been resolved with the work in the PR #4754.
Thanks @mikesprague!


Github sample and document does not align

Hello Team,
I was trying to create the sample using :
https://review.docs.microsoft.com/en-us/azure/azure-web-pubsub/tutorial-build-chat?branch=main&tabs=csharp
while I see below parameters :

While running the commans below :
dotnet new web
dotnet add package Microsoft.Azure.WebPubSub.AspNetCore --version 1.0.0-beta.3

If the application is targeting to ASP.NET 6.0 it does not have startup.cs, how do we modify the code then?
or do we need to specify the version while creating the app ?

The code mentioned in article and Github are two different code :

Code on article :
public void ConfigureServices(IServiceCollection services)
{
services.AddWebPubSub(o => o.ServiceEndpoint = new ServiceEndpoint("<connection_string>"))
.AddWebPubSubServiceClient();
}
Code on Github :
services.AddAzureClients(builder =>
{
builder.AddWebPubSubServiceClient(Configuration["Azure:WebPubSub:ConnectionString"], "chat");
});
There is no separate class SampleChatHub in the github article whereas the document ask to create a class
Could you please fix either the document or share the sample that is aligned with the article

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

ID: 6fc0961a-70a2-32c4-0feb-934aa5356b25
Version Independent ID: eff95be1-41e1-353c-9b88-e151d8c598ed
Content: Tutorial - Create a chat app with Azure Web PubSub service
Content Source: articles/azure-web-pubsub/tutorial-build-chat.md
Service: azure-web-pubsub
GitHub Login: @vicancy
Microsoft Alias: lianwei

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks for the feedback! The sample was in PR review and missed to merge. It's updated now and please take a look to have a try!


Child Attribute Selection

Having some issues with selecting read_attrs of a child component. Here is some code to reproduce what I'm seeing. This gives me inconsistent results:
from ophyd import Device, Component as Cpt
from ophyd.sim import SynAxis

class MyDevice(Device):
    x = Cpt(SynAxis)
    y = Cpt(SynAxis)
    z = Cpt(SynAxis)

    _default_read_attrs = ['x.readback', 'y.readback', 'z.readback',
                           'x.setpoint', 'y.setpoint', 'z.setpoint']

print(MyDevice(name='test').read_attrs)

Output:
$ python blah.py
['x', 'x.readback', 'x.setpoint', 'y', 'y.readback', 'z', 'z.setpoint']
$ python blah.py
['x', 'x.setpoint', 'y', 'y.readback', 'y.setpoint', 'z', 'z.setpoint']
$ python blah.py
['x', 'x.readback', 'x.setpoint', 'y', 'y.setpoint', 'z', 'z.setpoint']

It seems like things are getting confused with the redundant naming of a motor and its signal. This also raises the question on what the best way to indicate that you want a read_attr that is component of a compnent using the Kind syntax.

Well, that is deeply wrong...
I suspect the bug is in here
https://github.com/NSLS-II/ophyd/blob/07ab0b2cfc9fa3c5c35989fd58068df686100304/ophyd/device.py#L834-L844

Has this been solved?


Viewing tenant-level query stats

Fixes https://github.com/citusdata/citus_docs/issues/1083
@halilozanakgul could you provide me with updated sample SQL please? The output in the linked issue included columns that I don't see in the view, like cpu_usage_in_this_period. Columns are missing too, like score.

I added cpu_usage_in_this_period in after release branch is created but it is backported, so we have it in the latest version of the branch.
And the score is not something I think user should see. So it's in the citus_stat_tenants() function but not in the view.


Pre-weight AAD before expert analysis

Is it possible to weight AAD using custom list of objects before the active stage of the analysis?

Should be an opportunity to load a list with anomalies and non-anomalies. AAD should take into account both and distributes the weight based on the knowledge about anomalous/non-anomalous nature of labeled objects.


when checkout env: ERROR: No CloudFormation template found at /Users/xxxx/xxxxxx/amplify/#current-cloud-backend/function/newfunctionslayer/newfunctionslayer-awscloudformation-template.json

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm i -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v14.15.4
Amplify CLI Version
5.1.0
What operating system are you using?
Mac
Amplify Categories
function
Amplify Commands
push
Describe the bug
I have created a new lambda layer on SVIL env and pushed it correctly.
When I try to checkout on TEST with:
$amplify env checkout test
I get the following error:
No CloudFormation template found at /Users/xxxx/xxxxxx/amplify/#current-cloud-backend/function/newfunctionslayer/newfunctionslayer-awscloudformation-template.json
Error: No CloudFormation template found at /Users/xxxx/xxxxxx/amplify/#current-cloud-backend/function/newfunctionslayer/newfunctionslayer-awscloudformation-template.json
    at Object.readCFNTemplate (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-cli-core/src/cfnUtilities.ts:9:11)
    at Object.updateConfigOnEnvInit (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/provider-utils/awscloudformation/index.ts:408:57)
    at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/src/index.ts:131:28
    at /usr/local/lib/node_modules/@aws-amplify/cli/node_modules/promise-sequential/index.js:16:18
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)

Expected behavior
amplify env checkout test
then
Initialized your environment successfully.
Reproduction steps
1) amplify env checkout svil
2) create a new lambda layer
3) amplify push --yes
4)  amplify env checkout test
   ---> ERROR

Hi @fgiopp, on the last step, can you try passing in the --restore flag and see if that allows you to check out the other environment successfully? ie amplify env checkout test --restore

I have noticed that despite the Error, the checkout to the environment (TEST) was like almost complete. So, I was able to push TEST. After that I checkout back to SVIL and then finally again to TEST, this time without the Error.


SQL_ERROR from packaged Electron application

Used it in an electronjs, seems it worked on "dev" yet when app is packaged all my queries returns "SQL_ERROR"

I found the issue, it was my asset handling when I package the app. App packaged the database file while writing it as a new empty file. that's why my queries are returning an error.


link: Send linking errors to stderr, not stdout

Should use global.stdmsg?

What's global.stdmsg? I see it used for -v output and being set to stdout in globals.c.

I thought it was supposed to be where error messages go.  But for some reason it isn't being used by errors.c...

stdmsg is used for general messages.  The motivation behind it was that gdc uses stdout to emit assembly code - also at the time there was a lot of randomness around whether stderr or stdout was used in verbose messages.

Can't link.c use the error reporting functions?

Ugh, is this still open? I guess I'll rebase it

Now uses the error function per @ibuclaw , though I'm not sure it makes sense to in some places - e.g. it's also used to report signals received for child programs (for -run), long after the compiler's job is done.

Auto-merge toggled on


[DOCS]:+ Improved configuration.md

Short description and why it's useful
Better readability for the configuration.md
Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility)
[x] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

Contribution and currently important rules acceptance

[x] I read and followed contribution rules
[x] I read the TypeScript Action Plan and adjusted my PR according to it
[x] I read about Vue Storefront Modules and I am aware that every new feature should be a module

Thanks @ruthgeridema :)

Warning; accept current configuration.md (develop). Do not accept the new configuration.md


Wokouts type

How do you know the type of workouts such as cycling, walking, running and etc.

Thanks


Poor training effect

My training effect on the two data sets is far lower than the effect achieved in the original paper. I would like to ask if there is any solution. Could you tell me the method if you have solved it? I hope to get a reply or send the modified code to my email<EMAIL_ADDRESS>if it is convenient. Thank you very much for your help!

Same question.

Same question.

Same question.


Windows: undefined path resolution for directory junctions

This case is from istanbuljs/nyc#554. Reopened here as suggested by @bcoe. Anything mentioned there applies. All files listings and version info located at Gist. More specifics follows:
Problem: directory junctions on windows systems do not excluded from paths correctly.
Description & Case:
First, a structure example. Here, dir is simple directory, while junc is junction to dir (made with mklink /j junc dir)
`-- expr
  +-- dir
  | `-- foo.js
  +-- junc >> dir
  +-- main.js
  `-- package.json

main.js is simple test:
const assert = require('assert')

const exclude = require('test-exclude')

const junctionOnly = exclude({
  exclude: ['dir/']
})

assert.strictEqual(false, junctionOnly.shouldInstrument('dir/foo.js')) // GOOD
assert.strictEqual(true, junctionOnly.shouldInstrument('junc/foo.js')) // GOOD

const plainDirOnly = exclude({
  exclude: ['foo/']
})

assert.strictEqual(true, plainDirOnly.shouldInstrument('dir/foo.js')) // GOOD
assert.strictEqual(false, plainDirOnly.shouldInstrument('junc/foo.js')) // BAD

You can see that assert fails at excluding junctioned path.

Oh crap, sorry for the mess. Wrong repo, duh. =/


handling of breakpoints in mod.rs

Which OS:
Linux
Which LLDB version (lldb -version):
4.0.0
Which VSCode version (Help/About):
1.11.2
What is the problem and how did you get there:
When setting a breakpoint inside one mod.rs file, a breakpoint is set on all mod.rs files that are in the program.
What did you expect to have happened instead (if not obvious):
The breakpoint should be set on one mod.rs file
My guess is that the root cause is that a command along the line "b mod.rs:100" get sent to the debugger, which ambiguous (it should include more parts of the file path...).
example output of breakpoint list:
(here, breakpoints 2.6 - 2.8 are the only ones desired)
2: file = 'mod.rs', line = 397, exact_match = 0, locations = 13, resolved = 3, hit count = 1
  2.1: where = magicstick`futures::sync::mpsc::{{impl}}::inc_num_messages<magicstick::client::Packet> + 350 at mod.rs:397, address = 0x00005613531d4c3e, unresolved, hit count = 0  Options: disabled
  2.2: where = magicstick`futures::sync::mpsc::{{impl}}::inc_num_messages<tokio_core::reactor::Message> + 350 at mod.rs:397, address = 0x00005613531d4e6e, unresolved, hit count = 0  Options: disabled
  2.3: where = magicstick`futures::sync::mpsc::{{impl}}::inc_num_messages<tokio_core::reactor::Message> + 350 at mod.rs:397, address = 0x0000561353237cbe, unresolved, hit count = 0  Options: disabled
  2.4: where = magicstick`futures::sync::mpsc::{{impl}}::inc_num_messages<i32> + 350 at mod.rs:397, address = 0x0000561353237eee, unresolved, hit count = 0  Options: disabled
  2.5: where = magicstick`futures::sync::mpsc::{{impl}}::inc_num_messages<tokio_core::reactor::Message> + 350 at mod.rs:397, address = 0x00005613532649de, unresolved, hit count = 0  Options: disabled
  2.6: where = magicstick`magicstick::ibeacon::{{impl}}::read + 126 at mod.rs:397, address = 0x000056135321b5fe, resolved, hit count = 1
  2.7: where = magicstick`magicstick::ibeacon::{{impl}}::read + 149 at mod.rs:397, address = 0x000056135321b615, resolved, hit count = 0
  2.8: where = magicstick`magicstick::ibeacon::{{impl}}::read + 375 at mod.rs:397, address = 0x000056135321b6f7, resolved, hit count = 0
  2.9: where = magicstick`futures::task_impl::{{impl}}::poll_stream<futures::sync::mpsc::UnboundedReceiver<tokio_core::reactor::Message>> + 92 at mod.rs:397, address = 0x000056135326408c, unresolved, hit count = 0  Options: disabled
  2.10: where = magicstick`futures::task_impl::{{impl}}::poll_stream<futures::sync::mpsc::UnboundedReceiver<tokio_core::reactor::Message>> + 110 at mod.rs:397, address = 0x000056135326409e, unresolved, hit count = 0  Options: disabled
  2.11: where = magicstick`tokio_core::reactor::{{impl}}::consume_timeouts + 398 at mod.rs:397, address = 0x000056135328349e, unresolved, hit count = 0  Options: disabled
  2.12: where = magicstick`tokio_core::reactor::{{impl}}::consume_timeouts + 1348 at mod.rs:397, address = 0x0000561353283854, unresolved, hit count = 0  Options: disabled
  2.13: where = magicstick`core::iter::{{impl}}::next<core::slice::Iter<futures::task_impl::UnparkEvent>,futures::task_impl::UnparkEvent> + 23 at mod.rs:410, address = 0x00005613532a9727, unresolved, hit count = 0  Options: disabled

This is done intentionally because LLDB does not normalize paths properly when filtering breakpoint locations.  Note that all locations except 2.6-2.8 are disabled.
Does this cause any problems (other than bloating the output of break list)?

Thanks for the respsonse - one case where it doesn't work - when placing a breakpoint in the standard library - they are all disabled:
this is useful, as i want to break on when a specific error from the library happens.
For example:
breakpoint in "/home/yuval/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/libstd/io/mod.rs"
Current breakpoints:
1: file = 'mod.rs', line = 628, exact_match = 0, locations = 3
  1.1: where = magicstick`std::io::Read::read_exact<std::io::cursor::Cursor<&[u8]>> + 715 at mod.rs:628, address = 0x000055cfba0d083b, unresolved, hit count = 0  Options: disabled
  1.2: where = magicstick`futures::sync::mpsc::{{impl}}::close<i32> + 136 at mod.rs:629, address = 0x000055cfba13b778, unresolved, hit count = 0  Options: disabled

If you want to set breakpoints or step through std lib source, you'll need to set up source path remapping.

Yes, I know :) i did that.
The breakpoint from the prev comment was set while
            "sourceMap": {
                "/buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/": "/home/yuval/.multirust/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/"
            },

in the debug config in launch.json

Can you please post the output of break list -v?

output:/buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src
Current breakpoints:
2: file = 'mod.rs', line = 628, exact_match = 0
    2.1:
      module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
      compile unit = main.rs
      function = std::io::Read::read_exact<std::io::cursor::Cursor<&[u8]>>
      location = /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libstd/io/mod.rs:628
      address = 0x000055ad67622b2b
      resolved = false
      hit count = 0

        Breakpoint Options:
          disabled
        2.2:
          module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
          compile unit = ckh.c
          location = /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/liballoc_jemalloc/../jemalloc/src/ckh.c:102
          address = 0x000055ad67605474
          resolved = false
          hit count = 0

            Breakpoint Options:
              disabled
            2.3:
              module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
              compile unit = tokio_signal
              function = futures::sync::mpsc::{{impl}}::close<i32>
              location = /home/yuval/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-0.1.11/src/sync/mpsc/mod.rs:629
              address = 0x000055ad676a53d8
              resolved = false
              hit count = 0

                Breakpoint Options:
                  disabled
                2.4:
                  module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
                  compile unit = ckh.c
                  location = /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/obj/build/x86_64-unknown-linux-gnu/stage1-std/x86_64-unknown-linux-gnu/release/build/alloc_jemalloc-d621cf5c5864570d/out/include/jemalloc/internal/jemalloc_internal.h:691                  address = 0x000055ad676052c4
                  resolved = false
                  hit count = 0

                    Breakpoint Options:
                      disabled
                    2.5:
                      module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
                      compile unit = ckh.c
                      location = /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/liballoc_jemalloc/../jemalloc/include/jemalloc/internal/tcache.h:416
                      address = 0x000055ad6760582c
                      resolved = false
                      hit count = 0

                        Breakpoint Options:
                          disabled
                        2.6:
                          module = /home/yuval/Projects/burningman/software/magicstick/target/debug/magicstick
                          compile unit = core
                          function = core::fmt::float_to_decimal_common<f32>
                          location = /buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/libcore/num/flt2dec/mod.rs:628
                          address = 0x000055ad6774e3bc
                          resolved = false
                          hit count = 0

                            Breakpoint Options:
                              disabled

and just in case, my launch config (i'm using a local lldb server, as my program need to run as root):
        {
            "type": "lldb",
            "request": "launch",
            "name": "Launch LLDB",
            "program": "${workspaceRoot}/target/debug/magicstick",
            "args": [],
            "cwd": "${workspaceRoot}",
            "sourceMap": {
                "/buildslave/rust-buildbot/slave/stable-dist-rustc-linux/build/src/": "/home/yuval/.multirust/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/src/"
            },
            "initCommands": [
                "platform select remote-linux",
                "platform connect connect://localhost:1223"
            ],
            "sourceLanguages": ["rust"]
        }

You are setting that breakpoint in "/home/yuval/.rustup/...", but your mapping target is "/home/yuval/.multirust/...".
The breakpoint in futures-rs will need a separate mapping, because its source is in cargo source cache directory.

That's true! sorry about that - the source mapping works because of a symlink...
I tested and verified that it is enabled correctly - Thanks!


Update cats-effect, cats-effect-laws to 3.1.1

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 2.5.1 to 3.1.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

github:typelevel/cats-effect/v3_0_0?sha=series/3.x

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, semver-major, scalafix-migrations

Superseded by #93.


No work after 0.6.0

Hi,
I can not make the plugin work from the version 0.6.0. From version 0.7.0 is undefined window.plugins.permissions
thank

We changed it to var permissions = cordova.plugins.permissions; since 0.7.0.

Thanks!


DoH - cloudflare - failures

I have noticed that sometimes using cloudflare DoH it fails with error:
[INFO] Server [cloudflare] returned temporary error code [2] -- Upstream server may be experiencing connectivity issues
e.g.
dig 78977.duckdns.org

; <<>> DiG 9.10.3-P4-Raspbian <<>> 78977.duckdns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: **SERVFAIL**, id: 8301
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1536
;; QUESTION SECTION:
;78977.duckdns.org.             IN      A

;; Query time: 544 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Wed May 02 12:20:09 BST 2018
;; MSG SIZE  rcvd: 46

however when I run curl directly to <IP_ADDRESS> it works:
curl 'https://<IP_ADDRESS>/dns-query?ct=application/dns-json&name=78977.duckdns.org'
{"Status": 0,"TC": false,"RD": true, "RA": true, "AD": false,"CD": false,"Question":[{"name": "78977.duckdns.org.", "type": 1}],"Answer":[{"name": "78977.duckdns.org.", "type": 1,
"TTL": 60, "data": "<IP_ADDRESS>"}]}

It does not happen all the time but behaviour is always the same dig fails when curl had no issues.
What is even more strange is that as soon as I run dig 78977.duckdns.org @<IP_ADDRESS> it fixes DoH issues - for some time.

Yes, they do rate limiting, or rather limit the number of inflight queries per client.
dnscrypt-proxy just sends what it received. The SERVFAIL error is what Cloudflare sent. But this is a temporary error, your clients are going to retry no matter what.


Interactive preact create command

Tagging this issue as discussion so I can get opinion on having an interactive preact create for initializing the project using preact-cli.
If we want to use interactive preact create i.e. preact init there will not be any flags. Which in my opinion is awesome. 😄
All the flags in the current preact create command will be prompted as questions to the user.

I really like this idea!
Sent from my Bq Aquaris M5 using FastHub

Please still keep --default flag, like npm init -y

Sure, default flag is a must :D


Remote testing

This PR adds remote test capabilities. There are a few components:

test output/log capture, which happens in conftest.py
save/uploads to a testing server, also in conftest.py if requested
a "ci-runner" (for lack of a better name), which, using testing.conf can clone the git repo, run tests on some branches, and upload the results to said testing server

There is a corresponding server in the psi-j-testing-server repo. It is currently deployed on GCE at testing.exaworks.org, which, incidentally, can also be used to visualize test results.

Test result: installing in a VE is straight forward.  The result seems to get pushed, there is a new entry in the table (rivendell, my local machine).  Some tests failed actually (No such launcher: "mpi"), but the entry is grey (I would have expected red?).  Not sure how to interpret that.
When the runner starts, I see this message
$ python3 tests/ci_runner.py
Reading configuration... OK
Cloning repository... Cloning into 'code'...
remote: Enumerating objects: 1383, done.
remote: Counting objects: 100% (1383/1383), done.
remote: Compressing objects: 100% (701/701), done.
remote: Total 1383 (delta 764), reused 1132 (delta 577), pack-reused 0
Receiving objects: 100% (1383/1383), 225.39 KiB | 1.39 MiB/s, done.
Resolving deltas: 100% (764/764), done.
OK
Branch 'cobalt-executor' set up to track remote branch 'cobalt-executor' from 'origin'.
Switched to a new branch 'cobalt-executor'
Testing branch "cobalt-executor"... running launcher_scripts
ERROR: usage: __main__.py [options] [file_or_dir] [file_or_dir] [...]
__main__.py: error: unrecognized arguments: --upload-results --run-id --id "rivendell" --branch-name-override cobalt-executor --maintainer-email<EMAIL_ADDRESS>--server-url https://testing.exaworks.org --key "rivendell" --max-age 48
  inifile: None
  rootdir: /tmp/tmphgvajnlp/code

OK
Branch 'testing' set up to track remote branch 'testing' from 'origin'.

I interrupted the run a couple of time as I thought with was an error (it is UPPERCASED after all! ;-) ), but it turned out to be non-fatal.  Probably should be filtered out?

but the entry is grey (I would have expected red?). Not sure how to interpret that.

You live in the future, so your tests haven't happened yet!
It might be because the server or interface use local time to build the table. I will need to make sure that all times are in UTC.

You live in the future, so your tests haven't happened yet!

Indeed, my clone agrees! :-D
FWIW, deploying in conda worked just as well, it resulted in the same output.

FWIW, deploying in conda worked just as well, it resulted in the same output.

Interesting, but is it maybe because the dependencies were already installed?
If it's not too much work, can you wipe pystache from the system and try to install it under conda with pip?

Interesting, but is it maybe because the dependencies were already installed?
If it's not too much work, can you wipe pystache from the system and try to install it under conda with pip?

You are right, that failed in a new env.  This fixes it:
pip install "setuptools<58"

Ultimately that needs fixing in pystache I'm afraid...

Ultimately that needs fixing in pystache I'm afraid...

We should figure out why pip installs it from source rather than the wheel, since it might provide us with the easiest solution.

Ultimately that needs fixing in pystache I'm afraid...

We should figure out why pip installs it from source rather than the wheel, since it might provide us with the easiest solution.

More on this. The wheel for pystache 0.5.4 was removed from pypi and, unless you have a cached one locally or if you run with --no-cache, pip will use the source package which fails as described above.
There is a promising fork of pystache whose maintainer is attempting to take over the pypi package (see https://github.com/pypa/pypi-support/issues/1422). We could point to that github repo until the issue gets sorted.
There is also a newer implementation of mustache, https://github.com/noahmorrison/chevron, but it seems less used/tested. However, if the situation above does not resolve in a timely manner, this may end up being the better solution.

I figured I would move the pystache discussion to #68 since I don't think we should try to resolve it in this PR.

Do you think you could rebase with main so we can check whether flake8 passes?

Merging after agreement in the weekly meeting.


Feature request: fixedWeekCount option

Hi,
Thank you for great package.
Is it possible to add "fixedWeekCount" option like in full calendar?
When it is enabled it is supposed to always show 6 rows.

Thanks for your interest.
If you create a pull request for that feature, I'm happy to merge it.


Scaling bitmaps as they are loaded

Can Android-Universal-Image-Loader load bitmaps into memory scaled down, like this: http://developer.android.com/training/displaying-bitmaps/load-bitmap.html ?
Thanks!
I'm loading images like this:
final ImageSize size = new ImageSize(MAX_W, MAX_H);
final DisplayImageOptions options = new DisplayImageOptions.Builder()
    .imageScaleType(ImageScaleType.IN_SAMPLE_POWER_OF_2)
    .build();

ImageLoader.getInstance().loadImage(uri.toString(), size, options, new ImageLoadingListener() {

And I have two issues:

The resulting bitmap often has a height or width greater than the max I specified.
I worry it loaded the entire bitmap into memory and just scaled it down, which will fail with large images in low memory scenarios.

Use ImageScaleType.EXACTLY


License Term

Could you please let me know the exact licensing term for the codebase? Is it MIT or Apache2.0 License or something else? @wgcban Thanks!

@zaidbhat1234 updated.


Upgrade to rand 0.5 and switch to unseeded rand::XorShiftRng for random Katakana

When rand 0.5 reaches a stable release, upgrade appropriately. Also, use rand::XorShiftRng for the random Katakana feature (we prefer fast PRNG over crypto-grade).

Done in the release of 0.2.0 (b75edfcb01cdad451b2f10ad81a52a7fa3be9b27) which uses the SmallRng wrapper for XorShiftRng.


build: use the kernel8.img if page size is not 4k

fixes: https://github.com/raspiblitz/raspiblitz/issues/4346

Now the kernel is set correctly:
    arm.raspiblitz-arm64-rpi: *** PREPARE RASPBERRY OS VARIANTS ***
    arm.raspiblitz-arm64-rpi: Reading package lists...
    arm.raspiblitz-arm64-rpi: Building dependency tree...
    arm.raspiblitz-arm64-rpi: Reading state information...
    arm.raspiblitz-arm64-rpi: raspi-config is already the newest version (20231216).
    arm.raspiblitz-arm64-rpi: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
==> arm.raspiblitz-arm64-rpi: /usr/bin/raspi-config: 3078: do_memory_split: not found
==> arm.raspiblitz-arm64-rpi: /usr/bin/raspi-config: 3078: do_boot_wait: not found
    arm.raspiblitz-arm64-rpi: # Adding Raspiblitz Edits to /boot/config.txt
    arm.raspiblitz-arm64-rpi:
    arm.raspiblitz-arm64-rpi: # Raspiblitz
    arm.raspiblitz-arm64-rpi: kernel=kernel8.img
    arm.raspiblitz-arm64-rpi: max_usb_current=1
    arm.raspiblitz-arm64-rpi: dtparam=nvme
    arm.raspiblitz-arm64-rpi: dtoverlay=pi3-disable-bt
    arm.raspiblitz-arm64-rpi: dtoverlay=disable-bt
    arm.raspiblitz-arm64-rpi: * skipping tweak_boot_drive
    arm.raspiblitz-arm64-rpi: fsck.mode=force added to /boot/cmdline.txt
    arm.raspiblitz-arm64-rpi: fsck.repair=yes already in /boot/cmdline.txt
    arm.raspiblitz-arm64-rpi: [Login]
    arm.raspiblitz-arm64-rpi: HandlePowerKey=ignore
    arm.raspiblitz-arm64-rpi: nobody ALL=(ALL) NOPASSWD: /home/admin/config.scripts/blitz.shutdown.sh
    arm.raspiblitz-arm64-rpi: KEY_POWER    1    sudo /home/admin/config.scripts/blitz.shutdown.sh
    arm.raspiblitz-arm64-rpi:
    ```

    will remove the not found raspi-config comands too

The Debian11 RaspberryOS used previously only has the kernel8.img so keep using that shouldn't  make a difference for the RPi4.
Regardless I am flashing this to my RPi4 test node.

Works well on the RPi4 as well so merging as using the kernel8.img is actually the more conservative option.


Correction for raw affiliation Cerema - EL, Les Ponts-de-Cé, France

Correction needed for raw affiliation Cerema - EL, Les Ponts-de-Cé, France
raw_affiliation_name: Cerema - EL, Les Ponts-de-Cé, France
new_rors: 05k0nvr25
previous_rors: 05k0nvr25;02nwvxz07
works_examples: W4401152455
contact: 1eb5682db13b6a348a1809e53c6908f6:b13f518b7b1af62461520e5c6a3e5e @ recherche.gouv.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


index protected data consumed event

Added indexing for the consumption of protected data
Corrected a bug where the state of a protectedData would be still for sale (isForsale) after being sold

subgraph.template.yaml line 75, still a DealId mentioned, should we replace it by Consumption?


processReceipt invokation in "Recognize multiple files at once" sampl…

…e code

This looks good.