Why not add Packet Body Length field to EAPOL frame?

I am learning IEEE 802.1X protocol with gopacket. Currently, there are only three fields in EAPOL interface.
I know that when no further information is needed and the packet body length is set to 0 (and the body is omitted). However, if there is a packet body, such as an EAP message, its length and data are added on as appropriate.

So why there is no Length field in EAPOL type?  since sometimes it decodes EAPOL packet with errors

example:

packet (Get from wireshark)

----
# Packet 0 from /tmp/wireshark_eth0_20161108163321_MDBpM6.pcapng
- 154
- 6.941372676
- Hangzhou_91:eb:ec
- Nearest
- EAP
- 64
- Request, Identity

0000   01 80 c2 00 00 03 50 da 00 91 eb ec 88 8e 01 00  ......P.........
0010   00 05 01 01 00 05 01 00 00 00 00 00 00 00 00 00  ................
0020   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
0030   00 00 00 00 00 00 00 00 00 00 00 00 29 70 35 65  ............)p5e

Code:

import (
	"fmt"
	"log"
	"time"

	"github.com/google/gopacket"
	"github.com/google/gopacket/layers"
	"github.com/google/gopacket/pcap"
)

var (
	device      string = "eth0"
	snapshotLen int32  = 1024
	promiscuous bool   = false
	err         error
	timeout     time.Duration = -1 * time.Second
	handle      *pcap.Handle
)

func main() {
	// Open device
	handle, err = pcap.OpenLive(device, snapshotLen, promiscuous, timeout)
	var filter string = "ether proto 0x888e || udp port 61440"
	err = handle.SetBPFFilter(filter)
	if err != nil {
		log.Fatal(err)
	}
	defer handle.Close()

	packetSource := gopacket.NewPacketSource(handle, handle.LinkType())
	for packet := range packetSource.Packets() {
		printPacketInfo(packet)
	}
}

func printPacketInfo(packet gopacket.Packet) {
	eapolP := gopacket.NewPacket(packet.Data(), layers.LayerTypeEthernet, gopacket.Default)
	fmt.Println(eapolP)
}

Running log

PACKET: 64 bytes
- Layer 1 (14 bytes) = Ethernet {Contents=[..14..] Payload=[..50..] SrcMAC=50:da:00:91:eb:ec DstMAC=01:80:c2:00:00:03 EthernetType=EAPOL Length=0}
- Layer 2 (02 bytes) = EAPOL    {Contents=[1, 0] Payload=[..48..] Version=1 Type=EAP}
- Layer 3 (48 bytes) = DecodeFailure    Packet decoding error: runtime error: slice bounds out of range

PACKET: 64 bytes
- Layer 1 (14 bytes) = Ethernet {Contents=[..14..] Payload=[..50..] SrcMAC=50:da:00:91:eb:ec DstMAC=01:80:c2:00:00:03 EthernetType=EAPOL Length=0}
- Layer 2 (02 bytes) = EAPOL    {Contents=[1, 0] Payload=[..48..] Version=1 Type=EAP}
- Layer 3 (48 bytes) = DecodeFailure    Packet decoding error: runtime error: slice bounds out of range

But it supposed to be like this (with following modified codeseapol.go):
- Layer 1 (14 bytes) = Ethernet	{Contents=[..14..] Payload=[..50..] SrcMAC=50:da:00:91:eb:ec DstMAC=01:80:c2:00:00:03 EthernetType=EAPOL Length=0}
- Layer 2 (04 bytes) = EAPOL	{Contents=[1, 0, 0, 5] Payload=[..46..] Version=1 Type=EAP Length=5}
- Layer 3 (05 bytes) = EAP	{Contents=[..5..] Payload=[..41..] Code=1 Id=1 Length=5 Type=1 TypeData=[..41..]}

By the way, why there is not SerializeTo method associated with EAPOL type?
Provided with the customized code I have been tested:

layers/eapol.go
// Copyright 2012 Google, Inc. All rights reserved.
//
// Use of this source code is governed by a BSD-style license
// that can be found in the LICENSE file in the root of the source
// tree.

package layers

import (
	"encoding/binary"

	"github.com/google/gopacket"
)

// EAPOL defines an EAP over LAN (802.1x) layer.
type EAPOL struct {
	BaseLayer
	Version uint8
	Type    EAPOLType
	Length  uint16
}

// LayerType returns LayerTypeEAPOL.
func (e *EAPOL) LayerType() gopacket.LayerType { return LayerTypeEAPOL }

// DecodeFromBytes decodes the given bytes into this layer.
func (e *EAPOL) DecodeFromBytes(data []byte, df gopacket.DecodeFeedback) error {
	e.Version = data[0]
	e.Type = EAPOLType(data[1])
	e.Length = binary.BigEndian.Uint16(data[2:4])
	e.BaseLayer = BaseLayer{data[:4], data[4:]}
	return nil
}

// SerializeTo writes the serialized form of this layer into the
// SerializationBuffer, implementing gopacket.SerializableLayer.
// See the docs for gopacket.SerializableLayer for more info.
func (e *EAPOL) SerializeTo(b gopacket.SerializeBuffer, opts gopacket.SerializeOptions) error {
	bytes, _ := b.PrependBytes(4)
	bytes[0] = e.Version
	bytes[1] = byte(e.Type)
	binary.BigEndian.PutUint16(bytes[2:], e.Length)
	return nil
}

// CanDecode returns the set of layer types that this DecodingLayer can decode.
func (e *EAPOL) CanDecode() gopacket.LayerClass {
	return LayerTypeEAPOL
}

// NextLayerType returns the layer type contained by this DecodingLayer.
func (e *EAPOL) NextLayerType() gopacket.LayerType {
	return e.Type.LayerType()
}

func decodeEAPOL(data []byte, p gopacket.PacketBuilder) error {
	e := &EAPOL{}
	return decodingLayerDecoder(e, data, p)
}

Thank you in advance.

@gconnell This issue can be closed with the merged PR.

Thanks for the fix!


Is Metafile images like EMF and WMF supported by Skiasharp library?

Is Metafile images like EMF and WMF supported by the Skiasharp library?

Unfortunately not. SkiaSharp really only works with bitmap/raster images such as png/webp/jpg/bmp


[VS Code] [Audio] socket hang up

<!--
Attach verbose logs as follows:
1. Press F1 (or Ctrl-Shift-P), type export

@bjwtufv701 Can you please explain the scenario? Did you hit any error while performing any action?

Closing due to inactivity. Please re-Open if you’re still encountering this issue. Thanks!


OSX build

I have found that Hearth works on OSX just great:

It would be good to have executable for Mac. It might be automated using Travis:
https://docs.travis-ci.com/user/reference/osx/

Thanks for testing on OSX @torinaki !
We can use this template https://github.com/japaric/trust to build for Windows, Linux and OSX and publish artifacts.


Fix yaw out of bounds in mouseEventToCoords

If config.yaw is close to -180 or 180, yaw might be out of bounds.

Sorry, I'm new to GitHub. I don't know why my previous commit has been included as well. It had to be in previous request, and it was actually there. What did I do wrong?

Thanks. I ended up manually applying the patches.


update application to 0.0.143

UpdateBot pushed helm dependency: application to: 0.0.143

UpdateBot commands:
updatebot push-version --kind helm application 0.0.143


Please provide sandbox access

+1 for a nice UI. awesome work
I would really like to see sandbox access for tasks in order to debug certain events.

putting this together here https://github.com/Capgemini/mesos-ui/issues/77


[Image Segmentation Android] Update dependency versions

Thanks @ozbek,
Could you resolve the merge conflicts?

Could you resolve the merge conflicts?
Done, thanks.

Hi,
Do you still want buildToolsVersion restored?

Hi,
Do you still want buildToolsVersion restored?

Yes, it's still better to specify the version instead of using the implicit "minimum required version".

Done, thanks.

Hi! I can't find a way to resolve this one:


osm-bolivia

Community Resource Name
"OpenStreetMap Bolivia"
What is it?
"mailing list"
URL link to the resource
Mailing list: https://lists.openstreetmap.org/pipermail/talk-bo
Points of contact
name: "Marco Antonio", email<EMAIL_ADDRESS>Bounding polygon
relation: https://www.openstreetmap.org/relation/252645
Description (optional)
description: "Talk-bo is the official mailing list for the Bolivian OpenStreetMap community"
extendedDescription: 'Mapping in Bolivia? Have questions, want to connect with the community here? Join us at {Url}. All are welcome!'
Languages spoken (optional)
"es"
Country codes (optional)
"bo"

done in 1739626


Support for the gRPC Docker registry proxy

This PR adds a new gRPC service that makes use of the pre-existing gRPC connection to stream registry image data out of the embedded registry and into the local container frontend (docker pull, etc.).

Associated with: https://github.com/earthly/earthly/pull/3299

I think it looks good -- my only concern is if we find ourselves needing to proxy anything else this is tied to the http protocol. I think it's fine for now -- if (and this is a big if) we need to proxy to a different service, i think it would be good to refactor this to be more generic (e.g. Proxy could take some sort of serviceID).

Interesting point. This service is purpose-built to speak with the embedded registry, but it's certainly possible to register other services on the gRPC connection for other purposes. We could definitely take a look at making this more generic, like you suggested, as the need arises. I may also take a look at streaming the raw HTTP data over a lower-level TCP connection. I figured the HTTP libraries would help with some of the overhead, but that may not be necessary.

On second thought, I think I may leave this as is for the time being. We can always revisit it later if needed.


