Poor performance of the compiler

I've noticed that compiling code that includes larger array like the following
🍿 0x29 0x2E 0x43 0xC9 0xA2 0xD8 0x7C 0x01 0x3D 0x36 0x54 0xA1 0xEC 0xF0 0x06 0x13
   0x62 0xA7 0x05 0xF3 0xC0 0xC7 0x73 0x8C 0x98 0x93 0x2B 0xD9 0xBC 0x4C 0x82 0xCA
   0x1E 0x9B 0x57 0x3C 0xFD 0xD4 0xE0 0x16 0x67 0x42 0x6F 0x18 0x8A 0x17 0xE5 0x12
   0xBE 0x4E 0xC4 0xD6 0xDA 0x9E 0xDE 0x49 0xA0 0xFB 0xF5 0x8E 0xBB 0x2F 0xEE 0x7A
   0xA9 0x68 0x79 0x91 0x15 0xB2 0x07 0x3F 0x94 0xC2 0x10 0x89 0x0B 0x22 0x5F 0x21
   0x80 0x7F 0x5D 0x9A 0x5A 0x90 0x32 0x27 0x35 0x3E 0xCC 0xE7 0xBF 0xF7 0x97 0x03
   0xFF 0x19 0x30 0xB3 0x48 0xA5 0xB5 0xD1 0xD7 0x5E 0x92 0x2A 0xAC 0x56 0xAA 0xC6
   0x4F 0xB8 0x38 0xD2 0x96 0xA4 0x7D 0xB6 0x76 0xFC 0x6B 0xE2 0x9C 0x74 0x04 0xF1
   0x45 0x9D 0x70 0x59 0x64 0x71 0x87 0x20 0x86 0x5B 0xCF 0x65 0xE6 0x2D 0xA8 0x02
   0x1B 0x60 0x25 0xAD 0xAE 0xB0 0xB9 0xF6 0x1C 0x46 0x61 0x69 0x34 0x40 0x7E 0x0F
   0x55 0x47 0xA3 0x23 0xDD 0x51 0xAF 0x3A 0xC3 0x5C 0xF9 0xCE 0xBA 0xC5 0xEA 0x26
   0x2C 0x53 0x0D 0x6E 0x85 0x28 0x84 0x09 0xD3 0xDF 0xCD 0xF4 0x41 0x81 0x4D 0x52
   0x6A 0xDC 0x37 0xC8 0x6C 0xC1 0xAB 0xFA 0x24 0xE1 0x7B 0x08 0x0C 0xBD 0xB1 0x4A
   0x78 0x88 0x95 0x8B 0xE3 0x63 0xE8 0x6D 0xE9 0xCB 0xD5 0xFE 0x3B 0x00 0x1D 0x39
   0xF2 0xEF 0xB7 0x0E 0x66 0x58 0xD0 0xE4 0xA6 0x77 0x72 0xF8 0xEB 0x75 0x4B 0x0A
   0x31 0x44 0x50 0xB4 0x8F 0xED 0x1F 0x1A 0xDB 0x99 0x8D 0x33 0x9F 0x11 0x83 0x14 🍆 ➡ S

takes around 18 seconds

08:12 $ time emojicodec md2.emojic
real    0m18.509s
user    0m18.252s
sys     0m0.125s

while compiling the same with -O is fast.

time emojicodec -O md2.emojic
real    0m0.732s
user    0m0.578s
sys     0m0.029s

Looking at LLVM output I think the culprit is the overuse of alloca in the generated (by emojicode compiler?) code
 %S = alloca %s.vt_1f368
 %0 = alloca %s.vt_1f368
 %1 = alloca %box
 %2 = alloca %box
 %3 = alloca %box
 %4 = alloca %box
 %5 = alloca %box
 %6 = alloca %box
 %7 = alloca %box
 %8 = alloca %box
 %9 = alloca %box
 %10 = alloca %box
...

I would assume that -O would influence the output binary code to be optimized.
From logical point of view I would expect non-optimized compilation should be faster than the optimized one as optimization phase is omitted.

Thanks for reporting this, and sorry for not getting back to you earlier. I’m aware of this limitation as it also affects our test suite. There’s generally no downside in using -O except that it makes the produced LLVM harder to debug.
The generated code is an architectural limitation of the compiler. Although I started work to overhaul the compiler last year, which should also fix this problem, I have too little time to work on Emojicode these days.

Thanks for letting me know. I totally understand the lack of time


feat: adding model name column in service page

What does this PR do?
As recommended by @lstocchi adding a model name column to the Services list page
Screenshot / video of UI

What issues does this PR fix or reference?
Fixes https://github.com/projectatomic/ai-studio/issues/540
How to test this PR?

[x] unit tests has been provided

@lstocchi I went to have a look at how it's done throughout the app atm and there seems to be inconsistencies with it.

imo the left aligned looks better and that seems to be what is trying to be done throughout

@lstocchi I went to have a look at how it's done throughout the app atm and there seems to be inconsistencies with it.

imo the left aligned looks better and that seems to be what is trying to be done throughout

Thanks, i'll open an issue then 👍


docs: add example of how to write tests

Feel free to fully edit it, but I think this should be explained somewhere!

That's very helpful, thanks.


Extra foo() Test Being Displayed

When running kotlintest unit tests, an extra foo() test is being displayed as passing.
Probable cause: https://github.com/kotlintest/kotlintest/blob/master/kotlintest-runner/kotlintest-runner-junit5/src/main/kotlin/io/kotlintest/specs/specs.kt#L8-L10
I am writing tests for a gradle project. Here are the versions.
kotlintest version: 3.1.0-RC2
kotlin version: 1.2.41
gradle version: 4.7
Screenshot of the extra foo() test in Intellij.

The foo() dummy test is definitely the cause, but this would only happen if you had junit-jupiter on the classpath, which isn't pulled in by kotlintest by default.
The reason for the dummy test is in order to fool intellij into putting the little green arrow next to the test class.

In a mixed language environment with a combination of JUnit 5 and kotlintest tests, I think that would happen pretty commonly. I'm curious if there might be another way to fool IJ instead of battling with the classpath.

It is usual to have junit tests and kotlintest tests in the same project?
I would like to find another way to fool intellij though. Let me have a think and a play. I'm pretty close with an intellij plugin anyway, which would be the best solution - the intellij plugin is the main focus of 3.2

We're experiencing that now, where older Java code with extant JUnit tests is living side-by-side with newer Kotlin code and kotlintest. The dummy test reporting isn't the biggest deal in the world, but it is a bit of noise we'd be happier to get rid of.
I'm definitely excited about the progress on the IJ plugin and look forward to it. We're loving kotlintest.

thanks for the feedback :)

I've made a change that should yield better results. If you want to try it, please try with 3.1.0-RC3.

The RC3 doesn't look like it made any differnce now I tested it more, but I believe I do have a working fix in master currently ready for RC4 or 3.1.0 final. @bakejeyner  @coyotesqrl

Ok 3.1.0-RC4 is now released and I think you should be good. Let me know and we can close this ticket.

👍 The extra foo() is gone, works like a charm! Thanks!

Thanks, Stephen!

3.1.0 final is now released. Closing ticket.


Subscriber not listening all messages from EventHub

We are trying to use Eventhub in our application as notification channel. Presently we are facing issue with subscribing the message, the subscriber picks 1 message out of 4 message.
Expected Behavior
To be subscribe all the messages from event hub
Current Behavior
Subscriber not receiving all messages which are send by Publisher
Snapshot Code for Reproduce
@Component
@EnableBinding(Sink.class)
public class HUDInvoiceEventListener {

    @StreamListener(Sink.INPUT)
    public void handleMessage(String message) throws Exception {
        System.out.println(String.format("New message received: '%s'", message));
    }
}

Sample Screenshot: We sent 15 request with message 1 to 15, but our subscriber receives only 4 out of 15.

Your Environment

Version used: spring-cloud-azure-eventhubs-stream-binder
Operating System and version (desktop or mobile): windows & linux (both platforms have it)
SDK version: spring-cloud-azure-eventhubs-stream-binder 1.2.1

Thanks for reaching out, could you try to upgrade to our latest release 1.2.6 to see whether the same issue exists?

we also have similar issue. Not all events sent are received by the consumer. We're using version 1.2.6.
We don't see any error or exception in logs

@rodrigolopes Do you have a sample project that I could reproduce the issue?

I cleaned up some unrelated code, but the consumer is basically the below
`@EnableBinding(Sink.class)
public class AuditConfig {
private static final Logger LOGGER = LoggerFactory.getLogger(AuditConfig.class);

private final ObjectMapper objectMapper = new ObjectMapper();

@StreamListener(Sink.INPUT)
public void handle(Message<String> message, @Header(name = "messageType", required = false) String messageType) throws JsonProcessingException {
    if (MessageType.HEARTBEAT.name().equals(messageType)) {
        handleHeartbeatEvent(message);
    } else { // in case not all clients are sending the messageType header, we assume it's audit
        handleAuditEvent(message);
    }
    Metrics.counter("events.processed", "messageType", messageType).increment();
}

private void handleHeartbeatEvent(Message<String> message) {
    String heartbeat = message.getPayload();
    LOGGER.info("received heartbeat {}, at {}", heartbeat, Instant.now());
    heartbeatService.storeHeartbeat(heartbeat);
}

private void handleAuditEvent(Message<String> message) throws JsonProcessingException {
    String auditJson = message.getPayload();
    LOGGER.debug("Received auditVo: {}", auditJson);

….
}
@ServiceActivator(inputChannel = "audit.$Default.errors")
public void consumerError(ErrorMessage errorMessage) {

    Message<?> originalMessage = errorMessage.getOriginalMessage();
    Throwable throwable = errorMessage.getPayload();
    Object originalPayload = null;
    String contentType = "audit";
    if (originalMessage != null) {
        originalPayload = originalMessage.getPayload();
        MimeType mimeType = originalMessage.getHeaders().get("contentType", MimeType.class);
        if (mimeType != null) {
            contentType = mimeType.toString();
        }
    }

    LOGGER.error("Error processing message {}. Error: {}", originalPayload, throwable);
    auditService.handleError(contentType, originalPayload, throwable);
}

…
}`
properties:
spring.cloud.azure.eventhub.namespace=*** spring.cloud.azure.eventhub.connection-string=***** spring.cloud.azure.eventhub.checkpoint-storage-account=**** spring.cloud.azure.eventhub.checkpoint-container=events spring.cloud.azure.eventhub.checkpoint-access-key=**** spring.cloud.stream.bindings.input.destination=*** spring.cloud.stream.bindings.input.group=$Default spring.cloud.stream.eventhub.bindings.input.consumer.start-position=EARLIEST

