Responsive web

VALUE
Someone visiting our site could have a better experience regardless of the device
CONTEXT
Sophie is the owner of a software factory. She attended a technical event to recruit technical talent. She is looking for junior front-end developers to add to her team. At the event she mets one adalaber that shows her the website she made during the course. She saves the site to check it out in the office and she contacts the adalaber after the course in order to hire her.
RESOURCES
Images in different sizes
Tasks

[ ] Header - tablet version
[ ]  Hero - tablet version
[ ]  Who we are - tablet version
[ ] Strengths and weaknesses - tablet version
[ ] Adalabers cards - tablet version
[ ] Footer - tablet version
[ ] Header - desktop version
[ ] Hero - desktop version
[ ] Who we are - desktop version
[ ] Strengths and weaknesses - desktop version
[ ] Adalabers cards - desktop version
[ ] Footer - desktop version
[ ] Published online


Instrument OpenTracing example service2 using the JavaAgent.

Fix issue with baggage propagating Camel prefixed headers, causing outbound component to throw exception.
Added agent rule test.

@davsclaus Updated one of the services in the opentracing example so that it uses the new OpenTracing Java Agent to register the tracer - with the rule now being distributed in the camel-opentracing component. If you could review please?

@davsclaus updates applied.

Thanks for the PR it has been merged. Do you mind closing this?

@davsclaus Thanks!


AWS-android-iot

Working on an Android application with AWS-SDK-android SDK, finding difficulty in getting the list of Things from AWSIoTClient though the required data is passed. It would be helpful if a Sample app is created for displaying the Things list also.

Hi akskulk,
Would you please elaborate on how you were using AWSIotClient to get things list?
Thanks.

@akskulk Hi, see if this is any help https://github.com/aws/aws-iot-device-sdk-java/blob/master/aws-iot-device-sdk-java-samples/src/main/java/com/amazonaws/services/iot/client/sample/shadow/ShadowSample.java

Closing this. Please open if the issue persists.


Add some support for monitoring the instance

Please add some support for monitoring the instance.

onyx-platform/onyx-starter#3

Closing, duplicated in #20. Will track from there.


Make numCorePartitions as 0 for tombstones

This PR changes the core partitions for tombstones to 0, so they can exist independently if they're deleted or marked as unused without affecting availability of other appended segments in the same co-partition space. This is particularly important in the following scenarios:

Concurrent replace and append to a datasource containing tombstones and data segments in the same time chunk (also, related coordinator duty: https://github.com/apache/druid/pull/15281)
If a user drops a tombstone segment and there are other data segments appended to it, the data segments should still be available

Release note

Tombstone segments have 0 core partitions. This means they can be dropped or removed independently without affecting availability of other appended segments in the same co-partition space. Note that removing tombstones with 1 core partition (prior to this change) that contain appended segments in the partition space can make the appended segments unavailable.

Key changed/added classes in this PR

TombstoneShardSpec.java
IndexerSQLMetadataStorageCoordinatorTest.java

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[x] added documentation for new or modified features or behaviors.
[x] a release note entry in the PR description.
[x] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[x] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] been tested in a test Druid cluster.

Conceptually, the change makes sense to me but taking another pass just to be sure that it doesn't break any existing assumption in the code. Also, there are a couple of test failures.


Allow pod termination log to be configured to allow a clear error message on exit

Feature:
When a pod exits, the termination log is checked to for a message and the pod status updated with this message if it is present. The default location is /dev/termination-log however you cannot write to this location from within the APB pod.
If we made the location of the termination log configurable then a ServiceBundle developer could write a user friendly error to this location and as we check it in https://github.com/automationbroker/bundle-lib/blob/master/runtime/watch_pod.go#L146 it would make its way back to the user.
It maybe an option to create a ASB module for making this as simple as possible for the developer.
ping @shawn-hurley

I almost think a very quick proposal would make sense for this one. I think that we may want to allow the apb to specify where they will be printing out the termination log and should be an update to the apb spec. @dymurray @djzager @mhrivnak

I also made an APB write a message automatically to /dev/termination-log, and I see that message in the output of oc describe pod in the Containers.apb.State.Message attribute.

I think I found the problem you likely hit. I tried using the lineinfile module, which tries to create a temporary file in the same directory as the file being written to. The error message was:
The destination directory (/dev) is not writable by the current user. Error was: [Errno 13] Permission denied: '/dev/.ansible_tmpF36YNStermination-log'

The solution is to use the unsafe_writes option of the lineinfile module. Here is an example (thanks to @dymurray who was the brain behind what's below):
- name: do something
  shell: "/bin/false"
  register: somethingout

- lineinfile:
    line: "There was an error. <insert helpful info here>"
    path: "/dev/termination-log"
    unsafe_writes: true
  when: somethingout.rc != 0

- fail:
    msg: "There was an error. <insert helpful info here>"
  when: somethingout.rc != 0

I also think that @johnkim76 might have some thoughts as he implemented https://github.com/openshift/ansible-service-broker/pull/837

SGTM... I agree with @shawn-hurley that we should update the apb spec to make this configurable in APBs

SGTM... I agree with @shawn-hurley that we should update the apb spec to make this configurable in APBs

I think we should define the use case concretely for why this needs to be configurable. Is it just:
"As an APB author, I want to create temporary files in the same directory as the termination log so I can use ansible's lineinfile module without setting unsafe_writes=true" ?
Are there other use cases?

@mhrivnak I too had no issues while I was demoing this via my simple APB (here)[https://github.com/johnkim76/lastop-cem-demo-apb/blob/master/roles/provision-lastop-cem-demo-apb/tasks/cem.yml#L9].  My thought was that making this configurable may not be a bad idea since the (allows)[https://kubernetes.io/docs/tasks/debug-application-cluster/determine-reason-pod-failure/] the /dev/termination-log path to be configurable.

@mhrivnak I am happy with your solution here. The main usecase was to allow a clear error message to be returned to the user from an APB. Once the location can be written too, I am not sure on the advantage of making it configurable and updating the Spec to allow it.

I am also ok with not making this configurable. @mhrivnak thoughts?

I am also ok with not making this configurable. @mhrivnak thoughts?

I would leave it as-is unless there is a concrete use case that demonstrates value in making it configurable. I don't think we've seen such a use case yet.


gk-deploy: make it possible to run gk-deploy from a different directory

Signed-off-by: Michael Adam<EMAIL_ADDRESS>

This change is

@jarrpa PTAL, this works for me and fixes an error in running the simple tests.

Ugh, this failed .. investigating...

@jarrpa, it was a shellcheck issue (not sure why my system did not catch it...)
fixed now.


Add support for Gx instances

I found this commit being applied to the azure-sdk-for-ruby project:
https://github.com/Azure/azure-sdk-for-ruby/commit/25559310960a914ea30c6342235f92261ad5955d
However, it doesn't seem to be in the 0.6.4 nor 0.6.5 release. Can you add a monkeypatch for additional vm_size support?
I'm currently building out the infrastructure for a demo that will be shown at Build 2015 at the end of April and would be nice to have the correct instances supported by then.
Thanks again!

I think there will be a new release of the ruby sdk shortly. There have been quite a few desirable changes over the past few weeks. I'll leave this open until the new rev is released and this project is upgraded.

Great, sounds good! Thanks for the update!

This should be good in master. Grab that latest bits and give it a go.


Configuring reboot window using environment variables as documented is not working

Description
Hi, I setup a reboot window of 2 hours via the environment variables but the reboot is not done during this window.
Impact
The node is not rebooted during the reboot window and does not get the new update.
Environment and steps to reproduce

Set-up: I setup FLUO as described at the Usage section
Task: for the reboot window I added the following lines to the update-operator.yaml file:

        env:
        ...
        - name: UPDATE_OPERATOR_REBOOT_WINDOW_START
          value: "09:00"
        - name: UPDATE_OPERATOR_REBOOT_WINDOW_LENGTH
          value: "2h"

Action(s): to trigger an update I'm jumping to another channel
Error: the node isn't rebooted during the reboot window

Expected behavior
The node with the update should be rebooted during the reboot window
Additional information
I can see that the labels and annotaions changes:
Labels:             flatcar-linux-update.v1.flatcar-linux.net/group=stable
                    flatcar-linux-update.v1.flatcar-linux.net/id=flatcar
                    flatcar-linux-update.v1.flatcar-linux.net/reboot-needed=true
                    flatcar-linux-update.v1.flatcar-linux.net/version=3374.2.5
                    v1.kubeone.io/operating-system=flatcar
Annotations:        flatcar-linux-update.v1.flatcar-linux.net/last-checked-time:<PHONE_NUMBER>
                    flatcar-linux-update.v1.flatcar-linux.net/new-version: 3510.1.0
                    flatcar-linux-update.v1.flatcar-linux.net/reboot-in-progress: false
                    flatcar-linux-update.v1.flatcar-linux.net/reboot-needed: true
                    flatcar-linux-update.v1.flatcar-linux.net/status: UPDATE_STATUS_UPDATED_NEED_REBOOT

I can't see any problems from the logs of the pod:
$ kubectl logs -n reboot-coordinator flatcar-linux-update-operator-85b99fd865-swqgc
I0328 06:58:07.376415       1 main.go:108] /bin/update-operator running
I0328 06:58:07.376546       1 leaderelection.go:248] attempting to acquire leader lease reboot-coordinator/flatcar-linux-update-operator-lock...
I0328 06:58:07.401639       1 leaderelection.go:258] successfully acquired lease reboot-coordinator/flatcar-linux-update-operator-lock
I0328 06:58:08.382212       1 operator.go:593] Found 0 rebooted nodes
<for the sake of brevity>
I0328 07:18:47.188086       1 operator.go:593] Found 0 rebooted nodes

And I see the environment variables correctly set to the pod:
kubectl exec -it -n reboot-coordinator flatcar-linux-update-operator-85b99fd865-swqgc -- sh
/bin $ env
KUBERNETES_SERVICE_PORT=443
KUBERNETES_PORT=tcp://<IP_ADDRESS>:443
HOSTNAME=flatcar-linux-update-operator-85b99fd865-swqgc
SHLVL=1
UPDATE_OPERATOR_REBOOT_WINDOW_START=09:00
HOME=/
TERM=xterm
UPDATE_OPERATOR_REBOOT_WINDOW_LENGTH=2h
KUBERNETES_PORT_443_TCP_ADDR=<IP_ADDRESS>
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_SERVICE_PORT_HTTPS=443
KUBERNETES_PORT_443_TCP=tcp://<IP_ADDRESS>:443
POD_NAMESPACE=reboot-coordinator
KUBERNETES_SERVICE_HOST=<IP_ADDRESS>
PWD=/bin

Additional question
Is it possible to set the reboot window only for office working hours, for example:
UPDATE_OPERATOR_REBOOT_WINDOW_START: Mon, Tue, Wed, Thu, Fri 09:00
UPDATE_OPERATOR_REBOOT_WINDOW_LENGTH: 8h

Good finding. It seems those environment variables were documented in cda5e86e1c00d4976ad43b85830216b1c4ea7dc7, but never implemented. They should be removed from the documentation.
Separately, we can discuss whether it make sense to actually implement it, as right now I don't see an obvious benefit in doing so. Is there some specific reason you would prefer to use environment variables instead of CLI flags?

