[HeroSystem6eHeroic] Updates for compatibility with the new dark mode.

Changes / Comments
Changes made to preserve the appearance of the sheet and roll templates between light and dark modes.
Replaced most instances of 'label' where possible since Roll20 appears to override its text color settings.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[X] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[X] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


wifi password can't handle special chacter

I have a wifi password with & in it. WIFIManager is not able to connect to it. Error:
Trying to connect to mygreatwifi...
E (275725) wifi:sta is connecting, return error
Traceback (most recent call last):
  File "main.py", line 7, in <module>
  File "wifimgr.py", line 60, in get_connection
  File "wifimgr.py", line 317, in start
  File "wifimgr.py", line 200, in handle_configure
  File "wifimgr.py", line 88, in do_connect
OSError: Wifi Internal Error
MicroPython v1.21.0 on 2023-10-05; Generic ESP32 module with ESP32

try this:
# version 1.9 compatibility     try:         ssid = match.group(1).decode("utf-8").replace("%3F", "?").replace("%26", "&")         password = match.group(2).decode("utf-8").replace("%3F", "?").replace("%26", "&")     except Exception:         ssid = match.group(1).replace("%3F", "?").replace("%26", "&")         password = match.group(2).replace("%3F", "?").replace("%26", "&")

@ebolisa's suggestion has been added as default behavior in the captive portal version of this awesome library

@ebolisa's suggestion has been added as default behavior in the captive portal version of this awesome library

Instead of adding all possible combination of characters, why not adding a simple routine to convert them all:
txt = "%3F,%26"

def decode_html(txt):
    dec = json.loads('"' + txt.replace('%', '\\u00') + '"')
    return dec

print(decode_html(txt))  --> ? & and etc.


Values of Dataquality sections of metadata are not saved into database

Description
Values of Dataquality  sections (lineage, specificationtitle..) of metadata are not saved into database. For repository is used PostgrelSQL. We use it in production enviroment https://rpi.gov.sk/en as well as I made test in my local env. I made a check of parser ISO.py from owslib and it works OK. Thanks a lot.
Environment : production / dev

operating system: Ubuntu 22

Python version: prod env 3.8/ local env 3.10

pycsw version: tested 2.6.1 / 3.0

source/distribution

[ ] git clone

web server

[ ] Apache/mod_wsgi

Steps to Reproduce
Try to load to pycsw this record and check specificationtitle in the database.
testxml.zip
Additional Information

@tomkralidis I found error in code https://github.com/geopython/pycsw/blob/027fe70c186988d3ddb44f03f855a5d79548bad0/pycsw/core/metadata.py#L1352 . There is bad definition of condition  if hasattr(md.identification, 'dataquality'):  ... dataquality is not part of md.identification  and condition should be defined  if hasattr(md, 'dataquality')...
Also following part of code from line 1356 is bad.
`
if hasattr(md.dataquality, 'specificationdate'):
_set(context, recobj, 'pycsw:specificationDate',
md.dataquality.specificationdate[0].date)
_set(context, recobj, 'pycsw:SpecificationDateType',
md.dataquality.specificationdate[0].datetype)
`
specificationdate doesn't have attributes date and datetype defined in owslib iso parser.  It is also necessary change definition of specificationdate in owslib iso parser


Bespoke XML for X by @grapesmoker and @cmc333333 and fixes for #1444

This PR includes XML for Regulation X that parses cleanly with the parser as of this PR and works with the configuration in regulations-configs.
This fixes our issue with missing interpretations for subparts A and B.

Nice! Merging this in so that I can put it to good use this afternoon.


Is this a separate settings system than IMvxSettings?

Just considering it for a new app. Thanks!

yes


Maintenance: Clean up some compiler warnings

Spotted with MinGW32 g++

uimports.cpp: IMAGE_DATA_DIRECTORY.VirtualAddress is a DWORD
type, not a pointer type, so compare against a scalar type.
creatwth.cpp: LoadNtHeaderFromProcess returns a BOOL, so compare
with falsey check.

i686-w64-mingw32-g++ -c -Wall -Wextra -Wpedantic ./creatwth.cpp

# In file included from ./creatwth.cpp:329:
# ./uimports.cpp: In function 'BOOL UpdateImports32(HANDLE, HMODULE, const CHAR**, DWORD)':
# ./uimports.cpp:109:48: warning: NULL used in arithmetic [-Wpointer-arith]
#   109 |     if (inh.IMPORT_DIRECTORY.VirtualAddress != NULL && inh.IMPORT_DIRECTORY.Size == 0) {
#       |                                                ^~~~
# ./creatwth.cpp: In function 'BOOL DetourUpdateProcessWithDllEx(HANDLE, HMODULE, BOOL, const CHAR**, DWORD)':
# ./creatwth.cpp:624:80: warning: NULL used in arithmetic [-Wpointer-arith]
#   624 |     if (hModule == NULL || LoadNtHeaderFromProcess(hProcess, hModule, &inh) == NULL) {
#       |                                                                                ^~~~

Microsoft Reviewers: Open in CodeFlow

Nice finds, thanks for the PR!

Nice finds, thanks for the PR!

In this PR, the inequality sign in the original text was written as an equal sign,
inh.IMPORT_DIRECTORY.VirtualAddress != NULL => inh.IMPORT_DIRECTORY.VirtualAddress == 0 ???
which destroyed the original intent. It is estimated that it should be reproduced without testing.

In this PR, the inequality sign in the original text was written as an equal sign,
inh.IMPORT_DIRECTORY.VirtualAddress != NULL => inh.IMPORT_DIRECTORY.VirtualAddress == 0 ???
which destroyed the original intent. It is estimated that it should be reproduced without testing.

@sonyps5201314 @bgianfo
Apologies, fixed in #168

@sonyps5201314 @bgianfo
Apologies, fixed in #168


feat: jest and react-testing-library setup

Added Jest and React Testing Library Setup

label not set


Copy CF summary to mod's description

And thereby change the description away from the example mod text

Also add link to cg

done


Issues with dlsym

Our .bazelrc file is identical to the examples, and our WORKSPACE and BUILD files are only slightly modified for a custom library, but we keep getting a linker error relating to dlsym:
/home/awesome/.cache/bazel/_bazel_awesome/3310ac2ce17be999eb013d710f5b6147/external/__bazelrio_roborio_toolchain_linux/frc2022/roborio/bin/../arm-frc2022-linux-gnueabi/usr/lib/gcc/arm-frc2022-linux-gnueabi/7.3.0/../../../../../../arm-frc2022-linux-gnueabi/bin/ld: external/__bazelrio_com_revrobotics_frc_revlib-driver_linuxathenastatic/linux/athena/static/libREVLibDriver.a(CANSparkMaxHeartbeat.o): undefined reference to symbol 'dlsym@@GLIBC_2.4'
external/__bazelrio_roborio_toolchain_linux/frc2022/roborio/arm-frc2022-linux-gnueabi/lib/libdl.so.2: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

As far as we can tell, this is an issue with dlsym not being present in the Linux simulation. Is this correct? How can we fix it?
BUILD file:
load("@bazelrio//:defs.bzl", "robot_cc_binary")

halsim_configs = {}

halsim_configs["gui"] = ["@bazelrio//libraries/cpp/wpilib/simulation/halsim_gui"]

halsim_configs["ds_socket"] = ["@bazelrio//libraries/cpp/wpilib/simulation/halsim_ds_socket"]

halsim_configs["ws_client"] = ["@bazelrio//libraries/cpp/wpilib/simulation/halsim_ws_client"]

halsim_configs["ws_server"] = ["@bazelrio//libraries/cpp/wpilib/simulation/halsim_ws_server"]

halsim_configs["combo"] = [
    "@bazelrio//libraries/cpp/wpilib/simulation/halsim_gui",
    "@bazelrio//libraries/cpp/wpilib/simulation/halsim_ws_server",
]

robot_cc_binary(
    name = "robot",
    srcs = [
        "src/robot.cpp",
        "src/robot.hpp",
    ],
    halsim_configs = halsim_configs,
    team_number = 6341,
    deps = [
        "@bazelrio//libraries/cpp/wpilib/cameraserver",
        "@bazelrio//libraries/cpp/wpilib/wpilibc",
        "@bazelrio//libraries/cpp/ctre/phoenix",
        "@bazelrio//libraries/cpp/rev/revlib",
        "@firelib",
        "//src/subsystems",
    ],
    copts = [
        "-ldl",
        "-lz"
    ]
)

WORKSPACE file:
local_repository(
    name = "bazelrio",
    path = "../../bazelRio/bazelrio",
)

local_repository(
    name="firelib",
    path="../fireLib"
)

load("@bazelrio//:deps.bzl", "setup_bazelrio_dependencies")

setup_bazelrio_dependencies()

load("@bazelrio//:defs.bzl", "setup_bazelrio")

setup_bazelrio()

Thanks in advance!

adding linkopts = ['-ldl'] to https://github.com/bazelRio/bazelRio/blob/main/bazelrio/libraries/cpp/rev/revlib/BUILD#L1 fixed the issue for us.

Please make a PR for the fix!

Done!

Closed by #111


Re-vendor oxy to include PassHostHeader changes

These changes are an outcome of this issue: https://github.com/mailgun/vulcand/issues/172

thanks!

Does that fix the forwarded headers for the hostname?


Make integration scan time selectable

Integration scan time to be configurable in device options.

This is not easily done and is not worth implementing. Will change the scan times to default values.


[SuggestionBox] Add reaction to see approval rate of suggestions

As title says, I'll probably PR it, it should be fairly easy since I don't want to keep track of the votes, should this be available as a guild owner setting?

Thinking more about it, if we have a setting for it, we may want 3 options, off, on-but-optional and forced.
Usecase for the three options :

