3.6.0 Multi-Release JAR with JDK21 Virtual Threads

How is this for a compromise.  It uses JDK MultiRelease build to work for JDK8 or add Virtual Threads for 21+.
See: https://www.baeldung.com/maven-multi-release-jars
It was introduced in the JDK: https://openjdk.org/jeps/238

cc @ViToni @Siedlerchr

Yep so far in my BETA testing i have not seen any anomalies but you know in the real world with all this different devices would be the real test 😄

I know of a large scale OSGi based deployment working on Java8. Id' like to have this change tested there before signing this off.

Any chance you could build this SNAPSHOT and test it?

@melloware This is a nice and elegant approach. I assume that the size of the Jar should hardly increase as it is merely a single class that is added in Java21-style, right?
Clearly, this should be tested to work without any hiccups on Java8 systems, so let's wait for @ViToni's test results.
Btw, I see again many "source clean-up changes" within this PR. Maybe you can use the time to extract these into an independent PR, which we could already merge meanwhile and which would make this PR here short and easy to read, review and understand. 😄

@kaikreuzer yes we should test thoroughly on a Java8 only system.
However the source cleanup in the pom.xml was all necessary to compile for V21?   Some of the things I can't fix unless upgrading all those plugins etc to support multimodule?

Well, check out

https://github.com/jmdns/jmdns/pull/312/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L9-L50
https://github.com/jmdns/jmdns/pull/312/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L222-L223
https://github.com/jmdns/jmdns/pull/312/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L232
https://github.com/jmdns/jmdns/pull/312/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L276-L286
https://github.com/jmdns/jmdns/pull/312/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8L182-R211 (apart from the version change)

I'd guess all of this can be already done independent of the multi-release change.

OK reverted those changes

I am using this in a gradle project is there a way to "request" the version with jre8 or will it be somehow automatically determined? (It's part of a library that is used in android) that's why I am asking

the MANIFEST.MF tells its its multirelease JAR so the JVM when it classloads this JAR will see you are using Java8 and ignore the java21 code

@Siedlerchr report back if you find any different please.

OK reverted those changes

Thanks. Feel free to create a separate PR for these, so that we can merge them directly and not having to wait for this PR.

Did anyone get a chance to test this snapshot in a java8 environment?

@melloware I wanted to try out this PR on my setup, what I did is I patched my pull request https://github.com/jmdns/jmdns/pull/318 with the contents of this PR locally. In other words I wanted to execute the fixed tests against this PR.
Since I'm using IntelliJ I had a hard time to configure it, but it seems IntelliJ does not support (out-of-the-box) this multi-release output. See:
https://youtrack.jetbrains.com/issue/IDEA-255308/Maven-import-additional-compile-source-roots-with-multiReleaseOutput-option-as-separate-modules
So whenever I debugged the tests, I always ended up in e.g.: Executors.newSingleThreadExecutor() even if I used Java 21.
Maybe I've not spent enough time to figure out how it could be set up, but do you have any tricks or tips how can I make this work in IntelliJ?
The other thing which I came across - even if it is still used normal thread pools - I needed to add a new test dependency, because some tests are failed (basicall all JmDNSTest)
<dependency>
    <groupId>net.bytebuddy</groupId>
    <artifactId>byte-buddy</artifactId>
    <version>1.15.4</version>
    <scope>test</scope>
</dependency>

And it seems related to this issue

You might have to do mvn clean install to build the SNAPSHOT JAR and then simply use the SNAPSHOT JAR in a project and if it JDK21 it should pick up the 21 version.  Although as to what IntelliJ does I am not sure.

Yeah with a sample project outside JmDNS project it works. Maybe I'm doing something wrong, but if I run mvn clean install under Java21 for JmDNS project, I saw that the Java 8 class was loaded for the tests. Why is that? 😮

I think its because the classloader has to read the Manifest.MF of the JAR at classloading time to see its a multimodule project.

So I'm a little bit concerned how this will be tested if more and more things like this will be added.

i think it would have to be an integration test and not a unit test.

Could the JDK 21 code be carved out to a different maven module somehow and later package together to a single multi-release module? Similarly to what is here: https://github.com/khmarbaise/mrelease
I'm asking this because it could bring relief on how you unit test it and IDEs could easier understand the code.

I know what you mean but most libraries face two real solutions.

Separate branch which was my original proposal of a 4.0 that was JDK 21 only but @kaikreuzer did not want to maintain two branches which i totally understand.
This multi-module build which was why Java invented it for this scenario where we only need to change a few classes and not maintain two branches.

I don't think there are really any other options.

I understand. And don't get me wrong, this solution is way more better than going into different branches and separate jars for different JDKs. I'm just saying it would be better to separate the different JDK specific codes into specific maven modules (compile time) and in later (packaging) phase it could be packed together into a single jar.

@ViToni Did you already have a chance to test this in your environment?

@kaikreuzer this can wait until after you do the current release if you want. I really want to make sure this doesn't break people!

Oh well, we have so many merged PRs now, there's anyhow gonna be something that breaks. 😉
But sure, I'll do a new release with what we have. Will change version to 3.6.0 as it's definitely not a patch release.

Yep i will have to bump the Mockito version here too since its now blowing up using the legacy Mockito.

@melloware starting from mockito 5.3.0, mockito-inline was removed, see https://github.com/mockito/mockito/pull/2945

I just pushed this with Mockito 5.14.2 seeing how it goes

OK 1 single failure
DNSStatefulObjectTest.testWaitAndSignal:76 The thread should have finished. ==> expected: <true> but was: <false>

This looks much better but still failing on Mac: https://github.com/jmdns/jmdns/actions/runs/11518328911/job/32064851954


Fix distro builds

See commit msgs and discussion in https://github.com/bpftrace/bpftrace/pull/3433
Checklist

[ ] Language changes are updated in man/adoc/bpftrace.adoc
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Oh just thought of one small thing - maybe add a comment to the Dockerfiles explaining that CMAKE_BUILD_TYPE=Release can be used instead of "Debug" if the user isn't trying to develop bpftrace?
We had this problem years ago where everyone would end up running debug builds unnecessarily because they just copied the commands directly from places like this. We do actually tell people to follow the Dockerfile instructions when building bpftrace themselves: https://github.com/bpftrace/bpftrace/blob/master/INSTALL.md#building-bpftrace


Cannot run AzureContainerAppsV0 tasks on Win32 agents

I'm unable to run this task on a Windows agent due to a dependency on bash.  Please create a pwsh invocation for the same with a Win32 check and download package
Starting: AzureContainerAppsRC
==============================================================================
Task         : Azure Container Apps Deploy (Release Candidate)
Description  : An Azure DevOps Task to build and deploy Azure Container Apps.
Version      : 0.1.7
Author       : Microsoft Corporation
Help         : [Learn more about this task](http://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureContainerAppsV0/README.md)
==============================================================================
##[error]`Unable to run provided bash command '(curl -sSL "[https://github.com/buildpacks/pack/releases/download/v0.27.0/pack-v0.27.0-linux.tgz"](https://github.com/buildpacks/pack/releases/download/v0.27.0/pack-v0.27.0-linux.tgz%22) | tar -C /usr/local/bin/ --no-same-owner -xzv pack)'.
##[error]Unable to install pack CLI.
##[error]Unable to locate executable file: 'bash'. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Finishing: AzureContainerAppsRC

@icornett Hey Ian, apologies for the delayed response; thanks for the issue and the follow up pull request that you've opened. This is definitely an issue that should be resolved, so I'll take a look at getting your pull request merged and releasing a new version of this AzureContainerAppsRC task in the near future with the changes. Thanks!

@icornett Hey Ian, this issue is resolved in the latest release of the AzureContainerAppsRC task with an update made to our documentation -- unfortunately, there's still no way to run this task on Microsoft-hosted Windows or macOS runners due to the reasons called out here. For self-hosted Windows or macOS runners, this task should be usable with proper installation of Docker, as outlined here.
For now I'm going to close this issue, but if there are any updates in the future to the software available on the Microsoft-hosted Windows or macOS runners that would enable this task for those operating systems, I will follow-up here.


Use Vitest

It's fast.

I converted the main test suite to vitest, it seems to be similar in speed. Maybe the Hono test suite is too fast already 😜
Jest:

Vitest:

Two seconds faster, but still, maybe it can be made faster if we run things concurrently. I tried it but I think we have to adjust it fine-grain with describe.concurrent and it.concurrent to say which things can run concurrently, since some tests depend on the order of tests before and after I think.


Duplicate node with animation

Add simple animation to node
In exported section - nodes - I see this node twice (first - had parent -> scene, second without any parents)
In exported section - animations - I see animation channels with second node
test-animation.zip - contain .blend , .gltf, .bin
Blender 2.80 Release Candidate - Download 18 Jule 2019
This bug does not reproduce in previos version (Blender 2.80 Beta - 2019-06-13)

Thanks for reporting. This bug is already fixed in newer build.
Can you please re-test with current build, and/or with RC2 that will come in following days

Ок, thanks


dsf deletes an extra character

Checklist

[X] Have you tried updating the plugin to the latest version?
[X] Have you checked the Breaking Changes issue?
[X] Have you read through :h nvim-surround to see if there might be any relevant information there?

Neovim Version
NVIM v0.9.0-dev-869+g964ae205a
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Plugin Version
Tagged (Stable)
Minimal Configuration
require("nvim-surround").setup()
Sample Buffer
function myFunction(value) {
  return value
}

export default function Page() {
  const somevalue = "something";

  return (

  );
}

Keystroke Sequence
With the cursor on value in the onClick call, use dsf
Expected behavior
function myFunction(value) {
  return value
}

export default function Page() {
  const somevalue = "something";

  return (

  );
}

Actual behavior
function myFunction(value) {
  return value
}

export default function Page() {
  const somevalue = "something";

  return (

  );
}

Additional context
The problem here is that it deletes an extra character ( { ) at the beginning

Can you try the untagged version of the plugin and see if the issue persists?

I just checked this out, and it works in the stable version but not in the latest version. I corrected the description of the issue. sorry.

Try the latest commit, it should fix the issue. If not, feel free to re-open this issue.

Thank you, it's working now.


Carthage

Hi,
For iOS and OS X projets it's will be great to make your component Carthage compatible
Take a look at these articles:

Ruthlessly Simple Dependency Management with Carthage
Carthage Tutorial: Getting Started
Making Carthage-compatible Frameworks with Swift
[Creating Cross-Platform Swift Frameworks for iOS, watchOS, and tvOS via Carthage and CocoaPods] (http://basememara.com/creating-cross-platform-swift-frameworks-ios-watchos-tvos-via-carthage-cocoapods/)

On your README.md add   on top and add section for the installation with Carthage.

Hi,
Thanks for your advice, but project discovery is more difficult than CocoaPods and maintain two ways is more difficult. Maybe in the future I will make my libraries Carthage compatible.
Thanks again!


Broken links in tensorflow for poets2 - codelabs

Hello,
Links are broken in tensorflow for poets 2 codelabs
Broken link :
1] TensorFlow Lite Optimizing Converter
2] quantized graphs

I found the same broken link in the below.
https://github.com/tensorflow/models/blob/master/research/object_detection/g3doc/running_on_mobile_tensorflowlite.md
I searched "TensorFlow Lite Optimizing Converter" or "TOCO" in the website, but there are no information in website. I will let you know when I have more information.

@ymodak  some other links are also broken , please check other links from  codelab as well
:)

Nagging Assignee @tofulawrence: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Thanks for bringing these to our attention. Fixed the broken links.
For TOCO, please see here:
https://www.tensorflow.org/lite/convert
Thanks!


Make SchemaResponse object on Registration

…tion

Purpose

Changes

QA Notes
Please make verification statements inspired by your code and what your code touches.

Verify
Verify

What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation

Side Effects

Ticket

As discussed in check-in, one missing bit of logic: State logic for the initial SchemaResponse, since approvals will be handled by the sanction for now😣
Most reliable short-term solution:
Add some logic to the end of registration.update_moderation_state(). Something like
if self.sanction.sanction_type in [SanctionTypes.REGISTRATION_APPROVAL, SanctionTypes.EMBARGO]:
  if not self.sanction.is_complete()  # no action needed when Embargo "completes"
    initial_response = self.schema_responses.last()
    initial_response.state = self.sanction.approval_state
    initial_response.save()

As discussed in check-in, one missing bit of logic: State logic for the initial SchemaResponse, since approvals will be handled by the sanction for now in that case 😣
Most reliable short-term solution:
Add some logic to the end of registration.update_moderation_state(). Something like
if self.sanction.sanction_type in [SanctionTypes.REGISTRATION_APPROVAL, SanctionTypes.EMBARGO]:
  if not self.sanction.is_complete()  # no action needed when Embargo "completes"
    initial_response = self.schema_responses.last()
    initial_response.state = self.sanction.approval_state
    initial_response.save()

Still needs this bit.


Adding google analytics support

@apvarun One more feature: google analytics.

@engel-b  This is already included in footer.html as mentioned in the readme


Add deploy spark scripts for maven romote repo

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@zhixingheyi-tian
#1249

@zhouyuan
This PR just add a  script for deploy spark,


UART usage on Artik5 & 10

We need examples and info on UART usage for these boards.
 Front conversations

The ARTIK devices have been deprecated by Samsung and we no longer officially support them, so we can close this issue.


[FEATURE]: New Feature Card component

Description
Creating a new Feature Card component using Tailwind!
Screenshot of the tailwind component

Are you taking this fetaure implementaion
Yes

@jsvigneshkanna could you add the tags for Hacktoberfest, please?

Great @richardnikolas ,
BTW welcome to our cooleer Project 🥂


Add hover-over function to hyperlink

Opportunity page
The hyperlink on the header of the opportunity is not clear. Looks static and not clickable.  Add hover-over function to each

@smellems I tried to fix this but couldn't figure it out. It seems like the default behaviour for links is that the link changes colour. But this doesn't happen for the links (to the opportunities) in the opportunity table. Help? :-)

