Large numbers get truncated and final digits replaced with 00s when using Execute dbt SQL

Expected behavior
I have recently noticed that when you run Execute dbt SQL against a jinja sql file and there are large numbers in the results any numbers larger than 17 digits get their final digits replaced with 000s.
I am using snowflake as my backend.
Reproducable example
Create a sql file:
select<PHONE_NUMBER>23456789123 as id

This will return:

id

123456789123456800000

Actual behavior
If you run the same thing through the snowflake ui (or indeed the official snowflake plugin in vscode) you get:
select<PHONE_NUMBER>23456789123 as id

id

123456789123456789123

as expected
Steps To Reproduce
See my description above
Log output/Screenshots

Operating System
macos
dbt version
1.6.1
dbt Adapter
Snowflake
dbt Power User version
0.17.7
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

This issue with large numbers being rounded in the query results is likely due to the limitations of JavaScript's Number data type. JavaScript uses 64-bit floating point numbers to represent numbers, which can accurately represent integers up to 15 digits long. Any integer larger than that may lose precision.
I will push out a fix soon.

@louis-vines could you please upgrade to v0.31.4 and check if the issue has been resolved?


The redis queue takes the protobuf data warning

操作系统：
Linux version 2.6.32-431.29.2.el6.x86_64<EMAIL_ADDRESS>分支：master

This error indicates that a proto message contained invalid UTF-8 for a proto message with a string field.
The protobuf specification says regarding strings:

A string must always contain UTF-8 encoded or 7-bit ASCII text.

Instead, you should switch the proto field type to the bytes.

Closing as stale.


PORTALS-2806, add a DOI link if available

This may not be right, but this is limited to the ObservationCard, which is only used by the NF portal by utilizing the Timeline plot.

Will ask Robert to evaluate on the live staging site.


Trust commands favoring player names over explicit group names

If a user's name starts with the name of a group, the command will autocomplete to the user instead of using the group.
For example, after using /at default, it will favor the user defaultcrafter over the group named default
https://cdn.discordapp.com/attachments/215593150494801930/449381584173400075/unknown.png
Perhaps adding a feature which requires a g: prefix for groups could help fix this issue?

This will be resolved in GP 5.0.0 which will allow you to use context.


[RESOLVED] High ICMP ping response time

Problem started at 02:08:14 on 2023.05.15
Problem name: High ICMP ping response time
Host: ZO-FG
Severity: Warning
Operational data: Value: 190ms
Original problem ID: 20605
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23125&eventid=20605

Problem has been resolved in 5m 0s at 02:13:14 on 2023.05.15
Problem name: High ICMP ping response time
Host: ZO-FG
Severity: Warning
Original problem ID: 20605


IsARSupportedOnDevice returns true on LG G6

Seems like the utils function IsARSupportedOnDevice returns true on a LG G6 phone, but it does not support ARCore. https://developers.google.com/ar/discover/ .
Are there any ways to check the types of phones that returns true from the IsARSupportedOnDevice function?

Hi @cjrorvik, you could use something like this React Native module:https://github.com/rebeccahughes/react-native-device-info to extract more device info like the model type and manufacturer.
You can also modify our check and create your own native module. The method isARSupportedOnDevice wraps the following Android Java native code:
/**
     * Checks if ARCore is compatible with the target device. This does <i>not</i> indicate whether ARCore is
     * installed. If this method returns false, attempts to create {@link ViroViewARCore} will throw
     * an exception.
     *
     * @param context The {@link Context} of your application.
     * @return True if the current device is compatible with ARCore.
     */
    public static boolean isDeviceCompatible(Context context) {
        ArCoreApk.Availability availability = ArCoreApk.getInstance().checkAvailability(context);
        Log.i(TAG, "ARCore availability check returned [" + availability   + "]");
        if (availability == ArCoreApk.Availability.UNSUPPORTED_DEVICE_NOT_CAPABLE) {
            return false;
        }
        else {
            return true;
        }
    }

We return true on every value of ArCoreApk.Availability flag except UNSUPPORTED_DEVICE_NOT_CAPABLE. If you write your own native module to check, you may want to return false for UNKNOWN_ERROR or UKNOWN_CHECKING.
Here's a list of all possible return values: https://developers.google.com/ar/reference/java/com/google/ar/core/ArCoreApk.Availability
Hopefully the above can help you mitigate.
I've added a bug in our backlog so we can look into this.


Add new images

Description of change
New images from @JSto91
As always: before/after
Wiki
Type of change

[ ] Bug fix (a non-breaking change which fixes an issue)
[ ] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation Fix

Change checklist

[x] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

We are not sure if we can merge this. While we appreciate the improved images, the images are currently generated from a draw.io file, part of the repo. This allows anyone to submit a PR for suggested changes to DIDComm, including updated graphics. Merging this in removes that flexibility and might "centralize" updates to DIDComm to only IOTA Foundation members.

Nice, thanks for the information :)
I'll take a look at draw.io. Maybe it can be stylized. If you are ok with it :)

We are not sure if we can merge this. While we appreciate the improved images, the images are currently generated from a draw.io file, part of the repo. This allows anyone to submit a PR for suggested changes to DIDComm, including updated graphics. Merging this in removes that flexibility and might "centralize" updates to DIDComm to only IOTA Foundation members.

Hmm. I saw that it's draw.io graphs but didn't see the file. So i thought it was closed development. Thanks for the heads up :)

Thanks for the information :)
I'll take a look at draw.io. Maybe it can be stylized. If you are ok with it :)

It is. To a certain degree at least. I never really changed the styling 😅

Thanks for the information :)
I'll take a look at draw.io. Maybe it can be stylized. If you are ok with it :)

It is. To a certain degree at least. I never really changed the styling 😅

Yeah i looked into it. You can predefine colors etc into the palette and also the basic shapes. Don't know if you can add/import custom shapes. Need to dig in further 😄. I'll look if i can come up with some solution.

Update: So i looked for solutions and there are 3 that could work:
Option 1:
Create custom Icon/Shape Library for draw.io which is located in the Repository
How this would work (Icon/Shape Library already imported):
- User forks this Repo
- Opens draw.io
- imports Library via Github (selects library file from his repo)
- has access to the Icon/Shapes
Pro:
- draw.io is free
- no signup required
- can be linked with Github
Con:
- still limited style option
- color (for fonts) would need to be changed manually
- needs a "readme" somewhere for the colors (Color Hex)
- different font

Option 2:
Publish seperate Figma-File so anyone can duplicate it and do changes
Pro:
- free
- fully customizable
Con:
- Needs to upload manually to Github (which isn't a big deal imo)
- Needs to be a link to the published Figma somewhere in the wiki
- Signup required (They have the option for SAML SSO but i am not familiar with that. Don't know if this makes it any better)

Option 3:
Upload the images and leave the original (from draw.io) in another folder in the Repo.
If someone wants to change something in the flowchart, he can do it with the original-file in draw.io and replace the current-image with the updated-image.
After the updated img is online, i can stylize it.
In my opinion the best option.
But what do you think? @Dr-Electron @JelleMillenaar

Hi guys,
really appreciate the effort! My thoughts are as following:
Option 1 - We shouldn't change the shapes, they have meaning in the BPMN Notation. A thick outline means something different then a thin one, then a dotted one. If we can enhance the diagrams with changing colors, or more generally changes that don't change the meaning that might an interesting option.
Option 2 - since we want to stick to BPMN and potentially utilize other features or "shapes" it would mean to recreate the whole spec in Figma. I think that would be an insane amount of work.
Option 3 - this puts a lot of work on you and also creates a dependency. How long does it take you to respond to changes on average? Is there a fallback? Also we shouldn't deviate from the shapes, as they have meaning. So it would only be minor recolor, maybe different backgrounds and fonts.
I lean towards Option 1 if it improves the look without changing the meaning. We need to keep in mind that we would want to use the whole spec, so be able to drag in other shapes at any time. This Option is only worthwhile if it doesn't complicate the workflow significantly.
Option 2 and 3 create too much overhead in my Opinion.
I think we should consider leaving it as is as a very valid option. We can spice it up on a per diagram basis for special use cases like presentations or blog post, but leaving the spec as is has the most streamlined workflow.

Hi Eike,
thank you for the information :). In this case your Option 1 makes more sense i agree. I will use the original flowchart and just change some colors (Background etc) and leave the shapes/line-style/etc as they are. If that is fine.

Hi guys, really appreciate the effort! My thoughts are as following: Option 1 - We shouldn't change the shapes, they have meaning in the BPMN Notation. A thick outline means something different then a thin one, then a dotted one. If we can enhance the diagrams with changing colors, or more generally changes that don't change the meaning that might an interesting option. Option 2 - since we want to stick to BPMN and potentially utilize other features or "shapes" it would mean to recreate the whole spec in Figma. I think that would be an insane amount of work. Option 3 - this puts a lot of work on you and also creates a dependency. How long does it take you to respond to changes on average? Is there a fallback? Also we shouldn't deviate from the shapes, as they have meaning. So it would only be minor recolor, maybe different backgrounds and fonts.
I lean towards Option 1 if it improves the look without changing the meaning. We need to keep in mind that we would want to use the whole spec, so be able to drag in other shapes at any time. This Option is only worthwhile if it doesn't complicate the workflow significantly. Option 2 and 3 create too much overhead in my Opinion.
I think we should consider leaving it as is as a very valid option. We can spice it up on a per diagram basis for special use cases like presentations or blog post, but leaving the spec as is has the most streamlined workflow.

Everything you say makes sense. But also boring specs have the right to look beautiful :trollface:
So let's try option 1

Hey 😃
so i re-colored the current draw.io flowchart.
Example: https://critical94.github.io/iota-wiki/learn/future/future-of-iota
Question: We used the max-width of the content so the image isn't too small anymore. I would like to resize/move the content of the flowchart a little bit so it doesn't look cramped.
What do you think about the colors? Something you don't like? Let me know :)

Hey 😃 so i re-colored the current draw.io flowchart. Example: https://critical94.github.io/iota-wiki/learn/future/future-of-iota
Suggestion: We used the max-width of the content so the image isn't too small anymore. I would like to resize/move the content of the flowchart a little bit so it doesn't look cramped.
What do you think about the colors? Something you don't like? Let me know :)

Looking very good! Couple of issues came up discussing it internally:

the second decision block for ´Require information?´ does not have an orange arrow in the negative case.
some blocks are yellow and some are teal inconsistently. ´Sign verifiable credential´ might be meant to be yellow instead of teal?
Maybe the send and receive blocks should be the same color. The contrast on the receive blocks are too low to read comfortably.

Any update on this PR. Do we want to stick with our current images or incorporate the feedback from Eike. @JSto91 & @Dr-Electron :)