You never want them
You want them for some but not others so you could tell it with an optional positional argument
You always want them (so people can't suggest by accident without reaction for example)

Your thoughts?

I made the PR, feel free to close it if you don't want the feature.


DROOLS-1311 Add Google analytics and prepare for AsciiDoc PDF generation

The AsciiDoc PDF generation would already work, if not for the images from the shared directory. With the new maven plugin coming soon, we 'll be able to fix that too.
This PR:

standarizes the use of attributes into the adoc file (so it shows up when opening those in an adoc editor)
simplyfies the build somewhat
throws away all the stale PDF uncommented code
introduces the recent best way of doing PDF images generation (but fails to active that because the shared images don't show up in the PDF, but we can fix that once the maven plugin releases, see comments)
adds Google analytics supports
fixes a number of issues in the adoc files caused by the migration, some of which result into warnings and one that craches during PDF generation.

Build successful! See generated HTML docs (may take a while till they are available):
http://ci.kiegroup.org/job/kie-docs-pullrequests/189/artifact/drools-docs/target/generated-docs/html_single/index.html
http://ci.kiegroup.org/job/kie-docs-pullrequests/189/artifact/jbpm-docs/target/generated-docs/html_single/index.html
http://ci.kiegroup.org/job/kie-docs-pullrequests/189/artifact/optaplanner-wb-es-docs//target/generated-docs/html_single/index.html

Looks good, just one minor comment.
Thanks a lot @ge0ffrey!

Fixed. Thanks @psiroky

Thanks, I'll wait the build to finish (just to be safe) and then merge.

Build successful! See generated HTML docs (may take a while till they are available):
http://ci.kiegroup.org/job/kie-docs-pullrequests/191/artifact/drools-docs/target/generated-docs/html_single/index.html
http://ci.kiegroup.org/job/kie-docs-pullrequests/191/artifact/jbpm-docs/target/generated-docs/html_single/index.html
http://ci.kiegroup.org/job/kie-docs-pullrequests/191/artifact/optaplanner-wb-es-docs//target/generated-docs/html_single/index.html


[3.10.3] Jetpack Thrusters displaying Jet Fuels info

Instead of saying "maximum speed", it says "acceleration"

Should be live in 3.10.4 release.


[BinPAC++] Change the type returned by iterator::deref for iter<bytes…

Simple hack to fix #16
In deref operator of iterators, the returned type is foced to int<8> for iter (because hilti code returns int8).

Looks like this was already merged, but not closed.


mDNS messages not redirected from antrea-gw0 to nodes transport interface

Describe the bug
mDNS messages (<IP_ADDRESS>:5353) are not redirected from antrea-gw0 to the nodes transport interface (in my case ens32).
To Reproduce
Antrea v1.8.0 deployed via helm with the following values:
multicast:
  multicastInterfaces: [ens32]
  igmpQueryInterval: "10s"
featureGates:
  Multicast: true
logVerbosity: 2

Deployed an application sending mDNS messages (<IP_ADDRESS>:5353) which are not detected when sniffing on ens32
Expected
Expected mDNS messages be forwarded to ens32
Actual behavior
mDNS messages are detected when sniffing antrea-gw0, but not when sniffing ens32. The expected multicast routing entry is never created. This can be checked by executing ip mroute show.
Versions:

Antrea version: v1.8.0
Kubernetes version: 1.24.3
Container runtime: cri-o
Kernel: Linux debian 5.10.0-18-amd64 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux

Additional context
As discussed with @wenyingd @antoninbas on slack: https://kubernetes.slack.com/archives/CR2J23M0X/p1665485647704739
Antrea agent log is here: https://gist.github.com/meibensteiner/4815734f1a2195e60921b4c3e6f28816#file-antrea-agent-662vn-log

Hi @meibensteiner , thanks for filing this issue. Could you provide more details about your use case and purpose why you want to forward the Pod mDNS traffic to external hosts?
According to IPv4 Multicast Address Space Registry proposed by IANA (https://www.iana.org/assignments/multicast-addresses/multicast-addresses.xhtml#multicast-addresses-1), this CIDR (<IP_ADDRESS>/24) is reserved for the use of routing protocols and other low-level topology discovery or maintenance protocols, and Multicast routers should not forward any multicast datagram with destination addresses in this range.
Antrea thinks the Pods and Node network are locating in different networks even though they are on the same host, and uses Linux multicast routing technology to forward the traffic between antrea-gw0 ( via the interface where the Pod multicast traffic is sent from/to ) and Node multicast interfaces ( including the Node transport interface used for Pod inter-Node traffic ). Since Linux kernel multicast driver does not support forwarding the multicast datagram with destination addresses in <IP_ADDRESS>/24, the issued traffic can not be forwarded as you want.
We have made some internal investigations on how to forward such mDNS traffic from antrea-gw0 to the external world, and we realize there exists another problem in this scenario ( using mDNS between Pods and external hosts ): The multicast responder may not responde the mDNS query if the source address is not locating in the same subnet according to the RFC6762 (https://www.rfc-editor.org/rfc/rfc6762#page-38),  this exists because Pod CIDR and the external receivers are not in the same CIDR. Even for the Pods in the same cluster but on different Node, the IP are not in the same CIDR. And it may introduce a conflict between the L3 src IP with the address in the mDNS query payload even if Antrea performs SNAT on the packet when forwarding it.
So we want more information about what kind of mDNS scenarios you expect to leverage Antrea.

A customer is using hardware that is controlled by software which was moved into a container for some reason.
There are essentially two special services: one uses mdns to announce an endpoint the hardware is supposed to connect to. Another service uses ssdp for that.
Since we are now pushing to migrate services into k8s, we are looking for a solution for that in the cloud native landscape.
Essentially we have these options:

Run the application with hostNetwork: true => not that desirable since I like having the application contained.
Find a CNI which supports our weird use case natively. => an option I would like to explore in the scope of this ticket.
Find a Layer 2 CNI plugin which would allow us to use multicast-relay. => A possible solution I am playing around with in the meantime.

About option number 2:
After a quick search, Antrea and WeaveNet look like the only two possible options supporting Multicast. Antrea being the standout since it looked like it was possible to forward to the Host Network, which is something we need for our use case.


BUG: Fixed Factor Analysis lecture; scaling was off

Fixes https://github.com/quantopian/research_public/issues/256

--> 'is analyzed in different ways' (though this makes the next phrase sound awkward). in general, it might be helpful to be more explicit here instead of using 'this information'. What about something like "Alphalens provides three categories of analysis on alpha factors:"

'!' --> '.'

What does 'these point estimates' refer to here? wondering if it's referring to something the got cut in the change.

answered my own question re 'these point estimates'. I see what it's referring to, but I think we should be explicit and call it 'the returns point estimates chart' or something equivalent, and I think we should do it for each plot.

"a breakdown returns" --> "a breakdown of returns"
"feed it a set of classifiers" --> "feed it a set of industry labels"?

Alphalens is more general than just industry labels. I'll change it to feed it a set of classifiers (such as industry labels).

I'd recommend against the use of the word 'classifiers', since that means something specific in Pipeline. Maybe 'feed it a set of labels'?.

maybe add 'relative to the total portfolio value' at the end of this sentence? or is it relative to the actual gross book value of the portfolio?

How about categorical values? Labels are a separate thing that you can include as a parameter.

The turnover has nothing to do with the value of the portfolio in Alphalens. It's just the percentage of names in the basket that have changed.

'categorical values' works for me!

I was definitely mixing up turnover in my head, oops! Other than being more explicit on the references to plots and tables, and the minor language tweaks above, looks good to me.


Prometheus remote-write URL is only getting pushed to the leader unit

Bug Description
While trying to configure remote-write url on grafana-agent units using the grafana-cloud-integrator charm, the prometheus-url is only getting pushed into the leader unit of the grafana-agent charm. The correct behavior should be that after adding the juju relation between grafana-agent and the cloud-integrator, the loki/prometheus URLs and other configs (credentials) should be pushed to all the grafana-agent units.
To Reproduce

juju deploy grafana-agent # and relate to the existing app with more than one unit.
juju deploy grafana-cloud-integrator --channel latest/edge # to jammy machine
juju config grafana-cloud-integrator prometheus-url=http://some.domain.name:9090/api/v1/write
juju relate grafana-agent:grafana-cloud-config   grafana-cloud-integrator:grafana-cloud-config
After a few seconds, observe that the grafana-agent/leader unit has the prometheus-url in /etc/grafana-agent.yaml

prometheus_remote_write:

tls_config:
insecure_skip_verify: true
url: http://<IP_ADDRESS>/cos-prometheus-0/api/v1/write
basic_auth:
password: ''
username: ''
tls_config::
insecure_skip_verify: true
url: http://some.domain.name:9090/api/v1/write

Note that on all the other (non-leader) units if grafana agent, this is not reflected:

prometheus_remote_write:

tls_config:
insecure_skip_verify: true
url: http://<IP_ADDRESS>/cos-prometheus-0/api/v1/write

Environment
juju controller version 3.4/stable in maas VMs (jammy), running on standard PCB setting.
charm channel = latest/edge
Relevant log output
~$ juju debug-log --replay --include grafana-cloud-integrator
unit-grafana-cloud-integrator-2: 14:39:37 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 14:44:25 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 14:49:20 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 14:53:34 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 14:58:07 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 15:02:37 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-grafana-cloud-integrator-2: 15:07:09 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)

Additional context
No response

I can confirm this using @ahmadfsbd's reproduction, doing:
juju add-model ga1
juju deploy ubuntu -n 2
juju deploy grafana-agent --channel=latest/edge
juju deploy grafana-cloud-integrator --channel latest/edge --config prometheus-url=http://some.domain.name:9090/api/v1/write
juju relate grafana-agent ubuntu
juju relate grafana-agent:grafana-cloud-config grafana-cloud-integrator:grafana-cloud-config

# Then compare the following:
juju ssh grafana-agent/0 -- cat /etc/grafana-agent.yaml | yq .integrations.prometheus_remote_write
juju ssh grafana-agent/1 -- cat /etc/grafana-agent.yaml | yq .integrations.prometheus_remote_write

where we see the leader has:
- basic_auth:
    password: ''
    username: ''
  tls_config:
    insecure_skip_verify: false
  url: http://some.domain.name:9090/api/v1/write

whereas the other unit has an empty list.
This appears to be due to the leader guards here, where the library does nothing on relation changed/broken if the unit is not a leader.
Non-leader units have somewhat restricted access to relation application_data, where they cannot read/write to their side of the data but they can read the remote's application_data.  Since the requirer class here only reads data from the remote application_data, the guard appears unnecessary so the fix should be to remove it.

fixed the root cause, but still need to implement the fix in grafana-agent charms

The grafana-agent machine charm now uses this lib in its amd releases in:

20.04: rev249
22.04: rev250

arm releases are blocked by an unrelated bug


nvidia nvenc/nvdec support added

A new dockerfile with nvidia hw acceleration (nvenc/nvdec/libnpp gpu scaling) support .
nvidia drivers and nvidia-docker should be installed on host machine.

that's pretty cool, can you made it a variant, instead of just a 4.1 image ? so we can build for older versions than 4.1 ?

see https://github.com/jrottenberg/ffmpeg#contribute for instructions, but I'll gladly accept that variant ;-)

Will probably  create it as a variant next week.

Seems like almost everything went fine, checks failure seems to be unrelated to the new nvidia variant.

Super nice ! Thank you very much.
Not too sure what's up with 4.0 variant but I agree it should not block that.
Give me few hours to enable nvidia variant on docker hub.

or more... https://success.docker.com/article/docker-hub-maintenance


Update time management UDP port details

Add a clarification to the time management documentation stating that UDP port 123 only needs to be open for outgoing connections from the device.
Change-type: patch
Signed-off-by: Mark Corbin<EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@balena-ci rebase


improve readability, remove legacy arguments

Hey,
not long ago I forked your updater.sh to create a version for a user.js of another website. That's why I had a thorough look on the whole script and found several ways to improve it. Now I want to give something back and implement my ideas which hopefully you'll find appealing. So brace yourselves, there's a lot more to come.
First one:

remove lots of unnecessary echo commands which don't help at all
replace \t-alignments with spaces so that it is agnostic of the user's settings and always looks the same. this also improves the readability of the code
replace some small if-statements (especially one-liners) by [ if ] && then || else
those legacy arguments where introduced two years ago. that's more than enough to safely remove them now

i might also suggest printing the current Firefox version in the into text and warning if the new user.js version doesn't match the major Firefox version the user is currently running

Thanks so far. Just brought another one on the way. #1000


Invalid Key Hash

I am integrating react-native-fbsdk-next and did all the setup required and it is giving me this issue.
Share if you have any experience to deal with this error (highly appreciated)

I have found solution to this probleme.
Run this command cd android && ./gradlew signingReport
In variant debugAndroidTest, copy the SHA1 key.
Go to this link https://tomeko.net/online_tools/hex_to_base64.php?lang=en
Enter SHA1 key and get it converted to base64.
Copy and paste it into your key hashes on meta.
Done you are good to go.


Enable datadog rum worker

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for JFrankfurt @ 2024-08-02 15:32:39 UTC
User failed mfa authentication, see go/mfa-help

Review Error for JFrankfurt @ 2024-08-02 15:51:17 UTC
User failed mfa authentication, see go/mfa-help


About page sample 07 ./src/index.tsx should be ./src/components/index.tsx

Hey I noticed that the index here is listed with the wrong folder structure.  It was pretty straight forward to just look at the repo attached and see which index you meant but it could be confusing for some people.  Really like going through these samples so far!

Thanks a lot for notifying this, going to create a branch and fix it

Fixed, please don't hesitate reporting more faults on the readme's it will help a lot other developers following the guides. Thanks


is there any library of calendar for compose desktop app

Feature
A clear and concise description of the feature.
Tech (if applicable)
Add any other information that could help the development of this feature.

is there any library of calendar for compose desktop app


Add invoice notifications to REST api

invoice notifications created by WebSocket and add useWebSocketAdapter to nest.js.
Receive paymenthsash in addfinal.sh and add it to lru-cache.
When htlcchanged.sh is called, the saved value is taken out and returned to the client.

ok

Thanks!


On &pep and &zen commands

Now that April Fool's is over, there was discussions on removing the &pep and &zen commands.  However, I, along with others, thought it would be a shame to completely get rid of them. It was suggested that PEP 9001 be immortalized somehow. Specifically by moving the link into the &blurplify command which is planned to move to sir-lancebot (see here). As for &zen, to avoid confusion, there should be some sort of indication within the embed saying this is not the actual zen.
Please leave any other concerns or suggestions here, and I will self-assign this and make a PR if nobody else does within a few days

What about putting all of these as subcommands on a aprilfools or some sort of parent command? That way they can't be run as easily by using the wrong prefix.

I am in favor of

removing &pep
keeping &zen (already some of us have gotten used to using &zen X to refer to a specific line in the modified Zen poem)
Change Sir Robin's version of the zen command to have a link to PEP 9001 somewhere
Add footer to Sir Robin's zen embed saying "From April Fools 2022" or similar


Add separate issue templates

Current issue template has checkboxes which overshadow github's checklist feature
Github now supports separate issue templates for various occasions. Split the current issue template into 3 parts - bug, feature, and chore
Add 3 corresponding buttons to README in create an issue section where a user can be redirected to new issue template respectively

I would like to work on this issue

Please go ahead


RFID Reader Working code

[x] Fill in the dummy functions with working code
[x] Edit demo file to test the working code
[ ] Verify that code works by running demo file

I was able to get test the two functions tested by using the following section of code in a test file "RFID-test.py":

The test was successful, although there were some issues with the print line spacing:

I then tried running demo.py, but got this error when trying to run. The error appears to be on line 5 of demo.py which is an import for the Touchscreen display:

@creechelseaa review

@wecodewithmichaelmccloskey please review

Please update the working code to use the I2C communication. See the comments in issue #34 for clarification on why.

See #34 for clarification


Enable observability tracing test cases

Purpose
Fix spi service loading issue and enable tracing tests.
Fixes #18348
Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18615 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #18615      +/-   ##
==========================================
- Coverage   15.15%    15.1%   -0.05%
==========================================
  Files          48       48
  Lines        1254     1258       +4
  Branches      197      198       +1
==========================================
  Hits          190      190
- Misses       1050     1054       +4
  Partials       14       14

Impacted Files
Coverage Δ

tool-plugins/vscode/src/overview/activator.ts
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0e7c043...19d1fe3. Read the comment docs.


consider introducing different scope for  variable mapping

motivation
To  compatibility with other BPMN runtimes, we need introducing different scopre for variable mapping which means input mapping should be defined in local scope, while the output mapping maybe merged into parent scope.
Doc: https://docs.camunda.io/docs/components/concepts/variables/#inputoutput-variable-mappings
business background

Considering sending msg in differnet situationes,  the send_notice servicer task will face varaible conflict or overwrite if input mapping  does not defined in local scope.
If we change introduce a lcoal scope for input mapping, it will helps a lot.

@nitram509  I'm not quit understand how to deal with the output mapping. What do you think?


Restarted container, now it wont boot

Describe the problem
Just restarted the container and now it wont boot, was working fine until 1.20.4
Container definition
version: "3.9"
# make sure you edit the server-name with your server name
services:
  voxel:
    image: itzg/minecraft-server
    container_name: minecraft-kaizoku
    user: "1001:1001"
    # restart: unless-stopped
    environment:
      - EULA=TRUE
      - MEMORY=6G
      - TYPE=PAPER
    # This is most important - make sure your volume path is unique and exists - this is where your config will exist
    volumes:
      - /home/ubuntu/containers/minecraft-servers/kaizoku:/data
    networks:
      - minecraft-kaizoku
    # Make sure you use a unique port, check with Sawada for existing dns records if you are using this on a server with multiple minecrafts
    ports:
      - "25565:25565"
    stdin_open: true
    tty: true

networks:
  minecraft-kaizoku:
    name: minecraft-kaizoku
    driver: bridge```

### Container logs

[init] Downloading PaperMC 1.20.5 (build 22) ...
[init] Setting initial memory to 6G and max to 6G
[init] Starting the Minecraft server...
Applying patches
Starting org.bukkit.craftbukkit.Main
Exception in thread "ServerMain" java.lang.UnsupportedClassVersionError: org/bukkit/craftbukkit/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0

Please re-pull the image or add java21 image tag. Minecraft 1.20.5 now requires Java 21
https://docker-minecraft-server.readthedocs.io/en/latest/versions/java/

Stable tag worked for me
Get Outlook for iOShttps://aka.ms/o0ukef

From: Geoff Bourne @.>
Sent: Monday, April 29, 2024 6:03:54 PM
To: itzg/docker-minecraft-server @.>
Cc: Danny Gershman @.>; Manual @.>
Subject: Re: [itzg/docker-minecraft-server] Restarted container, now it wont boot (Issue #2808)
Please re-pull the image or add java21 image tag. Minecraft 1.20.5 now requires Java 21
https://docker-minecraft-server.readthedocs.io/en/latest/versions/java/
—
Reply to this email directly, view it on GitHubhttps://github.com/itzg/docker-minecraft-server/issues/2808#issuecomment-2083761267, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAOD3O5FXOZMHP7ZKBNAMVTY727UVAVCNFSM6AAAAABG6ZKXBCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTG43DCMRWG4.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


LoadGen: Big changes to TestSettings

Adds CreateSettings to mlperf_spec_constants.h/cc.

Provides an easy way to set up a spec-compliant test.
These are the only files that are model and
specification aware.
Final settings for submission still TBD.

Decouples TestSettings from the MLPerf constants.

Removes TestSettings::enable_spec_overrides.
Removes override prfix from TestSettings member names.
Makes non-spec defaults in TestSettings more conservative.
Splits target_latency into server and multi-stream variants.

Fixes tests, python demos, and the reference code.

@guschmue @itayhubara @christ1ne can one of you please review and merge or give feedback to Brian? There are several changes in this PR so didn't wanna assume it was a small delta to merge in.

Seems enable_spec_overrides is removed, and many other override parameters are renamed, does it mean we can use different settings than the spec default in final submission?

For submission, folks will still need to select settings that are spec compliant.
The mlperf::spec::v0_5::CreateSingleStreamSettings function (and similar functions for other scenarios) have been added in this patch to help people start with settings that are spec compliant (once the spec has been finalized).
In this way, the mlperf::spec namespace can be model-aware and spec-aware, while the loadgen itself does not need to be aware of either.

@guschmue  any commets?

In general I do not think model specifics should be in loadgen, that belongs passed in or in a config file.
I do not think we agreed on latency targets ... not sure about the values burned into code here. I also think there should to be multiple latency targets per model.
Not sure if this was tested.

Part of the goal of this patch was to remove mlperf specifics from the loadgen and make target_latency not an override setting.
If I remove mlperf_spec_constants.h/.cc from this patch, would that be good? Those are the only files that are aware of model, spec min durations, etc. Nothing else in the loadgen depends on them.

Ok, I've removed mlperf_spec_constants.h/.cc from this patch and from HEAD. The main thing this patch does now is remove the concept of "override" from TestSettings, leaving it completely up to the client to meet the spec requirements.

ok, I'll give it a test run and merge it today.


Change type of toFloat to number -> Float

I'm wondering whether it might be useful to change the type of toFloat from
toFloat : Int -> Float

to
toFloat : number -> Float

so that one could write functions like
module Number.Format where

prettyPrint : number -> String
prettyPrint n =
  let print = {- ... -}
  in print (toFloat n)

This might also be a more generic proposal to discuss than issues like https://github.com/elm-lang/core/issues/4 which might be repeated for various functions.

Having said that, it's not a big deal to just implement prettyPrint as
prettyPrint : Float -> String

for now...

Consolidated all the math related stuff into the #721 meta issue. Follow along there!


fix: add missing skeleton in component view

:tada: This PR is included in version 0.55.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


CoveragePublisher common library and PublishCodeCoverageV2

Change 1
PR introduces a library coveragepublisher in Tasks/Common, this library will henceforth be used for all coverage publishing needs for existing/new tasks. The library is packed with a dotnet library from azure blob, which performs parsing and the report generation. The task side coveragepublisher library simply acts as a wrapper to this.
Change 2
Bump publish code coverage to V2.

Use the common coverage publisher library

Task can now support taking in multiple inputs mixed with multiple formats
Will now support local merging
Will support future coverage improvements

Remove the redundant tool input and report directory input.

Any idea when this new version will be published?  Will simplify and speed up some builds I have.  Thanks!

Any idea when this new version will be published? Will simplify and speed up some builds I have. Thanks!
@PBoraMSFT on the ETA

@bkaid, btw you can try out the task on your account using https://github.com/microsoft/tfs-cli/blob/master/docs/buildtasks.md

@bkaid - we are looking at end of the quarter to ship these changes. Some of associated code coverage reporting experiences are changing as well and they need to go in tandem.

How can we monitor when this task is made public? Since the task has already been merged on master I assume it's already there but "public": true is not present in your manifest? Since your manifests are not in the repository, it's hard to know why a certain task is not available. I had to dig deep just to find this issue mentioning PublishCodeCoverageV2
Is there a release note somewhere for improvements to all your tasks? Mostly what changed from V1 to V2.. or V2 to V3 etc.

@eric-labelle - we publish release notes every sprint for Azure DevOps here. When the task becomes publicly available, information about changes will appear there.
To provide context, we are working on native code coverage reporting experiences in Azure Pipelines. This task revision is a part of that. We expect it to become available early next quarter.

Allright, thanks!
One more thing though, I was curious and uploaded the V2 to see if speed was improved. I modified the id and name in V2/task.json before uploading V2 but it still was uploaded with original id. I now cannot remove this V2 from my azure organization without completely deleting the V1 also.
Before I uploaded V2 (2.159.0 is latest on master) it was 1.160.1. I tried to reupload V1 with --overwrite (even if it's 1.159.0 on master) without success. If I want to restore the original 1.160.1, how can I achieve this?

@karanjitsingh @PBoraMSFT Is there any update on this? It would be great to remove some extra report generator merging steps from my pipelines

Hi folks, how is the plan on publishing new update for task? Will it be available soon at least for preview mode?

@PBoraMSFT Any update? It's getting close to 2 years since this PR was merged.

@PBoraMSFT ping


make manual no longer makes cmdstan-guide.pdf

Summary:
Or at least it doesn't copy it to the correct location...
Additional Information:
Provide any additional information here.
Current Version:
v2.18.0

Where should it go?  And should there be a version number?  I think the new stan targets may be fouling things up here.

It used to go in doc/. Maybe we should leave this unassigned in case
someone wants an easy way to contribute
On Fri, Jul 13, 2018 at 14:23 Bob Carpenter<EMAIL_ADDRESS>wrote:

Assigned #631 https://github.com/stan-dev/cmdstan/issues/631 to
@seantalts https://github.com/seantalts.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/cmdstan/issues/631#event-1733180176, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAxJ7FITQHtbmE3sFrTTKBxBoeY2xgYNks5uGOWHgaJpZM4VPLY4
.

--
Laboriously extracted via diminutive keyboard

fixed by https://github.com/stan-dev/cmdstan/pull/652


Icarasia's Detection Range

Define how an Icarasia will act based on Hestmor's distance. No need to set any actual numbers for now, just an overview of what will happen when Hestmor is:

Out of Range
Far
Close

@vitormaduro sorry for seeing this late, probably this is clear by now, from the mechanical workings you saw in https://github.com/Team-Awkward-Smile/Epilogue/wiki/Mechanical-Workings-Of-Individual-Enemies#icarsia.
But still summarizing it here:

Out of Range: Icarasia moves left and right at its place, and/or searching for a Terra Bischem. If a Terra Bischem is there, they can be seen floating near it.
Far: If Icarasia notices Hestmor from Far, then its height dependent. If Icarasia is higher or lower than Hestmor, then it will attempt a projectile attack. If its on the same plane or ground as Hestmor, it will attempt to get closer to her. If they are hit by Hestmor once, then they will approach her.
Close: Engage melee combat, aka, sting.

Honestly I don't remember why I opened this issue, but the entry on the wiki already answers this question, so I'm closing this issue hehehe


Add option for loading the editor in an iframe

Loading the editor in an iframe would encapsulate the editor better, allowing for completely separate editors with their own configuration etc. on the same page.

Implemented with 0.19.0


Allow scaling down even when dynamic replicas have -all

In a dynamic replica setting, such as 1-all, the lower bound counts for CrateDB to stay green. In this case, a cluster is considered healthy if there are still two nodes: 1 as the primary node and 1 with the one minimum required replica. The scaling operation should account for that.

Hi, im  new in python, I don't really know a lot but I wana to learn, do you think this is easy? I will be able to complete? 😞 O don't really get what I have to do😅

Hi @ikerdna, thank you for your interest in contributing :slightly_smiling_face:
This ticket is about the function parse_replicas. The task is to change the function in a way, such that any input (variable name r), if it contains a -, uses the lower limit, instead of the upper limit.
Here are some examples:

Input
Current return value
Expected return value

'1'
1
1

'all'
9223372036854775807
9223372036854775807

'1-4'
4
1

'3-all'
9223372036854775807
3

9223372036854775807 is identical to sys.maxsize.


son-gtkfnct is not pointing to new catalogues url

We have this configuration:
CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues

We need to change it for this:
CATALOGUES_URL: http://{{ public_ip }}:4002/catalogues/api/v2

grep -rl '4002/catalogues' | xargs sed -i 's/4002/catalogues/4002/catalogues/api/v2/g'
Affected 'docker_container': FNCT + SRV + PKG


Customizable gauge pointer path

Version: 3.3.2
It would be nice if the PointerPath can be provided as a symbol, or if it has a property that would allow to set radius of the bottom part similar to this one:

I also have a strong demand for this, in addition to the dashboard can be vertical or horizontal display.


Fix CAN error handling

I've stumbled across an issue with the bxCAN async implementation, whereby if in a loop you are polling read() for events, and an error exists on the bus (any error), you end up with a situation where the processor will never sleep and is instead caught in an infinite loop of returning the same CAN peripheral error(s).
The issue is the current_error function returns a value if there is any errors set in the ESR register. However, that register is read only, and those errors persist until either the peripheral is reset, or the condition causing the error on the bus has been resolved and the TEC/REC counters are decremented via the successful reception/transmission of messages.
Ideally, I believe the curr_error fn should only return an error if the ERRI flag is set in the MSR, at which point it should be cleared and the error value returned. If the same error condition exists on the bus during the next transmit/receive, the ERRI flag would be set again and the consumer would be notified again of the error condition.
To put this in some context, here is a generic scenario based on an actual production use case (of the original draft implementation I provided) today:

A task is setup to poll the bus for messages, deserializing messages received and placing them on a channel, as well as serializing messages from the application channel and transmitting them on the bus.
When the CAN task identifies one of a set of error conditions (bus off, bus passive, bus warning, no ack) the CAN task puts the bus to sleep and returns a bus unavailable error to the application. This is because there are nodes (CANOpen NMT) on the bus that may be the only  node powered up at specific times. If the node ignores these errors it will end up with the CAN peripheral in bus off, which requires a significant number of messages received to clear, or would require a full peripheral reset. Sleeping the bus also has the side benefit of a small amount of power savings.
It is impractical to stop polling the peripheral for new messages as once another node has appeared on the bus and has transmitted a message, the peripheral will wakeup, triggering the SCE interrupt, and the device can resume communications, as required. In the current implementation of the CAN peripheral, the only way to receive that notification is via polling the read() fn.

I've done some looking into what I believe is the best way to solve the issue, and I've noticed a few things;

The ERRI is acknowledged in the ISR itself. I understand this is so once the context of the handler is yielded, we don't end up with another interrupt triggered before the poll_fn body within the read fn is executed.
The next most obvious solution would be to disable the error interrupt within the SCE ISR, and NOT acknowledge the interrupt (clearing ERRI in MSR). This would allow the curr_error function to check the ERRI bit, and if set clear ERRI, re-enable the interrupt and return the appropriate error, and in all other cases return None. This is the implementation included with this PR.
The Error Warning/Passive/BusOff/LEC error interrupts were not enabled by default. This sets up a race condition where sometimes an error message would be delivered to the caller of the read() fn and other times not, depending on if the error condition was identified on the bus before the ESR register was read in the read()->try_read()->curr_error() call chain or not. If it wasn't the only waker that would be triggered is the frame RX waker, which, depending on the bus state, may never be fired.

can you rustfmt to fix ci?


Response to user requests for data from Facebook messenger

When a user asks for specific Earth data, respond with text, link to data, or image representation of data

Generate image plots assets and store at URL on Amazon S3


[Feature Request]:  adding logo to the google drive

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
In the google drive there is no logo in the navbar and the main page
Use Case
I want to add the logo in the google drive
Benefits
No response
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I have starred the repository

@jayanththalla I have recently seen that u are contributing really consistently in this repo & all of the changes u have made are really great also .But just want to remind you that one contributor can only get 150 points max from a particular repo under GSSOC , so keep this rule in mind please , otherwise really want to see more of your amazing contributions.

can you assign this issue to me?

can you assign this issue to me?

i have already assigned u some issue previously , Please try to complete the previously assigned issue, Then ping me here , i will assign u then

Sir i would like to take up this issue

@ayesha-firdaus u are assigned


Cleaning up some TODOs.

This removes several outstanding TODO entries and includes mostly comment deletion + minor cleanup.

This is no longer WIP.


Support for underscores in Python numbers #3038

Modified the regex for number in prism-python.js from:
https://github.com/PrismJS/prism/blob/59f449d33dc9fd19302f21aad95fc0b5028ac830/components/prism-python.js#L57
to:
/(?:\b(?=\d)|\B(?=\.))(?:0[bo](_)?)?(?:(?:\d|0x(_)?[\da-f])([\da-f]|[\da-f]_)*(?:\.\d*)?|\.\d+|((\d+_)*(\.)?(\d+)?)*)(?:e[+-]?\d+)?([^_]j)?\b/i

I have highlighted the rationale at #3038. Additional test cases were also added.

Test results:
><EMAIL_ADDRESS>test:languages (...)\prism
> mocha tests/run.js "--language=python"

  Testing language 'python'
    √ – should pass test case 'boolean_feature'
    √ – should pass test case 'builtin_feature'
    √ – should pass test case 'class-name_feature'
    √ – should pass test case 'comment_feature'
    √ – should pass test case 'decorator_feature'
    √ – should pass test case 'function_feature'
    √ – should pass test case 'issue1355'
    √ – should pass test case 'keyword_feature'
    √ – should pass test case 'number_feature'
    √ – should pass test case 'operator_feature'
    √ – should pass test case 'string-interpolation_feature'
    √ – should pass test case 'string_feature'
    √ – should pass test case 'triple-quoted-string_feature'

  13 passing (101ms)

Thank you for contributing @marvintensuan!


Is this package only for MusicXml? (Unable to emitSchema for QuickBooks XSD)

I'm trying to use this package to auto-generate the Haskell bindings for a QuickBooks' REST API (they publish an XSD for their API and supporting data-structures).
I followed your code at https://github.com/slpopejoy/fadno-xml/blob/e16b79de5c3273141b676f84f5e971658fa94cdf/src/Fadno/Gen/GenMusicXml.hs and came up with https://github.com/saurabhnanda/quickbooks2/blob/57f59bd314a9c8ef34c1d657b6db4a3ab2554139/src/Lib.hs However, it results in a stack-overflow error, as demonstrated below:
[LOCALHOST:~/projects/haskell-quickbooks (master) saurabhnanda] $ stack ghci
haskell-quickbooks-<IP_ADDRESS>: initial-build-steps (lib)
Configuring GHCi with the following packages: haskell-quickbooks
GHCi, version 8.4.3: http://www.haskell.org/ghc/  :? for help
[1 of 1] Compiling Lib              ( /Users/saurabhnanda/projects/haskell-quickbooks/src/Lib.hs, interpreted )
Ok, one module loaded.
Loaded GHCi configuration from /private/var/folders/j7/fgt692sj0wzg0lvrk86ctnxc0000gn/T/ghci78292/ghci-script
*Lib Lib> parseXsd
*** Exception: stack overflow
*Lib Lib>

How can I debug this further? One difference in the two code snippets is that my code snippet is not using namespaceSchema to adjust namespaces? Would that cause an infinite loop somewhere, or would that cause a dangling reference (and thus, a different error)?

Sorry for not responding. Is this still occurring?


update ip blacklist in waf-owasp-top-10 to all local ip addresses

Issue #, if available: none
Description of changes: when testing on local network, ip blacklist have to be valid with ip local addresses
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice: YES !

badly, it isn't working evenif the fix can be usefull => I forward to aws team


MB-10883 enable services counselors to edit destination type for shipments

Jira ticket for this change
Summary
It adds the destination address type field to the add and edit forms for MTOShipments. Also adds in e2e test coverage for both actions.
Setup to Run Your Code

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

Terminal 2
Start the UI locally.
make client_run

Terminal 3
Start the Go server locally.
make server_run

Additional steps

Login as a services counselor
Edit or add a shipment
Select 'yes' for knowing the destination address
Select a type and fill out the address
Save the thing -- you won't yet see it on the ShipmentDisplay component, that's being done in another task/PR.

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

[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

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

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Backend

[ ] Code follows the guidelines for Logging
[ ] The requirements listed in Querying the Database Safely have been satisfied.

Database
Any new migrations/schema changes:

[ ] Follows our guidelines for Zero-Downtime Deploys
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

Screenshots

Fails

:no_entry_sign:
Yarn Audit Issues Found:
high - node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Package node-fetch
Patched in >=2.6.7
Dependency of swagger-client
Path swagger-client > cross-fetch > node-fetch
More info https://github.com/advisories/GHSA-r683-j2x4-v87g
1 high vulnerabilities and 0 critical vulnerabilities found

Messages

:book:
:link: MB-10883

  Generated by :no_entry_sign: dangerJS against<PHONE_NUMBER>d787c37fac67fad39d8bc64742e502

Can we add the acronym at the end of each of the first three type options? So it would read Home of record (HOR) Home of selection (HOS) Place entered active duty (PLEAD) Other than authorized

Just pushed a change for the acronyms you mentioned.


address different hash result for non ascii characters in old node

I believe related to:
https://stackoverflow.com/questions/37213211/why-crypto-createhash-returns-different-output-in-new-version
I have tested this one dev and it appears to work nicely there for the currently open/error tasks.
@ramramps lets talk tomorrow about deploying the same thing to flood?

Few things, then LGTM


(PUP-1295) Fix always purging package resources that are not installed.

For package providers, the base package provider was defaulting to a
property hash with a status of :absent when the package was missing.
When the resource is ensure => purged, an :absent status causes it to
be purged.  This is because an absent package could represent a
"partially installed" package that is not truly installed and can
therefore be purged (see the dpkg provider).  If the base provider
always returns a status of :absent for missing packages then purgeable
providers will always attempt to purge a missing resource.
The fix is to have the base provider default to a :purged status when
the resource is missing and the provider supports purging.  Otherwise,
it defaults to :absent like before.

Review note: CI failure is from spurious rdoc failure on Windows and can be ignored.

CLA signed by all contributors.

The notices are a little funny now.
When installing: Notice: /Stage[main]/Main/Package[sudo]/ensure: ensure changed 'purged' to 'present'
When purging: Notice: /Stage[main]/Main/Package[sudo]/ensure: ensure changed '1.8.6p7-13.el7' to 'purged'
When absenting: Notice: /Stage[main]/Main/Package[sudo]/ensure: removed

This seems like it's worth running through some acceptance tests; have you done so? I'll kick off running  all the acceptance tests that manage packages.

To fix:

First notice: transitioning from purged to present should be treated the same as absent (i.e. created), so will fix that to say created.

Second notice: transitioning from present to purged should be treated as present to absent, but used purged instead of removed.

Does that make sense to do?

Yeah, those make sense.

The acceptance coverage is pretty sparse.

It looks like this may impact the acceptance test: tests/resource/package/common_package_name_in_different_providers.rb

Nice catch, I'll look through the acceptance tests and make sure there aren't any others.

I've tried out scenarios with gem, dpkg, apt, yum, and apple providers. No more observations, so just the previously mentioned cleanup should be sufficient.

:+1:

Can you add integration tests for the reports produced?

Will do.

@MikaelSmith Test added.

@MikaelSmith Looks like the new test failed travis (runs locally :-1: ).  Looking into the failure.

Appears to still fail.

@MikaelSmith Stubbed the instance instances instead of the class method.  Should work now.


External-GitHub

Parceiros/Links-patrocinados

I'm not sure I understand the issue.  Can you explain?

Can help! I want to create a custom space here in GitHub somehow to interact and call the Attention content creators to Register! from another platform! that pays $ by software creation apps, ads etc ...

I'm not sure I understand what you're talking about or how this is related to this project.  Thus I'll close it unless there is a legitimate issue.

ok no problem


You need to set the output format to "esm" for "import.meta" to work correctly.

Describe the bug
package.json
"dev:dev": "VITE_APP_ENV=dev vite --mode dev",
.env.dev
VITE_APP_ENV = dev
"import.meta" is not available with the "cjs" output format and will be empty [empty-import-meta]
config/sysConfig.ts:31:53:
  31 │ const { VITE_APP_ENV } = process.env ? process.env : import.meta.env;
     ╵                                                      ~~~~~~~~~~~

You need to set the output format to "esm" for "import.meta" to work correctly.
When I run vscode reports an error, I want to get the environment variable, "import.   meta" is not available with the "cjs" output format and will be empty [empty-import-meta]
Import.meta.env is available in the browser
An error was reported while running
Reproduction
https://stackblitz.com/edit/vitejs-vite-6wy8fp?file=package.json,.env.dev,vite.config.js,config.js&terminal=dev
Steps to reproduce
npm run dev
System Info
"import.meta" is not available with the "cjs" output format and will be empty [empty-import-meta]

    config/sysConfig.ts:31:53:
      31 │ const { VITE_APP_ENV } = process.env ? process.env : import.meta.env;
         ╵                                                      ~~~~~~~~~~~

  You need to set the output format to "esm" for "import.meta" to work correctly.

Used Package Manager
pnpm
Logs
"import.meta" is not available with the "cjs" output format and will be empty [empty-import-meta]
config/sysConfig.ts:31:53:
  31 │ const { VITE_APP_ENV } = process.env ? process.env : import.meta.env;
     ╵                                                      ~~~~~~~~~~~

You need to set the output format to "esm" for "import.meta" to work correctly.
Validations

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

import.meta.env is a feature that you can use inside the source processed by Vite. Config files are not the part of it.
If you want to use env vars from .env, check out this documentation.
https://vitejs.dev/config/#using-environment-variables-in-config


add transfer filed to blacklist

This change is

Coverage increased (+0.04%) to 71.529% when pulling 4e2952ed0e74b2863b0e64b530b645550c915c59 on vmotso:transferring into ed24ed2f9f67d8e46dc6495b50e505d6a8216374 on openprocurement:ea_core_master.

Coverage increased (+0.04%) to 71.529% when pulling 4e2952ed0e74b2863b0e64b530b645550c915c59 on vmotso:transferring into ed24ed2f9f67d8e46dc6495b50e505d6a8216374 on openprocurement:ea_core_master.


arch-vega,arch-gcn3: Bugfix V_PERM_B32 and V_OR3_B32

The V_PERM_B32 instruction is selecting the correct byte, but is shifting into place moving by bits instead of bytes. The V_OR3_B32 instruction is calling the wrong instruction implementation in the decoder.
This patch fixes both issues plus a bonus fix for GCN3's V_PERM_B32. (GCN3 does not have V_OR3_B32).
Change-Id: Ied66c43981bc4236f680db42a9868f760becc284

no gpu expertise required for this review...


remove findsubdomains.com

To follow the terms in https://findsubdomains.com/terms, we need to remove this source.

fixed with https://github.com/subfinder/research/commit/ab772de094675c74e002f2551fa99c87e7ede482


Add list of specs working on win32 in std_spec

This collects all specs currently working on win32 (working does not neccesarily they're passing) in a single spec, so they can be easily compiled using the crystal-windows helper from the Porting to Windows guide.
The current spec stats:
Finished in 2.81 seconds
3908 examples, 13 failures, 191 errors, 8 pending

The stdlib spec suite on linux64 currently runs 9110 examples, so we're currently at about half.
Most of the currently disabled specs are probably working as well. I've simply disabled entire files or even directories, but often there are just a few specs that don't work on win32 but exclude the entire file. This can be improved obviously by more fine-grained control.
The 5% failing specs are all in path and dir spec.
This list gives an overview over which specs are currently working on win32 and what not.
There are different levels of not-working:

Specs that error at compile time are completely commented out. This is mostly caused by some API not being ported to win32 (either the spec target or the spec uses non-ported features).
Specs that compile but don't link (at least not on basis of the Porting to Windows guide) are guarded by the require_nolink macro. When passing -Dwin32_nolink they can be enabled for testing codegen. Most of are just caused by missing libraries (libxml2, libyaml, libgmp, libllvm, libz, libssl), but there also seem to be some incompatibilities with the existing libraries.
Some of the require_nolink specs are annotated as # execution breaks, which means linking is fine but they break the entire spec suite at runtime. I assume it's related to the very basic exception handling on win32.

/cc @oprypin

See also https://github.com/RX14/crystal/commit/990f8bf19ff3c06bc1730c939e923aa87d2161bd for an alternative way of doing this.
Your method is neater, but can it be automated to update the list of what works? At this stage of development, there's a lot of work in the corelib which ends up making a lot of specs work at the same time.

Oh, nice. I didn't think about automating this.

Your method is neater, but can it be automated to update the list of what works?

This could probably work in a similar way as your script. The main difference is that my variant combines directory contents in a wildcard if all files run. That makes it neater. We could probably implement this in the script, but it's probably not really worth it. I don't mind having a long list of all  files.
So I'd prefer your solution since it's easier to maintain. We should better invest our efforts in making things work on windows.

@straight-shoota will you update this PR with something similar to my method then or?

Sure, can do that.
You should definitely share more of your goodies that have been laying around for 2 years!! 😆

@straight-shoota just check my windows branch!
All it has is the Process refactor which is very similar to #8518, this specs commit, and "shitty WIP stubbing" in the compiler (which gets the crystal compiler to build and work on windows, this is doable right after #8518 is merged)

I've improved the generator to use multiple stages in order to avoid compiling the same spec file twice and to distinguish codegen and linking failures.
New stats:
Finished in 6.13 seconds
4917 examples, 14 failures, 192 errors, 8 pending

P.S. We should consider printing the spec results at the very end when the listing of failed examples already fills 8 pages...

With a single character fix (#8667), we're down to 6 errors 🎉
Finished in 6.21 seconds
4917 examples, 14 failures, 6 errors, 8 pending

So I guess, never mind the suggestion for improving spec results 😄

So I guess, never mind the suggestion for improving spec results smile

You know, I've actually wanted to have the stats line last a bunch of times when working with rspec too. It doesn't matter when there is few issues, but with many (think rails version upgrades), things get problematic fast.

feel free to merge @straight-shoota


Migrating from travis-ci.org due to shutdown

The project currently has a build status badge from travis-ci.org, which is shutting down. Any opinions about moving to a different platform for CI?
Migrating to a free plan at travis-ci.com is probably the easiest method, and would presumably work with the existing config file.
I’m late to the party but have been playing around with using Github Actions for build tests, and have a good first impression. The main advantage of that would be tighter integration with github and one less account to manage.

Closing this since you just moved it all over to GitHub actions!
https://github.com/microformats/php-mf2/actions/workflows/main.yml
Thanks!


⚠ ETF has degraded performance

In 65a98fe, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 6112 ms

Resolved: 신규상장 performance has improved in 9596f8c.


2021/05/11 architecture review

Architecture review by r-sylph

The usecase needs not to know infrastructure's context.
Expectations should be insert into infrastructure layer.

Fixed in https://github.com/umatare5/telee/releases/tag/v1.3.7


radiance installation instructions step 0 contradiction

Installation Step 0 says:

This software requires the previous installation of RADIANCE from https://github.com/NREL/Radiance/releases.

but then step 0 item 2 says:

get the official Radiance 5.2 source tarball with auxiliary libraries rad5R2all.tar.gz from either RADIANCE online or LBL - do _not_clone the GitHub repo as it doesn’t have the auxiliary libraries which you may also need. Finally extract the tarball.

It's confusing to link to the RADIANCE github repo's release page and then say not to use it.
There's also a typo: _not_clone should be _not_ clone

Fixed in PR #235


ros os upgrade fails to keep the existing --append settings

RancherOS Version: (ros os version) 0.8.0
I store it in /boot/global.cfg, but seem to overwrite it from the defaults in the code on upgrade. its hard to be perfect - there might be new settings in later releases, but just losing the existing ones breaks lots os stuff.

it seems to work when upgrading from v0.8 but i feel its failing to do so from v0.7 and before.

dropping


The name of the function does not match the input

OS: Mac
Build Version: 20200708.13
Repro steps:

Right click a PostgreSQL account.
Create a new database.
Right click  "Functions" node --> Click "Create Function Query…".
Provide function name and select return type.
Execute the query.
Check the result.

Expect:
The name of the function is the same as the input.
Actual:
The name of the function does not match the input.
Input:

Created:

Verify we aren't messing with casing before running the create function query


Tree drops logs but doesn't disappear

I am having trouble explaining this, because I have nothing to do with coding/modding so please bare with me :)
I made a modpack. And got a dedicated server from Kinetic.
It includes (among other mods) Immersive Weathering, Panda's Falling Trees and Treechop.
Here's a screenshot of what happens and I'll detail the steps below.
https://i.postimg.cc/j2fpTsJH/2024-12-18-16-30-41.png

I chop the tree. Using Jade, I see it reaching the 5/5 logs breaking, dropping 7 logs.
Tree "fells". Sometimes, the chopped log retains a slim state. Sometimes (eg. screenshot) disappears. Sometimes (if tree is very tall) a good portion of trunk disappears. But always the tree top (logs + leaves) remain like in the screenshot.
Log items drop as intended.
Saplings drop.
Immersive Withering does its thing, leaving leaf piles on the ground, that break when hit, dropping more sticks/saplings.
The "remaining" logs/leaves remain solid, respawn instantly if you try to break and disappear after relog. If I cut the tree and create this "encounter", all online players see it the same. And each player must relog in order to "remove" it. As in if I relog, I remove it only on my screen.
The "remaining" logs/leaves can be deleted with right-click, but again, only on your screen.

None of this happen on singleplayer. Same mods, same config since the modpack is made by me, uploaded by me.
Kinetic support said "A mod working on singleplayer, doesn't always mean it will work on the server".
I don't know what to do. I want to keep the mod because we love the visuals of it and the fact that it works with all trees.

Update.
We added ESSENTIAL and I hosted a world.
Me, as the host, saw the tree falling as intended. Same thing as in singleplayer. Even if was cut by me OR by my friends.
Them on the other hand, saw the tree as described in the original post. Even if it was cut by themselves or by other player.
So what I understand is that server/host isn't sending the block state(?) to client...?

https://github.com/hammertater/treechop/issues/185 seem to solve my issue.
But maybe this post would help other noobs like me find the solution, since this one has more words than issue185 :D


clusterdeployment: include InstallImagesNotResolved condition when job fails

The cluster deployment controller creates a job that resolves the installer and cli
images for installing the cluster. this job uses the release image to extract these details.
When the release image being used can't be pulled due to some failure like authentication
the controller provides no update / condition that would provide use details on this failure and
the user sees no update on the clusterdeployment object.
With this change we add InstallImagesNotResolved condition to the clusterdeployment when the job fails.
Previously the job had activeDeadline set to 24 hrs, therefore the job controller would wait for that interval
before marking it complete+failed. To make sure the controller can actually give users report of job failure
the deadline is reduces to 2 minutes. This now matches the deadline used by CVO that uses a very similar job to
interact with the release-image contents 1.
NOTE: currently this depends on job controller's status reporting to provide user the reason for failure, but
we could later extend it to summarize the pods's failure reason as the pods from job stay until the job is deleted.
xref: https://issues.redhat.com/browse/CO-1306

/assign @dgoodwin
/cc @akhil-rane

/lgtm

/lgtm


The Things Network code update + Send to database

req.body = {
    device: {
        deviceId: req.body.hardware_serial
    },
    measurements: req.body.payload_fields
};

Should be replaced with:
req.body = {
    device: {
        deviceId: req.body.hardware_serial.toLowerCase()
    },
    measurements: req.body.payload_fields
};

How can I send the data with this i/o bridge also to an azure database?
IoT Central has this easy export option but it averages my data points to new 1 min average data points.
I want to log my original IoT data not the averaged data!

Thanks for the feedback on the first issue. I've sent a change to update the docs.
For the second one, the Continuous Data Export feature in IoT Central creates export files with a minute timestamp in the name, but the file will contain all measurements for the period, i.e., the points are not averaged.

For the second one, the Continuous Data Export feature in IoT Central creates export files with a minute timestamp in the name, but the file will contain all measurements for the period, i.e., the points are not

You are right, I did some more testing and also removed the simulated device from IoT central an it looks to be correct, would be better if the IoTCentral UI graph shows like up to 500 point (Excel doesn't have a hard time with 500 points)
Screenshot with the different data points (based on IoT central table view and added extra rows in excel), the empty column is strange, why is it there? Why not have headers with a timestamp instead of a time period (I didn't choose the period).

Is there an easy way to query/see blob data in table format?

@KenSense Do you want to see this data in table format for user consumption or do you have a downstream service that consumes tabular data?
Do you only want to view/query a minute's worth of data in table format?
Right now the only supported type of export is in Avro format and there isn't an easy way to change that to display or be queried in table format.

It's not for user consumption I would just like to make a graph of all the data that was logged.
(a real graph not like IoT Central)
or just query at which times certain conditions were true.
Seems like a lot of overhead to get the logged data.


Index out of range on os.StartProcess call

I'm running go 1.4.2 windows/amd64
I made a SO post here describing it: http://stackoverflow.com/questions/31072865/runtime-error-index-out-of-range-when-attempting-to-os-startprocess
Basically I'm attempting to start a process with os.StartProcess and a slice of arguments, but I keep getting an index out of range runtime error.
For simplicity, I also made this simplified go code to reproduce it for me:
http://play.golang.org/p/S6kRLMyd2I
which returns:
panic: runtime error: index out of range

goroutine 1 [running]:
syscall.StartProcess(0x4fa1f0, 0xe, 0xc082023f30, 0x1, 0x1, 0xc082023e20, 0x0, 0x0, 0x0, 0x0)
        c:/go/src/syscall/exec_windows.go:322 +0x94c
os.startProcess(0x4fa1f0, 0xe, 0xc082023f30, 0x1, 0x1, 0xc08200a280, 0x4db5e0, 0x0, 0x0)
        c:/go/src/os/exec_posix.go:45 +0x482
os.StartProcess(0x4fa1f0, 0xe, 0xc082023f30, 0x1, 0x1, 0xc08200a280, 0x4b5920, 0x0, 0x0)
        c:/go/src/os/doc.go:24 +0x79
main.main()
        C:/projects/go/gobug/gobug.go:11 +0xca

goroutine 2 [runnable]:
runtime.forcegchelper()
        c:/go/src/runtime/proc.go:90
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:2232 +0x1

goroutine 3 [runnable]:
runtime.bgsweep()
        c:/go/src/runtime/mgc0.go:82
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:2232 +0x1

goroutine 4 [runnable]:
runtime.runfinq()
        c:/go/src/runtime/malloc.go:712
runtime.goexit()
        c:/go/src/runtime/asm_amd64.s:2232 +0x1
exit status 2

Literally right as I hit post, a friend messaged me and said he fixed this lol. He's answering the SO post.

There might actually be a bug. Looking at the code in syscall.StartProcess (src/syscall/exec_windows.go) it even handles the attr == nil case, but never verifies len(attr.Fd) > 2 before accessing fd[2] in line 322. cc @alexbrainman.

I agree, we should not panic. https://go-review.googlesource.com/11604
Alex


Add cuda fixes

Codecov Report
Patch coverage has no change and project coverage change: -12.34 :warning:

Comparison is base (293378a) 78.10% compared to head (c7e16de) 65.76%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #873       +/-   ##
===========================================
- Coverage   78.10%   65.76%   -12.35%
===========================================
  Files          18       18
  Lines        8413     7951      -462
===========================================
- Hits         6571     5229     -1342
- Misses       1842     2722      +880

Impacted Files
Coverage Δ

src/compiler.jl
66.48% <0.00%> (-13.01%)
:arrow_down:

... and 14 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Tesseract 4, how to set only one lanugage ?

hello guys
i am using Tesseract 4 with java.
i get traineed data from https://github.com/tesseract-ocr/tessdata.
below my code.
	ITesseract instance = new Tesseract();
	instance.setLanguage('kor');
	instance.setDatapath(TESSDATA_PATH);

loading trained data from local is good work. and, i set language as 'kor'.
but as result, there are some korean, some chineses..
how to set only one language for ocr?
thanks

i get traineed data from https://github.com/tesseract-ocr/tessdata.

Please use tessdata_fast or tessdata_best instead.
The traineddata file in tessdata maybe having Chinese as a sub language in
the config file (I am guessing).
On Thu, Sep 6, 2018 at 9:51 AM, SEUNGGWAN<EMAIL_ADDRESS>wrote:

hello guys
i am using Tesseract 4 with java.
i get traineed data from https://github.com/tesseract-ocr/tessdata.
below my code.
ITesseract instance = new Tesseract();
instance.setLanguage('kor');
instance.setDatapath(TESSDATA_PATH);
loading trained data from local is good work. and, i set language as 'kor'.
but as result, there are some korean, some chineses..
how to set only one language for ocr?
thanks
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1898, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AE2_o4rYqgg2uIggafX_jLpqjb4ZwpnVks5uYKK1gaJpZM4WcM-w
.

--

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

@Shreeshrii
Thanks 👍  after i try it right now, i will reply a result of that

Please respect guidelines for posting issues! Use tesseract user forum for asking support.

@zdenop where tesseract user forum?

https://github.com/tesseract-ocr/tesseract/blob/master/CONTRIBUTING.md

@zdenop thanks ~ :)


[ci] Add missing transient per sonarqube

Caused by: java.lang.NullPointerException: null
        at org.apache.ibatis.cache.CacheKey.equals(CacheKey.java:99)
        at net.sf.ehcache.store.chm.SelectableConcurrentHashMap$Segment.get(SelectableConcurrentHashMap.java:876)
        at net.sf.ehcache.store.chm.SelectableConcurrentHashMap.get(SelectableConcurrentHashMap.java:360)
        at net.sf.ehcache.store.MemoryStore.get(MemoryStore.java:300)
        at net.sf.ehcache.store.MemoryOnlyStore.get(MemoryOnlyStore.java:107)
        at net.sf.ehcache.Cache.searchInStoreWithoutStats(Cache.java:2070)
        at net.sf.ehcache.Cache.get(Cache.java:1590)
        at cz.sa.ares.database.mybatis.cache.EhcacheCache.getObject(EhcacheCache.java:57)
        at org.apache.ibatis.cache.decorators.LoggingCache.getObject(LoggingCache.java:57)
        at org.apache.ibatis.cache.decorators.TransactionalCache.getObject(TransactionalCache.java:68)
        at org.apache.ibatis.cache.TransactionalCacheManager.getObject(TransactionalCacheManager.java:35)
        at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:101)
        at org.apache.ibatis.executor.CachingExecutor.query(CachingExecutor.java:83)
        at org.apache.ibatis.session.defaults.DefaultSqlSession.selectList(DefaultSqlSession.java:148)
        ... 61 common frames omitted

Note that only making the field transient is just plain wrong. You lose the updateList on serialization (replication, disk store) and make the cache effectively memory-only.

@FrantaM
Transient is simply a marker to java.  It is required when an object is NOT serializable. The object would fail either way if that data element is not managed properly.  It would get a serialization error without transient if it was attempted to be serialized because it does not implement serialization (unless that changed since April 23rd).  With it, it doesn't try to serialize thus the null pointer that you see upon object being restored for use.  Can you please open up a new issue if you haven't already that points back to this change and/or take your stack trace and place on the new issue.  We will look into it.
Thanks,
Jeremy

It is required when an object is NOT serializable.

So why did you add it? The object in that field is ArrayList and ArrayList is serializable just fine.

Hi @FrantaM ,
When you open a new issue, could you attach a test case or example project, please?
We should add a test case to avoid regression.
Thank you,
Iwao

@FrantaM
That is true if it were using ArrayList but it's using the interface which itself is not serializable.  Neither is Object.
Why I would have added it? because one of the various checkers (findbugs, checkstyles, or pmd and/or sonar stated to do so and there was a presumption this was being handled without errors thus no need to add in the serialization logic necessary to handle the transient).
I feel I should now test this to confirm our scanners are correct and any assumptions are as well.
Serializable by definition of a class requires that each element of the class is also serializable otherwise it's not actually serializable.
For reference, what version are you using of mybatis?  I belive this was introduced in 3.4.5 which just released.  I'm assuming you are then using 3.4.5 but wanted to be sure.  In that case, could you try dropping back to 3.4.4 and see if you can confirm if it is still an issue there?
Now looking closer at your stack trace, it's not failing on the class itself but rather the object passed in for comparison.
So I'm wondering if this is really just exposing another issue.
for (int i = 0; i < updateList.size(); i++) {
  Object thisObject = updateList.get(i);
  Object thatObject = cacheKey.updateList.get(i);  --> This line.  Nothing was done to ensure it even had 'i' at this point.  What if it doesn't.  Is updateList really null or the I its attempting to pull not present?
  if (!ArrayUtil.equals(thisObject, thatObject)) {
    return false;
  }
}

Is it possible the equals is implemented incorrectly and we have now exposed it?  A good test case can serialize and confirm the issue but would need to know a bit more on how your use case is using that.  I can look into building a serialization of this class to see if I can flush this out.

I happened to have a project that tests for serialization that I thought would help here.  However, it only goes as far as to write the object and that isn't enough ot prove serialization if some or anything is serializable.  Obvious outcome there is that this helped me see my testing project 'javabean-tester' isn't solid enough to ensure serialization is perfect.  Since its just a marker to java, it simply ignores what isn't serializable anyways.  Anyway in my test, I addeda  truely non serializable object I made up.  Running java bean tester using serialization write, it succeeds.  If I run my dummy class by itself it fails.  Contents of the dummy class themselves are serializable.  Thus this is going to take me a bit longer to write something up that is more solid.  I'm going to have to perform both the write then read to see what the data contains.  I suspect null in both cases but will take me a few to confirm.

confirmed.  Scanners are wrong.  This was a bug.  I'll review all my other work.  the 'transient' needs removed.

Of course it all matters on what is inside the list.
If string, the transient of causes it to be not saved and ends up null.
If object, it won't serialize at all.
So scanners are half right.  Sonarlint is the problem in this case.
@harawata
This appears to be a breaking change that needs pretty immediate attention.  Should we do a 3.4.6 release?

@FrantaM @harawata
I have raised PR #1084 to fix this issue with enough testing around it that it never occurs again.

That is true if it were using ArrayList but it's using the interface which itself is not serializable. Neither is Object.

Regarding serialization, the type of the field does not matter at all. You don't really need to tell me how serialization works.

For reference, what version are you using of mybatis?

3.4.5 and I cannot really go back because 3.4.4 contains another serious issue (#988).

Is it possible the equals is implemented incorrectly and we have now exposed it?

No. Marking updateList as transient made it nullable - cacheKey.updateList can by null and you can't call get() on null.

Of course it all matters on what is inside the list.

Note that the only non-serializable thing that may end up in updateList are mapper parameters. But this can by easily avoided by the users or they can just use memory-only cache or not use cache at all.

@FrantaM Thanks for feedback.  I think we are all good now.  Thanks for catching this so quickly as well.  Sonarlint is pretty strict on stating it is an issue and after all the work I did to test it, it's not so clear.  The use-case in which it is based on real usage as you point out is pretty weak at best.  This is the second or third issue I've seen with the new sonarlint that ultimately is flat out wrong.  Again thanks and thanks for letting me know going back is not an option.  I'm waiting on feadback from @harawata and expect this needs emergency release tonight.  I've got a head out for a bit but will check back in a few hours.

Thank you @FrantaM and @hazendaz !
So, to describe the issue from the user's perspective, is the following accurate?

Caches that perform serialization didn't function correctly.

Any correction or rewrite would be appreciated.

Code is on master now.  I merged the initial fix back to how it was with thorough tests and @FrantaM helped me cleanup from actually writing out a file in the process.  I think generally speaking serialization is up to the jvm needs and not usually controlled on our parts.  So this is probably a horrible regression as any to have leaked onto the code base.  However, I don't know the full ramifications of doing nothing at the moment.  I am surprised this didn't pop up sooner during various testing.  I sort of think it would be good to release 3.4.6 but not sure if we want to wait a few days to see if any other regressions exist after this overall release.  The release feels big to me anyways that maybe a few days is worth the wait.
@FrantaM @harawata Thoughts on waiting?
@harawata That basically sums it up.  The issue here is that serialization still occurred but the 'updateList' is simply ignored due to the transient I had added per sonarlint insistence resulting in it being null.  While the insistence is mostly true, it's really only true if the actual objects being written are not themselves serializable.  So string for example would serialize with no problems.  A non serializable object or Object as defined would fail to serialize.  In this case, good user usage would not have resulted in a serialization problem to start with.  However, since I added transient, it causes the object to become null as it is never written and not there to retrieve.  A better fix would be to know something better than object to store in the first place which I think would avoid ever having this situation.  However, not sure if anything being mapper is what is stored here.  I'm mostly speaking for me here as I don't know all use-cases of a lot of the overall code.

Caches that perform serialization didn't function correctly.

Not really. More like: If you define cache in your mapper, the cache can be serialized only when mapped statements parameters can be serialized.

Thoughts on waiting?

Well this thing rules out cache replication and loading serialized cache (e.g. from disk) without resorting to some dark voodoo reflection as I did. But I know mybatis internals so I can afford it. I would definitely not wait too much before releasing this.

Not really. More like: If you define cache in your mapper, the cache can be serialized only when mapped statements parameters can be serialized.

Thank you for the explanation.
I thought that caches could not be serialized at all if transient was specified.
(I was thinking about what to write in 3.4.6 release note, by the way)

Thoughts on waiting?

As @FrantaM can afford it, I think it's OK.

I thought that caches could not be serialized at all if transient was specified.

Caches can be serialized, but the serialized form is useless. And when you try to deserialize & use it you'll end up with NPE.

Ah, yes. That was what I thought. Thank you for the clarification!


[Bug]: Steering will sometimes make a sharp input

Tweaks version
outrun2006tweaks-9e79594a9fda217c32b1eb22023bd9ac3f66d61d
Describe your issue here (please attach the OutRun2006Tweaks.log file with your report, you can drag+drop it into the text area)
Utilizing the game's default 0.2% steering deadzone, I have found that occasionally, the car will steer too sharply instead of reading the input correctly, sending me into a wall if I do not catch it in time. This has not happened in older versions (even in older official releases). This is not a controller issue and I know this because I have changed from a PowerA Xbox One Controller (PowerA is notorious for having bad 3rd party controllers and I had one with horrible stick drift leading to having my inputs not being read AT ALL for a few seconds) to a GameSir Xbox Series Controller (Which has no stick drift issues right out of the box).
This is ruining my OutRun 2SP mode time attack runs and this needs to be looked into and addressed before another official release comes out.

UPDATE: Upon adjusting the deadzone to 0.1% in this specific version of Tweaks, the sudden sharp turns have stopped. something is wrong with the 0.2% percent deadzone. hopefully, this bug will be squashed before the next official release.

So this is something that only started in recent tweaks releases?
Not really sure why 0.2 deadzone would affect it, if it's set to 0.2 it should deactivate the deadzone patches since vanilla game uses 0.2 by default.

So this is something that only started in recent tweaks releases?
Not really sure why 0.2 deadzone would affect it, if it's set to 0.2 it should deactivate the deadzone patches since vanilla game uses 0.2 by default:
https://github.com/emoose/OutRun2006Tweaks/blob/df7fac4f10d51b18854f8da4db1f6f6e08faaac3/src/hooks_input.cpp#L333-L336
Could you check if https://github.com/emoose/OutRun2006Tweaks/releases/tag/v0.5.1 has the issue?

yes, apparently so. I'll get 5.1 in my game rn and see if it has the same issue

Just tested version 0.5.1. Fortunately, this patch does not have the issue I have mentioned in this post. This is just a guess but it could be any version of Tweaks where the ability to change the steering deadzone is where the issue came from.

This is just a guess but it could be any version of Tweaks where the ability to change the steering deadzone is where the issue came from.

Seems likely, but not really sure why since it should be getting deactivated at 0.2 like mentioned :/
Could you try with these 3 builds and see if there's any difference?
https://github.com/emoose/OutRun2006Tweaks/actions/runs/10511134416
https://github.com/emoose/OutRun2006Tweaks/actions/runs/10543165711
https://github.com/emoose/OutRun2006Tweaks/actions/runs/10551379579
The first one there is just prior to deadzone being added, middle one includes the deadzone stuff, and last one is just after deadzone was added.
May want to backup your INI files and use the INI included with them, since there were some INI changes in those.

This may be the case of the bad controller since I just recently tried the 0.2 deadzone and it looks like it is a me issue lol
but I'll try the tweaks you just linked when I can

Would be interested in what happens here.
I have also experienced it, but put it down to CPU load affecting things (n100/win11).
Will try some longer tests in batocera/wine when I have time as the game runs better/looks better under wine for some reason.

Would be interested in what happens here.
I have also experienced it, but put it down to CPU load affecting things (n100/win11).
Will try some longer tests in batocera/wine when I have time as the game runs better/looks better under wine for some reason.

What other issues have you encountered? I sometimes encounter the occasional stutter but it's not the kind of stutter that will cause the game to hitch for a bit too long. I put that issue down as I probably need to expand my ram for my desktop so the game can run as smooth as it can

Would be interested in what happens here.
I have also experienced it, but put it down to CPU load affecting things (n100/win11).
Will try some longer tests in batocera/wine when I have time as the game runs better/looks better under wine for some reason.

also please keep us posted in case you find something that is the cause of our issue. I just want to know before I start trying the tweaks files Emoose posted in this thread

To give an update, even with the 0.1% deadzone setting, I ran into the same issue in this thread. This is probably being caused by the CPU load that k0pp0 had mentioned earlier. The CPU load might be the culprit but who knows

Could try disabling SingleCoreAffinity, having that enabled does increase CPU load quite a bit afaik, might help remove the stutters but if you have a very modern CPU (I think ones with e-cores) it could cause freezes.

To be honest CPU load is so low on mine, even on a n100. GPU isn't stressed either

Could try disabling SingleCoreAffinity, having that enabled does increase CPU load quite a bit afaik, might help remove the stutters but if you have a very modern CPU (I think ones with e-cores) disabling it might cause freezes.

Will do


Key sanitization

I'd like use statsd to check the performance of a nginx server (through LUA).
As a key, I'm using [uri].[method].[http status code]
During my tests, I notice the key stored in the daemon isn't correct because the key is sanitized replacing some character at https://github.com/etsy/statsd/blob/master/stats.js#L189
I'd like to know if this behavior is requested or the graphite backend requires this sanitization.
My backend will not be graphite but ElasticSeach (http://www.elasticsearch.org/).

@allevo, we just merged #451 which optionally moves the sanitization to the specific backend. You can disable sanitization by setting keyNameSanitize to false in the config


Truncation

I implemented a truncation component that can contain one or more "truncatable" parts.
The truncation component itself can have one of the following 2 state: collapsed or expanded.
When the component is expanded, all its child "truncatable" parts are either totally expanded or capped at a specified amount of lines (@Input() max-lines).
When the component is collapsed, all its child "truncatable' parts are capped at a specified amount of lines  (@Input() min-lines).
I tried a lot of different approaches to implement the multiline clamping, including libraries like shave, ellipsis, clamp...
The issue with all these libraries is that heights can only be calculated when the content is already displayed. At the moment, there's no way of knowing when a component is totally loaded, the default Angular Lifecycle Hooks can't provide us with a solution.
This is why @artlowel and I chose to implement this with CSS instead. We took some inspiration for this from popular websites with a comparable layout. The text is now fading out at the end of a clamped line.
You might expect an ellipsis at the end of a clamped line instead, but with CSS this is only possible outside of a text block. This did not give us the expected results, especially in list views.
For now, the truncation has been applied to the search result items (both list and grid view). Clicking a truncated component, will expand it, clicking it again will collapse it again.

Works visually very well on Fedora 27 in Firefox 58.0.1.
I noticed that in Chrome (64.0.3282.140), when trying to select the truncated text, the behaviour of the selection differs from what a user normally expects. After you start to select the text, when you reach the point of truncation, your selection jumps back and starts over at the beginning.

Works visually very well on Fedora 27 in Firefox 58.0.1.
I noticed that in Chrome (64.0.3282.140), when trying to select the truncated text, the behaviour of the selection differs from what a user normally expects. After you start to select the text, when you reach the point of truncation, your selection jumps back and starts over at the beginning.

It looks good to me too

I've retested this today, and I do see the same behavior as @PTrottier around selecting text in Chrome.  However, I noticed this only occurs if the text is faded/truncated. If you click on the text, it appears fully and you can easily select it.  But, if the fade is in place, selecting the faded text is harder to achieve.
That said, I think this is a relatively minor UX issue (and, as I said, if you click to expand the text first, it can be easily selected).  So, I think this PR should still be merged as-is, and we can always open up a new ticket to describe this minor UX issue, as necessary.

Agreed, this behaviour also does not occur in Firefox.

Merged, and logged the minor UX bug here: #234