@rodrigolopes Thanks for the info and we'll look into it.

@yiliuTo - do you suggest this team also tries the fix you suggested for issue #709 ?

@rodrigolopes Sorry for the late response. Which version of the event-hub stream binder are you using?

Hi @jochenvw @rodrigolopes , it seem this issue is not the same as 709 which is about failing to reconect to eventhubs and blobs after losing connections. And that issue is due to that an error code of losing connection did not be processed and event hub consumer tried to drain queues while the link processor had already been terminated thus stopping disconnection state being propagated to user application.

@rodrigolopes Sorry for the late response. Which version of the event-hub stream binder are you using?

@rodrigolopes Sorry for the late response. Which version of the event-hub stream binder are you using?

Initially we used 1.2.1 and then we upgraded to 1.2.6.

@rodrigolopes Sorry for the late response. Which version of the event-hub stream binder are you using?

We use 1.2.6

@rodrigolopes
Could you try with setting this property: spring.cloud.stream.eventhub.bindings.input.consumer.checkpoint-mode=RECORD?
Do you have a logging output that could help up debug? Also, could you set logging.level.com.microsoft.azure.spring.integration.eventhub=debug to see if the checkpoint works correctly?

sorry for late response. We were handling the issue via a Microsoft ticket.
recreating the eventhubs and using the dependencies as below seems to have resolved the problem for us:
		<dependency> 		    <groupId>com.microsoft.azure</groupId> 		    <artifactId>spring-cloud-azure-eventhubs-stream-binder</artifactId> 		    <version>1.2.6</version>  		    <exclusions>  		        <exclusion>   		            <groupId>com.azure</groupId>  		            <artifactId>azure-messaging-eventhubs</artifactId>  		        </exclusion>  		        <exclusion>  		            <groupId>com.azure</groupId>  		            <artifactId>azure-core</artifactId>  		        </exclusion>  		    </exclusions> 		</dependency>  		<dependency>  		    <groupId>com.azure</groupId>  		    <artifactId>azure-messaging-eventhubs</artifactId>  		    <version>5.1.1</version>  		</dependency>  		<dependency>  		    <groupId>com.azure</groupId>  		    <artifactId>azure-core</artifactId>  		    <version>1.5.1</version>  		</dependency>

Any update on this issue?


Referenced files crash gulp-typescript on TS 1.5

gulp-typescript v2.7.6
typescript v1.5.0-beta local and global.
Compile task:
gulp.task('compile', function()
{
	var proj = typescript.createProject('src/tsconfig.json');
	proj.typescript = require('typescript');
	proj.sortOutput = true;
	return gulp.src('src/**/*.ts')
		.pipe(typescript(proj))
		.pipe(concat('index.js'))
		.pipe(gulp.dest('www/js/'))
	;
});

Line causing errors:
///<reference path="./Screen.ts" />

Now, if I compile it as-is, gulp-typescript gets filenames using internal TypeScript 1.4, returning referenced file names as filename. However, TypeScript 1.5 is looking for fileName (notice the capitalization). This crashes my build task.
For me, the problem was solved by replacing typescript in gulp-typescript/node-modules with an updated version.
Do you have plans to switch to v1.5 soon?

After the createProject call you can't modify the options any more. You should use the following:
var proj = typescript.createProject('src/tsconfig.json', {
  typescript: require('typescript'),
  sortOutput: true
});

I plan to use the latest stable release as the default compiler version, so when TS 1.5 is released, I will make that default.
Did that solve your problem?

