move origin to top-left text draw failed

When I use SetView(canvas.Identity.ReflectYAbout) text draw result

useSetCoordView can draw right, but other draw can't draw right, ↓ background draw out of canvas

var fontLoadSlice = []string{
	".SF Regular",
	"Arial",
	"Droid Sans",
}
var fontFamily *canvas.FontFamily
	fontFamily = canvas.NewFontFamily("times")
	for _, fontName := range fontLoadSlice {
		err := fontFamily.LoadLocalFont(fontName, canvas.FontRegular)
		fmt.Println(err)
		if err == nil {
			break
		}
	}
	headerFont := fontFamily.Face(28.0, canvas.Black, canvas.FontRegular, canvas.FontNormal)
	c := canvas.New(500, 200)
	ctx := canvas.NewContext(c)
	ctx.SetView(canvas.Identity.ReflectYAbout(100))
        //ctx.SetCoordView(canvas.Identity.ReflectYAbout(100))
	ctx.SetFillColor(canvas.White)
	ctx.DrawPath(0, 0, canvas.Rectangle(c.Size()))
	//ctx.SetStrokeColor(canvas.Black)
	//ctx.DrawPath(10, 10, canvas.Rectangle(480, 180))
	headerText := canvas.NewTextBox(headerFont, "test", 0, 0, canvas.Justify, canvas.Justify, 0, 0)
	ctx.DrawText(30, 30, headerText)

Yes, this may not be the easiest for people who'd like to work with top-left as the origin, but SetCoordView or SetCoordSystem should be used to change the coordinate transformation to position elements (but not transform the elements themselves) while SetView transforms the complete view. The former allows you to position the elements with top-left as the origin, but the elements themselves (a path for example) will always have bottom-left (the mathematical standard) as its origin. That is, you define the path with a bottom-left origin, and then you can position it using with top-left as the origin.
I'm thinking of changing this system, by introducing a CartesianIVContext for example that draws everything Y-flipped except for text. Additonally, it would be possible to add a PolarContext for polar coordinates etc.

Is this a duplicate of #72 ?

Yes it is! I will close this one. As mentioned in the other issue:
I've added a change that adds better support for CartesianIV (i.e. origin is top-left). It differs from CartesianI (i.e. origin is bottom-left) in that it anchors differently to images (anchors top-left vs bottom-left) and that text has always been anchored to the baseline (TextLine) or to top-left (TextBox) and remains so. This means that switching to CartesianIV may change the position of text and images.
You can change to CartesianIV using:
ctx.SetCoordSystem(canvas.CartesianIV)


Newsletter 13: Akigi

@chinedufn r? Should something be changed or added? :)
Part of #232  ("Newsletter 13")

:timer_clock: Merging in a few hrs if there're no objections.


Ruapu Java binding

Java’s Ruapu binding build by Gradle(@LinHeLurking ). Tested on Win, Ubuntu, and MacOS(@MollySophia )

Thanks for your contribution !


Stringify

I would love to be able to edit the parsed object and then stringify it back to CSS.

Or does this already exist? I noticed there's a ton of functions prototyped/exposed on the global.cssjs = fi;
There may need to be a README update, or additional documentation added.
Maybe utilize something such as ESDoc.

Digging into the source I've found this nifty functions to help me with what I was already trying to do:
      const CSSJS = require("css.js");
      //initialize parser object
      const CSS = new CSSJS.cssjs();

      let parsed = CSS.parseCSS(styling);
          parsed = CSS.applyNamespacing(parsed, prefix);
      let css = CSS.getCSSForEditor(parsed);

That's exactly what I need it for, thanks!
I couldn't see any tests for applyNamespacing()

Actually, just an addendum on this @ctsstc
You could call applyNamespacing(myCss) without calling parseCss because the namespacing method checks if you're passing a string and calls parseCss for you (see around line 557 of the unminified file)


Image Built

which program i am  able to build the Bytearray for the Image ?
Thx. Det

Hi, what worked fine for me was sth like:
 from PIL import Image
 im = Image.open('file.png', 'r')
 with open('binary.out','wb') as out: ## Open temporary file as bytes
     out.write(im.convert('1').tobytes())

In case the resolution matches your Micropython code could then just use that to display the image:
 with open("binary.out", "rb") as file:
      buf = bytearray(file.read())
      file.close()
      e.display_frame(buf)


Test suite unhandled promise rejection

Describe the bug

There is an unhandled promise rejection within the test sutie for intToBytes that does not cause the CI to fail.
Expected behavior

The CI should fail, and the test should probably also fail.
Steps to Reproduce

yarn install
yarn test

Screenshots

  intToBytes
    ✓ should correctly serialize number to bytes length 1
    ✓ should correctly serialize BN to bytes length 1
    ✓ should correctly serialize number to bytes length 2
    ✓ should correctly serialize BN to bytes length 2
    ✓ should correctly serialize number to bytes length 3
    ✓ should correctly serialize BN to bytes length 3
    ✓ should correctly serialize number to bytes length 4
    ✓ should correctly serialize BN to bytes length 4
    ✓ should correctly serialize number to bytes length 8
    ✓ should correctly serialize BN to bytes length 8
    ✓ should correctly serialize number to bytes length 32
    ✓ should correctly serialize BN to bytes length 32
    ✓ should correctly serialize number to bytes length 48
    ✓ should correctly serialize BN to bytes length 48
(node:67078) UnhandledPromiseRejectionWarning: Error: network does support ENS (operation="ENS", network="unknown", version=4.0.27)
    at Object.throwError (/Users/gregmarkou/Jobs/code/github.com/ChainSafe/lodestar/node_modules/ethers/errors.js:76:17)
    at /Users/gregmarkou/Jobs/code/github.com/ChainSafe/lodestar/node_modules/ethers/providers/base-provider.js:1007:24
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:67078) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:67078) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Desktop (please complete the following information):

OS:  OSX
Branch:  Master

That error is thrown from ethers.js when contract isn't found, I've looked into when building cli, it's actually ethers.js error which cannot be easily caught in our code other than hack like this:
process.on('unhandledRejection', error => {});

https://github.com/ethers-io/ethers.js/issues/189

But why is it being thrown in the middle of the test suite?

I'm not 100% on this, but I think mocha executes before of each describe before running it so my guess is that it happens in some before hook and since it's async it get's thrown in the middle of test execution. I might be wrong, that's my guess.

Do you know the specific test that's causing it? Perhaps we can make it async if possible?

Comment out ethers.test.ts and error will be gone. It happens there because contract address is TBD:
https://github.com/ChainSafe/lodestar/blob/master/test/unit/eth1/ethers.test.ts#L16