Exposes gregs from Fuchsia's libc

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @JohnTitor (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

cc/ @tmandry & @leecam

Any reference for that? This is all I could find, the definition is different: https://fuchsia.googlesource.com/fuchsia/+/master/zircon/third_party/ulib/musl/include/bits/x86_64/signal.h#57

I only added a subset of that definition. However, after going further down this path I think I've decided to not upstream this and use native syscalls to get the pc. Thanks for taking a look!


Create a new contributor quickstart page to funnel potential new contributors to

chrisproject.org needs a place for new contributors to learn about how they can get started with the project. Below is an initial wireframe idea of how this could look. Red Hat is going to be putting out some fresh media on ChRIS and would like to direct some traffic towards contributions, so we need a nice, easy-to-use landing page to drive those contributors to.

Updated snapshot so you can see WIP

As we discussed about the join-us page here in the Slack channel, I want to see some motivation parts inside chrisproject.org in the future.
https://fnndsc.slack.com/archives/C04FLFUA6/p1598535121028000
I think our demo site might be included somewhere as one of the steps in the funnel model designed page in the future.
I want to see the page view, unique user for each step and conversion rate between steps are measure if possible.
As you know, the tutorial is a very first part of the web site. It's more important to measure it than other pages.

@junaruga The tutorial isn't the first part, the front page is. But I think instrumenting the pages is a good idea. Can you open up a new issue for this?

(I'm going to close this issue now because the work is complete.)

Yes, right. The front page is a very first part. It's likely that the tutorial is a very second part for the first visitors. Those pages are still in early timing than other pages.

But I think instrumenting the pages is a good idea. Can you open up a new issue for this?

Sure. I will.

Memo: Lisa has been working on this ticket, drafting the copy for the front page.

Lisa - I'm adding you to this ticket to review/edit the text when you're ready.

This page is now live at http://chrisproject.org/join-us


add Event Hubs samples

Adds samples for managing Event Hubs namespaces and hubs, as well as using event hubs to send and receive events.
@devigned can you please review? Also, test of send/receive doesn't work at the moment, will look at main repo for ideas, do you have suggestions?
fixes #159

@joshgav what is the error you are receiving? Doesn't work is kind of abstract.

Good point :). Receive doesn't actually get a message in the test run, wondering if I've chosen the starting offset correctly, and if I need to have it wait.

Receive spins up a listener and continues on. You will have to wait to receive messages. Take a look at
https://github.com/Azure/azure-event-hubs-go/blob/master/hub_test.go#L324-L355. Which provides an example of send and receive with wait.

@joshgav here are the start of stream end of stream consts: https://github.com/Azure/azure-amqp-common-go/blob/master/persist/checkpoint.go#L29-L37
If you don't supply a starting offset, Receive will assume you mean start of stream.

Thanks @devigned! Adjusted to use the constant and tests now pass :)

Hi @devigned and @marstr, this is now complete with Send, Receive, and Receive with EPH examples, all passing tests. Can you please take a look? Would like to merge as soon as possible so we can reference from docs, preferably before EOD 6/29. Thank you in advance!

I addressed all your comments @marstr and made the changes you requested. Can you PTAL again? Thanks!

@marstr I moved context to top scope and fixed up a couple other items, PTAL.
I'm looking into the Travis setup now, the failure isn't cause of this I don't think.


TrainingArguments are now Immutable

We have to change we the way TrainingArguments are modified due to a recent update that made them immutable, as discussed in this thread.
Previously, we could directly modify the TrainingArguments like this:
training_args.logging_steps = len(corpora_encoded["train"]) // batch_size
training_args.output_dir = "xlm-roberta-base-finetuned-panx-all"

However, since TrainingArguments are now immutable(#25435),  we have to use the replace function from the dataclasses module to modify its fields. The replace function creates a new object of the same type as the original, replacing fields with new values specified, as mentioned here
So, the modification of TrainingArguments will now look like this:
training_args = replace(training_args, logging_steps=len(corpora_encoded['train'])//batch_size)
training_args = replace(training_args, output_dir="xlm-roberta-base-finetuned-panx-all")

@lvwerra @lewtun

The book has the transformers version pinned, so I believe that should not be an issue?

Aah, fair point. I probably missed that detail while going through the chapter. I'll close this PR. Thanks for pointing it out. Also   amazing content!


Support TypeScript

nbind should automatically generate TypeScript .d.ts definition files and Closure Compiler externs from the C++ code. This should be done with a simple interface to query internal typing data, and an external NPM package that can read such data and output bindings in either format. This should work regardless of whether the C++ code was compiled using Emscripten or natively to a Node.js plugin. This is scheduled after Emscripten support. The separate tasks are:

[x] Read type information from Node.js module.
[x] Same, but from Emscripten.
[ ] Output TypeScript definitions.

Closure compiler and comment extraction could be supported later:

[ ] Extract doc comments from C++ headers.
[ ] Support passing output through Closure Compiler.
[ ] Output Closure Compiler externs.

Typescript definitions would be a killer feature :+1:

This has finally landed in master. Run the newly included tool ndts after node-gyp (in the same directory) and it prints TypeScript definitions for the C++ module. The output can be directed to a .d.ts file and imported normally, see the test scripts in package.json and test/test.ts for a working example:
import * as foo from './testlib';

const binding = nbind.init<typeof foo>();

More documentation still to be written...


Dropdown with triggers on mobile res doesnt show modal correctly

Overview of the problem
Oruga version: [0.7.0]
Oruga Bulma version: [0.2.11]
Vuejs version: [3.2.13]
OS/Browser: Chrome
Description
Adding ":triggers="['hover', 'focus', 'click']" to the dropdown component options makes it show incorrectly for mobile screens the modal with the options
if you remove the triggers prop it will show correctly
Steps to reproduce

Add/Remove :triggers="['hover', 'focus','click']"

I think this is because the mobileClass is not applied if it is hoverable.
{
    [this.computedClass("mobileClass", "o-drop--mobile")]:
       this.isMobileModal &&
       this.isMatchMedia &&
       !this.hoverable,
},

soruce link
To me, a better solution would be to drop the 'hover' trigger if the client is a mobile agent (not just a small screen) and react the same as the 'click' trigger on a mobile agent.
@jtommy What do you think?


Auto-detect support for stderr

I want use colors only on console.error calls which is typically terminal.
I suggest some API extension, very easy idea is chaining like this:
const coloredOutput = chalk.stderr.red('RED ALERT');

This can be used more easily like this:
const chalk = require('chalk').stderr;
const coloredOutput = chalk.red('RED ALERT');

If I write it correctly, workaround for this is pretty cumbersome now:
const supportsColor = require('supports-color');
const chalk = require('chalk');
chalk.level = supportsColor.stderr.level;
chalk.enabled = chalk.level > 0;

require('chalk').stderr;

I don't mind this, really. I think it's the best solution API-wise, but implementation might look a bit like a hack - we'd want to lazy load which means a property getter.
Thoughts @sindresorhus?

Property getter is really fine, really. I'm fine now with the hackish code above but I cannot recommend altering chalk.level and chalk.enabled globally.
I will be really happy with require('chalk').stderr because it don't need alter global state of chalk

@langpavel you can already create a new Chalk instance.
https://github.com/chalk/chalk#chalklevel
const chalkErr = new chalk.constructor(supportsColor.stderr.level);

looks much better, thanks!

I think we're still deciding. I try to allow @sindresorhus to comment on changes to API decisions before any sort of "help wanted" tag is added.

I just published chalk-stderr with this package and supports-color as peer dependency.

I can recommend something like:
const cherr = require(`chalk/stderr`)

I like that actually. @sindresorhus thoughts?

Yeah, let's go with const chalkStderr = require(chalk/stderr). PR welcome :)

For anyone that wants to tackle this, see the previous attempt and the feedback: https://github.com/chalk/chalk/pull/317


Loading stops

Seems like the loading stops at 98% percent for me in both Firefox, Safari and Chrome. Seems like it work in both IE 7,8 and 9.
I got image tags with a blank src parameter. Could this be the problem?
If so, isn't it suposed to skip images with no path defined?

Thank you for this plugin, and thank you for your time.

Empty src are not supported indeed. This was an issue in the first version too, totally forgot about it. I will create a fallback for this in the next commit. Great find.

Thanks :) Got a donation button where i can throw a few $?

Oh! That solved the problem? I see I accidentally fixed this issue hah. Good to hear :).
Donations can be done through the "Buy me a Pizza" button on my webpage: http://www.gayadesign.com/
Thanks! Much appreciated.

This issue was fixed ?

I created a check to see if the src exists at all. Should be no issue :)

Bug doesn't happen with IE9, only with previous version I don't know why, there is a way to force complete method if the loading are freeze ? ^^

Could do that. I'll think about it. Loading large images might make it look like the loader is stuck too.

If you wan't you can see the bug at voeux2012.uzful.fr :)


Connect to YouTube API and gather data

Added new project. The new project is simply a server that connects to the youtube api. It makes it so that we don't have every single node trying to do authentication with google. Just the one server does it and everyone get data from it.


add new logo

added logo with 16px padding on the top margin. does it look right?

Oh, I forgot to take out the tagline "Clean & green vacant properties to reduce gun violence." After thinking about it a lot I think it's redundant and not necessary. Other than that it looks good. I'll write another ticket with more updates to the header nav, icons, and padding.

closes #185


REFERRER_CHECK_FAIL error verifying JWT token

Release: 1.0.130
I get an error REFERRER_CHECK_FAIL error when verifying the JWT Token.
Contents of apiKeyToken.referrerRestrictions:
0:"staart-demo.o15y.com"
1:"localhost"
2:"oswaldlabs.com"
3:"staart-ui.o15y.now.sh"
It tries to match <IP_ADDRESS> but fails.
What I don't understand is how and where these are set, since I can't find them searching the codebase.

Thanks for opening this issue, @dnordberg! These are part of the API key you're using in the frontend. This will go away if you remove the Axios API key: https://staart.js.org/ui/getting-started (under "Frontend API key")


feat: allow opt out of deleting legacy sdk cookies

Summary

Adds config.cookieUpgrade to retain old SDK cookie and treat as source of truth.
This allows parallel instrumentation of legacy and new SDK
Best practice is to remove config.cookieUpgrade when no longer in parallel instrumentation
[BONUS] Integration tests for @amplitude/analytics-browser now runs faster and in parallel

Migration guide
Step 0: Pre migration
This assumes customer is instrumenting solely using amplitude-js
import amplitude from 'amplitude-js';
amplitude.getInstance().init(...);

Step 1: Parallel instrumentation and partial migration
This assumes customer is instrumenting using both amplitude-js and @amplitude/analytics-browser
import amplitude from 'amplitude-js';
import * as amplitude2 from '@amplitude/analytics-browser';

amplitude.getInstance().init(...);
amplitude2.init(..., {
  cookieUpgrade: false, // retains legacy SDK cookies
});

Step 2: Bye amplitude-js and full migration
This assumes customer is instrumenting soley using @amplitude/analytics-browser
import * as amplitude from '@amplitude/analytics-browser';

amplitude2.init(...);
// options.cookieUpgrade can be explicitly set to `true` or completely omitted
// this effectively deletes legacy SDK cookies and new SDK soley maintain its own cookies

cc @jackmccloy
Checklist

[ ] Does your PR title have the correct title format?
Does your PR have a breaking change?:

For Step 1: Parallel instrumentation and partial migration, think it might still cause minor issue because of the init order. TS SDK will probably not use the legacy cookie in the first time of the page visit (legacy cookie is not ready yet), this might affect the events sent without a page refresh. This might be an edge case though.

@liuyang1520 what im thinking is that the cookies are already stored by step 0, so even if on step 1, amplitude-js has not finished initting, there will be some valid cookies to read. what do you think?

@liuyang1520 what im thinking is that the cookies are already stored by step 0, so even if on step 1, amplitude-js has not finished initting, there will be some valid cookies to read. what do you think?

I think step 0 will make it work for the existing tracked user, the step 1 can read from them, but not for newly tracked user (first time visiting the web app) from step 1. Besides this edge case, the change looks good to me, I am not sure whether we have an easy solution for this though.