I made a PR to show where I think you need to make the changes.
Feel free to make changes and merge it.
It's because of the style in the gridify.css that was setting the same color for all the states for a.
I also put some classes to make the title bigger but it might not be needed.


Improve handling when no current referral program

The Chore
Currently the handling for no active programs is a little flaky.
It will let you try to create a code, and then the screen stays unchanged, it doesnt flip to some reduced version of the stats page, it just goes back to teling you you can ctreate a code.
Tasks

[x] Add an extra check when someone creates a code to see if there is a program active.

[x] If there is no program display an extra step in the modal to say "There is currently no referral program active, are you sure you want to create a code?"
[x] If they click yes, it should continue the flow as normal

[x] Once they create the code the screen should change to the referrer stats page which should keep certain bits and replace others with a "No active programs" text
[x] We should also change that text at the bottom a bit. We're not "sorry" ... :) ... change text to the below:

There are currently no active referral programs.
Check the Governance App to see if there are any proposals in progress and vote.
You can propose a new program via the Docs.
Additional details / background info
Sketch below

@dalebennett1992 made a couple of comments on the PR but the rest of this looks good.


closes scopes with arrow at left of line

When we try to close scopes with the arrow at left of line, it does not work every times. Sometimes it does nothing

Couldn't reproduce the bug..It seems,


The active month is always Dec whenever the picker is hidden and opened again

In my local application, i find that the month picker is always Dec active after it's hidden and opened again.
I tried the official demo again after that, but the result is same.

+1

@z3h just FYI there is a fix PR opened to solve this

+1

@z3h @jordancardwell @gordonk
Fixed with #293 (thanks @jordancardwell!). Update to 2.8.9 to get this fix.


Converter improvements for v1.0.08

After updating to the latest version, Zigbee Model and Zigbee Manufacturer do not change

