Latest code does not run at all on some Agon HW when PSRAM is enabled.

I have an original Agon Light from the first series.
I updated MOS (and Basic to the very latest versions).
Until mid August I could always compile the latest Agon VDP software using the Arduino IDE under Linux and upload it to my board using the recommended settings, including "PSRAM Enabled". This worked.
When I compile the latest version with "PSRAM Enabled", it compiles without warnings, it uploads to Agon without any issues, but Agon does not start up. No sound or video whatsoever.
I will try to narrow it down to the exact git commit where the problem starts to occur.
When I keep everything the same and just set "PSRAM DIsabled", everything works when I upload the compiled VDP code.
In the past I did run software that absolutely required PSRAM and this worked.
It's absolutely the hardware at fault, not the Arduino setup:

I tried to upload the precompiled binary (posted Sep 28, 2023 by Jeroen Venema), both on Windows and on Linux. In both
cases the upload procedure appears to complete without errors, my board just does not work.
I tried to compile on both IDE 2.2.1 and 1.8.9 under Linux with the correct ESP toolchain v2.0.4 and the correct versions of ESP32Time and vdp-gl. Same result with PSRAM Enabled, runs with PSRAM Disabled. Works with PSRAM Enabled when compiling an older version of the VDP code.

Seems to break on the following commit:
9d9bd7cd6c34497fb23019a3dc39fc0a733f340f
Author: Steve Sims<EMAIL_ADDRESS>Date:   Wed Aug 9 15:24:56 2023 +0100
improve audio memory management

use C++ vectors and smart pointers

But before just condemning the hardware: never rule out an uninitialized variable bug. I guess modern gcc finds most on its own if enough warnings are enabled, but a good static code check can be worth your trouble.

When I enable the serial monitor in the Arduino ToolKit and #define DEBUG 1 in video.ino, I get the following output:
ets Jun  8 2016 00:22:57
rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13864
load:0x40080400,len:3608
entry 0x400805f0
wait_eZ80: Start
wait_eZ80: End
init_audio: we have reserved 32 channels
audio_driver: setWaveform 0
audio_driver: setWaveform 0 done
audio_driver: init 0
free mem: 240424
audio_driver: setWaveform 0
audio_driver: setWaveform 0
audio_driver: setWaveform 0 done
audio_driver: init 2
free mem: 122628
audio_driver: setWaveform 0 done
audio_driver: init 1
free mem: 122628
after change of canvas...
free internal: 166084
free 8bit: 122628
free 32bit: 166084
do_modeChange: canvas(640,480), scale(2.000000,2.133333), mode 1, videoMode 0
audio_driver: play_note 0,100,750,125
audio_driver: play 0,100,750,125
audio_driver: elapsed 126
audio_driver: end

When I run with PSRAM enbaled, output stops at "Wait_eZ80: Start". It's the only thing printed from the VDP firmware, the previous output is from the internal boot loader, which I also get when not enabling DEBUG

Probably the UART RX buffer gets allocated in PSRAM and as PSRAM is not reliable on my device, the wrong bytes get returned from it. Something like this must be it.

I re-flashed MOS with the official latest 1.04RC2 version and now as of a sudden, VDP with PSRAM enabled works again. When I first discovered the problem I did make sure to update MOS to the then latest version. So the original Agon flies again.

yup - for a while there was a version of MOS that didn't wait long enough for the VDP to start up - oops :grin:


There's a ghosting problem when the animation is on the same plan for too long.

Hi the script is awesome but do you know how I can fix the ghosting problem ? thanks

I'm working on trying to solve ghosting issue. It became much less noticeable with additional processing, but for now it seems very hard to get rid of it completely.

Thanks for all the hard work, I try to post all my test with the script on reddit I hope it's will bring more attention to your work
Here some test I made :
https://www.reddit.com/r/StableDiffusion/comments/12hacuk/hes_possible_to_make_beautiful_anime_movie_with/
https://www.reddit.com/r/StableDiffusion/comments/12h7ilw/testing_the_temporal_consistency_of/
https://www.reddit.com/r/StableDiffusion/comments/12gaq06/jenna_ortega_sings_never_gonna_give_you_up/
https://www.reddit.com/r/StableDiffusion/comments/12g1e00/wow_crazy_temporal_consistency_using/

Yeah, I've seen your results and they are incredible.


v2.0.59 and v2.0.60 az --version hangs

Describe the bug
With version 2.0.59 or 2.0.60 installed executing az --version from an admin command prompt just hangs.
To Reproduce
Install Azure CLI
Open cmd admin prompt
Execute az --version
Hangs!
Expected behavior
It shouldn't hang.
Environment summary
Windows MSI installer v 2.0.59 or 2.0.60 downloaded from https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest
Additional context
Add any other context about the problem here.

I was not able to reproduce this on my windows machine- installed using the msi for 2.0.60.
@agray could you try again/give your system info?

Are you running behind a network proxy?  If you disable your network and try running it again, does it still hang?

We had to set the HTTP_PROXY and HTTPS_PROXY environment variables.
Then it worked.
 If you disable your network and
try running it again, does it still hang?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/8762#issuecomment-472149556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHNVg2wyhCoX24tqvK2uuIrt0VsL8rpks5vWAE_gaJpZM4bp0SX
.

Thanks @agray. If you temporarily turn off your network connection and run az --version does it hang or does it say "Unable to determine if your CLI is up-to-date"?

It takes a VERY long time to eventually say that it can't check CLI update
as you said.
On Wed, Mar 13, 2019, 9:04 AM Travis Prescott<EMAIL_ADDRESS>wrote:

[image: Boxbe] https://www.boxbe.com/overview Automatic Cleanup: keep
last 1 emails<EMAIL_ADDRESS>Edit rule
https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3D56NC1yIWmwxwa2dJewycG1yMOwI%252BgU826tgbS9oLAGw%253D%26token%3DFDSnW2kjZzU9l8iPdAyAfR9T7E0lln5CrJ0UTbNb3OK5TqoNMcOTMh%252FZ1eUAtBTpvfJLo%252BkrGXw2rH5RMiClnMtzn2Fs7vLhtKKHGB8PRQWYXO2yO%252B%252Fd9MvUVsqtnfomagRnfT3MusepXiPomlKZAQ%253D%253D&tc_serial=48695421323&tc_rand=2057011939&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_EDIT&utm_content=001
| Delete rule
https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3D56NC1yIWmwxwa2dJewycG1yMOwI%252BgU826tgbS9oLAGw%253D%26token%3DFDSnW2kjZzU9l8iPdAyAfR9T7E0lln5CrJ0UTbNb3OK5TqoNMcOTMh%252FZ1eUAtBTpvfJLo%252BkrGXw2rH5RMiClnMtzn2Fs7vLhtKKHGB8PRQWYXO2yO%252B%252Fd9MvUVsqtnfomagRnfT3MusepXiPomlKZAQ%253D%253D&tc_serial=48695421323&tc_rand=2057011939&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_EDIT&utm_content=001
| Mark important
https://www.boxbe.com/popup?url=https%3A%2F%2Fwww.boxbe.com%2Fcleanup%3Fkey%3D56NC1yIWmwxwa2dJewycG1yMOwI%252BgU826tgbS9oLAGw%253D%26token%3DFDSnW2kjZzU9l8iPdAyAfR9T7E0lln5CrJ0UTbNb3OK5TqoNMcOTMh%252FZ1eUAtBTpvfJLo%252BkrGXw2rH5RMiClnMtzn2Fs7vLhtKKHGB8PRQWYXO2yO%252B%252Fd9MvUVsqtnfomagRnfT3MusepXiPomlKZAQ%253D%253D%26important%3Dtrue%26emlId%3D98268811435&tc_serial=48695421323&tc_rand=2057011939&utm_source=stf&utm_medium=email&utm_campaign=ANNO_CLEANUP_EDIT&utm_content=001
Thanks @agray https://github.com/agray. If you temporarily turn off
your network connection and run az --version does it hang or does it say
"Unable to determine if your CLI is up-to-date"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/8762#issuecomment-472198360,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHNVkODOPa5xpxbLRO3xZsUBHsIRDO6ks5vWCOOgaJpZM4bp0SX
.

Thanks @agray this was a concern I had when putting this check in. I'll see what we can do.


Luxury to Dream Prefix/Kit Bug

Hey common bug here, I just hit 60% Pokedex completion and claimed the Dream rank. I received the one-time rewards but cannot redeem the /kit dream, and my prefix is also still Luxury. I play on Atlas and my ign is CyberEnt

I'll be home Tuesday to fix your rank if it has not been fixed before then. (As I'm onholidsy right now)


Add more surface plot options

This is a quick fix to #134.
I have adopted multiple plot engines to plot the toroidal surface in 3D.
What I have changed:

add options for using Matplotlib and Plotly.
add **kwargs to pass advanced plotting arguments.

Something we can discuss:

I haven't prepared the options plot_normal, plot_derivative for the other two engines. It might be messy, especially when using matplotlib.
I forgot which docstring format we are using. I looked at other parts and try to follow similar conventions.
The default engine is matplotlib, which can be changed to mayavi for backward capabilities.

I have updated the plotting functions for both curves and surfaces, but I have problems testing it on my MacBook #139 . By the way, I didn't found too many examples using surface.go (maybe I missed). For example, in this case, I would like to create a toroidal surface and plot it. I don't find an example showing how to do this.
For a demonstration of plotly, you can check this page. https://zhucaoxiang.github.io/CoilPy/examples/Plot_with_plotly.html

I'm not sure what you are referring to with surface.go. Can you expand?
To create a toroidal surface in simsopt, simply
from simsopt.geo.surfacerzfourier import SurfaceRZFourier
s = SurfaceRZFourier()

This defaults to a torus with major radius 1 and minor radius 0.1.

@florianwechsung Sorry, I was saying geo.Surface. But what you provide should enough for a test (after I installed it on my MacBook).

I think it is now working. Here is a simple example plotting both curves and surfaces using plotly (forgive me that I chose a curve lying inside the surface).

I have add some docstring in the source introducing the arguments. I am happy to add some documentation as long as someone can kindly direct me where I should put.

This looks excellent. Thanks @zhucaoxiang for working on this. I will try to add a basic unit test for plotting today.