@liuyang1520 what im thinking is that the cookies are already stored by step 0, so even if on step 1, amplitude-js has not finished initting, there will be some valid cookies to read. what do you think?

I think step 0 will make it work for the existing tracked user, the step 1 can read from them, but not for newly tracked user (first time visiting the web app) from step 1. Besides this edge case, the change looks good to me, I am not sure whether we have an easy solution for this though.

ahh I see what you mean. we can just update the code sample to await the legacy init
amplitude.getInstance().init(apiKey, userId, config, () => {
  amplitude2.init(..., {
    cookieUpgrade: false, // retains legacy SDK cookies
  });
});

do you think this would solve it?

@liuyang1520 what im thinking is that the cookies are already stored by step 0, so even if on step 1, amplitude-js has not finished initting, there will be some valid cookies to read. what do you think?

I think step 0 will make it work for the existing tracked user, the step 1 can read from them, but not for newly tracked user (first time visiting the web app) from step 1. Besides this edge case, the change looks good to me, I am not sure whether we have an easy solution for this though.

ahh I see what you mean. we can just update the code sample to await the legacy init
amplitude.getInstance().init(apiKey, userId, config, () => {
  amplitude2.init(..., {
    cookieUpgrade: false, // retains legacy SDK cookies
  });
});

do you think this would solve it?

This looks good, think it should work, as long as the JS SDK sets the cookie before the TS SDK init.

@kevinpagtakhan catching up after being away for a long weekend. thanks so much for the fast turnaround on this ❤


V8 produces bogus signature mismatch errors for innocuous changes to the SDK

Point master at the SDK at
https://github.com/proxy-wasm/proxy-wasm-cpp-sdk/tree/v8-signature-bug
and V8 will load the file, passing the signature check but then at runtime will fail the signature check for on_grpc_receive().
Note, the above patch does not effect that function and both the .wat file disassembly and all other signature checks pass.

C++ exception with description "Function: proxy_on_grpc_receive failed: Uncaught RuntimeError: function signature mismatch" thrown in the test body.


Hardware::CPU.type: check uname -m

Determining CPU type by reading /proc/cpuinfo is less reliable than
checking the value of uname -m. Particularly, /proc/cpuinfo often
return the CPU info for the host CPU when running Linuxbrew inside a VM.
Therefore, if the host and VM share different CPU architectures,
/proc/cpuinfo will return incorrect result.
To fix the problem, checking uname -m first, otherwise fallback to
/proc/cpuinfo.
Fixes #336.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #348   +/-   ##
=======================================
  Coverage   70.57%   70.57%
=======================================
  Files         341      341
  Lines       17700    17700
=======================================
  Hits        12492    12492
  Misses       5208     5208

Continue to review full report at Codecov.

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

Thanks again for your contribution to Linuxbrew, Xu!


Illegal instruction error

Details

Project URL: http://readthedocs.org/projects/zhusuan/
Build URL (if applicable):http://readthedocs.org/projects/zhusuan/builds/6845577/
Read the Docs username (if applicable): thjashin

Expected Result
I regularly update the repo and the docs should rebuild.
Actual Result
In recent commits the building failed with the following error log when starting Sphinx:
python /home/docs/checkouts/readthedocs.org/user_builds/zhusuan/envs/latest/bin/sphinx-build -T -E -b readthedocs -d _build/doctrees-readthedocs -D language=en . _build/html
Running Sphinx v1.7.1
Illegal instruction

My local building works well and I've tried Sphinx 1.6.5 and 1.7.1. They both failed with the same error. Do you have an idea what the problem is?

I imported your project in my local instance and I wasn't able to reproduce this issue. We will need more research on this.

Thanks for taking a look. Anything I can help? I've been bothered for a while about this.

I tried to import your project on my local instance, but I got an memory limit error, so I think probably that is the issue. Related to #3613.
@humitos Do you have the default limits for memory and time on your local installation?

@stsewd I modified them using the local_settings.py with these values
DOCKER_LIMITS = {
    'memory': '2048m',
    'time': 3600,
}

@stsewd Can you paste the log here? It's strange that my project takes that much memory.
I set
ulimit -Sv 1000000 #1000m

to run make html. It doesn't seem to fail.

Looking at http://readthedocs.org/projects/zhusuan/builds/6828690/, the return code is 132 which means sphinx-build was interrupted by SIGILL. I don't rule out the OOM case since Python 2 is doing a poor job at handling OOM errors, but this might be caused by an extension module compiled with a flag that is not supported by CPU (or virtual CPU?) in our servers.
We probably need to check versions of all dependencies with extension modules (numpy, tensorflow, matplotlib etc.) in http://readthedocs.org/projects/zhusuan/builds/6828690/ (first failed build) and http://readthedocs.org/projects/zhusuan/builds/6822461/ (last completed build)

@stsewd @berkerpeksag  I just updated the dev branch and found the memory error when downloading tensorflow 1.6.0.

I did some experiments on the dev branch. When I set TF to 1.4.0 in the doc requirements file, everything works well (build page). When I changed it to 1.6.0, the build failed with a MemoryError (build page) or Illegal instruction (build page).
I'm now using <=1.4.0 for a temporal fix. Should I request more memory for my project or wait for a fix?

@thjashin I'm glad that you have your docs working! And not really sure if with more memory your problem would go away, what @berkerpeksag mentions is also very valid (but the builds are executed within a docker container, so maybe a problem with the host?).

Looking at the build logs shared by @thjashin in https://github.com/rtfd/readthedocs.org/issues/3738#issuecomment-371385013, I there are two different problems:

Getting MemoryError when installing tensorflow 1.6.0 (it looks like it randomly fails with MemoryError)
SIGILL after tensorflow 1.6.0 successfully installed (without getting MemoryError)

There are some reports about the second problem in tensorflow's issue tracker: https://github.com/tensorflow/tensorflow/issues/17373 (uses precompiled wheels like us), https://github.com/tensorflow/tensorflow/issues/17411 (same issue) and https://github.com/tensorflow/tensorflow/issues/17441 So I'm beginning to think that the cause of the problem is a buggy wheel distribution.
I don't know what to do with the first problem though. Perhaps we could just increase memory limit (this needs to be discussed with operations team) or implement a retry mechanism (but it's hard to guess whether a MemoryError raised randomly)

@thjashin simple question: do you really need TensorFlow to build your documentation? If it's not a strict requirement for building the docs, the better solution here is to not install it on RTD env. You can avoid installing it by using a docs/requirements.txt specific for RTD with only the packages needed to build your docs :)

@stsewd @berkerpeksag Thanks for the comments and pointers. I guess the SIGILL problem would be solved in future versions of TF. As for the MemoryError, how about the solution proposed by @stsewd ?

@humitos Maybe I'm doing in the wrong way, but since there are plenty of import tensorflow in my source code, is there any way to let sphinx.autodoc generate api docs from doc strings without installing TF?

@thjashin you could try mock TF https://docs.readthedocs.io/en/latest/faq.html#i-get-import-errors-on-libraries-that-depend-on-c-modules

@stsewd Cool, thanks. I shall try this.

is there any way to let sphinx.autodoc generate api docs from doc strings without installing TF?

If you are using autodoc, you need to install it.
Otherwise, supposing that you don't need autodoc, you can mock it as http://docs.readthedocs.io/en/latest/faq.html#i-get-import-errors-on-libraries-that-depend-on-c-modules

@thjashin hey, I see your latest builds are passing, were you able to solve the issue?

@stsewd Thanks for asking. It passed because I'm using TF 1.4. I haven't got time to try the mock solution since I'm busy with other things these days. I will report in this thread once I try it.

Downgrading worked for me too. Thanks for reporting, and sharing work-around!

Thanks for the information everyone! I see the project is building now, so perhaps the immediate error was resolved with these solutions. I would echo using mocking to anyone hitting a similar issue. Closing this for now, but speak up if this error is still a problem for you.


Hide InternalSetup variables in inspector

It makes sense to still have the fields as public, but they should not show up in the inspector. Use [HideInInspector] to do so.

Perhaps we want to drop the **DO NOT CHANGE** -  in both the [Tooltip] as well as the XML docs?


Add ESLint

At the moment, we have Prettier formatting checks and TypeScript checks, but not ESLint checks. Adding ESLint would help us improve JavaScript code quality and maintain consistency across the codebase.
cc @kylebarron @batpad

I'm happy to do this. Do you have any opinions about newer alternatives like oxlint?

This is the first time I'm hearing about oxlint, it looks very interesting. My main concern is whether it has good integration with VSCode. If the development experience is similar to using ESLint, I think we can give it a try.

@kylebarron I looked into oxlint, it seems very bleeding edge. I created an oxlintrc.json file with the no-console and no-unused-vars rules enabled, but the oxc VS Code extension isn't able to pick it up.

That's fine; a PR to add eslint would be great


Bbox F@st5688b seems not working

Hi.
I'm trying to connect to my bBox SagemCom F@st5688B. I'm using HA OS ans HACS module integration.
When I'm trying to connect with the user = admin and (my_password) with MD5 or SHA512 the connection is refused.
I don't known if it shoud be working ?
Thanks for your response

Hey scalmaa,
Without a log, it would be pretty difficult for us to help you, so it would be an advantage if you could provide one.

Where can I find the logs. I'm looking for it but don't find it. Thanks for your help

I found nothing in the HA OS log.

I found this, I could be close to the problem, I don't know
Logger: asyncio
Source: /usr/local/lib/python3.9/asyncio/selector_events.py:911
First occurred: 19:37:29 (1 occurrences)
Last logged: 19:37:29
socket.send() raised exception.

I'm sorry, but I can't really pinpoint the problem with that.
Do you know the basics of python?
If so, you could get a more detailed log with the quickstart script of the sagemcom_api.

A little bit. Do I need to install the sagemcom_api manually ?
I installed the integration by HACS
Thanks

One thing I forgot: Did you...
Enable debug logging
The logger integration lets you define the level of logging activities in Home Assistant. Turning on debug mode will show more information to help us understand your issues.
logger:
  default: critical
  logs:
    custom_components.sagemcom_fast: debug

@scalmaa Did you manage to connect to the bbox ? I try but I can't.

I'm sorry, but I can't really pinpoint the problem with that.
Do you know the basics of python?
If so, you could get a more detailed log with the quickstart script of the sagemcom_api.

I tried the API, and I got a message that sends me "0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://mabbox.bytel.fr')" with HOST = "<IP_ADDRESS>"
I've tried with HOST = "https://mabbox.bytel.fr" and obviously message "Cannot connect to host https:80 ssl:default [getaddrinfo failed]"


Reactive not behaving like an Observable

I'm trying to connect a model parameter (which is therefore of type Reactive) through a function with a bunch of observables, like this:
map!(any, model.disable, bad_firstname, bad_lastname, bad_email, bad_password)