I really love the new banners.
Also really cool that we now have a flowchart lib. But shouldn't we make it more general? So a basic IOTA lib?
Or are there thing that will be different for identity? Do other frameworks even use flowchart so that we could reuse?


build(deps):  Raise OpenVDB minimum to 9.0

Soon we'll raise the minimum OpenEXR to 3.1, and OpenVDB 9.0 is the first version to support that. And because OpenVDB has Imath types in its public APIs, it's really hard to mix and match our using an OpenEXR/Imath 3 internal to OIIO with an OpenVDB that uses an OpenEXR/IlmBase 2.

Any objections to this?

Does anybody think there is merit to continuing to support OpenVDB older than 9.0? And, really, we simply cannot, given our decision to bump the minimum OpenEXR version to 3.x, which was not supported until OpenVDB 9. So asking for OpenVDB < 9 is asking to keep supporting OpenEXR 2.4.
I think there is no question that we should merge this, but thought I'd give one last chance...


fix: fix checkstatus response code

Type of change:

[x] Bugfix
[ ] New feature provided
[ ] Improve performance
[ ] Backport patches

What this PR does / why we need it:

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?

Codecov Report
Attention: 878 lines in your changes are missing coverage. Please review.

Comparison is base (3604a24) 39.71% compared to head (04d784e) 36.29%.
Report is 192 commits behind head on main.

Files
Patch %
Lines

...phere-operator/pkg/controllers/chaos_controller.go
0.00%
276 Missing :warning:

...rdingsphere-operator/pkg/kubernetes/pod/builder.go
0.00%
118 Missing :warning:

...perator/pkg/controllers/storage_node_controller.go
26.58%
96 Missing and 20 partials :warning:

...operator/pkg/controllers/auto_scaler_controller.go
0.00%
89 Missing :warning:

pitr/agent/internal/pkg/opengauss.go
2.70%
36 Missing :warning:

...ator/cmd/shardingsphere-operator/manager/option.go
6.06%
31 Missing :warning:

...hardingsphere-operator/pkg/kubernetes/resources.go
0.00%
28 Missing :warning:

...ere-operator/pkg/kubernetes/container/container.go
31.25%
22 Missing :warning:

shardingsphere-operator/pkg/kubernetes/helpers.go
46.15%
20 Missing and 1 partial :warning:

...perator/pkg/controllers/compute_node_controller.go
0.00%
20 Missing :warning:

... and 15 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #460      +/-   ##
==========================================
- Coverage   39.71%   36.29%   -3.42%
==========================================
  Files          51       59       +8
  Lines        6083     6620     +537
==========================================
- Hits         2416     2403      -13
- Misses       3448     3990     +542
- Partials      219      227       +8

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


feat(accidental): ✨ add isNatural getter

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
997

Relevant Lines:
997

💛  - Coveralls


Add collection for Reactive Monolith Frameworks (#10086)

Collection Title: Reactive Monolith Frameworks
This commit introduces the "Reactive Monolith Frameworks" collection with the ID 10086. The purpose of this collection is to list and highlight frameworks that provide reactive UI functionalities within a monolithic architecture. Unlike traditional full-stack frameworks, these reactive monolith frameworks specialize in creating highly interactive and dynamic user interfaces without relying on separate API calls from the client side. They handle UI reactivity and state management primarily on the server side, leveraging technologies such as WebSockets for real-time updates. They can be interesting alternatives to Full-stack client-side front-ends such as React/Vue etc.
The frameworks included in this collection are:

Livewire (livewire/livewire): A full-stack framework for Laravel that makes building dynamic interfaces simple, without leaving the comfort of Laravel.

Django Unicorn (adamghill/django-unicorn): A reactive framework for Django that is similar to LiveView in Phoenix, focusing on simplifying the creation of interactive web applications.

Phoenix LiveView (phoenixframework/phoenix_live_view): Part of the Elixir Phoenix framework, LiveView enables rich, real-time user experiences with server-rendered HTML.

Hotwire (hotwired): An approach by the Ruby on Rails community to offer modern and reactive web applications using HTML over the wire.

Inclusion Criteria:
The primary criteria for including a framework in the "Reactive Monolith Frameworks" collection are as follows:

Monolithic Architecture: The framework should follow a monolithic architecture, where both the client-side and server-side codebases are tightly integrated and managed as a single unit.
Server-Side Reactivity: A key characteristic is the framework's ability to manage UI reactivity and state updates predominantly on the server side, minimizing the need for client-side JavaScript or external APIs for UI updates.
Real-Time Interaction: The framework must support real-time, dynamic user interfaces, enabling instant updates to the UI in response to server-side state changes.
Community and Maturity: Preference is given to frameworks that have an active community, good documentation, and a track record of stability and reliability in production environments.

Exclusion Criteria:
Frameworks will be excluded if they primarily rely on API calls for client-server communication, focus extensively on client-side rendering, or fall under the category of decoupled, microservice-oriented architectures. The goal is to spotlight frameworks that challenge traditional web application structures by leveraging server-side capabilities to drive the UI dynamically.
This collection aims to provide developers and enthusiasts with a curated list of frameworks that push the boundaries of traditional web application development paradigms, focusing on server-side reactivity and minimal JavaScript usage for client-side interactions.
Kindly consider this addition to enhance the OSS Insight's repository with a collection that represents an evolving area in web application development.

@SimbaNinja917 Interesting, hotwired should be replaced with Rails, right? Can we also include Next.js, and server action seems to meet the requirements


How to control a native application menu?

The question is related to the native menu that is shown on window frame on Windows or in the system bar on Mac
Probably this is the relevant subject that I suspect could have a matter:
https://developer.apple.com/documentation/uikit/uimenusystem/3327314-mainsystem?language=objc

There is currently no support for this in the core library but given that the native window handle is exposed by the library then I think you could implement this for Linux and Windows at least. I am not sure exactly what is doable on macOS outside of the core library.

Best solution I have found so far is below... Works well with webview.
https://github.com/getlantern/systray
Another is fyne systray

There is currently no support for this in the core library but given that the native window handle is exposed by the library then I think you could implement this for Linux and Windows at least. I am not sure exactly what is doable on macOS outside of the core library.

Can you point to where we can access the window handle?
I'd like to do some thaangs to it.

@SharkFourSix You can retrieve the window handle with webview_get_window().

Best solution I have found so far is below... Works well with webview.
https://github.com/getlantern/systray
Another is fyne systray

I tried, but it didn't work for me., can please provide a code example .


.Page.Store is not working in production mode

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.104.0+extended darwin/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes
Issue
Variables set with .Page.Store.Set are accessible with .Page.Store.Get only when using hugo server, but not when building the website with hugo command.
Source code
I was following the examples from https://gohugo.io/content-management/diagrams/#mermaid-diagrams
My content file content/index.md (to trigger the execution of the render hook):
```mermaid
Example mermaid code
```

The render hook layouts/_default/_markup/render-codeblock-mermaid.html:

  {{- .Inner | safeHTML }}

{{ .Page.Store.Set "hasMermaid" true }}

The template layouts/single.html:

Mermaid variable: {{ default false (.Page.Store.Get "hasMermaid") }}

      {{ .Content }}

The file config.yml is empty
Running with hugo server displays the hasMermaid variables as it should, but after building the website with hugo it is not working.
Apparently, there is difference in how the render hooks are handled in dev and prod environments.
Reproducible minimal example:
git clone https://github.com/ivanduka/page-store-bug
cd page-store-bug
hugo server

This will display the variable that was set in a render hook:

However, when building the website, this variable is not retrievable:
hugo && npx http-server public

In this case the variable is not set:

I also tested the same source code with the Hugo from the first release that introduced .Page.Store (https://github.com/gohugoio/hugo/releases/tag/v0.93.0) and the same issue is there, so this is probably not a regression.

Mermaid variable: {{ default false (.Page.Store.Get "hasMermaid") }}

      {{ .Content }}

The render hook is invoked in `.Content´ where the variable gets set. You need to switch the order.


Point Cloud visualization

I try to get the point could from range image using
from waymo_open_dataset.v2.perception.utils import lidar_utils as _lidar_utils
but I have the following error
  File "~/lidar-sensor/venv/lib/python3.10/site-packages/waymo_open_dataset/v2/perception/utils/lidar_utils.py", line 92, in convert_range_image_to_cartesian
    if calibration.beam_inclination.values:
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

changing
 if calibration.beam_inclination.values:
to
 if calibration.beam_inclination.values.any:
return the point cloud and I'm able to visualize it using open3d. Is this a bug or something with my environment?
I use
Python 3.10.10

Hi @atanasko ,
Thank you for flagging this issue. Depending on how calibration is initialized, calibration.beam_inclination.values can be None, list or numpy array. When it's a numpy array, this error shows up. A hot fix you may also use is changing this line into
  if calibration.beam_inclination.values is not None: to cover all cases.
We'll fix it in the next commit.

hi @Jingwei,
Thank you! I'll use local fix for the moment and try changes after committed.


Users should be able to close embeded photos or videos

Users should be able to close embedded photos or videos, like with irccloud where embedded/inline content can be dismissed if you don't want it to take up space in the chat. Or maybe minimize embedded content.

:+1:


Question: how to use maven resource filtering?

Hello,
Let me say it's a great project and it's a real pleasure to use in our development life cycle.
However, I'm having a hard time with one particular use case. I'm not particular sure whether it's the right place to ask question. Please forward me to right place if it is not.

The question:
How does one use properly maven resource filtering capability? I've found mentioning of assembly filter flag in some other issues. I've tried, but I kinda failed / didn't like the result.
Let me explain my use case first:

I have Docker file ADD-ing some configuration file from src/main/docker
That particular file contains artifactId and artifact version.
I would like to have that information to be provided / injected by maven resource filtering.

What I've tried:

Assembly <fileSet>, which took the original file and placed it somewhere at
target/docker/registry-xyz.com/artifact/0.0.1-SNAPSHOT/build/maven/home/username/path1/path2/target/docker/registry-xyz.com/artifact/0.0.1-SNAPSHOT/build/maven/MY_FILE

I'm struggling to find the proper workaround and come up with concise and clear configuration snippet to get it done.
Any suggestions, maybe some links to examples or documentation etc ...  I would really appreciate that...

First of all thanks for using d-m-p :)
Currently filtering is not supported yet when using Dockerfiles directly (see #205 which should be implemented soon).
For an asemmbly <files> this should work however when setting the property filtered. The target in this fileset should be relative to the specified basedir within the Docker container (not somewhere below target).
The following snippet is not tested but should you make the usage clear:
<files>
    <file>
      <source>src/main/docker/app.properties</source>
      <outputDirectory>/</outputDirectory>
      <filtered>true</filtered>
    </file>
</files>

This will put an app.properties filtered into the top-level dir, which is the assemblies basedir (/maven in the target image by default).
Does this answer your question ?

Thanks, it helps a lot.
First of all I got one more idea to try, second I got the place to look for updates regarding this use case (the issue you have so kindly linked).
Thanks. I will close this issue as dup for linked issue.

This is a snippet from our pom that uses a Dockerfile to generate the image; The docker file has maven replacement properties in the FROM line
FROM ${docker.rc.registry.host}/${docker.tomcat.namespace}:${tomcat.base.image.tag}
Each of the ${} is replaced by maven when copying the resource to the build directory, target.  The target folder set is then used as input to building the image.

maven-resources-plugin

copy
prepare-package

copy-resources

${project.build.directory}/${project.build.finalName}
false

${*}

src/main/resources
true

Dockerfile
scripts/**
webapp/WEB-INF/classes/properties/service-discovery.properties

src/main/resources
false

webapp/conf/**

Chris Snider
Senior Software Engineer
Intelligent Software Solutions, Inc.
[Description: Description: Description<EMAIL_ADDRESS>From: Roland Huß<EMAIL_ADDRESS>Sent: Monday, November 16, 2015 12:41 PM
To: rhuss/docker-maven-plugin<EMAIL_ADDRESS>Subject: Re: [docker-maven-plugin] Question: how to use maven resource filtering? (#330)
First of all thanks for using d-m-p :)
Currently filtering is not supported yet when using Dockerfiles directly (see #205https://github.com/rhuss/docker-maven-plugin/issues/205 which should be implemented soon).
For an asemmbly  this should work however when setting the property filteredhttp://maven.apache.org/plugins/maven-assembly-plugin/examples/single/filtering-some-distribution-files.html. The target in this fileset should be relative to the specified basedir within the Docker container (not somewhere below target).
The following snippet is not tested but should you make the usage clear:

<file>

  <source>src/main/docker/app.properties</source>

  <outputDirectory>/</outputDirectory>

  <filtered>true</filtered>

</file>

This will put an app.properties filtered into the top-level dir, which is the assemblies basedir (/maven in the target image by default).
Does this answer your question ?
—
Reply to this email directly or view it on GitHubhttps://github.com/rhuss/docker-maven-plugin/issues/330#issuecomment-157147260.

Hi @leonardinius @vberruchon,
below is my answer (similar to @chris-snider):

setup maven-resources-plugin:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-resources-plugin</artifactId>
        <executions>
          <execution>
            <id>filter-dockerfiles</id>
            <phase>process-resources</phase>
            <goals>
              <goal>copy-resources</goal>
            </goals>
            <configuration>
              <resources>
                <!-- # Filtered Resources -->
                <resource>
                  <directory>${project.basedir}/src/main/docker</directory>
                  <filtering>true</filtering>
                  <includes>
                    <include>Dockerfile</include>
                  </includes>
                </resource>
                <!-- # Unfiltered Resources -->
                <resource>
                  <directory>${project.basedir}/src/main/docker</directory>
                  <filtering>false</filtering>
                  <excludes>
                    <exclude>Dockerfile</exclude>
                  </excludes>
                </resource>
              </resources>
              <outputDirectory>${project.build.directory}/docker</outputDirectory>
            </configuration>
          </execution>
        </executions>
      </plugin>

the <outputDirectory>${project.build.directory}/docker</outputDirectory> is important for 2 reasons a) when you do resource filtering you should always send the filtered (modified) resource to the build output directory (${project.build.directory}), and b) this acts as the Dockerfile input for the Docker maven plugin below

setup docker-maven-plugin:

      <plugin>
        <groupId>org.jolokia</groupId>
        <artifactId>docker-maven-plugin</artifactId>
        <configuration>
          <images>
            <image>
              <name>${groupbyinc.docker.image.name}:${project.version}</name>
              <alias>${project.artifactId}</alias>
              <build>
                <assembly>
                  <dockerFileDir>${project.build.directory}/docker</dockerFileDir>
                </assembly>
              </build>
            </image>
          </images>
        </configuration>
        <executions>
          <execution>
            <id>build-docker-image</id>
            <goals>
              <goal>build</goal>
            </goals>
            <phase>package</phase>
          </execution>
          <execution>
            <id>push-docker-image</id>
            <goals>
              <goal>push</goal>
            </goals>
            <phase>deploy</phase>
          </execution>
        </executions>
      </plugin>

Hi @leonardinius @vberruchon,
below is my answer (similar to @chris-snider):
Step 1: setup maven-resources-plugin:
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-resources-plugin</artifactId>
        <executions>
          <execution>
            <id>filter-dockerfiles</id>
            <phase>process-resources</phase>
            <goals>
              <goal>copy-resources</goal>
            </goals>
            <configuration>
              <resources>
                <!-- # Filtered Resources -->
                <resource>
                  <directory>${project.basedir}/src/main/docker</directory>
                  <filtering>true</filtering>
                  <includes>
                    <include>Dockerfile</include>
                  </includes>
                </resource>
                <!-- # Unfiltered Resources -->
                <resource>
                  <directory>${project.basedir}/src/main/docker</directory>
                  <filtering>false</filtering>
                  <excludes>
                    <exclude>Dockerfile</exclude>
                  </excludes>
                </resource>
              </resources>
              <outputDirectory>${project.build.directory}/docker</outputDirectory>
            </configuration>
          </execution>
        </executions>
      </plugin>

Note: the <outputDirectory>${project.build.directory}/docker</outputDirectory> is important for 2 reasons a) when you do custom resource filtering you should always send the filtered (modified) resource to the build output directory (${project.build.directory}) as good practice, and b) this acts as the Dockerfile input for the Docker maven plugin below
Step 2: setup docker-maven-plugin:
      <plugin>
        <groupId>org.jolokia</groupId>
        <artifactId>docker-maven-plugin</artifactId>
        <configuration>
          <images>
            <image>
              <name>${docker.image.name}:${project.version}</name>
              <alias>${project.artifactId}</alias>
              <build>
                <assembly>
                  <dockerFileDir>${project.build.directory}/docker</dockerFileDir>
                </assembly>
              </build>
            </image>
          </images>
        </configuration>
        <executions>
          <execution>
            <id>build-docker-image</id>
            <goals>
              <goal>build</goal>
            </goals>
            <phase>package</phase>
          </execution>
          <execution>
            <id>push-docker-image</id>
            <goals>
              <goal>push</goal>
            </goals>
            <phase>deploy</phase>
          </execution>
        </executions>
      </plugin>

You can now add Maven variable interpolation ${...} inside your src/main/docker/Dockerfile, for example I do something like:
FROM ${docker.repo}/${docker.groupId}/base:${project.version}
MAINTAINER ${docker.maintainer}
...

using properties such as:
  <properties>
    <docker.repo>docker.example.com</docker.repo>
    <docker.groupId>example</docker.groupId>
    <docker.artifactId>${project.artifactId}</docker.artifactId>
    <docker.image.name>${docker.repo}/${docker.groupId}/${project.artifactId}</docker.image.name>
    <docker.maintainer>"Example Engineering" <eng@example.com></docker.maintainer>
  </properties>

Setting <dockerFileDir>${project.build.directory}/docker</dockerFileDir> makes my build fail with Execution docker of goal io.fabric8:docker-maven-plugin:0.15.16:build failed: A tar file cannot include itself.  probbably beacuse it causes the docker-build.tar to reference itself. When I open the tar it has a Dockerfile at root, a maven directory, and a directory structure corresponding to the docker repository with tmp, build and work folders.


No Instructions on README for install (documentation totally missing)

There is no explanation of any official merit on how to install or use this software that I can find. It would be appreciated if actual installation instructions were provided, there are multiple ways to download this file on the page and it is not apparent what to do with the file.

Hi, installation instructions are now added to the README file.


Account summary - active markets

Update to copy, 'open markets' to 'active markets'
Can remove the copy next to the search icon
Update to column label copy
Update to the format of the % values in rows

most of this was updated, maybe it isn't on sneakpreview yet. Ryan is working in getting the backend numbers for those so everything is zero as a placeholder.
do we want all places where 0% is shown to be 0.00%? like here:

make mobile and desktop match as so:


[sram_ctrl] Fix sram error checking and byte sequencing

Should fix #8905
Previously, the error checking was mostly done downstream of
sram_byte. This meant that illegal write transactions would
become correctly transformed by the sram_byte module, and thus
the would-be error silenced.
This PR moves all the error checking upstream of the sram byte
module and passes the error through if it is observed. This is
more consistent error behavior.
The documentation is also updated with a high level overview on
how the adapater sram behaves.

Signed-off-by: Timothy Chen<EMAIL_ADDRESS>

oops, I still see these assertion errors. You can reproduce it by running sram_ctrl_csr_mem_rw_with_rand_reset with this PR #8701

run.log:UVM_ERROR @   9328562 ps: (tlul_adapter_sram.sv:498) [ASSERT FAILED] TlOutKnown_A
run.log:UVM_ERROR @   9328562 ps: (prim_fifo_sync.sv:173) [ASSERT FAILED] DataKnown_A
run.log:UVM_ERROR @   9328562 ps: (sram_ctrl.sv:412) [ASSERT FAILED] RamTlOutKnown_A
run.log:UVM_ERROR @   9370229 ps: (tlul_adapter_sram.sv:502) [ASSERT FAILED] WdataOutKnown_A

oops, I still see these assertion errors. You can reproduce it by running sram_ctrl_csr_mem_rw_with_rand_reset with this PR #8701

run.log:UVM_ERROR @   9328562 ps: (tlul_adapter_sram.sv:498) [ASSERT FAILED] TlOutKnown_A
run.log:UVM_ERROR @   9328562 ps: (prim_fifo_sync.sv:173) [ASSERT FAILED] DataKnown_A
run.log:UVM_ERROR @   9328562 ps: (sram_ctrl.sv:412) [ASSERT FAILED] RamTlOutKnown_A
run.log:UVM_ERROR @   9370229 ps: (tlul_adapter_sram.sv:502) [ASSERT FAILED] WdataOutKnown_A

let me have a look.

oops, I still see these assertion errors. You can reproduce it by running sram_ctrl_csr_mem_rw_with_rand_reset with this PR #8701

run.log:UVM_ERROR @   9328562 ps: (tlul_adapter_sram.sv:498) [ASSERT FAILED] TlOutKnown_A
run.log:UVM_ERROR @   9328562 ps: (prim_fifo_sync.sv:173) [ASSERT FAILED] DataKnown_A
run.log:UVM_ERROR @   9328562 ps: (sram_ctrl.sv:412) [ASSERT FAILED] RamTlOutKnown_A
run.log:UVM_ERROR @   9370229 ps: (tlul_adapter_sram.sv:502) [ASSERT FAILED] WdataOutKnown_A

let me have a look.

@weicaiyang and i took a look at the failures. I believe it is happening because a partial write transaction was issued when the memory is uninitialized.  This causes tlul_sram_byte to issue a read to uninitialized space and thus returning all x's.
@weicaiyang believes the right fix is to have the test automatically initialize the memory, but that's probably a different PR.

oops, I still see these assertion errors. You can reproduce it by running sram_ctrl_csr_mem_rw_with_rand_reset with this PR #8701

run.log:UVM_ERROR @   9328562 ps: (tlul_adapter_sram.sv:498) [ASSERT FAILED] TlOutKnown_A
run.log:UVM_ERROR @   9328562 ps: (prim_fifo_sync.sv:173) [ASSERT FAILED] DataKnown_A
run.log:UVM_ERROR @   9328562 ps: (sram_ctrl.sv:412) [ASSERT FAILED] RamTlOutKnown_A
run.log:UVM_ERROR @   9370229 ps: (tlul_adapter_sram.sv:502) [ASSERT FAILED] WdataOutKnown_A

let me have a look.

@weicaiyang and i took a look at the failures. I believe it is happening because a partial write transaction was issued when the memory is uninitialized. This causes tlul_sram_byte to issue a read to uninitialized space and thus returning all x's.
@weicaiyang believes the right fix is to have the test automatically initialize the memory, but that's probably a different PR.

Thanks Tim. I made a fix in the DV side.


[DO NOT MERGE] Fix composer version conflict on Travis

Jira
n/a
Summary
Update cweagans/composer-patches to fix Travis build failure.
Details
Travis is now using Composer 2, which is incompatible with the current version of cweagans/composer-patches. See failing build: https://travis-ci.com/github/boltdesignsystem/bolt/jobs/407817182#L461
Updating this package to 1.7.0 fixes the issue.
How to test
Build is passing: https://travis-ci.com/github/boltdesignsystem/bolt/builds/192947578

Closing in lieu of https://github.com/boltdesignsystem/bolt/pull/2006


Charts[Network Node]: Only allow jrs profile and remove patched Dockerfile

In order to support "main" profile and initial testing, we had to create patched version of Dockerfile and download openjdk. Since we only need to use "jrs" profile, it is time to remove all those patched files and cleanup codebase.

:tada: This issue has been resolved in version 0.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


New tag component with suggestions

Adding to existing tag was getting complicated, and the focus, blur events were easy on the text edit

Fixes for autocomplete actively listening to keyboard shortcuts even with removed from the UI

Customisable placeholder, classname for text edit

Hi @marianamarasoiu thanks for testing it - I have fixed the following issues

Focus is now handled properly - scrolling and the focus do not change at the same time
Im truncating the long list to 5 items with 1 more item partially visible
On arrow keys to focus a suggestion, the list scrolls to show that item in view
Autocomplete is position above or below the text edit based on the height of the list & position of the textbox (some values are hard coded now, will fix in the subsequent PR)
z index where some tags were showing through

Could you test one more time please? Also would be good to take one more look at the code since I'm passing a bounding box


Codi 🐶 default base test

🐶 Added Codi Test Module for Building Default Mapview 🧪
Description 📝
This pull request introduces a comprehensive test module that ensures the correct functionality and behavior of a mapview in our application. The test module covers various aspects of the mapview, including dictionary merging, user authentication, language selection, scroll restoration, tab functionality, locale retrieval, mapview creation, layer management, gazetteer integration, and more.
Key Features and Improvements ✨
1. Dictionary Merging 📘

Tests the merging of dictionaries from different languages.
Verifies that the English dictionary is updated with new entries.
Asserts that the merged dictionaries have the expected properties and values.

2. User Authentication 🔒

Tests the refreshing of the user's cookie and retrieval of updated credentials.
Asserts that the user object is updated after refreshing the cookie.
Verifies that the user object has the expected properties.

3. Language Selection 🌐

Tests the setting of the language based on the specified priority.
Asserts that the language is set correctly based on the available overrides.

4. Scroll Restoration 📜

Tests the scroll restoration functionality if supported by the browser.
Asserts that scroll restoration is set to 'auto' when supported.

5. Tab Functionality 🗂

Tests the setting of help text from the dictionary for each tab.
Verifies the handling of tab click events.
Asserts that the active class is added to the clicked tab and corresponding panel.
Asserts that the active class is removed from other tabs and panels.

6. Locale Retrieval 🌎

Tests the retrieval of accessible locales from the Workspace API.
Asserts that the retrieved locales is an array and not empty.
Tests the retrieval of the locale with the list of layers from the Workspace API.
Asserts that the retrieved locale is not an instance of Error and has the expected properties.

7. Mapview Creation 🗺

Tests the creation of the mapview with the provided options.
Asserts that the mapview is created successfully and has the expected properties.

8. Layer Management

Tests the addition of layers to the mapview.
Asserts that the layers are added successfully to the mapview.

9. Gazetteer Integration 📍

Tests the creation of a gazetteer if available in the locale.
Asserts that the gazetteer is created when available.
Asserts that the locations tab is hidden when the gazetteer is not available.

10. Listview Creation 📋

Tests the creation of the layers listview.
Asserts that the layers listview is created successfully.
Tests the creation of the locations listview.
Asserts that the locations listview is created successfully.

11. Highlight Interaction 🔦

Tests the beginning of the highlight interaction.
Asserts that the highlight interaction is added to the mapview.

12. Tabview Functionality 🗂

Tests the showing and hiding of the tabview.
Asserts that the tabview is shown when the showTab function is called.
Asserts that the tabview is hidden when the removeLastTab function is called.

fin 🎉
This test module serves as a comprehensive suite to validate the functionality and behavior of a view that simulates our default mapview. It ensures that all the critical components, such as dictionary merging, user authentication, language selection, tab functionality, locale retrieval, mapview creation, layer management, gazetteer integration, and listview creation, are working as expected.
By including this test module, we can have confidence in the stability and reliability of our application's default mapview. It will help catch any potential issues or regressions during development and provide a solid foundation for future enhancements and modifications.
Please can you review the test module and provide any feedback or suggestions for improvement. Once approved, we can merge this pull request and include the test module in our codebase.

To test this you can navigate to http://localhost:300/{dir}?template=test_view.
You should see something like the following in your console.

Loving it - so easy to use and covers so many good tests! 👌👏
Only one thing - can we update the readme / config docs somewhere to highlight this option and how to use?

@simon-leech I have included a how to test on the mapview module docs.
Will need to think how we can better document the tests too.
Lets create a TODO for that 👍

Thanks Rob! Just that little bit of docs looks good to me for now. We can revisit more detailed in the future 👍

I have also made each test in the _default.test.mjs await so that we ensure nothing runs before it needs to.


New interface design proposal for GeneAnnoLogy

union: add new annotations, keep all

intersect: add new annotations
  -r|--replace    delete existing annotations that overlap with new annotations
  -c|--complement   do not add new annotations that overlap with existing annotations

clean: start all over again

update: modify existing annotations
  -n|--new: STRING    add transcript as new isoform, provide ID
  -r|--replace: STRING    provide ID of transcript to replace
  -c|--clean    start fresh at locus

delete: delete

Schematic for init/clean

GFF3InStream
AgnGeneStream
AgnLocusStream
AgnRepoStream

Schematic for union

Stage 1 (load infiles)

GtGFF3InStream
AgnGeneStream
GtFeatureOutStream

Stage 2 (load repo annots from matching seqids)

GtGFF3InStream
AgnGeneStream
GtFeatureOutStream

Stage 3 (write annots to repo)

GtFeatureInStream
AgnLocusStream
AgnRepoStream

Schematic for update

Stage 1

GtGFF3InStream
AgnInferParentStream (mRNA => gene, attribute for flagging deletion?)
AgnGeneStream
AgnRepoUpdateFeatureVisitor
GtFeatureOutStream

Stage 2

GtGFF3InStream (repo, affected seqids)
AgnGeneStream
AgnRepoUpdateFeatureVisitor
GtFeatureOutStream

Stage 3

GtFeatureInStream
AgnLocusStream
AgnRepoStream

Schematic for merge

Stage 1 (features to keep)

GtGFF3InStream
AgnGeneStream
GtFeatureOutStream

Stage 2 (features to merge)

GtGFF3InStream
AgnGeneStream
AgnRepoMergeStream (maintain feature index; keep certain features, delete remainder)

Stage 3

GtFeatureInStream
AgnLocusStream
AgnRepoStream

I may come back to implement update later, but for now I'm going to ignore it. The clean mode is unnecessary (just use merge --replace), and the other modes can be accomplished with existing commands as well.


Renew "Pages Framework guide" on Cloudflare Docs

Thanks to @rishavs, we have the documentation for Cloudflare Pages on the Cloudflare official site. That is one of "Pages Framework guides".
https://developers.cloudflare.com/pages/framework-guides/deploy-a-honojs-site/

And, in this PR https://github.com/cloudflare/cloudflare-docs/pull/7410, @dario-piotrowicz improved it. That's great for us.
But, what Hono can do with Pages is not limited to what this document describes. We can make it as API for SPA in /functions or we can use JSX middleware for SSR. So, we have to renew the document.
Let's consider writing new documentation after v3 is released.

@dario-piotrowicz told me that the documentation to be put on Cloudflare Docs should be minimal. I think it's right.
https://github.com/cloudflare/cloudflare-docs/pull/7410#issuecomment-1404947082
However, I think it's not a best, so either way, let's make it new.

The instructions for getting started with Hono on Cloudflare Pages are currently significantly different if you compare:

hono.dev: Cloudflare Pages
Cloudflare: Deploy a Hono site

The most fundamental difference is that Cloudflare instructs you to configure and run Esbuild directly, while hono.dev uses Vite. Among other things this prevents Client components from working when following the Cloudflare instructions, since only the main worker will ever be transpiled.
On the other hand, following the instructions from hono.dev doesn't give you any obvious way to develop locally with live reload while also using Cloudflare bindings (such as KV, R2, D1 etc).
I might have missed something important, but it seems like the documentation should at a minimum be aligned. Ideally the instructions should also find a good tradeoff between the different configuration options.

Hi @kpalmvik
Yes. We should take an action.

On the other hand, following the instructions from hono.dev doesn't give you any obvious way to develop locally with live reload while also using Cloudflare bindings (such as KV, R2, D1 etc).

I think this is wrong. We can develop the Pages application using Hono and Bindings with live reloading. Have you ever tried it? https://hono.dev/getting-started/cloudflare-pages#bindings

We can develop the Pages application using Hono and Bindings with live reloading. Have you ever tried it?

You are most likely correct, but for some reason I didn’t get it to work the first time. Will try again and get back soon.

I can confirm that by following all the steps in Hono: Cloudflare Pages, including the Binding section, I seem to have a working local development environment! ✅ 🎉
Some feedback on the current instructions:

The step touch wrangler.toml seem to be redundant as npm create hono@latest my-app already created the file.

The step Edit vite.config.ts is redundant, since the file already has the exact same lines with a slightly different formatting/ordering.

When running npm run dev for the first time I got a (perhaps unrelated) Vite error: (!) Could not auto-determine entry point from rollupOptions or html files and there are no explicit optimizeDeps.include patterns. Skipping dependency pre-bundling.

The Client side instructions leaves out things such as how to implement a basic client component. There is no reference to Client Components, but that page doesn't cover all the parts either as far as I can understand.
For example:

using a TSX file as the entrypoint (/src/client.tsx) does not seem to work even after changing input in vite.config.ts. To me it remains a bit unclear how it should be possible to do render(<App />, root) instead of render(App(), root)
The client component sources needs a "lib": ["dom"] entry in the tsconfig.json to allow document.getElementById("root");

Hi @yusukebe,
I faced a few issues with updating the documentation for Cloudflare. The command to create a Hono application is:
$ npm create cloudflare@latest my-hono-app -- --framework=hono

However, this will create an application with the cloudflare-workers template. Now, I can write documentation to show how to update it to the pages template, but as you mentioned:

the documentation to be put on Cloudflare Docs should be minimal.

We are unable to create multiple options it appears on c3, but if we allowed create-hono to accept an argument, that would update the template list to be just cloudflare-workers and cloudflare-pages. I think that would fix this, and I can update c3 accordingly.
I understand that this creates a bigger abstraction on top of the create-hono package, but I wanted to at least give the option. Let me know your thoughts, and I will proceed with changes accordingly.

Hi @NicoPlyley
Yes. I know about that issue, and I have some ideas.

It appears we are unable to create multiple options on c3, but if we allowed create-hono to accept an argument, that would update the template list to be just cloudflare-workers and cloudflare-pages. I think that would fix this, and I can update c3 accordingly.

Currently, create-hono already accepts --template options:
https://github.com/honojs/create-hono?tab=readme-ov-file#--template
So you can specify the template for create-hono command. But I think we can't pass the args to C3 and it's impossible to use cloudflare-pages template without modifying C3.
In Cloudflare internal, we are disuccusing about it but this not will resolved immediately.

For Hono, it's a little special because Hono can create a Web API for Workers or create web pages for Pages. So, my selfish suggestion is to introduce both Workers and Pages patterns. It's an exceptional case, but it will be best.
For example, the first section is for Workers and uses the C3 command. The second section is for Pages using create-hono directly. I think if we write them shortly, it will be a great document for the new users. What do you think about it?

@yusukebe, I want to explain what I was mentioning because I think it would fix the issue. However, we would be working around c3 rather than c3 working with Hono. And it would require two small modifications to c3.
If we had an option for a template (or another argument) like --template=cloudflare (this would not be a visible template, only accessible from the cli) it would then make the only option a user can select from the template list to be cloudflare-workers or cloudflare-pages. create-cloudflare Would have to be updated for the template command and to update the .ts or .tsx file to the same additions they already make.
I do understand if this is too much complexity. Or just does not make sense for a single use case. For now I will finish the docs for using create-hono instead since any updates would be minor.

@NicoPlyley
I see! C3 can't be changed immediately, so as you are doing, please use create-hono. Thanks!


Move ZAP templates specific to a language into language specific folders

Problem
This PR moves language specific templates into language specific folders.
Currently CHIPClustersObjc.* are generated for every .zap file while they only need to be part of src/darwin.
Similarly python-* depends on the configuration of controller-clusters while src/controller/python contains its own ZAP file.
Summary of Changes

Move Python specific templates into src/controller/python/templates
Move Objc specific templates into src/darwin/Framework/CHIP/templates

@msandstedt @andy31415 @jepenven-silabs ?


Changing Priority & Frequency settings on individual pages

Does changing priority &frequency properties on individual pages make any difference when sitemap.xml is generated .I have been trying to change them for a few of the pages & running the scheduler to generate the sitemap.xml but cant see any difference.The generated xml still holds the old value (priority/frequency)for the page.

I figured out the issue on why changing SEO configuration settings(enabled, priority & frequency) on individual pages was not reflecting on the generated sitemap.xml
I had renamed SEOSitemaps & so the changed settings was not being considered on the generated sitemap.xml
[Display(GroupName = Name = "Sitemap Configuration")]
[UIHint("SeoSitemap")]
[BackingType(typeof(PropertySEOSitemaps))]
//NOTE: This property must be named exactly SEOSitemaps or the Geta.SEO.Sitemaps will not use the values set per page
public virtual string SEOSitemaps { get; set; }


IP Address

So most likely we do not know the IP address of our own computer. It would be helpful to print out the IP address of your computer (aka the one you are connecting with) when creating a Poker Server so your opponent know what to type into their computer. This is to make starting up the game much quicker!
Estimate: ~50 pts

F16 CLOSED: This issue was resolved in M16


Emacs alt-v keybinding triggering solo Alt key in firefox

One minor thing...
I'm using the provided emacs keybindings. In Firefox when I use alt-v (page-up), page-up does successfully work, but it also triggers a solo alt press (open menu).
Is there any way to separate an alt pressed separately with one thats part of a key sequence?

You could try the virtual_modifiers feature, or use Super instead of Alt. I personally use the latter method myself for this exact problem.

You use Super systemwide in lieu of Alt (except in emacs I guess)? Or just in firefox?
Is there any way to make Alt behave as normal Alt when pressed singly, and ignored when held?

Yes. This is what you said:
modmap:
  - remap:
      Alt_L:
        held: KEY_UNKNOWN
        alone: Alt_L

but I think you want to put Alt_L in held and Unknown in alone?

Yes. This is what you said:
modmap:
  - remap:
      Alt_L:
        held: KEY_UNKNOWN
        alone: Alt_L

but I think you want to put Alt_L in held and Unknown in alone?

I did both solutions, your suggestion that Alt_L in held and Unknown in alone does work but after using a keybinding such as Alt_R-j for left arrow, I cannot type anything. It behave like the Alt_R is stuck or always pressed.

Can you run xremap with RUST_LOG=debug xremap, reproduce the problem, stop xremap, and share the entire output of the xremap command and the config YAML file?

Here is the output after I run xremap with debug:
[2024-05-21T04:54:45Z DEBUG xremap::event_handler] => 0: KEY_ENTER [2024-05-21T04:54:45Z DEBUG xremap::action_dispatcher] 0: KEY_ENTER [2024-05-21T04:54:55Z DEBUG xremap::event_handler] => 1: KEY_RIGHTALT [2024-05-21T04:54:55Z DEBUG xremap::event_handler] => 1: KEY_I [2024-05-21T04:54:55Z DEBUG xremap::action_dispatcher] 0: KEY_RIGHTALT [2024-05-21T04:54:55Z DEBUG xremap::action_dispatcher] 1: KEY_UP [2024-05-21T04:54:55Z DEBUG xremap::action_dispatcher] 0: KEY_UP [2024-05-21T04:54:55Z DEBUG xremap::action_dispatcher] 1: KEY_RIGHTALT [2024-05-21T04:54:55Z DEBUG xremap::event_handler] => 0: KEY_I [2024-05-21T04:54:55Z DEBUG xremap::action_dispatcher] 0: KEY_I [2024-05-21T04:54:55Z DEBUG xremap::event_handler] => 0: KEY_RIGHTALT [2024-05-21T04:55:00Z DEBUG xremap::event_handler] => 1: KEY_I [2024-05-21T04:55:00Z DEBUG xremap::action_dispatcher] 1: KEY_I [2024-05-21T04:55:00Z DEBUG xremap::event_handler] => 0: KEY_I [2024-05-21T04:55:00Z DEBUG xremap::action_dispatcher] 0: KEY_I [2024-05-21T04:55:01Z DEBUG xremap::event_handler] => 1: KEY_A [2024-05-21T04:55:01Z DEBUG xremap::action_dispatcher] 1: KEY_A [2024-05-21T04:55:01Z DEBUG xremap::event_handler] => 0: KEY_A [2024-05-21T04:55:01Z DEBUG xremap::action_dispatcher] 0: KEY_A [2024-05-21T04:55:02Z DEBUG xremap::event_handler] => 1: KEY_A [2024-05-21T04:55:02Z DEBUG xremap::action_dispatcher] 1: KEY_A [2024-05-21T04:55:02Z DEBUG xremap::event_handler] => 0: KEY_A [2024-05-21T04:55:02Z DEBUG xremap::action_dispatcher] 0: KEY_A [2024-05-21T04:55:03Z DEBUG xremap::event_handler] => 1: KEY_A [2024-05-21T04:55:03Z DEBUG xremap::action_dispatcher] 1: KEY_A [2024-05-21T04:55:03Z DEBUG xremap::event_handler] => 0: KEY_A [2024-05-21T04:55:03Z DEBUG xremap::action_dispatcher] 0: KEY_A [2024-05-21T04:55:05Z DEBUG xremap::event_handler] => 1: KEY_LEFTCTRL [2024-05-21T04:55:05Z DEBUG xremap::action_dispatcher] 1: KEY_LEFTCTRL [2024-05-21T04:55:05Z DEBUG xremap::event_handler] => 1: KEY_C [2024-05-21T04:55:05Z DEBUG xremap::action_dispatcher] 1: KEY_C
This is my YAML file content:
`virtual_modifiers:

Alt_R

keymap:

remap:
Alt_R-i: Up
Alt_R-j: Left
Alt_R-k: Down
Alt_R-l: Right
Alt_L-Alt_R-i: KEY_PAGEUP
Alt_L-Alt_R-j: Home
Alt_L-Alt_R-k: KEY_PAGEDOWN
Alt_L-Alt_R-l: End
Shift_L-Alt_L-Alt_R-i: Shift_L-KEY_PAGEUP
Shift_L-Alt_L-Alt_R-j: Shift_L-Home
Shift_L-Alt_L-Alt_R-k: Shift_L-KEY_PAGEDOWN
Shift_L-Alt_L-Alt_R-l: Shift_L-End`

I use virtual_modifiers with Alt_R and modmap: Alt_R in held and Unknown in alone does work but after using a keybinding such as Alt_R-j for left arrow, I cannot type anything. It behave like the Alt_R is stuck or always pressed.

It appears that you're not using held/alone in the YAML you've just pasted. What is the problem again? I'm just seeing that remapping Alt_R-i to Up worked just fine.

I have the same problem of M-v triggering a solo alt key press. It is not specific to firefox.
The cause is quite clear since the logs show that alt is being dispatched after pageup:
[2024-08-06T12:08:16Z DEBUG xremap::event_handler] => 1: KEY_RIGHTALT
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 1: KEY_RIGHTALT
[2024-08-06T12:08:16Z DEBUG xremap::event_handler] => 1: KEY_V
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 0: KEY_RIGHTALT
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 1: KEY_PAGEUP
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 0: KEY_PAGEUP
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 1: KEY_RIGHTALT
[2024-08-06T12:08:16Z DEBUG xremap::event_handler] => 0: KEY_V
[2024-08-06T12:08:16Z DEBUG xremap::action_dispatcher] 0: KEY_V
[2024-08-06T12:08:17Z DEBUG xremap::event_handler] => 0: KEY_RIGHTALT
[2024-08-06T12:08:17Z DEBUG xremap::action_dispatcher] 0: KEY_RIGHTALT

This is necessary behavior in order for the applications default shortcuts to work.
However, I was curious why I did not get the same behavior for other bindings using alt. It turns out those bindings all involve an additional modifier key like control, which prevents the alt action. For example, I have bound M-l to C-pagedown in order to switch tabs in the browser, and this works successfully without opening the alt-menu.
Logs:
[2024-08-06T12:08:11Z DEBUG xremap::event_handler] => 1: KEY_RIGHTALT
[2024-08-06T12:08:11Z DEBUG xremap::action_dispatcher] 1: KEY_RIGHTALT
[2024-08-06T12:08:12Z DEBUG xremap::event_handler] => 1: KEY_L
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 1: KEY_LEFTCTRL
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 0: KEY_RIGHTALT
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 1: KEY_PAGEDOWN
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 0: KEY_PAGEDOWN
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 1: KEY_RIGHTALT
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 0: KEY_LEFTCTRL
[2024-08-06T12:08:12Z DEBUG xremap::event_handler] => 0: KEY_L
[2024-08-06T12:08:12Z DEBUG xremap::action_dispatcher] 0: KEY_L
[2024-08-06T12:08:13Z DEBUG xremap::event_handler] => 0: KEY_RIGHTALT
[2024-08-06T12:08:13Z DEBUG xremap::action_dispatcher] 0: KEY_RIGHTALT

I believe the fact that control is not released until after alt is activated prevents the menu from opening, since holding pressing alt while control is pressed does not open the alt-menu.
My solution: Since firefox has an alternative binding for going up the screen that contains a modifier key, namely Shift-space we can just use that one instead.
The more proper solution would be to use an entirely different modifier key altogether. The problem with this is that modifier keys are limited, and I already use keys like super for other purposes. What I would really like to do is to use the alt key as the physical modifier key but have it work like a unique modifier key that is not used by any application. Is there any way to achieve this?
I suppose I could use some obscure key X as a virtual modifier and assign it to the alt key, and then use X instead of alt for my keymap. However, I do not know what choice for X would be appropriate. Ideally, X would not be a real key at all.
Alternatively, if we could have an option to disable the modifier key from being dispatched at all, and only dispatch whatever we have assigned in our keymap, that should also work. Although this would require work.


mypy failing with "config not defined"

Bug Description
mypy is failing with the following:
src/fidesops/service/connectors/saas_connector.py:98: error: Name 'config' is not defined  [name-defined]
                if config.dev_mode:  # pylint: disable=R1720
                   ^
src/fidesops/service/connectors/saas_connector.py:129: error: Name 'config' is not defined  [name-defined]
        if config.dev_mode:
           ^
Found 2 errors in 1 file (checked 146 source files)

I did a bisect and it started in this commit https://github.com/ethyca/fidesops/commit/12e25a175526f7c70625cf62f604ffab7bd2088d (happens to be the most recent).
Steps to Reproduce

Run make mypy
Running mypy outside make mypy src --ignore-missing-imports gets the same error.

Expected behavior
No mypy errors
Screenshots
N/A
Environment

Version:
OS: Linux
Python Version: 3.10
Docker Version: 20.10.14

Additional context
N/A

It looks like #448 will fix this. This brings up another issue. Both MyPy and Pylint should have failed CI from this, but it looks like both passed. On first pass I don't see any reason for this.

I think https://github.com/ethyca/fidesops/pull/363 would have failed if we had gotten it up-to-date with main before merging. It was an old PR that had been sitting for awhile.

Closed via #448


[Spillover] Validation pending and e2e testing remaining items

Description
This Epic will cover some of the spilled over items from the HA plan:

Migration: Chef server band to HA
Validation script - net-cat utility package
E2E testing - Upgrade scenario pending
Documentation - Migration + remaining documents

Current State:
Migration: Chef server backend to HA - Complete
Validation script - net-cat utility package - In PR | Under Review | PR: https://github.com/chef/automate/pull/6493
E2E testing - Upgrade scenario pending - Upgrade dev complete | E2E testing from release Engg side remaining
Documentation - Migration + remaining documents - Only Upgrade documentation is pending for walk-thru + Migration - Automate to Automate HA.


fix: adapt to command changes from XSUAA-3964

Purpose
The domain is no longer reset to null if omitted in btp CLI command for updating a subaccount trust configuration.
This PR fixes the corresponding resource by changing the domain to computed and reading from state is unknown.

...

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[X] Bugfix
[ ] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Test the code via automated test

go test ./...

Additional test steps

...

What to Check
Verify that the following are valid:

Automated tests are executed successfully

...

Other Information

Checklist for reviewer

The following organizational tasks must be completed before merging this PR:

[X] The PR is assigned to the Terraform project and a status is set (typically "in review").
[X] The PR has the matching labels assigned to it.
[X] The PR has a milestone assigned to it.
[X] If the PR closes an issue, the issue is referenced.
[X] Possible follow-up items are created and linked.

Issue with inclusive language is due to upstream dependencies that we cannot fix.


Add async decode to bao

PR: https://github.com/oconnor663/bao/pull/44

Not sure how to proceed with this. We now got our own crate bao-tree that supports all the things. Also we got abao which has an async decoder.


Add Medium Articles published

https://medium.com/@anuhosad/porting-medium-articles-to-create-a-blog-in-gatsby-749c0932523f


skip the sample generation for some upcoming new operations in mgmt plane

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Feature Search

It's completed but it has some bugs but they can be fixed with other issues if you would agree.
Close #64

@hadi-norouzi The build is failing.I think instead of merging dev to search you should rebase search with dev. I'll fix that.

Dear @hadi-norouzi. Thanks for your great contribution.
As you mentioned we have some issues and I think its better to address them before merging this branch. e.g:

State is lost when you navigate to a search item and press back button. even you can not change between search tabs (All, Move and TV)
Better handling of that SerializationException
Pagination
Grid state reset

If you are overwhelmed with this feature, I might have time next weekend and I can contribute to this feature. Let me know WDYT.

Dear @hadi-norouzi. Thanks for your great contribution.
As you mentioned we have some issues and I think its better to address them before merging this branch. e.g:

State is lost when you navigate to a search item and press back button. even you can not change between search tabs (All, Move and TV)
Better handling of that SerializationException
Pagination
Grid state reset

If you are overwhelmed with this feature, I might have time next weekend and I can contribute to this feature. Let me know WDYT.

Sure, they are. I have no idea about them but I can implement pagination in this PR and create new issues for others.

You can work on pagination. No need to create new issues. We'll fix them here


fix destructuring env to pass tests

Thanks, but I intentionally didn't handle it as #29 will solve it. It's not enough to just fix that as master tests with Node.js 4, which doesn't handle destructuring.


Map /ssl into syncthing container

Which addon?

Syncthing
Is your feature request related to a problem? Please describe.

No problem - just a feature request
Describe the solution you'd like

Would it be possible to also make the /ssl folder available inside the Syncthing container? My specific use case is that I have LetsEncrypt add-on requesting wildcard certificates that have validity across multiple other hosts in my environment. I'd like to then use Syncthing to automatically sync these certificate files to all the servers that need them
Describe alternatives you've considered

I did try to use portainer to map the volume in manually, but I don't think this is possible with a hassio addon
Additional context

I think this should be as simple as mapping /mnt/data/supervisor/ssl to /ssl...

The mapping is an easy and simple change 😉

I had hoped it would be! :)

It works brilliantly! Thanks very much.


terraform-docs must be upgraded to 0.19.0 to avoid breaking docs with htlm tags

What problem are you facing?

Currently on my mac I have the version of terraform-docs v0.19.0.
installed via brew.
Unfortunately this version of terraform-docs introduces a correct change from the point of view of html validation so the
 tag is now correctly generated as

unfortunately the latest available version of pre-commit (v1.96.1) has the terraform-docs's version v0.18.0 inside it which generates the tags as , not being able to downgrade the version of terraform docs in my mac. I find that locally the pre-commit run and tells me that everything is ok, when the pipelines with the docker image instead it fails.
How could pre-commit-terraform help solve your problem?

Please I ask you to release a version of pre-commit with the update of terraform-docs to allow this problem to be fixed
Now my workaround is to run a script locally that runs pre-commit via docker-image
#!/bin/bash
TAG="v1.96.1@sha256:9aea677ac51d67eb96b3bbb4cf93b16afdde5476f984e75e87888850d18146c9"
docker run -v "$(pwd):/lint" -w /lint ghcr.io/antonbabenko/pre-commit-terraform:$TAG run -a

Thx so much for your effort

Duplicates of #724

Pre-built docker images contained latest version of tools available during it buid time, and never change again.
If you want to use latest builds - use nightly tag - https://github.com/antonbabenko/pre-commit-terraform/pkgs/container/pre-commit-terraform/291188741?tag=nightly
Or you can build your own image with needed versions, for this - checkout Docker section in https://github.com/antonbabenko/pre-commit-terraform?tab=readme-ov-file#1-install-dependencies

And actually, HTML5 (released in 22 January 2008) uses
, not
. So I not use why they changed it (support of XHTML?), but whatever.


Preparation for 2.0 Release

It's really hard to break things up into small PRs when a bunch of things have to change, especially if we can't do timely reviews on even one-liners.
So here is a 2,000 liner.

Fixes thread safety issue with JUnit 5
Removes deprecated code and sets snapshot to 2.0 beta
implements serialization so SauceOptions can be copied
implements abort method to quit session without updating test result for when tests are aborted
Fixed up CITools class so you can get the CI tool name and the logic is more obvious
Add CI Tool and Sauce Bindings to Custom Data on startup
Bunch of fixes for testing when disabling Sauce in properties

To Do

Ensure TestNG is thread safe (I think it is probably good, but need to verify it doesn't need copy())
JUnit 4 is definitely not thread safe
JUnit 4 and TestNG plugins both need to update to add things to custom data

I think a test suite that runs in parallel is needed to make sure all these changes are actually doing what you are expecting.

This test suite does run in parallel, but it doesn't have enough tests to consistently hit the race conditions
I've been using another test suite to verify that it is working properly, which isn't ideal, but has been helpful.

I've got a test suite I'm using, we can discuss if it should get added to this repo or not.

for future reference: the force pushes above was me playing around with adding fixes for CI tooling things, but I'm going to make that another PR.


Update util.py

Added proxies to connect by params.

@schercav can you fix the test that failed? https://travis-ci.com/github/paragbaxi/qualysapi/jobs/343566112


Experimental support of Optional Chaining (at least static property access) via experimentalOptionalChaining

Suggestion
Add experimentalOptionalChaining property to compilerOptions which will support at least static property access – the most required and expected feature.
Use Cases
For me, in 2019 the most important part of Optional Chaining is static property access. It will greatly improve DX for GraphQL client apps and make client code more robust and clean. 🚀
Current shortcomings:

if-check-hell 🤢
unchecked dottedPaths as string 💩

_.get(obj, ['some.nested.field']) with lodash.get
objectPath.get(obj, 'dottedPath') with object-path (900k weekly downloads 😱)

Examples
Assume we have following GraphQL response from the server on the client side:
interface IResponse {
  viewer?: {
    article?: {
      title?: string
    }
  }
}

const response: IResponse = await apolloClient.query(`query {
    viewer {
      article(id: 15) {
        title
      }
    }
}`);

On any level, graphql may return null, so before displaying title we must check viewer and article existence.
... with if-check-hell 🤢
if (response && response.viewer && response.viewer.article && response.viewer.article.title) {
  // ... display title
}

Pros: statically checked (if query changed, then we will be warned about un-existed props)
Cons: to much code
... with unchecked dottedPaths as string 💩
if (_.get(response, ['viewer.article.title'])) {
  // ... display title
}

Pros: quite clean code
Cons: statically UNchecked (if query changed, then we will NOT be warned about un-existed props checks)
... with Optional Chaining ❤
if (response?.viewer?.article?.title) {
  // ... display title
}

Pros: very clean code & static checks
Cons: not implemented in TS, but already implemented about a year ago in Flow 0.74, Eslint, Babel.
Recap
We just have 3 levels deep query, but in most cases it's deeper.
if (response && response.viewer && response.viewer.article && response.viewer.article.title) {
if (_.get(response, ['viewer.article.title'])) {
if (response?.viewer?.article?.title) {

Definitely, OptionalChaining is the winner 🥇
Suggestion: repeat once more
Just add static property access from optional chaining proposal under experimentalOptionalChaining flag. This part is stable in the proposal and it is the most required feature in 2019.
Let's keep problematic optional chaining for function calling, short-circuiting, grouping, deletion, template literals – out of the scope of this issue.
Please do not reference this issue as a duplicate for issue #16 from the 2014 year, here are 2019 and requirements changed from that time.
Search Terms
Optional Chaining, null propagation.

Stale old issue #16 (discussed in 2014-2017 years)
TC39 optional-chaining (Stage 1, but all preparations for Stage 2 were done)

Checklist
My suggestion meets these guidelines:

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

I'm prepared a simple video demo with Flow and Optional Chaining: https://youtu.be/NzlDE3cWnDc

Again: I'm telling about optional chaining for reading properties from objects.
PS. Let's keep problematic optional chaining for method calling out of the scope of this issue.

Why this:
const value = this?.foo?.bar?.baz !== undefined ? this.foo.bar.baz : defaultValue;

Better than this?
const value = get(this, 'foo.bar.baz', defaultValue)

@lifeart please watch the video above when I breaking response interface. Such kind of things usually love to do backenders 😜
And I want to get strongly typed code with static analysis for such kind of things, rather than old-school dot-path in a string, which not understands TypeScript.
With optional chaining, TypeScript will help to catch such changes. 👍

@nodkz  this can be statically analyzed:
const value = get(get(get(this, 'some'), 'nested'), 'key', defaultValue);

@lifeart wow! I think that it cannot be used as a good solution 😜
In such case better to use if-check-hell 😈

I don't think that a feature like this belongs in the language.

Having a long chain of unknown fields should be an unlikely pattern.
A typed language encourages writing out typed schemas so that you don't get into situations like this.

A schema where each field is unknown to be present doesn't usually make much sense.
...But those cases where it does make sense the problem should be explicit. But having a syntax to help you hide the unreliability of a schema will encourage creating unreliable schemas. It should be the other way around.

Accessing the data through long chains is likely to be a violation of the Principle of Least Knowledge

Duplicate of https://github.com/Microsoft/TypeScript/issues/16?

Where did this get brigaded from?

@RyanCavanaugh HackerNews

@RyanCavanaugh from twitter https://twitter.com/nodkz/status/1101432188883603456?s=19 and GraphQL community. Need to wait while US wake up for bigger feedback ;)

+1. I've seen the "if-check-hell" pattern and the "dottedPaths" pattern used, and it would be great if the language had first-class support for them.
Justification: fundamentally, TypeScript is often used in the application space of web clients. Web client design is well-served by support for the robustness principle. In client logic, this implies one ought not assume that the response from any RPC always matches the format expected by client logic (even if the developer controls both client and server, any number of intermediary pieces of logic in the network stack can modify a response for various reasons).
This feature supports good development practice by simplifying the task of graceful degradation when it's discovered a nested data structure doesn't match the anticipated shape, which is a common occurrence in web application development.

Also https://news.ycombinator.com/item?id=19283238
FWIW, I'm against this, I'd rather have proper recursive checking for R.path(['foo', 'bar'], {foo: {bar: 5}}).
On top of that, optional chaining is still a stage 1 proposal.

I will be seeking Stage 2 for Optional Chaining at the next TC-39 meetup in March which, based on the outlook coming out of our November meetup, it should reach.

I'm going to leave this open only because people get tend to get salty when they click on a link and see we closed something, but the definitive issue tracking this is #16 and we are (still!) committed to waiting for TC39 to decide what the semantics of this feature would be.
After being burned multiple times by adding features to TS only to have the semantic rug pulled out from under us at the last second, there is seriously no number of upvotes that would have us adding a feature that could potentially drastically change runtime behavior at some point in the future.

We have been waiting on optional chaining for years. What semantics are honestly going to change? I'm not asking in a snarky way or in an insincere way, I just honestly don't understand what could possible change from 3-years ago to now to whenever this gets implemented.

What semantics are honestly going to change?

There are currently 29 open issues in the proposal repo, any one of which represents possible semantic changes, plus any new changes the committee might come up with.
From https://github.com/tc39/proposal-optional-chaining/issues/2 / https://github.com/tc39/proposal-optional-chaining/issues/10

Is undefined?.a.b an exception or undefined ?
Is (undefined?.a).b an exception or undefined ?
Is undefined?.a() an exception or undefined ?
What's behavior of a?.b() when b is undefined?

From https://github.com/tc39/proposal-optional-chaining/issues/5

What's the syntax?

From https://github.com/tc39/proposal-optional-chaining/issues/28

How, if at all, does it work with private fields?

From https://github.com/tc39/proposal-optional-chaining/issues/40

How does it work with the delete operator?

https://github.com/tc39/proposal-optional-chaining/issues/51

65 comments and hundreds of votes on something like a dozen different syntax options, including a clarification that the "obvious" solution is "not available"

From https://github.com/tc39/proposal-optional-chaining/issues/61

Wait, is it a.?b or a?.b ?

From https://github.com/tc39/proposal-optional-chaining/issues/69

Will null?.prop result in undefined or null ?

I completely concur with @RyanCavanaugh's assessment. We've come a long way and we're closer than ever, but part of the reason it's been such a long running proposal is the complexity around JavaScript, the semantics that exist and need to continue to work, and the readability/understandability of the code proposed.

There are currently 29 open issues in the proposal repo...
One of the first things I plan to do once we reach Stage 2 is to go and clean out issues. As a semi-OCD person, this is going to scratch an itch I've had for awhile 😆. We simply didn't want to shut down discussions until we were a bit firmer in our approach, and Stage 2 will be that point.

I can also answer some of the above questions:

What's the syntax?

The syntax that we've largely reached consensus on (which will become official once it reaches Stage 2) is:

a?.b?.c for static property lookup
a?.[b] for dynamic property lookup
a?.() for optional function execution
delete a?.b for optional deletion

Not everyone is thrilled about these (trust me, that's part of why this proposal has taken as long as it has), but believe me, these are the best options that we have. If you've thought of something else, feel free to search in the issues because it's more than likely been discussed.

How, if at all, does it work with private fields?

This one isn't baked into the proposal yet, simply because private fields themselves aren't baked yet. So we don't want to hold up this proposal if that one happens to stall out. Once that one has reached Stage 4, we will address it then.

How does it work with the delete operator?

See Answer 1

Will null?.prop result in undefined or null ?

This will result in undefined because by that logic, you are looking for prop, which is not defined. You can be more verbose in your code if you care about getting the null.

I know most if not all of you are as excited as I am for this proposal. It's been a long road and I ask you wait just a little longer. These things take time, and since JavaScript is forever (once a proposal reaches Stage 4 and is officially part of the language, it can't be removed save for a security flaw), we want to make sure we've covered all the angles and considered all possibilities.

Maybe this is the wrong place to discuss the proposal but why it simply couldn't be ?foo.bar.baz.buz

This is the wrong place to discuss the proposal 😉

@dustinsavery will be great if Optional Chaining will be split into several parts (if possible).
For example static property access may become Stage-3 or even more Stage-4, this gives legitimacy to TS tram for implementing this feature in near time.
And other non-cozy parts like dynamic lookup, function execution, delete operator – may stay at Stage-1 or 2. 😉
PS. Divide and conquer complex and loooong parts.

@nodkz Trust me when I say we have tried many different angles to get this through. The fact that it hasn’t advanced isn’t for lack of trying or brainstorming new ideas or approaches. This is one that I tried during our last meeting, but that was voted down. We have a plan that has buyoff, now we just require patience from the community.

@typescript-bot holy life, you will close issues from us??? And we – the bags of blood and bones are nothing for you... Realy???
@RyanCavanaugh @dustinsavery please alive this issue! and remove duplicate to relax the typescripts's bot.
I understand that complex questions better to keep closed by the bot... But it's too early to allow bots to take decisions in 2019...
#diversity #humanity_please_live #no_bots

As a human, I approve the bot's behavior.


Chart Theme: Figma data visualization tokens

Area
UI Components
The problem
Description:
We need to establish a consistent and reusable design system for our High Charts data visualization theme. This involves creating Figma tokens to ensure uniformity across all data visualizations.
Tasks:
Define Figma tokens.
The solution
Create a Figma library file containing all defined tokens.
Alternatives and examples
TBD
Are you a JPMorgan Chase & Co. employee?

[x] I am an employee of JPMorgan Chase & Co.

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Externalised data for the navigation

The basic requrest for these PR was to update the label of the menus:
'Sections' become 'Topics'
'Products' become 'More'
Then I thought it was I good idea moving the data outside of the component (I will add a static version of @economist/component-sections-card/context inside fe-blogs) and to prevent error due to the 2 different menus I centralised some information shared betwen the accordion, the sections card and the top menu.
So next step will be move the data and the relative massaging on fe-blogs.

Super cool


How to exclude registry key

[Enter feedback here]
I would like to exclude some registry key.
Like this "HKEY_CURRENT_USER\Software\xxxx"
How to write to redirections.xml?

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

ID: 960d3cdb-4c5a-7c10-a78e-127b1216a547
Version Independent ID: a1bf2ff6-41a6-e840-676e-0eb4b9feed72
Content: Profile Container content - FSLogix
Content Source: fslogix-docs/manage-profile-content-cncpt.md
Product: fslogix
GitHub Login: @SteveD-MSFT
Microsoft Alias: stdowns

Duplicate


[cfitsio] fix uwp build

Don't forget to remove it from CI baseline

Don't forget to remove it from CI baseline

The build does not even run in this case 😮


Search function

This is to allow users search posts by keywords.

Refer to current Pitayan.com search function. When user click on the search button, it will pop out a modal for text input

Looks like gatsby-plugin-local-search supports Gatsby V5.0
https://github.com/angeloashmore/gatsby-plugin-local-search

Looking for solutions of alternatives to gatsby-plugin-local-search


validate pipes on creation

add direction labels to ports (in\out) and handle error when user tries wrong piping

implemented in https://github.com/hovsep/fmesh/pull/78


Apply title rules to test.step

Updated valid-title rule to apply to test.step commands.

@mskelton Thanks for the review! I addressed your comment (it was only about the first test case, right?) and pushed a tiny update to rule description.


Update docs to show usage of column accessor

The current documentation does not cover using the accessor on a series. We should update the documents to show how this works. Of particular importance is the use of the init_series function which needs to be used any time initialization would require changing the dtype of the series.

Closed by #717


The demo does not generate the same id

The demo does not generate the same id

Are you using our official demo? What's prompt setting?

It's the official website. prompt is a man


Fix Razor formatting bug

Fixes https://github.com/microsoft/vscode-dotnettools/issues/218
Short PR, but a hard one to investigate. The reason why nothing was happening was because the HTML formatter wasn't respecting the html.format.preserveNewLines setting, which in turn made some of our code go from:
@model Test

Text

to
@model Test Text

Since the above is invalid Razor syntax, it caused Razor's FormattingDiagnosticValidationPass to fail, resulting in our formatter doing nothing.
While the HTML formatter failed to respect the html.format.preserveNewLines setting, the HTML range formatter respected it. I was confused as to why this was the case, and started digging into the HTML code. I eventually filed https://github.com/microsoft/vscode/issues/191395 which I believe is the root cause. (Tl;dr HTML isn't explicitly registering a document formatter, which I believe they need to do in order to pick up settings.) Once the HTML-side bug is fixed, Razor should hypothetically be able to remove the workaround in this PR.
Razor formatting will still be broken in the case where the user turns html.format.preserveNewLines off (it's on by default, so hopefully this case is rare), since vscode's FormattingOptions doesn't take custom formatter settings. The real long-term fix here is probably to complete https://github.com/dotnet/razor/issues/7564 on Razor's end, but that seems to be a ways off.

Wow, nice find!
One question, and maybe you don't know the answer which is cool, but if HTML isn't registering a document formatter, then why would it be called at all when we executed the formatting command? Essentially, I wonder if the response will be that this is by design, and the workaround will therefore be permanent. Fine by me if it is, just thinking out loud :)

Good question, to be honest I'm not quite sure. My theory is that there's some fallback way they call the formatter, but I couldn't find the exact path through my digging. Will be curious to see how the VS Code HTML team responds. 😊


Added the Proper text

Related Issue

Issue No. #291

Changes you made :

I have added the proper text in the contact section of your website in the place of lorem ipsum.

Check list :

[x] I have followed code style of this project.
[x] I have read the CONTRIBUTING document.
[x] All the aspects mentioned in the issue are covered.
[x] The website is properly working after my changes.
[x] 🌟 ed the repo

Output Screenshots :

@SaiSantosh2209 Good
LGTM 🎆


install in home directory? [almost pull request]

:zap: Electron is fun to play with, especially with the recent growth of apps. Between experimenting and modifying apps, electron-prebuilt started downloading lots of :floppy_disk: on my machine. But I only want one copy, so I forked the lib and named it electron-bin. I felt like the changes might break other apps and don't address any major bugs, so I didn't submit a PR:
Difs:
Downloads electron in home directory - ~/.electron/<version>/.../electron - checks for it's existence before starting any downloads, and rimrafs the .zip after download. Also added electronVersion field in the package.json for convenience.
PR potential?
If ~/.electron/ is treated as a cache, with the files copied into the local node_modules/electron-prebuilt/dest folder, the behavior might be similar enough to not break anything. Let me know if there's PR interest because these libs are almost identical!!

Does your thing copy the electron binary into the locally installed dep? If so I'm fine with a shared cache.

No, it doesn't copy the binary into the locally installed dep. It's definitely possible. home-path is cross platform, the only questions I have are:

is .electron a safe namespace?

symlinks? or full copies? (I assume copies)

figured it out - https://github.com/mafintosh/electron-prebuilt/pull/23

nugget downloads zip into home directory ~/.electron
extract-zip works identical but sources from the cache
if .zip already exists, no need to download, just extract-zip

simple

The other lib (electron-bin) will use bin-link that focuses on cmd-line usage of single binary (-g)


[0.4] Add documentation on M1 support status in installation page

Related Issue: #1242
We should notify users how to install AutoGluon on M1 Mac or that it is explicitly not supported. Currently we do not mention M1 Mac / ARM support (or lack thereof) in our documentation.

I also have issue on installing on M1Max when compiling scipy, scikit-learn, pyarrow. Also, the pip gives an error
ERROR: Cannot install autogluon==0.0.10, autogluon==0.0.11, autogluon==0.0.12, autogluon==0.0.13, autogluon==0.0.14, autogluon==0.0.15, autogluon==0.0.2, autogluon==0.0.3, autogluon==0.0.4, autogluon==0.0.5, autogluon==0.0.6, autogluon==0.0.8 and autogluon==0.0.9 because these package versions have conflicting dependencies.

The conflict is caused by:
    autogluon 0.0.15 depends on catboost<0.25 and >=0.23.0
    autogluon 0.0.14 depends on catboost<0.25 and >=0.23.0
    autogluon 0.0.13 depends on catboost<0.24
    autogluon 0.0.12 depends on catboost<0.24
    autogluon 0.0.11 depends on catboost<0.24
    autogluon 0.0.10 depends on catboost<0.24
    autogluon 0.0.9 depends on catboost<0.24
    autogluon 0.0.8 depends on catboost
    autogluon 0.0.6 depends on catboost
    autogluon 0.0.5 depends on catboost
    autogluon 0.0.4 depends on catboost
    autogluon 0.0.3 depends on catboost
    autogluon 0.0.2 depends on catboost

@FranklinBao Can you try pip install --pre autogluon.tabular? This is a minimal pre-release install, and then you can install the separate optional dependencies one by one as needed.


fix: admonitions style

waiting for #412 to merge
fix admonitions
light theme

dark theme

Nice work @Revathyvenugopal162 .
Thanks for all the presentation related to it yesterday.

I bet it is tricky to get the admonition icon inline with the rest of the text for multi-line admonitions.
If we want to keep the icon next to the title of the admonition, then let's increase the margin between the icon and the left border of the admonition. Otherwise, icons for one-line admonitions and multi-line ones show a margin difference.

I bet it is tricky to get the admonition icon inline with the rest of the text for multi-line admonitions.
If we want to keep the icon next to the title of the admonition, then let's increase the margin between the icon and the left border of the admonition. Otherwise, icons for one-line admonitions and multi-line ones show a margin difference.

updated the margin and the screenshots

@Revathyvenugopal162, I can see both the admonition title and the content are left justified and aligned. However, the icon still shows a bigger margin than in the multi-line admonitions than in the multi-line admonitions than in the one-line ones.

@Revathyvenugopal162, I can see both the admonition title and the content are left justified and aligned. However, the icon still shows a bigger margin than in the multi-line admonitions than in the multi-line admonitions than in the one-line ones.

margin left for both the icons are same, but the right margin after the icons were different  , i just aligned it back, let me know if this works, otherwise i can revert with the small margin in between.


Unknow problem

Hi
Someone know how to fix this problem?
I already have avisynthplus 3.7.2 and Microsoft VisualC++2022
Windows 10
Xeon e5 2696 v2
rtx 3060
32gb ram

Hi,
What's the exact version of avs+? Type version() to see it. From the requirements section of the readme: "AviSynth+ r3682 (can be downloaded from here until official release is uploaded) (r3689 recommended) or later".

"how to fix this problem?"
Better to show smallest possible script how to reproduce this crash. Better with internal source like BlankClip() if possible.