I can easily fix tests by using sinon to stub Eth1Notifier constructor, but the error is quite annoying since it cannot be catched (it's thrown inside ethers.js contract constructor, so I think we should add checker is contract exists before initiating ether.js contract constructor

We can hardcode the contract Address if we wanted to.
Assume its always deployed by the same mnemonic at nonce 0 (or 1? not sure what default is) then the address will always be the same

No need, since those are unit tests and they don't actually listens on smart contract events (deposit contract is not even deployed). We just need to skip constructor execution in Eth1Notifier. As for integration tests, I've already setup contract deployment and it uses deployed address.
But if someone is going to use cli and input wrong contract address or connects to wrong network, they will receive this misleading error unless we check for contract before ethers.js.

hmmm i see what you're saying - makes sense. I'm thinking for the tests though, if we need to do tests we can standardize that contract address

if we need to do tests we can standardize that contract address

We already solved it like this:
https://github.com/ChainSafe/lodestar/blob/master/test/unit/eth1/deploy.ts#L25

mmm yeah that always works too


Issue 309 adrenal hormone replacement

adding adrenal replacement and adrenal suppressant therapies. Holding off on the whole hormone replacement therapy revision, which will be tackled at a later time. #309


PCB Improvements

[x] - Fix orientation of right angle fan headers (current solution is use to vertical mounting ones and follow schematic for pin placement)
[x] - Add reset button so the Pico can be reset without removing the molex
[x] - Design CH340g circuit and have it presoldered on the PCB as an alternative to using a USB-TTY dongle
[x] Thicker traces to avoid damaging the PCB as easily

PCB in production, files in #39


[BUG]: Azure devops pipeline does not pass variables to stages

New issue checklist

[x] I searched for existing GitHub issues
[x] I read pipeline troubleshooting guide
[x] I checked how to collect logs

Task name
No response
Task version
No response
Issue Description
We want to create variable in the build stage and use the variable in all deployment stages.
We are able to create variable in the first stage, and pass it to the dev environment. But we are not able to pass the variable from either build stage to the 3rd stage (test) nor from the deployment to dev stage to deployment to test stage.
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[x] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
ubuntu
Relevant log output
2024-11-25T17:19:36.8830621Z echo "Received variable from Dev: "

Full task logs with system.debug enabled

[build-variable.txt](https://github.com/user-attachments/files/17906739/build-variable.txt)
[deploy-to-dev.txt](https://github.com/user-attachments/files/17906740/deploy-to-dev.txt)
[deploy-to-test.txt](https://github.com/user-attachments/files/17906741/deploy-to-test.txt)

Repro steps
trigger:
- none

stages:
- stage: Build
  displayName: Build Stage
  jobs:
  - job: BuildJob
    displayName: Build Job
    steps:
    - script: |
        echo "##vso[task.setvariable variable=myVar;isOutput=true]Hello from Build"
      name: OutputStep

- stage: DeployDev
  displayName: Deploy Dev Stage
  dependsOn: Build
  variables:
    myVarFromBuild: $[ stageDependencies.Build.BuildJob.outputs['OutputStep.myVar'] ]
  jobs:
  - deployment: DeployJob
    displayName: Deploy to Dev
    environment: "Dev"
    strategy:
      runOnce:
        deploy:
          steps:
          - script: |
              echo "Received variable from Build: $(myVarFromBuild)"
              echo "##vso[task.setvariable variable=myVarDev;isOutput=true]$(myVarFromBuild)"
            name: SetOutputForDev

- stage: DeployTest
  displayName: Deploy Test Stage
  dependsOn: DeployDev
  variables:
    myVarFromDev: $[ stageDependencies.DeployDev.DeployJob.outputs['SetOutputForDev.myVarDev'] ]
  jobs:
  - deployment: DeployJob
    displayName: Deploy to Test
    environment: "Test"
    strategy:
      runOnce:
        deploy:
          steps:
          - script: |
              echo "Received variable from Dev: $(myVarFromDev)"

Is there any timeline to fix this bug?

We are also experiencing the same issue described here by @scholtz

@ericsciple @davidstaheli @DmitriiBobreshev Is there some way how to work with this? My goal is to build applications using build pipelines, and then deploy 10 applications at once to the test environment. When they are properly tested they should be deployed to prod environment. However this does not work as in the prod environment we dont have proper build info if something else was built meanwhile.. This seems to be so basic functionality that either we are missing some basic config or the azure pipelines has serious critical bug.
Btw we can solve this using the release pipelines, however there is bad management of the source of the pipes and we would like to prefer to use the build pipelines as it seems to be the future.

Build to DeployTest

You need to explicitly add a dependency on Build stage for the variables to be accessible. Ref : FAQ

DeployDev to DeployTest

Your syntax is incorrect, it should be :
myVarFromDev: $[ stageDependencies.DeployDev.DeployJob.outputs['DeployJob.SetOutputForDev.myVarDev'] ]
Ref : Deployment Jobs


remote-run: make tests partially pass on Windows

Not all the tests are possible to run on Windows since they expect a
Unix-like shell environment.  However, the rest of the tests can be
accommodated.  This actually found an issue in the implementation.
Since the implementation assumes the target is POSIX/Unix-y, we should
use posixpath rather than os.path which uses the host's path style.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test


Write tests to ensure feature-correctness.

As the project grows - which I certainly hope - and more features will be added, it will become more necessary to verify that new things don't break old things. As such, I think it would be very useful to at least implement unit tests of some sort.

@sungwoncho, any thoughts?

It is a good idea. We don't need to aim for a high coverage but it would be useful to have unit tests for some important functions.

Once #39 is merged, I'll look towards setting up some basic tests.


Review the usage of deprecated APIs

Kubernetes 1.22 will stop serving a few deprecated API versions. The affected APIs have all been promoted to v1 from v1beta1. A list is provided in the deprecation guide.
Also note that some of these v1 APIs were introduced as recently as v1.19, which means that by switching to them we would have to drop support for versions < v1.19. Let's figure out if this is the case for the APIs we use and establish the range of Kubernetes versions we can support.

Moving to https://github.com/cloudfoundry-incubator/eirini-controller/issues/14.


turned off autocomplete on inputs

added  autoComplete="off" for <Input /> elements

yarn.lock should be ignored from commits @karbafoo

I can't get it to remove this conflict.... $%#@$

sorry about that

@karbafoo can we close this one and create a new pr, I can't seem to resolve the yarn.lock conflict...

ofc


runtime(java): Optionally highlight parameterised types

In the presence of parameterised types whose names begin
with a capital letter and end with a less-than sign < that
introduces a type argument or a list of comma-separated type
arguments, followed by a greater-than sign >, a variable
g:java_highlight_generics can be defined to have some
components of such types uniformly coloured (by picking
highlight groups for javaGenericsC{1,2}, javaWildcardBound).
For example,
java.io.InputStream stream = java.io.InputStream.nullInputStream();
java.util.function.Function<String,
    java.util.function.BiFunction<String, String, String>> updater =
	property -> (oldValue, newValue) -> oldValue;
java.util.logging.LogManager.getLogManager()
    .updateConfiguration(stream, updater);

Note that the diamond form and explicit type arguments do
not qualify for this kind of recognition.
For example,
new java.util.HashSet<>().<String>toArray(new String[0]);

References:
https://docs.oracle.com/javase/specs/jls/se21/html/jls-4.html#jls-4.5
https://docs.oracle.com/javase/specs/jls/se21/html/jls-15.html#jls-15.9
https://docs.oracle.com/javase/specs/jls/se21/html/jls-15.html#jls-<IP_ADDRESS>

thanks!

thanks!


Overlay shows wrong :closure-defines

The overlay that is shown on Ctrl + h shows :closure-defines {"re_frame_10x.trace.trace_enabled_QMARK_" true}, should be {"re_frame.trace.trace_enabled_QMARK_" true} as per the README. I think the relevant place in the code is here.

Thanks, good catch!


add child to father only know id but don't know position

i have nodes = [
{id : 4, name : "child1"},
{id :7, name : "child2",children:
[
{id :12, name : "child4"},
{id : 41, name : "child6",children:
[
{id :123, name : "child43"},
]},
]
}]
I want to add children to the parent with id  = 41 ? thank !

This is a recursive function I made to find any id.
Usage:
let foundElement = this.findById(yourArray, "41");
This should retrieve the element you're looking for.
Then to access it's children simply use:
foundElement.children
Hope this helps.
findById(arr, id) {
  let nestingKey = 'children';
  // if empty array then return
  if (arr.length === 0) return

  // return element if found else collect all children(or other nestedKey) array and run this function
  return arr.find(d => d.id === id)
    || this.findById(arr.flatMap(d => d[nestingKey] || []), id)
    || null
}

Closing this issue due to inactivity. Please open a new issue if the problem still exists.


Can't install in "symfony/symfony": "2.8.*"

Hello, I had tried to install the Bundle in symfony 2.8.X, it failed.
composer require nelmio/NelmioSecurityBundle
You are running composer with xdebug enabled. This has a major impact on runtime
 performance. See https://getcomposer.org/xdebug

  [InvalidArgumentException]
  Could not find package nelmio/NelmioSecurityBundle at any version for your
  minimum-stability (stable). Check the package spelling or your minimum-stab
  ility

require [--dev] [--prefer-source] [--prefer-dist] [--no-progress] [--no-update]
[--update-no-dev] [--update-with-dependencies] [--ignore-platform-reqs] [--sort-
packages] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--] [<packag
es>]...

You should use composer require nelmio/security-bundle ;)

@jayS-de is right :)

@jayS-de  Thanks.


[Community Tutorials] Exporting multiple rasters

This follows from a public health tutorials request opened two weeks ago (patch-1) to generate multiple rasters for download. I have closed that other request

@jdbcode Could you kindly do a technical review pass on this tutorial?

Hi @hiyer09 is there anything we can do to help you address the initial review comments? We look forward to working with you on completing the review and integrating your tutorial into the Developer Guide.

Hi Justin, Thanks for sending this reminder. I should be able to get to
this tutorial in the next couple of weeks. Thanks for your patience.
Hari
On Tue, Oct 15, 2019 at 3:47 PM Justin Braaten<EMAIL_ADDRESS>wrote:

Hi @hiyer09 https://github.com/hiyer09 is there anything we can do to
help you address the initial review comments? We look forward to working
with you on completing the review and integrating your tutorial into the
Developer Guide.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/earthengine-community/pull/50?email_source=notifications&email_token=AJVBCMIXOCM7ZWDPSXSZA2LQOYM4DA5CNFSM4I42TZW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBJ7ZSQ#issuecomment-542375114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJVBCMKUDWNABECZ5Q4EVLLQOYM4DANCNFSM4I42TZWQ
.

Thanks for the update, Hari.

Hi @hiyer09 !
Do you have an ETA on completing this tutorial? If not please let me know and we can close it for now until you have a chance to revisit it.
Thanks!
Gino

Hi Gino-
Thanks for your message and reminder, hope you are safe and well.
Apologies for my delinquency. I do hope to complete this - let me take a
look again and confirm timelines, I will get back to you early next week.
Thanks,
Hari
On Tue, Apr 28, 2020 at 11:35 AM Gino Miceli<EMAIL_ADDRESS>wrote:

Hi @hiyer09 https://github.com/hiyer09 !
Do you have an ETA on completing this tutorial? If not please let me know
and we can close it for now until you have a chance to revisit it.
Thanks!
Gino
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/earthengine-community/pull/50#issuecomment-620682339,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJVBCMOC7UVQOMNZH46OUWTRO3ZV3ANCNFSM4I42TZWQ
.

Closing this pull request for inactivity and the fact that exporting multiple images to Drive can be accomplished in the Code Editor using the var batch = require('users/fitoprincipe/geetools:batch') module. For more context on the module see: https://gis.stackexchange.com/questions/248216/exporting-each-image-from-collection-in-google-earth-engine


Terraform deployment not compatible with CID dashboard deployment

When deploying either the CUDOS, Cost Intelligence or KPI dashboards the CID Dashboard deployment via terraform wrapper uses a cloudformation template that relies on a stack output cid-DataExport-Database from the cloudformation destination deployment. When deploying the solution using the cur-setup-destination terraform module this stack doesn't exist and as a result, the stack output also does not exist; this causes the stack deploy to fail.
By passing CurVersion = "1.0" to the cid deployment stack parameters this issue looks like it is resolved.
There isn't any reference in the documentation that this stack parameter is required currently in either the Terraform deployment instructions or the README for the cid-dashboards terraform module.
It would save implementers a lot of time spent troubleshooting if this is noted in the documentation.

@sean-nixon we probably need to provide terrarform wrappers for Data Exports modules as well

Also running into something similar.  We are being advised by our TAM to go forward with CUDOS v5 and CUR 2.0, but the 'source' Terraform module provided only creates the aws_cur_report_definition resource: https://github.com/aws-samples/aws-cudos-framework-deployment/blob/main/terraform-modules/cur-setup-source/main.tf#L253
That resource is legacy and not CUR 2.0.
Rather, the resource it should be using is this:aws_bcmdataexports_export
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/bcmdataexports_export
For us to move forward, we will have to copy the source module and modify it so that it uses the correct resource.  However - I think that once that issue is addressed, the rest of the provided bits and pieces should work, as all of the complicated downstream infrastructure has already been coded to support CUR 2.0.

Hopefully this is helpful.  I followed the contributions guide as best I could.
https://github.com/aws-samples/aws-cudos-framework-deployment/pull/1040

Amusingly, I was already using that CurVersion parameter when I wrote my PR. However, due to switching to v2 and removing that parameter, I'm now getting the same cid-DataExport-Database error that @nickcasscs gets.  Will look at addressing this next.

Ok, am now encountering many issues that stem from the bucket name being wrong.  I believe this is due to a shift in naming conventions in the move from CUR1 to CUR2.
CUR1 = s3://${prefix}-${accountID}-shared/cur
CUR2 = s3://${prefix}-${accountID}-data-exports/cur2/

The existing TF instructions create the CUR1 naming pattern, but the data-exports-aggregation stack expects CUR2.
https://github.com/aws-samples/aws-cudos-framework-deployment/blob/67067259c93cf708f4ee94ffc0fbb8bc1996365f/cfn-templates/data-exports-aggregation.yaml#L173
BucketName: !Sub "${ResourcePrefix}-${AWS::AccountId}-data-exports"
This sheds some light: https://github.com/aws-samples/aws-cudos-framework-deployment/blob/67067259c93cf708f4ee94ffc0fbb8bc1996365f/cfn-templates/cid-cfn.yml#L136-L140
i.e. "We support 2 options: CUR 2.0 from DataExports stack managed by CID or CUR 1(Legacy).
However, just a few lines down from that... https://github.com/aws-samples/aws-cudos-framework-deployment/blob/67067259c93cf708f4ee94ffc0fbb8bc1996365f/cfn-templates/cid-cfn.yml#L144
Default: 's3://cid-{account_id}-shared/cur/'
If CUR version2 is a default, and this is a default, then the data-exports stack can't work?
And then down here: https://github.com/aws-samples/aws-cudos-framework-deployment/blob/67067259c93cf708f4ee94ffc0fbb8bc1996365f/cfn-templates/cid-cfn.yml#L944
CUR BucketPath={parts[0]} format is not recognized. It must be s3://(bucket)/cur or s3://(bucket)/(curprefix)/(curname)/(curname)
Still digging - there is something fundamental I'm missing maybe...?

if we use CUR2, the stack with CUR2 comes with athena table and crawler. So we do not manage it here in this stack as we do for CUR2

Ok, so I wrote some simple Terraform wrappers for the three Cloudformation links here: https://catalog.workshops.aws/awscid/en-US/dashboards/foundational/cudos-cid-kpi/deploy
(they basically work like this: https://github.com/aws-samples/aws-cudos-framework-deployment/blob/main/terraform-modules/cid-dashboards/main.tf)
I broke apart the URLs from that page to get the needed config, plus looked at the Cloudformation YAML files for more details.
After applying them in order, everything is working wonderfully.  So I think the lesson is, for CUR2/CudosV5, do not use the existing TF modules.  If it would help, I can submit a PR with my example code, but honestly I whipped it off in an hour or so - not exactly a shining example of Terraform work.


vim-mode delimits paragraphs differently to Vim

Before dap is typed:
# XXX fix
add_atom_command: (binding, fn) ->
    binding = 'gpd:' + binding
<EMAIL_ADDRESS>atom.commands.add 'atom-workspace', binding: -> fn.call(@)

Expected result after dap is typed:
█

Actual result after dap is typed:
# XXX fix
█

Not sure how important this is, just thought I'd report it anyway.

I think this was just fixed via #684.

No, the ip/ap is still delimited by comments. It should be a pretty easy fix, I will probably look into it :)

Ok thanks for clarifying @MarkusSN.

Thanks guys. I really appreciate your work!


Update readme v1.0.0 mk

Comments for @tulios

[ ] How does one implement a custom decoder for consuming?
[ ] Elaborate on the statement "It will also provide more utility functions to give your code more flexibility" for eachBatch
[ ] In resolveOffset I understand that the default behaviour is that processed messages within a batch will be commited in case of errors, while the rest will remain unprocessed. But it is not clear to me why I would like to change this. What is the use case? It is only adding confusion for me.
[ ] Pause & Resume: I removed mentions of "unsupported by the library"
[ ] Pause & Resume: The example is very weird. Maybe its fine, but its not the way ppl use topics. Maybe use 1 topic and pause because of a dependency being down which seems more like a useful scenario?
[ ] Seek: you don't need to await consumer#run - can you elaborate why this is the case?

The example is very weird. Maybe its fine, but its not the way ppl use topics. Maybe use 1 topic and pause because of a dependency being down which seems more like a useful scenario?

We actually do something similar, where we expose an HTTP endpoint to pause/resume. When I wrote the example, I just didn't want to make assumptions about how the pause/resume would be invoked, so invoking it via a Kafka message seemed appropriate. 😅
If you have an idea for a clearer example, I'm all for it. I just can't think of one that wouldn't involve more non-KafkaJS related cruft. For example, if we take the example of your dependency responding with 429:
await consumer.connect()

await consumer.subscribe({ topic: 'jobs' })

await consumer.run({ eachMessage: async ({ topic, message }) => {
  try {
    await sendToDependency(message)
  } catch (e) {
    if (e instanceof TooManyRequestsError) {
      consumer.pause([{ topic }])
      setTimeout(() => consumer.resume([{ topic }]), e.retryAfter * 1000)
    }

    throw e
  }
}})

@klippx

How does one implement a custom decoder for consuming?

The codec works for both consumers and producers; the consumer will detect that the message is compressed with some codec and it will use the appropriate decompress function do decompress. If the codec is implemented in KafkaJS, it'll just work.

Elaborate on the statement "It will also provide more utility functions to give your code more flexibility" for eachBatch

The eachBatch functions receive 3 helpers besides the batch: resolveOffset, heartbeat,
and isRunning.

In resolveOffset I understand that the default behavior is that processed messages within a batch will be committed in case of errors, while the rest will remain unprocessed. But it is not clear to me why I would like to change this. What is the use case? It is only adding confusion for me.

When we shut down the consumer, it will wait for the full batch to be processed before it exit, if you use isRunning to stop processing the messages the consumer will automatically commit the last offset, skipping the messages you didn't consume. If you make sure you call resolveOffset and you disable the auto-resolve, you can quickly shut down the consumer without losing/skipping any messages.

Seek: you don't need to await consumer#run - can you elaborate why this is the case?

It's possible to optionally await consumer.run, this will make sure your promise resolves when the consumer successfully receives its first batch, this isn't necessary since this operation will happen multiple times throughout the app lifecycle but it gives an extra check. If you call seek after waiting for run, it means that the consumer received the first batch and then performed the seek operation. To make sure your consumers start from the seek definition you have to call run without await.
The reason for all of that is that we need to initialize the consumer before we invoke the seek operation and run is the best place to initialize the consumer.


unit tests

This PR adds unit tests to the 3 modules in s1-reader. The tests are currently very sparse and serve as a frame to build on.
Usage:

checkout unit_test branch from my fork
cd to tests directory
in terminal call: pytest

To do:

test and validate more attributes

Thank you @LiangJYu, following your note above, the test runs nicely.
How did you prepare the SAFE zip file? I notice there are measurement folder and tiff files but with 0 in size.

Thank you @LiangJYu, following your note above, the test runs nicely.
How did you prepare the SAFE zip file? I notice there are measurement folder and tiff files but with 0 in size. Maybe write this in a README.md file within the tests folder?

The 0 size files were touchd with a correct name and path. I will add a README to tests folder.

Thus far, the checks for simple attributes have been implemented. I'm unsure how to test the following more complex attributes.
orbit: Ensure all state vectors within sensing start and stop? Check if position actually above surface of the earth? Check if velocity fast enough?
poly1D: These vary with burst so the verbose method would be to store and check order, std, mean, and coeffs of each. I can't think of a cleaner way.
lut2D: Can this be skiped since this is derived from poly1d?

@LiangJYu  for the lut2d you can check if we are able to eval successfully compared to poly1d. For example :
np.isclose(burst.doppler.lut2d.eval(t0.total_seconds(),r0), burst.doppler.poly1d.eval(r0))

t0 and r0 can be the same middle of swath in my previous comment.

@hfattahi @yunjunz @vbrancat With the new tests added, I think this PR is ready for another look. Thanks!

Hi @LiangJYu @yunjunz I am about to merge the annotation reader in PR #48. The new implementation loads IPF version from manifest.safe file in SAFE .zip file, which is currently not included in the test data. It would be great if the test data is updated with manifest.safe file included, so that the new PR can pass CircieCI.


[move-prover][diem-framework] Support the emits verification with opaque functions

When a function calls an opaque function with a emits spec, Prover generate the corresponding emit_event bytecode in order to simulate the side effect of the opaque function to the EventStore.

If the opaque function has a partial emits spec, then Prover generate the bytecode event_store_diverge which performs some kind of “havoc” to the EventStore. It makes the EventStore grow in an abitrary way, but never shirnk.

[NOTE & TODO] If the opaque function has no emits spec, the current implementation automatically treats the absence of the emits spec “strictly” even though the emits_is_strictis not on for the opaque function. This tentative remedy may sound suprising, but is convenient. Otherwise, the user needs to add emits_is_strict to every opaque function that emits no event. There are many of them in the Diem Framework. This matter needs to be discussed and decided as a group.

emits specs in the conditional schema inclusion is now correctly supported

For example, consider spec schema EmitsSchema { emits msg to handle if cond };
Then, include P ==> EmitsSchema; yields emits msg to handle if P && cond

Added more of the emits specs to the DiemFramework.

modules

DiemAccount
DiemConfig
DiemSystem

transaction scripts

add_validator_and_reconfigure
cancel_burn_with_amount
create_parent_vasp_account
create_validator_account
create_validator_operator_account
remove_validator_and_reconfigure

Motivation
To support the emits verification with opaque functions
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
cargo test

/land

/cancel

/land


Out of date .phar

The phar at http://get.sensiolabs.org/sami.phar (which is the suggested way to use this package) is currently on 4.0.1-DEV, which seems a little out of step with the releases. Can we get the phar updated to include the new, awesome, @todo features?

The new feature was just merged. Please, be patient :)