[match] Don’t hang when git credentials are not there

This would be hanging when not running in read-only mode, having a public repo, but not having push access

This is great! However, it feels like we are putting this magic sauce in a lot of places. It would be good to think a bit about whether we can centralize knowledge about this flag so that we don't need to remember to use it everywhere 👍


docs: escape curly braces

noticed that some curly braces were causing blank text in the docs. i haven't tested this (apologies), but i assume escaping them should fix

ok, first time didn't work. so i actually looked at the vitepress docs then. now the braces are escaped https://kubb-git-fork-wickynilliams-patch-1-kubb.vercel.app/plugins/swagger-client/#output-1

@all-contributors please add @WickyNilliams for docs

@WickyNilliams Great, thanks for changing this!

@stijnvanhulle no worries! i got quite confused reading the docs trying to work out how to use some options because of the empty text. happy to fix, so the next person doesn't face the same


Type literals handled poorly by IntelliSense

VSCode Version: 1.15.0-insiders
OS Version: Windows 10

Steps to Reproduce:

Open a new file in TypeScript mode. File does not need to be part of a project.
Copy the code from this gist: https://gist.github.com/zackschuster/3172f3d85e04ea2619d86129d9b4ec60
Expected behavior is in comments

I left a comment in https://github.com/Microsoft/vscode/issues/25034 with some of this info, then after finding more problems I decided to post a new issue. I bring this up because issues here may indirectly affect that bug.
Basically, it seems that IntelliSense is given a lot of over-simplified information w/r/t type literals, none of which follows a reliable or even necessarily coherent theory; depending on the context, the same literal may be revealed as its primitive, as its type alias, or as a completely unrelated type alias (!!!) that just happens to share properties.
While none of this appears to have an impact on compile-time correctness, it does make navigating code with IntelliSense more cumbersome than it needs to be while losing an opportunity to use keyof and crew with vscode in really powerful ways.
Reproduces without extensions: Yes

This issue was moved to Microsoft/TypeScript#17310


Trying out BuildKite

Still having trouble with Cassandra. It installs as root but the integration tests are unable to connect to it.

Is anyone able to see the build pipeline? https://buildkite.com/uberopensource/cadence-server

close in favor of #1643


fix(check): analysis uses --artifacts=all

Fixes an issue where the preflight config check would use whichever artifact options the user had passed. If --artifacts=local was passed, we would be inappropriately flagging GitHub CI as out of date because we'd try to omit the global artifacts.

ugh whoops


Google App Engine Support

Hi!
I would really like to use this package for a project using Google App Engine, but I get this error:
go-app-builder: Failed parsing input: parser: bad import "unsafe" in github.com/tidwall/gjson/gjson.go from GOPATH
I was hoping there might be an simple way to replace unsafe.Pointer so that it will work on App Engine?
Thanks a lot!

If these lines were commented out then the "unsafe" import can be removed:

https://github.com/tidwall/gjson/blob/master/gjson.go#L1300-L1307
https://github.com/tidwall/gjson/blob/master/gjson.go#L1310-L1358

Doing so will also remove the gjson.GetBytes function, but the gjson.Get should still work.

Hi @dadatawajue I'm closing this issue for now. Please let me know if there anything else I can help with around this issue.

Hi, I just noticed I forgot to reply earlier; it worked, thanks a lot, really appreciate it <3

@dadatawajue You're welcome. :)


fixed internal link

First content link here: https://keras.io/api/keras_nlp/models/

Take it or leave it, I'm not going to sign anything for adding a single slash. I promise I won't sue if you steal it.


chore: rename topos-network to topos-protocol

Description
Rename to topos-protocol

I need to update some package dependencies related to this change


New Drop Destination Not Being Used

How to reproduce.

Create folder and only set it to "Watch For New Files".
Create a drop source and a drop destination, set each to "Watch For New Files" as well.
Drop some files in drop source.
Once files have been moved into original drop destination change drop destination.
Drop some files in drop source.
Files should go to new drop destination but end up in the first folder we added back in step 1.

Additionally, adding a new drop destination or reusing the original one does not work either. As far as I can tell you're no longer able to select a drop destination.

For an existing series files are moved to the folder where the latest episode is located, regardless of drop source.


GET /sign in loop on Login page

I just completed a fresh install on Digital Ocean.
When i signin using the .htpasswd it takes me to the page to enter my Tesla credentials.
Here the sign-in button doesnt work. The page constantly refreshes.
In the console i see the following:
teslamate_1  | 05:05:51.394 [info] Version: 1.18.2
teslamate_1  | 05:05:51.446 [info] Running TeslaMateWeb.Endpoint with cowboy 2.7.0 at :::4000 (http)
teslamate_1  | 05:05:51.448 [info] Access TeslaMateWeb.Endpoint at http://teslamate.c0mrade.net
mosquitto_1  |<PHONE_NUMBER>: New connection from <IP_ADDRESS> on port 1883.
mosquitto_1  |<PHONE_NUMBER>: New client connected from <IP_ADDRESS> as TESLAMATE_302E3031303 (p2, c1, k60).
teslamate_1  | 05:05:51.460 [info] MQTT connection has been established
teslamate_1  | 05:06:14.099 [info] GET /
teslamate_1  | 05:06:14.114 [info] Sent 302 in 15ms
teslamate_1  | 05:06:14.144 [info] GET /sign_in
teslamate_1  | 05:06:14.155 [info] Sent 200 in 11ms
teslamate_1  | 05:06:17.620 [info] GET /sign_in
teslamate_1  | 05:06:17.624 [info] Sent 200 in 3ms
teslamate_1  | 05:06:21.119 [info] GET /sign_in
teslamate_1  | 05:06:21.124 [info] Sent 200 in 5ms
teslamate_1  | 05:06:22.892 [info] GET /sign_in
teslamate_1  | 05:06:22.895 [info] Sent 200 in 2ms
teslamate_1  | 05:07:56.893 [info] GET /sign_in
teslamate_1  | 05:07:56.897 [info] Sent 200 in 3ms
teslamate_1  | 05:07:56.929 [info] GET /sign_in
teslamate_1  | 05:07:56.932 [info] Sent 200 in 2ms

Which browser are you using and could you please try to sign in with another browser? And are there any additional error messages visible in the browser console?

The above was using the latest Safari.
When I use Chrome 80 - get a ERR_TOO_MANY_RETRIES
I ran Console in Safari on the mainpage and get:
WebSocket connection to 'wss://teslamate.c0mrade.net/live/websocket?_csrf_token=VmF4BSwhJAwVLQMuICgrJyQ-CyQxDjJgfYKHVMBcYdNBZJ_Thn_HTE_8&baseUrl=https%3A%2F%2Fteslamate.c0mrade.net&referrer=https%3A%2F%2Fteslamate.c0mrade.net%2Fsign_in&tz=America%2FLos_Angeles&vsn=2.0.0' failed: Unexpected response code: 401