Yes, it helped, thank you.
Has it always been like that? I think proj.typescript = require('typescript'); worked in previous versions (I haven't used tsconfig.json before).

I'm not sure whether it worked in previous versions, maybe it worked but that wasn't intentional. You can find the supported public api in the readme.


Resize for vertical slider

Issue description:  resizeTasks() is not fired  in the onResize method upon a vertical only window resize. For a vertical aligned slider this messes up the vertical offset.

What exactly is the issue you're encountering?
Right now the responsive options are only related to window width, so it doesn't make sense to check the window height changes. But if you want set the responsive options related to window height, I will consider add an option.

Not so much about responsive options, but about what happens on a window resize. With respect to a vertical slider, after the window resizes vertically the vertical offset is not recalculated and so the visible slide sits vertically out of line.

@ganlanyuan
I would actually need to change the axis when it heads down to mobile from vertical to horizontal. is that possible?

@rdoc101 Just added a fix
@viktorlarsson You may need to destroy it and rebuild again

@rdoc101 fixed in v2.7.0


dockerdigest w/ and w/o arch fetches different digests.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Default architecture is amd64 in documentation, I think updatecli should behave in the same way.
 sources:
   bookworm-slim-amd64:
     kind: dockerdigest
     spec:
       image: debian
       architecture: "amd64"
       tag: "bookworm-slim"

   bookworm-slim:
     kind: dockerdigest
     spec:
       image: debian
       tag: "bookworm-slim"

Results:
bookworm-slim
-------------
✔ Docker Image Tag debian:bookworm-slim resolved to digest index.docker.io/library/debian:bookworm-slim@sha256:d02c76d82364cedca16ba3ed6f9102406fa9fa8833076a609cabf14270f43dfc
DEBUG: empty changelog found for the source

bookworm-slim-amd64
-------------------
✔ Docker Image Tag debian:bookworm-slim resolved to digest index.docker.io/library/debian:bookworm-slim@sha256:6bdbd579ba71f6855deecf57e64524921aed6b97ff1e5195436f244d2cb42b12
DEBUG: empty changelog found for the source

Even I cannot find d02c76d82364cedca16ba3ed6f9102406fa9fa8833076a609cabf14270f43dfc on dockerhub for any arch. I do not know where is comming from.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- OS: mac Sonoma 14.2.1
- updatecli: v0.73.0

Anything else?
No response

More context on https://github.com/updatecli/updatecli/issues/1603
If an architecture is undefined, Updatecli retrieves the digest of the image index which can be used regardless of the architecture but if an architecture is specified then Updatecli retrieves a specific image digest.
You could try with the following manifest
name: Get digest
sources:
  all:
    kind: dockerdigest
    spec:
      image: ghcr.io/updatecli/updatecli
      tag: v0.73.0
  amd64:
    kind: dockerdigest
    spec:
      architecture: amd64
      image: ghcr.io/updatecli/updatecli
      tag: v0.73.0
  arm64:
    kind: dockerdigest
    spec:
      architecture: arm64
      image: ghcr.io/updatecli/updatecli
      tag: v0.73.0

Thank you so much.
Cool, I never heard it before.
doc misleaded me.

I open this pullrequest which I hope clarify the situation.
Those comments are used to generated both the IDE documentation and www.updatecli.io


Matcher binding on repeat elements is only working the first time the element is attached

I'm submitting a bug report

Library Version:
1.4.0

Please tell us about your environment:

Operating System:
Same issue on both OSX and Windows10

Node Version:
6.2.0

NPM Version:
3.8.9

JSPM OR Webpack AND Version
webpack 3.3.0

Browser:
all

Language:
ESNext

Current behavior:
Array repeat strategy is losing the matcher binding once the element is removed from the view. The function bound to matcher on repeat is only called when the element is rendered the first time. Once the parent element (element which contains repeat elements) is removed from dom (because of if binding/route change) and attached to the dom again, the matcher is not from here on.
Expected/desired behavior:

https://gist.run/?id=fe857a95d87d2f07bd5a8ee86e1fd15e
When the element is attached for the first time, scope has a matcher

When the element is attached again later, scope has no matcher

What is the expected behavior?
The function bound to matcher should be called everytime

I believe the culprit is
  _captureAndRemoveMatcherBinding() {
    if (this.viewFactory.viewFactory) {
      const instructions = this.viewFactory.viewFactory.instructions;
      const instructionIds = Object.keys(instructions);
      for (let i = 0; i < instructionIds.length; i++) {
        const expressions = instructions[instructionIds[i]].expressions;
        if (expressions) {
          for (let ii = 0; i < expressions.length; i++) {
            if (expressions[ii].targetProperty === 'matcher') {
              const matcherBinding = expressions[ii];
              expressions.splice(ii, 1);
              return matcherBinding;
            }
          }
        }
      }
    }

    return undefined;
  }

in https://github.com/aurelia/templating-resources/blob/master/src/repeat.js
This is removing the matcher expression from the viewFactory if it is found. But I guess viewFactory is cached and the next time the element is bound, the matcher expression won't be there

Should be fixed by this: https://github.com/aurelia/templating-resources/pull/372

I'm experiencing the same problem and it is not fixed by #372. The issues is that this line https://github.com/aurelia/templating-resources/blob/9d3be39948644990ba2755b3fb28b1a8329fb355/src/repeat.js#L227
removes the matcher expression from the view factory. So, if the parent view that implements the Repeater is removed from the DOM and then re-rendered, the second time _captureAndRemoveMatcherBinding is invoked, the expression has already been removed.

@Seebiscuit thanks for the explanation. I think its potentially is the issues. Probably it wont be hard to fix, can you help create a small repro for this?

Thanks for looking into this @bigopon. I made a minimal repro here: https://gist.dumber.app/?gist=fc7be8c1f018dab0029267501c8a7c9e.
To debug the issue, open DevTools and open aurelia-templating-resources.js. Drop a breakpoint on line 1244 (as of the date of this post, it should be pointing to https://github.com/aurelia/templating-resources/blob/9d3be39948644990ba2755b3fb28b1a8329fb355/src/repeat.js#L223
You'll notice that when the app first loads expressions is truthy. Then, if you toggle the component with the repeater, the next time the code breaks here expressions is no longer available.


Tidy defmt-decoder

This PR

moves the cfg-attributes from modules to crate root
rename mod logger to log

@jonas-schievink What do you think of the dissolving? I hope it reduces a bit of complexity in the imports and file structure.

bors r+


Don't use split when retrieving by stable_id for archived identifiers…

…, the ensembl library knows how to handle this now
Also, pass along the determined type of identifier to the Archive Adaptor since some identifiers can't be determined by regex (ie. C. elegans)

yeah to cleaner code :-)

Do I understand correctly that this will now make two DB calls for every versioned ID? It may be ok anyway I suppose.


mobx-react causes yarn warning about peer dependency

Yarn gives the following warning:
<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^3.0.0"
This happens when I run "yarn upgrace other-pkg".
It looks like<EMAIL_ADDRESS>should be ok with mobx ^4.0.0 also.

That is possibly incorrect indeed. But upgrading your deps will fix the
issue anyway, so I recommend to do that instead
Op vr 21 sep. 2018 om 15:15 schreef jbergens<EMAIL_ADDRESS>
Yarn gives the following warning:
<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^3.0.0"
It looks like<EMAIL_ADDRESS>should be ok with mobx ^4.0.0 also.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/558, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhORQX1ssIDE7MBUVBsoG7NXlMfShks5udOZcgaJpZM4W0IiV
.


Tab order

Love this plugin.
But Tab order is going down the columns, not across.  Any way to fix?

hey @mcyzyk sorry i haven't found the time to check in. I think this is an inherent flaw of columns (be it css columns or implemented with floats). It would probably take a very different approach based on css grid and some js or absolute positioning/transform to accomplish this. that is out of scope for this package.


Merge updates for 1.0.6

As noted in CHANGES.md:

Fixed md5 hash format (#25)
Added support for sha-1 and sha-256 hashes

Coverage decreased (-0.1%) to 86.543% when pulling 941cba41b189f8e6a5ec56ab7b729bbb23168405 on develop into 46e154375357dac9f7baa01f752ff0ce3453deb8 on master.


spectrum.spectrl2 calculates negative irradiance for angle of incidence outside +/- 90°

When using pvlib (but also the spectrl2 implementation provided by NREL), I obtain negative Irradiance for a north-facing panel.
From @kevinsa5 's reply on StackOverflow I take that this is in fact not intended.
In the example code below, the angle of incidence is calculated as values around 115°, so exceeding a possible (implicitly assumed) +/- 90° bound (sun behind panel).
This seems to be left open in the original report (Bird & Riordan, 1984).
The direct irradiance I_d (of a horizontal panel, Eq 2-1) is obtained by multiplying by cosine of the sun zenith angle. I'd guess that setting that value strictly to zero for angles when cosZ is negative would not be too much of a stretch.
Then, the direct irradiance I_d goes into (Eq 3-18):
I_T(t) = I_d*cos(aoi) + I_s * ( (I_d*cos(aoi) / (H_0*D*cos(Z)) ) + 0.5*(1+cos(t)) * (1 - I_d/(H_0*D)) + 0.5 * I_T0 * r_g * (1-cos(t))

As such, when you view the angle of incidence aoi as the analogue of the sun zenith angle in the prior example, the two first terms of the diffuse irradiation (Eq 3-18) would become zero, which - again - for the direct irradiance would kind of make sense. What remains of (Eq 3-18) would be
I_T(t) = 0 + 0 + 0.5*(1+cos(t))*(1 - 0) + 0.5*I_T0*r_g*(1-cos(t))

I'm not from the field, so I'm very, very wary about the implications of such a work-around suggestion. Can anyone with a proper background comment on this? (Maybe it's the future of air conditioning :-D)
MWE based on the tutorial below
## Using PV Lib

from pvlib import spectrum, solarposition, irradiance, atmosphere
import pandas as pd
import matplotlib.pyplot as plt

# assumptions from the technical report:
lat = 49.88
lon = 8.63
tilt = 45
azimuth = 0 # North = 0
pressure = 101300  # sea level, roughly
water_vapor_content = 0.5  # cm
tau500 = 0.1
ozone = 0.31  # atm-cm
albedo = 0.2

times = pd.date_range('2021-11-30 8:00', freq='h', periods=6, tz="Europe/Berlin") # , tz='Etc/GMT+9'
solpos = solarposition.get_solarposition(times, lat, lon)
aoi = irradiance.aoi(tilt, azimuth, solpos.apparent_zenith, solpos.azimuth)

# The technical report uses the 'kasten1966' airmass model, but later
# versions of SPECTRL2 use 'kastenyoung1989'.  Here we use 'kasten1966'
# for consistency with the technical report.
relative_airmass = atmosphere.get_relative_airmass(solpos.apparent_zenith,
                                                   model='kasten1966')

spectra = spectrum.spectrl2(
    apparent_zenith=solpos.apparent_zenith,
    aoi=aoi,
    surface_tilt=tilt,
    ground_albedo=albedo,
    surface_pressure=pressure,
    relative_airmass=relative_airmass,
    precipitable_water=water_vapor_content,
    ozone=ozone,
    aerosol_turbidity_500nm=tau500,
)

plt.figure()
plt.plot(spectra['wavelength'], spectra['poa_global'])
plt.xlim(200, 2700)
# plt.ylim(0, 1.8)
plt.title(r"2021-11-30, Darmstadt, $\tau=0.1$, Wv=0.5 cm")
plt.ylabel(r"Irradiance ($W m^{-2} nm^{-1}$)")
plt.xlabel(r"Wavelength ($nm$)")
time_labels = times.strftime("%H:%M %p")
labels = [
    "AM {:0.02f}, Z{:0.02f}, {}".format(*vals)
    for vals in zip(relative_airmass, solpos.apparent_zenith, time_labels)
]
plt.legend(labels)
plt.show()

Thanks @cweickhmann!  I want to take a closer look at the technical report to be sure, but on a first glance I think the problem here is the same one solved by the line marked with # GH 526 in irradiance.haydavies:
https://github.com/pvlib/pvlib-python/blob/aba071f707f9025882e57f3e55cc9e3e90e869b2/pvlib/irradiance.py#L811-L816
Note that, even though spectrum.spectrl2 uses irradiance.haydavies under the hood, the above branch is not hit because spectrl2 passes in a pre-calculated projection_ratio.  So I think clipping the projection to be non-negative before passing it to haydavies would solve the problem.  The # GH 432 line might be desirable as well, though I don't think it's relevant for this issue.
Does anyone have qualms about us deviating from the reference by implementing that fix and making a note about it in the docstring?  aoi > 90 is hardly an uncommon occurrence, even for arrays that aren't high-latitude and facing north.

deviating from the reference by implementing that fix and making a note about it

I support that.


Add layering for stacked tunnels

This image from lower Manhattan shows that stacked tunnels are a problem, in addition to stacked bridges:

The NYC example is no longer a problem, but I'm not sure if that's because it's a toll vs free overlap.  Is this still a problem anywhere?

Blocked by maplibre/maplibre-gl-js#2108

This example

This example in Sydney, Australia has values of layer going down to at least layer=-5:


Monitor Superset Performance

I don't find any articles or docs describing how we can monitor superset in production environment. So any help regarding how we can have matrix which we can use to monitor superset ?

Yes, we have deployed Superset in a production environment and as we have more users, it is becoming critical to monitor. Is there any future plan for exposing Prometheus metrics for Superset?

Superset uses statsd: https://github.com/statsd/statsd
You can find a number of metrics already there.
If you run it using gunicorn: https://docs.gunicorn.org/en/stable/instrumentation.html
As for machine / DB utilization: cpu, memory, disk, network  - that depends on how you run it, e.g. in AWS you'll have cloudwatch metrics.
Celery needs a bit of magic:

https://docs.celeryproject.org/en/stable/userguide/monitoring.html
https://medium.com/meilleursagents-engineering/how-we-monitor-asynchronous-tasks-da25728173d6

@bkyryliuk  I have used the following command in my superset_config file
STATS_LOGGER = StatsdStatsLogger(host='<IP_ADDRESS>', port=8125, prefix='superset')

Then i am using gunicorn
 nohup  gunicorn \
      -w 6 \
      -k gevent \
      --timeout 120 \
      -b  <IP_ADDRESS>:8088 \
      --limit-request-line 0 \
      --limit-request-field_size 0 \
      --statsd-host <IP_ADDRESS>:8125 \
      "superset.app:create_app()" &

AT   <IP ADDRESS>:8125 i am not seeing any metrics i am doing anything wrong here ?

@bkyryliuk  I am getting this error
gunicorn/instrument/statsd.py", line 127, in _sock_send
    self.sock.send(msg)
ConnectionRefusedError: [Errno 111] Connection refused

Thanks @bkyryliuk


Update Scala 2.12 to 2.12.1 (and other stuff)

Current coverage is 91.66% (diff: 100%)

Merging #33 into master will not change coverage

@@             master        #33   diff @@
==========================================
  Files             6          6
  Lines           144        144
  Methods         144        144
  Messages          0          0
  Branches          0          0
==========================================
  Hits            132        132
  Misses           12         12
  Partials          0          0

Powered by Codecov. Last update 63d1602...2bd39f3


Type narrowing for awaited values

Search Terms
promise, type narrowing, await

Suggestion
The type narrowing that occurs inside if statements, should work with awaited values
Though generally speaking a type is used for values that are already

Examples
type A = {
  kind: 'a'
  a: string
}

type B = {
  kind: 'b'
  b: string
}

let data: A | B

async function valueTest() {
  if ((await data.kind) === 'a') {
    // 'data' hasn't been narrowed to type 'A'
    data.a // Error
  }

  // Works fine without await
  if (data.kind === 'a') {
    data.a // Okay
  }
}

Checklist
My suggestion meets these guidelines:

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

This is due to #9998.

I think it's more that there's a limited set of syntactic constructs we can analyze because it would be inefficient otherwise. I guess the question I have is whether there's a reason to write code like that.

I guess this is the same issue that for-await-of doesn't narrow types?
/// <reference lib="esnext.asynciterable"/>

interface MyIterator<T> {
  next(): Promise<
    | {
        done: false;
        value: T;
      }
    | {
        done: true;
        value: undefined;
      }
  >;
  [Symbol.asyncIterator](): MyIterator<T>;
}
interface Item { name: string }

async function m(iter: MyIterator<Item>) {
  for await (const it of iter) {
    console.log(it.name);           // Error here complaining about 'it': Object is possibly 'undefined'.ts(2532)

  }
}

hmm, actually it is not related to await.  iterator has the same error
interface MyIterator<T> {
    next():
      | {
          done: false;
          value: T;
        }
      | {
          done: true;
          value: undefined;
        }
    ;
    [Symbol.iterator](): MyIterator<T>;
}

interface Item { name: string }

function m(iter: MyIterator<Item>) {
    for (const it of iter) {
        console.log(it.name);           // Error here complaining about 'it': Object is possibly 'undefined'.ts(2532)

    }
}

Now that #37610 has reverted the awaited type I don't know what to do I have posted an example below and my real-life situation is as follow :

I was relying on this solution because I have a Promise<MaybeList<Promise<ISymbolSearchResult[]>>>
where MaybeList is an array abstraction so I am using promise.all to remove the inner Promise I don't know what to do now to avoid using as unknown as MaybeList<ISymbolSearchResult[]> inside of my async function (which should be returning the Promise<MaybeList<ISymbolSearchResult[]>> instead of the Promise<MaybeList<Promise<ISymbolSearchResult[]>>>)

A copy of this problem in first explained in  #37526 is also in #33055 and in #33707 hoping it can be helpful
Update 2
I am not used to be working with thing so sensitive in a nightly version (thing added/removed that were solving my problems at the exact same moment they have been removed)...
My problem is back with the Revert 'awaited' type #37610    version of typescript but I will publish it here also in case it can be useful for something or someone

"typescript": "3.9.0-dev.20200326"

Update 1
My problem [was] solved with the nightly version of typescript [...]

"typescript": "3.9.0-dev.20200324"

Issue or problem description and example...
I have a similar problem and I don't know if I should open a different issue ...

"typescript": "3.8.3"

    // Promise.all(this.fork) take a T1[] where T1 is a Promise<number>
    // and return a Promise<T2[]> where T2 is a number
    // therefore T1 and T2 are not both «T»

export class MyMaybeList<T = any> {
  private constructor(values: T[]) {
    this.values = values;
  }

  private values: T[];

  // get =======================================================-| fork() |-====

  public get fork(): T[] {
    return this.values != null ? this.values.slice() : [].slice();
  }

  // public =====================================================-| map() |-====

  public map<R = any>(
    fn: (val: T, index: number, array: T[]) => R
  ): MyMaybeList<R> {
    return MyMaybeList.of(...this.values.map(fn));
  }

  // static ======================================================-| of() |-====

  public static of<TVal>(...val: TVal[]): MyMaybeList<TVal> {
    if (val == null || !val.length) return new MyMaybeList<TVal>([]);
    return new MyMaybeList<TVal>([...val]);
  }

  // async =====================================================-| will() |-====

  public async will /* <R> */() /* : Promise<MyMaybeList<R>> */ {
    // Promise.all(this.fork) take a T1[] where T1 is Promise<number>
    // and return a Promise<T2[]> where T2 is a number
    // therefore T1 and T2 are not both «T»
    console.log(this.fork);

    const willThen = Promise.all(this.fork);

    const thenWill = await willThen;
    return MyMaybeList.of(...thenWill);
  }
}

const oneToTen = MyMaybeList.of(1, 2, 3, 4, 5, 6, 7, 8, 9, 10);
const powersOneToTen = oneToTen.map(async val => val * val);

// "log->" powersOneToTen: MyMaybeList<Promise<number>>
console.log(powersOneToTen);

// "log->" awaitedList: MyMaybeList<Promise<number>>
// instead of a -> MyMaybeList { Promise<number> }
// in fact is a -> Promise {  MyMaybeList<number> }
const awaitedPowersOneToTen = powersOneToTen.will /* <unnknow> */();
awaitedPowersOneToTen.then(awaitedList => console.log(awaitedList));

// Promise { <pending> } will resolve into ->
console.log(awaitedPowersOneToTen);

/*
 // Promise.all(this.fork) take a T1[] where T1 is Promise<number>
    // and return a Promise<T2[]> where T2 is a number
    // therefore T1 and T2 are not both «T»
    // console.log(this.fork); will display same as console.log(powersOneToTen);

// console.log(powersOneToTen); ->
// "log->" powersOneToTen: MyMaybeList<Promise<number>>
MyMaybeList {
  values: [
    Promise { 1 },
    Promise { 4 },
    Promise { 9 },
    Promise { 16 },
    Promise { 25 },
    Promise { 36 },
    Promise { 49 },
    Promise { 64 },
    Promise { 81 },
    Promise { 100 }
  ]
}

// console.log(awaitedPowersOneToTen); ->
// "log ->" awaitedPowersOneToTen: Promise<MyMaybeList<Promise<number>>>
Promise { <pending> }
// Promise { <pending> } will resolve into ->

// awaitedPowersOneToTen.then(awaitedList => console.log(awaitedList)); ->
// console.log(awaitedList) ->
// "log->" awaitedList: MyMaybeList<Promise<number>>
// instead of a -> MyMaybeList { Promise<number> }
// in fact is a (should be) -> Promise {  MyMaybeList<number> }
MyMaybeList {
  values: [
     1,  4,  9, 16,  25,
    36, 49, 64, 81, 100
  ]
}
*/


Update the root readme to include clear acquisition and installation details.

Things left to do (out-of-scope for this PR):

Add FAQ section for common errors and potential solutions when trying to build via vcpkg
Structure the doc with the following groups, if there is not a lot of overlap:

Windows

Visual Studio
VS Code
Command Line

Linux/Posix/Mac

VS Code
Command Line

Another dimension is Vcpkg vs fetch content from GitHub vs build the SDK from source.

cc @kyle-patterson

/check-enforcer override

/check-enforcer override

@msftbot do not merge unless @RickWinter approves

@msftbot hold this pr for the next 1 hour

@ahsonkhan Is consuming SDK as a submodule supported scenario?

Is consuming SDK as a submodule supported scenario?

We plan it to be, and it might just work already, but I haven't tried it yet. It is a bit lower in the priority list. Do you know of any particular pitfalls to look out for or document that is unique to consuming as a submodule (which would be different from just building the SDK as source outside of the application repo)?

/check-enforcer override

@ahsonkhan Is consuming SDK as a submodule supported scenario?

Consuming as a submodule is not the mainline consumption scenario.  It may work but is not officially supported.
The reason for that is we do not expect all packages to ship on the same cadence.  i.e. Storage may ship 1.0 at the same time KeyVault ships the first Beta.  The folders within sdk directory are only verified stable at the release tags for each package (i.e. sdk/)

The reason for that is we do not expect all packages to ship on the same cadence.

Ah yes, good reminder Rick. Even if you submodule for a particular GA tag, it may contain libraries that are still in beta.


Image license - select list

Currently the license field in the Create specimen data object tool is free text - but @llivermore do we have a limited type of licenses the SDR will support (CC0, CCBY, CCNC for e.g.?)  In which case we should define these, and then change the field to a select list.

Following on from dicussion as today's meeting: Should we use the same licenses as GBIF?
According to this blog post https://data-blog.gbif.org/post/gbif-multimedia/ multimedia licenses are free text - CC0, CCBY, CCBYNC are for the occurrence data only.
But as per FAQs https://www.gbif.org/faq?question=can-i-use-the-images-i-find-via-gbif-org - "data providers includes the URLs of multimedia associated with the records they publish, which are then displayed on GBIF.org."
SDR is not just displaying images - creating derivatives etc., so I think we need an explicit license type.

I would avoid CCBYNC, as it is against open data principles so we cannot use that licence under DiSSCo. I think it was a mistake in GBIF to allow it, actually.


🚧Refactor WindowSizeEventArgs ctor param data types

I have done the items below . . .

[X] I have updated the title by replacing the '<title>' section.

Description
Refactor the data types of both the width and height constructor parameters and properties for the WindowSizeEventArgs class from int to uint.
This will of also force a change to be done in the unit testing file for this class in the WindowSizeEventArgsTests.cs file.
Refer to the changes below:
WindowSizeEventArgs.cs File Changes:
    /// <summary>
    /// Holds information about an event when a window resizes.
    /// </summary>
    internal class WindowSizeEventArgs
    {
        /// <summary>
        /// Initializes a new instance of the <see cref="WindowSizeEventArgs"/> class.
        /// </summary>
        /// <param name="width">The width of the window.</param>
        /// <param name="height">The height of the window.</param>
-        public WindowSizeEventArgs(int width, int height)
+       public WindowSizeEventArgs(uint width, uint height)
        {
            Width = width;
            Height = height;
        }

        /// <summary>
        /// Gets the width of the window.
        /// </summary>
-        public int Width { get; }
+       public uint Width { get; }

        /// <summary>
        /// Gets the height of the window.
        /// </summary>
-        public int Height { get; }
+       public uint Height { get; }
    }

WindowSizeEventArgsTests.cs File Changes:
        [Fact]
        public void Ctor_WhenInvoked_SetsProperties()
        {
            // Arrange
-            var eventArgs = new WindowSizeEventArgs(123, 456);
+           var eventArgs = new WindowSizeEventArgs(123u, 456u);

            // Act
            var actualWidth = eventArgs.Width;
            var actualHeight = eventArgs.Height;

            // Assert
-            Assert.Equal(123, actualWidth);
+           Assert.Equal(123u, actualWidth);
-            Assert.Equal(456, actualHeight);
+           Assert.Equal(456u, actualHeight);
        }

Acceptance Criteria
This issue is finished when:

[ ] Both constructor parameter data types refactored
[ ] Both properties updated
[ ] Unit tests updated accordingly
[ ] Code documentation added if required
[ ] All unit tests pass

ToDo Items

[ ] Draft pull request created and linked to this issue
[X] Priority label added to issue (low priority, medium priority, or high priority)
[ ] Issue linked to the proper project
[X] Issue linked to proper milestone
[ ] Unit tests have been written and/or adjusted for code additions or changes
[ ] All unit tests pass

Issue Dependencies
No response
Related Work
No response
Code of Conduct

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

I would like to work on this.

@SyedMSawaid You got it!!
Issue assigned and setup for you to work on.


SA1502: ElementMustNotBeOnSingleLine

http://www.stylecop.com/docs/SA1502.html

Grabbing this one.

Created pull request #547 for this.


Custom type Ref leaks

Ref of custom type T leaks if it is created from gdnative module.
Ref<A> a;
a.instance(); //leaks

Ref of Godot type T is freed correctly.
Ref<File> f;
f.instance(); //ok

Custom type instances created from gdscript are freed correctly as well.
var a = load('res://a.gdns').new() #ok

Update:
As a workaround I'm currently using a = Ref<A>::__internal_constructor(A::_new()); instead of a.instance which seems to work fine.

ugh that sucks, I use that a lot in procmesh...

Hey this is pretty a copy and paste comment from https://github.com/godotengine/godot/issues/24905
I've had memory leaks with assignment in GDNative, it seems like this issue is similar.
It has to do with = operator.
This is a problem:
void bug(Variant var) {
    // make_array returns an array with minimum two elements of Object type
    Variant arr = var.call("make_array", NULL, 0);
    Variant v = arr.call("pop_back", NULL, 0);
    Variant b = arr.call("pop_back", NULL, 0);

    // This here is the sequence that causes the problem
    Variant c; // This is okay
    c = v; // This is okay
    c = b; // This causes the memory leak
}

It seems like an issue that happens when c is an Object variable replaced by another variant.
So these also leak:
Variant c;
c = v;
c = Variant();
// ----
Variant c;
c = v;
c = v;

The issue is replacing a non-null Object-type Variant. This isn't an issue with Godot primitive types (int, string, bool, ...) or Godot basic types (Dictionary, Array, ...). This is an issue with objects you need to instantiate - References included, Objects instances of FuncRef (tested) or user defined classes (tested) cause memory leaks if they are v.
The only thing that seems to fix this right now is this:
Variant c;
c = v;
c.call("unreference", NULL, 0); // Remove a reference count
c = Variant();

But obviously this isn't satisfactory.

@karroffel I'm willing to try and fix this issue since it's extremely debilitating in my project, but I'm not sure where to start :/
I'm thinking it might be a problem with Ref.hpp (one of the copy constructors maybe?) - but I'm not certain and I wouldn't know which one based on my examples above.
For some reason (maybe after 3.1-stable) my workaround above doesn't work anymore, and memory leaks are rampant now in my project haha
When you get the chance, would you mind giving me some pointers on where you might think the problem is? Or where to start to look?
Thanks

I stumbled across the same problem. First I thought I did something wrong, because there is so little documentation. Then I found two workarounds. The first one is the same as the one from @bruvzg . The second is as follows:
Ref<A> a;
a.instance();
a->unreference();

But this is of course not ideal. Maybe I try to fix it myself.

It seems like the problem is that if you create a new instance of a custom type (that inherits Reference) like this A::_new() then refcount is 1 and refcount_init is 0, but refcount_init should also be 1. If you create a new instance of a build-in type e.g. ArrayMesh::_new() refcount and refcount_init are both 1 like it should be. This indicates that somewhere in the A::_new() call, a Ref of the new instance was created, which reduced the refcount_init to 0. My guess is, that line 499 in nativescript.cpp is the culprit. But of cause we can't change that without breaking everything. The easiest way is probably to add a reset function to the Reference class in the main godot project and to call it maybe from NativeScript::new_() in the godot-cpp project.

I encountered this issue as well, and the workaround with __internal_constructor still works - thank you for that! Before that, I was manually calling a.unreference() in Godot, which also worked but is much more cumbersome.
Possibly related: If I don't call init_ref() in my custom class' _init(), returning a reference to an object of this class throws a segfault.

I made a new PR that fixes the issue without the need for a reset_ref() function in Godot https://github.com/GodotNativeTools/godot-cpp/pull/408

Just merged it, let me know if that works for you now ;)

As of ~ 9eceb16f0553884094d0f659461649be5d333866 (i.e. after @Zylann's PR) the __internal_constructor() workaround should no longer be necessary and use of it may lead to crash, this should now work correctly:

Ref<CustomClass> ref = Ref<CustomClass>(custom_class_instance);

I've attempting to summarise the current state here: #417

Fixed by #408 (IIUC).


503 Errors

Running in docker.
level=error msg="status: 503 message: \r\n<title>503 Service Temporarily Unavailable</title>\r\n\r\n
503 Service Temporarily Unavailable
\r\n
openresty\r\n\r\n\r\n"
config.yaml looks like this (modified to hide details):
update_interval_minutes: 10

credentials:
  n:
    porkbun_api_key: pk1_...
    porkbun_secret_key: sk1_...

records:
  - domain: x.com
    host: A
    ipv4: true
    credentials: n
  - domain: x.com
    host: B
    ipv4: true
    credentials: n
  - domain: x.com
    host: C
    ipv4: true
    credentials: n
  - domain: x.com
    host: D
    ipv4: true
    credentials: n
  - domain: x.com
    host: E
    ipv4: true
    credentials: n
  - domain: x.com
    host: F
    ipv4: true
    credentials: n

I'm able to reproduce it. I'll work on this as soon as possible.


Fix from_bytes for WriteBid and WriteWithdraw variants of Transform

Fix FromBytes for WriteBid and WriteWithdraw variants of Transform
Currently, if you attempt to decode previously encoded WriteBid and WriteWithdraw variants of Transform, it would fail with a bytesrepr::Error::Formatting error. This commit properly decodes them, and introduces a convention for doing so in the future.

I just noticed a bug in the PR. Blocking pending the fix.

Merged your suggested change -- good catch. The CI stuff seems to be a repeated problem where my local toolchain is different from the one in CI, not sure what I should do to systematically fix it but I've been reading the CI scripts and invoking bits of them locally as my intermediate fix.

bors r+


[Bug]: Georeference direct coordinates not working

Steps to reproduce the bug
1. In Collecting Event page
2. Click on Georeference (0), and a map popup appears
3. Click on Enter Coordinates
4. Enter lat, long in decimal degrees, and "range distance"
   (BTW, this could be better labeled - I assume this is georef error in m)
5. Click Add
6. Long pause, then an error popup appears (see screenshot), and no point is saved

Screenshot

Expected behavior
A point with an error should be saved.
I also tried using "POINT ( )" in WKT and get the same errors.
I can enter a point using the visual map interface, but the coordinates of this cannot be editted manually.
Additional Screenshots
No response
Environment
Production
Sandbox Used
No response
Version
0.43.2
Browser Used
Firefox on Linux

@camwebb This is a correct validation, likely, that is ensuring the point you picked is inside the area you picked. From the error message you have selected a GeographicArea that is incompatible with the point.  If you wish to allow this incompatability then you need to check the "prefer Geographic Area" in the previous screen.

Ah... :smiley: I swear that yesterday I was trying to add a point within the geographic area (Nunavut, and tried Canada too), but today can't recreate the situation, and it's working well. Thanks for your attention.


RTDB transaction timeout

RTDB transaction timeout was removed.
Must be restored and documentation updated.

@alex9153
I don't see any reference for timeout being removed from plugin's changelog : https://pub.dev/packages/firebase_database/changelog
Can you please point it to me ? Also what issue are you facing without it ?

var transactionResult = await ref.runTransaction((mutableData) {
			return mutableData;
		}, timeout: Duration(seconds: 10));

timeout missing in latest version of firebase

Thanks for the update.
Using plugin's example, I see the same behavior:

So how to add timeout in 9.0.3 ?

The underlying implementation of Realtime Database does not support Timeout so we cannot support it on Flutter.
You can open a ticket on native SDK to request this feature.


Intermittent bosh agent client timeouts

We have been seeing intermittent timeouts in the agent client connection on recent versions of BOSH-lite (>= 9000.85). We see this manifest as the following behavior:

Deploy a 5-node cluster of the consul-release.
Change deployment to 3-node cluster.
Redeploy.
The deployment fails with either of these messages:

'Timed out sending drain'
'Timed out sending prepare'

When we look at the agent logs on the VMs that triggered the deployment, we see log lines like the following:
"2016-01-21_21:54:47.75061 [main] 2016/01/21 21:54:47 ERROR - App run Running agent: Sending heartbeat: Unresponsive client detected, connection dropped"
It then looks like the agent process on the VM restarted itself. If this were to have happened during a drain or prepare action, those actions would never be completed, thus leading to the timeout message reported by the director, and the resulting deployment error.
I have attached logs from two deployments that failed in this manner.
timeout-logs.zip

@ryanmoran can you include a manifest you are using so i can repro locally.

Here are a couple manifests. You can deploy the 5-node cluster, and then the 3-node cluster to scale down. We would see the issue manifest about 1 in 5 attempts.
yamls.zip

@ryanmoran The manifests has some keys and certs in them. Are these ok to be public?

@cheeseblubber yes. there are no secrets in that manifest. The keys and certs were generated and only used here in this issue.

@ryanmoran did you start seeing this issue starting from certain version of bosh-lite? What version was working for you?

@mariash we started seeing issues with 9000.88, but also continued to see issues after downgrading to 9000.85.

@ryanmoran garden team have found an issue (https://www.pivotaltracker.com/story/show/113553565). they are working to resolve it.

@cppforlife great. thanks for the fast response.

we believe this was resolved in https://github.com/cloudfoundry/bosh-lite/releases/tag/9000.105.0


Wait for NSX controller to be ready

Usually deployment of NSX (vm) is fast enough to be ready.
Ensure that the script will not break if it does take longer.
Note the:
Note: Waiting for the VM to boot...
Note: Ping result for nsxcon2
PING nsxcon2.cloud.lan (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from nsxcon2.cloud.lan (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.105 ms

--- nsxcon2.cloud.lan ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.105/0.105/0.105/0.000 ms

in this "test":
Note: You want to deploy a VM with role 'nsx-controller-cluster1'..
Note: VM name nsxcon1 is already in use
Note: VM name nsxcon2 is available
WARNING: nsxcon2: No firstboot script defined.
Note: nsxcon2: Running postboot script: /data/shared/deploy/postboot/post_nsx_controller.sh nsxcon1 nsxcon2
Note: Waiting for the VM to boot...
Note: Ping result for nsxcon2
PING nsxcon2.cloud.lan (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from nsxcon2.cloud.lan (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.105 ms

--- nsxcon2.cloud.lan ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.105/0.105/0.105/0.000 ms
Package sshpass-1.05-5.el7.x86_64 already installed and latest version
Joining cluster
Warning: Permanently added 'nsxcon2,<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Stopping nicira-nvp-controller: [Done]
Clearing nicira-nvp-controller's state: OK
Starting nicira-nvp-controller: CLI revert file already exists
ssh stop/waiting
ssh start/running, process 2597
ssh stop/waiting
mapping eth0 -> bridged-pif
mapping breth0 -> eth0
mapping breth0 -> eth0
ssh start/running, process 2768
Setting core limit to unlimited
Setting file descriptor limit to 100000
WARNING: Logging before InitGoogleLogging() is written to STDERR
D0209 14:31:07.134882  2891 info-file.cc:23] Created a InfoFile object for info_file: /var/cloudnet/data/controllerd.info
 nicira-nvp-controller [OK]
Clearing controller state and restarting
** Watching control-cluster history; ctrl-c to exit **
===================================
Host nsx-controller
Node 8fa10a0d-04dc-4e07-8dd3-4b0a305709d0 (<IP_ADDRESS>)
  ---------------------------------
  02/09 14:31:08: Joining cluster via node <IP_ADDRESS>
  02/09 14:31:08: Waiting to join cluster
  02/09 14:31:08: Joined cluster; initializing local components
  02/09 14:31:20: Initializing data contact with cluster
  02/09 14:31:20: Fetching initial configuration data
  02/09 14:31:22: Join complete

Nice one!


Just now created PR

Author please review my PR #6285

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

ID: fb5cd998-7919-6eb6-8198-0c3e90d76c56
Version Independent ID: 4e9c7668-62f6-912d-5354-bff400f591ac
Content: Microsoft Security Compliance Toolkit 1.0 Guide - Windows security
Content Source: windows/security/threat-protection/windows-security-configuration-framework/security-compliance-toolkit-10.md
Product: w10
Technology: windows
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@illfated .@e0i  . Please review PR #6285 .
https://github.com/MicrosoftDocs/windows-itpro-docs/pull/6285

Thank you for properly starting a new issue ticket to reference your PR with your recommended changes to this document.  That in itself is the proper way to go about unreported issues, especially if you are going to create a pull request to resolve the issue at hand.
What I am hoping for you to learn more about, as you progress in your work here in these Microsoft repositories, is to discover that there is a format and code style (although not broadcast or published particularly well for all users to be discovered. This is more of a general code style that you may need to learn as time goes by and you see what others use to describe their issue tickets and pull requests.
Anyway, since I have already suggested an improvement to your PR title, I would like to suggest an improvement to this issue ticket title as well.
Suggestion:
Microsoft Security Compliance Toolkit 1.0 : versions missing in the Security Baselines lists

@RAJU2529 Please do not create blank issues to draw attention to Pull Requests.


[integration_test] What is the difference between flutter test and flutter drive in flutter integration_test?

## Steps to Reproduce
In continuation of the issue raised in #117593. I could not run the takeScreenshot() method when using flutter test but the same runs when flutter drive is used
Logs when flutter test used:
package:flutter/src/foundation/binding.dart': Failed assertion: line 55 pos 12: '!_debugInitialized': is not true.
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:51:61)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:40:5)
#2      new BindingBase (package:flutter/src/foundation/binding.dart:55:12)
#3      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding (package:flutter_test/src/binding.dart)
#4      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding (package:flutter_test/src/binding.dart)
#5      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding (package:flutter_test/src/binding.dart)
#6      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding&SemanticsBinding (package:flutter_test/src/binding.dart)
#7      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding&SemanticsBinding&RendererBinding (package:flutter_test/src/binding.dart)
#8      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding&SemanticsBinding&RendererBinding&PaintingBinding (package:flutter_test/src/binding.dart)
#9      new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding&SemanticsBinding&RendererBinding&PaintingBinding&WidgetsBinding (package:flutter_test/src/binding.dart)
#10     new _TestWidgetsFlutterBinding&BindingBase&SchedulerBinding&ServicesBinding&GestureBinding&SemanticsBinding&RendererBinding&PaintingBinding&WidgetsBinding&TestDefaultBinaryMessengerBinding (package:flutter_test/src/binding.dart)
#11     new TestWidgetsFlutterBinding (package:flutter_test/src/binding.dart)
#12     new LiveTestWidgetsFlutterBinding (package:flutter_test/src/binding.dart)
#13     new IntegrationTestWidgetsFlutterBinding (package:integration_test/integration_test.dart)

Command used:
flutter test integration_test/test/<test_file_name>.dart --no-sound-null-safety -d emulator-5554
Code :
Code is the same as in the issue #117593

@RamyaAcharya
Please check Integration testing for more information.
Closing from here as this is more of a what-is question rather than a bug or feature request. Please see https://flutter.dev/community for resources and ask questions like this. You may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp.


Merge dependabot PR's

I keep forgetting to merge #28 and #32. Since I've already tagged 3 alphas at this point, I don't want to rebase on these PR's, and therefore I don't think these will make it into the old 1.x library. That's another good reason to deprecate that library at this point. And this might be a separate issue, but it could be a good time to set the main branch at the most recent alpha commit as well, to prevent confusion on the status of this library as a whole, as in https://github.com/farmOS/farmOS.js/issues/29#issuecomment-853277956 and other more recent issues.

Actually, I might just go ahead and do all this now, including a reset of the main branch onto the the 2.0.0-alpha.3 tag. @mstenta, any objections?

I think that makes sense! No objections.

Resolve by 3f0a27a.


add arch option

This change adds a new configuration variable to allow for branching the install on different architectures, since public/free github actions don't support aarch64 allowing for this kind of download would be helpful when trying to cross compile from x86_64-apple-darwin for aarch64-apple-darwin.

An alternative here would be to potentially add a configuration to specify the file name explicitly.

Instead of continuing down the path of hard-coding more and more data, I am working on a new method that pulls the assets from the LLVM releases on GitHub dynamically based on the version, platform, and architecture.
I have the code mostly finished and hope to complete and release it this week.
The idea is that there will be a new (optional) resolver option added to this action that supports two values:

legacy – the default value which enables the current logic for finding the URL to download
github – enables new logic that searches through the llvm/llvm-project releases using the GitHub API to find a matching asset for the specified version, platform, and architecture

This way the change will be backwards-compatible (since the legacy resolver will be used by default), but going forward I may release a v2 of this action that makes the github resolver the default (or requires an explicit resolver in the options).

I am curious how that might work with alternative sources, Ideally users would be able to supplement or overwrite the default URL to include other sources. For example, I've been maintaining a repo with releases of versions not currently available on llvm/llvm-project for my own needs. Are you expecting the source url to be configurable?

I've added v2.0.0 which adds an arch input (defaults to NodeJS's process.arch if not provided).
Most users shouldn't need to change anything to move from v1 to v2, see the above the link for what changed.


Missing redirection info

"Log creation and redirection" section does not have anything on redirection.

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

ID: fe69b3a9-896f-e189-0c2c-f87ff735df9c
Version Independent ID: 97c8549b-66ad-0a23-1971-784fb923042a
Content: ASP.NET Core Module configuration reference
Content Source: aspnetcore/host-and-deploy/aspnet-core-module.md
Product: aspnet-core
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @under3415 ... Thanks for commenting. "Redirection" in this context refers to redirecting console stdout and stderr output to disk (i.e., to a log file).
I'll try changing the first sentence. Perhaps, specifying "console output" instead of "log" in the first sentence will make what's being redirected clearer.


GPII-3909: Disable default version upgrade check

This PR disables GKE default version skew check to prevent undesired minor version upgrades, until GKE rolls-out 1.12 as a default across all regions.
Ticket will be created to re-enable this.

LGTM

Ticket will be created to re-enable this.

Link?

https://issues.gpii.net/browse/GPII-3913


[HOLD FOR #49931][$250]  Expensify card - Deactivated card re-appears again (occasionally)

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.50-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
**If this was caught during regression testing, add the test name, ID and link from TestRail:**https://expensify.testrail.io/index.php?/cases/view/3272221
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: expensifail account. Workspace with enabled Expensify card feature and added VBA.

Go to WS > Expensify card
Issue card for a user (Physical or Virtual)
Click on added card > Deactivate card > Deactivate

Expected Result:
Card disappeared
Actual Result:
Sometimes card re-appeared and user has to deactivate it again
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/ca2aa1e3-c9cc-40f6-8ffa-b188f8df3003
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021847105131344829604
Upwork Job ID:<PHONE_NUMBER>344829604
Last Price Increase: 2024-10-18

Issue OwnerCurrent Issue Owner: @abdulrahuman5196

@jliexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Hey, How can I get acess to solve this issues I have asked for various issues and some chats are discusses on slack and some on stackoverflow. I have send an email before couple of weeks but still not got any reply. Any other way to get reply faster or solve this issues ?

@abdulrahuman5196 @lanitochka17 from what I'm seeing, the cards are getting deactivated but there's a lag.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Sometimes card re-appeared and user has to deactivate it again
What is the root cause of that problem?
After we create a card, GetMissingOnyxMessages API is called and the queue is paused here and the CreateExpensifyCard's Onyx data is pushed to queuedOnyxUpdates. After the queue is unpaused, because there is no other write API in the queue, the Onyx above isn't updated to OnyxDB, and the queuedOnyxUpdates has old data.

https://github.com/Expensify/App/blob/d1f6190f6503fea55d16ca9e66ea7d70788bad23/src/libs/Network/SequentialQueue.ts#L34
That is why the added card isn't shown immediately after CreateExpensifyCard API is complete, it's only shown after  OpenPolicyExpensifyCardsPage API is called again.
After we deactivate the card, the queuedOnyxUpdates is updated to OnyxDB here which includes the old card data of CreateExpensifyCard API.
This is the RCA of this issue
What changes do you think we should make in order to solve the problem?
When the queue is unpaused here, we should update queuedOnyxUpdates to OnyxDB if numberOfPersistedRequests is 0
if (numberOfPersistedRequests === 0) {
    flushOnyxUpdatesQueue();
}

https://github.com/Expensify/App/blob/d1f6190f6503fea55d16ca9e66ea7d70788bad23/src/libs/Network/SequentialQueue.ts#L190
What alternative solutions did you explore? (Optional)

The same RCA with https://github.com/Expensify/App/issues/49931

Thanks @DylanDylann - will pop this issue on HOLD for now.

Still on hold

I'm making the backend PR ready for review: https://github.com/Expensify/Auth/pull/13168

@jliexpensify This issue has already been fixed
https://github.com/user-attachments/assets/4cc7725a-b811-4958-b5d5-0bdd5e9dbdb7

Nice, thank you! Lets close this out.


DOC-2123 add alerting rules endpoint, events

Addresses: DOC-2123
CRDB: (couldn't find in Jira)

Added new Alerting tools section to v22.1/monitoring-and-alerting.md, showcasing new metrics endpoint, including:

Accessing the new endpoint, configuring Alertmanager, configuring Prometheus
Expanded Events to alert on to include location of corresponding rules definition, some from old pre-defined yaml file, some from this PR.

Updated code examples to use latest Prometheus | Alertmanager values on v22.1/monitor-cockroachdb-with-prometheus.md
Fixed broken link on v21.2/monitoring-and-alerting.md

v22.1/monitoring-and-alerting.md |  v22.1/monitor-cockroachdb-with-prometheus.md | v21.2/monitoring-and-alerting.md

This change is


Results with public checkpoints

Running the evaluation in the following fashion:
./generate.py --model jkulhanek/augpt-mw-21 --dataset multiwoz-2.1-test --file predictions.txt
./evaluate_multiwoz.py --file predictions.txt --dataset multiwoz-2.1-test

I get inform and success results somewhat lower than what is reported in the paper (Table 1):

info: match: 0.8440, success: 0.6780
info: computing bleu
info: test bleu: 0.0000
info: test delex bleu: 0.1732

Is this to be expected? Is the jkulhanek/augpt-mw-21  checkpoint the same one used to obtain the results in Table 1?

There was a bug in evaluation in the original source code. We have a new version of the paper under submission.

Ok, I see. But the code is now up to date and I can assume I'm getting the right results?

Yes, the results are consistent with the original evaluation published by Budzianowski.

Thanks. And can I ask for a clarification on why responses are not lexicalized in generate.py? Does that also have to do with keeping the evaluation procedure consistent across works?

The generate script generates delexicalized responses to be evaluated by the MultiWOZ evaluation (which uses delexicalized responses). You can change this line or use interact.py script.

Thanks. I noticed one small thing while using the generate.py code - there is some randomness in the predictions made, which can be avoided by fixing the seed.
May I also ask whether it is standard in evaluation of dialog systems that when a new system response is predicted, it is conditioned on past gold standard system responses rather than past generated system responses? This appears to be the case in generate.py, but to me it seems more "fair" let's say, or more realistic to condition the generation on past generated  system utterances.

@jkulhanek , I also ran the evaluation script here (which is the official recommendation as stated here) and obtained the following results for the predictions of jkulhanek/augpt-mw-21:

====== BLEU ======
damd           16.71749836889923
uniconv        15.605802335898408
hdsa           15.56793789619695
lava           15.539192586808422
augpt          17.242521108846592
mwz22          17.013728423986837
====== SUCCESS ======
inform         {'total': 75.5, 'taxi': 100.0, 'attraction': 85.6, 'restaurant': 83.1, 'train': 96.6, 'hotel': 72.8}
success        {'total': 60.9, 'taxi': 68.7, 'attraction': 56.6, 'restaurant': 64.5, 'train': 78.2, 'hotel': 60.2}

Do you know where the mismatch in inform and success stems from?

@Tomiinek  can you please look into it?

Hello,
First, I have to say that I am not completely sure guys :slightly_smiling_face: There might be multiple factors.
The difference between the current and the very first numbers were caused by the approach to Venue updates (see the evaluation paper). I believe that the current difference is caused mainly by the method of Venue comparison, see these lines and the paper for more details.
The current AuGPT venue comparison (checking whether there exists any overlap between predicted and ground truth database results) is probably more compatible with the method used in DAMD, MinTL, etc., but the right and hopefully preffered method is the one used, for example, in MarCo (see these lines), i.e. checking whether the database results corresponding to current dialogue state are a non-empty subset of the ground-truth results.
Hope it helps :innocent:

Hi @Tomiinek, thanks for the pointers. I'll look into those! :)


per_sec in 0.17 shows too many digits

I'm trying the new 0.17 release and I noticed the {per_sec} output now uses f64. However, when trying to use it in a sample program it uses too much precision:
for example: TPS:<PHONE_NUMBER>244087/s

That's fair. What do you think about #313 as a fix?

looks good!

Thanks for the review!


mqttMsgReceived does not exist

I went through this out-of-order while things were changing, but it looks to me like there's a step that requires mqttMsgReceived which does not exist (at least not yet).
bx wsk rule create handleMQTTMessage mqttMsgReceived translateText
error: Unable to create rule 'handleMQTTMessage': trigger /mark.sturdevant_myspace/mqttMsgReceived does not exist (code 03ac15c407bf50360aba72e460e6f7a6)

Hey Mark,
Thanks for pointing that out, the "mqttMsgReceived" trigger gets created as a result of deploying the MQTT feed, I've adjusted the order in #34 , would you mind seeing if that updated README looks good to you?

@ljbennett62 , this was due to an error in the ordering of the README steps, and has been addressed updating the README to direct the user to run the "Deploy MQTT Feed" step before creating the "Cloud Function" rules.


Fix file paths do not match with new application name (HRConnect)

Fixes #115
Fixes #153

The coverage should not be an issue as these are logs, and only the string content was changed.
They were also not covered in the original code.


Make cloudwatch and tag semaphore concurrency configurable

Should resolve #82 if users pass high enough numbers for the new -tag-concurrency and -cloudwatch-concurrency flags, e.g. -tag-concurrency 1000 -cloudwatch-concurrency 1000

Thanks a lot!


support admin qos configuration for kcc

refine kcc framework to dynamically apply admin qos

 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.


Fix down_component for agentInfo view

Seangchan, thanks for spotting this issue.
In principle "down_components" has no usage for global workqueue. Though we could extend it - eventually - to also report possible problems with the threads.
If you prefer to keep this key around, then we just close this PR. Otherwise this would fix the problem.

Sigh, I noticed this global_workqueue doc uploaded to couch was also breaking reqmgr2 when pulling the list of teams, my bad :(
This should fix it.


Optimize calls to Array.apply() overloads with literal varargs.

In Scala/JVM, this optimization is performed by the cleanup phase, but it comes after our back-end, so we have to reimplement it ourselves.
We then also change some uses of Array.apply in Character.scala so that the new optimization can kick in.

Could you drop a short comment why our backend runs before cleanup?

Because we don't want any other stuff that cleanup does to happen. For example it rewrites reflective calls into actual calls to the Java reflection API, which is a big no no for us. Moreover, there are other phases before cleanup that we don't want, such as delambdafy.

Because we don't want any other stuff that cleanup does to happen. For example it rewrites reflective calls into actual calls to the Java reflection API, which is a big no no for us. Moreover, there are other phases before cleanup that we don't want, such as delambdafy.

Ah, yes sorry. I meant add it to the commit message. Currently it reads a bit strange, like we can't change when our phase runs. (cleanup's description also says "platform specific" or something the like, so it makes sense it doesn't run).

OK, I updated the commit message. Is it better?

LGTM


Update documentation on java agent

Hi! Want to do small addition to documentation about how to add java agent into the image.

Thanks! What kind of agent are you specifically thinking of? Or some general instructions for loading native agent libraries or Java agents?
BTW, we have an FAQ on configuring JDWP debugging, if that's relevant here.

@chanseokoh Its similar, yes. But I've thought it's still worth to have it that it will save some time for others.
Please check my draft PR https://github.com/GoogleContainerTools/jib/pull/1540

Closed by #1540.


Dev: Web - Console error Provide a valid string for accessibilityLabel prop

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any money request report.
Click on the amount such that the edit amount screen opens up.

Expected Result:
No console error
Actual Result:
Getting the console error:
Warning: Failed prop type: Provide a valid string for accessibilityLabel prop when accessible is true
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: Dev:
Reproducible in staging?: n/a
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @allroundexperts
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1692300040853639
View all open jobs on GitHub

I'm unable to repo this.

Alright, closing.


VIN search needs completing

Current VIN search uses the original ePer files.  Would be better if these were moved on to DB.  Also need to parse out properly the model specific data from the VIN files.

Resolved by recent checkins


DAO: more details

I liked what we did in the #1485 button, maybe we do something similar or whatever you guys believe is best.

The more details part was removed from the card and was added in the form of a button that leads to the more details route.

verified on devnet
version : 5c12959
the more details is removed and a button for the details was added and changed in UI.
opening another issue for devnet redirecting leads to a non existing page.

https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=422339#case_4250546


upload issues with boring-nginx and nextcloud 11.0.2

I know I am not on the latest version but I had the same issues with nextcloud 10 too. I will try and update to nextcloud 12 towards the weekend but I doubt that will fix the issues.
The problem is the issues are intermittent so I am struggling to figure out the cause.
We are using both your containers on a hosted server and for all these tests I am using the same nextcloud user. The max upload size is set to 10G.

from home, uploading a 160MB file works with FF and Chrome
from work,, uploading a 160MB file works with Chrome only (same browser versions as above and there is no outgoing Firewall/Proxy in use)
a client, from inside his corporate network, can't upload a 160MB file with any browser.

For the test I log on with the client credentials and create a folder. "Sometimes" I then try to enter the folder to upload and I get: "Operation not permitted" and am not able to enter this folder I just created. Logging onto another computer with the same credentials I can enter the folder.
When the 160MB file fails to upload, the upload is aborted with the error: "Connection to server lost".
Any idea what to look into? The nextcloud logs rare not showing any irregularities and neither does the nginx log.

Can you please post your boring-nginx conf?
You need to set client_max_body_size 10G; in this config.

OK; so this is the vhost file:
server {
  listen 8000;
  server_name portal.mydomain.tld;
  return 301 https://$host$request_uri;

  client_max_body_size 0M;
}

server {
  listen 4430 ssl http2;
  server_name portal.mydomain.tld;

  ssl_certificate /certs/portal.mydomain.tld.pem;
  ssl_certificate_key /certs/portal.mydomain.tld.key;

  #include /etc/nginx/conf/ssl_params;
  include /etc/nginx/conf/headers_params;
  include /conf.d/extra.conf;

  client_max_body_size 0M;

  location / {
    proxy_pass http://nextcloud-11:8888;
    include /etc/nginx/conf/proxy_params;
  }
  location /.well-known/ {
        root /www;
  }

error_log /var/log/nginx/portal-error.log;

}

the included extra.conf which cobbled together to solve various problems, probably introducing more in the process:
ssl_protocols  TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
ssl_prefer_server_ciphers on;
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Proxy "";
proxy_set_header Connection "upgrade";
proxy_buffer_size               8k;
gzip                            off;

I hope you can spot something. As far as I remember, the SSL stuff I had to change as some people using older browsers had trouble connecting to nextcloud. the other stuff I can't remember but it was all to solve various issues.

@ovizii as hoellen said. In you config file the client_max_body_size is set to 0M.
Please change both lines with:
client_max_body_size 0M;
to
client_max_body_size 10G;

Thanks. I will do so and let you know how things go. I have set it to 0 because according to nginx dos that is the same as unlimited. => http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
I'll post back later this week after testing it with "10G"

Unfortunately this change had absolutely no effect. I changed these 2 values then restarted the nginx proxy container and tried the same scenario as initially described but got the same failure message as described above.


Globals are not accessible in a service worker

Describe the bug
The global variables described in the define section are not available in the serviceworker
Reproduction
https://github.com/budarin/vite-sw-globals
Steps to reproduce

run dev
to see in console an error in the service worker that a global variable named VERSION is not defined

System Info
System:
    OS: macOS 12.7.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
    Memory: 44.45 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 22.3.0 - ~/.nvm/versions/node/v22.3.0/bin/node
    Yarn: 1.22.18 - ~/.yarn/bin/yarn
    npm: 10.8.1 - ~/.nvm/versions/node/v22.3.0/bin/npm
    pnpm: 9.5.0 - ~/.nvm/versions/node/v22.3.0/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.127
    Edge: 126.0.2592.102
    Safari: 17.5
    Safari Technology Preview: 16.4
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1
    vite: ^5.3.4 => 5.3.4

Used Package Manager
pnpm
Logs

Click to expand!
[vite] connecting...
client:614 [vite] connected.
index.mts:1 Uncaught ReferenceError: VERSION is not defined
    at index.mts:1:24
(anonymous) @ index.mts:1
localhost/:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('http://localhost:3000/src/sw/') with script ('http://localhost:3000/src/sw/index.mts'): ServiceWorker script evaluation failed

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Vite relies on /@vite/env module during dev to inject define to runtime, but new URL("...". import.meta.url) js assets alone doesn't trigger such injection. Manually writing import "/@vite/env"` seems to work for the provided reproduction.
Since Vite doesn't support service worker out-of-the-box https://github.com/vitejs/vite/issues/2248, there's no expected behavior for this situation, so I think we can close this in favor of #2248.


Buy now stops working after a few redirects

Was wondering why explorer tests were failing on github actions and encountered the following bug:
https://github.com/kodadot/nft-gallery/assets/36627808/d299f0a6-9ab6-4e2b-a6b4-7a2dfc15af67
to reproduce:
past this on the browser till it happens:
https://canary.kodadot.xyz/ahk/explore/items?page=1

👋


Added "start_index" attribute in the assign_ugrid_topology function

Also added some of the other possible topology variable, etc.
Now we should be able to use the start_index attribute in the subsetting code, rather than having to assume or infer it.

This is great, the only issue is when the node or face variables are large, and pulling them ahead of time also means we have to pull them later so there may be a performance hit if not used wisely. I should doucment everywhere data is pulled and accessed in the docs


fix(core): made v-if work again

Sounds promising 🔥:

[x] LightHelpers
[x] OrbitControls
[ ] Groups


Automated Package Upgrade

:tada: This PR is included in version 25.3.73 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


JavascriptChannel not working for Android but working fine for iOS

I am using the webview_flutter package and calling the JavaScript Interface which was defined at server side.
It works fine for iOS, but doesn't work for Android.
This is the code which I've used
               WebView(
                    navigationDelegate: (action) {
                      return NavigationDecision.navigate;
                    },
                    javascriptMode: JavascriptMode.unrestricted,
                    javascriptChannels: {

                      JavascriptChannel(
                        name: 'goToHome',
                        onMessageReceived: (JavascriptMessage response) {
                          print('goToHome');
                          Navigator.pop(context);
                        },
                      ),
                      JavascriptChannel(
                        name: 'backToLobby',
                        onMessageReceived: (JavascriptMessage response) {
                          print('backToLobby');
                          Navigator.pop(context);
                        },
                      ),
                    },
                    onWebViewCreated: (WebViewController webViewController) {
                      _controller = webViewController;
                      _controller.loadUrl(Uri.parse(finalUrlString).toString());
                      log(finalUrlString);
                    },
                    onPageFinished: (url) {},
                    debuggingEnabled: true,
                    onProgress: (progress) {
                      setState(() {
                        this.progress = progress / 100;
                      });
                    },
                  )

This is the build.gradle
defaultConfig {
        applicationId "com.example.sabanzuri"
        minSdkVersion 20
        targetSdkVersion 30
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
    }

This is the server-side code for JsInterface:
appLobbyBack() {
    if (typeof Mobile != 'undefined' && typeof Mobile.goToHome == "function") {
      Mobile.goToHome();
    } else if (typeof JSInterface != 'undefined' && typeof JSInterface.backToLobby == "function") {
      JSInterface.backToLobby();
    } else if (typeof webkit != 'undefined' && typeof webkit.messageHandlers.goToHome != 'undefined') {
      webkit.messageHandlers.goToHome.postMessage("event from Angular Iframe");
    }
  }

Flutter Doctor output:

Thanks for the report.

doesn't work for Android.

What exactly is meant by doesn't work ? Looking at the code and usage of JavascriptChannel, is navigation not working ?
Does this happen in debug or in release mode ?  Do you get any error in console when it doesn't work ?

Hey @darshankawar !
Thanks for the response. We debugged and found out it was an issue from server side javascript.
They added this in server-side code.
 if(typeof goToHome == 'object') {
      goToHome.postMessage("");
    }

And things started to work.


MB-11326 Add functionality for labeled data in the move history

Jira ticket for this change
Summary
Add in a new component that shows things by labels.
Remove all the labeled tests for now since they'll be added as the corresponding
tickets are worked
Add in mappings of database values to names, and names to how it should be displayed
in the move history
I am not confident that the below steps are the right way to test these changes.
i.e. I don't know what updating a move task order looks like.
Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the UI locally.
make office_client_run

Terminal 2
Start the Go server locally.
make server_run

Additional steps

Access the office app
Login as a TOO
Go to the Move task order page. (This might work best with a move that has an NTSR shipment.)
Edit some items in the Move task order.
Go to the Move history tab.
There should be some labeled fields and values changed.

Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output

Screenshots

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - Path Traversal: 'dir/../../filename' in moment.locale
Package moment
Patched in >=2.29.2
Dependency of moment
Path moment
More info https://github.com/advisories/GHSA-8hfj-j24r-96c4
1 high vulnerabilities and 0 critical vulnerabilities found

Messages

:book:
:link: MB-11326

  Generated by :no_entry_sign: dangerJS against 2dff0bfb1e3bf141e5bf13b4f8ee2c2616cfe5ce


ETIMEDOUT ETIMEDOUT

connect <IP_ADDRESS> 2376

It sounds like your VM has lost it's connectivity

This issue still cannot be fixed by restart docker machine. I don't know what happened.

@faisontw you may need to regenerate your certificates
docker-machine regenerate-certs default


Make React Tutorial use Hooks

Description
At present, the React section in Front End Library Certification is using Class Components.
But since hooks are the new way of doing React and more people are adapting to Hooks, I suggest including Hooks in the program.
Also, I think for beginners hooks will be easier and welcoming to the React world.

Yes, I was just thinking the same. I would love to contribute to including Hooks.

@RandellDawson is the best person to guide here.  My understanding is that we'd love to include lessons with modern React concepts, but that we will be adding them in the upcoming curriculum, rather than the current one.

If the team is planning to add this to the upcoming curriculum, I would suggest doing that as soon as possible, as the frameworks are regularly being updated the new curriculum also may get irrelevant soon. Also as @JimmyJoo said I also would love to contribute to include hooks.

Hello there ! I'm a  junior developer ( I've learned a lot from you website and would love to give back )
I'm confident I can learn a lot by making the change from class component to hooks in your react tutorial, how can I get going ? ( first time collaborating ! 🎊 )

Hello there ! I'm a junior developer ( I've learned a lot from you website and would love to give back )
I'm confident I can learn a lot by making the change from class component to hooks in your react tutorial, how can I get going ? ( first time collaborating !  )

@ludocourbin We are going to leave the existing class component lessons as there are still many code bases out there that use them still.  We will be incorporating new lessons in our project-based curriculum that is currently being built by staff.  We might post some GitHub issues around this in the future, but for now, you can take a look at any outstanding issue that has a help wanted label.  Looking forward to your contributions!

Hello @RandellDawson, I'll go on and explore the issue with the corresponding tag as you mentioned. Thank you for your answer.

@ludocourbin If it is your first time contributing, you'll find the contribution docs very useful. Happy coding!

Thank you @Twaha-Rahman for you helpful recommendation 😁

as far as i can see - react version need to be upgraded first (16.4 has no support for hooks)

Thanks for the input, we will not be adjusting the existing challenges this much anymore in favor of the project based curriculum in the works. Thanks and happy coding 🎉


Voice Attack & EDDI will CTD with FSD Drive

It is a Google translation. I am sorry that I am not good at English.
I am using the EDDI plugin.
When entering EDDI Jumping with FSD Drive, Voice Attack will CTD.
It happens many times when CTD happens, but never happens when it does not happen.
My friend has no problem at all with the same setting, but what is the cause of the problem?
Please let me know how EDDI Jumping will not be CTD.
I use Windows10 Anniversary ver.

Please could you do the following:

remove %APPDATA%\EDDI\eddi.log
start EDDI standalone (not from VoiceAttack)
enable the 'Enable verbose logging' option on the first tab
jump (at this point you say EDDI crashes)
restart EDDI standalone
press the 'Send EDDI log to developers' button
respond on this thread to let me know

Thaks

As I'm also experiencing this, I thought I'd step in and say that my log was just uploaded as per the instructions above. Cmdr Viridol if it is of any help finding it.

@Viridol Thank you for the log, however I don't see anything in there that suggests a jump from one system to another.  Please could you try again, and let me know which system you jumped to and from, and at what time?  Thank you.

Oh, strange! All right, sorry for the delayed response. Submitted another and the jump was from LTT 17868 to Breksta.
I might also add the same crash is occuring frequently outside of jumping, but unpredictably as far as I can tell. A system jump is just a reliable way to reproduce it.

Apologies, but it looks like my instructions were incorrect.  If you could please do it again, but this time enable verbose logging then restart EDDI, then jump, it should catch the required information.

Makes sense! I was wondering about how it didn't seem to generate a new eddi.log. :P
Right-o, guv. This time from Breksta to LTT 17868.

There's nothing in the log that suggests why the crash occurs, which in itself is odd.  The best I can come up with is that it's totally outside of EDDI, which points to the speech synthesis layer.
Do you have a different voice you can try?  I have heard of other users crashing with Salli, and was never able to track it down, but it might be a bug in the voice itself.

Huh. Yes, Microsoft Zira and David perform fine, while my Ivona voices (Salli, Amy, and Ivy) all exhibit this crash.
What's especially weird about that to me is that there were no crashes the first day using Salli, at all, with over 40 jumps. This got me thinking about just reinstalling the Ivona packs, but no dice there. Curious...
Anyway, thank you for the help!

Ah! So, interesting find:
Checking "Disable Phonetic Speech" in EDDI appears to make the IVONA voices happy, though it sure does cripple their excellent pronunciation. Still, I was considering it very strange that it seemed fine using phonetic speech it for so long before, and...
Turns out that it's apparently all about the ship I'm flying! I remembered that I switched from an Adder to a Cobra Mk. III the other day, and so by switching around the "Ship for testing voice" option in EDDI, I found that as long as "Disable phonetic speech" is not checked, it crashes when asked to test anything with "Mk." or the Fer-de-Lance.
Adding these terms to its lexicon doesn't seem helpful, though, so I'm inclined to just go into the EDDI personality and replace all the {ShipName()} with "ship" or something.

The way that phonetic speech is handled has been altered in EDDI 2.3 (currently in beta).  Please give it a try and see if this fixes your issue.