Apologies, I didn't mean "immediately" - just in the future, when possible. I'm just aware there was also a 4.0.2 release that the .phar didn't seem to ever get updated with.

4.0.3 is out. The previous phar was 4.0.2, but I forgot to bump the version back then.

@fabpot Awesome, thank-you. Apologies again, didn't mean to rush you.


Rendering artifacts with isosurface/volume on dataset

Describe the bug
VAPOR is showing rendering artifacts with a ZFP compressed NetCDF file. However the underlying data renders fine with the slice renderer, strongly suggesting there is nothing wrong with the underlying data.
Expected behavior
No artifacts.
Attachments

Can you reproduce the bug on our test data?
Yes

If so, which file?
Available upon request

Desktop

OS and version: Rocky Linux 8.5
Version: VAPOR 3.5 and 3.6

File is here: https://www.dropbox.com/s/4nv980q76e8dai8/NVIDIA-small-ORF-ElReno10m-a.05670.000000.nc?dl=0

To show the artifacts easily, choose the windmag_sr field. Any contour should do. The artifacts show up in all of the 3D fields.

So, it turns out the artifacts DO NOT occur with another machine. The machine where the artifacts occur uses an Nvidia card with the Nvidia proprietary driver, the one that does not uses an AMD Radeon card.

@leighorf Can you provide us with your Nvidia chipset and driver version?