Thanks. Safari has a long-standing bug (see #415) that makes it impossible to use basic authentication. Chrome should work fine though. Do you run the Advanced Docker Setup with Traefik?

I get the below errors. But I set all these in my .env files which is stored at "/"
root@teslamate:~# docker-compose logs -f proxy
WARNING: The TM_DB_USER variable is not set. Defaulting to a blank string.
WARNING: The TM_DB_PASS variable is not set. Defaulting to a blank string.
WARNING: The TM_DB_NAME variable is not set. Defaulting to a blank string.
WARNING: The FQDN_TM variable is not set. Defaulting to a blank string.
WARNING: The TM_TZ variable is not set. Defaulting to a blank string.
WARNING: The GRAFANA_PW variable is not set. Defaulting to a blank string.
WARNING: The GRAFANA_USER variable is not set. Defaulting to a blank string.
WARNING: The FQDN_GRAFANA variable is not set. Defaulting to a blank string.
WARNING: The LETSENCRYPT_EMAIL variable is not set. Defaulting to a blank string.
Attaching to default_proxy_1

I moved my .env to ~/ (root directory) and that seemed to fix the issue


Write blog post on pagination

What
Write a blog post on pagination that both outlines how pagination works and as a detailed breakdown of how we build a component.
Why
To promote the design system internally and externally. Spun off of https://github.com/alphagov/design-system-team-internal/issues/603
Who needs to work on this
@owenatgov
Who needs to review this
The team, GDS comms
Done when
A final draft of the blog post is released

[x] Draft blog structure
[ ] Initial content draft
[ ] Review from team
[ ] Review from comms/relevant stakeholders
[ ] Decide which GDS blog this goes on
[ ] Publish blog post

Draft being written here https://docs.google.com/document/d/1ImpgBN7cq_BKqfMHBCaKVPMTkiU1nbG5EGNxrdgWh-I/edit#heading=h.uxml3npyh7fm

Closing as the moment's passed 😢


Break out Engine from Scene code

Engine should be separate, and allow for things like loops, asset loading, manifests?, maybe even canvas resizing.
var engine = Engine()
var renderer = engine.renderer
var scene = engine.scene

engine.on('init', function() {
  scene.add( ... )
})

engine.on('update', function() {
  doSomething()
})

+1

This is implemented on the dev branch, although the renderer is still handling the canvas adding and resizing.
https://github.com/glamjs/glam/commits/dev
https://github.com/glamjs/glam/blob/dev/docs/api/engine.md


cmd/compile: function-to-interface conversion leads to miscompilation and segfault

What version of Go are you using (go version)?

$ go version
go version devel go1.18-6e5dd0b59b Mon Sep 27 11:52:07 2021 +0000 windows/amd64

Does this issue reproduce with the latest release?
No
What operating system and processor architecture are you using (go env)?

windows/amd64
linux/amd64 (godbolt)

What did you do?
https://play.golang.org/p/JxrNfegu__C
https://go.godbolt.org/z/1E6Kx3aoT
What did you expect to see?
Successful compilation.
What did you see instead?

   I think this may be a problem with doing CONVIDATA on a function pointer which happens at line 47, when the program converts 'it' from an IteratorFunc[R] to an Iterator[R].  Do you know of any probably there might be with CONVIDATA in this case?

I have a theory. It looks like there are 2 instantiations of Pipe, Pipe[.shape.int_0,.shape.int_1] and Pipe[.shape.int_0,.shape.int_0] each has a different dictionary layout. But the dictionaries when instantiated with int and int generate identically named dictionaries, .dict.Pipe[int,int].
I think the code ends up using the dictionary designed from the 0/1 version, but passes it to the 0/0 version.
Why does the 0/0 version exist at all? I'm not sure about that.
>>> InstInfo for Pipe[.shape.int_0,.shape.int_1]
  Typeparam .shape.int_0
  Typeparam .shape.int_1
  Subdictionary at generic function/method call: FromIterator - (<node FUNCINST>)(IteratorFunc[.shape.int_1](it))
  Itab for interface conv: IteratorFunc[.shape.int_1](it)
  Derived type Stream[.shape.int_0]
  Derived type func(.shape.int_0) (.shape.int_1, bool)
  Derived type Stream[.shape.int_1]
  Derived type func(func(.shape.int_1) bool)
  Derived type Iterator[.shape.int_0]
  Derived type func(.shape.int_1) bool
  Derived type func(.shape.int_0) bool
  Derived type func(Iterator[.shape.int_1]) Stream[.shape.int_1]
  Derived type Iterator[.shape.int_1]
  Derived type IteratorFunc[.shape.int_1]
>>> Done Instinfo

>>> InstInfo for Pipe[.shape.int_0,.shape.int_0]
  Typeparam .shape.int_0
  Typeparam .shape.int_0
  Subdictionary at generic function/method call: FromIterator - (<node FUNCINST>)(IteratorFunc[.shape.int_0](it))
  Itab for interface conv: IteratorFunc[.shape.int_0](it)
  Derived type Stream[.shape.int_0]
  Derived type func(.shape.int_0) (.shape.int_0, bool)
  Derived type func(func(.shape.int_0) bool)
  Derived type Iterator[.shape.int_0]
  Derived type func(.shape.int_0) bool
  Derived type func(Iterator[.shape.int_0]) Stream[.shape.int_0]
  Derived type IteratorFunc[.shape.int_0]
>>> Done Instinfo

Note that 0/1 has 14 entries, whereas 0/0 has 11 entries.
This is the only dictionary for Pipe in the assembly output, having 4 entries (so it's for the 0/1 instantiation):
""..dict.Pipe[int,int] SRODATA dupok size=112
	0x0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	0x0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
	rel 0+0 t=25 type."".Iterator[int]+96
	rel 0+0 t=24 type.int+0
	rel 0+0 t=24 type."".IteratorFunc[int]+0
	rel 0+0 t=24 type.int+0
	rel 0+0 t=25 type."".Iterator[int]+96
	rel 0+0 t=24 type."".Stream[int]+0
	rel 0+0 t=24 type.func("".Iterator[int]) "".Stream[int]+0
	rel 0+0 t=24 type.func(int) (int, bool)+0
	rel 0+0 t=24 type.func(int) bool+0
	rel 0+0 t=24 type."".Stream[int]+0
	rel 0+0 t=24 type.func(int) bool+0
	rel 0+0 t=24 type.func(func(int) bool)+0
	rel 0+8 t=1 type.int+0
	rel 8+8 t=1 type.int+0
	rel 16+8 t=1 type."".Stream[int]+0
	rel 24+8 t=1 type.func(int) (int, bool)+0
	rel 32+8 t=1 type."".Stream[int]+0
	rel 40+8 t=1 type.func(func(int) bool)+0
	rel 48+8 t=1 type."".Iterator[int]+0
	rel 56+8 t=1 type.func(int) bool+0
	rel 64+8 t=1 type.func(int) bool+0
	rel 72+8 t=1 type.func("".Iterator[int]) "".Stream[int]+0
	rel 80+8 t=1 type."".Iterator[int]+0
	rel 88+8 t=1 type."".IteratorFunc[int]+0
	rel 96+8 t=1 ""..dict.FromIterator[int]+0
	rel 104+8 t=1 go.itab."".IteratorFunc[int],"".Iterator[int]+0

But the only call in the binary is to the 0/0 version:
	0x0080 00128 (/Users/khr/gowork/issue48645.go:30)	CALL	"".Pipe[.shape.int_0,.shape.int_0](SB)

Which seems to be using the dictionary appropriate for the 0/1 implementation (reading it out of .dict.Stream[int].DropWhile).

package main

import (
	"fmt"
	"reflect"
)

type Stream[T any] struct {
}

func (s Stream[T]) DropWhile() Stream[T] {
	return Pipe[T, T](s)
}

func Pipe[T, R any](s Stream[T]) Stream[R] {
	it := func(fn func(R) bool) {
	}
	fmt.Println(reflect.TypeOf(it).String())
	return Stream[R]{}
}

func main() {
	s := Stream[int]{}
	s = s.DropWhile()
}

@korzhao Yes, I believe that misbehavior is the same issue. It's trying to load the derived type func(func(.shape.int_0) bool) from the dictionary but instead gets Stream[.shape.int_1] because it is using the wrong dictionary.

OK, thanks @randall77  and @korzhao for point out the behavior with the multiple InstInfo & dictionaries.  I figured out that problem and fixed it with this change: https://go-review.googlesource.com/c/go/+/353030
However, it looks like there is another bug, possibly related to converting a closure with captured variables to an interface using a dictionary.  (so this could next bug could possible be related to OCONVIDATA).  In the CL above, I comment out the closure body so that the test would pass.
If you re-enable the closure body, the you get a seg fault later in the execution in the closure with Reduce/Stream.Iterate/IteratorFunc.Iteration above it.


[Workflow] Add libGoReSym, update image

This PR is for:

Agent

Add libGoReSym, update image
Checklist

[ ] Added unit test.

Backport to branches

main

agent检查也要改一下tag


SNMPv3 Trap Listener

Hello, I've been looking for a nice SNMP lib for awhile and found this. It has a nice feature set, but I am wondering what work needs to be done for v3 trap support. I am interested in helping implement it.

I wrote the V3 Trap Listener(without InformRequest) on trapv3_receiver branch.
Try it if you like.

@k-sone is there a reason that's in a different branch, or has that simply not been merged back yet?

As far as I know, there is a bug in the authentication part.
I'll see if I can fix it this weekend.


Fix for #51, should use locale day of week format

Fix for #51
The format should be the locale day of week, since the operation is done on moment().localeData().
As provided by moment.js documentations:
http://momentjs.com/docs/#/displaying/format/

@jonquach thanks, seems your proposed change is much better than mine here, https://github.com/Baremetrics/calendar/pull/53
Will try your change out in my Fork for the different locales I am working with & then suggest it as the fix

I tried your change @jonquach and was not able to get it to work as expected. I do not get any errors when clicking on the second date in the date range picker, however the dates in the calendar are mapped to the wrong day/s.
For me today's date Wednesday 18th of May shows up under Tuesday


hello

Hello, first of all i want to thank you for the great contribution, it's a great project.
I have only one issue, when i try to run the project i get this error :
Error	1	 error: cannot find symbol
mono.android.Runtime.notifyTimeZoneChanged ();
symbol:   method notifyTimeZoneChanged()
location: class Runtime
C:\Users\Alex\Desktop\NFCForms-master\Example\NFCFormsSample\NFCFormsSample.Droid\obj\Debug\android\src\mono\android\app\Application.java	23	24	NFCFormsSample.Droid
Any idee what is wrong ? I am using VS 2013 SP on the Droid version.
Thank you

Duh, simple fix, i just cleaned solution + rebuild = works


C# code leads to crashing the game (instead of just logging an error)

Tested versions

reproductible in v4.3.stable.mono.official [77dcf97d8]
also observed in v4.2.2
(I did not checked older versions)

System information
Windows 11
Issue description
The code below leads to crashing the game when it starts. Admittedly the code is wrong. But it's still an issue for 2 reasons:

Godot doc says:

We believe games should not crash, no matter what. If an unexpected situation happens, Godot will print an error (which can be traced even to script), but then it will try to recover as gracefully as possible and keep going.

but it's not what occurs.

As a developer of this code (unless I launch Godot from a terminal in order to see its stdout) I have no clue why my game crashes when I launch it, in the sense that nothing is logged (I guess the crash occurs before it could log the error?)

FTR, here is the stacktrace I get when I reproduce this issue with a version of godot 4.3 compiled with debug symbols:
================================================================
CrashHandlerException: Program crashed
Engine version: Godot Engine v4.3.stable.mono.custom_build (77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[0] CSharpInstance::disconnect_event_signals (C:\dev\misc\godot\modules\mono\csharp_script.cpp:1786)
[1] CSharpInstance::~CSharpInstance (C:\dev\misc\godot\modules\mono\csharp_script.cpp:1941)
[2] CSharpInstance::`scalar deleting destructor'
[3] memdelete<ScriptInstance> (C:\dev\misc\godot\core\os\memory.h:116)
[4] Object::set_script_instance (C:\dev\misc\godot\core\object\object.cpp:958)
[5] CSharpScript::_create_instance (C:\dev\misc\godot\modules\mono\csharp_script.cpp:2355)
[6] CSharpScript::instance_create (C:\dev\misc\godot\modules\mono\csharp_script.cpp:2424)
[7] Object::set_script (C:\dev\misc\godot\core\object\object.cpp:941)
[8] Node::set_script (C:\dev\misc\godot\scene\main\node.cpp:3860)
[9] Object::set (C:\dev\misc\godot\core\object\object.cpp:255)
[10] SceneState::instantiate (C:\dev\misc\godot\scene\resources\packed_scene.cpp:350)
[11] PackedScene::instantiate (C:\dev\misc\godot\scene\resources\packed_scene.cpp:2093)
[12] Main::start (C:\dev\misc\godot\main\main.cpp:3894)
[13] widechar_main (C:\dev\misc\godot\platform\windows\godot_windows.cpp:179)
[14] _main (C:\dev\misc\godot\platform\windows\godot_windows.cpp:206)
[15] main (C:\dev\misc\godot\platform\windows\godot_windows.cpp:220)
[16] WinMain (C:\dev\misc\godot\platform\windows\godot_windows.cpp:234)
[17] __scrt_common_main_seh (D:\a\_work\1\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl:288)
[18] <couldn't map PC to fn name>
-- END OF BACKTRACE --
================================================================

Steps to reproduce

Create a project with a single Node2D
Attach a C# script to it with this code

using System;
using Godot;

namespace Godottrain.code;

public partial class Map : Node2D
{
    // This signal is unused, but if we remove this declaration, we cannot reproduce the crash
    [Signal] public delegate void IsClickedEventHandler();

    public Map()
    {
        // Sure, this code is not expected to behave correctly (but putting it in a C# Lazy would fix it).
        // Anyway, it's expected that this line fails and logs an error. But it should not crash the game
        var position = GetNode<Node2D>("ChildThatDoesNotExist").GlobalPosition;
    }
}

Launch that scene

Expected behavior: an error that says that the child does not exist and the game remain opened (though it's just an empty window)
Actual behavior: the game crashes
Minimal reproduction project (MRP)
MRP-godot-crash.zip

This is the code that executes when creating a new C# instance:
https://github.com/godotengine/godot/blob/1bd740d18d714f815486b04bf4c6154ef6c355d9/modules/mono/csharp_script.cpp#L2348-L2358
The ScriptManagerBridge_CreateManagedForGodotObjectScriptInstance function invokes the C# constructor of the type that we're creating. Since your constructor throws an exception, it fails and returns false so it enters the if below to clear the script instance we just created which is invalid.
When destructing C# scripts, we also make sure to disconnect the signals. As the stack trace shows, it's crashing on this line:
https://github.com/godotengine/godot/blob/1bd740d18d714f815486b04bf4c6154ef6c355d9/modules/mono/csharp_script.cpp#L1786
Since we failed to create the C# script instance, the owner is null. But disconnect_event_signals assumes it will never be null. I think this may be as simple as changing the order of clearing the owner to after destroying the script.


Add version of GetUnits to take a set of filters

Is your feature request related to a problem? Please describe.
Currently, only 1 type of Filter can be passed to GetUnits to return a filtered list of units. We then have to do additional manually filtering after the initial call.
Describe the solution you'd like
It would be great to use multiple filters in one call.
alkurbatov: "i.e. assuming that we have IsNonSaturatedTownHall, IsTownHall and IsFinished it would be convenient to use e.g. 'AllOf' predicate which uses inside all of these." -- "I suggest to add it ... in the form of a separate call like getUnits, but getUnitsAllOf with array of filters passed by reference. In this case the implementation will be much simpler."
Describe alternatives you've considered
Instead of an array of filters, allow sequential chaining composition. [e.g. .GetUnits( IsNonSaturated( IsFinished( IsTownHall())) ) ]  A filter could take a filter input and output a compound filter.
References for different chaining syntaxes:
https://www.fluentcpp.com/2019/08/06/chaining-output-iterators-into-a-pipeline/
http://cpptruths.blogspot.com/2014/03/fun-with-lambdas-c14-style-part-1.html
https://stackoverflow.com/questions/8367879/c-lambda-expression-for-method-chains
https://chriskohlhepp.wordpress.com/advanced-c-lisp/lambda-over-lambda-in-cplusplus14/

I'm working on api extensions, and resolved the problem in the following way:
https://github.com/kubivan/sc2-bot/blob/master/src/utils/UnitQuery.h
so, you can easily implement your own filters, even in compile time(if possible):
 const auto is_mineral = type(UNIT_TYPEID::NEUTRAL_MINERALFIELD) || type(UNIT_TYPEID::NEUTRAL_MINERALFIELD750);
const auto is_resource = is_mineral || is_gas;
const auto resources_around_probe = obs->GetUnits(is_resource && in_radius(probe_pos, 10 ));

Here is my new and improved attempt.
https://github.com/Nickrader/cpp-sc2/commit/b4ce518c2c7e6dd848ac17ab69262a35e97946aa
It lacks testing at the moment, beyond the simple test I put in Tutorial.cc


Fix text2d view-visibility

Objective
Fixes #9676
Possible alternative to #9708
Text2dBundles are not currently drawn because the render-world-only entities for glyphs that are created in extract_text2d_sprite are not tracked by the per-view VisibleEntities.
Solution
Add an Option<Entity> to ExtractedSprite that keeps track of the original entity that caused a "glyph entity" to be created.
Use that in queue_sprites if it exists when checking view visibility.
Benchmarks
Quick benchmarks. Average FPS over 1500 frames.

bench
before fps
after fps
diff

many_sprites
c8fd390
884.93
879.00

bevymark -- --benchmark --waves 100 --per-wave 1000 --mode sprite
c8fd390
75.99
75.93

bevymark -- --benchmark --waves 50 --per-wave 1000 --mode mesh2d
c8fd390
32.85
32.58

Don’t want to muddy the waters but since the new sprites are only created for visible entities could we just have a force_visible bool that gets set to true on the new ones? Not sure if there’s other value to tracking the original entity

Don’t want to muddy the waters but since the new sprites are only created for visible entities could we just have a force_visible bool that gets set to true on the new ones? Not sure if there’s other value to tracking the original entity

My understanding is that entities that are definitely not visible in any view are not extracted, but the visibility check in queue_sprites is per-view / based on RenderLayers.

I re-did the benchmarks on power / without a sneaky bevy ant simulator running in the background / actually averaging all 1500 framerate samples (oops).


Skyrim Egg crashes

Hi @Technoguyfication
since a few days always comes this error.

Getting the same error..Any Fix?

Running into the same issue, any pointers would be welcome

I hate to zombie a thread, however, for anyone else running Ubuntu 22.X that happens across this issue. I changed the docker Image under the egg's 'Configuration' tab to use 'ghcr.io/goover/ubuntu:22-jammy.' Once deployed the egg I chose that as the Docker Image under the 'Startup' Tab along with any other server configurations such as 'difficulty' and 'XP Sync.' Then I started the server for the first time and it booted.

I have fixed this myself 4 months ago was just a little inactive sry


Jt400: make native work

fixes https://github.com/apache/camel-quarkus/issues/5742
PR makes extension jt400 compilable for native. (which was failing before, even if there are no tests)

We should probably tidy up a bit after the 3.8.0. But lets merge so that we have a baseline included in the release.


El Capitan Open Window Dialog

In OS X El Capitan it is impossible to use the open window when it is not bound to a window. This is a demo of the working version: http://gfycat.com/AggravatingHardAmmonite . This is a demo of it not working: http://gfycat.com/DeterminedUnkemptFeline . This also shows up in Atom.

I don't know if we can fix it on Electron's side, I think we should just wait for El Capitan to be stable.

Cross post from https://github.com/atom/atom/issues/7811

I can reproduce the problems on 15A215h.
Here's a snippet of the relevant parts of the system log:
https://gist.github.com/thomasjo/7d5755428327361b8798
The part that stands out is
BUG in libdispatch client: kevent[EVFILT_MEMORYSTATUS] add: "Operation not supported" - 0x2d

I believe that is triggered when you launch the Open dialog. Hard to time exactly, but I get the same stuff dumped every time I provoke the problem.

I have narrowed it down to the following:
var remote = require('remote');
var dialog = remote.require('dialog');

// dialog works as expected:
dialog.showOpenDialog(remote.getCurrentWindow(), { properties: [ 'openFile' ]});

// dialog will not close:
dialog.showOpenDialog({ properties: [ 'openFile' ]});

The same issue is also happening for showSaveDialog, however @crazytyper solution where you specified the browser window, worked for that as well.

Fixed by el capitan beta 3

Anyone have this problem with signed binary for mas submission?
I use electron-v0.34.0-mas-x64.zip and cannot open dialog after signin.


#deliver_later not working with DJ 4.1.3/Ruby 2.4.0/Rails 5.1.1 when using delayed_job as adapter

Using ActiveMailer, delivering synchronously works without issue, but running through the delayed_job adapter I get the following error. Of course, default_url_options[:host] is being initialized in application.rb (otherwise the plain #deliver call would not work).
I'm assuming I'm doing something dumb, but after quite a bit of googling around, I've yet to figure out what that dumb thing is.
application.rb
config.action_mailer.default_url_options = { host: ENV['HOSTNAME'] }

error + stacktrace
ERROR -- : [ActiveJob] [ActionMailer::DeliveryJob] [9ea66c90-6de0-4ae8-a323-b185a05e7889] Error performing ActionMai
ler::DeliveryJob (Job ID: 9ea66c90-6de0-4ae8-a323-b185a05e7889) from DelayedJob(production.mailers) in 1.85ms: ActionView::Template::Error (Missing host to
 link to! Please provide the :host parameter, set default_url_options[:host], or set :only_path to true):
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/http/url.rb:62:in `full_url_for'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/http/url.rb:52:in `url_for'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:331:in `block in <class:RouteSet>'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:826:in `url_for'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:267:in `call'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:208:in `call'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/action_dispatch/routing/route_set.rb:323:in `block (2 levels) in define_url_helper'
/home/rails/thumber_co/app/views/user_mailer/welcome.html.erb:14:in `_app_views_user_mailer_welcome_html_erb__2119493127553626931_43639480'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/template.rb:157:in `block in render'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications.rb:168:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/template.rb:352:in `instrument_render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/template.rb:155:in `render'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/template_renderer.rb:52:in `block (2 levels) in render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/abstract_renderer.rb:42:in `block in instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166:in `block in instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/abstract_renderer.rb:41:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/template_renderer.rb:51:in `block in render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/template_renderer.rb:59:in `render_with_layout'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/template_renderer.rb:50:in `render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/template_renderer.rb:14:in `render'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/renderer.rb:42:in `render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/renderer/renderer.rb:23:in `render'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/rendering.rb:103:in `_render_template'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/rendering.rb:83:in `render_to_body'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/abstract_controller/rendering.rb:24:in `render'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:935:in `block in collect_responses_from_templates'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:932:in `each'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:932:in `each'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:932:in `map'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:932:in `collect_responses_from_templates'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:917:in `collect_responses'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:830:in `mail'
/home/rails/thumber_co/app/mailers/user_mailer.rb:5:in `welcome'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/abstract_controller/base.rb:186:in `process_action'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/callbacks.rb:97:in `run_callbacks'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionpack-5.1.1/lib/abstract_controller/base.rb:124:in `process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/rescuable.rb:23:in `block in process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/rescuable.rb:15:in `handle_exceptions'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/rescuable.rb:22:in `process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionview-5.1.1/lib/action_view/rendering.rb:30:in `process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:609:in `block in process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166:in `block in instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/activesupport-5.1.1/lib/active_support/notifications.rb:166:in `instrument'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/base.rb:608:in `process'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/message_delivery.rb:105:in `block in processed_mailer'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/message_delivery.rb:104:in `tap'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/message_delivery.rb:104:in `processed_mailer'
/home/rails/.rvm/gems/ruby-2.4.0/gems/actionmailer-5.1.1/lib/action_mailer/message_delivery.rb:95:in `deliver_now'

My guess is that environment variable is not set when and where the DJ process is started.

@albus522 That was my first thought, but the value is initialized in application.rb, so env doesn't come into play. Also, the logs indicate that DJ is running in production env.

ENV['HOSTNAME'] is a command line environment variable. That has to be set outside the process for the process to pick it up.

@albus522 Ah. I see what you're asking. No, it's not that. Replacing with a hard-coded string does the same thing.

The workers do not pickup code changes automatically. You have a worker process started that was incorrectly started and has not quit as expected. Do a full stop of all DJ workers. Confirm that every worker process has exited. Then start up fresh. There is nothing special about DJs boot process. DJ simply runs the standard rails boot process same as every other rails process.


[Event Change Request] codeunit 7322 "Create Inventory Pick/Movement" - OnBeforeModifyWarehouseActivityHeader

Could you please add the Location: Record Location to the event OnBeforeModifyWarehouseActivityHeader ?
local procedure ModifyWarehouseActivityHeader(var WarehouseActivityHeader: Record "Warehouse Activity Header"; WarehouseRequest: Record "Warehouse Request")
begin
    //+Change
    //-OnBeforeModifyWarehouseActivityHeader(WarehouseActivityHeader, WarehouseRequest);
    OnBeforeModifyWarehouseActivityHeader(WarehouseActivityHeader, WarehouseRequest, Location);
    //-Change
    WarehouseActivityHeader.Modify();
end;

[IntegrationEvent(false, false)]
//-local procedure OnBeforeModifyWarehouseActivityHeader(var WarehouseActivityHeader: Record "Warehouse Activity Header"; WarehouseRequest: Record "Warehouse Request") //OLD
local procedure OnBeforeModifyWarehouseActivityHeader(var WarehouseActivityHeader: Record "Warehouse Activity Header"; WarehouseRequest: Record "Warehouse Request"; Location: Record Location) //NEW
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


False negative from NBER

https://oadoi.org/10.1093/qje/qjy005 redirects to the closed-access publisher location, but several preprint and postprint versions are available elsewhere.
The "easiest" to find is probably https://www.nber.org/papers/w21331, which includes a link to https://www.nber.org/papers/w21331.pdf and to the published version.

https://support.unpaywall.org/public/tickets/58345d7bd47d699cc45ff7c9b13ae4ed58fe0516758ab6830a0993d0baee60fc


Froala At.js integration issue.

I followed the Froala example and have atjs pretty much working, but there's issues with deleting inserted tags. I noticed the markup is slightly off from the example. This is the markup that's getting inserted:
@Nathan
Any idea why I'm getting contenteditable="false"?
My config:
let config = {
    at: '@',
    data: names,
    displayTpl: '
${name} ${email}
',
    limit: 100
};

The examples online don't have contenteditable at all.

You should close this and follow this one https://github.com/froala/wysiwyg-editor/issues/2166


disable create space without vid_type

Fixes https://github.com/vesoft-inc/nebula-graph/issues/1127

It's an incompatible modification.

what's the return if no vid specified. The return message will be asked many times.

what's the return if no vid specified. The return message will be asked many times.

What do you mean by "The return message will be asked many times"?

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Highlights entire query phrase

Removes split on spaces, so entire query phrase is highlighted.
Fixes #340

I want to acknowledge the tradeoffs in that an AND search doesn't have to be a phrase. So a search for Nelson Rockefeller won't highlight anything in the title/description if they read Nelson A. Rockefeller, for example. Or any two words that may be in the description, but don't appear together would be a hit, but not highlighted.

Yes, that's true. I think this comes down to whether it's worse to highlight some words that aren't hits, or to not highlight some words that are.
I'm also noting that react-highlight-words allows you to write your own findChunks method, so we could potentially use that to introduce more Boolean-like logic.

Ok, good find. I think react-highlight-words is a good in-between solution in that it will align pretty closely with our default Boolean 'AND' search.


chore: preset IDs for pages

Adding a mechanic to keep the count of pages in component trees, and to add predefined keys & IDs for pages if case if they're not provided by user. Fixes a bug with losing CMC page focus upon app code update.

@FabienArcellier @mmikita95 are we good to merge?

@ramedina86 yes, good to go.


Execute recurring user comms and measure

Problem statement
Now that we have tested internally, we want to send this communication out to our first round of users.
What you need to know
Initial Receiver List:

Send date to initial list: Tues, Sept 3
Send date to remaining list: Fri, Sept 6

Acceptance criteria

[x] Create separate unsubscribe list
[x] Send email to initial list from #15189
[x] Send email to remaining users
[x] Monitor shared inbox in case of responses
[x] Measure statistics/impact
[x] Review with Product to determine next steps
[x] Define a short term process of how to manage and add users to SendGrid email list
[x] Create documentation on how to manage the SendGrid and users

Made a video on creating the single send for monthly updates

Video for instructions on managing contacts


Gtest/mock submodules point to outdated repo

See https://code.google.com/p/chromium/issues/detail?id=539853.

Fixed. Thanks for reporting!


Improper working of Interactive marker in rviz

Hello all,
I am using moveit setup tutorial for kinetic version. Instead of pr2 robot, I have generated config file for my own robot. But when I was visualized it in rviz it shows following error -
Interactive marker 'EE:goal_link5' contains unnormalized quaternions. This warning will only be output once but may be true for others; enable DEBUG messages for ros.rviz.quaternions to see more details.
I am attaching my config file also, any help is appreciated. Thanks.
https://drive.google.com/open?id=1cPfW2JxU0rGC3Bdub8vKyUQd5BIHuSCj

Hi @mukesh148, this is not an error with your custom setup (or with rviz) but it's a warning caused by one of the plugins publishing an invalid quaternion. If you identify the publisher of the invalid quaternion please notify the maintainers of the package.
I am not sure if you have seen the ROS support guidelines but we kindly ask that in the future you raise questions like this on answers.ros.org instead.
The rationale for asking all kinds of questions in a single place is:

There are many more people reading questions there so your chances on getting an answer and in a timely manner are much higher.
In the future other users will search there for similar problems and can find your question and the potential answers.
The issue tracker in this repo is used to track bugs, feature requests, etc. But your question is not such an action item.

Hi @mukesh148, did you resolve the error?


Current live sample site gives error

On the sample site after first click I get the error below on chrome Version 58.0.3029.96 (64-bit):
Uncaught Error: No ampdoc found for [object HTMLElement]
at va (https://cdn.ampproject.org/shadow-v0.js:7:358)
at ta.f.createError (https://cdn.ampproject.org/shadow-v0.js:4:36)
at xf.getAmpDoc (https://cdn.ampproject.org/shadow-v0.js:129:512)
at HTMLElement.b.connectedCallback (https://cdn.ampproject.org/shadow-v0.js:161:11)
at https://cdn.ampproject.org/rtv/001493770802531/v0/amp-carousel-0.1.js:21:318
at Array.forEach (native)
at S.push.f.f.buildSlides (https://cdn.ampproject.org/rtv/001493770802531/v0/amp-carousel-0.1.js:21:142)
at S.push.f.f.buildCarousel (https://cdn.ampproject.org/rtv/001493770802531/v0/amp-carousel-0.1.js:16:326)
at S.push.f.f.buildCallback (https://cdn.ampproject.org/rtv/001493770802531/v0/amp-carousel-0.1.js:11:465)
at HTMLElement.b.build (https://cdn.ampproject.org/shadow-v0.js:155:514)

Sebastian/Will, do you know where/why this error is happening?
On Sun, May 7, 2017 at 3:12 AM, Serge van den Oever <
<EMAIL_ADDRESS>wrote:

On the sample site after first click I get the error below on chrome
Version 58.0.3029.96 (64-bit):
Uncaught Error: No ampdoc found for [object HTMLElement]
at va (https://cdn.ampproject.org/shadow-v0.js:7:358)
at ta.f.createError (https://cdn.ampproject.org/shadow-v0.js:4:36)
at xf.getAmpDoc (https://cdn.ampproject.org/shadow-v0.js:129:512)
at HTMLElement.b.connectedCallback (https://cdn.ampproject.org/
shadow-v0.js:161:11)
at https://cdn.ampproject.org/rtv/001493770802531/v0/amp-
carousel-0.1.js:21:318
at Array.forEach (native)
at S.push.f.f.buildSlides (https://cdn.ampproject.org/
rtv/001493770802531/v0/amp-carousel-0.1.js:21:142)
at S.push.f.f.buildCarousel (https://cdn.ampproject.org/
rtv/001493770802531/v0/amp-carousel-0.1.js:16:326)
at S.push.f.f.buildCallback (https://cdn.ampproject.org/
rtv/001493770802531/v0/amp-carousel-0.1.js:11:465)
at HTMLElement.b.build (https://cdn.ampproject.org/shadow-v0.js:155:514)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ampproject/amp-publisher-sample/issues/66, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAsUIXmXVovtbIKIJJnskOkBVbMZR9CIks5r3ZkVgaJpZM4NTFuy
.

I believe this is a dupe of https://github.com/ampproject/amphtml/issues/9291.


[Compatibility suggestion] Open Parties and Claims

A optional compatibility feature with Open Parties and Claims would perfectly fit into this one. Any chance for it?
UPDATE: I might was too fast asking that, because as far as I know there is no per player claims count. It is done with ranks how many claims a rank can have.

Hmm for the moment no, I'm leaving the computer world at the moment, I'm just updating some mod, that's all :(


Fails to properly recognize The Grandfather

Console showed this warning when I (very luckily) had The Grandfather drop:
[3.3.1 2023-12-19 05:35:55,124] WARNING    item.read_descr.read_descr: Could not find affix: ignores loss

Oh yeah. I filter out the word "durability" since I dont want to have it e.g. for "Durability: 100/100". Grandfathers affix is the only one that also includes it.
I will filter out "Durability:" which should fix this. Good catch.
I dont have too many Grandfathers to test on ^^

Thanks for fixing this so quickly!


[BUG] HTML5 data-jstree "opened:false" is not respected

Hi,
http://jsfiddle.net/h6phbzd3/1/

Two nodes have data-jstree='{"selected":true}': "iPhone Original (EDGE)" and "iPhone 3GS".
All of their parents all the way to the top have data-jstree='{"opened":false, set.

Expected behaviour: nodes "iPhone", "iPhone 1", "iPhone 3GS" should be collapsed.
Actual behaviour: nodes "iPhone", "iPhone 1", "iPhone 3GS" are expanded.
Thanks!

There is no opened:false rule - all nodes are closed by default, you can use opened to explicitly open them. The problem you are having is that by default all selected nodes are revealed (their parents are opened), to prevent this from happening when the tree is ready use the expand_selected_onload config option:
http://www.jstree.com/api/#/?q=expa&f=$.jstree.defaults.core.expand_selected_onload
Here is the fixed demo (you may want to open the root though):
http://jsfiddle.net/h6phbzd3/2/

So then, checked checkboxes override behaviour described at http://www.jstree.com/docs/html/:
You can also set the state on a node using a data-jstree attribute.
You can use any combination of the following: opened, selected, disabled, icon.

Wouldn't it be easier for the user to allow use opened:false to avoid onload opening of nodes?

No, as this would lead to conflicts when traversing up and down. opened is designed to open nodes, by default they are closed - I think this is clear enough.
The only time opened:false can be useful is your use case, which only exists because of selected nodes down the hierarchy and is solved by the expand_selected_onload setting. There would be no benefit in introducing one more option that does the same, but could also lead to a lot of conflicts when used.
Best regards,
Ivan

Thanks for the explanation. No further questions.


Replace mlra.service.justice.gov.uk route53 item

Customer would like to replace the mlra.service.justice.gov.uk route53 hosted zone with maat-libra-administration-tool.service.justice.gov.uk and the lower level one in that zone too
He asked for this to be done for mlra-production
MLRA
Description of application
Update the route53 zone and add the new one into https://github.com/ministryofjustice/modernisation-platform/blob/404531ce3e263c3c7[…]65f814d/terraform/environments/core-network-services/route53.tf
Environments
|[ ] Production | [ ] view-only[ ] developer |
Tags

tag
value

application
MLRA

business-unit
LAA

infrastructure-support
<EMAIL_ADDRESS>

owner
<EMAIL_ADDRESS>

Networking options
Current settings listed under MLRA are
"ns-1347.awsdns-40.org."
"ns-508.awsdns-63.com."
"ns-641.awsdns-16.net."
"ns-1943.awsdns-50.co.uk."
Plus an additional one with a type of SOA pointing to ns-1347.awsdns-40.org. awsdns-hostmaster.amazon.com.   - suggest we leave this alone.
Definition of done

[ ] route53 node created
[ ] original definition removed
[ ] customer informed

Sent a message to the network team via slack on #network-operations to get this set up


Support More Cell Editor Types in MudDataGrid

Feature request type
Enhance component
Component name
MudDataGrid
Is your feature request related to a problem?
MudDataGrids Inline Edit Mode only appears to support numeric (casts to double) and string types. Other Types such as DateTime and DateTime? aren't supported.
If you try to implement support with an EditTemplate the value is changed on the row without pressing to save (It doesn't roll back). Nullable types also seem to be an issue even with numeric.
Describe the solution you'd like
Add support for all the basic types and nullable types. I think the DefaultConverters class and possibly allowing passing in a Converter to the cell would be a way to support this.
If support cannot be added soon it may be worth adding to the documentation that only string and numerics are supported editors. Numeric will also cast to double so may create some rounding issues if its a decimal.
Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
Passing in stringified versions of rows and converting back manually.
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

MudDataGrid is under active development, the finished component and what features or purpose it will have is not determent yet.
Until then please don't do feature requests for it. @tjscience tagging you just for FYI


Timer on icon freezes the extension when horn is sounded

this is very noticeable when one uses the popup to sound the horn. Probably need to catch that edge case in the timer so it doesn't bug out when the page is loading.
Workaround for popup notification users: disable the icon timer
Also we will have to rework how extension works for manifest v3, so might not be worth the effort until then.

Found that the issue is with this line here:
https://github.com/m-h-c-t/mh-helper-extension/blob/45565c02c70f5591a2cc4cad7635fb1d5b38fe18/src/scripts/background.js#L88
Specifically, if the browser doesn't have access to the '🎺' emoji, it will almost completely lock up the browser until the hunt is completed and the '🎺' emoji is removed from the icon.
Workaround discussed was to change from using an emoji.
I wonder if there is a check that could be made to see if it's available, and then set it (or an alternative if not available) as a variable in initialisation, rather than as a string constant in that line.
It is a weird edge case, no doubt about it.


Added inline comments to 242-Valid-Anagram

hi @anushibin007 ! thanks for contributing!
do you mind resolving the merge conflicts? it seems like the solution was updated and some of the comments should be changed

closing as stale! please feel free to reopen once the changes have been made, provided there are no existing solutions for the problems given


Add support for radius uncertainties to gas mass calculation

This will be quite a bodgy fix, but to achieve some sort of parity with the XXL gas mass measurements which I'm comparing to in the first mass paper I will add support for radius uncertainties to the  calculation of gas masses in the GasDensity3D profile.
Ultimately this will be achieved through issue #913, but that will take a while so I will add a quick fix first.

I was concerned that this might be a breaking change because I have altered the way that GasDensity3D profiles store gas masses, but actually it should only affect cases where an error was passed because otherwise the storage keys remain the same.
This is all only relevant (and hopefully isn't actually a breaking change) for density profiles that are saved to disk and have been read back in.

I need to make sure that any distributions of radii generated by the function are truncated at zero - can't go below that as it wouldn't be physical behaviour.


Web app user experience is broken

When doing a smoke test on the built source-build cli, the user experience for building a web app is broken.
Steps to repro:
dotnet new web
dotnet restore
dotnet build
dotnet run

The results of dotnet run are:
Using launch settings from /src/tarball-output/testing-smoke/C#_web/Properties/launchSettings.json...
It was not possible to find any compatible framework version
The specified framework 'Microsoft.AspNetCore.App', version '2.1.0-preview2-final' was not found.
  - Check application dependencies and target a framework version installed at:
      /src/tarball-output/testing-smoke/builtCli/
  - Installing .NET Core prerequisites might help resolve this problem:
      http://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
  - The .NET Core framework and SDK can be installed from:
      https://aka.ms/dotnet-download

This message seems to indicate that I need to download Microsoft.AspNetCore.App, but I don't see that it's available separately.  It is only available if you download dotnet core.
There should be some way to acquire just the aspnet bits.

cc @natemcmaster

ASP.NET Core is not source-buildable yet, so this is expected #375. https://aka.ms/dotnet-download doesn't show Microsoft.AspNetCore.App yet because we haven't RTM-ed the first version.  Presumably the instructions look similar to https://www.microsoft.com/net/download/linux-package-manager/fedora26/runtime-2.1.0-preview2, but install the aspnetcore-runtime-2.1.0-preview2-final package.
cc @leecow @rowanmiller - it looks like ASP.NET Core runtime installers are not yet listed on https://www.microsoft.com/net/download/dotnet-core/runtime-2.1.0-preview2. How can we add a section for this?

Downloads are driven by https://github.com/dotnet/core/blob/master/release-notes/releases.json. Work with @leecow to get the missing entries added.

@natemcmaster We are planning on using source-build on RHEL. There are are a few major issues with the suggestions that I can see.

We can't ask users to use a non-RHEL repository to have a working ASP.NET Core setup. If we are asking users to do that, why not just ask them to use all the packages from the Microsoft repository? Same issues applies for anyone else trying to use source-build on any Linux distribution.

What about dependencies? Most packages from the Microsoft RPM repo have dependencies on other Microsoft packages. Is installing just ASP.NET Core runtime package (without installing the Microsoft-built RPMs) even an option? For any distribution not supported by Microsoft, it looks like using ASP.NET Core may not even work.

The packages at the microsoft repository will install the ASP.NTE Core shared runtime at /usr/share/dotnet/.., while our installation of .NET Core will be somewhere under /opt/... Our installation will not be able to make use of the ASP.NET Core packages installed that way.

cc @aslicerh  @tmds @Bob-Davis It looks like ASP.NET Core will not work out of the box from source-build. and will require users to install extra bits by hand

@natemcmaster was just looking at the file and I see the entries there and the corresponding links on the site. Are there some that are missing?

I would echo what @tmds stated - the expectation here is that it would work how 2.0 worked, and pull the package(s) from nuget.
This sounds like this point release is breaking the expected functionality.
Am I misunderstanding this?

To be clear, what I meant by

If I remember right, you worked around this in 2.0.x by disabling the ASP.NET Core runtime store. We'll have to investigate if a similar workaround is available now that we are shipping aspnet as a shared framework.

is that in 2.0, this was the story.

Source built installation
Default installations

NuGet Packages
NuGet.org
NuGet.org

ASP.NET Core runtime binaries
In app's publish folder (via opt-ing out of the runtime store trimming)
ASP.NET Core Runtime Package Store

In 2.1, the issue at hand is this

Source built installation
Default installations

NuGet Packages
NuGet.org (no change)
NuGet.org

ASP.NET Core runtime binaries
???? (need to determine how to make this app local)
ASP.NET Core Shared Runtime Framework

???? (need to determine how to make this app local)

Yes, we are missing the equivalent of 2.0 'PublishWithAspNetCoreTargetManifest=false'.

The shared framework can be opted out of by having the templates explicitly set Microsoft.NETCore.App as the platform package.

The shared framework can be opted out of by having the templates explicitly set Microsoft.NETCore.App as the platform package.

@DamianEdwards how do you csproj that?

Presumably you can do that by setting this:
  <PropertyGroup>
    <MicrosoftNETPlatformLibrary>Microsoft.NETCore.App</MicrosoftNETPlatformLibrary>
  </PropertyGroup>

Disclaimer: haven't tried it myself.

And setting MicrosoftNETPlatformLibrary makes those assemblies part of the published application?
Would it be possible to make this a single property we can set (like we were setting PublishWithAspNetCoreTargetManifest), since in our scripts we don't know if the user is targeting Microsoft.NETCore.App or Microsoft.NETCore.All.

And setting MicrosoftNETPlatformLibrary makes those assemblies part of the published application?

That's the theory. It instructs the SDK which NuGet package represents the shared framework.

Would it be possible to make this a single property we can set

I believe <MicrosoftNETPlatformLibrary>Microsoft.NETCore.App</MicrosoftNETPlatformLibrary> is the default value for all projects using Microsoft.NET.Sdk. But if you find setting this unconditionally causes issues, let me know.

But if you find setting this unconditionally causes issues, let me know.

We are unconditionally setting PublishWithAspNetCoreTargetManifest. And our users can be using anything with this setting. For 2.1, they may be using Microsoft.NETCore.App or Microsoft.NETCore.All or their application may even not be ASP.NET Core based webapp. All these cases should work. I will do some experimentation. If you know some of these things may not work/have unexpected side-effects, we should look into something that works more similar like PublishWithAspNetCoreTargetManifest.
My use-case is focusing on the publish command. The issue report is on the run command, which we like to work out-of-the-box too on source-built .NET Core.

I believe Microsoft.NETCore.App is the default value for all projects using Microsoft.NET.Sdk. But if you find setting this unconditionally causes issues, let me know.

@natemcmaster Passing /p:MicrosoftNETPlatformLibrary=Microsoft.NETCore.App to dotnet publish works! It is a suitable replacement for 2.0 /p:PublishWithAspNetCoreTargetManifest=false.
Any thoughts on how we can make dotnet run work out-of-the-box on source-build .NET Core? For 2.0 this worked without making any changes to the project file or passing additional parameters.

Any thoughts on how we can make dotnet run work out-of-the-box on source-build .NET Core?

There are a range of options, from ones requiring explicit user action to overriding the default. My preference would be to add a condition to detect when the aspnet sharedfx is unavailable.

Explicit user choice: aspnet adds an option to templates such as dotnet new web --no-shared-fx so new projects contain the override for MicrosoftNETPlatformLibrary. Source-build users are expected to use this option
Detect source-built SDK: ASP.NET could honor some conditions which a source-build SDK could set differently from a normal build of the SDK.

<!-- In the source-build SDK -->
  <_AspNetSharedFxIsAvailable>false</_AspNetSharedFxIsAvailable>

<!-- In Microsoft.AspNetCore.App.nupkg -->
  <MicrosoftNETPlatformLibrary Condition="'$(_AspNetSharedFxIsAvailable)' != 'false'">Microsoft.AspNetCore.App</MicrosoftNETPlatformLibrary>

Override the SDK: Source build adds properties to Microsoft.NET.Sdk to override MicrosoftNETPlatformLibrary, even when set via PackageReference to Microsoft.AspNetCore.App

Thoughts @JunTaoLuo @DamianEdwards @muratg ?

If we went with the "Detect source-built SDK" option, we could make detection smart enough to know when Microsoft.AspNetCore.App is installed. But even if we didn't, user's apps will still run...they will just be sub-optimal and bulky.

@natemcmaster thank you for providing some options.

If we went with the "Detect source-built SDK" option, we could make detection smart enough to know when Microsoft.AspNetCore.App is installed.

That is the best option.

But even if we didn't, user's apps will still run...they will just be sub-optimal and bulky.

And imo this is also a good option.

@DamianEdwards, @natemcmaster, what option are we going for?

We haven't made a decision yet. I think we have scheduled time to discuss this and other aspnet related things tomorrow.

Thanks for the update!

I just realized the lack of a shared framework also impacts global tools.
A tool like dotnet-serve has a dependency on the ASP.NET Core shared framework. So it won't run on source-build .NET Core.
I've checked the tools that ship out-of-the-box with Microsoft sdk (watch, dev-certs, user-secrets, sql-cache, ef). These all depend on 'Microsoft.NETCore.App', so they should work on source-build (to be verified).
I don't think it is feasible to solve this for 2.1 in general. We definitely like tools that come with the Microsoft installation to be able to work out-of-the-box on source-build (after manual dotnet tool install). This should be the case already.
Side-note: the dotnet-ef package wasn't published on nuget.org for 2.1-preview2.

The tools that you listed (watch, dev-certs, user-secrets, sql-cache, ef) will actually ship in-box with the SDK. They only shipped to nuget.org for preview1, but were then moved into the SDK (see https://github.com/aspnet/Announcements/issues/290). That means for preview2 and rc1, those tools are not available in source-build. This is an important part of the aspnet story on source-build we need to fix. I was going to bring up in our meeting in a few hours, but I'll share my thinking now anyways.
Two options:

Getting all of aspnet supported in source-build is too big a task to accomplish in the 2.1.0 timeframe (see #375 ). However, pieces of aspnet could be made to build in source-build. We could start with the most used global tools first like watch and ef. I can't commit to the work required, but I think it's feasible.
Alternative: ship the tools to nuget.org as packages. Source-build users acquire them via dotnet tool install. On our end, we need to change these tools to support shipping to nuget.org. This will take much less work than getting these into source build, however, IMO its a less desirable solution. Pros: unblock source-build users. Cons: requires manual install, the presence of these packages on nuget.org may confuse users about how they are expected to acquire and use them.

We had another meeting today and I think we can squeeze in a few last minute changes. They won't be in 2.1.0-rc1, but we believe we can land them before 2.1.0.
The planned work is described here https://github.com/aspnet/Universe/issues/1125 and here https://github.com/aspnet/Universe/issues/1126. In a nutshell, we'll disable the shared framework trimming in the SDK and ship global tools to nuget.org so they are available via dotnet tool install. Our hope is this will mitigate the biggest issues in the web experience when using a source-build SDK. Please take a look at the proposals and let me know if you have questions or concerns.

@natemcmaster Great!! This will give the best experience for source-build .NET Core users to deal with 'missing bits'!

I found something I don't understand about source-build. Does dotnet new web actually work on a source-built SDK? If so, where is the web template coming from?
We deliver the web template to the CLI via the Microsoft.DotNet.Web.ProjectTemplates.2.1 package, which is built with the rest of the aspnetcore runtime and shouldn't be available during source-build.
cc @dseefeld

@natemcmaster Yes, dotnet new web does work.  The Microsoft.DotNet.Web.ProjectTemplates.2.1 package is included as a prebuilt package, since we don't build any aspnet assets as part of source-build, yet.

Interesting...I thought prebuilt packages weren't allowed. What are the rules for including prebuild packages? Any reason we couldn't include other packages too, like the ones that contain aspnet console tools?

My guess is because the templates package doesn't actually include any binaries, just text files, so it's essentially just source.

For 2.0 we are in fact unzipping the prebuild package and patching the templates (adding PublishWithAspNetCoreTargetManifest=false).
Ideally everything is built from source and those sources can just be patched.

Ok, I've completed all the work we are planning to do for 2.1.0. This won't be in rc1, but should be in the rtm build. See https://github.com/aspnet/Universe/pull/1131, https://github.com/aspnet/Universe/pull/1130, and https://github.com/dotnet/cli/pull/9178.
I believe there is at least one other item affecting global tools acquisition, but let's use https://github.com/dotnet/cli/issues/9114 to track that. That's not specific to aspnet tools.
This should solve the scenario as described in the original issue. If it doesn't, we can re-open for more investigation.


Create TCP/UDP/HTTP/Websocket balancer for timely

Use of the memory cache feature requires that all requests for storing or querying a metric go to the same timely instance.

Created load balancer


[Feature] Force/bypass fullscreen

Device
Desktop
Suggestion
A checkbox to stop xbox from checking if the window is in fullscreen

Screenshot?

Device
Desktop
Suggestion
A checkbox to stop xbox from checking if the window is in fullscreen

Have you already tried to achieve this by using one of the Smart TV UA profiles?

Device
Desktop
Suggestion
A checkbox to stop xbox from checking if the window is in fullscreen

Have you already tried to achieve this by using one of the Smart TV UA profiles?

doesnt work, i want to use mouse and keyboard

#373


Add an openapi.yaml file to the server implementation.

Rendered API documentation
This PR creates a single OpenAPI specification for the Warg registry server.
It is intended to (ultimately) be the complete specification of a Warg registry server's REST API.
The specification proposed here is not what is currently implemented by warg-server, but it is inspired heavily by both the existing implementation and previously proposed APIs.
We can use this as a starting point to finalize an API specification for the initial version.
An API around streaming records to federated registries is not currently included in the specification, so design around this is welcome.

The intention behind this PR is to be a starting point for coming to consensus on exactly what the REST API should be for 1.0.
I'll bring this up in tomorrow's meeting, but everyone should feel empowered to collaborate on this proposed specification.
The sooner we have a real spec, the sooner we can get the warg-server implementation conforming and alternative implementations can begin.

There are things here I think make a lot of sense, like putting limits on package log fetching which works pretty well with the "since"-semantics to enable paging/cursoring.
There are other changes here that I'm less sure about and I think are going to require a lot of discussion. Especially around changes to the package API and the introduction of metadata.
In the package log semantics, you can't initialize a package without signing a record containing an init entry and there's nothing preventing you from putting other entries in that record. So IMO it doesn't really make sense to separate initialization into its own API and if you did that API would still need to send a signed record.
The package metadata proposed here isn't verifiable by end users and its not clear who would have permission to update it. We should discuss different options for metadata, because there are ways to include metadata that are more consistent with the rest of the protocol design and in-log permissions system.
Other than that, there's some minutiae. For example, I think the name field in the 200 response to GET /package/{logId} might need to be optional someday in the case that we eventually support name-takedown and I'm not sold on appended as the name of that status, but we can bikeshed these after the core issues are resolved.

I'm totally fine with eliminating the "create package" and "update package" endpoints in favor of putting the metadata into the log itself, thus only needing a "append record" endpoint for both creating new logs and updating package metadata. I'd like us to start thinking about basic metadata sooner than later, though.
We might still want a "give me the latest metadata" endpoint (i.e. GET /package/{logId}) where the registry can return back what it believes to be the latest metadata; clients could verify it is correct themselves via validating the log, if so desired.
I'm definitely not married to appended, so open to alternatives; accepted I wanted to avoid because it can be confused with the HTTP status and published didn't feel right for records when most registries talk about releases in that context.

With #114 merged, this spec now reflects the current state of the REST API implemented in the client and server.

It's up to date in the sense it describes how the current implementation works.
I think we should merge it to then let Danny update it with the proposed changes to return the upload URLs to the client.


Add monsters to ignore / hide in loot tracker

Is your feature request related to a problem? Please describe.
Whenever I use the loot tracker, and I kill irrelevant monsters (eg. Scavenger beasts in raids), all the loot of those monsters shows up in the loot tracker.
Describe the solution you'd like
I'd like an option in the loot tracker settings menu, where we can enter names of monsters that we do not want the loot to appear from, in the loot tracker.
Describe alternatives you've considered
You could right click a monster name in the loot tracker, and select "Add to ignore monster list of loot tracker" to add it to that list.
Both solutions could also be implemented.
You could also hide the monsters instead of putting them on ignore, like you can do with items.

Is this closed because it can't be done, or just because there isn't enough interest for it?
I feel that janholbrouck is right, it's rather obnoxious to have to disable every possible drop in order to not see a monster's loot, especially if you want to see any of those items when you get them from another monster.


add %c handling to console, add color support for proxy console

I've added support for:
console.log('%cthis is colored text', 'color: red; background: pink;')
since I work with pixi.js (pixi-shim) and they have a pretty colored hello message that was looking plain ugly
to see the message in action

add library pixi-shim

import {Application} from 'pixi-shim'
new Application

see console tab

fixed console.log('%c') corner case

added %s string replace


Praetorian abilities

[x] #364
[x] #365
[x] #366
[x] #367
[x] #368
[x] #391
[x] #405
[x] #406
[x] #393

Done in https://github.com/RMC-14/RMC-14/pull/4155


Flash IFS root not possible

It wont find the command out of the script!
Cannot execute - no such file or directory
Btw. flash unlock needs to be written together "flashunlock". Can this be fixed? Thanks

Fixed it.

When will the new version be available?

It's already committed

Script is still the same in latest release!

Hmm, changes must have not been committed then. I'll fix it. But.....if you need to use the function, in the mean time it's easy to update this script by yourself 😉

I've done this already before, the problem is, that these command are not working in the user context that the toolbox is working on! I thought you have found a problem for this as well.
Its still saying "file not found"

With the "on -f" command, it doesn't care about the context. I use modifye2p in the same way.., works here. I can see if I can make it better.

I tried this now:
on -f rcc /net/mmx/fs/sda0/Advanced/IFS/flashunlock
on -f rcc /net/mmx/fs/sda0/Advanced/IFS/flashmib -a 0x00BA0000 -d -f /net/mmx/fs/sda0/Advanced/IFS/ifs-root.ifs
on -f rcc /net/mmx/fs/sda0/Advanced/IFS/flashlock
Get the error:
ldd:FATAL: Could not preload library /lib/libeccp-ne.so.4


Amend Transition page metadescription

I'm going to check why this isn't read from the content item. Will make a new story to sort this (and the search index entry) out if they can be.
https://trello.com/c/zYugZiMJ/288-update-meta-description-for-transition-landing-page-for-site-search-purposes

Also see https://github.com/alphagov/collections/pull/1817


v2.2.4 Non-master branch not detecting .rancher-pipeline.yml

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Push .rancher-pipeline.yml to branch
Result:

Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.2.4
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): custom
Machine type (cloud/VM/metal) and specifications (CPU/memory): metal
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.0", GitCommit:"e8462b5b5dc2584fdcd18e6bcfe9f1e4d970a529", GitTreeState:"clean", BuildDate:"2019-06-19T16:40:16Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:           18.09.6
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        481bc77
 Built:             Sat May  4 02:35:27 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.6
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.8
  Git commit:       481bc77
  Built:            Sat May  4 01:59:36 2019
  OS/Arch:          linux/amd64
  Experimental:     false

Can you elaborate the source code provider and its version you are using?
Do you find the pipeline file commit(create/update) in the commit history of the v0.2 branch?
Can you share the pipeline file stored in the v0.2 branch if feasible?

@gitlawr both master and v0.2 branch are identical
It shows the .rancher-pipeline.yml for the master branch, but not for the v0.2 branch
stages:
- name: Build
  steps:
  - publishImageConfig:
      dockerfilePath: ./Dockerfile
      buildContext: .
      tag: registry/ui:v2.0.22
      pushRemote: true
      registry: registry.world0:5000
    env:
      PLUGIN_DEBUG: "true"
      PLUGIN_INSECURE: "true"
- name: Deploy
  steps:
  - applyYamlConfig:
      path: ./deployment.yaml
timeout: 60
branch: {}
notification: {}


Bump VexRiscv

This updates VexRiscv submodule to the version that supports building emulator for LiteX.

@enjoy-digital I'm working on an automated scritp for building and running Linux on LiteX+VexRiscv using litex-buildenv. For this I need the newest VexRiscv version that supports building emulator (VexRiscv BIOS) configured for LiteX platform. This feature has recently been added to master so I need to bump submodules in Litex to use it.

Thanks!


"editor.tokenColorCustomizations" shows different colors in different scope?

See the image, after my customizing the theme color, Javascript's "const", "let", "var", "function" declaration does not change color under the class scope. Why? Is this a bug?

Can you run the "Developer: Inspect TM Scopes" command and click on the "var", "let", "const", and "function"? What scopes does the command say those have?

Which's purple color:

Which's pink color:

@alexr00

What theme are you using? If not one of the defaults, can you reproduce with a default theme? I don't see anywhere we might be using that color.

I use the Snazzy Light
 theme, downloaded from marketplace.visualstudio.com
And what's the meaning of "reproduce with a default theme"?

The scopes listed are different, which means that any theme author can color them differently if they wish.
If you can reproduce the issue with a default theme, such as Dark+, then the color difference could be because of the theme that you have installed.

It looks like the colors are different because the theme you have installed gets very specific.
The pink is coming from meta.class storage.type and the purple is from your customization of storage.
@aeschli Can you confirm that more specific wins with themes?
	"editor.tokenColorCustomizations": {
		"textMateRules": [
			{
				"scope": ["storage.type"],
				"settings": {
					"foreground": "#cc66ff",
					"fontStyle": "bold"
				}
			}
		]
	}

This is the sample:
var a = 1;
let b = 'sss';
const c = [];
function d() {}

class F {
    somr() {
        var w = 1;
        let x = 'sss';
        const y = {};
        function z() {}
    }
}

Yes, the most specific match wins.

@alexr00 , I understand what you mean, maybe my expression was indistinct.
I change the "storage.type" scope to set bold and italic font style and it work except for colors under the class scope.

As @aeschli  said that the most specific match wins, my customization should be the top priority, but except for colors now...🤔

The theme specifies meta.class storage.type, which is more specific.


popover: Fixed color-picker popover responsiveness.

The color picker popover overflows the screen width when an user attempts to change the stream color in devices with narrow screen width size ( <500px ) .
Made suitable changes as suggested by @timabbott here .
Fixes #16477
Before :

After

768<=width<=400
width < 400

Visually that looks great, except that the | vertical separator should disappear in the smallest size.

Could you review it again @timabbott .

This is great, merged, thanks @aryanshridhar!
@amanagr FYI -- the 768 breakpoint here may be relevant for your media CSS migration.
(One thing I'm realizing is that we probably need to put the new constants in static/js/resize.js or maybe an associated data module or util.js or something and access them in other modules to the extent that we have JS logic that needs to agree with the Media CSS).

@aryanshridhar it'd be awesome if you could continue with doing this sort of migration for any other popovers you can find this sort of issue with -- it's the kind of thing that's much more efficient to do in series, and would also let us advertise this effort as complete in the release notes.

Okay, maybe a variables.js that will store all variables to be used both in js and css files.


Feature validator

@cgewecke can you please try to test it locally, as when I remove JSON.parse on loadFiles level I can't seem to get positive results from this function: https://github.com/ethereum/source-verify/blob/03a6bf4a7b3a9cd3e2eea092732894f7a567d3b8/injector.js#L96
I'm using files from test/sources/all/simple.meta.json and Simple.sol

I read through the relevant thread about this at Solidity and it looks like the person wants to verify a contract on-chain by cloning a Truffle project on Github, compiling the contracts and checking if the metadata produced matches the hash of the bytecode deployed to chain.
There are difficulties with this because of the way Truffle compiles using absolute paths as source keys - something discussed in #23, #24, and #27. I'm not sure this PR is really the validation they're looking for unfortunately ...
Perhaps we should investigate this in more depth as part of a second iteration where we try to make a truffle plugin or general lib for cli tools that could handle this use case.
Reproducing part of the thread here for reference:
So here is how it works-:
I compiled contracts on my machine and deployed it on the chain.
Which means metadata associated with the deployment is related to my machine
Now user wants to verify that the contract that they are going to interact with actually
corresponds to our open source repository
1. They clone the repository
2 .They compile the contracts using their machine. Now in this case metadata will change
3. Now they verify both bytecodes

The verification process should work out of the box, irrespective of the machine and environment used for the actual compilation and deployment
Though the compiler version and other compiler settings should remain same

I definitely agree. Let's keep it open and discuss it after ethcc to see how to solve this.

This was merged by mistake :( @cgewecke should I remove it from staging?

@edisinovcic I undid it in an earlier rebase it's all fine :)

Awesome, tnx!


Customer theme

Fixes #13

[GitHub Actions]
Deployment SUCCESS
Commit e33dff541f6cd82e70072992f885a0c13d2adfa9 successfully deployed to https://nrn-admin-frgc12vm7.now.sh
Deployment aliased as https://nrn-admin-customer-theme.now.sh

[GitHub Actions]
E2E tests FAILED
Download artifacts (screenshots + videos) from checks section at the top