Ok, I think I found the problem...
The time in the pod is GMT but we are at GMT +2
So 2 questions:
Is it possible to update the timezone for the pod?
Is it possible to set the reboot window only for office working hours, for example:
UPDATE_OPERATOR_REBOOT_WINDOW_START: Mon, Tue, Wed, Thu, Fri 09:00
UPDATE_OPERATOR_REBOOT_WINDOW_LENGTH: 8h

Ok, I opened [RFE] Add support for multiple reboot windows
This ticket than can be closed...
Thanks for your support 👍


"ghcr.io/ferretdb/ferretdb:1.23.0" is not work

FerretDB version
1.23.0
Backend
sqlite3
Environment

OS:docker
Deployment:
Deployment details:

What did you do?
docker-compose file:
version: "3.9"

services:
  ferretdb:
    image: ghcr.io/ferretdb/ferretdb:1.23.0
    network_mode: "host"
    environment:
      - FERRETDB_HANDLER=sqlite
      - FERRETDB_SQLITE_URL=file:/data/
    volumes:
      - ./configs/ferretdb_data:/data/
    restart: always

I use "mongodb://yingshaoxo:yingshaoxo@<IP_ADDRESS>:27017/?authMechanism=PLAIN" to do operations with pymongo
What did you expect to see?
I should see it is working normal.
What did you see instead?
But I see bugs here:
[msg_update.go:135 handler.(*Handler).updateDocument] [update.go:114 common.UpdateDocument] [collection.go:191 sqlite.(*collection).UpdateAll] [collection.go:177 sqlite.(*collection).UpdateAll.func1] attempt to write a readonly database (8), full error: {'ok': 0.0, 'errmsg': '[msg_update.go:135 handler.(*Handler).updateDocument] [update.go:114 common.UpdateDocument] [collection.go:191 sqlite.(*collection).UpdateAll] [collection.go:177 sqlite.(*collection).UpdateAll.func1] attempt to write a readonly database (8)', 'code': 1, 'codeName': 'InternalError'}

or
ferretdb_1  | 2024-08-06T07:03:45.919Z  WARN    clientconn/conn.go:641  Response message:
ferretdb_1  | {
ferretdb_1  |   "FlagBits": "[]",
ferretdb_1  |   "Checksum": int64(0),
ferretdb_1  |   "Sections": [
ferretdb_1  |     {
ferretdb_1  |       "Kind": 0,
ferretdb_1  |       "Document": {
ferretdb_1  |         "ok": 0.0,
ferretdb_1  |         "errmsg": "[msg_update.go:135 handler.(*Handler).updateDocument] [update.go:114 common.UpdateDocument] [collection.go:191 sqlite.(*collection).UpdateAll] [collection.go:177 sqlite.(*collection).UpdateAll.func1] attempt to write a readonly database (8)",
ferretdb_1  |         "code": 1,
ferretdb_1  |         "codeName": "InternalError",
ferretdb_1  |       },
ferretdb_1  |     },
ferretdb_1  |   ],
ferretdb_1  | }

This bug is extreamely obvious when the sqlite3 data folder is empty at the beginning, when you want to create a database or add data to it by using mongodb command

I also found if I use image: ghcr.io/ferretdb/ferretdb:1.23.0, everything works again.
version: "3.9"

services:
  ferretdb:
    # ./ferretdb-linux-amd64 --sqlite-url="file:data/"
    image: ghcr.io/ferretdb/all-in-one:1.23.0
    network_mode: "host"
    environment:
      - FERRETDB_HANDLER=sqlite
      - FERRETDB_SQLITE_URL=file:/data/
    volumes:
      - ./configs/ferretdb_data:/data/
    restart: always

It looks like ./configs/ferretdb_data is not writeble by the user ferretdb inside Docker container. Could you please check the permissions and ownership of that directory?

Why you guys think docker should not have root permission? In production, I always login in to my server with root permission.
root@service:~/it_has_alternatives/configs/ferretdb_data# ls -hl
total 676K
-rw-r--r-- 1 root root 4.0K Aug  6 06:54 it_has_alternatives_object.sqlite
-rw-r--r-- 1 root root  32K Aug  6 07:07 it_has_alternatives_object.sqlite-shm
-rw-r--r-- 1 root root 636K Aug  6 07:07 it_has_alternatives_object.sqlite-wal

To simplify the dev process, I'd better use old software forever
Thanks for the help


undocker: 1.2.2 -> 1.2.3

Description of changes
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)

Reword the commit according to the guidelines.
undocker: 1.2.2 -> 1.2.3

Or don't. I am not a cop.

Result of nixpkgs-review pr 341364 run on x86_64-linux 1

1 package built:

undocker

Or don't. I am not a cop.

Regardless I am gonna squash merge to make it appropriate anyway

Thanks! ❤


Support for multiple versions of the same package in different optional dependencies

Summary
I'm working on a project that requires different versions of the same package for two separate environments. For example, I need numpy==2.1.2 for one environment and numpy==2.0.0 for another. However, UV does not seem to support this scenario, as it results in dependency resolution conflicts.
Expected behavior
Is there a way to specify different versions of the same package in separate optional dependencies without causing conflicts?
Example
Here is a simplified example of my pyproject.toml file:
dependencies = [
    "some-shared-lib",
]

[project.optional-dependencies]
project1 = [
    "numpy==2.1.2",
    "some-other-lib",
]

project2 = [
    "numpy==2.0.0",
    "some-other-lib",
]

Issue
When I run uv sync with this configuration, I get No solution found when resolving dependencies for split (python_full_version == '3.11.*') error.
My current uv version is 0.4.19 installed from brew.
Why this would be useful
In cases like our repository, where different subprojects require different versions of the same package, not having this feature forces us to create a separate project for each subproject within the same repository. This approach is less convenient compared to having distinct optional dependencies that are exclusive to each other.

Duplicate of #6981
cc @BurntSushi


Setuptools is required at run-time, not just build-time

Previously, we relied on the fact that setuptools must be installed at build-time to ensure that it was also available at run-time. However, unless setuptools is explicitly listed as a run-time dependency, there's no guarantee that it won't be uninstalled. Package managers like Spack only add run-time dependencies to PYTHONPATH, so this distinction becomes even more important.
I'm not sure what versions of setuptools are required, but let me know if you want me to add an upper/lower bound.

As far as I understand there should be no run-time dependency of Fiona on setuptools.

There's one right here: https://github.com/Toblerity/Fiona/blob/1.9.0/fiona/fio/main.py#L7

Yes, that's it, CLI command discovery depends on setuptools's pkg_resources.


Need Query Support and Evaluation for DM58

Need Query Support and Evaluation for DM58 to
<IP_ADDRESS> Actions2:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for each SP identified as supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU.
b. Display the scaled engineering value for the requested SP.
<IP_ADDRESS> Fail/Warn criteria2:
a. Fail if NACK received for DM7 PG from OBD ECU
b. Fail, if DM58 not received (after allowed retries)
c. Fail, if expected unused bytes in DM58 are not padded with FFh.
d. Fail, if data returned is greater than FBh (for 1 byte SP), FBFFh (for 2 byte SP), or FBFFFFFFh (for 4 byte SP).
<IP_ADDRESS> Actions3:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for first SP identified as not supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU. (Use of an SP that supports test results is preferred when available).
<IP_ADDRESS>  Fail/Warn criteria3:
a. Fail if a NACK is not received

<IP_ADDRESS> Test Identifier
The test identifier (SPN 1224) shall echo the value of TID 245 (F516) that was provided in the directly addressed DM7 query. Additional TIDs for alternate uses of the DM58 format are not defined. The full range of test identifiers is described in <IP_ADDRESS>. See Table 25 for all other response requirements.
<IP_ADDRESS> Rationality Fault SPN
The rationality fault SPN (SPN 8555) identifies the content of the rationality fault SPN data value and determines the length of the data in rationality fault SPN data value. The rationality fault SPN shall provide the data given in SPN 4148 of the DM7 query submitted to request rationality fault information. The bit ordering shall match the SPN bit ordering defined in 5.7.1 where the value of the SPN conversion method SPN is zero.
<IP_ADDRESS> Rationality Fault SPN Data Value
The rationality fault SPN data value (SPN 8556) shall provide the data as defined in Table 25 for the SPN identified in <IP_ADDRESS>. The data will be the same value that is provided in rationality fault SPN’s assigned PG, when there are no fault conditions. When there are rationality fault conditions, the “normal process” data shall be provided using the SPN’s defined gain and offset to extrapolate the raw measurement. (An SPN’s defined gain and offset are defined by its slot assignment as documented by SAE J1939DA.) Where possible, the value measured for a threshold monitor is provided by DM58. When it is not possible to provide a value for a threshold monitor, the error indicator, FEh, is provided instead. When a value cannot be determined due to circuit failures (either externally or internally), an error indicator value (e.g FEh) is provided. The values beginning with FBh may also be provided as described by the SPN’s definition in SAE J1939DA and SAE J1939-71 Section 5.
The rationality SPN data value shall be reported in the lower order data bytes as required by the parameter data size starting in byte 5 and continuing in bytes 6, 7, and 8. Any rationality SPN data value bytes not required for reporting the SPN data value shall be filled with FFh. For example, if the data value SPN is a 2-byte parameter, the “data value data” is reported in bytes 5 and 6 and bytes 7 and 8 are filled with FFh. The presentation layer concepts defined in SAE J1939-71 Section 5 (i.e., little endian ordering) shall be observed when filling bytes 5 through 7. Enumerated types shall be presented in the same manner as they are provided as freeze frame values in DM25 starting in byte 5 bit 8.

Need parallel construction for parts 2 and 12 too

Parts 2 and 12 added
<IP_ADDRESS> Warn Criteria
a. Warn if all test results show initialized results across all SPs requested. [35]
<IP_ADDRESS> Actions2:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for each SP identified as supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU.
b. Display the scaled engineering value for the requested SP.
<IP_ADDRESS> Fail/Warn criteria2:
a. Fail if NACK received for DM7 PG from OBD ECU
b. Fail, if DM58 not received (after allowed retries)
c. Fail, if expected unused bytes in DM58 are not padded with FFh.
d. Fail, if data returned is greater than FBh (for 1 byte SP), FBFFh (for 2 byte SP), or FBFFFFFFh (for 4 byte SP).
<IP_ADDRESS> Actions3:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for first SP identified as not supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU. (Use of an SP that supports test results is preferred when available).
<IP_ADDRESS> Fail/Warn criteria3:
a. Fail if a NACK is not received
Note outline numbers for DM58 part 12 additions will modified for DM20 addition.
6.12.10 DM7/ DM30: Command Non-Continuously Monitored Test/Scaled Test Results
<IP_ADDRESS> Actions
a. DS DM7 with TID 250 for specific ECU address + SPN + FMI that had non-initialized values earlier in part 12 test 8.
b. Use responses to help verify coordinated DM11 code clear in this part (i.e., all or no ECUs clear).
For example, this will be evident in the increased count of initialized test results for the SPN and FMI pairs  that were listed with non-initialized values.
<IP_ADDRESS> Actions2:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for each SP identified as supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU.
b. Display the scaled engineering value for the requested SP.
<IP_ADDRESS> Fail/Warn criteria2:
a. Fail if NACK received for DM7 PG from OBD ECU
b. Fail, if DM58 not received (after allowed retries)
c. Fail, if expected unused bytes in DM58 are not padded with FFh.
d. Fail, if data returned is greater than FBh (for 1 byte SP), FBFFh (for 2 byte SP), or FBFFFFFFh (for 4 byte SP).
<IP_ADDRESS> Actions3:
a. DS DM7 with TID 245 (for DM58) using FMI 31 for first SP identified as not supporting DM58 in a DM24 response In step <IP_ADDRESS> to the SP’s respective OBD ECU. (Use of an SP that supports test results is preferred when available).
<IP_ADDRESS> Fail/Warn criteria3:
a. Fail if a NACK is not received