This might be another reason to consider updating our build libraries. NetCDF/HDF5 are currently not built with support for ZFP compression.

With the updated third party libraries it is now possible to load this data set and reproduce the bug on Casper that @leighorf reported.


TypeError: Cannot read property 'length' of null

From https://ticino-errors.azurewebsites.net/Errors?bucketIdHash=58b08c6d-e50f-a6aa-f626-a7eac6214218
TypeError: Cannot read property 'length' of null
/vs/base/browser/ui/list/listView.ts#216:20 (length)
/vs/base/browser/ui/list/listWidget.ts#862:19 (length)
/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#266:28 (call)
/vs/base/common/event.ts#144:18 (fire)
/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#1156:30 (setVisible)
/vs/workbench/browser/parts/compositePart.ts#387:19 (hideActiveComposite)
/vs/workbench/browser/parts/sidebar/sidebarPart.ts#125:14 (hideActiveViewlet)
/vs/workbench/electron-browser/workbench.ts#828:30 (setSideBarHidden)
/vs/workbench/browser/actions/toggleSidebarVisibility.ts#33:26 (run)
/vs/workbench/common/actions.ts#114:38

Here is another similar callstack
TypeError: Cannot read property 'length' of null[TypeError: Cannot read property 'length' of null](https://github.com/microsoft/vscode/blob/9a199d77c82fcb82f39c68bb33c614af01c111ba/srcTypeError: Cannot read property 'length' of null)/vs/base/browser/ui/list/listView.ts#L216:20 (length)/vs/base/browser/ui/list/listWidget.ts#L862:19 (length)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#L271:29 (splice)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#L262:73 (call)/vs/base/common/event.ts#L142:15 (fire)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#L1096:20 (call)/vs/base/common/event.ts#L144:18 (fire)/vs/workbench/services/scm/common/scmService.ts#L120:25 (registerSCMProvider)/vs/workbench/api/electron-browser/mainThreadSCM.ts#L289:37 (apply)

Here is another similar callstack
TypeError: Cannot read property 'length' of null/vs/base/browser/ui/list/listView.ts#216:20 (length)/vs/base/browser/ui/list/listWidget.ts#862:19 (length)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#271:29 (splice)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#262:73 (call)/vs/base/common/event.ts#142:15 (fire)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#1096:20 (call)/vs/base/common/event.ts#144:18 (fire)/vs/workbench/services/scm/common/scmService.ts#120:25 (registerSCMProvider)/vs/workbench/api/electron-browser/mainThreadSCM.ts#289:37 (apply)/vs/workbench/services/extensions/node/rpcProtocol.ts#174:16

Here is another similar callstack
TypeError: Cannot read property 'length' of null/vs/base/browser/ui/list/listView.ts#216:20 (length)/vs/base/browser/ui/list/listWidget.ts#862:19 (length)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#266:28 (call)/vs/base/common/event.ts#144:18 (fire)/vs/workbench/parts/scm/electron-browser/scmViewlet.ts#1156:30 (setVisible)/vs/workbench/browser/parts/compositePart.ts#387:19 (hideActiveComposite)/vs/workbench/browser/parts/compositePart.ts#124:22 (doOpenComposite)/vs/workbench/browser/parts/compositePart.ts#112:14 (openComposite)/vs/workbench/browser/parts/sidebar/sidebarPart.ts#113:33 (onComplete)/vs/base/common/winjs.base.raw.js#1579:0


Node connection not drawn

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
I have created at with some experimental lambda on columns and when I tried to connect a node to the input port in the at node it started treating entire node as a port.
Expected behaviour
Ability to connect another node to the input port of at
How we can reproduce it?
folow the movie
Screenshots or screencasts
https://user-images.githubusercontent.com/108271897/236894370-357885fe-a2f2-4588-91dc-20ebc29f0450.mp4
Enso Version
2023.5.6 nightly
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
standalone
Operating System
Windows
Operating System Version
Win11pro 22H2 22621.1555
Hardware you are using
12th Gen Intel(R) Core(TM) i9-12900HK / RTX3060 Laptop / Nvidia Drivers 531.68

Greg, the things that you describe are 2 separate issues. The thing that the whole node is treated as an input is a known issue.
The second issue needs logs. Could you please divide this issue into 2 reports and always in such cases show on your video logs from console, please? You can open the console with a shortcut. Without logs, it's impossible to triage such reports.

Sure, it seemed connected. I'll create a separate issue for the connection not being drawn.
Here's the updated video with the logs, and a panic catch:

https://github.com/enso-org/enso/assets/108271897/862cfe98-44ad-410f-b0f3-5f8816067048

There is another screencast in #6615, which is a duplicate of this issue.

@farmaazon you are 100% right. the left side of -> is the lambda header and the node in this issue is not valid. We are not supporting displaying connections ot inside of lambda body right now, and there is a ticket for that, so I'm closing this issue as not valid.

@farmaazon you are 100% right. the left side of -> is the lambda header and the node in this issue is not valid. We are not supporting displaying connections ot inside of lambda body right now, and there is a ticket for that, so I'm closing this issue as not valid.

is operatro57 (you can observe it in my original post in the video) treated as lambda header?

Yes


Material icons are confused (missing?) in tip of tree?

[✓] Flutter (on Mac OS X 10.12.6 16G29, locale en-US, channel master)
    • Flutter at /src/flutter
    • Framework revision 154f2e5402 (3 hours ago), 2017-10-26 09:55:36 -0700
    • Engine revision ec19da1c80
    • Tools Dart version 1.25.0-dev.11.0

[✓] Android toolchain - develop for Android devices (Android SDK 26.0.2)
    • Android SDK at /Users/eseidel/Library/Android/sdk
    • Platform android-26, build-tools 26.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] iOS toolchain - develop for iOS devices (Xcode 8.3.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 8.3.3, Build version 8E3004b
    • ios-deploy 1.9.2
    • CocoaPods version 1.3.1

[✓] Android Studio (version 2.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_112-release-b06)

[✓] IntelliJ IDEA Community Edition (version 2017.2.5)
    • Flutter plugin version 17.0
    • Dart plugin version 172.4155.35

[✓] Connected devices
    • iPhone 6 • 80FD76E9-4422-479B-B503-2EFE5C622125 • ios • iOS 10.3 (simulator)

Maybe something is wrong with my setup?  But this is what I see when I run a fresh flutter create app:

Maybe @xster knows?

I reset my simulator and it still reproduces.

I reverted back to 765167bb8caf311f16008bb93db7d6ccf8bdb5e3 (just picked a random point in the past) and the bug went away.  So there is some sort of regression on tip of tree.

Supposedly this was seen in https://github.com/flutter/flutter/issues/12551, but I'm also seeing this on flutter/flutter@154f2e5402 which I believe is tip of tree?

Happened between engine commits https://github.com/flutter/engine/commit/8e79156765c67b71b1e1b9895dbc8eea43f9949c and https://github.com/flutter/engine/commit/ec19da1c8098b321672a3770ec0b4e84bd0621e9

Reopening this since it's still on head and the chromebots are somehow not building

Pinged the infra bug. Seems out of our control for now unless we un-roll the engine.

Infra bots are back on, no?

This was fixed in flutter/engine#4285 and rolled in flutter/flutter#12787.


Enable dynamic resource creation option

Creating new resources (usually devices) doesn't reflect under the NRT object.
The logic to support was already there, but the option to enable it was never exposed to the user.
For the start, this option would be disabled by default until we'll be sure it's stable enough

[x] expose the flag
[x] fix capacity
[x] unit-test
[x] e2e test
[x] decide whether we want to enable this option by default
[x] consider decoupling this logic from the standard polling routine.

Looks good to me so far. I will review this PR again once we have added some tests and addressed the other bullet points.

/retest

/hold

There is a time when we're having the initial scan on the main thread but the informer is not starting yet.
That could lead to an event (device creation) that will occur just between those two actions and then won't be reflected on the NRT object.
This is a very unlikely scenario, but it would be almost impossible for detecting on user's environment and that's something that we would like to avoid,

everything else LGTM

There is a time when we're having the initial scan on the main thread but the informer is not starting yet. That could lead to an event (device creation) that will occur just between those two actions and then won't be reflected on the NRT object. This is a very unlikely scenario, but it would be almost impossible for detecting on user's environment and that's something that we would like to avoid.

Will think about this a little bit more about this scenario and provide my comments.

everything else LGTM

There is a time when we're having the initial scan on the main thread but the informer is not starting yet. That could lead to an event (device creation) that will occur just between those two actions and then won't be reflected on the NRT object. This is a very unlikely scenario, but it would be almost impossible for detecting on user's environment and that's something that we would like to avoid.

Will think about this scenario a little bit more and provide my comments.

I'm concern handling this edge case will require a lock, or at least moving the update logic back to the scan loop

everything else LGTM

There is a time when we're having the initial scan on the main thread but the informer is not starting yet. That could lead to an event (device creation) that will occur just between those two actions and then won't be reflected on the NRT object. This is a very unlikely scenario, but it would be almost impossible for detecting on user's environment and that's something that we would like to avoid.

Will think about this scenario a little bit more and provide my comments.

I'm concerned handling this edge case will require a lock, or at least moving the update logic back to the scan loop

this is a legit concern which can be handled in a followup patch.
The very first thing coming to mind (so debatable) is that we should have only a goroutine handling the scans. If the main thread wants to trigger a scan (= initial scan), it can just send a request into a channel, which will be serviced ASAP.

this is a legit concern which can be handled in a followup patch.

Ack. Then I'll open an issue to track it.

The very first thing coming to mind (so debatable) is that we should have only a goroutine handling the scans. If the main thread wants to trigger a scan (= initial scan), it can just send a request into a channel, which will be serviced ASAP.

This is possible, it'll requires the scan loop to have additional channel in the select but that's OK I guess.

The very first thing coming to mind (so debatable) is that we should have only a goroutine handling the scans. If the main thread wants to trigger a scan (= initial scan), it can just send a request into a channel, which will be serviced ASAP.

This is possible, it'll requires the scan loop to have additional channel in the select but that's OK I guess.

Maybe not. We can possibly generate an event at startup time using the existing event source.

The very first thing coming to mind (so debatable) is that we should have only a goroutine handling the scans. If the main thread wants to trigger a scan (= initial scan), it can just send a request into a channel, which will be serviced ASAP.

This is possible, it'll requires the scan loop to have additional channel in the select but that's OK I guess.

Maybe not. We can possibly generate an event at startup time using the existing event source.

The Scan loop doesn't contain the update logic. if we would add it to the existing event source, we again, coupling the capacity and allocatable update logic with the available update logic.
That means we should have a separate channel or at least a different type of event.


Add math formulation docs

Add mathematical formulation documentation.

I like how we can include the conceptual overview in the code. However, now we have the same material in two places: Overleaf design doc and here. If we change one, we should change the other. Is there any way of automatically including LaTeX (e.g., from Overleaf) in the code here, to make it easier to keep them in sync?

That's a good point. I agree that having duplicate docs is a bad idea. I don't think there's a way to synchronize them. We could alternatively include a link to the overleaf in the docs, but I don't think the overleaf has public access-- so most users won't be able to view it.
Personally, I'd be fine with using this repo as the primary source for the documentation, and simply referencing this repo's docs in the overleaf-- I feel that the overleaf has more or less converged over the last year. That said, I understand the usefulness of being able to make quick changes in the overleaf. So, unless there's a better alternative, I'm fine with whichever you prefer, @tapios:

[ ] Keep these docs, and reference from overleaf
[ ] Close this PR, and just stick with the overleaf

I like how we can include the conceptual overview in the code. However, now we have the same material in two places: Overleaf design doc and here. If we change one, we should change the other. Is there any way of automatically including LaTeX (e.g., from Overleaf) in the code here, to make it easier to keep them in sync?

That's a good point. I agree that having duplicate docs is a bad idea. I don't think there's a way to synchronize them. We could alternatively include a link to the overleaf in the docs, but I don't think the overleaf has public access-- so most users won't be able to view it.
Personally, I'd be fine with using this repo as the primary source for the documentation, and simply referencing this repo's docs in the overleaf-- I feel that the overleaf has more or less converged over the last year. That said, I understand the usefulness of being able to make quick changes in the overleaf. So, unless there's a better alternative, I'm fine with whichever you prefer, @tapios:

[ ]  Keep these docs, and reference from overleaf
[ ]  Close this PR, and just stick with the overleaf

Let's keep the duplicate docs for now. It's not ideal, but acceptable for now. In principle, this documentation can supersede the Overleaf doc. It's just that I think eventually the Overleaf docs can become a CliMA book, which has everything essential on the conceptual side together in one place. So I do not want to give it up yet. Could you just put a note with a link to these docs into the Overleaf, so people know that if they change the Overleaf, they probably should make changes here too.

bors r+


Initialize open publishing repository: https://github.com/angelgolfer…

…-ms/angelgolfer-msRepo0302200349 of branch live

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

angelgolfer-msDocset0302200349/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Extract script to set test environment

This makes it easier to set the environment into your current shell for running specific tests.

:+1:


Detect item-not-found in update and perform an add

When update() returns an error code, the method now checks if it's the errSecItemNotFound error code and if so performs an add().

Thanks! :)