and I'm getting these errors:
ERROR: LoadError: MethodError: no method matching Observables.MapUpdater(::typeof(any), ::Reactive{Bool})
Closest candidates are:
  Observables.MapUpdater(::F, ::Observable{T}) where {F, T} at /home/yakir/.julia/packages/Observables/OFj0u/src/Observables.jl:367
Stacktrace:
 [1] map!(::typeof(any), ::Reactive{Bool}, ::Observable{Bool}, ::Vararg{Observable{Bool}, N} where N; update::Bool)
   @ Observables ~/.julia/packages/Observables/OFj0u/src/Observables.jl:416
 [2] map!(::typeof(any), ::Reactive{Bool}, ::Observable{Bool}, ::Observable{Bool}, ::Observable{Bool}, ::Vararg{Observable{Bool}, N} where N)
   @ Observables ~/.julia/packages/Observables/OFj0u/src/Observables.jl:416
 [3] top-level scope
   @ ~/tmp tests 4 stipple/UserUI.jl:55
 [4] include(fname::String)
   @ Base.MainInclude ./client.jl:444
 [5] top-level scope
   @ REPL[3]:1
in expression starting at /home/yakir/tmp tests 4 stipple/UserUI.jl:55

Is this a known issue due to how Reactive is implemented, or am I doing something wrong here?
MWE
Temp env with just Stipple and Observables
julia> using Stipple, Observables

julia> r = Reactive(true)
WARNING: both HttpCommon and Genie export "Headers"; uses of it in module Html must be qualified
WARNING: both Html and Base export "div"; uses of it in module Stipple must be qualified
WARNING: both Html and Base export "mark"; uses of it in module Stipple must be qualified
WARNING: both Html and Base export "summary"; uses of it in module Stipple must be qualified
WARNING: both Html and Base export "time"; uses of it in module Stipple must be qualified
Reactive{Bool}(Observable{Bool} with 0 listeners. Value:
true, 0, false, false)

julia> o1, o2, o3 = (Observable(false), Observable(true), Observable(false))
(Observable{Bool} with 0 listeners. Value:
false, Observable{Bool} with 0 listeners. Value:
true, Observable{Bool} with 0 listeners. Value:
false)

julia> map!(any, r, o1, o2, o3)
ERROR: MethodError: no method matching Observables.MapUpdater(::typeof(any), ::Reactive{Bool})
Closest candidates are:
  Observables.MapUpdater(::F, ::Observable{T}) where {F, T} at /home/yakir/.julia/packages/Observables/OFj0u/src/Observables.jl:367
Stacktrace:
 [1] #map!#11
   @ ~/.julia/packages/Observables/OFj0u/src/Observables.jl:416 [inlined]
 [2] map!(::typeof(any), ::Reactive{Bool}, ::Observable{Bool}, ::Observable{Bool}, ::Observable{Bool})
   @ Observables ~/.julia/packages/Observables/OFj0u/src/Observables.jl:416
 [3] top-level scope
   @ REPL[6]:1

The quick solution to this is to use map!(any, Observable(r), o1, o2, o3), the longer is to wait for a patch 😉

Of course.. Thanks!
(Feel free to close this when the patch comes out)

It's actually an issue of Observables.jl. If submitted a PR there.

You could also do
import Base.map!
@inline Base.map!(f::F, r::Reactive, os...; update::Bool=true) where F = Base.map!(f::F, getfield(r, :o), os...; update=update)

which might be a workaround from Stipple side.
@essenciary what do you think?

I implemented the change together with another fix for map!() and released a new version.

I leave this open until we know, how the maintainers of Observables will deal with the PR.

@timholy explained in the issue above why our PR was not a good solution.
So we stick with our workaround, which seems to be the correct implementation.
(I had actually forgotten that i fixed this and just reinvented the workaround a second time ...)


Extend for new models

Hi,
Could you provide a guide on how to extend the dictionaries to accommodate new models?
Thank you!

Hi there,
I'm trying to grok this, there's not much in the readme for this and run_main.py doesn't have much in the way of comments to help guide me.
I have a sample of text from an LLM, let's say Mistral and I want to train a new dictionary to accommodate the new model, how would I go about that?


Travis's sudo is not required (faster builds)

Hm looks like the Travis build wasn't run without sudo. Maybe only the owner of the repo can actually test a sudo: change? I'll try on my fork.

I believe that since the build uses Docker, sudo is enabled anyway? See https://docs.travis-ci.com/user/reference/overview/#For-a-particular-.travis.yml-configuration
I have the sudo key there because I thought it was good to be explicit, but I guess it could just be removed.


 LUL
OxidizeBot: User -> Sorry, something went wrong :(

Hey, any chance you can have a peek in the error log? It should say what went wrong.

This is the error:
ERROR oxidize::irc - Error when processing command
ERROR oxidize::irc - caused by: Scope `song/edit-queue` not associated with user Some("User")

After some testing I found out the issue also affects other commands, !command edit gives the proper response but !auth permit or !game edit also send the error.


QUIC: Better SSL_clear()

Undo SSL_clear() changes in test
Break apart SSL_clear() into SSL_clear_quic() and SSL_clear_not_quic()
In SSL_clear(), call both functions
In SSL_accept(), call SSL_clear_not_quic()
Don't make the new functions public.
Fixes #55

Checklist

[ ] documentation is added or updated
[X] tests are added or updated

Not worried about fuzz


Consider public setters for Device / LightBulb

At the moment, these types can't be serialized/deserialized in UWP (no reflection as a workaround). I don't want to have to rely on device discovery upon app startup before issuing commands to cached light bulbs and the Lifxnet API only accepts Lightbulb instances for telling it where to send commands.
An alternative would be to provide API overloads allowing MAC, IP, port params etc and I can just cache that data instead rather than Lightbulb instances.
Thanks ;)

I would suggest you build a model around each bulb that you can serialize. As lights gets re-discovered, you feed the model the Lightbulb instance, and enable it to allow for interaction in the UI. I would heavily recommend against trying to work with bulbs that hasn't actually been announced yet. You can't really rely on parameters staying the same.

I did exactly as you described in the first version of the code. Unfortunately, to respond to Cortana commands, I can't wait for bulbs to announce :(

Fair point. Let me think a little and see if I can't come up with a way the supports both.


_update fix for collections

Description

Fixed an issue where _update was setting the state instead of adding for a collection containing a non-nested type.
Overview of Changes

Parsing collections now takes priority over leaf state parsing (this was the previous behavior back before it was broken)
Type of Change

[ ] Bug fix

Test Details

See DefaultActionExecutorUpdateTest#t12_update_collection_simple()
Additional Notes

It looks like this was introduced back in 1.1.0.M1-SNAPSHOT.

You did it @lopezton-anthem!
Thank you for signing the Anthem Opensource Software CLA.

All test cases are passing with this change.


Fixes unhandled rejection in Skybox.update  #12306

Description
Adds an error handler to loadCubeMap in Skybox.update and then throw any errors during the next call.
This allows the error to be thrown in normal usage when update is called repeatedly.  It prevents throwing the error after the end of a test because update is not called after the test ends.   Previously the error would be thrown in afterAll when the tests were running.
Issue number and link
Fixes  #12306
Testing plan

Checkout this branch
Focus the "handles error when Resources fail to load" spec
Run npm run tests.

Verify the tests pass

Run git checkout main -- packages/engine/Source/Scene/SkyBox.js to get the previous version
Run npm run tests.

Verify the tests fails with an error in afterAll

Author checklist

[x] I have submitted a Contributor License Agreement
[x] I have added my name to CONTRIBUTORS.md
[x] I have updated CHANGES.md with a short summary of my change
[x] I have added or updated unit tests to ensure consistent code coverage
[x] I have updated the inline documentation, and included code examples where relevant
[x] I have performed a self-review of my code

Thanks for the feedback @ggetz .  Updated and ready for another look

Test failure only occurs in release mode.  For some reason scene.mode = SceneMode.SCENE2D when the test was run instead of SCENE3D.  Gave each test its own instance of Scene to prevent cross test contamination.

For some reason scene.mode = SceneMode.SCENE2D when the test was run instead of SCENE3D

The calls with the toThrowDeveloperError expectations are not run in the release tests, so it's likely a side effect of that. The fix here works. :+1:
Thanks @angrycat9000, this all looks good!


Add a spag history command

spag history lists previous requests
spag history show <index> shows a specific request from your history

fixes #29

I like this.


This breaks resources { 'rabbitmq_user': purge => true }

@hashbrowncipher Thank you for your contribution, however I'm going to close this PR due to inactivity. Please feel free to open another PR with your work in it and we will gladly review. Thanks again!


Reexport rand_core

There are issues with conflicting versions of rand_core since x25519 does not use the latest version. It would be helpful if rand_core was exported to avoid conflicts

Although, given that this crate already depends on rand_core, wouldn't there be more useful to have an additional feature flag, say getrandom, that just enables OsRng on rand_core, and then if this flag is set, to provide a wrapper say new_from_os_rng that just uses new(rand_core::OsRng).
The current crate has a great API that makes it hard for misuse, and key generation should fall into this category.

I think a getrandom feature flag that activates rand_core/getrandom is a good idea.
A convenience method for generating a key using OsRng is a good idea as well.


Lexer

Small fix for makefile (also builds minishell.out when running make test)
Added extra assertion in lexer cases
Added failing lexer cases
Rewritten are_quotes_closed to fix failing lexer cases
Added malloc fail checks to program

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

42 of 42 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 56.056%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
1009

Relevant Lines:
1604

💛  - Coveralls


Tag latest not found in repository docker.io/tianon/true

When run
docker-compose up -d  nginx mysql

Pulling applications (tianon/true:latest)...
Pulling repository docker.io/tianon/true
ERROR: Tag latest not found in repository docker.io/tianon/true

It is working for me.
$ docker pull tianon/true
Using default tag: latest
latest: Pulling from tianon/true
3934d4176d73: Pull complete
Digest: sha256:ddd6f0608ed7fba548cced2a27bfdc00864ff95ce94c94820c4c89e5e34446ce
Status: Downloaded newer image for tianon/true:latest

Closing this since I don't think that would be a bug on our side.


How to test custom errors?

Hi all.
We are making use of ErrorTracker.report/3 to store custom errors within the tracker but are struggling to work out how to test this.
Our current thinking is to generate the error and then assert if the error has been stored in the DB with MyApp.Repo.all(ErrorTracker.Error) however this always returns an empty list (Manual testing has proved it works).
Any suggestions welcome. Thanks.

Hello!
There are several options I can think of, depending on your app architecture.
As of now, the ErrorTracker inserts the error on the database using the Repo defined. I have just tried calling Repo.all(ErrorTracker.Error) using our test suite and it works as expected.
However, your experience may be different depending on where are you calling the ErrorTracker from. I'm not completely sure of what happens if you for example insert the error from a GenServer (a separate process), as I don't know if the Ecto sandbox for testing may work there or not.
To be able to reproduce it we would need to know:

from which kind of process are you reporting the error? (a controller, a module called synchronously, a Task, a GenServer...)
do you run sync or async tests?

Another option to test this is using Telemetry, as the library emits events every time an error or occurrence is stored. However, that requires some extra code in your tests to attach to the events (example and example).

We are using a custom backend for Logger to catch the exceptions (and extract them from the metadata). This backend uses @behaviour :gen_event so will be some form on GenServer.
This backend gets triggered for any exceptions or Logger calls. I've tested in a development environment with Logger.error(...) and that works and I can see the error in the DB with MyApp.Repo.all(ErrorTracker.Error), however doing the same thing within the test doesn't work.
The test file is sync and I've confirmed the logger backend is triggered and it executes the report/3 line.
Telemetry sounds like it could work, I'll see if I can get that implemented.
Elixir: 1.17.2-opt-27
ErrorTracker: 0.2.4

That may be the issue.
If the Logger is a separate process, you may need to allow it accessing the SQL Sandbox:
https://hexdocs.pm/ecto_sql/Ecto.Adapters.SQL.Sandbox.html#module-collaborating-processes
another option may be setting the sandbox in shared mode (which is the default in async tests) but I don't know the consequences of doing so in your system.
On the other hand, Telemetry events know nothing about the SQL Sandbox and should work if the ErrorTracker is able to insert the error (which I don't know if it is not allowed to access the sandbox, but I suppose on that case you would see exceptions in the console you are executing the tests).
Please, keep us updated on your findings 👀

So I've tested with the different DB modes (and ultimately couldn't get it to work but here are the results). As part of the debug I viewed the DB before and after running the test. I also tried various different thing in the allow.
With shared: true

With no Sandbox.allow: Run 1 & Run 2: Nothing before or after
With Sandbox.allow(Logger): Run 1 & Run 2: Nothing before or after

With shared: false

With no Sandbox.allow: Run 1 Nothing before or after. Run 2 Error Before & After
With Sandbox.allow(Logger): Run 1 & Run 2: Nothing before or after.

There is clearly something going on with point 3. as its not cleaning the DB between runs.
I have have managed to get it working with telemetry, checking the same fields as the DB check so that works for us.
The project is quite old so there may be something under the hood causing it to bug out with the DB. If I get a chance over the next week I'll try create a fresh project and attempt to re-produce (and let you know outcomes).
Thanks for the help.


[Accessibility] Verified domain in Extension page doesn't have a clear title attribute

Currently, the Verified domain: http://example.com only show as http://example.com, which make it hard for screen readers to understand its meaning.

In contrast, other icons and texts are well-labelled and easy to understand.

It would be nice to give Verified domain a proper accessibility attribute.

Hi, I think I have found a fix for this. However I was wondering if someone could provide some insight into what the best way to validate my fix would be considering the extension marketplace is not available on the test environment. Thanks!

@amaust you can create a PR and I can test it. Or you can install an extension by downloading it and then clicking install via .vsix in the overflow menu of the extensions view

I'll try downloading an extension and trying it that way and if I can't get that to work I'll submit a PR. Thanks!


kube-capacity

An overview of the resource requests, limits, and utilisation in a Kubernetes cluster.
To find out the nodes with the total CPU and Memory resource requests and limits for all the pods running on them.
Find out the  total available resources on the node.

updated estimated time with introduction of dependency versions problem and increased testing scope

reverted time estimation, will create separate tickets with plan for new scope


Added information about manually installing SWATE on Windows

This week I received feedback on the manual installation of SWATE. I have added the information to our install instructions.

Could someone please review this? I promised the person who gave me this feedback that I would add it to our knowledge base


Prevent the user from issuing warnings if there are no valid warning definitions for them to use

(Upgrade process needs some bugfixing I think)

What about the custom warning definition? Was it deleted during upgrade process?

The warning_count variable wasn't set so it couldn't find any warnings.
The design of the category permissions is to explicitly allow denying the custom warning to some groups.

There will always be a warning definition available (warning_definition_id === 0) so this is not a bug right?

That isn't guaranteed, if there are no warning definitions available then they can't issue warnings.
In a proper configuration, there should be at least 1 warning. But it may not be (warning_definition_id === 0).

Done : https://github.com/Xon/XenForo2-WarningImprovements/pull/43/commits/ef79d8483a0dfc28b8f60adfa6b6a10ed8c3b7e9


Validation not compliant when using bnodes?

I tested on the playground with the following shape:
@prefix sh: <http://www.w3.org/ns/shacl#> .
@prefix ex: <http://example.org/> .

ex:ClassShape a sh:NodeShape ;
  sh:targetClass ex:C ;
  sh:property [
    sh:path ex:p ;
    sh:maxCount 1
  ] .

As expected, the following instance has no violation:
@prefix ex: <http://example.org/> .

<tag:b0> a ex:C ; ex:p 0 .
<tag:b1> a ex:C ; ex:p 1 .

However, if I use blank nodes as follows, I get a max count violation:
@prefix ex: <http://example.org/> .

_:b0 a ex:C ; ex:p 0 .
_:b1 a ex:C ; ex:p 1 .

This should make no difference according  to the standard, right?

Yes this looks incorrect. I do believe the SHACL engine itself is correct but there might be an issue with how matching of bnodes is implemented in that rdflib.js version. The query is here
https://github.com/TopQuadrant/shacl-js/blob/master/shared/dash.js#L218
and $this is the focus node (i.e. the blank nodes). I don't know how rdflib treats equality of bnodes during the PathQuery execution. This is of course a requirement for the upper code (in dash.js) to work correctly. Does anyone see something wrong?

Both ways pass validation when using this fork:
https://github.com/zazuko/shacl-js


Fix an email unlink bug

Consider adding a test to catch regressions of this bug. We've had similar bugs in email/password and email/link handling in the past.

Yeah, we don't have a good coverage for email link flow.


[HUDI-5652] Add hudi-cli-bundle docs

Change Logs
Add Hudi cli bundle docs
Impact
medium
Risk level (write none, low medium or high below)
low
Documentation Update
This change is a doc update
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@yihua

@rahil-c : once feedback is addressed, let us know.


Blurry image when used in motion, Exposure time adjustment?

Hello,
recently I've purchased few ArduCAM mini modules OV2640 and OV5642...
The goal is for evaluating the camera module build quality and possibility to be used in a mass production devices with both 2MP and 5MP variants.
So far I am amazed with the products overall quality, PCB board,  soldering, lenses, product packaging software support and documentation - everything is better than all other competitive products.
However, during the tests I've figured out, that camera performs perfect when stationary, and produces
a blurry image, even when moved slowly during footage. This effect is observed both with 2MP i 5MP devices, and with various resolutions. Is there any way for setting exposure time by software?
In the provided libraries all registers are configured via table based values, for each model and resolution.
How can we find detailed description of these values, and which are responsible for fine tune
of colour tint, white balance, scan modes and resolutions, and exposure times as well.
Thank you
Best Regards

@gonzoveliki Customized camera settings like resolution, frame rate, exposure and etc can be supported, please contact<EMAIL_ADDRESS>for detail.

Hello, I've addressed this to<EMAIL_ADDRESS>and so far there is no reply.
Please advice where I can find detailed registers description of the image sensor (via i2c) and
capture FPGA (via spi)...
Regards

Hello Lee,
This is an issue that me as well would like to solve.
Could you please give some more information?
Is it possible to make the adjustments on the cameras we already have or there is not a way to do this?
Also I would like to know if the compression rate is possible to be adjusted.

@Display, Four 5MP camera consume a lot of power when working at the same time, that's why we design low power mode for that, but there will be peak current when start them together.
For adjust compression, please change the register 0x4407 value, 0x04 is good, 0x08 is fair, 0x0C is low quanlity. Please make sure the total size doesn't exceed the total frame buffer.

What about the Exposure time @gonzoveliki  asked about?
Could you give some more informations about that as well?

Hello again!
@gonzoveliki  Did you get an any info for the exposure from @ArduCAM  Lee?
Please provide us with any more info about this...  It would make a great difference in quality to have the exposure time a little bit faster!
Thank you very much!

@gonzoveliki - were setting information shared regarding exposure, etc?

These are handy for figuring out the registers  -- http://www.uctronics.com/download/cam_module/OV2640DS.pdf and http://www.uctronics.com/download/cam_module/1Inch4_5_Megapixel_OV5642_CMOS_Camera_Module_DS_V1.1.pdf

@Displav @gonzoveliki
: I am adding my voice to your call to get this into the API
I can read this http://www.dragonwake.com/download/camera/ov5642/OV5642-DS.pdf until I go blue in the face but I'm sure @ArduCAM could do this in 20 minutes @dis

@aldobranti, It is not very easy to raise the frame rate even if the datasheet says you can. There is limited info about the sensor, we have to build the settings from scratch, and gain a little bit more experience than you though.
You need to pay a lot of time to trial and fail.

Thankyou for explaining @Arducam. I am not the only user who would value this feature. .A.
Sent from my BlackBerry® smartphone
-----Original Message-----
From: Lee<EMAIL_ADDRESS>Date: Wed, 31 Aug 2016 17:40:27
To<EMAIL_ADDRESS>Reply-To: ArduCAM/Arduino<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [ArduCAM/Arduino] Blurry image when used in motion, Exposure time
adjustment? (#42)
@aldobranti, It is not very easy to raise the frame rate even if the datasheet says you can. There is limited info about the sensor, we have to build the settings from scratch, and gain a little bit more experience than you though.
You need to pay a lot of time to trial and fail.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/ArduCAM/Arduino/issues/42#issuecomment-243943766

Hi, I am too evaluating the OV5642 and have the same blurry images with movement. I have the version with 8Mbyte FIFO. My test program is as follows.
I capture multiple images until the fifo is full.
Then I copy the images to SD card.
When I look at the images I see a few blurry images when there is movement.
From my observation since the images are stored directly to the FIFO it seems that this is an issue with the arducamchip and OV5642.
Has anyone managed to get this fixed some how?


Add background dim button

Add a button to allow user to dim background of synctube while watching videos
mockup:

Completed


Feature/update elasticsearch version

! Needs  https://github.com/ucam-cl-dtg/isaac-app/pull/984 !
The main change enforced by this version update is that ElasticSearch indices can now only have a single type for each index.
We have addressed this by creating underscore separated "typed indices".
If the index would have previously been created as 123gitcommithash321 with type contentError,
the new index will be 123gitcommithash321_content_error, still with type contentError.

Pull Request Check List

[ ] Unit Tests & Regression Tests Added (Optional)
[ ] Removed Unnecessary Logs/System.Outs/Comments/TODOs
[ ] Added enough Logging to monitor expected behaviour change
[ ] Security - Injection - everything run by an interpreter (SQL, OS...) is either validated or escaped
[ ] Security - Data Exposure - PII is not stored or sent unencrypted
[ ] Updated Release Procedure & Documentation (& Considered Implications to Previous Versions)
[ ] Peer-Reviewed

Updated version on other pull request


trigger sentry when legacy is used

@kulla maybe cf worker is the best place for this?
This way we can keep track of all routes that might still be relied upon.

When #317 is deployed we already now all paths which go to frontend. These are the ones in https://github.com/serlo/cloudflare-worker/blob/279-change-frontend-proxy-default/src/frontend-proxy.ts#L165-L184 -> So which other things shall be tracked?

Basically I want to see every time legacy is accessed (even with "disable-frontend"). Just for peace of mind :)