Therefore, in order for the device to work, you need to update the converter.
 const definition = [ {     fingerprint: [{modelID: 'TS0601', manufacturerName: '_TZE204_u9bfwha0'},                   {modelID: 'TS0601', manufacturerName: '_TZE204_aoclfnxz'},                   {modelID: 'TS0601', manufacturerName: '_TZE204_edl8pz1k'},                   {modelID: 'TS0601', manufacturerName: '_TZE204_tagezcph'},                   {modelID: 'TS0601', manufacturerName: '_TZE204_xyugziqv'}                                   ],   zigbeeModel: ['TS0601'],
Tested on _TZE204_aoclfnxz

This is unnecessary. You just need to go through the interview and configuration again.


Input fallback_value option limitation/feature suggestion

Would be nice if possible to use fallback value on optional fields only when input not set. Current behavior is when input is not set or validation fails, but I would like to fail validation if input is not valid and use fallback only when input is not set at all. With current behavior is impossible to check if data is invalid.
example:
// create $inputFilter with 'optional_field' input and 'fallback' as fallback value

// when input is not set
$inputFilter->setData([]);
$inputFilter->isValid(); // return true
$inputFilter->getValue('optional_field'); // return 'fallback'

// when input is set but not valid
$inputFilter->setData(['optional_field' => 'invalid']);
$inputFilter->isValid(); // return false

This is not possible at the moment, but very important scenario for me. I think after https://github.com/zendframework/zend-inputfilter/pull/25 when required option works as 'is set' and not as 'not empty' this would make more sense. no?
I think having fallback on invalid data is bad idea. Also if data should be modified somehow to be valid there is filters for this.

A fallback_if_invalid setting would fix this. If it defaulted to true there would be no BC break. It would also be pretty easy to implement.

It would also be pretty easy to implement.

Considering the dozens of hours spent with the most recent releases to build a test matrix for the current combination of options, I beg to differ. Any new options introduced at this point need to be very carefully evaluated, as they add more permutations to the test matrix: we already are testing something like 32 combinations of options; adding another would double that to 64.

Considering the dozens of hours spent with the most recent releases to build a test matrix for the current combination of options, I beg to differ. Any new options introduced at this point need to be very carefully evaluated, as they add more permutations to the test matrix: we already are testing something like 32 combinations of options; adding another would double that to 64.

In that case, maybe we could remove the "fallback if invalid" behaviour in 3.0?

I think the name is not correct for this behavior I am thinking about default_value or something this should be used only if value not set, otherwise should be used fallback if set. this also would solve BC problem but also have big test matrix problem. But well if this is good feature and we want it in 3.0 we can do it now and remove whole test matrix in 3.0 when other options will be removed.

The behavior can be do with very little effort by extending Input with your custom class.
Personally I prefer don't add implementations are not required by the Input interface and just provide stable and tested implementations.
Anyway, feel free to send a PR with the desired implementation and I'll reconsider my opinion if the implementation is simple and bugfree
Hint:
https://github.com/zendframework/zend-inputfilter/blob/a05fa0bfca3a82ef119e1af2e970a48d787913c7/test/InputTest.php#L581-L587
https://github.com/zendframework/zend-inputfilter/blob/a05fa0bfca3a82ef119e1af2e970a48d787913c7/test/BaseInputFilterTest.php#L473-L506

@Maks3w what do you think if we make this default behavior in ZF3?
I think it is more logical to add fallback(default value) if value isn't set, but not when value is invalid(I would want error here). Or support both, but maybe that would be to complicated.
This would be BC but for 3.0 this is acceptable.

@svycka +1 I use same behavior especially in grid controllers

@svycka I don't consider replace a behavior an option. Instead I suggest send a PR where two behaviors could be used (one at time) probably setting a second parameter to setFallbackValue with an optional second argument where the default value is the current behavior.

Closed due inactivity

Ran into this issue today made me pull my hair out. Fallback values which just work in the empty case would be very much appreciated.
W.r.t. complexity in the combination of flags: I think the solution is to split the Input class to multiple classes. Some combinations of options don't make sense or are very niche and you avoid that entirely that way.


Last month data should be accurate using last 30 days, not since current date of last month

The view count for last month should be last 30 days, not since current date last month because the days in a month varies from 28 (February) to 31 (January, March, May, July, August, October, and December).

Looks like it should be -1 month AND reset day number to 1. Assuming by "last 30 days" we want data for the last month.

I w'll not merge this PR, but i will increase data range in future


Unable to install package osbee>0.2.0

As noted in chickenandpork/hass-osbee#9 the dependency resolution for osbee>0.2.0 fails, but there's no harvestable details as to why.  Blocks install on hass-osbee > 1.1

The log message collected from HomeAssistant doesn't show the actual error.  The recommended repro is helpful:

Terminal
docker exec -it home assistant /bin/bash
/usr/local/bin/python3 -m pip install 'osbee>0.2.0' --constraint /usr/src/homeassistant/homeassistant/package_constraints.txt

The error is that package_constraints.txt has typing==1000000000.0.0 meaning it's impossible to install any other version and be compatible.  Looking further, this is their way of blocking any dependency ontyping but they don't indicate what to use instead. They've got from typing include ... in their code, so they're getting it from somewhere.  Likely installed on their base image and silently assumed to be present thereafter.


Negative/positive OU filtering

Added information about default behaviour of OU filtering in the installation wizard. (=negative filtering)
Added information how to do positive OU filtering, by only synchronizing selected OUs.
Updated article date

Hi @bartbilliet, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@msftclas CLA signed.

@andkjell @billmath Please review these proposed changes. Thanks.

Hi, I am closing and re-opening this PR to bump the CLA bot. Sorry for the inconvenience!

Hi @bartbilliet, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Hi @bartbilliet, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

Had a lot of comments and discussed with Bart off-line. It was easier for me to create a new pull request:
https://github.com/Microsoft/azure-docs/pull/408

Thanks @AndKjell, will close this one.


driver.py:find()

pyleniumio/driver.py:
line 363 is currently: elements = self.webdriver.find_element(by, css)
should be: elements = self.webdriver.find_elements(by, css)

Good catch! This will be fixed in the next release

@darylkell This is now fixed in v1.12.6
https://pypi.org/project/pyleniumio/


test: Initial golden tests

Initial framework for golden tests.
Integrates nicely with Go's testing model.

Looks good to me, thanks!. Maybe the "demo" directory in the project root could be removed as you've basically now moved everything to tests/golden/demo. Apart from that feel free to merge.


Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
Submission Guidelines:

Questions and bugs are welcome, please let us know what's on your mind.
If you are reporting an issue around any of the documents or articles, please provide clear reference(s) to the specific file(s) or URL('s).
Remember to include sufficient details and context.
If you have multiple issues, please submit them as separate issues so we can track resolution.

(DELETE THIS PARAGRAPH AFTER READING)

Category

[ ] Question
[ ] Documentation issue
[ ] Bug

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
If you are planning to share a new feature request (enhancement / suggestion), please use the OneDrive Developer Platform UserVoice at http://aka.ms/od-dev-uservoice, or the SharePoint Developer Platform UserVoice at http://aka.ms/sp-dev-uservoice.
If you have a question about Azure Active Directory, outside of issues with the documentation provided in the OneDrive Developer Center, please ask it here: https://stackoverflow.com/questions/tagged/azure-active-directory
(DELETE THIS PARAGRAPH AFTER READING)

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior.
(DELETE THIS PARAGRAPH AFTER READING)

Observed Behavior

If you are reporting a bug, please describe the observed behavior.
Please also provide the following response headers corresponding to your request(s):

Date (in UTC, please)
request-id
SPRequestGuid (for requests made to OneDrive for Business)

(DELETE THIS PARAGRAPH AFTER READING)

Steps to Reproduce

If you are reporting a bug, please describe the steps to reproduce the bug in sufficient detail for another person to be able to reproduce it.
(DELETE THIS PARAGRAPH AFTER READING)

Thank you.
Originally posted by @all-1995 in https://github.com/OneDrive/onedrive-api-docs/issues/1325

@Alaoy24

@- Hello ``


Topic 2 - Schema specification

A Schema is a standardized and reusable template that defines the structure of Attestation data. It is designed to be independent of any specific business validation rules, as validation business rules will be handled by Modules. Instead, Schema’s main purpose is to provide a clear description of the expected data that should be filled in by the Attestation Issuer.
In addition to describing the expected data, a Schema also specifies how this data should be serialized and deserialized from the blockchain storage. This ensures that the data can be easily exchanged and interpreted by different components or systems that interact with the Attestation.
A Schema consists of a set of fields, each associated with a specific Data Type. These fields define the attributes or properties that an Attestation can have. For example, a Schema may include fields such as "timestamp" to indicate when the Attestation was issued, "issuer" to identify the entity issuing the Attestation, "subject" to specify the entity being attested, and "data" to hold the actual content or information being attested. Each field is assigned a Data Type, which can be a basic type like string, integer, or boolean, or it can be a custom-defined type specific to the application's needs.
The business intent behind the Linear Attestation Service is to maximize the composability and reusability of existing Schemas and Modules. This means that Schemas are designed to be versatile and compatible with different Attestors. Multiple Attestors can use the same Schema to ensure consistency and interoperability. Additionally, the service encourages the creation of new Schemas by allowing anyone to define and contribute their own Schemas.
To facilitate the discovery and adoption of Schemas, it is important to establish a mechanism for making Schemas easily accessible. This enables users to explore and select from a range of existing Schemas rather than creating new ones from scratch. By promoting the reuse of Schemas, the Linear Attestation Service aims to streamline the development and deployment of Attestation systems while maintaining consistency and compatibility across different entities and applications.
The creator of a Schema should be able to add some context about their Schema. A dedicated field will be available for the creator to put a text or a URL.
Here is the list of technical challenges and technical decisions to be collectively discussed and accepted:

One or Many schemas per Attestor
Schema with collections of fields or objects
Schema with nested objects
Self reflecting and cross-reflecting Schemas
Linking Attestations
Data Types
Enforcement of standards
Nullable (required or not) fields => not covered in this Topic. Pushed to the Topic #12

1. One or Many schemas per Attestor
At first glance, only one Schema should be set for an Attestor. Nevertheless, two benefits can be imagined by having multiple schemas for an Attestor:
a. Attestor as a First Class Citizen with reputation
We could consider Attestors as First Class Citizens. This means that they could have different unrelated business domains Schemas, using the same list of Modules as attached to the Attestor.
As an Attestor would become more widely used over time, as it can serve different business domains, it has the potential to gain popularity and trust within the community. The increased usage contributes to building its reputation.
Eg: One Attestor, having a Module “Eth Payment”, using DID schema or Quest Schema

One Attestation Issuer wants to use a well known and trusted Attestor to attest users identity, with ETH payment to create the attestation (DID)
Another one wants also a well known and trusted Attestator, with ETH payment, but to attest a task completion (Quest)

The Attestor configuration would be as follows:

Different Attestation Issuer would use the Attestor as follows:

Pro’s and Con’s
Pro's:

Ensure Attestator reliability and trust;
Creates a much more comprehensive list of Attestors and direct usability, from Attestation Issuer point of view;
Concentrate Attestations registration around Blue Chip Attestators;

Con's:

From Attestion Issuer perspective, it adds complexity, as he has to understand and know that there are several Schemas available, and know which one he has to use;
Hard to cover all use cases, and eventually, new Attestators should be created (need other schema, need other module); Otherwise, we should consider the possibility to attach new Schemas or Modules to an existing Attestor, that opens new rules to design: who can add a Schema, who can add a Module, how to replace one, ...
From technical perspective, it would add complexity to the following technical topics, not yet fully designed at this stage:

How to ensure that all Modules are compatible with each Schema: For instance, if a Module needs to verify a specific field value, should all the Schemas attached to the Attestor using this Module include that field?
Dealing with Modules expected data is not trivial and not yet designed. We are still exploring how Modules will be able to access and interpret data from the Attestation Data (as discussed in Topic #9). For instance, if a Module needs to verify a zero-knowledge proof (zkp), it remains unclear whether this zkp should be described in the Schema or not. Considering the complexity of this topic, the presence of multiple Schemas for an Attestor would introduce additional layers of complexity.
The current on-chain discoverability mechanism is highly inefficient (will be eventually covered by an off-chain indexer - not in the current scope of work), and introducing a link from an Attestation to a Schema would further decrease efficiency and complicate the implementation of looping. For instance, if an Attestor is restricted to having only one unique Schema, retrieving and listing all its Attestations is already a hard process for a user. User would need to obtain the count of Attestations and retrieve them individually using index-based access. If we were to introduce the concept of linking an Attestation to one of the available Schemas for the Attestor, it would add even more complexity in the discoverability process.

b. Complex Attestations with different objects to attest
Objects that are connected and associated with the same Business Domain should be attested through the same Attestor, leading to have a unified set of Schemas under an Attestor.
Two approached can be imagined to create Attestations with this coherent set of Schemas:
Eg: an Attestation Issuer wants to attest that students are registered for courses

Two approaches could be imagined to add Attestations within this coherent set of Schemas:

Approach 1: “Per entity approach”
Approach 2: “Aggregate Root approach” (assuming Student is the AR in the following example)

Pro’s and Con’s
Pro's:

Creates de-facto a super reliable data schema;

Con's:

From Attestion Issuer perspective, it adds complexity, as he has to understand (depending on the approach) how to create a new Attestation
As the prefered approach would be "Per entity" approach, having multiple Schemas for Attestor becomes useless, as it could be done by linking Attestions from different Attestors (see technical design below)

DECISION TO BE TAKEN ("Decision 1"): Is it required for an Attestor to have exactly one Schema, or can it have multiple Schemas?

2. Schema with collections of field values
EAS describes Schema with a simple list of types and field name.
As an example, the following functional description of a Schema would lead to the following calldata:
Functional description of the Schema "Person":
schema Person {
    string   firstName;
    string   lastName;
    uint256  dobTimeStamp;
}

Corresponding calldata:
string firstName, string lastName, uint256 dobTimeStamp

The built-in types available are discussed further in this topic: see: 8. Data Types
This representation works perfectly for flat array Schemas. But how to handle collections.
As an example, here is the functional description of a Schema with a collection of timestamps:
schema Person {
    string     		firstName;
    string     		lastName;
    uint256[]  		eventsTimeStamps;
}

Lists can be added in flat arrays, just by using the convention []
Notes:

Parsing Schema calldata is a technical challenge to be discussed in Topic #12
As EAS does, SchemaId should be the keccack of the schema description / calldata. It prevents de-facto the creation of two identical Schemas and it is easy to compute

DECISION TO BE TAKEN ("Decision 2a"): Shall we use EAS convention to code flat array Schemas?
DECISION TO BE TAKEN ("Decision 2b"): Shall we use the convention [] to code collections?

3. Schema with nested objects
Schema should be able to handle nested objects
Say we have the following functional description of Schemas:
Functional description of the Schema "Patent":
schema Patent {
    string   name;
    string   number;
    Person  creator;
}

Functional description of the Schema "Person":
schema Person {
    string   firstName;
    string   lastName;
}

Three different approaches can be elaborated to handle this situation
a. Keep using EAS style
Extending the EAS convention, we could define a the Patent Schema as follows:
string name, string number, {string firstName, string lastName} creator
Pro’s and Con’s
Pro's:

No need to create nested Schema, as the whole structure in described in a single transaction

Con's:

Becomes pretty unreadable
Does not foster the creation of re-usable schemas

b. Link a Schema from a Schema
We can imagine that

First, the Attestor Configurator creates the Schema Person; eventually, this Schema will be used for the Schema Patent, but also for anyone else willing to use a Schema Person; Assuming that the SchemaId of the Person is 894a...2147f(keccack("string firstName,string lastName"))
In a second time, the Attestor Configurator creates the Schema Patent. In this Schema, the type to code the Person, would be the schemaId of the Schema Person, leading to the following schema description / calldata:
string name, string number, 894a...2147f creator

By extrapolation, collection of objects can be defined using the convention []; eg with a Schema Patent having several creators: string name, string number, 894a...2147f[] creators
Pro’s and Con’s
Pro's:

Foster the creation / re-utilisation of existing Schemas

Con's:

Need to create nested Schema
There is a technical challenge not solved: how to parse a Schema, to be discussed in Topic #12

c. Use json-schema or other highly descriptive standard
Con's: That would not be feasible on-chain

DECISION TO BE TAKEN ("Decision 3"): Shall we use define nested objects, by linked a Schema field to another Schema?

4. Self reflecting and cross-reflecting Schemas
a. Self reflecting Schemas
A Schema should be able to have itself as a linked Schema.
Functional description of the Schema "Person" where the key father points out to a Person:
schema Person {
    string    firstName;
    string    lastName;
    Person  father;
}

In this situation, it is not possible to know the SchemaId of the Schema Person, as there is a circular reference for the relation Person.
To designate the circularly referenced Schema, the most effective approach would be to utilize the reserved type 'Self' to cover this situation. Hence, the description / calldata of this Schema would be: string firstName,string lastName,self father
b. Cross reflecting Schemas
Two Schemas could be cross-reflecting.
Functional description of the Schema "Person" and a Schema "Residence", where both Schemas have at least one property that references the other Schema.
schema Person {
    string             firstName;
    string             lastName;
    Residence     residence;
}

schema Residence {
    string             description;
    string             zipCode;
    Person           owner;
}

Given this cross-reflection, it is not possible to create these Schemas, as we do not know the SchemaId of the Schema Person before creating the Schema Residence, that needs the SchemaId Person to be created.
Many workarounds exist, like creating higher objects, or having a different business data model.
Workaround with higher objects:
schema Person {
    string                          firstName;
    string                          lastName;
    OwnedResidence      residence;
}

schema OwnedResidence {
    Person            owner;
    Residence      residence;
}

schema Residence {
    string             description;
    string             zipCode;
}

DECISION TO BE TAKEN ("Decision 4a"): Self-reflecting type is coded with the type self
DECISION TO BE TAKEN ("Decision 4b"): It is not possible to create cross-reflecting Schemas

5. Linking Attestations
Schema construction taken apart, Attestations should be linkable to other Attestation.
For the sake of clarity, linking Attestation is not related to referring a Schema as a property of a Schema (elaborated in the precedent chapter).
Two questions appears when it comes to link Attestations:

Should the link between Attestations be enforced in the Schema or not?
How could it be implemented?

Here is a functional description of an Attestation "Patent" where the creator is one Attestation "Person":
patentPhone = Patent {"Phone", Attestation Person("personAlexanderBell")}

personAlexanderBell = Person {"Alexander", "Bell"}

a. Linking Attestations enforced on the Schema or not
At first glance, we can imagine that the Schema is responsible to enforce the fact that a nested object of the Schema is hydrated by an existing Attestation and that data expected from the Attestation Issuer is the AttestationId.
On the other hand, we could assume that the Schema does not tell anything about links between Attestations, and this responsibility is pushed backed to a Module.
Pro’s and Con’s having the Schema responsible to enforce linking
Pro's:

If not handled through the Schema description, it would be complex to code this behaviour in a Module
Allows to have consistent data content for a Schema . If this is not enforced at the Schema level, some Attestations may have specific content, manually pushed by sometimes and pointing out an Attestation some other times.
Con's:
Brings business logic within the Schema, which is considered as a non business artefact

b. How could it be implemented?
Considering that Schema is responsible to enforce the link between Attestations, how could it be implemented in the description / calldata of a Schema?
First approach: designate the AttestorId, wearing the expected Schema:
Say we have an Attestor whose Schema is "Person". Its id is Attestor1234
Hence, when creating the Schema "Patent", we would have the following description / calldata of the Schema:
string name,  Attestor1234 creator
Second approach: designate the SchemaId:
Say we have a Schema "Person", with Id Schema9876
Hence, when creating the Schema "Patent", we would have the following description / calldata of the Schema:
string name,  Schema9876 creator
Pro’s and Con’s having the First approach
Pro's:

Allow to enforce the business rules that have been invoked by the Modules of the Attestor, instead of having any Attestor using the Schema Person, without any corresponding and expected business rules. As an example, assuming that the Person Schema is used by two Attestors. One is a "famous" one, with "serious" modules that does interesting and expected checks. The other Attestor using the Schema Person is a dummy Attestor, created by someone, without any module or signature verification. If we link the the Patent Schema to only a SchemaId, the Attestation Issuer will have to pick an AttestationId among all the Attestators having this Schema. The Attestation Issuer will not know what are the relevant Attestors to use for his purpose.
If we were to use a SchemaId as the key to describe the link between Attestations, we would have a conflict with what has been defined to describe the nesting of objects in a Schema, as both would use the Id of the Schema to specify it

Con's:

Brings business logic within the Schema, which is considered as a non business artefact

DECISION TO BE TAKEN ("Decision 5a"): Should the link between Attestations be enforced in the Schema or not?
DECISION TO BE TAKEN ("Decision 5b"): Should link description be done with AttestorId or SchemaId?

6. Data Types
We can imagine two different approaches to define the Data Types available when creating a Schema.

Approach 1: a defined list of human-readable types for the average guy (string, number, boolean, date, datetime, URL, …)
Approach 2: all the solidity primitive types (see EAS)

DECISION TO BE TAKEN ("Decision 6"): Should Data Types be solidity primitives or human-readable types?

7. Enforcement of standards
Bringing standards could be a huge benefit for schema interoperability (eg: force using Schema.org conventions). Nevertheless, at this stage, it is hard to imagine a coercive mean to force user to use a standard

DECISION TO BE TAKEN ("Decision 7"): No enforcement of the standard is expected?

I agree with most of @orbmis's assessments, except I'm not sure if we can actually enforce links on an ongoing basis.  The challenge comes from (the proposed addition of) revocations: If an attestation A (issued by X) refers to another attestation B (issued by Y), then later B is revoked, there are a few enforcement actions, similar to SQL's referential integrity enforcement via ON DELETE clause:

SET NULL/SET DEFAULT – alter A's referencing field.  Not possible because an attestation and all its fields are immutable once published.
CASCADE – revoke A as well.  Not possible if X != Y.  It may also have a gas implication if the fan-out is huge.
NO ACTION/RESTRICT – prevent the revocation.  This is probably the only technically feasible option at the moment.

However, even NO ACTION/RESTRICT have a real-life implication, and it opens up the need for semantic clarification of "revocation":

If Y wanted to retract B because it used to reflect their opinion but does not anymore, Y should be able to do so.
However, if A referred to B in order to, for example, express X's approval/disapproval of Y's opinion as of its initial publication, it should be also possible to keep A, as Y's change of heart does not invalidate A's past opinions.

IMO this can be solved if we agreed that an attestation captures an instantaneous, immutable snapshot of something that may still evolve over time, and an attestation cannot really be retracted (in the sense that it's to be deemed invalid/nonexistent) once published, but can only be fully superseded/partially updated by publishing another attestation that links to the original attestation.


Rename file links in queries when file is renamed

As the title describes, auto-rename file links that are in queries.
dataview already autocompletes links when typing them out in a query, however when the file is renamed the link isn't renamed in the query. Obsidian automatically renames the link everywhere else though.
Query example:
WHERE project = [[Projects/P - Sample project]]

I'll have to see if I can hook into the existing renamer to also do codeblocks; as far as I'm aware, Obsidian intentionally skips frontmatter and codeblocks by default.

Thanks! I can imagine some people may want a switch to enable / disable this feature in the settings menu

Exactly what I need +1

Automatically renaming things inside Dataview scripts/queries sounds risky (it would need actual understanding of code structure), and also sounds like something that Obsidian doesn't even support. So sure, the feature would be nice but sounds impossible at the moment.

Obsidian does change wikilinks if you rename the file or move it around but I agree that it's risky to do that in code. I wonder if Obs simply ignores wikilinks in code blocks.

Given that DV does parse the note contents, it does sound doable but then you'd need to support both wikilinks and markdown links and it honestly may be more trouble than it's worth. Perhaps a separate plugin could cover this?

As a possible workaround: You could extract the link to a inline field, so that the link is a proper content of the file and dataview will rename it for you while your query stays functional. Of course, that'd mean the link shows up in your graph.
queryKey:: [[Some project]]

```dataview
LIST
WHERE project = this.queryKey
```

As a possible workaround: You could extract the link to a inline field, so that the link is a proper content of the file and dataview will rename it for you while your query stays functional. Of course, that'd mean the link shows up in your graph.
queryKey:: [[Some project]]

```dataview
LIST
WHERE project = this.queryKey

the field can be made invisible with:
[ queryKey::[[Some project]] ]
wthout "inline fields bracket syntax" does not work

I encountered this problem aswell and found my own solutien. I use these inline file links because I don't want them to appear on the graph. The direction in which I link my notes is very important because when a note links to it's parent, it is a dependency of that note. In other words the direction of links is a hirarchical dependency structure.
Here is my solution:

I use templater to assign a unique identifier (YYMMDDhhmmss) to my notes
Then I query this unique identifier:

$= dv.pages().where(p => p.note_id ==<PHONE_NUMBER>5012).file.link

There are a few caveats tho: If for some reason the ID of a note breaks I have no way of figuring out whether that note is linked somewhere.
My feature request therefor would be to allow the use of custom javascript snippets such as the ones that templater allows  to use and in fact I use these a lot in my templates as I do a lot of scripting. Ideally I would want to be able to declare a simple function that I can use everywhere that is exposed through the dv object that allows me to do some error handling or more advanced stuff such as including a smoll sqllite database. @s-blu


Swap position of (t+b)/(t-b) in frustum matrix

Not completely sure, but it seems there is typo here, where (top + bottom) / (top - bottom) is at position M[2,1], but should be at M[1,2]. Checked it with the implementation of GLM (C++ version at https://github.com/g-truc/glm) and your own examples at https://www.labri.fr/perso/nrougier/python-opengl/
Does not matter much in this library though, because, when top == - button then the value is always zero, and since there are no direct calls to frustum, but instead perspective is used, that issue will probably not be noticed. However, the reason is why I wanted to make this PR is also to note that the same implementation of frustum is used at https://matplotlib.org/matplotblog/posts/custom-3d-engine/. If you agree with the fix, probably you would like to fix the article as well.
Having this chance once more, I would like to say again that appreciate your work a lot!
P.S.: Yes, I also checked the implementation of frustum with ChatGPT 😅

Thanks! Would you have a simple example that uses Frustum to check if it's correct now ? In the meantime, I'll merge your PR.


ingress should support https

Currently, ingress is hardcoded to http it should be configurable and default to https. If a deployment sits behind an additional reverse proxy that forwards requests to http that should be an extra configuration step.

hmmm ... I may misunderstand how the rules work

For the default openshift IngressController, the easiest way to use https is to use this annotation:
 - ingress:
     enabled: true
     annotations:
       route.openshift.io/termination: edge


Add on_release to Buttons and Container controls

Please Describe The Problem To Be Solved
Is there way to track when a button click is released (after mouse click and/or touch)?  Maybe add an on_release() event in all buttons and container controls?   This can be very helpful for audio and video recording purpose.
(Optional): Suggest A Solution
(Replace This Text: A concise description of your preferred solution. Things to address include:

Details of the technical implementation, e.g. Flutter widget solving the problem.
Tradeoffs made in design decisions
Caveats and considerations for the future

If there are multiple solutions, please present each one separately. Save comparisons for the very end.)

You can use GestureDetector for this case,seems flet control are based from flutter control. on the flutter control like a ElevatedButton _https://api.flutter.dev/flutter/material/ElevatedButton-class.html_ Constructors doesn't  have onRelease event. it's mean even you code on flet you have to code like flutter ways
import flet as ft

def main(page: ft.Page):

    def change_text(e):
        text.value = e
        text.update()

    page.add(
        ft.Container(
            height=50,
            width=50,
            content=ft.GestureDetector(
                on_tap=lambda e: change_text("On Release"),
            ),
            bgcolor="red",
            on_click=lambda e: change_text("On Click"),
            ink=True,
        ),
        text := ft.Text("Test text"),
    )

ft.app(target=main)


syntax hilighting not active for build.rs file

Can you give more information? What OS, which lapce version? What project did you open?

Ah sorry
I'm on Linux, using the latest nightly release
The project I have open contains 2 crates inside of it
Syntax hilighting is working for everything within the src/ directory of the crates
But the build.rs file doesn't have it (despite rust-analyzer from the rust extension picking it up
Hope that helps

Can't reproduce, build.rs in lapce repo highlights properly in lapce


including domains automatically?

I'm revising the README.md files in the tutorial and I find it difficult to have to explain upfront about the domains.k file and about its DOMAINS and DOMAINS-SYNTAX modules.  Besides, these may/will change anyway in the future, in which case we'd have to change the tutorial again.  Also, we'd like to have good defaults in general, that give beginners a quick way to using K without much upfront learning, especially of low level details that may change anyway.
I would therefore like to suggest that we include automatically the domains.k file, and that each user-defined module suffixed with -SYNTAX includes DOMAINS-SYNTAX and any other user-defined module includes DOMAINS.  This will allow us to have minimal changes to the tutorial and will buy us time to think about how to organize our domains without bothering our users yet.
Then for those who do not want to have the predefined domains included in their definitions, we can offer an option --no-domains.  Note that this is also what Maude does with its prelude.
What do you guys think?
p.s. I know this looks like "something new that was not planned" and we are under time pressure, but I actually think that this will save us overall time!  Is should be easy to add the above right after ekore/outer parsing, probably it will take a couple of hours, and then we don't have to spend hours and hours of low-level work to change tens of definitions and readmes.

We have no time to argue about this, there are literally only a bit more than 2 weeks left, which is barely enough time to revise the tutorial.  So I take full responsibility for this decision: let's include domains.k and DOMAINS-SYNTAX and DOMAINS automatically as described above.  It is a very risky move to change the user-visible syntax in all definitions for a temporary reason.

We have no time to argue about this, there are literally only a bit more than 2 weeks left, which is barely enough time to revise the tutorial.  So I take full responsibility for this decision: let's include domains.k and DOMAINS-SYNTAX and DOMAINS automatically as described above.  It is a very risky move to change the user-visible syntax in all definitions for a temporary reason.

I'm saying this after revising #1966 and seeing how ugly all those imports are.  It is just too early in the learning flow to tell students about it, so it must be a default.

I'm saying this after revising #1966 and seeing how ugly all those imports are.  It is just too early in the learning flow to tell students about it, so it must be a default.

solved by #1976


Remove BaseMetastoreTables and HiveTables

It seems to me that these are replaced by their Catalog counterparts. Should we delete these then?

+1


New beta version <IP_ADDRESS>-beta

Happy with CLR and .Features being updated on SmartContracts side 👍


issue

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: Failed to deploy because the path is not part of an open workspace. Open in a workspace and try again.
Version: 0.16.2
OS: win32
OS Release: 10.0.17763
Product: Visual Studio Code
Product Version: 1.42.1
Language: en

Call Stack
extension.bundle.js:1:719808extension.bundle.js:1:719808
o extension.bundle.js:1:719007

Hi @prinsiahirwar1995
Thanks for reporting.  We require that you have the workspace that you are deploying open due to project settings that we use when deploying.  If that doesn't resolve your issue, please reopen and provide repro steps.


Macro does not highlighted if it defined inside of QBS group

If a macro is defined inside of a Group:
Group {
    cpp.defines: ["FOO"]
}

then it will not be found.

Done


Generated code not run when outputModule: true and entry chunk dependent on common chunk

Bug report
If the current behavior is a bug, please provide the steps to reproduce.
repro: https://github.com/ahabhgk/webpack-output-module-repro
What is the current behavior?
index.js:
import common from './common.js`
console.log(common)

common.js:
export default true

webpack config:
module.exports = {
  experiments: {
    outputModule: true,
  },
  target: 'es2020',
  optimization: {
    splitChunks: {
      cacheGroups: {
        common: {
          test: /common\.js/,
          minSize: 0,
          chunks: 'all'
        }
      }
    }
  }
}

run the build output: node ./dist/main.mjs, it will log nothing, but it should log true
Other relevant information:
webpack version:  ^5.79.0
Node.js version:  16
Operating System:  OSX

Yeah, I see

@ahabhgk Oh, there is not problems with webpack, something wrong with target, if you change it to target: "web" (or node) all works fine, but if you change it to ['es2020', 'web'], it doesn't work

Also if you speficity options manually (chunkFormat and etc) all works fine too, so something wrong with our defaults...

Note: target: 'es2020', is not valid good value, because we don't know your env, so you should use target: ['es2020', 'web'] or ['es2020', 'node'], anyway if you use just es2020 you will need to setup chunkFormat (and etc) manually

I'm trying to find a chunkFormat that can run both on browser and node, target: "universal" would be perfect, but not implement yet, so I tried chunkFormat: "module" and found this bug.

Certainly should keep this open.  It also causes ESM web workers not to load if they are split using default optimization as discussed in #17298.

@alexander-akait

https://github.com/webpack/webpack/issues/17014#issuecomment-1513226276

Could you please help with the config options that we need to pass manually until this is fixed ?  I tried the following. But didnt work !
  output: {
    ...
    chunkFormat: "module",
    chunkLoading: "import"
    asyncChunks: true
  },

bump

I think I am also hitting this but without outputModule: true being involved:
I have two entrypoints (A, B) depending on a shared module (C)
A both imports from C and re-exports several of the things in C.
In dev, everything works. In prod, webpack only re-exports the things from C, while additional code is still present in A its own exports are not exported.

@ahabhgk I think the same - https://github.com/webpack/webpack/issues/13852, did you find a fix in rspack?

No, I haven't found a suitable fix that can be built into Rspack/or webpack, we usually just let user to use chunks: "async" and disable runtime chunk to avoid split the entry chunk

@ahabhgk Thanks for the feedback, I'll try to find a solution (what's the problem) after the next issue


Feature Request: Terraform icon

Thank you for your cool icons.
Can you add the terraform icon as well, please?
References

Terraform by HashiCorp
Terraform logo

https://github.com/yamatsum/nonicons/commit/ca15fd447824a37c34ea95d10e490ae0eac6967c
enjoy it!


Simple MARKET order failing with "Invalid signature for order"

Error message do not say much. Python code is:
private_client = Client(
host='https://api.dydx.exchange',
api_key_credentials={
'key': CREDENTIAL_KEY,
'secret': CREDENTIAL_SECRET,
'passphrase': CREDENTIAL_PASSPHRASE
},
stark_private_key=STARK_KEY,
default_ethereum_address=ETHEREUM_ADDRESS,
)
order = private_client.private.create_order(
position_id=120,
market=MARKET_BTC_USD,
side=ORDER_SIDE_BUY,
order_type=ORDER_TYPE_MARKET,
post_only=False,
expiration_epoch_seconds=time.time() + 70,
limit_fee='0.002',  # 0.02%
price='23230.00',
size='0.002',
time_in_force=TIME_IN_FORCE_IOC
)

DydxApiError: DydxApiError(status_code=400, response={'errors': [{'msg': 'Invalid signature for order'}]})
Tried without any success several combinations, always respecting the ORDER_TYPE_MARKET. Also, any reason for requiring the price in a market order request? This is similar to https://github.com/dydxprotocol/dydx-v3-python/issues/137

For my case, I tried to place a limit order and got the same error "DydxApiError: DydxApiError(status_code=400, response={'errors': [{'msg': 'Invalid signature for order'}]})".
(I also wonder why we need price for market order request.)

At Japanese dYdX community, I got a suggestion to try with other account. Interestingly I didn't have any trouble with a new account. I could sign to my order with the same code.

Thanks for the insight! Was the new account created in Metamask?

I had the same issue. What I realize is if you've previously used an ETH account to onboard via DYDX's web interface, you should get the stark key from your browser's local storage (inspect element -> application) see bottom of this page: https://docs.dydx.community/dydx-governance/resources/market-maker-onboarding.
Calling onboarding.derive_stark_key after onboarding via web UI somehow generates a different set of stark key from the one in your browser's local storage which causes "Invalid Signature for order".
I didn't investigate why onboarding.derive_stark_key generates differently. But that's the cause.

On the other hand, if you went through the flow of creating user and deriving stark key programmatically first and then connect to DYDX's web UI via Metamask or others, the stark key would be the same.


How about a template without Docker

How can I use this template without Docker ? Would be nice to have one such
Thanks
Ravishankar

You should be able to use it without opening the container.  The only delta I can think of is the environment variables - meaning you may need to source your ROS install.
What errors are you running into?

I think there would be no errors if I used the package as it is.
I am using ROS2 galactic on WSL2. I did a few adaptations:

Removed .devcontainer, .git and .github folders

Changing foxy to galactic in .vscode JSON files

Added --merge-install option to clean task otherwise there is an error like this:
[0.201s] ERROR:colcon:colcon build: The install directory 'install' was created with the layout 'merged'. Please remove the install directory, pick a different one or add the '--merge-install' option.

Edited package CMakeLists.txt file to build the node
find_package(rclcpp REQUIRED)
add_executable(helloworld_node src/helloworld_node.cpp)
ament_target_dependencies(helloworld_node rclcpp)
install(TARGETS
helloworld_node
DESTINATION lib/${PROJECT_NAME})

I

So sounds like it works as intended then
Pro tip: there's a branch for each release.  If you want something other than the latest LTS you need to select "include all branches" when you create a repo from the template to get them
galactic: https://github.com/athackst/vscode_ros2_workspace/tree/galactic


Fix Prototype Pollution

📊 Metadata *
assign.js is vulnerable to Prototype Pollution.
This package allowing for modification of prototype behavior, which may result in Information Disclosure/DoS/RCE.
Bounty URL: https://www.huntr.dev/bounties/1-npm-assign.js/
⚙ Description *
Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects.
JavaScript allows all Object attributes to be altered, including their magical attributes such as proto, constructor and prototype.
An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values.
Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain.
💻 Technical Description *
Fixed by avoiding setting magical attributes.
🐛 Proof of Concept (PoC) *

Create the following PoC file:

// poc.js
var Assigner = require("assign.js")
var assigner = new Assigner()
const payload = JSON.parse('{"__proto__":{"polluted":"Yes! Its Polluted"}}');
var obj = {}
console.log("Before : " + {}.polluted);
assigner.assign(obj, payload);
console.log("After : " + {}.polluted);

Execute the following commands in another terminal:

npm i assign.js # Install affected module
node poc.js #  Run the PoC

Check the Output:

Before : undefined
After : Yes! Its Polluted

🔥 Proof of Fix (PoF) *
After fix execution will block prototype pollution and polluted will be undefined for new objects

👍 User Acceptance Testing (UAT)
After fix functionality is unafected

Sorry alromh87, we enjoyed reviewing your fix but it has not been selected this time. If this bounty has not been closed, please feel free to try again with a new pull request!
We appreciate your effort and look forward to reviewing more of your fixes in the future! 🔨😎
Come join us on Discord


Can not encrypt wallet

I downloaded zcash4mac and everything seems to be working great, except that I can't seem to encrypt the wallet that contains the private keys. Is there a way to fix this? Is short, the "encrypt..." option is shown in the menu, but you can't click on it.

Its greyed out because the zcash core team is still working on re-enabling
wallet encryption....its disabled right now because the process of
encrypting/decrypting private keys for shielded z-addresses is going to
have to be wildly different than that from the bitcoin inherited
transparent t-addresses due to how it has to scan the blockchain
differently for them on startup.
As soon as its enabled, I'll be pushing an update that supports it.
On Wed, May 17, 2017 at 4:58 AM, Lunokhod<EMAIL_ADDRESS>wrote:

I downloaded zcash4mac and everything seems to be working great, except
that I can't seem to encrypt the wallet that contains the private keys. Is
there a way to fix this? Is short, the "encrypt..." option is shown in the
menu, but you can't click on it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/radix42/zcash4mac/issues/2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF9e0PgJadcRE1umgR4vJYlx7pae8JtZks5r6uEBgaJpZM4Ndwoq
.

I hope that this is their number one priority. No one would recommend having an unecrypted wallet on their computer... Thanks for the response.

Maybe you can create a workaround until wallet encryption is enabled. Create a growable read/write sparsebundle, encrypted either with a password or an S/MIME key, mount the volume, copy the wallet to the sparsebundle volume, move the original wallet file to a different location, then create a symbolic link to the wallet on the sparsebundle at the wallet's original location. So when you quit the Zcash app and stop zcashd, you can unmount the volume, and your wallet will be safe. Downside: when running zcashd and the zcash app, you need to mount the volume beforehand, and then it's not encrypted anymore, i.e. people with access to your system will have access to the wallet. (If it works, you can probably delete/shred the original wallet file.)
Afaik the Ledger Nano S now also supports Zcash, so that might be yet another alternative.


New version: ServerManager.ServerManager version <IP_ADDRESS>-alpha

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116589&drop=dogfoodAlpha

Close with reason: Duplicate; Existing package has correct ARP


SvmVec should support CL_DEVICE_SVM_FINE_GRAIN_SYSTEM

Currently SvmVec does not support CL_DEVICE_SVM_FINE_GRAIN_SYSTEM memory, it expects the user to use a vector instead. SvmVec should support all types of shared virtual memory for ease of use.

SvmRawVec now uses alloc to allocate and deallocate system memory for CL_DEVICE_SVM_FINE_GRAIN_SYSTEM memory and test_opencl_2_system_svm_example has been added to test it.


Add documentation to the tap

What should go in the config?
What data will be extracted by the tap?

This has been completed. Can close.


Fixing issues in horizon-wiotp scripts

Fixing issues https://github.ibm.com/Blue-Horizon/wiotp-horizon/issues/70 and https://github.ibm.com/Blue-Horizon/wiotp-horizon/issues/74.

Fixed


Empty metrics

When I try to use --metrics option, only new dimensions (CloudMain) get created in CloudWatch - but no data points.
# tag-compliance.yml
policies:
  - name: tag-compliance
    resource: ec2
    filters:
      - "State.Name": running
      - or:
        - "tag:Owner": absent
        - "tag:CostCenter": absent

custodian run --region all --output-dir s3://my-bucket/custodian --metrics tag-compliance.yml

There are 4 instances that match this policy, and I can see them in CSV reports, as well as S3 bucket.
What am I doing wrong?

thats odd, there should be resource and policy dimensions  in addition to the namespace, metrics should be resource time, action time, resource count.

Yes, sorry, they exist as well. What I meant is that no data is put, no metrics seem to be published
Am 31. Okt. 2017, 19:56 +0000 schrieb Kapil Thangavelu<EMAIL_ADDRESS>
thats odd, there should be resource and policy dimensions in addition to the namespace, metrics should be resource time, action time, resource count.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm seeing the same thing. It creates the metrics, but there are no values populated. I tested on a brand new account.

It looks like it might be an issue when using the --metrics flag, as it seems to be working when I use --metrics-enabled


Document the type of object returned by dataset_dimensions()

Currently the documentation notes what dataset_dimensions() returns, but not the format (i.e. list/vector): https://github.com/jsphdms/scotgov/blob/5e3a04f277e8c39b6714df4c00f149c18920719c/R/dataset_dimensions.r#L4

a5646b944d6907eff5fd65b0f3c544217b5deef1


Added deeplink prefix to config for demos with custom wallets

Added deeplink prefix to config file so the demo can support custom wallets
Signed-off-by: wadeking98<EMAIL_ADDRESS>

Required for, https://github.com/bcgov/trust-over-ip-configurations/pull/106

@esune, if this looks good to you I can get these two PRs moving and the changes deployed.

@WadeBarnes @wadeking98 changes look good to me


NativeWindow doesn't provide OnHandleChange

For some lightweight applications, such as sniffing WM_DEVICECHANGE (and subsequent DBT_DEVICEARRIVAL events), we must call RegisterDeviceNotification() when we have a valid handle; but we must also re-register if our handle ever changes. In the Windows.Forms NativeWindow implementation, this is done in the OnHandleChanged() method. This PR adds such a method to WinApi.

Hi @jaydcarlson, thanks for the PR :) But lets think about it a moment. WinForms does a lot more than just a think wrapper, though I don't exactly remember how and when a handle changes.
The problem I see with merging this is that - it creates an API with caveats. The class provides an OnHandleChange - so from the outside perspective it must cleanly abstract all Handle changes, but it is not so. It is only handled when the change is limited to the NativeWindow itself. NativeWindow is a class that's essentially the core and lightweight bridge. So, it doesn't guarantee that handle are within it's scope.
The second problem is that it causes OnHandleChange during zeroing out the pointers. This may be desired in some cases, and not desired in others.
I think it's simpler and caveat free, when change of handles is just handled externally when you need it. Please let me know if you think there's any other way to do this without these caveats above.

Closing stale PRs


deprecate use of GenericArray

With const generics, it should be possible now. I think we use GenericArray because it impls Default though. I'm not sure what we need to use instead @lulf
eg:
let mut phy: DataPayloadCreator<[u8; 255], C> = DataPayloadCreator::default();
    |                                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `core::default::Default` is not implemented for `[u8; 255]`

Firstly, GenericArray dependency is used both in our code and our dependencies, whenever default-crypto is used.
Our unconditional usage

JoinAcceptCreator.encrypt_payload(...): https://github.com/lora-rs/lora-rs/blob/969ee2406d957954921d4be6fda69adac976534b/lorawan-encoding/src/creator.rs#L175-L179

We use it in securityhelpers::encrypt_frm_data_payload(...):
https://github.com/lora-rs/lora-rs/blob/969ee2406d957954921d4be6fda69adac976534b/lorawan-encoding/src/securityhelpers.rs#L61

We re-export generic_array from securityhelpers: https://github.com/lora-rs/lora-rs/
blob/969ee2406d957954921d4be6fda69adac976534b/lorawan-encoding/src/securityhelpers.rs#L2

Internal re-export usage

EncryptedJoinAcceptPayload.decrypt(...): https://github.com/lora-rs/lora-rs/blob/969ee2406d957954921d4be6fda69adac976534b/lorawan-encoding/src/parser.rs#L378-L379

Encrypter, Decrypter and Keys traits: https://github.com/lora-rs/lora-rs/blob/969ee2406d957954921d4be6fda69adac976534b/lorawan-encoding/src/keys.rs#L187-L201

Use by dependencies
Regarding dependencies, RustCrypto (from where our aes and cmac implementations are coming from) is trying to get rid of GenericArray dependency as well in favor of const generics - https://github.com/RustCrypto/traits/issues/1481
As an interim step they have introduced a hybrid_array crate and have ported latest release candidate version to use it instead of GenericArray.

I have a quick and dirty (with only minimal changes to get it to build) branch here that uses the pre-release crates: https://github.com/plaes/lora-rs/tree/hybrid-array

Completed as per #309 by @lucasgranberg
:100:  Thanks!


[SPARK-11206] Support SQL UI on the history server (resubmit)

Resubmit #9297 and #9991
On the live web UI, there is a SQL tab which provides valuable information for the SQL query. But once the workload is finished, we won't see the SQL tab on the history server. It will be helpful if we support SQL UI on the history server so we can analyze it even after its execution.
To support SQL UI on the history server:

I added an onOtherEvent method to the SparkListener trait and post all SQL related events to the same event bus.
Two SQL events SparkListenerSQLExecutionStart and SparkListenerSQLExecutionEnd are defined in the sql module.
The new SQL events are written to event log using Jackson.
A new trait SparkHistoryListenerFactory is added to allow the history server to feed events to the SQL history listener. The SQL implementation is loaded at runtime using java.util.ServiceLoader.

One question that I had from the other PR: why is it okay to merge the event log streams from different SQLContexts into the same UI tab? Are relevant identifiers used by those SQL contexts (such as execution IDs) guaranteed to be unique as long as the SQLContexts belong to the same SparkContext?

Test build #46949 has started for PR 10061 at commit 8222a0c.

Hi @JoshRosen, the execution IDs are from the static SQLExecution object. So I think they are always unique. Yes, previously each SQLContext has its own SQLListener. Since the SQL events are now sent to the same event bus, all SQLListeners will receives SQL events executed from other SQLContexts. If we still want to keep one UI Tab for each SQLContext, I think we need keep something like a SQLContext ID in the SQL event so that the SQLListener knows if it need handle that event. Is there any strong requirement to keep one UI Tab for each SQLContext? I remember some users don't want so many UI tabs because they create many SQLContext.

Test build #46949 has finished for PR 10061 at commit 8222a0c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  *   case class SubExprEliminationState(isNull: String, value: String)\n  * class SparkPlanInfo(\n  * class SQLMetricInfo(\n  * case class SparkListenerSQLExecutionStart(\n  * case class SparkListenerSQLExecutionEnd(executionId: Long, time: Long)\n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/46949/
Test PASSed.

Looks ok to me; can't really comment on the multiple UIs issue (aside from what Carson said being correct, if that functionality is desired).

Single tab is fine, just wanted to understand and make sure that it would be safe.

alright, if no one else has comments I'll merge this after: retest this please.

Test build #47161 has started for PR 10061 at commit 8222a0c.

Test build #47161 has finished for PR 10061 at commit 8222a0c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):\n  * class SparkPlanInfo(\n  * class SQLMetricInfo(\n  * case class SparkListenerSQLExecutionStart(\n  * case class SparkListenerSQLExecutionEnd(executionId: Long, time: Long)\n

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/47161/
Test PASSed.

Merging to master.


Suggestion

Maybe have the message link of the giveaway when giveaway ends?

Also you can use the easy-me module so you can do something like 1m2s

Maybe have the message link of the giveaway when giveaway ends?
You can use giveaway.message.url (using the giveawayEnded event)

Wdym?


[release-v1.3] Manual dep bump for ocp

/hold
until https://github.com/openshift-knative/eventing-kafka-broker/pull/252 is merged
(will rebase than)

/unhold
/assign @pierDipi
this is ready

/lgtm

/test 410-conformance-aws-ocp-410

/retest
On Tue 10. May 2022 at 13:32, openshift-ci[bot] @.***>
wrote:

@matzew https://github.com/matzew: The following tests failed, say
/retest to rerun all failed tests or /retest-required to rerun all
mandatory failed tests:
Test name Commit Details Required Rerun command
ci/prow/410-conformance-aws-ocp-410 f91ace7
https://github.com/openshift-knative/eventing-kafka-broker/commit/f91ace7f126d41f7fee86708e25da11dddbebf6c
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-knative_eventing-kafka-broker/254/pull-ci-openshift-knative-eventing-kafka-broker-release-v1.3-410-conformance-aws-ocp-410/1523980843582754816
true /test 410-conformance-aws-ocp-410
ci/prow/49-conformance-aws-ocp-49 f91ace7
https://github.com/openshift-knative/eventing-kafka-broker/commit/f91ace7f126d41f7fee86708e25da11dddbebf6c
link
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-knative_eventing-kafka-broker/254/pull-ci-openshift-knative-eventing-kafka-broker-release-v1.3-49-conformance-aws-ocp-49/1523980843725361152
true /test 49-conformance-aws-ocp-49
Full PR test history
https://prow.ci.openshift.org/pr-history?org=openshift-knative&repo=eventing-kafka-broker&pr=254.
Your PR dashboard
https://prow.ci.openshift.org/pr?query=is:pr+state:open+author:matzew.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/guide/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
Reply to this email directly, view it on GitHub
https://github.com/openshift-knative/eventing-kafka-broker/pull/254#issuecomment-1122269364,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGPTQFQMPFU34SSS7QWMTVJJCLFANCNFSM5VQXEFDA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sent from Gmail Mobile


pgsql: pq: relation "goose_db_version" already exists

We can deploy Clair successfully a first time, but, subsequent container restarts raise a DB migration error with Goose.
sudo /usr/bin/docker -H unix:///var/run/docker.sock run -it --name=clair --rm -p 6060-6063:6060-6063 -v /etc/clair:/etc/clair quay.io/coreos/clair:v1.2.2 -config=/etc/clair/config.yaml
2016-06-27 02:36:18.102369 I | pgsql: running database migrations
2016-06-27 02:36:18.137254 E | pgsql: pq: relation "goose_db_version" already exists
2016-06-27 02:36:18.137279 C | main: database: could not open database

This seems to be related to goose issue #1 about the proper way to create metadata tables.
We are using a AWS RDS Postgres instance for the DB.
Any ideas on how to fix this?

/cc @stevehorsfield

Hi,
My apologize the delayed answer, I am not sure why I never noticed that issue before.
goose ensures that the table doesn't exist before trying to create it [1]. However, by looking at how it is done, we notice that goose executes a SELECT query on goose_db_version and consider any error as the table missing [2]. Besides the Ping call which makes sure that the connection to the database is alive, this query is the very first to be executed on the database when Clair starts. It would be very useful to know the exact error that this query encounters, either by making goose print it, or by reading the database logs (verbose mode).
Also, could you please share the PostgreSQL version you run on RDS and the connection string configured in Clair?


Automatically check Reference Files are compatible

As we are bundling kits + genomes now, this won#t be an issue anymore!


StakingPage: Support sorting by validator name

Fixes sorting by name on the validator list page. If validator name is not present, sort by oasis address.

I noticed sorting by name also didn't work in the Active delegations and Debonding delegations pages as well as sorting by Amount. Fixed those as well.


Company logos should link to case studies

The logos of companies using Dapr in production should link to a case study or blog post.

Links added to all new case studies


inTouch app dead ?

Are inTouch servers have some issues ?
Since more then one week my Robolinho is not visible in app. I made a reset inTouch from Robolinho menu , conected once again to wifi , removed from inTouch ap , and it can't connect any more.
I can see , that Robolinho is connecting to Wifi every 2 min. ( and pobably is not able to o something in server , and it do reset after 2 min).  Internet is availble from this network , but not works.
I send a mail to Al-Ko support last friday , but till now they answer was a question :" From where  am  I ? " and no further responce....

Yes its dead, add your mail here to get updates.
https://alko-garden.se/drift

Just to remind , my Robolinho went to service for WiFi module exchange , update was not completed , so it  was somehow locked.
Now app works again. Hope also integration can work again for next season...


Tall figures in columns overlap with text

Description
I have a document with two columns of text and a figure that is over half the height of the page.  When I compile my document, the figure is where I expect it, but the following text isn't pushed down far enough, and overlaps both the figure and its caption.  I would expect it to position the text below the caption; there's even enough space to fit a full paragraph down there if it does.
This doesn't happen every time I have a figure this tall.  It seems the paragraphs need to line up just right for it, but I haven't able to find a way to predict when it will or won't happen.
Minimum working example:
#text(weight: 700, 1.75em, lorem(17))
#pad(x: 2em, {
  v(1.1em)
  heading(outlined: false, numbering: none, text(0.85em)[Abstract])
  lorem(150)
  v(1.1em)
})

#show: columns.with(2, gutter: 0.5in)

= Introduction

#lorem(50)

#figure(
  rect(width: 2.3in, height: 1.9in),
  caption: lorem(10),
)