*H. in RVBASIC gives Bad command

(From StarDot at https://www.stardot.org.uk/forums/viewtopic.php?p=401999#p401999 — here to track.)
*H. (i.e. short for *HELP) works at the PiTubeDirect RISC-V NLE *-prompt but it doesn't when in RVBASIC (it gives a Bad command, from memory — I'm not in front of the machine right now!), but *HELP itself does.
If I QUIT from RVBASIC, *H. works again.  (This is on MOS 3.50 with Indigo-alpha1 of PiTubeDirect; I've not tried anything else.)

I've simplified the local command parser to not accept abbreviated forms.


Async eviction

Based on https://github.com/pmem/CacheLib/pull/16 with a few fixes
Right now, there are a few features missing:

support for chained items
exposing per-tier statistics
support for temporary mappings (CacheAllocator ctor without ShmSharedNew/Atttach)

This change is

Async eviction implementation.
TODO:

support for chained items
exposing per-tier statistics
support for temporary mappings (CacheAllocator ctor without ShmSharedNew/Attach)


Validation fixes

Category

[ x] Content fix

Global effort to fix build validation errors
@VesaJuvonen
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!

@andrewconnell edited tables have been converted to markdown, please review. Thank you

Docs Build status updates of commit bce8af6:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md
:warning:Warning
View
Details

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md
:warning:Warning
View
Details

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md
:warning:Warning
View
Details

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/control-element-delegate-control.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinition.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/controls-element-group.md
:warning:Warning
View
Details

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md
:warning:Warning
View
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/control-element-delegate-control.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-group.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@andrewconnell please disregard previous comment, I need to make ms.date changes before you review again

Docs Build status updates of commit e2fbd65:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md
:warning:Warning
View
Details

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md
:warning:Warning
View
Details

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md
:warning:Warning
View
Details

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/control-element-delegate-control.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinition.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/controls-element-group.md
:warning:Warning
View
Details

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md
:warning:Warning
View
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/control-element-delegate-control.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-group.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b1dc9bf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md
:warning:Warning
View
Details

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md
:warning:Warning
View
Details

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md
:warning:Warning
View
Details

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md
:warning:Warning
View
Details

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/control-element-delegate-control.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinition.md
:warning:Warning
View
Details

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/controls-element-group.md
:warning:Warning
View
Details

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md
:warning:Warning
View
Details

docs/schema/context-element-managedpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdeactivated-element-in-contexteventhandlers-solutionmanifestdeclarativeex.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinition-element-in-contextdefinitiongroup-solutionmanifestdefinitions.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroup-element-in-contextdefinitiongroups-solutionmanifestdefini.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextdefinitiongroups-element-in-solutiondefinition-solutionmanifestdefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contexteventhandlers-element-in-declarativecontextdefinition-solutionmanifestdec.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualgroup-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/contextualtabs-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/control-element-delegate-control.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinition.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/controls-element-group.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/converttype-element-in-interpretation-bdcmetadata-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!


Workspace / feature group: PATRIC_ID not displayed

PATRIC ID is not displayed in the workspace feature group member list.
I think it missed out the memo on change seed_id to patric_id! :)
-Maulik