Automate removing documents from algolia

Right now we need to delete documents manually from Algolia. We should have a function doing it automatically.

Is this captured by #1138?

duplicate


ToDo before 1.0.0 release

I've started preparing a checklist of what needs to be done before the 1.0.0 release so that we don't forget about anything. Feel free to add. I've assigned some of the jobs, feel free to change/edit.

update docs submodule with the most recent link and check that RTD build works - @jmrohwer
manually build a PDF of the user guide and upload to source - @jmrohwer
check building of wheels and anaconda packages by manually triggering workflows (they will not be uploaded to Anaconda.org/PyPI) - @jmrohwer
finalize release notes - @jmrohwer / @bgoli
tag version 1.0.0 and craft GitHub release - @jmrohwer (I don't mind doing this but don't have to)
prepare zenodo release - @bgoli (would appreciate if you do this as you have done it before and sorted things out)
add badges for RTD and the GitHub CI actions to the main README.md - @jmrohwer

All looks good to me

@jmrohwer I've merged in my changes. With respect to tagging, I think when you make a release the repository is automatically tagged with the release version, so you don't need to manually create a release tag.

@bgoli Did you get my comments on your latest merge? A couple of minor issues, let me know if you are happy with that. I have not changed the code (yet) but am happy to do so if you are too busy.
Still had some issues to sort out with the CI build, hopefully all is good now. Anaconda build on Python 3.6 gives version conflicts using the Anaconda compilers on macOS. I guess it has to do with available numpy versions. I dropped 3.6, figured if people are using Anaconda, it is trivial to upgrade to a more recent version. Python 3.7-3.9 seem to build okay.

@bgoli Release version 1.0.0 is out. :grin:
Wheels and source tarball are on PyPI. Anaconda packages are building at the moment.
Go ahead and prepare the zenodo release!

Great 👍 Unfortunately, something went wrong and the release failed to get to Zenodo I may have to do it all manually which will take some time.

Zenodo record created  I'll update the readme and website and CFF file with the final release info.

Great :+1: thanks. Did you figure out why the web hook was not working and is it working now?

It turned out that a single value (the license id string) in the CFF was in an incorrect format and that trashed the whole thing. I will update the CFF and readme files and merge it.


Lack of documentation

Is there any way to chain WHERE in a query?
What does 'logical?' operator and 'between' do?
What is offset property?

Hope it would save someone time. You could chain query results like this:
const res = localDatabaseName.query({             select: [],             where: [                 { property: "time", comparison: "greaterThanOrEqualTo", value: start },                 { property: "time", comparison: "lessThanOrEqualTo", value: end }             ]         });

The new docs are located here I'll try to add more info


events skipped over unlikely sqlite error

I noticed some missing events in my calendars, even after syncing. So I deleted khal.db to let khal regenerate it. This outputs a lot of errors like the following:
Unknown exception happened.
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/khal/khalendar/khalendar.py", line 233, in _update_vevent
    self._dbtool.update(event.raw, href=href, etag=etag)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 251, in update
    self._update_impl(vevent, href, self.calendar)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 329, in _update_impl
    self.sql_ex(recs_sql_s, stuple)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 208, in sql_ex
    self.cursor.execute(statement, stuple)
sqlite3.OperationalError: database or disk is full
warning: Skipping calendar/some-id.ics: database or disk is full
warning: This event will not be available in khal.

The same happens with khal-git:
debug: Updating some-id.ics because<PHONE_NUMBER>733836800.000000000 != None
Unknown exception happened.
Traceback (most recent call last):
  File "/usr/lib/python3.5/site-packages/khal/khalendar/khalendar.py", line 286, in _update_vevent
    update(event.raw, href=href, etag=etag, calendar=calendar)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 259, in update
    self._update_impl(vevent, href, calendar)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 386, in _update_impl
    self.sql_ex(recs_sql_s, stuple)
  File "/usr/lib/python3.5/site-packages/khal/khalendar/backend.py", line 215, in sql_ex
    self.cursor.execute(statement, stuple)
sqlite3.OperationalError: database or disk is full
warning: Skipping calendar/some-id.ics: database or disk is full
warning: This event will not be available in khal.

Considering the error message I've checked that the disk is certainly not full. Also khal.db seems to be not too big either:
240K	.khal/khal.db

Currently I have less events displayed in khal than before.

This sounds interesting... I've never seen something like this before. Can you give us some more info, on your operating system, file system, etc?

Never mind this. Searching for this behaviour of sqlite I found out that it uses temporary files in /var/tmp which is on another partition which was close to be full.


not working?

just added this addon and it looks like the bar is in an endless loop of filling white, depleteing red, filling white, depleteing red, etc.  the behaviour does not change whether i move or stand still or attack.
Did blizzard break your addon?

Installed this morning and seeing this behavior as well. From looking at the guides for this it doesn't seem like it should be doing anything when not in combat, however for me it keeps looping.

Duplicate of #15


Generate controller functions flag can not take multiple arguments

It does. They must be comma separated with no spaces (csv)


Project Completion QA Checklist: 	Single cell RNAseq characterization of cell types produced over time in an in vitro model of human inhibitory interneuron differentiation.

Project UUID: 2043c65a-1cf8-4828-a656-9e247d4e64f1
Project Title: Single-cell RNA-seq analysis throughout a 125-day differentiation protocol that converted H1 human embryonic stem cells to a variety of ventrally-derived cell types.
Project Short Name: Single cell RNAseq characterization of cell types produced over time in an in vitro model of human inhibitory interneuron differentiation.
Submission UUID: 0948a727-228f-4cfc-857e-6243c6aed08d
Environment: Production

[ ] Process QA of bundles
[ ] Metadata tsv validation: Run metadatatsv_validator.py

Process QA found the following issue:

Project is missing collection protocol (Slack conversation). Not sure if this will require re-ingest to add a protocol. Has been added to hca-data-wrangling/issues/349

Also found:

cell_line_WAe001-A is a cell line without files that is not being displayed on the browser samples tab:


libamqpcpp: 4.2.1 -> 4.3.8

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/CopernicaMarketingSoftware/AMQP-CPP/releases.
meta.description for libamqpcpp is: "Library for communicating with a RabbitMQ server"
meta.homepage for libamqpcpp is: "https://github.com/CopernicaMarketingSoftware/AMQP-CPP"
meta.changelog for libamqpcpp is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/5423ab93951ddb7176864ea6677a5d45

du listing: https://gist.github.com/91f654d94d7b35e7d1446c6ba7eafb14

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
libamqpcpp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nwa7c9gpq524cv03jvqm6f99ijcjpwa2-libamqpcpp-4.3.8 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libamqpcpp https://github.com/r-ryantm/nixpkgs/archive/51c69db0aa751225cd9a334092351427f1f2b498.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nwa7c9gpq524cv03jvqm6f99ijcjpwa2-libamqpcpp-4.3.8
ls -la /nix/store/nwa7c9gpq524cv03jvqm6f99ijcjpwa2-libamqpcpp-4.3.8/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package built:

libamqpcpp

Maintainer pings
cc @MikePlayle for testing.

Result of nixpkgs-review pr 103445 run on x86_64-darwin 1

1 package built:

libamqpcpp


Enable more linters and update config

What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Final linter PR for now which should be safe to apply.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

None

/approve
/lgtm

@kwilczynski had to push another commit, PTAL again

/approve
/lgtm


Remove the 461 target

If you use the repo as submodule and try to use travis, it will fail cause the proyect target is .Net Framework 4.6.1 also and travis doesn't support it. Net Standard also target 461 so it is redundant but it crash travis compilations.
With this little change, the proyect can be builded in all platforms.

I've had issues referencing this project as a net standard project -- would travis be happy if net standard was the first target listed?

I am going to try it, when i have results I will post here

The "reason" for targeting net461 along with netstandard2.0 is it improves the developer ergonomics when using this package from a project that is itself both targeting net461 and has not upgraded to the new csproj format. In those cases it avoids the "system reference spam".
This package should absolutely work as a netstandard2.0 only package, if it's not then it's likely the version of System.Net.Http needs to be explicitly set to one that works with net461 (4.3.2 works in my experience).
It's probably also worth mentioning that travis now supports windows.