#lorem(50)

#figure(
  rect(width: 2.5in, height: 7in),
  caption: lorem(10),
)

#lorem(30)

#lorem(30)

#lorem(30)

#lorem(30)

The problem is on page 2:

Reproduction URL
https://typst.app/project/rr9vwQjcgU17NGm79GAU5O
Operating system
Web app
Typst version

[X] I am using the latest version of Typst

Minimized:
#v(10cm)
#show: columns.with(2)
#lorem(250)
#block(rect(width: 100%, height: 20cm), breakable: false)
#lorem(30)

The problem is that the unbreakable block overflows in the first region (less height), is then migrated into the second region, but there we do have enough space, so we need to relayout.


HOTFIX - Reporter.sendMetric is sending the keys name as the value

closes #10
Problem
I'm using appoptics-apm-node to send my metrics, but when I used the TAGs I realized that the values of the keys are coming with the value of the TAGs.
To reproduce the problem, I created a simple application and attached below, you need to run specifying your appoptics service key
appoptics-bindings-node-tags-bug.zip
npm install
APPOPTICS_SERVICE_KEY={YOUR-SERVICE-KEY} npm start

Solution
Looking for at the code I realized that in the assignment of the TAGs the same object, the values of the TAGs, was being passed to key and value, probably error by CTRL+C and CTRL+V
The hotfix is here, but I could not run the tests :disappointed:

Released v6.2.1.

Thank you!

:raised_hands:


Y / M keys inside of Configure Cell form trigger keybindings

It appears in the latest version of VS Code, new keyboard shortcuts were introduced to switch between Markdown/Code cells. This is problematic when input's required.

Version: 1.75.1 (Universal)
Commit: 441438abd1ac652551dbe4d408dfcec8a499b8bf
Date: 2023-02-08T21:34:59.000Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Sandboxed: No

Let's see if we can use setContext to make the conditional keyboard shortcut return false: e.g.
notebookEditorFocused && !inputFocus && activeEditor == 'workbench.editor.notebook' && notebookCellType == 'markup'

Fixed by https://github.com/stateful/vscode-runme/pull/210,


Fix: return workreport from running the escalation workflow

I noticed that when running a check flow that has an escalation flow associated to it, the parent executer does not return the workreport from running the escalation flow. This PR fixes that so that the return workreport is from the escalation flow and not from the check flow.
@lshannon @RichardW98 PTAL.
/Jordi

As discussed, it's working as expected so I'm closing this PR :smile:


Add support for graph aliases

Coverage increased (+0.03%) to 91.519% when pulling 7139bb2c5f5a06bafe7ac3db0414e600874da5cc on aliases into 143a954af37f9a2e71f48fe11e4294f2e6211753 on master.