Fixed and pushed to beta


New package: DiDa v0.1.0

Registering package: DiDa
Repository: https://github.com/LCSB-BioCore/DiDa.jl
Created by: @laurentheirendt
Version: v0.1.0
Commit: 49e2ed74d9b0dc64a78ed5693beacdcf480f8afa
Reviewed by: @laurentheirendt
Reference: https://github.com/LCSB-BioCore/DiDa.jl/issues/9

This PR can be closed - Thanks 👍

This PR can be closed - Thanks 👍


GH-39883: [CI][R][Windows] Use ci/scripts/install_minio.sh with Git bash

Rationale for this change
curl in Rtools can't be used on non Rtools' MSYS2 environment. Because curl in Rtools can't refer /usr/ssl/certs/ca-bundle.crt on non Rtools' MSYS2 environment.
What changes are included in this PR?
Use the bash in GitHub Actions Runner. curl in the environment works.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.

Closes: #39883

+1
No objection.


Error: Invalid value for user_name, must not be None - AccountApi

Hello,
Using following code with my API Key result in the error in title:
configuration = sib_api_v3_sdk.Configuration()
configuration.api_key['api-key'] = '<my_key>'
api_instance = sib_api_v3_sdk.AccountApi(sib_api_v3_sdk.ApiClient(configuration))
account_data = api_instance.get_account()