NOx-binning-GHG-Tracking-Additions-for-J1939-84-June-2-2021.docx

In consolidated text proffer

Task 3-4 Artifact considered complete


Rectangular selection overlap algorithm (and Firefox support)

Rectangular select uses checkIntersection but we could use getIntersectionList instead.  Not sure whether it's faster though...
Sadly, neither is supported on Firefox. https://github.com/thelonious/kld-intersections/ doesn't look easy to drop-in... have to duplicate entire DOM, and doesn't support transforms?

[x] Add warning about lack of rectangular drag support on Firefox

Chrome doesn't actually implement these correctly: you can select a rectangle, ellipse, or segment by selecting any rectangle that intersects their bounding box. ☹ (Pen strokes work only because of the silly way we're currently rendering them.)
So maybe we should use getIntersectionList, if it's available, as a filter.  Then check for actual intersection among those objects manually? An advantage of a manual check is that we can add an error threshold, especially useful for selecting objects without clicking on them exactly (formerly related: drag detection #109).

[ ] Use getIntersectionList only if available
[ ] First level: check for bounding-box intersection (like Chrome does now)
[ ] More efficient and correct for paths?
[ ] Correct intersection with line segments
[ ] Correct intersection with ellipses

When doing this, it would also make sense to do it in a way that supports polygon selection (#115), and line selection (#46).

I mentioned here that things outside of my selected rectangle, often get deleted. Would fixing this issue (#87) help with that?

Yes, and work is in progress to fix this: see #183.


JavaScript Dynamic Imports

OctoLinker version:  4.9.0
JavaScript is adding dynamic imports which look like this:
import("./module") // >> Promise<Module>

OctoLinker doesn't appear to support these yet, it would be nice if it did.

This seems like it should be relatively straight-forward to implement, if anyone would like to. You'll need to change require(\.resolve)? to ( require(\.resolve)? | import ) here, then port some valid and invalid tests into the corresponding forms using the dynamic import syntax.

Hi, I am not sure how the CI works, but I forked and created a branch called Issue #315.
https://github.com/OctoLinker/browser-extension/pull/318


The speed of quantized tflite model  is slower than its float model.

I benchmarked the models on the OnePlus 3T platform, The performance of tflite quantized models are worse than the float modes. Has anyone run into the same issue?
The command I used:
python tools/benchmark.py --output_dir=output --frameworks=all \
--runtimes=all --model_names=all \
--target_abis=arm64-v8a

model_name
device_name
soc
abi
runtime
MACE
SNPE
NCNN
TFLITE

InceptionV3
ONEPLUS A3010
msm8996
arm64-v8a
CPU
886.312
664.404
1578.295
997

InceptionV3
ONEPLUS A3010
msm8996
arm64-v8a
DSP

4.996

InceptionV3
ONEPLUS A3010
msm8996
arm64-v8a
GPU
153.049
141.246

InceptionV3Quant
ONEPLUS A3010
msm8996
arm64-v8a
CPU

1014.75

MobileNetV1
ONEPLUS A3010
msm8996
arm64-v8a
CPU
52.046
385.444
37.883
71.367

MobileNetV1
ONEPLUS A3010
msm8996
arm64-v8a
GPU
25.267
24.441

MobileNetV1Quant
ONEPLUS A3010
msm8996
arm64-v8a
CPU
36.743

145.778

MobileNetV2
ONEPLUS A3010
msm8996
arm64-v8a
CPU
40.625
413.553
29.208
76.021

MobileNetV2
ONEPLUS A3010
msm8996
arm64-v8a
GPU
17.546
14.966

MobileNetV2Quant
ONEPLUS A3010
msm8996
arm64-v8a
CPU
28.679

294.099

SqueezeNetV11
ONEPLUS A3010
msm8996
arm64-v8a
CPU
37.453
59.481
21.376

SqueezeNetV11
ONEPLUS A3010
msm8996
arm64-v8a
GPU
20.001
17.986

VGG16
ONEPLUS A3010
msm8996
arm64-v8a
CPU
452.521
1002.442
821.195

VGG16
ONEPLUS A3010
msm8996
arm64-v8a
DSP

136.465

VGG16
ONEPLUS A3010
msm8996
arm64-v8a
GPU
196.507

Another question: For Inception V3, the performance of DSP is ~132x faster than CPU. Is it normal?

DSP number looks like problematic, SNPE may has some errors for Snapdragon 821. @lee-bin @lydoc Can you have a look?

Another question: For Inception V3, the performance of DSP is ~132x faster than CPU. Is it normal?

I tested it on msm8996, and get results below. You can check the benchmark log, maybe it does not exit normally?

model_name
device_name
soc
abi
runtime
MACE
SNPE
NCNN
TFLITE

InceptionV3
MI 5s
msm8996
armeabi-v7a
DSP

67.856

VGG16
MI 5s
msm8996
armeabi-v7a
DSP

141.415

I benchmarked the models on the OnePlus 3T platform, The performance of tflite quantized models are worse than the float modes. Has anyone run into the same issue?
 We use available big cores to benchmark by taskset command for TFLITE benchmark and the default number of threads is 4. For msm8996, it has 2 big cores and 2 little, so you can use :
python tools/benchmark.py --output_dir=output --frameworks=all \
--runtimes=all --model_names=all \
--target_abis=arm64-v8a \
--num_threads=2

Besides, for some SoCs such as msm8996, it may be faster by using all of the CPUs instead of binding big cores CPUs. You can change the relative code: https://github.com/XiaoMi/mobile-ai-bench/blob/ff6667dafe6189b04724e583913d968322ca7c0e/tools/sh_commands.py#L394

@lee-bin Does XiaoMI 5S support both OpenCL GPU and DSP? I have tried Pix phone with msm8996, and got a runtime exception. The same issue can be found at https://developer.qualcomm.com/forum/qdn-forums/software/snapdragon-neural-processing-engine-sdk/34526

@lydoc I will try again later. Many thanks.

@liyancas  Yes. MI 5S support both OpenCL GPU and DSP, SNPE works fine on CPU/GPU/DSP of MI 5S.
So it seems like a problem of Pixel phone.

Google does not support OpenCL in their devices (unofficial source says that it's due to OpenCL trademark is hold by Apple).


Port SolovayKitaevDecomposition to Rust

Similar to #12197 I think this synthesis routine is the source of some warnings coming from numpy on arm64 macos. It's not causing spurious failures like with isometry but I expect if we move this to rust I expect it'll fix the warnings.


raft_test doesn't Step through messages generate by Raft.tick()?

from what I understant both local messages and network messages should be append into Raft.msgs, and some code is responsible for loop through Raft.msgs and call Raft.Step.
Is that correct?
so the local messages(MessageType_MsgHup and MessageType_MsgBeat) generate by Raft.tick() just sit in msgs, waiting to be process, until then it's state will not change.
if that is the case, the following code will not terminate
https://github.com/pingcap-incubator/tinykv/blob/1df74d600cb0c5001f32d2d21d6f89e9744ee3e0/raft/raft_test.go#L797-L799
https://github.com/pingcap-incubator/tinykv/blob/1df74d600cb0c5001f32d2d21d6f89e9744ee3e0/raft/raft_test.go#L853-L855

PTAL @NingLin-P

from what I understant both local messages and network messages should be append into Raft.msgs, and some code is responsible for loop through Raft.msgs and call Raft.Step.
Is that correct?

Actually, Raft.msgs only contains messages that this raft peer wants to send out, for local messages and received messages Raft.Step will be called by the user.

Thank you for replying! Appreciate it


Rebase against release 2.2 version

Rebase CSI driver against latest version of release 2.2

cc @openshift/openshift-team-storage

/retest


Modifying ecr check script to output in more detail

Current:
if image_count > 5: return Fail
if image_not_exist_in_ecr: return Fail

To be:
if image_count > 5:
  1. select_old_images
  2. check_is_using to selected images
  3. if true, return service name

if image_not_exist_in_ecr: return "Not exist in ECR"

it seems to be already applied


Consider removing the human atlas

The human atlas is not perfect, when I created it I didn't finish everything correctly so the meshes have some problems (e.g. origin/scale.. ).  Since I didn't see much interest in it at the time I didn't develop it further and as such it's the only BG atlas in version < 1.

Given all of this, I would consider removing it from the list of available atlases until an improved version is made, as this can cause problems for people interested: https://github.com/brainglobe/brainrender/issues/196
Internally in BG there was some initial effort to improve the atlas by Rami Hamati, but I'm not sure if it has progressed very far.
cc: @adamltyson  @vigji

We could remove it, or somehow mark that it's a WIP? Either make explicit what the version number means, or change the name?

I've seen people use this atlas (mostly for figures etc), so we should keep it in. Keeping the issue open to track improvements to it.


Couple of exceptions when running evinse on javascript projects

overflowdb.traversal.filter.StringPropertyFilter$InvalidRegexException: invalid regular expression
Caused by: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 9

Exception in thread "main" overflowdb.traversal.filter.StringPropertyFilter$InvalidRegexException: invalid regular expression
Caused by: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence near index 9

Full exception output attached.
chen.txt

This must be fixed already. Wait for the new atom to be released for retesting though.

@cerrussell can you check with the latest main branch of atom?
https://github.com/AppThreat/atom

@prabhu I just updated and still got the same thing.

@cerrussell, are you testing atom directly after building?


Client won’t show up

Quasar version
1.4.1
Server installed .NET version
.NET 6.0
Server operating system
Windows 10/Server 2019/2016
Client installed .NET version
.NET 6.0
Client operating system
Windows 10/Server 2019/2016
Build configuration
Release
Describe the bug
I created the software for the client and send it to them. I turned listening on. But as they opened it (with admin rights) nothing happened on my dashboard. All windows security features are off on their PC and it is brand new (now other software installed). So I tried opening the software on my own laptop and it worked just fine. Why is that? And is there anything I could do about it? Thank you.
How to reproduce
Install Quasar, click on „build“, build the software, send it to your client, start to listen
Expected behavior
The client‘s PC should show up on my dashboard.
Actual behavior
My dashboard stays completely empty and nothing happens.
Additional context
No response

Hello, this is a port forwarding and/or firewall issue, not Quasar issue.


Panic on debug

Substrate master @ https://github.com/paritytech/substrate/commit/1c2eaa3bc6a5659fb70cfcc88037573921612064.
local testnet with alice and bob (see below)
Send any tx from any client (I mostly use Polkadot JS apps but the js library should be the same)
Panics here:

https://github.com/paritytech/substrate/blob/1c2eaa3bc6a5659fb70cfcc88037573921612064/core/client/src/block_builder/block_builder.rs#L129-L134
Which will actually not be triggered in a release build.
exact commands:
sub --base-path=/tmp/alice --chain=local --alice
sub --base-path=/tmp/bob --chain=local --bob

sub: aliased to cargo run -- --validator

cc @jacogr

This was a false alarm. Seems to be fixed now.


VSCode - Debug logs are not consistent between platforms

Steps to Reproduce

Steps to reproduce the behavior:

run flutter create my_app
cd my_app

add the file .vscode/launch.json :
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Run",
      "request": "launch",
      "type": "dart",
      "program": "lib/main.dart"
    },
  ]
}

Then for iOS, macOS, and chrome, press F5 to run the application with VSCode. The logs are not consistent. For example, "💪 Running with sound null safety 💪" log is only visible on chrome.
Because of that, I spent quite some time trying to find why my app was not running null-safely on macOS and iOS (it was not the same code). But from this issue, I believe it is running null-safely but it is only not logged?
I also opened a issue there: https://github.com/Dart-Code/Dart-Code/issues/3812
Expected results:
The logs should be consistent between the platforms.
Actual results:
Chrome:

VSCode launch
Launching lib[/main.dart]() on Chrome in debug mode...
lib/main.dart:1
This app is linked to the debug service: ws://<IP_ADDRESS>:53511[/ozhDRx6xrqM]()%3D[/ws]()
Debug service listening on ws://<IP_ADDRESS>:53511[/ozhDRx6xrqM]()=[/ws]()
💪 Running with sound null safety 💪
Connecting to VM Service at ws://<IP_ADDRESS>:53511[/ozhDRx6xrqM]()=[/ws]()

Command line
Running with flutter run lib/main.dart
Launching lib/main.dart on Chrome in debug mode...
Waiting for connection from debug service on Chrome...             16.1s
This app is linked to the debug service: ws://<IP_ADDRESS>:54213/a29Uqn05_vY=/ws
Debug service listening on ws://<IP_ADDRESS>:54213/a29Uqn05_vY=/ws

💪 Running with sound null safety 💪

🔥  To hot restart changes while running, press "r" or "R".
For a more detailed help message, press "h". To quit, press "q".

An Observatory debugger and profiler on Chrome is available at: http://<IP_ADDRESS>:54213/a29Uqn05_vY=
The Flutter DevTools debugger and profiler on Chrome is available at:
http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:54213/a29Uqn05_vY=

iOS:

VSCode launch
Launching lib[/main.dart]() on iPhone 12 Pro Max in debug mode...
lib/main.dart:1
Xcode build done.                                            8.1s
Connecting to VM Service at ws://<IP_ADDRESS>:54344[/4nX6XeDauZg]()=[/ws]()

Command line
Running with flutter run lib/main.dart
Launching lib/main.dart on iPhone 12 Pro Max in debug mode...
Running Xcode build...
 └─Compiling, linking and signing...                      2,328ms
Xcode build done.                                            8.0s
Syncing files to device iPhone 12 Pro Max...                        91ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

💪 Running with sound null safety 💪

An Observatory debugger and profiler on iPhone 12 Pro Max is available at:
http://<IP_ADDRESS>:54468/GF1QrQ6IbsE=/
The Flutter DevTools debugger and profiler on iPhone 12 Pro Max is available at:
http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:54468/GF1QrQ6IbsE=/

macOS:

VSCode launch
Launching lib[/main.dart]() on macOS in debug mode...
lib/main.dart:1
Connecting to VM Service at ws://<IP_ADDRESS>:54540[/cAD_JOHmRow]()=[/ws]()

Command line
Running with flutter run lib/main.dart
Launching lib/main.dart on macOS in debug mode...
Building macOS application...
Syncing files to device macOS...                                   104ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

💪 Running with sound null safety 💪

An Observatory debugger and profiler on macOS is available at: http://<IP_ADDRESS>:53306/4qNSLtaDOHU=/
The Flutter DevTools debugger and profiler on macOS is available at: http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:53306/4qNSLtaDOHU=/

Logs

Analyzing flutter_app...
No issues found! (ran in 1.6s)