integration over boundary elements

Hello.
I have the following simple question. When I calculate the uniform force on the upper boundary using this code
import numpy as np
from skfem import *
from skfem.visuals.matplotlib import *

m = MeshTri.init_tensor(np.linspace(0, 10, 20), np.linspace(0, 2, 10))
e = ElementTriP1()
gb = InteriorBasis(m, e)
draw(m, node_numbering=True, figsize=(10,10))

# Neumann boundary condition
@LinearForm
def loadingN(v, w):
    return -1.0 * v

top_facets=m.facets_satisfying(lambda x: x[1] == 2.)
top_basis = FacetBasis(m, e, facets=top_facets)

rpN = asm(loadingN, top_basis)

loaded = gb.get_dofs(lambda x: x[1] == 2.0).all()
rpN[loaded]

Output:
array([-0.26315789, -0.52631579, -0.52631579, -0.52631579, -0.52631579,
       -0.52631579, -0.52631579, -0.52631579, -0.52631579, -0.52631579,
       -0.52631579, -0.52631579, -0.52631579, -0.52631579, -0.52631579,
       -0.52631579, -0.52631579, -0.52631579, -0.52631579, -0.26315789])

shouldn't i get a result like
Output:
array([-0.25, -0.5, -0.5, -0.5, -0.5,
       -0.5, -0.5, -0.5, -0.5, -0.5,
       -0.5, -0.5, -0.5, -0.5, -0.5,
       -0.5, -0.5, -0.5, -0.5, -0.25])

because we are using piecewise linear continuous P1 finite element.

If you split the upper boundary to 20 elements instead of 19, does it change the result? I'm now on my phone so cannot test it out.

If you split the upper boundary to 20 elements instead of 19, does it change the result? I'm now on my phone so cannot test it out.

Yes, that was the problem. I misunderstood how np.linspace works. Thank you.


Airflow orchestrator improvements

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to the documentation, I have updated the documentation accordingly.
[x] I have added tests to cover my changes.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Describe changes

Airflow orchestrator doesn't start by itself now but requires a CLI call (same for shutting down)
Added ability to monitor an orchestrator via the CLI

This PR does not update the docs with the new Airflow Orchestrator workflow (yet). I will add it here or in a separate PR once we think the usage is how we want it to be.


chore: update readme content

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/terraform?version=dev:72dd21e0603b9117fa3bdabb0e8d6b1e0e48aad9

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/circleci/terraform?version=dev:58a05dc080edf1d70fb877b5bfaacadd0f1b2b60


Use /usr/bin/env bash for portability (IDFGH-708)

bash is not always installed in /bin/bash.  This could be related to
issue #2600 (or at least, manifests with similar symptoms).

This change was performed mechanically, with:
$ find . -name \*.sh -exec sed -i "" -e 's|^#!.*bin/bash|#!/usr/bin/env bash|' {} +

(Note that BSD sed -i "" is basically identical to GNU sed -i.)

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

Thanks, @igrr !

@cemeyer No problem, sorry for the delay and sorry that I had to make a new commit rather than reusing the commit you have authored (it was a pain to rebase... again, due to the delay).

No worries, this is definitely the kind of thing it makes sense to just re-apply mechanically instead of trying to rebase.


Lifecycle for RxReact.Component

I'm trying to extend Component as well as use FuncSubject. The issue is that Component overrides componentWillMount where I'd like to create the FuncSubject. Any tips on what to do? Building on the comment tutorial from React's documentation, I've illustrated my present workaround below. I'd be happy to submit any PRs, but I figured I'd ask first.
export class CommentComponent extends RxReact.Component {
  getStateStream () {
    this.makeComment = RxReact.FuncSubject.create();
    this.makeComment
      .forEach(makeComment);

    return commentListStream.map(list => {
      return { data: list }
    });
  }

  render () {
    return (

Comments

        <CommentList data={this.state.data} />
        <CommentForm onCommentSubmit={this.makeComment} />

    );
  }
}

I don't really understand your problem here, Creating FuncSubject in getStateStream is a good pattern.
Also if you wish to have a component will mount just use super:
class MyComp extends RxReact.Component {
  componentWillMount() {
    super.componentWillMount();
    ....
  }
  ....
}

Is there something else ?

Using super would work. Thanks.
My problem with putting that in getStateStream is the incongruence between the actions and the name of the method. I'd be making a Subject where I should only be retrieving an Observable to be used as my component's state; "query xor update" would be violated.

To be honest I generally use ES7 class property declaration :
class MyComponent extends RxReact.Component {
  buttonClick = FuncSubject.create();
  getStateStream() {
    return this.buttonClick.map(...)
  }
}

you can also use the constructor