After debugging the code it seemed that the API call is working fine and the data are returned.

The bug is caused by the deserialization trying to get the value 'data' of 'relay', which is empty.

Issue solved after ticket opening by the company


Feature: allow for Org import from any org

Type of feature
🍕 Feature
Current behavior
Currently, org import for workspaces only works for orgs that I'm in, not for other orgs I want to track. Example:

Suggested solution
It's be really great to be able to track other orgs I'm not in so I don't have to manually import all those orgs reps.
Additional context
No response
Code of Conduct

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

Contributing Docs

[X] I agree to follow this project's Contribution Docs

duplicate of #2874


Interaction response body with only a String value

When preparing a Pact test using PactSwift (which uses pact-ffi under the hood) a test that expects only a single String value in the response body fails to prepare a valid response body.
The response expectation In a consumer test:
.willRespondWith(status: 410,
                        headers: [HttpHeaders.contentType: "application/json"],
                        body: Matcher.EqualTo("\"EXPIRED\"")

Expected response written in Pact file:
"response": {
        "body": "\"EXPIRED\"",
        "headers": {
          "Content-Type": "application/json"
        },
        "matchingRules": {
          "body": {
            "$": {
              "combine": "AND",
              "matchers": [
                {
                  "match": "equality"
                }
              ]
            }
          }
        },
        "status": 410
      }

Actual:
"response": {
        "body": "EXPIRED",
        "headers": {
          "Content-Type": "application/json"
        },
        "matchingRules": {
          "body": {
            "$": {
              "combine": "AND",
              "matchers": [
                {
                  "match": "equality"
                }
              ]
            }
          }
        },
        "status": 410
      }

Enabling PactSwift logging shows that PactSwift sends the following data to pact-ffi:
{"metadata":{"pactSpecification":{"version":"3.0.0"},"pactSwift":{"version":"0.12.0"}},
"interactions":[
  {
    "response": {
      "status": 410,
      "body": "\"EXPIRED\""
    },
    "providerState": "elements exist",
    "request":{"path":"\/elements","method":"get"},
"description":"Request for a list"}],"provider":{"name":"unit-test-api-provider"},
"consumer":{"name":"pactswift-unit-tests"}}

Initially raised at https://github.com/surpher/PactSwift/issues/89#issue-1230776527

What is happening here, because the Pact file is JSON and the content is JSON, it renders the body as a string value. When the Pact file is used, it knows the content type is JSON, so it creates a JSON String body (i.e. adds the quotes back). It will do the same thing with an empty object {}. It will write the JSON as "body": {} and not "body": "{}".
Is there a reason that the body has to have the quotes in the Pact file? This behavior goes all the way back to the original Pact implementation.

This was reported a while back here -> https://github.com/surpher/PactSwift/issues/89#issue-1230776527
If I understand this correctly, the issue here was that the body's content is not JSON, but a single String value in " which the reporter's provider was providing.
imo a bit of an edge case.

But the content type is being set, so it is JSON

Will file it under "misusing".


× Deployment failed! 🛑 File size<PHONE_NUMBER>98) is greater than 2 GiB

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

App Id
d3jciwd36mhkwf
AWS Region
eu-west-2
Amplify Hosting feature
Backend builds, Build settings, Frontend builds, Manual deploys
Frontend framework
React
Next.js version
n/a
Next.js router
N/A
Describe the bug
After doing amplify publish for the first time I got the below error.
File sizes after gzip:
324.39 kB  build\static\js\main.5e101fe0.js
24.82 kB   build\static\css\main.6deb9a98.css
1.78 kB    build\static\js\787.38ba03fb.chunk.js
The project was built assuming it is hosted at /.
You can control this with the homepage field in your package.json.
The build folder is ready to be deployed.
√ Zipping artifacts completed.
× Deployment failed! Please report an issue on the Amplify Console GitHub issue tracker at https://github.com/aws-amplify/amplify-console/issues.
🛑 File size<PHONE_NUMBER>98) is greater than 2 GiB
Session Identifier: 7c6ea617-f81e-496b-8867-087647bd0e26
Expected behavior
I was expecting it to publish
Reproduction steps
amplify publish
Build Settings
No response
Log output
No response
Additional information
No response

figured it out, needed to change project configurations to look at build folder, it was currently looking at entire app.
? What javascript framework are you using react-native
? Source Directory Path:  src
? Distribution Directory Path: build
? Build Command:  npm.cmd run-script build
? Start Command: npm.cmd run-script start


Fix: Remain focus when selecting option

Details
Remain focus on search input when selecting an option
Fixed Issues

$ https://github.com/Expensify/App/issues/19231
PROPOSAL: https://github.com/Expensify/App/issues/19231#issuecomment-1559698481
Tests

Click on FAB
Click on "Split bill"
Type an email and select the contact that shows up in the below suggestion
Verify that the search input still be focused

[x] Verify that no errors appear in the JS console

Offline tests

same above
QA Steps

Click on FAB
Click on "Split bill"
Type an email and select the contact that shows up in the below suggestion
Verify that the search input still be focused

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/129500732/573b7add-f77d-41c4-92a7-916c79273863

Mobile Web - Chrome
https://github.com/Expensify/App/assets/129500732/23b23dfc-2bf5-4695-bc21-b6cb99be7e81

Mobile Web - Safari
https://github.com/Expensify/App/assets/129500732/74b700e5-d9ee-4908-a807-567864d2f628

Desktop

https://github.com/Expensify/App/assets/129500732/a41733e7-1a78-41d9-b90b-d087af857a6e

iOS

https://github.com/Expensify/App/assets/129500732/a7e0be12-b183-4eaf-9dad-c84ceee8e0b4

Android
https://github.com/Expensify/App/assets/129500732/e17a5a66-0385-4ee8-bfcb-9642faed3d5c

@dukenv0307 We will want it to be fixed in this PR. And we want the text input to be selected in SplitBill page as well.

Yes

Added my comments on https://expensify.slack.com/archives/C01GTK53T8Q/p1687282549853709. Let's HOLD the PR for now.

@dukenv0307 We decided to highlight/select the text input after user selects/deselects any row. So, I don't think any change will be required in New Group Page.
You can go forward with the change.

Yes @dukenv0307.

@dukenv0307 Is it ready for review? Please let me know when it's ready for review.

What is the difference?

For mWeb, we don't select the text input.
https://github.com/Expensify/App/blob/11b8908b8ba3282d06543e2808a7c722690521fa/src/pages/NewChatPage.js#L200

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/Julesssss in version: 1.3.37-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


bugfix: patch for security advisory  CVE-2021-23017

patch for CVE-2021-23017
https://x41-dsec.de/lab/advisories/x41-2021-002-nginx-resolver-copy/
https://github.com/alibaba/tengine/issues/1561

Hi ,
Thanks for your pr, we used a new official patch to fixed this issue.
fixed in Tengine 2.3.4, and in this pr: https://github.com/alibaba/tengine/pull/1655