Ye, I know (actualy travis doesn't support C# over Windows) , but I am using travis without Windows becouse the final enviroment of my proyect is debian, also I build on Windows with AppVeyor, but only for tradition...
The unique reason for tageting net461 is the developer ergonomics?

I'd be interested in knowing why you're not using the nuget package and instead using a submodule? I assume its because you have custom changse?

Re, no, the only reason to use submodule instead the nuget package, is cause when I started my proyect, the nuget package was out of date and the repo was in date.
Now I supose that the package is updated, so I will try using it instead submodule.

@JorTurFer I am going to close this for now as it seems updating the package works. We can revisit this if there are more requests around this in the future. thanks guys


mat-tab-group doesn't fit label in IE when using mat-stretch-tabs

Bug, feature request, or proposal:
Bug
What is the expected behavior?
A mat-tab-group with mat-stretch-tabs active should correctly size each tab to fit the label even when pagination becomes active.
What is the current behavior?
In IE only, the tabs do not become wide enough to fit medium/long labels when the browser window becomes too narrow.
Works correct in Chrome and Firefox.
I did not test any additional browsers.
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-7elo43
https://angular-material2-issue-7elo43.stackblitz.io/
Have a mat-tab-group with mat-stretch-tabs active, give the tabs somewhat long labels and open in Internet Explorer. Shrink the window narrow enough that pagination should become active. Instead, the label runs off the right side of the tab.
What is the use-case or motivation for changing an existing behavior?
The label would look better.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Internet Explorer 11
Is there anything else we should know?
This is the result of the above stackblitz running in IE11:

And here is the result in Chrome:

The cause of this bug is this css rule:
https://github.com/angular/material2/blob/592af48be6393b99bcbf6231a9f104ed8cea5e90/src/lib/tabs/tab-group.scss#L33
Changing:
.mat-tab-group[mat-stretch-tabs] > .mat-tab-header .mat-tab-label {
  flex-basis: 0;
  flex-grow: 1;
}

to:
.mat-tab-group[mat-stretch-tabs] > .mat-tab-header .mat-tab-label {
  flex: auto;
}

fixes the issue for me.
I got this suggestion from here:
https://stackoverflow.com/questions/39192995/flex-container-wont-expand-to-fit-content-in-ie#comment90243713_39193253

Similar in Edge but here the labels overlap.


New Jade plugin to show machine core controllers

Here's a very basic Jade plugin.
It should add the machine controller's name in italics underneath the machine core name when looking at a machine core.
It turns out that just registering a server data provider for the machine core ended up automatically adding the fluid, energy, and storage contents to the Jade panel as well due to the way the providers were already implemented on the machine cores.
So now Jade should give all of the same information for machines and connected machine cores, while still making it very obvious that it's a machine core.

This implements https://github.com/Rearth/Oritech/issues/43

Huh, I had no idea that jade could even be extended like this. Huge thanks.


Design for multi-band support in source-build

I don't know if this is the final home for this doc, but it seems as good a place as any to review it.

Major changes made:

Split --with-packages into two switches, defining "CSB" and "PSB" artifacts.
Fixed up the distro maintainer workflows.

@dotnet/distro-maintainers - please take a look and provide feedback.


Python 3.11 Support

Describe the bug
Not working on Python 3.11
To Reproduce
Steps to reproduce the behavior:

Install Python 3.11
Run Reloadium
It prints

It seems like your platform or Python version are not supported yet.
Windows, Linux, macOS and Python >= 3.7 (3.9 for M1) are currently supported.
Please submit a github issue if you believe Reloadium should be working on your system at
https://github.com/reloadware/reloadium

Expected behavior
Working
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
OS version: 11
Reloadium package version: 0.9.4
PyCharm plugin version: 0.8.8
Editor: PyCharm
Run mode: Run and Debug

Additional context
Add any other context about the problem here.

Blocked by https://github.com/Nuitka/Nuitka/issues/1856

O confirm this on virtual environments too.

Get the same problem with pycharm 2022.3.2 as well as 2022.3
reloadium 0.9.5

Added in reloadium 1.0.1 and PyCharm plugin 1.0.1

This isn't blocked by the linked issue anymore?

@boxed they released a version that supports 3.11 except some speed improvements which is good enough for Reloadium purposes.

Is there any solution for this?

@kusrohit Python 3.11 is supported in the latest version.


Issue #7450 fixed

Issue Reference
#7450

@peeyush-webkul
Not working fone Ipad Air  device

@peeyush-webkul Not working fone Ipad Air device

@peeyush-webkul
This is working fine. please find the screenshot Here


enhancement req: time slots

I was playing around with a channel I have setup and wanted to try time slots.
I see that it seems that once you choose to go down the time slot route, you are locked in to setting up all 24 hours in a day and need to specify what goes where and when.
What I would love to see if possible...
Start with a standard channel with normal shuffling...

add a slot from 7am and duration of 1 hour, play A program
add a slot from 8am and duration of 1 hour, play B program
9am (ish) resume normal programming shuffle play
add a slot from 6pm and duration of 1 hour, play X program
add a slot from 7pm and duration of 1 hour, play Y program
add a slot from 8pm and duration of 1 hour, play Z program
9pm (ish) resume normal programming shuffle play

So essentially, just override some times a day so at certain times, I can say hey, its 'Sesame Street' time or, later, its 'Everybody Loves Raymond' time, and everything inbetween is just random... bad channel example, but I hope you see what I would like to see if possible.
Anyway.........
Thanks
j

I suggest using a channel redirect for this.

I suggest using a channel redirect for this.


Html page title is not updated when using webpack externals configuration

Version
v2.4.3
Reproduction link
https://github.com/ChenZhuoSteve/nuxt-meta-issue.git
Steps to reproduce

set page title
index.vue page

about.vue page

configuration webpack externals

npm run build

npm start

check page title

click link, switch route

What is expected ?
Html title will change
What is actually happening?
Html title will not change

This bug report is available on Nuxt community (#c8730)

@pi0 This happens because VueMeta does not register in external Vue, VueMeta uses once inside vue-renderer/src/spa-meta.js.
https://github.com/nuxt/nuxt.js/blob/a5654876aa203c353c6a34ff856acc4f34bc191f/packages/vue-renderer/src/spa-meta.js#L16-L21
When we use Vue as an external library it doesn't have VueMeta and breaks meta bindings.

@farnabaz
Thanks!
I tried to manually register VueMeta, but still no effect.

2.6.1 version work well.

in production mode, html title is still not updated.😂

Hi @ChenZhuoSteve
Could you confirm the issue is still happening with latest version of Nuxt.js? (v2.8.1)?


fix: LEAP-461: Fix displaying conditions for comments tab monorepo

Hi @Gondragos!
This PR was created in a response to PRs in upstream repos:

https://github.com/HumanSignal/label-studio-frontend/pull/1650

closing this as monorepo was merged to develop branch


Update codecov plugin

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 35.51%. Comparing base (f71b3b7) to head (0fc5e03).
Report is 41 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main     #844       +/-   ##
===========================================
- Coverage   77.58%   35.51%   -42.08%
===========================================
  Files         107      114        +7
  Lines        9277     8030     -1247
===========================================
- Hits         7198     2852     -4346
- Misses       1699     4815     +3116
+ Partials      380      363       -17

Flag
Coverage Δ

integration-test
?

oats-test
35.51% <ø> (?)

unittests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Can not connect to the self-hosted Gotify server

Can not connect to the self-hosted Gotify server.

Node red connects with the gotify-notification

The red bubble means that you are missing a required configuration-node. Is the message receive node working for you? Or only the sende node?

Both, Neither send nor receive working.

My self-hosted Gotify server, working just fine with the https://flows.nodered.org/node/node-red-contrib-gotify

App token and Gotify-server field outline are red.

It is important to have trailing slash in Gotify-Server address.
https://gotify.example.com/  -> works
https://gotify.example.com -> displays error message in node-red's log: "Error: getaddrinfo ENOTFOUND gotify.toomyem.netmessage
at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:71:26)"

It is important to have trailing slash in Gotify-Server address.

I have tried with/without trailing slash with the same result. The app token and the Gotify-server field still outline in red.
I think this is interference with the https://flows.nodered.org/node/node-red-contrib-gotify which is installed in the NodeRed

Just confirmed the  interference with the https://flows.nodered.org/node/node-red-contrib-gotify
Installed the nr-gotify-push on testing Nodered and everything is working


Update libgpgerror-version to 1.50 from 1.47

Upgraded to 1.51 as part of this. Hence, closing this PR.


Contributors

@pfefferle and @snarfed should be listed as contributors. I never contributed to this project, so should not be listed.

That would be my mistake in copy/pasting I think. @snarfed what is your wp.org username?

@miklb "snarfed" https://profiles.wordpress.org/snarfed


⚠ Bofrost.at has degraded performance

In e73f6b2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1196 ms

Resolved: Bofrost.at performance has improved in 909624f after 14 minutes.


New package: tanuki-.tanuki-wcsc33 version <IP_ADDRESS>

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree
2023年11月23日(木) 15:04 azure-pipelines[bot] @.***>:

Azure Pipelines successfully started running 1 pipeline(s).
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/winget-pkgs/pull/127870#issuecomment-1823857382,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFHMOO24HKMXUZJSLU3JNDYF3RN7AVCNFSM6AAAAAA7XH5BMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTHA2TOMZYGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Added IFA to JetBrains index

3 year course System Engineer, Advanced Federal Diploma of Higher Education: https://www.ifa.ch/nc/weiterbildung/studiengaenge/kursdetail/dipl-technikerin-hf-informatik/kurs/show/

@KilnOfTheSecondFlame Pull request merged. Thank you!


Probabilities can be truncated to 0.00000% in stateAsString(true)

Not necessarily an issue - perhaps an enhancement though. Due to the truncation (or maybe rounding - haven't looked behind the scenes) some probabilities (as well as vector values) for viable states end up being output as 0.
Example program:
const QuantumCircuit = require('quantum-circuit');

let qc = new QuantumCircuit();
let qasm = "OPENQASM 2.0;\n" +
           "include \"qelib1.inc\";\n" +
           "qreg r1[1];\n" +
           "rx(0.0000000001) r1;\n";

qc.importQASM(qasm, (error) => {
    qc.run();
    console.log(qc.stateAsString(true));
})

Output:
 1.00000000+0.00000000i|0>	100.00000%
 0.00000000+0.00000000i|1>	  0.00000%

@DanBlackwell thank you for reporting.
Late answer, I know...
Internal state is correct, it is truncated only when printed.
qc.stateAsSimpleArray();

Returns:
[
    { re: 1, im: 0 },
    { re: 0, im: -5e-11 }
]

And:
qc.stateAsArray(true);

Returns:
[
  {
    index: 0,
    indexBinStr: '0',
    amplitude: { re: 1, im: 0 },
    amplitudeStr: ' 1.00000000+0.00000000i',
    magnitude: 1,
    chance: 100,
    chanceStr: '100.00000',
    phase: 0,
    phaseStr: '0.00000'
  },
  {
    index: 1,
    indexBinStr: '1',
    amplitude: { re: 0, im: -5e-11 },
    amplitudeStr: ' 0.00000000+0.00000000i',
    magnitude: 2.5000000000000002e-21,
    chance: 2.5e-19,
    chanceStr: '0.00000',
    phase: -1.5707963267948966,
    phaseStr: '-1.57080'
  }
]

Goal of stateAsString() method is to show state which is easy to read, and 8 decimal places is enough info for quick view. This is suitable only for small circuits anyway, because nobody will read state with e.g. 2^20 entries :). In small circuits, 8-th decimal place doesn't make any difference in measurement outcome.
However, it could be more informative if it prints something like:
 1.00000000+0.00000000i|0>	 100.00000%
>0.00000000+0.00000000i|1>	  >0.00000%

Or do you have better idea?

These look like good solutions to me; if the print formatting is to a fixed number of decimals places, I think the following may be more informative:
 1.00000000+0.00000000i|0>	 100.00000%
+0.00000000+0.00000000i|1>	  <0.00001%

to me >0.0% makes me think 0% < probability <= 100%, while <0.00001% suggests 0% < probability <= 0.00001%. I think that ultimately between the three suggestions it's a matter of personal preference.

Oh yes, that's better solution for probability. Thanks.
But, amplitude...
We have real and imaginary part and adding any mark there will make it more confusing (especially for imaginary part).
Maybe simply to keep amplitude unchanged and mark only probability:
 1.00000000+0.00000000i|0>	 100.00000%
 0.00000000+0.00000000i|1>	  <0.00001%

Hmm, besides going to e-notation I'm not sure there really is a nice solution to this. If it were me, I'd be tempted to add a [TRUNCATED] to the start or end of any line where the value is too small to be printed properly (or log something to stderr or whatever the JS equivalent is).
I think that as long as the documentation notes that this is possible, that's probably good enough imo. Looking at the documentation here, I initially thought that the true parameter was being ignored when getting 0% out; if it had noted that truncation is possible I'd have not filed this issue.


Option to call load_config service without triggering "There are unsaved changes" dialogue?

Calling the load_service service nearly always triggers a "There are unsaved changes" dialogue.

An option (perhaps via an additional field in the service definition) to always discard changes would be nice for our workflow.

I've had a look at the code, and it seems like this shouldn't require too many changes. Looks like a if (!discard_changes) around this prepareToExit() call should do the trick
https://github.com/ros-visualization/rviz/blob/noetic-devel/src/rviz/visualization_frame.cpp#L750
This would mean adding a discard_changes argument to VisualizationFrame::loadDisplayConfigHelper.
I thought about adding a discard_changes field to SendFilePath.srv, but that seems like it should rather be a new service. Perhaps something like LoadConfig.srv
std_msgs/String path # absolute path to file or directory
bool discard_changes # discard changes to RViz config
---
bool success

The main issue is how to implement this sercice. I'm guessing changing the service type of load_config is not an option, since it would be a breaking change?
I could always make a new service like load_config_discard_changes or similarly, but that might pollute the namespace too much?
Let me know if you have any suggestions, and I'll try to make a proper PR.


Add Experimental AdaptiveCardPrompt Sample

Reference: https://github.com/microsoft/botframework-sdk/issues/5396
Per @johnataylor in SDK standup on 6/28, adding this as a sample.
Proposed Changes
Adds a sample for using the un-merged AdaptiveCardPrompt
Testing

Note
The C# Sample doesn't work because it uses:

Prompt<int>.AttemptCountKey, and
PromptValidatorContext

...which are both internal to the Dotnet SDK and can't be directly used in a sample without AdaptiveCardPrompt getting merged. However, the C# sample is included (without having tested), so it's easy to add, if needed.

This is a really good idea!  Thanks @mdrichardson !!!

@mdrichardson What's the plan with this?

@cleemullins That's up to you guys. The AdaptiveCardPrompt solves our most frequently-recurring issue. I brought it up in FTE standup a couple of months ago and was told to make a PR with samples that show how it works, which is what this issue is.
Ideally, the AdaptiveCardPrompt and the samples get merged into the SDK. Otherwise, it might be suited for Community. Again, though, this is the specific issue that we see the most: users wanting a better way to handle input from Adaptive Cards.

@stevengum @cleemullins Now that 4.6 is out, I figure it's a good time to chime in and say that we still see users asking "how do I retrieve the submit values of an adaptive card in a waterfall dialog?" question more than any other. I think we've had 2-3 this week. The AdaptiveCardPrompt solves that.

Closing, as the new one is here: https://github.com/microsoft/BotBuilder-Samples/pull/1986


.mts and .cts copied as is

Environment
mkdist 1.1.2 on Node.js 16.14.2, v18.14.0.
Reproduction

Have .mts and .cts files in your src directory.
Run mkdist -d --ext js

Example project files
// farewells.cts
export function sayGoodbye(name: string) {
  console.log(`Goodbye, ${name}!`)
}

// greetings.ts
export function sayHello(name: string) {
  console.log(`Hello, ${name}!`)
}

// index.mts
import { sayHello } from './greetings.js'
import { sayGoodbye } from './farewells.cjs'

sayHello('World')
sayGoodbye('World')

StackBlitz example: https://stackblitz.com/edit/node-erv3qh?file=package.json&view=editor (use pnpm build:tsc to build with TypeScript and pnpm build:mkdist to build with mkdist, start to run ./dist/index.mjs with Node).
Describe the bug
mkdist ignores .cts and .mts files and copies them as is instead of compiling them to .cjs (+.d.cts) and .mjs (+.d.mts) respectfully.
Additional context
I could've tried to explain the importance of these file extensions on my own but Bing did a nicer job than me 😢

The .mjs and .cjs extensions are used to specify the module type of a JavaScript file in Node.js 16+. The .mjs extension indicates that the file is an ECMAScript module (ESM), which is a standard format for modular JavaScript code. The .cjs extension indicates that the file is a CommonJS module, which is a legacy format that was widely used before ESM was introduced^1.
The .mts and .cts extensions are used to specify the module type of a TypeScript file. TypeScript is a superset of JavaScript that adds static types and other features. The .mts extension indicates that the file is an ESM TypeScript file, which will be emitted as an .mjs file when compiled to JavaScript. The .cts extension indicates that the file is a CommonJS TypeScript file, which will be emitted as a .cjs file when compiled to JavaScript^1.
These extensions help Node.js to determine how to load and execute different types of modules without relying on ambiguous heuristics or configuration options^3. They also help developers to write clear and consistent code across different environments.

While this is a nice explanation, it fails to mention a few other important things:
If your file has a .ts extension, TypeScript always assumes the resulting file will have .js extension. So if any of the files in your project imports the other file that has .ts extension, and you use Node16 (NodeNext) module resolution (which you very much should btw), TypeScript forces you to write import with .js extension, which is incompatible with mkdist, unless you force it in .js extension mode (--ext js), which you cannot do in environments like nuxt-module-builder without patching it (which is exactly what I'm struggling with and what I am doing).
The other important thing is that .ts, .cts, .mts on the declaration files imply the existence of the file with the same basename: that is, index.d.ts says ‘the declaration file is for index.js’, a.d.cts is ‘for a.cjs’, and b.d.mts is ‘for b.mjs’. That becomes super important for libraries that ship with wildcard exports in package.json, as well helps you as developer to avoid writing types condition which may or may not lead to a correct declaration file (without types export condition TypeScript looks for [basename].d.[ts/cts/mts]).
{
  "exports": {
    "./locale-data/*": { "import": "./dist/locale-data/*" }
  }
}

Logs
No response

Hi and thanks for well explaining in issue. Primary support added vis #162. Please feel free to mention if you think something is not following up spec with new handler.


Multi-arch builds are failing

We successfully built amd64, but ppc64le is failing:
 > [1/2] FROM gcr.io/distroless/static:latest:

failed to solve: rpc error: code = Unknown desc = failed to load cache key: no match for platform in manifest sha256:7d687a1d8809b89c60211ff08a9277ffbe76895907aedffac4d2400a4e1a2dc7: not found
+ docker buildx rm multiarchimage-buildertest
make: *** [release-tools/build.make:128: push-multiarch-csi-provisioner] Error 1
ERROR
ERROR: build step 0 "gcr.io/k8s-testimages/gcb-docker-gcloud:v20200421-a2bf5f8" failed: step exited with non-zero status: 2

https://storage.googleapis.com/kubernetes-jenkins/logs/post-external-provisioner-push-images/1312087665054584832/build-log.txt

This may be related to changes made for:
https://github.com/GoogleContainerTools/distroless/issues/583

@msau42 It does seem to be breaking since above change. The latest gcr.io/distroless/static image shows only amd and arm manifest. Pulling this image gives same error on s390x machine as seen in the Prow job.
We would need to extend support for ppc64le+s390x in distroless image.

@namrata-ibm would you be able to help with adding support for those other platforms to the distroless build?

@msau42 Adding support to distroless would need some time to sort Bazel related support first. Will work on that as a long term solution in parallel.
However to get the builds passing again, can we make changes to Dockerfile to use gcr.io/distroless/static:latest-amd64 image as suggested here? I can raise PRs for that.
cc @pohly

Yes, the workaround sounds fine to me. I'm only concerned that we will stop getting updates to the image so we should actively work on adding support for the missing platforms

This workaround is no good - switching the build to amd64 just broke all the pods running on my arm64 nodes.

@stuartpb can you be more specific? Which containers broke (name, image version, etc.) and which binary in them cannot be executed?

These were the images I saw exec format errors from - I believe it was in every container spawned by Rook using any one of them:
k8s.gcr.io/sig-storage/csi-provisioner:v1.6.0
k8s.gcr.io/sig-storage/csi-snapshotter:v2.1.1
k8s.gcr.io/sig-storage/csi-attacher:v2.2.0
k8s.gcr.io/sig-storage/csi-resizer:v0.4.0

We have not officially supported multi arch images for those versions.
Multi arch is supported starting with
provisioner 2.0
attacher 3.0
snapshotter 3.0
resizer 1.0

Maybe it's a coincidence, then, but I'm pretty sure I was using those images successfully for about a week at least before this change hit.

@msau42 https://github.com/GoogleContainerTools/distroless/pull/622

This should be addressed with the latest sidecar releases and head.
/lclose

/close


hyperglot is a GPLv3 dependency

see: https://github.com/felipesanches/gflanguages/pull/4

see: https://github.com/felipesanches/gflanguages/pull/4

This link is broken

here's the new place where that issue lives nowadays :-D
https://github.com/googlefonts/lang/pull/4

@felipesanches this can be closed, no? The dependency has been removed afaik.

No, we still use it in Lib/gftools/scripts/lang.py and Lib/gftools/util/google_fonts.py.


PHP 7.0 isn't supported anymore. Suggest referencing PHP 7.2 instead.

PHP 7.0  isn't even maintained for security releases anymore. It has been completely End-of-Life'd.  ( https://php.net/supported-versions.php ) I'd suggest updating this page to mention a version that is supported ;-)

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

ID: f970943e-c7b4-919c-65ea-6ba20831e74d
Version Independent ID: 90c5dd06-ea6d-7af8-f88c-9d189e9ceef2
Content: Build a custom image and  for Web App for Containers - Azure App Service
Content Source: articles/app-service/containers/tutorial-custom-docker-image.md
Service: app-service
GitHub Login: @msangapu
Microsoft Alias: msangapu

Thanks for the feedback @kenguest! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Hi @kenguest. Thank you for the feedback. I will update it.
Btw, you're also able contribute updates to our article. With so many moving parts in the cloud, sometimes things get missed. See this link if you'd like to contribute: https://docs.microsoft.com/en-us/contribute/#quick-edits-to-existing-documents

Being handled in https://github.com/MicrosoftDocs/azure-docs-pr/pull/80837

PR has been signed-off.
#please-close


Returning ph:// uri on IOS

Hi there, not really sure where to ask this but here it goes.
I am getting a ph:// prefixed uri returned on IOS when a video is selected, however I get the usual file:// prefix when it is selected on Android. This is only happening as of recently switching from the managed to bare workflow.
I am also not getting the .mov extension that is expected for  IOS.
Please let me know,
Thank you, All the best.

Hi there,
I am facing the same issue.
please let me know if there is any workaround or solution to this.
thank you.

You can enable getImageMetadata in the Settings prop to get localUri which has the file:// prefix.