[✓] Flutter (Channel stable, 2.8.1, on macOS 11.5.1 20G80 darwin-x64, locale en-GB)
    • Flutter version 2.8.1 at /Users/valentin/flutter/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 77d935af4d (7 weeks ago), 2021-12-16 08:37:33 -0800
    • Engine revision 890a5fca2e
    • Dart version 2.15.1

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /usr/local/Caskroom/android-sdk/4333796
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[!] Xcode - develop for iOS and macOS (Xcode 12.5.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.0.0.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.27.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 11.5.1 20G80 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 97.0.4692.99

! Doctor found issues in 2 categories.

Versions (please complete the following information):

VS Code version: 1.63.2
Dart extension version: v3.27.2
Flutter extension version: v3.27.0
Dart/Flutter SDK version:
Running flutter --version :

Flutter 2.8.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 77d935af4d (7 weeks ago) • 2021-12-16 08:37:33 -0800
Engine • revision 890a5fca2e
Tools • Dart 2.15.1

Hi @ValentinVignal, Thanks for filing the issue. I am able to see the same behavior on stable and the master channel The "unsound null safety" log is only available in chrome logs and not in other platforms.

IOS
Launching lib/main.dart on iPhone 12 Pro in debug mode...
Xcode build done.                                           37.3s
Connecting to VM Service at ws://<IP_ADDRESS>:49207/2uV0_lZQbmk=/ws

Android
Launching lib[/main.dart]() on Redmi K20 Pro in debug mode...
lib/main.dart:1
Warning: Mapping new ns [http://schemas.android.com/repository/android/common/02]() to old ns [http://schemas.android.com/repository/android/common/01]()
Warning: Mapping new ns [http://schemas.android.com/repository/android/generic/02]() to old ns [http://schemas.android.com/repository/android/generic/01]()
Warning: Mapping new ns [http://schemas.android.com/sdk/android/repo/addon2/02]() to old ns [http://schemas.android.com/sdk/android/repo/addon2/01]()
Warning: Mapping new ns [http://schemas.android.com/sdk/android/repo/repository2/02]() to old ns [http://schemas.android.com/sdk/android/repo/repository2/01]()
Warning: Mapping new ns [http://schemas.android.com/sdk/android/repo/sys-img2/02]() to old ns [http://schemas.android.com/sdk/android/repo/sys-img2/01]()
Warning: Mapping new ns [http://schemas.android.com/repository/android/common/02]() to old ns [http://schemas.android.com/repository/android/common/01]()
Warning: Mapping new ns [http://schemas.android.com/repository/android/generic/02]() to old ns [http://schemas.android.com/repository/android/generic/01]()
Warning: Mapping new ns [http://schemas.android.com/sdk/android/repo/addon2/02]() to old ns [http://schemas.android.com/sdk/android/repo/addon2/01]()
Warning: Mapping new ns [http://schemas.android.com/sdk/android/repo/repository2/02]() to old ns [http://schemas.android.com/sdk/android/repo/repository2/01]()

chrome
Launching lib/main.dart on Chrome in debug mode...
This app is linked to the debug service: ws://<IP_ADDRESS>:65306/KOlcs-N0Yn4%3D/ws
Debug service listening on ws://<IP_ADDRESS>:65306/KOlcs-N0Yn4=/ws
💪 Running with sound null safety 💪
Connecting to VM Service at ws://<IP_ADDRESS>:65306/KOlcs-N0Yn4=/ws

macos
Launching lib/main.dart on macOS in debug mode...
--- xcodebuild: WARNING: Using the first of multiple matching destinations:
{ platform:macOS, arch:x86_64, id:6A745C96-D83E-5C8D-8EE9-5958E598001B }
{ platform:macOS, name:Any Mac }
Connecting to VM Service at ws://<IP_ADDRESS>:65025/azrxZb7SAF0=/ws

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.0, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.10.0 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5f105a6ca7 (3 days ago), 2022-02-01 14:15:42 -0800
    • Engine revision 776efd2034
    • Dart version 2.16.0
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 60.1.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (4 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:5555                     • android-arm64  • Android 11 (API
      30)
    • iPhone 12 Pro (mobile) • 14F40EC6-3B73-469A-A1C0-8CF0B152290F • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.1 21C52
      darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome
      98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 2.10.0-1.0.pre.371, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.10.0-1.0.pre.371 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d1285eef1b (2 days ago), 2022-02-02 00:50:20 -0500
    • Engine revision 5bbdb7a6f7
    • Dart version 2.17.0 (build 2.17.0-74.0.dev)
    • DevTools version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 60.1.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (4 available)
    • Redmi K20 Pro (mobile) • <IP_ADDRESS>:5555                     • android-arm64  • Android 11 (API
      30)
    • iPhone 12 Pro (mobile) • 14F40EC6-3B73-469A-A1C0-8CF0B152290F • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.1 21C52
      darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome
      98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Thanks for filing this and the detailed information (it really helps us when triaging!). However, since from the logs you shared it looks like the message is correctly showing from the command line tool, and the problem is that VSCode is not showing it, I will close this issue in favor of https://github.com/Dart-Code/Dart-Code/issues/3812, as it seems like the command-line tool is working correctly.
Thanks again for filing the detailed issue however!

@christopherfujino I believe the problem is that Flutter isn't sending the output when using --machine. I would expect the issue is also present in Android Studio for this same reason. Below is my comment from the other issue explaining what I think the problem is.

This seems to be a difference in Flutter behaviour, so should be filed at https://github.com/flutter/flutter/.
For non-web, the line is printed here:
https://github.com/flutter/flutter/blob/d7688ca0930fe80d162361be30405a15c929ada9/packages/flutter_tools/lib/src/run_hot.dart#L1012
This is part of printHelp(), so it only appears when Flutter prints the shortcut keys for using the terminal. When running from the IDE (which runs flutter run --machine), this code is not called, so the message is not printed.
However for Web, it looks like both the standard and --machine versions go through a different path and into resident_web_runner which always prints the message:
https://github.com/flutter/flutter/blob/61a0add2865c51bfee33939c1820709d1115c77d/packages/flutter_tools/lib/src/isolated/resident_web_runner.dart#L638
I suspect the best fix will be to move the message in run_hot.dart to somewhere called in both modes so that the message is always printed for all types (it seems like useful info to have in the IDE output too).
If you raise in Flutter, please post the link back here. Thanks!


Update README.md

Pull Request
Related issue
Unknown
What does this PR do?

Fixed an error in the README.md regarding the plugins.js

bors merge


Is channel aggregation block stronger than SE block?

Does replacing SE with CA in any network have an increase of 0.6?

Hi, @xuesongnie, thanks for your question. Unfortunately, we haven't applied the proposed CA to other architectures except for MogaNet in our experiments. But, I believe that CA will achieve performance gains when applied to the FFN module (e.g., in ViTs and MetaFormer variants), and it is likely to outperform SE under the same parameter budget. Meanwhile, CA doesn't require the extra Norm layer compared to SE, which might be easier to adopt in ViTs. If you are interested in CA, maybe you can try it in your experiments, and we can discuss it in a specific scenario. Please free to ask me or contact me at WeChat (Lupin_1998) if you have further questions.

I closed this issue if there is no more question. You can reopen it or start a new issue if you have more questions. Thanks again for your attention.


V2 - (geolocation BUG) - Geolocation doesn't seem to update for where the user really is

Checked & Found in testflight build iSeaTree 2.0 (34).
Geolocation package is suppose to check where the user is and report the location in BOTH the Tree Benefits Calculator AND in the saved Firebase issue.
Notably MOST of the users data originates from Shoreline, WA....and that's where the user was when the /testflight/ package was downloaded.
ToDO:

Identify source of bug
Fix, and verify that the correct City, State is being using when the iTree API is being called
Fix, and verify that the correct location is showing up in the Tree Benefits Calculator UI AND in Firebase

Example of an error (prod database. User 'treemama2'.).
Record 'zRbRTfTuPP5oHniLkd9P'
https://console.firebase.google.com/project/iseatree-dev/firestore/data/trees/zRbRTfTuPP5oHniLkd9P
Actual Location: Seattle, WA
Reported (Erroneous) Location: Shoreline, WA

Database errors:

Fixed as of 2.0(Build 36) - this is great thanks @JonathanKoerber !

Fixed as of 2.0(Build 36) - this is great thanks @JonathanKoerber !


Update: Error Boundary

https://issues.redhat.com/browse/RHCLOUD-34203
“Error boundary without error” example doesn’t show the error components (icon, text)

closing as this is intended


Tailscale client not checking the mode of the IP address

Environmental Info:
K3s Version:

Node(s) CPU architecture, OS, and Version:

Cluster Configuration:

Describe the bug:

Tailscale client asks the tailscale server for its IPs. Tailscale server provides a slice of IPs. We are assuming that ipv4 will be in the first position, which is always the case when using tailscale. However, when using alternatives, such as the headscale server, this is not the case
Steps To Reproduce:

Installed K3s:

Deploy k3s+tailscale with https://github.com/k3s-io/k3s/pull/7807 in an ipv4 only k3s using headscale default config. Apiserver fails to start with the error:
Jun 27 13:03:54 mbuil-vm0 k3s[7974]: Error: error creating bootstrap controller: service IP family "<IP_ADDRESS>/16" must match public address family "fd7a:115c:a1e0::1"
Jun 27 13:03:54 mbuil-vm0 k3s[7974]: time="2023-06-27T13:03:54Z" level=fatal msg="apiserver exited: error creating bootstrap controller: service IP family \"<IP_ADDRESS>/16\" must match public address family \"fd7a:115c:a1e0::1\""

and the reason is that we are passing an ipv4-only serviceIP and clusterIP but the advertiseIP is ipv6.
Expected behavior:

K3s starts correctly
Actual behavior:

K3s fails to start
Additional context / logs:

Is this getting backported to v1.24?

Is this getting backported to v1.24?

Nope. Tailscale did not end up in 1.24 because it was a mess

Validated using commit id be442433538a39c0a568516fd39a06e364d5d075 from master branch
Environment Details
Infrastructure
Cloud EC2 instance
Node(s) CPU architecture, OS, and Version:
Ubuntu 20.04
Cluster Configuration:
Single node
Config.yaml:
ipv4 only
$ cat config.yaml
write-kubeconfig-mode: 644
token: <TOKEN>
cluster-init: true
cluster-cidr: <IP_ADDRESS>/16
service-cidr: <IP_ADDRESS>/16
vpn-auth: "name=tailscale,joinKey=<joinKEY>,controlServerURL=http://<tailscalewithheadscale.com>"

Results from ipv4 node
$ ip a
...
3: tailscale0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UNKNOWN group default qlen 500
    link/none
    inet <IP_ADDRESS>/32 scope global tailscale0
       valid_lft forever preferred_lft forever
    inet6 fd7a:115c:a1e0::3/128 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::2f8a:aa3b:a27a:5156/64 scope link stable-privacy
       valid_lft forever preferred_lft forever

$ kubectl get nodes
NAME              STATUS   ROLES                       AGE   VERSION
ip-172-31-9-100   Ready    control-plane,etcd,master   14m   v1.27.3+k3s-be442433

$ kubectl get pods -A
NAMESPACE     NAME                                     READY   STATUS      RESTARTS   AGE
kube-system   coredns-77ccd57875-h8vhq                 1/1     Running     0          13m
kube-system   helm-install-traefik-bccww               0/1     Completed   1          13m
kube-system   helm-install-traefik-crd-v6rz9           0/1     Completed   0          13m
kube-system   local-path-provisioner-957fdf8bc-x5dt7   1/1     Running     0          13m
kube-system   metrics-server-648b5df564-kh2mr          1/1     Running     0          13m
kube-system   svclb-traefik-26ff4f39-h5whl             2/2     Running     0          13m
kube-system   traefik-64f55bb67d-m2fm9                 1/1     Running     0          13m

Logs
$ journalctl -u k3s|grep advertise
Jul 20 18:49:00 ip-172-31-9-100 k3s[2893]: time="2023-07-20T18:49:00Z" level=info msg="Running kube-apiserver --advertise-address=<IP_ADDRESS> --advertise-port=6443 --allow-privileged=true

$ journalctl -u k3s|grep node-ip
Jul 20 18:49:07 ip-172-31-9-100 k3s[2893]: time="2023-07-20T18:49:07Z" level=info msg="Running kubelet --address=<IP_ADDRESS> --allowed-unsafe-sysctls=net.ipv4.ip_forward,net.ipv6.conf.all.forwarding --anonymous-auth=false --authentication-token-webhook=true --authorization-mode=Webhook --cgroup-driver=systemd --client-ca-file=/var/lib/rancher/k3s/agent/client-ca.crt --cloud-provider=external --cluster-dns=<IP_ADDRESS> --cluster-domain=cluster.local --container-runtime-endpoint=unix:///run/k3s/containerd/containerd.sock --containerd=/run/k3s/containerd/containerd.sock --eviction-hard=imagefs.available<5%,nodefs.available<5% --eviction-minimum-reclaim=imagefs.available=10%,nodefs.available=10% --fail-swap-on=false --healthz-bind-address=<IP_ADDRESS> --hostname-override=ip-172-31-9-100 --kubeconfig=/var/lib/rancher/k3s/agent/kubelet.kubeconfig --node-ip=<IP_ADDRESS>

Note:
Issue found during ipv6 testing is tracked separately here: https://github.com/k3s-io/k3s/issues/8020
We were not able to reproduce the issue. Will iterate back when we have a fix (maybe unrelated)


fix(typechecker): less permissive equality for optional types

Closes #649

[x] I have updated CHANGELOG.md
~[ ] I have documented my contribution in Tact Docs: https://github.com/tact-lang/tact-docs/pull/PR-NUMBER~
[x] I have added tests to demonstrate the contribution is correctly implemented: this usually includes both positive and negative tests, showing the happy path(s) and featuring intentionally broken cases
[x] I have run all the tests locally and no test failure was reported
[x] I have run the linter, formatter and spellchecker
[x] I did not do unrelated and/or undiscussed refactorings

First we check whether X? is null and return false in this case because null cannot be equal to X

In general, equality comparisons only make sense for terms of the same type. The check you describe should be done by the user, e.g. if (x != null) { return x!! == y } where, for instance, x: Int? and y: Int.

Same for comparison of X? and X?: First we check if either both of these are null or both of these are not null and compare them accordingly, and in other cases (first is null and second is not or vice versa) we just return false

Look at the tests: we don't forbid equality comparisons for X? and X? in general, just for non-equality types like Builder or structs.

Why do we forbid comparing X and X?? It makes sense to allow comparing these two

wait, we don't actually forbid that -- we check assignability of types
so, my example above is not correct, because Int and Int? are both equality types

@Gusarich Added a test for that: https://github.com/tact-lang/tact/pull/650/files#diff-570728cab178f5e1fa5f1885b32ee9826e95de3a357d341adbc331578591ab1a


Contributor action

I think it would be good to add a note about the yarn changeset. I was wondering if any updates to the version or changelog are required but did not find any information regarding that part :)

This is what this PR will do 😄, I am adding docs around creating PR's and changesets and the GitHub action will comment a link to those docs.

I think it would be good to add a note about the yarn changeset. I was wondering if any updates to the version or changelog are required but did not find any information regarding that part :)

This is what this PR will do 😄, I am adding docs around creating PR's and changesets and the GitHub action will comment a link to those docs.


Regression in minor version 1.1.0

Hello, I'd like to report a regression bug in v1.1.0. Last working version is v1.0.36.
Usecase:
function MyComponent() {
  const [mutate] = useMutation(event => {
    event.preventDefault()
    return MyAPI.post('/endpoint/', event.target.elements) // simplified
  }
  return <form onSubmit={mutate}>
    // omitted
  </form>
}

In v1.0.36, it correctly prevents default on the event and submits data. In v1.1.0 however, an error is thrown: Cannot read property "elements" of undefined because event no longer has a target. We all know React synthetic events cannot be used asynchronously so I expect something in v1.1.0 change and the mutate function is not run immediately anymore.
I don't believe this use case is that uncommon to become unsupported in a minor release.
Workaround is to wrap it, but I though I would just report it.
function MyComponent() {
  const [mutate] = useMutation(data => {
    return MyAPI.post('/endpoint/', data)
  }
  const onSubmit = event => {
    event.preventDefault()
    mutate(event.target.elements) // simplified
  }
  return <form onSubmit={onSubmit}>
    // omitted
  </form>
}

Thank you for your work!

I believe, you have to call event.persist() before using the event in the asynchronous call.
https://reactjs.org/docs/events.html#event-pooling

You have to call event.persist() to use the event in the asynchronous call. I don't think you should rely on library internal implementation hoping it persists it for you.

Yep. This is out of scope for React Query. It has never prevented default, nor made any guarantees around synchronously calling on mutate. Persist the event and handle this in your own callbacks before you trigger the Mutation


ELO brand

elo test number
6362 9700 0045 7013

Hey @Fivell, I've got some more Elo BINs that I found after some research. Can I add them?

closed by #57


Upgrade to bevy_egui 0.26

There's a new version of bevy_egui out.

I'm fine waiting!

There is now a 0.27 release of both egui and bevy_egui. I am also fine waiting, my app compile as it is, but some behaviors are the subject of bugs fixed in 0.27.


Returning promise will cause a React state error "update on a component that hasn't mounted yet."

My RR7 part of the loader looks like this:
const academiesCourses = db.query.Course.findMany({
	columns: {
		id: true,
		name: true,
	},
	with: {
		academy: {
			columns: {
				slug: true,
			},
		},
	},
	where: and(
		ne(Course.id, course.id),
		eq(Course.academyId, course.academyId),
	),
}).execute()

return {
       ....
	academiesCourses,
       .....
}

As you can see I just return a promise from loader. When I navigate from other page to this page I got client error message
hook.js:608 Can't perform a React state update on a component that hasn't mounted yet. This indicates that you have a side-effect in your render function that asynchronously later calls tries to update the component. Move this work to useEffect instead. Error Component Stack
    at JsonRenderer (react-router-devtool…v=98655d0b:38736:23)
    at div (<anonymous>)
    at InfoCard (react-router-devtool…v=98655d0b:39398:13)
    at div (<anonymous>)
    at div (<anonymous>)
    at li (<anonymous>)
    at RouteSegmentInfo (react-router-devtool…v=98655d0b:39480:27)
    at ol (<anonymous>)
    at div (<anonymous>)
    at PageTab (react-router-devtool…v=98655d0b:39591:18)
    at div (<anonymous>)
    at div (<anonymous>)
    at ContentPanel (react-router-devtool…v=98655d0b:40496:23)
    at div (<anonymous>)
    at div (<anonymous>)
    at MainPanel (react-router-devtool…v=98655d0b:40579:30)
    at div (<anonymous>)
    at DevTools (react-router-devtool…v=98655d0b:41051:28)
    at RDTContextProvider (react-router-devtool…v=98655d0b:33721:39)
    at ReactRouterDevTools (react-router-devtool…v=98655d0b:41104:30)
    at RequestProvider (react-router-devtool…v=98655d0b:37352:36)
    at react-router-devtool…v=98655d0b:41162:10
    at Wrapped (with-props:7:15)
    at div (<anonymous>)
    at div (<anonymous>)
    at body (<anonymous>)
    at html (<anonymous>)
    at Layout (root.tsx:69:35)
    at RenderedRoute (chunk-X5ZNL6V3.js?v=5ee2615a:5357:26)
    at RenderErrorBoundary (chunk-X5ZNL6V3.js?v=5ee2615a:5316:5)
    at DataRoutes (chunk-X5ZNL6V3.js?v=5ee2615a:5945:3)
    at Router (chunk-X5ZNL6V3.js?v=5ee2615a:6030:13)
    at RouterProvider (chunk-X5ZNL6V3.js?v=5ee2615a:5775:3)
    at RouterProvider2 (<anonymous>)
    at RemixErrorBoundary (chunk-X5ZNL6V3.js?v=5ee2615a:6945:5)
    at HydratedRouter (react-router_dom.js?v=3acd5a31:145:46)
    ```
When I remove dev-tools everything looks OK.

Thank you for the report! I know exactly what it is, I'll fix it asap!

@jurajkrivda mind confirming it works with:
npm i https://pkg.pr.new/forge42dev/react-router-devtools@172


Redirect error message needs more clarity

What problem does this feature solve?
Regarding this:
https://github.com/vuejs/vue-router/blob/677f3c1f714fb61cc495345e535409b1cbb90429/src/util/errors.js#L14-L16
This error message is unclear. Why is redirection an issue, exactly? What really happened here to raise an exception, and how should the developer address it?
What does the proposed API look like?
N/A

The thing is it's not an error, it's a navigation failure. It happened when you do next('/other-location'). This is documented.
Remember to use the discord chat to ask questions 🙂


Create new release

Create a new release and maybe auto-create with github actions?

Would it be possible to consider a version compatible with proxmark3?, for reading data

hi, feel free to do a PR doing it

I think this issue can be closed?

I think this issue can be closed?

why?

@ElDavoo the Proxmark3 cannot be used directly with the libnfc library. Here's why:
Protocol and Compatibility:
The Proxmark3 uses its own firmware, communication protocol, and specific tools (like the Proxmark3 client software or CLI). The libnfc library, on the other hand, is designed for devices that use standard NFC protocols, such as readers based on PN53x chips (e.g., ACR122U readers).

the Proxmark3 cannot be used directly with the libnfc library

welcome back!
I guess you wanted to tag @ManuelPq ?

yes, thank you :)


Feature Request

Provide the ability to change the color of the output text

Sure, will add that!

added!


Nitro returns error differently for /api and /routes

Environment
Operating System: Linux
Node Version: v18.18.0
CLI Version: 3.10.1
Nitro Version: 2.9.1
Package Manager<EMAIL_ADDRESS>Reproduction
https://stackblitz.com/edit/github-zyt6se?file=routes%2Ffoo.ts,api%2Ffoo.ts,public%2Findex.html
Describe the bug
Check the response for /api/foo and /foo endpoints. Each of them throws same 404 error in the handler, but:

/foo -> returns error as html page
/api/foo -> returns error as json object as expected

Additional context
No response
Logs
No response

@manniL Fixed the link 🙈
Based on the docs /api is just a convenient way to create routes and automatically prefix them with /api - https://nitro.unjs.io/guide#api.
This PR partially fixes the problem :) https://github.com/unjs/nitro/pull/1763
But some projects may want to have multiple "api" endpoints (f.e. /api, /api-cms, /api-commerce etc), so they should have possibility to response with JSON when throwing errors.

@pi0 Just ran into this again. What is the purpose of current /routes directory?
My suggestion:

There should be just routesDir, not routeDir and apiDir (IMO naming "routes" is preferable Router -> routes)
This means Nitro will always return html response OR json response
A new config variable to enable/disabled html responses for full app (IMO html responses should be disabled by default because an API should return json)

Additionally I found a bug for current latest v2:
When changing apiBaseURL to any other URL, it returns html pages.
Reproduction:
https://github.com/MickL/nitro-apibaseurl-bug

GET localhost:3000/api2 -> Should return JSON, not html page
GET localhost:3000/api2/not-found -> Should return JSON, not html page


Unicode operators ≤≥≠≢≡≣⩶⩵«»⋙‖⁇∈∉∋∌▷‥…≔→⇒

For fun, here are some simpler and less controversial Unicode operators from #555.
The only one I'm less sure about is ≡ mapping to ===. But given that ≠ makes != and ≢ makes !==, this feels natural. And anyway it's good to encourage === over ==. Alternatively, we could use ≣ for === and ≡ for ==...
Incidentally, TIL there are symbols for double and triple equals: ⩵ and ⩶.
Going forward:

I'm less sure about the symbols with equals and such because they look like comparisons to me, but Civet uses them as assignments.
I think the power operators, specifically ², would be handy, but that's a little more complicated, so left for the future.
If there are other Unicode operators you think I should add now, let me know!

I think these are good. ≡ mapping to === makes sense to me. ∈ and ∉ are cool. Looking forward to exploring more in the future!

, we could use ≣ for === and ≡ for ==...

I prefer this combo, I guess. 💭

we could use ≣ for === and ≡ for ==...

This would follow the pattern: for every line beyond =, you add another =. @STRd6 what do you think? (With coffeeEq, I would imagine ≡ still maps to ===, just like == does.)

we could use ≣ for === and ≡ for ==...

This would follow the pattern: for every line beyond =, you add another =. @STRd6 what do you think? (With coffeeEq, I would imagine ≡ still maps to ===, just like == does.)

This sounds good, either way is fine with me.

OK, I switched, and also added → and ⇒ for functions (obvious in hindsight!) and inclusion operators ∋ and ∌. Plus tests and docs. Let me know if there are any final comments before merging.

Looks good to me! 👍


Docs update

Documentation needs an update to all the new features such as users and utility functions

JSDoc in progress


support for node 0.6.x

The current version depends on node 0.5.x :(

Yep, that's intentional, contracts.js doesn't work under 0.6.x. When node moved from 0.5.x to 0.6.x they downgraded their version of V8 which has some blocking Proxy bugs.
Just tested out node 0.7.3 and it looks like they've finally updated V8. As soon as that becomes stable we'll switch to it.


Display statistics trend values (percentages) in addition to symbols

Current Implementation
The statistics tiles use an arrow and color to indicate the trend for values shown in the app
For instance, today, Tuesday, March 16, 2021 the Trend for the 7-Day Average of Confirmed New Infections is shown as upwards.
The fact that the trend actually represents an increase of 23.0% compared to the previous week is not explicitly displayed. The red color just says that the increase was more than 5%.

ComparisonValue \ Steady band %
Daily1%
Weekly5%

Confirmed New Infections7-Day Average

✔

Warnings by App Users7-Day Average

✔

7-Day Incidence
✔

7-Day R Value
✔

Suggested Enhancement
The app should show the numerical value of the trend in % terms, in addition to the trend symbol.
If the % change is shown then the UI also needs to display whether it is a weekly comparison or a daily comparison. A daily 1% change is approximately equivalent to a 7% weekly change.
Expected Benefits
The magnitude of the trend should be clearer to users so they can better judge the overall national pandemic situation.

Internal Tracking ID: EXPOSUREAPP-5840

Thank you for the submission. We've added this to the wishlist in Jira as EXPOSUREAPP-5840.

Corona-Warn-App Open Source Team

Extensive trend information is available through
https://www.coronawarn.app/en/analysis/ > https://www.rki.de/DE/Content/InfAZ/N/Neuartiges_Coronavirus/Situationsberichte/COVID-19-Trends/COVID-19-Trends.html?__blob=publicationFile#/home
I withdraw this request, since the % comparison with the previous day is not so helpful. The graphs available through the above link give a much better picture.


add setting to enable/disable status bar buttons

Adds a setting to enable status bar buttons.
It will default to true so the initial experience is the same.

LGTM, Thanks


Created RecursiveUploadEnabledInterface

Q
A

Bug fix?
No

New feature?
Yes

BC breaks?
No

Deprecations?
No

Fixed tickets
#908

Now the pull request seems correct :)

Why has this been closed?

No needed any more as of reimplementation here #1092
Now every upload is recursive 😉

great! 👍


Update Cargo.toml

Updates dependency to the patch version of 0.9.8
Advisory

Good stuff, thanks @Dylan-DPC!


Build failing due to docker pull limit.

https://travis-ci.com/github/tiangolo/full-stack-fastapi-postgresql
Is it possible you could login to docker or switch container repositories?

Thanks! This is now running on GitHub Actions, if the errors comes again I'll check it out. :nerd_face:


Buggy mod

When i use it on 1.20.1 servers things like pearl damage doesn't shake the camera directionally but when i take fire damage or fall damage its still the same directional damage...

Could you send a complete list of the mods you have installed?

starlight, entity culling, antighost, appleskin, architectury api, bedrodium, boosted brightness,
carpet, carpet fixes, chunky, clean f3, cloth config api, clumps, completeconfig, c2me, dashloader, debugify, dynamic fps, enhanced block entities, fabric language kotlin, faster random, ferritecore, immediately fast, indium, iris shaders, krypton, lithium, log cleaner, logical zoom, memory leak fix, midnightlib, mixin conflict helper, mod menu, model gap fix, more culling, more culling extra, no resource pack warnings, noxesium, player health indicators, reese's sodium options, server pack unlocker, shulker box tooltip, small totem pop, sodium, sodium extra, threadtweak, toomanyplayers, totemcounter, verymanyplayers, yetanotherconfiglib, ukulib, better beds, better fps distance, connectivity, do not tilt camera in relation to damage direction, fastload, get it together drops!, raknetify, servercore, simple armour hud

I still can't reproduce the issue, even with that exact set of mods.

Mods I tested with
antighost-1.20-fabric0.83.0-1.1.5.jar
appleskin-fabric-mc1.20-2.5.0.jar
architectury-9.1.12-fabric.jar
bedrodium-0.2.2.jar
betterbeds-1.3.0-1.19.3.jar
betterfpsdist-fabric-1.20.1-3.8.jar
boosted-brightness-2.2.0+1.20.1.jar
c2me-fabric-mc1.20.1-0.2.0+alpha.10.96.jar
carpet-fixes-1.20-1.16.1.jar
Chunky-1.3.92.jar
CleanF3-0.4.0-mc1.20.jar
cloth-config-11.1.106-fabric.jar
Clumps-fabric-1.20.1-<IP_ADDRESS>.jar
completeconfig-2.5.0.jar
connectivity-fabric-1.20.1-4.5.jar
cupboard-fabric-1.20.1-1.5.jar
dashloader-5.0.0-beta.1+1.20.0.jar
Debugify-1.20.1+2.0.jar
DoNotTiltTheCameraInRelationToDamageDirection-1.0.1+1.19.4.jar
dynamic-fps-2.4.0.jar
enhancedblockentities-0.9+1.20.jar
entityculling-fabric-1.6.2-mc1.20.jar
fabric-api-0.86.1+1.20.1.jar
fabric-carpet-1.20-1.4.112+v230608.jar
fabric-language-kotlin-1.10.8+kotlin.1.9.0.jar
Fastload+1.18.2-1.20-3.4.0.jar
fastrandom-1.3.jar
ferritecore-6.0.0-fabric.jar
getittogetherdrops-fabric-1.20-1.3.1.jar
ImmediatelyFast-1.1.26+1.20.1.jar
indium-1.0.23+mc1.20.1.jar
iris-mc1.20.1-1.6.5.jar
krypton-0.2.3.jar
lithium-fabric-mc1.20.1-0.11.2.jar
logcleaner-1.0.0.jar
logical_zoom-0.0.20.jar
memoryleakfix-fabric-1.17+-1.1.1.jar
midnightlib-fabric-<IP_ADDRESS>.jar
MixinConflictHelper-1.2.0.jar
modelfix-1.14-fabric.jar
modmenu-7.2.1.jar
moreculling-1.20.1-0.19.0.jar
MoreCullingExtra-1.1-1.20.1.jar
no-resource-pack-warnings-1.3.0.jar
noxesium-0.1.9.jar
PlayerHealthIndicators-1.1.0-1.20.1.jar
raknetify-fabric-0.1.0+alpha.5.91-all.jar
reeses_sodium_options-1.6.4+mc1.20.1-build.94.jar
servercore-fabric-1.3.7+1.20.1.jar
shulkerboxtooltip-fabric-4.0.4+1.20.1.jar
simple-armor-hud-1.20.1-1.3.1.jar
smallpop-1.20.1-0.2.jar
sodium-extra-0.5.0+mc1.20.1-build.111.jar
sodium-fabric-mc1.20.1-0.5.0.jar
spu-1.6.jar
starlight-1.1.2+fabric.dbc156f.jar
threadtweak-fabric-1.20.1-0.1.0.jar
toomanyplayers-1.20-1.1.4.jar
totemcounter-1.3.0+mc1.20.jar
ukulib-0.7.0+1.20.jar
vmp-fabric-mc1.20.1-0.2.0+beta.7.100-all.jar
yet-another-config-lib-fabric-3.1.0+1.20.jar

Try testing without Carpet + Carpet Fixes, Debugify, and/or Noxesium. It's a mostly random guess, but I think they would be the most likely to modify something like this.

Stale.


[Feature]: add codeql workflow

Description
Is your feature request related to a problem? Please describe.
The repository contains code in javascript, it does not have workflow for code scanning.
Describe the solution you'd like
I aim to implement the CodeQL workflow to automate security checks. CodeQL, GitHub's code analysis engine, will identify vulnerabilities in the code and present the findings as code scanning alerts. This workflow will be activated for every push, commit, and pull request through GitHub Actions.
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a IWOC'24 contributor

@harmeetsingh11 seems interesting assigning this issue to you, kindly raise a successful PR.


Update of gulp-tslint removes format

Steps to reproduce and a minimal demo of the problem
Clone a clean copy of this project and insert some tslint-warnings like:

change src/client/app/components/home/home.components.ts:2 to import { Store } from "@ngrx/store";
run gulp tslint

Current behavior
Warning is thrown without colors and format. In my case the linting process even crashes with some errors and stops the build process but I can't produce a mwe.
Expected/desired behavior
Formatted and colored warnings like with<EMAIL_ADDRESS>without errors in gulp-tslint
Other information
A change in package.json:104 to "gulp-tslint": "^4.3.3", corrects this behavior.

We are now at 6.1.2.

The update to<EMAIL_ADDRESS>didn't help. I'm working with an older version of this project with<EMAIL_ADDRESS>and the lint messages are colored and styled. The lint messages in the current version of this project are grey and not styled. The configuration with<EMAIL_ADDRESS>was correct and the styling of the  current gulp-tslint doesn't work for me.

That's how it looked in an earlier version with<EMAIL_ADDRESS>
And that's how it looks now with<EMAIL_ADDRESS>


Annotation handling when grouping signals

This is a follow up of #625.
When loading information using the rawio framework, annotations are handled differently depending on the grouping modes of the signals. When splitting signal into individual Neo objects, all channel-wise annotations are loaded and attached to the objects. However, when grouping the signals according to common aspects, some channel-wise annotations might be lost if they can not be converted into an array_annotation.
Here is an example using the NixIO Raw implementation for loading
# writing block with two AnalogSignal traces and individual annotations
with NixIO(filename,'ow') as io:
    bl0 = Block(my_custom_annotation='hello block')
    bl0.segments.append(neo.Segment())
    bl0.segments[0].analogsignals.append(neo.AnalogSignal([1,2,3]*pq.V, sampling_rate=1*pq.Hz, anno1 = 'myfirstannotation'))
    bl0.segments[0].analogsignals.append(neo.AnalogSignal([1,2,3]*pq.V, sampling_rate=1*pq.Hz, anno2 = 'mysecondannotation'))
    io.write_block(bl0)

# test for signal_group_mode='split-all'
with NixIOFr(filename) as io:
    bl1 = io.read_block(signal_group_mode='split-all')
    assert len(bl0.annotations) == len(bl1.annotations)
    assert len(bl1.segments[0].analogsignals) == len(bl0.segments[0].analogsignals)
    for aid in range(len(bl0.segments[0].analogsignals)):
        for k,v in bl0.segments[0].analogsignals[aid].annotations.items():
            assert bl1.segments[0].analogsignals[aid].annotations[k] == v

# test for signal_group_mode='group-by-same-units'
with NixIOFr(filename) as io:
    bl1 = io.read_block(signal_group_mode='group-by-same-units')
    assert len(bl0.annotations) == len(bl1.annotations)
    assert len(bl1.segments[0].analogsignals) == 1
    for anasig in bl0.segments[0].analogsignals:
        for k,v in anasig.annotations.items():
            # these assertion fail due to grouping of AnalogSignals leading to missing annotation information
            assert k in bl1.segments[0].analogsignals[0].array_annotations
            assert bl1.segments[0].analogsignals[0].annotations[k] == v

Here, since both objects have different annotations keys, the annotation is not handled as an array_annotation, but ignored during loading. Maybe annotation of this type should be expanded to be represented as array_annotations to not be lost during the loading of the data?
@samuelgarcia: What do you think?

Hi Julia,
this example is a bit tricky because because we create 2 analosignal splitted we save then and we try to load then grouped (here poissble because same size/sr/units but a special case).
I don't known how it is possible to handle annotations when assymetric (not all channel).
Maybe we could add a option load_assymtric_annoation_array_when_grouping_anyway=True/False by adding some None in the array. But it is for a very special case. At least we could have a wrning when annoation are not all loaded because of an internal assymety.
What do you think ?

Hi Samuel,
I agree this case is probably special when looking at output data of a recording system, but think this case is much more likely to occur in the context of data analysis and corresponding results being saved (e.g. using Nix). For example, the user might want to have an original and a processed version of the recorded data in two different AnalogSignal objects, whereas the processed version has the same basic properties as the original, permitting a grouping into a single AnalogSignal, but containing additional annotations e.g. to describe the processing performed.
There are different options on how to handle such asymmetric channels

extending the annotation to all channels by introducing an empty annotation for all other channels (therefore creating additional overhead for annotation storage) as you described above
-providing these infos as regular annotations, loosing all advantages of array_annotations, but not creating too much overhead. Here, the annotations could be added below a special annotation key sparse_channel_annotations.

For solution 2, how would be the annoations dict ? Would we have the channel index as key for this sub dict ?
For instance:
anasig.annotations['sparse_channel_annotations'] = { 0 : dict(anno1 = 'myfirstannotation'),
                                                                                1 : dict(anno2 = 'mysecondannotation'), }

Yes, that's what I had in mind. But as said, this solution looses all array_annotation advantages, so if we implement this, we should add an explicit, huge warning with it.

This second solution is easier to implement and easier to anderstand for a user.
So I vote for this with a a warning.
Do you want I do this ?
I you want to have a look you start with create_analogsignal_array_annotations in io/proxyobject.py.
This function should return 2 dict:

array_annotations for symetric across channel annotataions
sparse_channel_annotations : for special case

What do you think ?

Ok, if @apdavison does not object, then we go for the sparse channel annotations. Feel free to code ahead ;)

@JuliaSprenger
Hi julia.
A last question before trying to implement this.
In anasig.annotations['sparse_channel_annotations'] what is the key. channel index ? channel id ?
If channel index it is a bit more complicated, because it will created with the global channel index but each time we want a slice along channel axis the key will be wrong.
And we will need to implement at object some reammping key only for this sparse_channel_annotations sub dict.
What do yout think ?

Hi @JuliaSprenger I really don't see how we will implement this.
The bad is the key : is it the channel index ? what append when we slice along channel axis ? The key then will be bad.
I think this sparse_channel_annotations is not a so good idea implemented with keys. Maybe with sparse arrays it would be better to be robust when slicing.


switching provisioner

switching to network-automation/lightbulb provisioner

Internal red hat mojo page launches tomorrow or early next week for networking workshop we are out of time, network-automation will become a separate project


Add googletest tests

Make the unittests as a seperate target. Use GoogleTest framework, since it has builtin Visual Studio support and is widely known. Add the following tests for now:

[x] Migrate old string test
[x] Migrate old AtlasNode test
[x] Basic math tests
[x] Add to CI

Tried compiling it locally, seems like it's related to dynamic/static linking settings
gtestd.lib(gtest-all.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MTd_StaticDebug' doesn't match value 'MDd_DynamicDebug' in globals.obj [F:\Development\overgrowth\Build\tests\OvergrowthTests.vcxproj]


fix: Resizes notification window on replace

The message parameter is also allowed to be a list of strings. Hence, compared to the previous message, it's viewport dimensions can change both horizontally and vertically.
This sets the existing window width & height to fit the new notification buffer.

To reproduce the issue, run this snippet on the master.
local prev = require("notify")("Somewhat long initial test message", "INFO", { title =  "Note" })
require("notify")({ "A multi line", "replacement" }, nil, { replace = prev })

Notice the notification body only contains the string "A multi line". The second "replacement" line is not visible.

And here's the expected result with this change:

Thanks for the PR!


USHIFT-19: add example config file to rpm

Add /etc/microshift/microshift.yaml with the current defaults,
all commented out.
Closes #663

/cc @fzdarsky

/type documentation

/lgtm


Persistent offlineRetryProvider between sessions

The 'offlineRetryProvider' uses the internal repositories to find offline operations, and the retry works perfectly when transitioning from offline to online within the same session. However, creating data offline, closing the app, and then reopening it with an internet connection does not automatically trigger the retry logic for the previously saved offline operations. I know I can manage this manually by iterating through my repositories and adding an 'isSynced' flag to all my models, but I was hoping it would be possible for the offline operations to be saved across sessions somehow.
On a side note, I would like to know if you have a community Discord or Slack. I have thoroughly read your documentation but still have some questions. My company is about to start an 'Offline First' project, and we are currently exploring our options in existing frameworks. Also, do you recommend waiting for v2, or will it be easy enough to migrate when it is ready?

Sorry for the late response! You are right about offlineRetryProvider. Actually it has been removed in v2 to push specific implementations to user-space (primitives will keep being supported). It also needs thorough testing.
Appreciate the fact that you were considering Flutter Data for your project. I created and have been maintaining this package since 2019 but I had some personal issues and had to step away for a few months. At the moment I am unsure about my future involvement here but I'm talking to someone who could potentially carry on. Honestly v2 has a significant amount of changes, I'll try to keep the API as unchanged as possible, but I'm not sure how easy it will be to migrate. A Slack community is a great idea, actually.


OAuth login error using IDCS

Describe the bug
Receive an error when logging into CiviForm via IDCS
To Reproduce
Steps to reproduce the behavior:

Go to https://civiform.seattle.gov/loginForm
Click on "Login:
See error: {"error":"invalid_client","error_description":"The OAuth Client app is inactive or the OAuth Client facet is not enabled for app clientId: c1cb583904dd44359423313eba1ecb0b, name: CiviForm. ECID: MhxMV01o910000000"}

Expected behavior
Would expect it to do to the IDCS login page

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

We are currently investigating the issue. No ETA at the moment. Will update when we have more details.

Thank you!
[Title: City of Seattle logo]Elise Kalstad
City of Seattle, Innovation & Performance
206-256-5515 |<EMAIL_ADDRESS>Learn more about Innovation & Performance: seattle.gov/innovation-performancehttps://www.seattle.gov/innovation-performance
Facebookhttps://protect2.fireeye.com/v1/url?k=daf2de2b-8569e719-daf2f69b-8697e44c76c2-ac8cbbaf40b6a748&q=1&e=a18b8788-8c55-40b3-b962-7521a34eb6bf&u=https%3A%2F%2Fwww.facebook.com%2Fseattlemayorsoffice%2F | Twitterhttps://twitter.com/CityofSeattle | Subscribe to Mayor Durkan's E-Newsletterhttp://wwwqa.seattle.gov/mayor/subscribe
From: Hung-Ming Hsu @.>
Sent: Tuesday, June 29, 2021 4:47 PM
To: seattle-uat/civiform @.>
Cc: Kalstad, Elise @.>; Author @.>
Subject: Re: [seattle-uat/civiform] Login Error (#1534)
CAUTION: External Email
We are currently investigating the issue. No ETA at the moment. Will update when we have more details.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://protect2.fireeye.com/v1/url?k=57e4a4fe-087f9dd8-57e48c4e-867666c9b37a-ed8e7c7bdb7fd9c3&q=1&e=7104dd8b-c685-46e3-800c-35b0f36dd839&u=https%3A%2F%2Fgithub.com%2Fseattle-uat%2Fciviform%2Fissues%2F1534%23issuecomment-870990691, or unsubscribehttps://protect2.fireeye.com/v1/url?k=eac49bdc-b55fa2fa-eac4b36c-867666c9b37a-c8f7e582aaaf4505&q=1&e=7104dd8b-c685-46e3-800c-35b0f36dd839&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUQYIYYIMHXHF6CC77ANWDTTVJLODANCNFSM47RFPGJQ.

The service should be operational now. Please check and let us know if the issue is still ongoing.
We identified the issue may be coming from the IDCS server and City's IDCS team helped us resolve this.

Tested! Looks great. Thanks for all your help on this, Hung-Ming!
-Elise
[Title: City of Seattle logo]Elise Kalstad
City of Seattle, Innovation & Performance
206-256-5515 |<EMAIL_ADDRESS>Learn more about Innovation & Performance: seattle.gov/innovation-performancehttps://www.seattle.gov/innovation-performance
Facebookhttps://protect2.fireeye.com/v1/url?k=daf2de2b-8569e719-daf2f69b-8697e44c76c2-ac8cbbaf40b6a748&q=1&e=a18b8788-8c55-40b3-b962-7521a34eb6bf&u=https%3A%2F%2Fwww.facebook.com%2Fseattlemayorsoffice%2F | Twitterhttps://twitter.com/CityofSeattle | Subscribe to Mayor Durkan's E-Newsletterhttp://wwwqa.seattle.gov/mayor/subscribe
From: Hung-Ming Hsu @.>
Sent: Wednesday, June 30, 2021 11:05 AM
To: seattle-uat/civiform @.>
Cc: Kalstad, Elise @.>; Author @.>
Subject: Re: [seattle-uat/civiform] OAuth login error using IDCS (#1534)
CAUTION: External Email
The service should be operational now. Please check and let us know if the issue is still ongoing.
We identified the issue may be coming from the IDCS server and City's IDCS team helped us resolve this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://protect2.fireeye.com/v1/url?k=57ae9aeb-0835a3d9-57aeb25b-8697e44c76c2-96bb496a3d2bd7f3&q=1&e=6dacd2e0-44e1-4230-8cfd-14bf9fa6d726&u=https%3A%2F%2Fgithub.com%2Fseattle-uat%2Fciviform%2Fissues%2F1534%23issuecomment-871618182, or unsubscribehttps://protect2.fireeye.com/v1/url?k=b74fd4fd-e8d4edcf-b74ffc4d-8697e44c76c2-dda0c8f0f60e772b&q=1&e=6dacd2e0-44e1-4230-8cfd-14bf9fa6d726&u=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAUQYIY6MOZH5IEW4ZJMDZBTTVNMERANCNFSM47RFPGJQ.


Fennel + love2d + VISUAL eval silently stops eval working

Hey, thanks for putting together such a great project! Not sure if this is to do with Conjure, love2d, configuration problem, or something I've done, but thought I'd start with Conjure.
I've put together a reproducible test case here: https://github.com/EdwardIII/reproduce-fnl-conjure
If I evaluate the outer expression (<leader>ee) on each expression after a fresh start from (local state...:
https://github.com/EdwardIII/reproduce-fnl-conjure/blob/main/game.fnl#L6
downwards, it works great:
; Sponsored by @rgm ❤
; --------------------------------------------------------------------------------
; "love ." (started)
; --------------------------------------------------------------------------------
; eval (current-form): (local state {:started 0})
nil
; --------------------------------------------------------------------------------
; eval (current-form): (fn duration [start end] (- end start))
#<function: 0x10e11778>
; --------------------------------------------------------------------------------
; eval (current-form): (fn now [] (love.timer.getTime))
#<function: 0x10de53c0>
; --------------------------------------------------------------------------------
; eval (current-form): (now)
18330.517284708

But if I select the same text with VISUAL, evaluate it with <leader>E, I no longer get the eval return output:
; Sponsored by @rgm ❤
; <snip>
; eval (selection): (local state {:started 0}) (fn duration [start end] (- end start)) (fn now [] (love.timer.getT.
nil

And any future attempts to eval behave the same, e.g. if I go to down (now) and hit <leader>ee, I get no more output:
; --------------------------------------------------------------------------------
; eval (current-form): (now)
; --------------------------------------------------------------------------------
; eval (current-form): (now)

Conjure settings in .vimrc:
Plug 'Olical/conjure', {'tag': 'v4.22.1'}
let g:conjure#filetype#fennel = "conjure.client.fennel.stdio"
let g:conjure#client#fennel#stdio#command = "love ."

Version:
NVIM v0.5.0
Build type: Release
LuaJIT 2.1.0-beta3
On MacOS Big Sur 11.4 (20F71)

Possibly on further investigation I think the problem might be with the repl rather than Conjure, as when I try to paste in more than a few lines I see similar behaviour (https://gist.github.com/EdwardIII/130b1ab9926b584dae0544eae19acbf6) so asking around.

Yep pretty sure it's interactions with the repl rather than Conjure, so closing this and linking to the new issue:
https://gitlab.com/alexjgriffith/min-love2d-fennel/-/issues/6


Added link to the Google Play badge

It looks like the link is broken. So does this PR still makes sense?

No, because the app isn't anymore on gplay


v0.28.3 // Site will not load after upgrade

Describe the bug
It seems that issue #1921 is still hapening. I've just upgraded from v0.27.5 to v0.28.3 and get the same error.
I did a composer install running PHP 7.4.2
Steps To Reproduce
Steps to reproduce the behavior:

Get latest release branch
Do a composer install
Visit BookStack url
See error

Expected behavior
The login page should show
Your Configuration (please complete the following information):

Exact BookStack Version: v0.28.3
PHP Version: 7.4.2
Hosting Method Nginx:

Never mind. Did a clean installation and got it working.


Lava refusing to flow 1.21.1 + feature request

Unsure what's going on, I've messed around with letting the lava drop down after breaking blocks under it, but the individual puddles of lava don't flow down the sides of blocks. They'll connect if beside each other and one is flowing straight down, but they don't flow off of a block. Water works normally.
I also have a feature request, as there's a mod similar to this in 1.16 on Forge that allows you to collect a multiple block wide puddle, but this isn't a feature in this mod. It's not entirely necessary, especially once the flow is fixed, but it'd be a nice QoL feature.

Literally just found another oddity: If you place a block in the fluids, it straight up deletes it. Not sure if that's intentional, but if it was, it'd be awesome of the fluids are pushed out of the block instead of deleted.

Thank you for noticing this.
It's more of a laziness thing than a bug. I was well aware that I never updated lava to use the same flow method as water, so its still using the rather basic mechanics that the original DHMO employed.
I might look into how much work would be needed to implement IF flow for lava. But it may not be worth the effort as the successor mod to this will have built in fluid agnosticity.


[Razor Tooling] Remove TypeForwarded TagHelper services from MS.VS.Editor.Razor.

@alexgav @ToddGrun I recently moved our TagHelper services from the editor.razor dll to the CodeANalysis.Razor.Workspaces dll. We're type forwarding all the types so you wont have any issues but at some point in the future we should do a coordinated insertion to change your references.
PR in question: https://github.com/aspnet/AspNetCore-Tooling/pull/211

Why would we do anything to follow up on this ever??? TypeForwards are free and they work forever. If you want to remove them in 2 years we can.

Will never do this


Library size

Library size is about 23 mb on making an apk which drastically change the apk size in development. Mainly the jinlibs itself is 20mb with .so files please if possible then help me reduce apk size I only want to use cropping part of li

Any updates on this ?

You can only use jinlibs for one architecture like "armeabi-v7a", to cropping purpose it will work correctly.