Error: Could not save view.

Hi, I'm Jerry.
When I view my metrics on my project page, I got an error message like "Error: Could not save view." on the web page.
Can you tell me about the situation that can cause this error?
Is it about db connection?

Hi @jjerry-k, thanks for reporting this! Would you mind sharing with me a link to the page where this issue is raising? Also, have you tried other browsers, clearing cache/cookies and incognito window to see if the same error appears?

Hi @jjerry-k, I wanted to follow up here! If this issue is still appearing, would you mind sharing with me a link to the Workspace and try other browsers, clearing up cache/cookies and incognito window?

Hi @luisbergua,
Sorry, about the late reply.
I tried several ways that using another browser and clearing cache/cookies. But, didn't repair.
So, I want to get about wandb local web page's log.
Could you explain where the log saved

Hi @jjerry-k, thanks for your answer! So this error could happen if the view exceeds a certain size threshold, could you explain me what's the size of the metrics? Also, are you running this by using wandb local? And could you send me a sudo code of how are you logging your metrics?

Hi @luisbergua, thank you for your reply!
I'm running wand by using docker!
First, I'm logging 2029 items for each run with 40 epochs.
metrics = {
... 2029 items
}
wandb.log(metrics)

While looking at the log files, I got this message in mysql.log file.
2022-12-29T01:02:58.101968Z 22452 [Note] Aborted connection 22452 to db: 'wandb_local' user: 'wandb_local' host: '<IP_ADDRESS>' (Got an error reading communication packets)
2022-12-29T01:03:10.724457Z 22433 [Note] Aborted connection 22433 to db: 'wandb_local' user: 'wandb_local' host: '<IP_ADDRESS>' (Got a packet bigger than 'max_allowed_packet' bytes)

Did mysql's max_allowed_packet option change when 0.9.40 to 0.9.49 was released?

I solved this issue.
There was no max_allowed_packet option in the mysql configuration file.
This is the content of the file.
# Copyright (c) 2014, 2021, Oracle and/or its affiliates.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License, version 2.0,
# as published by the Free Software Foundation.
#
# This program is also distributed with certain software (including
# but not limited to OpenSSL) that is licensed under separate terms,
# as designated in a particular file or component or in included license
# documentation.  The authors of MySQL hereby grant you an additional
# permission to link the program and your derivative works with the
# separately licensed software that they have included with MySQL.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License, version 2.0, for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301 USA

#
# The MySQL  Server configuration file.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

[mysqld]
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
datadir         = /vol/mysql
#log-error      = /var/log/mysql/error.log
# By default we only accept connections from localhost
#bind-address   = <IP_ADDRESS>
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
max_connections = 500
max_prepared_stmt_count = 65536

# I added this line
max_allowed_packet      = 16M

Hi @jjerry-k, thanks a lot for sharing this! You can check the changes in the different releases here, I cannot see any changes regarding max_allowed_packet. Let me know if I can help you in any other way!

Please close this issue!


My Account: Update username state

Provide visual feedback after the username is successfully updated

hey @italoacasas check #19

@italoacasas now it uses tailwind components #20


[Feature Request] Walls Below Tiles Should be Ignored

As per title. Having a multilevel structure walls below other "walkable" space causes those walls to be calculated for drawing shadows, but only if those walls are above height 0. Having a basement floor at a negative elevation w/ negative height walls will not show up.
Disabling shadows and letting levels/wall height handle vision is a solution, but I find that my players don't always understand why they can't see tokens obscured by wall height, despite telling them that the creature they're trying to see is blocked by the floor/walls around them, despite that location being "within their vision radius". The shadows provide a much clearer indicator as to how and why a token's vision is being obscured, & how terrain really affects their vision on a map.
Images below illustrate how negative floors are restricted to their level, but the walls of height 0-15 are still visible while above a tile on height 15. Ideally, those walls shouldn't cast shadows for the token as they're below the height of the floor (Note, I think the correct way to set up the walls would be height 0-14. Changing this doesn't change the shown behavior). Would be doubly nice if this was integrated with Levels, where toggling the "Allow Sight" option would toggle on the current behaviour.

This is something I've been assuming is a bug, but if this behavior is baked into the current build, I think this module would massively benefit from implementation of the feature described by OP. Currently, to take advantage of Elevated Vision on multi-level maps, one has to tailor a map specifically to ensure EV doesn't actively disrupt the experience, despite having several wonderful features that otherwise significantly enhance battle maps for players and save GMs a great deal of time. I fear the complexity of this feature would require collaboration with other mod-makers, such as the author of the Levels module, which would likely require a lot of patience from us users as development lies at the mercy of schedules.

You have anticipated one upgrade I have been pondering for Elevated Vision! It may take awhile to pull off, but I do want to make this work.
Right now, the shadow shader does this for terrain if you use the WebGL setting. Terrain higher than the shadow at a given pixel will not be shadowed. Essentially, I need to do the same thing for each overhead tile, which will require a bit of work. It might be doable with some sort of masking, where each tile masks the shadows below and is in turn shadowed by what is above. So some conceptual things to figure out.
Alternatively, I could delete walls under tiles, but that would not be correct for all cases. For example, any time a wall is near an edge of a tile, the shadow should probably appear when the tile ends. Or if the tile has a transparent portion, the shadow should be seen below.
This would be a big step toward having something like Levels, but based solely on wall and overhead tile elevations in the scene.


[BUG] Failed to delete rancher-monitoring-crd

Rancher Server Setup

Rancher version: v2.7.12 prime
Monitoring (102.0.3+up40.1.2)

Information about the Cluster

Kubernetes version: v1.27.10+k3s2
Cluster Type: Local k3s

User Information

What is the role of the user logged in: Admin

To Reproduce
When I try to install monitoring I go to Apps -> Installed Apps

uninstall rancher-monitoring (pass)
uninstall rancher-monitoring-crd (fail)

Result
Warn: failed to list *unstructured.Unstructured:
 customresourcedefinitions.apiextensions.k8s.io "thanosrulers.monitoring.coreos.com" is forbidden:
  User "system:serviceaccount:cattle-monitoring-system:rancher-monitoring-crd-manager" cannot list resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

Error: Failed to watch *unstructured.Unstructured:
 failed to list *unstructured.Unstructured:
  customresourcedefinitions.apiextensions.k8s.io "thanosrulers.monitoring.coreos.com" is forbidden:
   User "system:serviceaccount:cattle-monitoring-system:rancher-monitoring-crd-manager" cannot list resource "customresourcedefinitions" in API group "apiextensions.k8s.io" at the cluster scope

** Workaround 88
Add list to rancher-monitoring-crd-manager ClusterRole
~ k get clusterrole -n cattle-monitoring-system rancher-monitoring-crd-manager -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  annotations:
    meta.helm.sh/release-name: rancher-monitoring-crd
    meta.helm.sh/release-namespace: cattle-monitoring-system
  creationTimestamp: "2024-04-18T09:04:24Z"
  finalizers:
  - wrangler.cattle.io/auth-prov-v2-crole
  labels:
    app: rancher-monitoring-crd-manager
    app.kubernetes.io/managed-by: Helm
  name: rancher-monitoring-crd-manager
  resourceVersion: "8178"
  uid: c4ce7764-ec94-45f7-81e4-3fddd526102d
rules:
- apiGroups:
  - apiextensions.k8s.io
  resources:
  - customresourcedefinitions
  verbs:
  - create
  - get
  - patch
  - delete
  - list # << Workaround

I see 3 referenced PRs and crds uninstall works fine on rancher v2.7.15 prime, I assume it's fixed.


Julia Setup on Windows

See http://discourse.quantecon.org/t/problem-with-setting-up-julia-enviaroment/473.
Need to pin down exactly what "run as admin" entails, and then modify the instructions and/or the codebase.

Closing as we concluded this was a quirk in the user's Jupyter setup. If anybody reports a similar issue, we can add a note about this to the instructions.


fix(rollup): update rollup to accept gifs

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: