Question: How to add crash info upon crash?

Since I don't see any example, tutorial or guides, about how to show Activity stack for each crash, I've decided to gather this information myself, by using this callback:
http://developer.android.com/reference/android/app/Application.html#registerActivityLifecycleCallbacks(android.app.Application.ActivityLifecycleCallbacks)
Thing is, I can't find where exactly can I send the entire stack of the activities upon app-crash.
There is no such listener.
Is it possible that what I just need to use is "Custom Keys" :
https://docs.fabric.io/android/crashlytics/enhanced-reports.html#custom-keys
?
So that upon each event of activity, I set it to something different?
Or maybe use "Custom Logging" :
https://docs.fabric.io/android/crashlytics/enhanced-reports.html#custom-logging
so that for each event, i just log it ?

You're probably best asking this question on the developer forums instead of on this repo.

@andypiper The link you provided is of Twitter. I wanted to ask about the SDK of Crashlytics (AKA Fabric), which is supposed to be used in this sample.
As the sample is supposed to cover all of the features of the SDK, I wanted to ask how can I achieve the above.
Another scenario is that I'd like to report the used heap-memory when the crash occurred.

Yes, I understand. Fabric is provided by Twitter, and the forums are where we are able to answer some of these questions.

I don't understand. Twitter is the owner of Crashlytics?
In any case, I've written this question on StackOverflow:
http://stackoverflow.com/q/37256595/878126
This is much more global and easy to find.

As you wish - but yes, Crashlytics is part of Fabric which is part of Twitter, and twittercommunity.com is our developer community for the products. Thanks.


Dissalow running Scheduler with ephemeral storage when in HA mode

Issue reference
https://github.com/dapr/dapr/issues/8305
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] Code compiles correctly
[ ] Created/updated tests
[ ] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Changes lgtm, but do we need to update docs to mention this?

Does this look ok? I think that's the right place. Is there anywhere else we should mention it?


! add isLinkedToDateRange to children props

Codecov Report

Merging #307 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #307   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files         137    137
  Lines        3281   3281
  Branches      732    732
=====================================
  Hits         3281   3281

Impacted Files
Coverage Δ

src/components/datePicker/DatePickerDropdown.tsx
100% <ø> (ø)
: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 c815d07...955728f. Read the comment docs.


Ethereum smart contract should allow dumping of all anchors in a simple script

Task added to avoid other updates of the smart contract. In future we should be able to migrate to different blockchain technologies.


pull request for e2e test at 02/06/2017 19:26:07

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


Update sponsor banner

Our Sponsor banner https://github.com/qgis/QGIS-Website/blob/master/themes/qgis-theme/static/images/sponsors.png needs an update.  QGIS Usergroup Switzerland is our new GOLD sponsor and AGH isn't sponsor anymore.

@anitagraser @andreasneumann is this true? Should we update the image?

Well, I already did https://github.com/qgis/QGIS-Website/blob/master/themes/qgis-theme/static/images/sponsors.png

Mmm, I see it here on my local build indeed. Thanks!
WIll have a look into the builds...

The images is updated and the good one is in the output directory.
It is in the rsync step that it was not synced, because it has the same name.
AND we do cloudflare caching which also caches.
So I removed the old (non rsynced) images so it was synced, and then if you use: http://foo.qgis.org, you see it, but http://qgis.org still does, though I disabled Cloudflare just now. Not what ttl=automatic time is now...
Easiest solution (I think) is to (instead of my plan to just name it 'sponsors'.png' to add a time to it.. sponsors201606.png or so?
@timlinux  maybe other ideas?

Hi Richard,
On Tue, 28. Jun 2016 at 00:27:55 -0700, Richard Duivenvoorde wrote:

@anitagraser @andreasneumann is this true? Should we update the image?

See http://qgis.org/en/site/about/sponsorship.html
Jürgen
--
Jürgen E. Fischer           norBIT GmbH             Tel. +49-4931-918175-31
Dipl.-Inf. (FH)             Rheinstraße 13          Fax. +49-4931-918175-50
Software Engineer           D-26506 Norden             http://www.norbit.de
QGIS release manager (PSC)  Germany                    IRC: jef on FreeNode

@jef-n yes, don't worry, not questioning your issue ;-) Just wanted to ping the people who normally fix those (and actually did...)
Thanks all!

@rduivenvoorde Any naming approach is fine for me. Just let me know what works.

@anitagraser the naming approach will work, it is just that without it, it would be easier to update... /me hoping somebody comes up with a better solution....

ok, rsync step is doing fine, the new image is already on the server for all languages... Sorry for the noise. It is apparently purely the Cloudflare cache...

The banner has changed for english language but is still the same for other languages

fixed


*: fix some minor typos

This PR fixes some minor typos.

branch name is not right, please use docs/typo, thank you very much.

you can rebase develop then push again, the check for branch has been removed.


Micro_ros udp transport build issue on esp32

Issue template

Hardware description: esp-wroom-32
RTOS: freertos
Installation type: micro_ros_setup
Version or commit hash: humble

Steps to reproduce the issue
ros2 run micro_ros_setup configure_firmware.sh motor_subscriber -t udp -i [YOUR IP] -p 8888
ros2 run micro_ros_setup build_firmware.sh
Expected behavior
100% build
Actual behavior

Additional information
When I try to build it with serial Transport the build is successful with some stderr outputs but when I try udp it does not seem to build

Hello @Apurva2510 the recommended approach for using micro-ROS in ESP32 is using the component for ESP-IDF. Could you give a try using this repo: https://github.com/micro-ROS/micro_ros_espidf_component

Hello @Apurva2510 the recommended approach for using micro-ROS in ESP32 is using the component for ESP-IDF.  I will try that approach.

Update: @pablogs9 The repo that you mentioned worked for the udp transport. Thanks a lot for that advise!

Closing as its solved


feat(script): add repeat interval for script failure and exec-if

What type of PR is this? (check all applicable)

[ ] Refactor
[x] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Other: Replace this with a description of the type of this PR

Description
Added repeat interval for script failure (interval-fail) and exec-if (interval-if), both falling back to interval if not specified. The implementation is straightforward, current configurations retain their behaviour.
Related Issues & Documents
Closes #943, #2606
Documentation (check all applicable)

[x] This PR requires changes to the Wiki documentation (describe the changes)
[ ] This PR requires changes to the documentation inside the git repo (please add them to the PR).
[ ] Does not require documentation changes

The following should be added to Modules/script/Basic Settings:
; Interval used when the `exec` command returns with a non-zero exit code
; If not defined, interval is used instead
interval-fail = 300

; Seconds to sleep between `exec-if` invocations
; If not defined, interval is used instead
interval-if = 180

Additional notes
One thing I've discovered is that the whole exit-code mechanism is not very reliable due to the fact that script invocations and output updates are not synchronized in any way. Here's a sample config to describe the problem:
[bar/bar]
modules-right = test

[module/test]
type=custom/script

format = <label>
format-background = #090
format-foreground = #fff
format-padding = 4

format-fail = <label-fail>
format-fail-background = #900
format-fail-foreground = #fff
format-fail-padding = 4

label = %output%
label-fail = %output%

exec=echo %counter% $(date +%S) ; ((%counter% % 2))

interval=3
interval-fail=5

The script prints it's %counter% with date in seconds and fails every other time. Expected output is green-red-green-red....
Here's an example of the output I've got:
1 00 (green)
2 03 (green)
3 08 (red)
4 11 (green)
5 16 (green)
6 19 (red)
7 24 (red)

As you can see 2 was considered "successful" by formatting, but applied the correct inteval, because it's actually controlled by script_runner. What actually happened is this:
set exit_status: 0 // exec at ~00
// 1
get_output
  get exit_status: 0
// 2
get_output
  get exit_status: 0
set exit_status: 1  // exec at ~03
// 3
get_output
  get exit_status: 1
set exit_status: 0 // exec at ~08

The same is for 4-5 and 6-7.
My point is, it may be confusing for users if their scripts go for (probably longer) interval-fail while being displayed as successful. It's also not an expected behavior really and performs poorly with "flickering" scripts like the one in the example. At the same time I'm not sure If we could do something about it.
Sorry for not noticing this before #2596.

What do you think about this? Do you want to tackle this?

I think I should, yeah. I'll make a separate PR for these changes.

@indev29 If you work on it, use the hotifx/3.6.2 branch as the starting point so that we can more easily get it into the next hotfix release.
There has already been a potential report of this issue (even without the intervals): #2650


Toggle switch button?

I’m sorry if this has been addressed before.
Just got some Aqara wireless switches and while they’re not visible in Phoscon, they were easily added there, and showed up in HomeKit via Homebridge-Hue.
Is it possible to somehow program (in Homebridge, Home.app, Eve, or Deconz) them to toggle the same light on and off on the same button (without having to E.g. short press for on and long press for off)? This is a very common behaviour on similar switches in general, and also long press dimming which remembers the last direction of dimming and toggles this too.

Afaik, this can only be done through rules on deCONZ, not through HomeKit automations.  See
https://developers.meethue.com/develop/application-design-guidance/create-a-hue-tap-toggle-button/.  They still use a CLIPGenericFlag, but you can also use the light state.on or group state.all_on as the condition.

Ok. So I dabbled a bit with the REST API and see that there's actually a "toggle" action which works fine. But it would be even better to BIND by the Deconz rules as you say (BINDing would make it quicker, no?). I tried this because it says in the docs that you should use the "ep" value of the Switch as the value of the condition, but this does nothing:
{     "actions": [         {             "address": "/groups/5/action",             "body": {                 "on": true             },             "method": "BIND"         }     ],     "conditions": [         {             "address": "/sensors/11/state/buttonevent",             "operator": "eq",             "value": "1"         }     ],     "name": "Kjøkken grp 5 bryter 11 ep 1 all lights On/Off" }

there's actually a "toggle" action which works fine.

The toggle action only works for groups, and uses state.all_on to determine whether to send On or Off., see https://github.com/dresden-elektronik/deconz-rest-plugin/pull/396.

BINDing would make it quicker, no?

In theory yes, although I doubt you notice much difference in practice.  With bindings (from the switch to (a group of) lights), the switch sends a message to the (group of) light(s), controlling them directly (even when the gateway is down).  Without, the switch sends a message to the gateway, causing a rule to be fired, which causes another message to the (group of) lights.

BIND by the Deconz rules

I never got BIND rules to work.  I setup my bindings manually in the deCONZ GUI.
Note that a binding only specifies to which device/endpoint or group the switch sends its commands.  The switch needs to send the appropriate Zigbee command to control (a group of) lights directly.  Typically the command is hard-coded in the switch firmware, but some professional-grade switches (like ubisys) allow the command to be configured.  Not all switches support sending commands though; some (notably Xiaomi) only send notifications to the coordinator, requiring rules to control (groups of) lights.

Ok, currently doing toggle logic in Node-Red against the Deconz REST API. Just doesn’t feel as instant, but I don’t know.
Regarding dimming logic; it’s a shame the websocket notifications from Deconz doesn’t actually notify all button events, especially the hold (push) and hold (release) (two distinct for holding events).

I'm unfamiliar with Node-Red, but I image it introduces some overhead.  Gateway rules would be more responsive.
The buttonevent values that deCONZ reports depend on what the switch supports.  Different (versions of) different Xiaomi switches send notifications for different events.  See https://github.com/dresden-elektronik/deconz-rest-plugin/wiki/Supported-Devices#wireless-switches.

I have the "Aqara smart wireless switch" WXKG11LM 2018 and I'm pretty sure the Deconz websocket only reports the first of the "hold" events.
But anyway, since it's not visible in Phoscon, and setting up binding rules through the REST API doesn't seem to work, i will have to get into the GUI again to set up binding/rules. It's been a long time, and I have since an early install of Deconz upgraded many times without changing my deconz.service file. It's now says amongst other things "-platform minimal" and "user 1000".
When I stop it and start Deconz GUI from /lib/bin (with X11 forwarding via SSH) it doesnt seem like the same Deconz used in my ordinary Phoscon. Only a limited devices are visible. And when I exit and return to deconz.service and Phoscon it seems messed up for a while before returning to normal.
I know you have an issue with Deconz-REST-API concerning a similar problem with the GUI and the .service file, but is it generally possible to enter the GUI while Deconz is running its usual business ? And is that an easy fix to my .service file ?

I'm pretty sure the Deconz websocket only reports the first of the "hold" events.

What do you mean "only the first of the hold events"?  The Hue dimmer switch is the only device that continues to issue events, while a button is held; all other switches only issue a single notification while holding.

is it generally possible to enter the GUI while Deconz is running its usual business

deCONZ installs two services, deconz.service and deconz-gui.service.  If you disable and stop the first and enable and start the second, the GUI is enabled.  I run this on a headless Raspberry Pi and connect to the GUI over VNC when needed.

The wiki says my switch supports:

1 | x001 | Hold
3 | x003 | Release (after hold)

But I only get a one message when holding, and not on final release. Will investigate buttonevents more closely, but this would imply 2 events for hlding a button.
Regarding the GUI service, it seems the deconz-gui.service depends on VNC and another graphical(?) system which I don't have installed or use (?). I think I got an error the last time I tried to enable this service. Will have to try and delete the dependants and just try again then.

You should get an x003 after an x001.  Next step would be to enable deCONZ logging and check whether the gateway receives notifications for both.
The deCONZ GUI doesn’t depend on VNC, but it needs the graphical X11 environment.  There’s still some issues that the service is started too early in the boot process and crashes a couple of times, before the graphical environment has initialised, see
https://github.com/dresden-elektronik/deconz-rest-plugin/issues/797.

Actually it only supports button events 1,2,4 (I corrected the Wiki which only said 2,4) which means "hold", "Release (after press)" and "Double press", so advanced logic for hold events then:-/
Anyway, I tried the remote Phoscon (at http://www.dresden-elektronik.de/pwa/) and the Aqara switches were suddenly showing (even though my own Phoscon with no visible switches came with Deconz 2.05.60 which should be the latest), and to my surprise I was able to link simple button toggles to light groups in the GUI (which created a barrage of resource links and rules but that's ok).

Actually it only supports button events 1,2,4 (I corrected the Wiki which only said 2,4) which means "hold", "Release (after press)" and "Double press", so no logic for hold events then:-/

It's one of the lumi.remote.b...acn01 wireless wall switches, then?  Does homebridge-hue expose it correctly, with support for Single Press, Double Press, and Long Press (on hold)?

I tried the remote Phoscon (at http://www.dresden-elektronik.de/pwa/) and the Aqara switches were suddenly showing

I don't use Phoscon myself, but I see a lot of issues related to the browser cache.

Yep, and hb-Hue has been showing them perfectly in Homebridge/Home.app since pairing; 3 kinds of presses for single rocker and 3x3 for the double rocker.

You can use EVE app to toogle switch.
let's start:
Open SCENES --> RULES and ADD RULE. NEXT
First step (Trigger):
ADD TRIGGER, ACCESSORY --> OTHER VALUE.
Now - go to room, look for corespondent switch and mark "SINGLE PRESS".
Then ADD and NEXT
Second step (Value):
Add Value Condition
Go to room, find lamp (or other device).
(This is why HK know - to switch ON or OFF)
--> check Your device OFF ("next time" set ON) and NEXT
Third step (Scene):
Add Scene, find Your switch (from second step) and set reverse action for this in Value Condition (Value step).
(if in "Value step" it is OFF then set to ON). Name scene, name rule.
This is half of Your job.
Now again but reverse  (steps second and third "next time")


Document minimum host requirements for lima

Description
Currently when trying to run the Linux binary on Ubuntu 20.04, you get an error:
./bin/limactl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./bin/limactl)
./bin/limactl: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./bin/limactl)

So we need to document that you need Ubuntu 22.04 to run, and macOS xx..yy.
.github/workflows/release.yml:    runs-on: macos-12
.github/workflows/release.yml:    runs-on: ubuntu-22.04

We could also mention that you need qemu version 4.0.0 or higher, in order to run.

https://github.com/lima-vm/lima/issues/320

A stretch goal could be to redirect to where to find binaries for older OS versions.
Some of them, like CentOS 7 and Ubuntu 20.04, can be made to work (with effort)

Fixed:

https://github.com/lima-vm/lima/pull/1841

Supporting CentOS 7 (2014) and CentOS (2018) can be done by external party, as desired.
Otherwise we will assume that the Ubuntu 20.04 binaries will run, also on CentOS 9 (2022)


Replication demo

This PR adds a new tutorial demonstrating data replication with a local cluster.
Fixes #857

This change is

@spencerkimball, PTAL. I'd like to add simulations to these tutorials, too, at some point.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8bef82eeec6d74def78c55d43e329917f30967e2/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/59bd1ab25359a8e85d33fa632cba8308fe97480e/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9df555a2bd690fafc813c45a6482a76eec065c13/


don't require IP address or fully qualified domain name

Is your feature request related to a problem? Please describe:
My fans did not have fixed IP addresses. I modified my network set up to get my DHCP server to assign them fixed IPs for now, but wish I didn’t have to.
Describe the solution you'd like:
No idea what exists in this version of the Big Ass Fans protocol, but the older Haiku fans plugin supported discovering fans if I told it how many to expect.

Wanted to add: Thank you very much for making this plugin!
@pponce gave me a heads-up that this plugin existed before I had updated my Haiku fans. I got them updated, got them fixed IPs, and now they’re working great with this plugin.
I have a Haiku H-series, an I-series, and an I-series with a light.

I'm all for this.  If someone tells me what message the Big Ass Fans app sends out to trigger discovery I'll give it a shot that much quicker.
I could maybe address the fans using their "hostname" rather than IP if that would helpful in the meantime.  I just noticed I can connect to mine as BigFan.local.
PS - thanks

Yep it’s in no way urgent for me now, but it’s a step that I think would help others who want to get started using these fans with Homebridge. I’ll share if I figure anything out.

Turns out (per my test just now) if you use the fan's hostname instead of an IP address in the config, it works just as well.

Interesting! I’m not having much luck with that just yet.
(julian@saga)=(~)=(% host <IP_ADDRESS>
<IP_ADDRESS>.in-addr.arpa domain name pointer Entryway.
(julian@saga)=(~)=(% ping Entryway.local
ping: Entryway.local: Name or service not known
(julian@saga)=(~)=(% ping Entryway.local.
ping: Entryway.local.: Name or service not known
(julian@saga)=(~)=(% ping Entryway
ping: Entryway: Temporary failure in name resolution

@pponce discovered his Haiku's hostname was Haiku-xx:xx:xx where his fan name was Haiku and after the dashes the last 3 octets of his MAC address.  He found it using either Discovery or wifiman iPhone apps.

Thanks. I’m looking at what my Ubuntu NUC is telling me from avahi-browse. I see Fanname xx:xx:xx advertised but haven’t been able to figure out the mapping to the hostname I can use for ping. It does seem like a bug (on the Haiku’s end) if the advertised reverse host for address doesn’t map directly.

Lol, you just stepped outside my comfort zone.

@jmissig have you tried to ping
Fanname-xx:xx:xx.local
I also see it advertised as “Fanname xx:xx:xx” but the above ping works.

@pponce yeah trying various combinations of that now — that seems like the intended mapping — but they’re all failing. Looking more like a bug in my mDNS setup on this computer at the moment 🤷
+   eno1 IPv4 Entryway XX:XX:XX                             Web Site             local
=   eno1 IPv4 Entryway XX:XX:XX                             Web Site             local
   hostname = [Entryway-XX\058XX\058XX.local]
   address = [<IP_ADDRESS>]
   port = [31416]
   txt = ["mac=XX:XX:XX:XX:XX:XX" "path=/FW000007-GEN3"]

Oh! It works now. ping Entryway-XX:XX:XX.local is succeeding. I tried that before and it was failing. mDNS it is a mystery.

Cool.  Thanks for confirming this.

Now I have to ask, what's port = [31416] in the above avahi-browse -r _http._tcp output?  I only know about port 31415.

Seems to be an HTTP session. I’m trying some basic GET requests (at least, what I think are basic requests) and they’re all returning 400.

interesting 🤔

Definitely! I’ve not been able to yield anything of interest yet, but there’s something responding negatively to HTTP requests on that port.

perhaps the ghost of firmware past (or yet to come).

I use the iOS “Discovery” app.
Within that I go to the
“world wide web http, _http._tcp.” row.
When I click into that, I see my fans.
And if I click on a fan, amongst other details i see
FanName-XX:Xx:XX.local:31416
so I also see this 31416 port.

I’ve been successfully using the Entryway-XX:XX:XX.local type format since, well, April 23 2022 presumably.
Today some combination of updates seems to have made that stop working. I repeatedly get:
[7/22/2023, 7:15:42 AM] [homebridge-i6-bigassfans] Cocktail Room Overhead Fan (CocktailRoom-XX:XX:XX.local) : Unhandled network error: ENOTFOUND.  Attempting reconnect in 512 seconds.

Setup

Ubunutu 22.04.2 LTS (didn’t change, but I perform regular apt full-upgrade)
Nodejs v18.17.0 (updated just now)
Homebridge v1.6.1 (updated recently)
homebridge-i6-bigassfans v0.5.4 (updated recently)

Things I tried:

Confirmed I can ping CocktailRoom-XX:XX:XX.local and all the rest from the computer running Homebridge just fine.
Switched Homebridge between Avahi and Ciao, no change.

For now I’ve switched to resolved IP address, which works.


feat(exchanges): add binding for @urql/retry-exchange

This PR adds support for using @urql/retry-exchange.
The binding for this is fairly thin, although we did need to introduce a makeRetryExchangeOptions function to support the creation of a retryExchangeOptions record. There are generally two mechanisms for doing this type of "object creation with potentially undefined values" workflow. The first is what we do here, where we have a function that uses optional labelled arguments to generate a record. For example, calling makeRetryExchaneOptions with no arguments (just the positional unit parameter):
open ReasonUrql

let retryExchangeOptions = Client.Exchanges.makeRetryExchangeOptions();

results in the following object on the JS-side:
{
  initialDelayMs: undefined,
  maxDelayMs: undefined,
  maxNumberAttempts: undefined,
  randomDelay: undefined,
  retryIf: undefined,
}

while calling it with some arguments:
open ReasonUrql

let retryExchangeOptions =
  Client.Exchanges.makeRetryExchangeOptions(~initialDelayMs=2000, ~randomDelay=false, ())

results in the following object on the JS-side:
{
  initialDelayMs: 2000,
  maxDelayMs: undefined,
  maxNumberAttempts: undefined,
  randomDelay: false,
  retryIf: undefined,
}

We could also use an abstract record, but these are generally recommended against because of the ergonomics. The one case where they're useful is when compiling an unspecified property explicitly to undefined would result in negative behavior. In this case, urql checks the truthiness of all properties and supplies defaults downstream, so we should be safe explicitly compiling to undefined!

Good shout @kitten. I haven't figured out a good way of testing these new exchanges TBH. I think the tests of "can they be applied" actually aren't meaningful, because even a Client snapshot doesn't verify that the exchange is being applied. We'd need more sophisticated logic to execute requests with a Client instance and spy on some behavior of the exchange. That's more effort than I want to invest just yet, but I'll remove the unnecessary snapshots here 👍


Update index.html

The Github logo is not appropriate in the footer as here we try overflowing by using 12 + 5 small columns while we have max 12 columns so we can add that link in the first 8 columns and the logo in the last 4 columns.

@harsh1868  barely being able to see the octocat is by design. Thanks for the PR but we won't be merging it as we are looking into a complete re-design of the site.


Support relative patches in th15

Part of https://github.com/touhouworldcup/thprac/issues/92

Why is this is own issue?

Why is this is own issue?

Easier to track and if somebody would pick up another game it would be more visible that that one is also in progress.
However if we want to have everything in that  #92 then I can close this one


Translate errors

hi, is there anyway to translate default errors ?!

All exceptions use Django’s gettext_lazy. You’ll just need to add some more translations for languages we haven’t translated yet. Check out the locale dir in the package directory for all currently supported languages.

Actually i did some digging in locales before writing this issue but still couldn't find any thing relative to this package.

I must be confused somehow but all exceptions have translations for the currently support languages https://github.com/SimpleJWT/django-rest-framework-simplejwt/blob/master/rest_framework_simplejwt/locale/cs/LC_MESSAGES/django.po That’s an example file of translations.


Test

Just testing.  Don't merge!

/benchmark validation cap=11

/benchmark validation cap=8-12

/benchmark validation cap=11

/benchmark validation cap=8-12


Not able to log traces for Mongoose in NestJS

What version of OpenTelemetry are you using?
"@opentelemetry/auto-instrumentations-node": "^0.36.4",
"@opentelemetry/exporter-jaeger": "^1.10.0",
"@opentelemetry/exporter-metrics-otlp-proto": "^0.41.1",
"@opentelemetry/exporter-trace-otlp-http": "^0.37.0",
"@opentelemetry/instrumentation-express": "^0.32.1",
"@opentelemetry/instrumentation-graphql": "^0.35.0",
"@opentelemetry/instrumentation-grpc": "^0.36.0",
"@opentelemetry/instrumentation-http": "^0.36.0",
"@opentelemetry/instrumentation-ioredis": "^0.35.0",
"@opentelemetry/instrumentation-mongodb": "^0.36.0",
"@opentelemetry/instrumentation-mongoose": "^0.33.0",
"@opentelemetry/instrumentation-nestjs-core": "^0.33.0",
"@opentelemetry/resources": "^1.10.0",
"@opentelemetry/sdk-node": "^0.36.0",
"@opentelemetry/sdk-trace-base": "^1.10.0",
"@opentelemetry/semantic-conventions": "^1.10.0",

What version of Node are you using?
v18.17.0
What did you do?
I am attempting to capture logs for MongoDB interaction using Mongoose in NestJS, I've attempted both Auto instrumentation and named and neither capture any mongo interaction.
main.ts
import { otelSDK } from './tracing';
otelSDK.start();

import { NestFactory } from '@nestjs/core';
import { MicroserviceOptions, Transport } from '@nestjs/microservices';
import { join } from 'path';
import { AppModule } from './app/app.module';

async function bootstrap() {
  const app = await NestFactory.createMicroservice<MicroserviceOptions>(
    AppModule,
    {
      transport: Transport.GRPC,
      options: {
        package: 'employee',
        protoPath: {path-to-proto},
        url: '<IP_ADDRESS>:{port}'
      },
    },
  );
  await app.listen();
}
bootstrap();

tracing.ts (auto instrumentation)
import {
  BatchSpanProcessor,
} from '@opentelemetry/sdk-trace-base';
import { NodeSDK } from '@opentelemetry/sdk-node';
import * as process from 'process';
import { getNodeAutoInstrumentations } from '@opentelemetry/auto-instrumentations-node';
import { Resource } from '@opentelemetry/resources';
import { SemanticResourceAttributes } from '@opentelemetry/semantic-conventions';

import { OTLPTraceExporter } from '@opentelemetry/exporter-trace-otlp-proto';

const jaegerExporter = new OTLPTraceExporter({
  url: 'http://localhost:4318/v1/traces',
});

export const otelSDK = new NodeSDK({
  spanProcessor: new BatchSpanProcessor(jaegerExporter),
  resource: new Resource({
    [SemanticResourceAttributes.SERVICE_NAME]: {service-name},
    [SemanticResourceAttributes.SERVICE_NAMESPACE]:
      process.env.GOOGLE_CLOUD_PROJECT_NAME,
    [SemanticResourceAttributes.SERVICE_INSTANCE_ID]:  {service-name},
  }),
  instrumentations: [
    getNodeAutoInstrumentations({
      '@opentelemetry/instrumentation-mongoose': {
        enabled: true,
        requireParentSpan: false,
        suppressInternalInstrumentation: false
      },
      '@opentelemetry/instrumentation-http': {
        enabled: false,
      },
      '@opentelemetry/instrumentation-fs': {
        enabled: false
      },
      '@opentelemetry/instrumentation-nestjs-core': {
        enabled: false,

      },
      '@opentelemetry/instrumentation-ioredis': {
        enabled: true,
        requireParentSpan: false
      },
      '@opentelemetry/instrumentation-net': {
        enabled: false,
      },
      '@opentelemetry/instrumentation-grpc': {
        enabled: true,
      },
      "@opentelemetry/instrumentation-graphql": {
        enabled: true,
      },
      "@opentelemetry/instrumentation-mongodb": {
        enabled: true,
        enhancedDatabaseReporting: true,
      },
      '@opentelemetry/instrumentation-dns': {
        enabled: false
      }
    }),
  ],
});

mongo.module.ts
import { Module } from '@nestjs/common';
import { ConfigModule, ConfigService } from '@nestjs/config';
import { MongooseModule } from '@nestjs/mongoose';

@Module({
  imports: [
    MongooseModule.forRootAsync({
      imports: [ConfigModule],
      useFactory: async (configService: ConfigService) => ({
        uri: configService.get<string>('DATABASE_CONN'),
        useNewUrlParser: true,
        useUnifiedTopology: true,
      }),
      inject: [ConfigService],
    }),
  ],
})
export class MongoModule {}

app.module.ts
import { MongoModule } from './mongo.module.ts';
import { forwardRef, Module } from '@nestjs/common';

import { GraphQLModule } from '@nestjs/graphql';
import {
  ApolloFederationDriver,
  ApolloFederationDriverConfig,
} from '@nestjs/apollo';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { CommonModule } from './common.module.ts';
import { ConfigService } from '@nestjs/config';

@Module({
  imports: [
    forwardRef(() => CommonModule),
    MongoModule,
    GraphQLModule.forRootAsync<ApolloFederationDriverConfig>({
      driver: ApolloFederationDriver,
      imports: [CommonModule],
      inject: [ConfigService],
      useFactory: async (configService: ConfigService) => ({
        typePaths: [
          './**/*.graphql'
        ],
      }),
    }),
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}

example db call
getAll(): Promise<Customer[]> {
    return this.usersModel
      .find({ deleted: false })
      .sort({ name: 1 })
      .exec();
}

What did you expect to see?
I would expect to see spans logged providing timings for DB calls
What did you see instead?
No MongoDB communication is logged.
Additional context
"@nestjs/mongoose": "^9.0.3",
"mongoose": "^6.2.4",
"@nestjs/core": "9.0.9",

This blog post has a lot of useful tips on how to diagnose common issues: https://www.aspecto.io/blog/checklist-for-troubleshooting-opentelemetry-nodejs-tracing-issues/
Please try it out and update here about your findings:

Do you see the mongoose instrumentation patching message in otel diag logs?
Do you see any spans at all? if you create a manual span, are you able to see it in jaeger?

seems like the same issue as #1469

Hi @blumamir. Thanks for the response. Had a look at the diagnose article and found the following:
Do you see the mongoose instrumentation patching message in otel diag logs - Yes see below:
@opentelemetry/instrumentation-nestjs-core Module @nestjs/core has been loaded before @opentelemetry/instrumentation-nestjs-core so it might not work, please initialize it before requiring @nestjs/core
@opentelemetry/instrumentation-grpc Module @grpc/grpc-js has been loaded before @opentelemetry/instrumentation-grpc so it might not work, please initialize it before requiring @grpc/grpc-js
@opentelemetry/instrumentation-graphql Module graphql has been loaded before @opentelemetry/instrumentation-graphql so it might not work, please initialize it before requiring graphql
@opentelemetry/instrumentation-mongoose Module mongoose has been loaded before @opentelemetry/instrumentation-mongoose so it might not work, please initialize it before requiring mongoose

Interestingly I am seeing a few errors such as graphql loaded before instrumentation-graphql however the interesting one is that instrumentation-mongoose is complaining about the instrumentation loading before instrumentation.
Do you see any spans at all? if you create a manual span, are you able to see it in jaeger? - Yes I see a lot of logs, almost for everything except Mongoose.

@blumamir interestingly if I move my trace init process out of a separate file and put it inline above the bootstrap process I do start to capture Mongoose instrumentation, however no matter how I attempt call and init tracing in another file it doesn't capture. Is there a recommended approach to structuring the trace init when in another file?

Thanks for trying it and updating your findings here.
I do not remember the exact details, but nestjs import a lot of things before the app actually runs, so hooking up opentelemetry into nest requires modifying the nest command itself, something like this: nest start -e 'node -r ./tracing.js'
When I tested the integration with aspecto otel distribution a long time ago, I got it to work and documented instructions here: https://docs.aspecto.io/v1/send-tracing-data-to-aspecto/aspecto-sdk/nodejs/nestjs
The docs are for a specific (aspecto) distribution, but you can modify it quite easily to your SDK setup.


bugfix: correct resource change action

close: https://github.com/KusionStack/kusion/issues/169

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.2%) to 72.117%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/engine/operation/graph/resource_node.go
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

pkg/kusionctl/cmd/destroy/options.go
7
83.25%

pkg/kusionctl/cmd/apply/options.go
7
73.77%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
4552

Relevant Lines:
6312

💛  - Coveralls


Implement the saving and reading of taskList

TaskList will now save to schedulelist.json.
Format of serialized Tasks:
For a DONE task:
+{taskDescription} e.g. "+Contact parents"
For an UNDONE task:
-{taskDescription} e.g. "-Contact parents"
TaskList is serialized as a comma separated string.
for e.g.:
"+Contact parents,-Mark work"
Additional changes

Re-enabled the TaskListView
Removed the sample tasks in LessonDetailListPanel.java

Fix  #125


imports.json needs better resolution

Currently, the fallback imports.json is resolved relative to the pwd not the executing script
Additionally, this can only be a local path not a URL. Ideally, this should look next to the script file even for remote scripts.

Fixed in v1.5.4


Proposal: Template as entry point for UI components

Current setup:
src/components/my-component/
index.js
module.exports = require('marko-widgets').defineComponent({
    template: require('./template.marko'),
    getTemplateData: function(state) { ... },
    ...
});

template.marko
<div w-bind>
    ...
</div>

Proposed solution
The above setup is not bad, but there is some boilerplate that we would like to remove by making the following changes:

Rename: index.js → component.js
Rename: template.marko → index.marko (the template becomes the entry point)
Remove: require('marko-widgets').defineComponent(...)
Remove: template: require('./template.marko')

Marko Widgets will detect that the template is the entry point and compile the template differently such that it no longer exports a Template instance, but rather it will be a module that exports two methods:

render(input) - Allows the UI component be rendered via a JavaScript API (e.g., require('my-component').render({ name: 'Frank' }).appendTo(document.body);)
renderer(input, out) - Used by the custom tag renderer

The previous setup would now be simplified as shown below:
src/components/my-component/
component.js
module.exports = {
    getTemplateData: function(state) { ... },
    ...
};

index.marko
<div w-bind>
    ...
</div>

Additional thoughts
Future improvements
By making the template the entry point, we can do a lot more things that were not previously possible. This is because we have full control over how a Marko template is compiled while we don't have control how the user writes the JavaScript code.
Single file component
We could easily support inlining the JavaScript code for the component into the template as shown below:
<div w-bind>
    ...
</div>

<script marko-component>
var Component = {
    getTemplateData: function(state) { ... },
    ...
};
</script>

No references to marko-widgets
With the new setup, there are no references to the marko-widgets module when building a UI component. This is a good thing since it makes it easier to merge Marko Widgets functionality into the core marko package (future proposal).
Backwards compatibility
We intend to maintain backwards compatibility. Developers could start to use the new, simplified setup, but old code would continue to work.
Related proposals

Issue #152 - Proposal: Marko Widgets with ES6 and inline Marko templates

Would there be any proposed changes to defineRenderer and defineWidget in this case? Are you looking to phase those out?

@yomed

Would there be any proposed changes to defineRenderer and defineWidget in this case? Are you looking to phase those out?

To keep things simple I didn't want to go into the split renderer case, but we would also like to simplify that as well by removing the calls to defineRenderer and defineWidget:
Split widget/renderer
src/components/my-component/
renderer.js
module.exports = {
    getTemplateData: function(state) { ... },
    ...
};

widget.js
module.exports = {
    handleFooClick: function() { ... },
    ...
};

index.marko
<div w-bind>
    ...
</div>

I would very much look forward to this change.

Ah, this looks amazing!
Also:
module.exports = {
    getTemplateData: function(state) { ... },
    ...
};

Not?:
export default {
    getTemplateData: function(state) { ... },
    ...
};

@basickarl You are free to use ES6 (you'll need to use babel on both the server and the browser if you use import/export though). We plan on allowing the following as well:
export default class {
    handleFooClick() { ... }
    handleBarClick() { ... }
    ...
};

The only good reason to use class is that you don't have to worry about comma separators, which is kind of nice.

Closing this issue in favor of the issue created on the marko repo: https://github.com/marko-js/marko/issues/416


Add pure operations (pure_map, pure_flat_map) that use memoization to improve performance

Description
Propose versions of map and flat_map that use memoization to improve performance. This works only for pure functions so we add a new function instead of modifying map.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

@Gondolav WDYT? I made additions only to list for now to open the discussion.

I like it, but you could use directly functools.cache() on the function to apply ;)

haha thanks, didn't know this package :)

I did the modifications :) @Gondolav

done 👍


CONFIG_ERROR - ElasticSearch's version is not compatible

不支持es6.3.2？

In ‘ElasticRestClient'，will check the major version between connected and current used automatically. Default version of dependency is '6.7.x', you can try to change the version

好的


Improve flexibility of input files

Like the v1 pipeline, this workflow assumes that the input fasta files are names PREFIX_1.fastq.gz and PREFIX_2.fastq.gz. This is convenient to write and configure but insufficiently flexible, especially since many input read files are suffixed R1 and R2 rather than _1 and _2.
nf-core pipeline requires a samplesheet that fully specifies the path to each read file. This seems like overkill, but hopefully there's something intermediate that would work well for our use case.

Renaming input files to have the suffixes we expect when importing them seems fine?  There are a lot of formats we could receive data in (interleaved fastq, bam, nanopore squiggles) and requiring a little munging before data goes into the pipeline doesn't seem to bad to me

I think at a minimum we should be able to handle R1 and R2.

This is not handled in the new pipeline version currently in the dev branch, so remains an active issue.

Further discussion here: https://github.com/naobservatory/mgs-workflow/issues/24

For being able to handle either _R1.fastq.gz or _1.fastq.gz, we can enable extended globbing and use the ?(R) pattern,
shopt -s extglob
# Get file paths from library IDs
r1=""
r2=""
for l in !{libraries.join(" ")}; do
  L1=$(ls ${read_dir}/*${l}*_?1.fastq.gz)
  L2=$(ls ${read_dir}/*${l}*_?2.fastq.gz)
  r1="${r1} ${L1}"
  r2="${r2} ${L2}"
done

Files output by Illumina software often have an additional field after the R#, e.g. {sample-name}_S3_L001_R1_001.fastq.gz. The following extended glob seems to be working but looks a little ugly and I may replace it with a regex solution:
L1=$(ls ${read_dir}/*${l}*_?(R)1?(_[[:digit:]][[:digit:]][[:digit:]]).fastq.gz)
L2=$(ls ${read_dir}/*${l}*_?(R)2?(_[[:digit:]][[:digit:]][[:digit:]]).fastq.gz)

This is obsolete as of v2.4, as the pipeline now takes in full input filepaths via the samplesheet.


Change (1) Makefile, and (2) deps.edn; add (3) resources/logback.xml

(1) The Makefile changes remove the use of deprecated -A flag in favor of -M.
(2a) The deps.edn changes update the olical/depot dependency for outdated dependency management.
(2b) olical/depot expects there to be a logger, so two additional dependencies, slf4j and logback-classic, were added in order to prevent the errors when running make outdated
(3) By default, logback-classic log level is DEBUG, which results in unnecessary logging, so the resources/logback.xml file deals with that, as well as standardizes log formatting to a common pattern that can be searched, as the regex is defined in the file.

Thanks for your contribution :-)


File exists, but ENOENT: no such file or directory... reported.

I'm receiving the following error for some, but not most, files in my project.
(node:26484) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, realpath 'C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\composite-permissions.service.js'
    at Function.realpathSync.native (fs.js:1684:3)
    at Function.native (electron/js2c/asar_bundle.js:5:4556)
    at c:\Users\usernam\.vscode\extensions\dbaeumer.vscode-eslint-2.1.19\server\out\eslintServer.js:1:14128
    at I (c:\Users\usernam\.vscode\extensions\dbaeumer.vscode-eslint-2.1.19\server\out\eslintServer.js:1:14188)
    at c:\Users\usernam\.vscode\extensions\dbaeumer.vscode-eslint-2.1.19\server\out\eslintServer.js:1:16188
(node:26484) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 290)

Note that failure is silent. I have to open the Output tab to see that anything's wrong. I would not have known except that I noticed issues eslint should have caught.
(Actual user name in paths changed to protect the innocent.)

Files with this error (not necessarily exhaustive, but all I can find atm):
C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\cache.service.js
C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\composite-permissions.service.js

Works from the same parent folder:
C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\folder-store.service.js
C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\folder.js

The "no such file or directory" makes me suspect it's not the contents of the files that's the issue, which is why I'm giving paths here.
But additionally note that If I move a file that won't lint to, eg, c:\temp\composite-permissions.service.js, it lints as expected. Another piece of evidence that it's not content?
If I execute eslint C:\workspaces\WebProduct\Features\MF-QBvN2\Source\Instructor\QuestionBuilder\QuestionBuilder.Web\Scripts\QuestionBuilder\Bank\Models\composite-permissions.service.js from a command prompt in the C:\Users\usernam directory, the file lints as expected.
Is there a limit to the characters in a file path specific to the extension? Anything else I can send?

@ruffin-- a workaround is to specify your installed node version as the runtime using the eslint.runtime setting. But please note that you need to confirm the setting using the Command ESLint: Select Node Runtime.
Let me know if that helps.

I'll give that a shot today. Out of curiosity, what's causing it to blow up? The paths of things that work seem as long or longer than some that fail. Is it b/c they start with c? (I'm joking. I think. :^D)

VS Code updated to v1.55.0 and now I'm receiving

Output says...
[Info  - 1:08:59 PM] ESLint server is starting
[Info  - 1:08:59 PM] ESLint server stopped.
[Error - 1:08:59 PM] Starting client failed
Launching server using runtime C:\Program Files\nodejs\eslint failed.

I no longer receive the above error after removing eslint.runtime from settings.
That is, I'm not 100% how sure a fix this is. I'm in another project now; will try with the one that was giving the original errors when I return.

@ruffin-- you need to set the runtime setting to a node executable (e.g. node.exe). In addition you need to confirm.
The reason why this will address the issue is that it looks like you are using JS constructs which aren't support in the node runtime VS Code ships.

@dbaeumer I'm experiencing the same issue, changing node runtime doesn't help; tried 14, 15, 16.
I see this happening on very long file paths, 250-255

@Niaro this could be the old Windows path limitation of 256 characters.

@Niaro this could be the old Windows path limitation of 256 characters.

That was my assumption too, I changed the registry setting to support long paths and nothing has changed. Although I didn't restart the machine... Could be it

I am actually not very familiar with the workaround of the long path name issues in Windows.

select node version failed
and why the eslint disappear from the vscode status bar

I get this error when I create a new file.  To fix it, I either have to save the file, close it, then re-open it, or restart the LSP workspace.

I have the same problem, someone knows how to solve it, at the moment the solution is to upload that component a subfolder before, and there it reads, but when many subfolders eslint does not support it.
(node:24172) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, realpath 'G:\proyectos\deerview\frontendsegurosuni\src\app\universal\area-tecnica\configuracion-producto\components\productos\descuento\editar-descuento\descuento-usuario\editar-descuento-usuario\modal-plan-usuario\editar-modal-plan-usuario\editar-modal-plan-usuario.component.html'
    at Function.realpathSync.native (fs.js:1787:3)
    at Function.native (electron/js2c/asar_bundle.js:5:4607)
    at c:\Users\Luis O. Gonzalez\.vscode\extensions\dbaeumer.vscode-eslint-2.2.2\server\out\eslintServer.js:1:171219
    at X (c:\Users\Luis O. Gonzalez\.vscode\extensions\dbaeumer.vscode-eslint-2.2.2\server\out\eslintServer.js:1:171279)
    at c:\Users\Luis O. Gonzalez\.vscode\extensions\dbaeumer.vscode-eslint-2.2.2\server\out\eslintServer.js:1:174350
(node:24172) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36)

I am also  seeing this issue on a Windows machine with the registry setting to allow for long file paths turned on. No visible errors but files with a path over 256 are not showing the linter errors.

@thomaswdean I had to move the files because I did not find suddenly someone has managed to solve it

@luis-cosillo Thank you. I am considering doing the same. I just wanted to post here to see if anything is being done to address this issue.

@thomaswdean Yes, I still hope to have it because it may be later on, depending on the project, but hopefully they will fix it.

I do not think this has been fixed yet... Same issue

Follow the only solution is to rename files

This is an actual issue which might be hard to fix.
Say I have a filename which should be AppleandPeach.jpg
This "feature" of VSCode makes the filename as appleandpeach.jpng.  How will u programmatically capitalize the capital letter in the second word? No way.

For me error looks like this:
Error: ENOENT: no such file or directory, realpath '/Users/username/path/src/lib/ui/dialog/index.ts'
    at realpathSync.native (node:fs:2554:3)
    at Function.native (node:electron/js2c/asar_bundle:5:4831)
    at t.getFileSystemPath (/Users/username/.vscode/extensions/dbaeumer.vscode-eslint-2.2.6/server/out/eslintServer.js:1:33280)
    at b (/Users/username/.vscode/extensions/dbaeumer.vscode-eslint-2.2.6/server/out/eslintServer.js:1:206750)
    at /Users/username/.vscode/extensions/dbaeumer.vscode-eslint-2.2.6/server/out/eslintServer.js:1:19353
    at async /Users/username/.vscode/extensions/dbaeumer.vscode-eslint-2.2.6/server/out/eslintServer.js:1:210071

This file existed in different branch.
Workaround: delete repo where issue appears, create new folder with new path, clone repo.
I've tried to clean cache, vscode history and other things too.. Nothing except this helps.
Maybe vscode-eslint uses some cache under the hood that may be outdated or something..

Same issue here, occurs when filepath length is greater than Windows MAX_PATH length, even though long paths are enabled both in policies and registry. In my case, filepath length is 302.
Looking forward for a fix.
Log:
Uncaught exception received.
Error: ENOENT: no such file or directory, realpath 'LONG_COMPONENT_PATH_THAT_IS_PRIVATE'
    at Function.realpathSync.native (node:fs:2554:3)
    at Function.native (node:electron/js2c/asar_bundle:5:4831)
    at t.getFileSystemPath (c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:34203)
    at b (c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:217463)
    at c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:19757
Uncaught exception received.
Error: ENOENT: no such file or directory, realpath 'LONG_COMPONENT_PATH_THAT_IS_PRIVATE'
    at Function.realpathSync.native (node:fs:2554:3)
    at Function.native (node:electron/js2c/asar_bundle:5:4831)
    at t.getFileSystemPath (c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:34203)
    at b (c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:217463)
    at c:\Users\Ilya\.vscode\extensions\dbaeumer.vscode-eslint-2.4.0\server\out\eslintServer.js:1:19757

They still haven't fixed it, I think we will die without a solution

I've done some research and probably it's related to a node version VS Code is using.
My VS Code setup:
Version: 1.76.2 (user setup)
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
Date: 2023-03-14T17:55:54.936Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
There was an issue (https://github.com/nodejs/node/pull/44536) with fs.realpathSync.native  that was fixed in Node v16.18.0 & 18.10. As we can above, in the VS Code versions, it uses Node v.16.14.2.
Sadly, we cannot do anything until VS Code starts using newer version of Node.

@tryonelove actually you can. You can use eslint.runtime setting to point to a different node version used to run the ESLint server.


fix ipmitool location

unfortunately  Dockerfile was wrong, and ipmitool in emebedded was not added to image

Are you sure?
just built image from master branch and i see ipmitool  in image an Docker file looks correct.
go build
docker build . -t mauy-infopusher
docker save mauy-infopusher > image
mkdir tmp
tar xf image -C tmp
ls tmp/*/layer.tar | xargs -I{} tar tf {} | grep ipmitool

gives embedded/ipmitool

@r7vme for some reason image built  by quay did not have the folder and ipmitool available, so i switched to more foolproof direction.


Make locked y position account for wave height

Could make it move upwards to be at the top of the wave height
Might also want to move the player fixed position a bit farther back so that if they do start dipping under the boat they dont clip into it

Since they can set their player position this is fine honestly


BUG: foldlevel breaks help display

Did you check docs and existing issues?

[X] I have read all the docs.
[X] I have searched the existing issues.
[X] I have searched the existing discussions.

Neovim Version (nvim -v)
v0.10.0
Operating System / Version
macOS 14.4.1
Describe the Bug
When I set vim.opt.foldlevel = 3 in my config the neo-tree help menu gets super wonky:

When I remove this or set it to something like vim.opt.foldlevel = 999 things work as expected:

I can't use fold commands to show the text but I can expand/collapse stuff in the help menu using :foldopen a few times on certain items:

Is there something I can do short of disabling foldlevel in my config or is there maybe a way to have the help pop-up have a different fold level or ignore folding? This feels like a bug but it also feels like one of those weird ones where it's my fault for having a lower fold level.
Screenshots, Traceback
No response
Steps to Reproduce

Set vim.opt.foldlevel = 3
Open file explorer
Toggle help

Expected Behavior
Full help menu is displayed without issue
Your Configuration
vim.opt.foldlevel = 3

-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
  vim.fn.system({ "git", "clone", "--filter=blob:none", "https://github.com/folke/lazy.nvim.git", lazypath, })
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  -- add any other plugins here
}

local neotree_config = {
  "nvim-neo-tree/neo-tree.nvim",
  dependencies = { "MunifTanjim/nui.nvim", "nvim-tree/nvim-web-devicons", "nvim-lua/plenary.nvim" },
  cmd = { "Neotree" },
  keys = {
    { "<Leader>e", "<Cmd>Neotree<CR>" }, -- change or remove this line if relevant.
  },
  opts = {
    -- Your config here
    -- ...
  },
}

table.insert(plugins, neotree_config)
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

I haven't had a chance to test it locally but I wonder if something like this:
  vim.api.nvim_buf_set_option(popup.bufnr, 'foldenable', false)

Inside of lua/neo-tree/sources/common/help.lua might take care of things.


Implement Truncate

There is no protocol command to do this, so it would need to be implemented by combining disable + drop + create. I have implemented this myself in a wrapper, and it works, but there are two issues that would be best if directly integrated into gobhase:

The largest issue is that with the current API exposed by gohbase, you need to specify the column families when you create the table, and if a table already exists, there is no way to retrieve this information. For this to work best, gohbase should at least implement the Describe Table command to retrieve this information programmatically.
Disable, Drop, and Create all take a context.Context, which is great, but there is no easy way (that I am aware of, at least) to have a context that spans all 3 of these commands. For instance, If I pass a context to the Truncate function, it should only call Done when all 3 of Disable, Drop, and Create have completed.

It would be nice if gohbase provided this integration directly. At the very least, support for Describe Table would be great.

I would prefer to implement the support for DescribeTable and keep AdminClient to minimum. It should be trivial to implement Truncate by users. We can start from that at least.

Implementing DescribeTable is a great start, but leaving implementation of Truncate up to the user leaves issue #2 unresolved. Unless you can think of a better way to handle the cross-call context for cancellation?

Actually, I think my understanding of context.Context was inaccurate and this should just work.

I'm going to close this for now.


ECM-434 Fix Case API update Multiple reference

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/ECM-434
Change description
Extend Fix Case API to update multiple references in single cases
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

build.gradle -> version needs incrementing


Istio Circuit Breaker Not working with Kong

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
2.2
Current Behavior
We’re running Istio on Kubernetes and Kong as API gateway and ingress controller for our K8S cluster.
We’ve created virtual services and destination rules and applied circuit breaking rules for our service.
I'm using fortio client in order to test circuit breaker functionality. Functionality is working perfectly fine and circuit breaking is happening if fortio is calling the service directly.
The same is not working as expected when fortio is calling Kong and Kong itself is calling the service.
fortio ==> service (Working fine)
fortio ==> kong ==> service (Not working)
Could please anyone advise here urgently ?
Expected Behavior
Circuit breaking should happen even if the call is coming through Kong.
Steps To Reproduce
No response
Anything else?
No response

@dawo0od Make sure Kong is configured properly to forward status, headers to client according your circuit breaker policies.

@fffonion I have found that in my Istio-proxy logs for my Kong POD , it is connecting to my service with the POD IP , not the service IP. I believe this is the issue.
Is this the normal behavior for Kong that it is calling the service with the POD IP ?

[C117875][S7310483570645225078] cluster 'PassthroughCluster' match for URL '/price-listing-service/v1/config/currency/0'
2021-12-27T11:06:31.643385Z	debug	envoy upstream	transport socket match, socket default selected for host with address <IP_ADDRESS>:8080
2021-12-27T11:06:31.643394Z	debug	envoy upstream	Created host <IP_ADDRESS>:8080.
2021-12-27T11:06:31.643470Z	debug	envoy upstream	addHost() adding <IP_ADDRESS>:8080
2021-12-27T11:06:31.643513Z	debug	envoy upstream	membership update for TLS cluster PassthroughCluster added 1 removed 0
2021-12-27T11:06:31.643543Z	debug	envoy upstream	re-creating local LB for TLS cluster PassthroughCluster
2021-12-27T11:06:31.643572Z	debug	envoy router	[C117875][S7310483570645225078] router decoding headers:

@fffonion  Any update here please ?

@dawo0od Sorry for the late reply. Try to use the annotation mentioned in this blogpost: https://kubernetes.io/blog/2020/03/18/kong-ingress-controller-and-istio-service-mesh/
ingress.kubernetes.io/service-upstream: "true" .

@fffonion Yes I have this annotation configured on the service level already and preserve_host is disabled as well but still does not work.
Actually we are struggling with this  since long time and not able to get it fixed. I've also noticed that a lot of people have exactly the same issue as per below link.
https://discuss.konghq.com/t/kong-ingress-controller-is-unable-to-route-request-to-istio-virtual-services/4457/5

@Kong/team-k8s

@dawo0od Hi, what Kong Kubernetes Ingress Controller version are you using?

@dawo0od Also, can you provide the Helm Chart version of Ingress Controller and post values.yaml file here?

notice: don't forget to remove sensitive secrets from values.yaml

There may be something wrong with the configuration and these versions of running components may help us investigate and find the key to solving your question.

We have references for running Kong and Istio in your K8s clusters.
Take a look:

https://docs.konghq.com/kubernetes-ingress-controller/2.0.x/guides/getting-started-istio/
https://github.com/Kong/demo-scene/tree/main/gateway4mesh/istio

@mayocream We are using Kong ingress controller version 1.2 and helm chart 3.
Please also find attached va/Users/dicetekllc/Documents/Hyke-git-repos/hyke-cicd/k8s/charts/java/hyke/java-nonprod-1.0/java-nonprod/values.yamllues.yaml file as you requested.
Please also note that I've already tried below link you shared on my minikube cluster but still istio routing rules are not working. They are only working when calling from service to service directly and not through Kong.
https://docs.konghq.com/kubernetes-ingress-controller/2.0.x/guides/getting-started-istio/
values-yaml.txt

Do the controller logs indicate it's failing to update configuration? If you set ingressController.env.log_level=debug in your Helm values, do you see a fetching endpoints log for the upstream in question?
The code that handles this is quite simple and is tested; there's not an obvious reason for it to fail. We check for the presence of the annotation at:
https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/pkg/annotations/annotations.go#L187-L191
https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/pkg/annotations/annotations_test.go#L274-L309
And then set the service hostname as the sole upstream target at:
https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/pkg/parser/parser.go#L385-L391
https://github.com/Kong/kubernetes-ingress-controller/blob/v1.2.0/pkg/parser/parser_test.go#L3424-L3458
If you do see a fetching endpoints log for that upstream, that indicates we did not see the annotation on the Service. Can you provide the Service YAML definition and the admin API output for GET /upstreams/<UPSTREAM>/targets, where <UPSTREAM> is <service name>.<service namespace>.<service port>.svc (e.g. for a Service named foo in namespace default on port 80, foo.default.80.svc).

@rainest  Thanks a lot for your response. The issue is that I was using Ingress.kubernetes.io/service-upstream: "true" instead of ingress.kubernetes.io/service-upstream: "true" ('I' of ingress was capital ) :(
Last question please , in my case do I need to have Istio side car on Kong POD as well ? or it is not mandatory ?

We indicate that you should use sidecars on the Kong instances in https://docs.konghq.com/kubernetes-ingress-controller/2.0.x/guides/getting-started-istio/#deploy-kong-gateway-and-kubernetes-ingress-controller
I think the more specific answer is that you do not need one for some Istio features, e.g. circuit-breaking should not require anything on the Kong side since it can be handled entirely by the upstream Service's sidecar, whereas other features require sidecars on both the client (Kong) and upstream, e.g. mutual TLS requires that both sides have a sidecar to present the managed certificate. Not positive as I haven't tested it exhaustively, but that's what I would expect.

remove here values.yaml in this sensitive information


upgrade: reject formulae checked in earlier levels

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?

@MikeMcQuaid  -- I finally hit that depth level issue you had previously told me about in #6397, when upgrading the packages below:
amalia@Sakura:~ $ brew outdated
ffmpeg (4.2.1) < 4.2.1_1
gdk-pixbuf (2.38.2) < 2.40.0
gtk+3 (3.24.12) < 3.24.12_1
libsoup (2.68.1) < 2.68.2
vala (0.46.2) < 0.46.3
x264 (r2917) < r2917_1
yarn (1.19.0) < 1.19.1

This pull request ensures that only new kegs are scanned in each level. I've attached the stacktrace in a separate file, because it is TOO BIG.
massive-log.txt
CAVEAT: I know brew style will fail -- I'm happy to get any suggestions in order to fix that double-block chain.

Thanks again @amyspark!

Still has this issue in 2.1.15.

@smoothdvd see https://github.com/Homebrew/brew/issues/6586


Pasting a Head tag replaced with a div

pasting in something like the below
      <Head>
        <meta
          key="twitter:title"
          name="twitter:title"
          content="Tailwind CSS - Rapidly build modern websites without ever leaving your HTML."
        />
        <meta
          key="og:title"
          property="og:title"
          content="Tailwind CSS - Rapidly build modern websites without ever leaving your HTML."
         />
  <meta key="og:title" property="og:title" content="Tailwind CSS - Rapidly build modern websites without ever leaving your HTML." />
  <title>Tailwind CSS - Rapidly build modern websites without ever leaving your HTML.</title>
</div>

Thanks for opening the issues, however I would not really consider this a bug, since <Head> is not a valid HTML tag.
The htmltojsx-package that we use under the hood probably replaces invalid tags with <div>.

gotcha. not the end of the world, but assumed it would keep it, especially in this case as it is a valid nextjs tag :-) even if it wasn't, would still personally want it to keep custom component tags like that. maybe you add a setting where we can control that? regardless, cool tool so far!

Oh so you are just copying JSX, not HTML now I get it. The extension currently doesn't detect if you are copying JSX and will just try to convert it to JSX again, which is why the tag gets messed up.
I'll see if I can make it so the extension detects that you copied JSX and not do any conversion then.

I added the detection of JSX tags for version 0.2.2, so the problem should be fixed when you upgrade.


Convert commons-logging to slf4j

Replace Java Commons Logging with slf4j to make sure we are independent
in a good way.

Err need to update ver


[3.x, iOS] Remove deprecated LaunchImages support and switch to Storyboard by default.

Backport of https://github.com/godotengine/godot/pull/86312 for 3.x

Thanks!


persistWithLocalStorage causes content mismatch between server/client

Describe the bug
Not 100% sure I can accurately describe the issue (mostly because I can't get an exact reproduction going), but I'll do my best.
It seems that when using persistWithLocalStorage in a Next.js app, it causes a content mismatch with the devtools between server/client when refreshing the page (after the queries are saved to local storage).
This is what I get in my app (not a public repo):
Warning: Text content did not match. Server: "0" Client: "1"
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef)
    in ForwardRef (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef)
    in ForwardRef (created by ForwardRef(ReactQueryDevtoolsPanel))
    in ThemeProvider (created by ForwardRef(ReactQueryDevtoolsPanel))
    in ForwardRef(ReactQueryDevtoolsPanel) (created by ReactQueryDevtools)
    in ThemeProvider (created by ReactQueryDevtools)
    in footer (created by ReactQueryDevtools)
    in ReactQueryDevtools (at _app.tsx:50)
    in QueryClientProvider (at _app.tsx:40)
    in MyApp (created by withRedux(MyApp))
    in Provider (created by withRedux(MyApp))
    in withRedux(MyApp)
    in ErrorBoundary (created by ReactDevOverlay)
    in ReactDevOverlay (created by Container)
    in Container (created by AppContainer)
    in AppContainer
    in Root

I'm assuming the issue is the devtools thinks there isn't any queries on the server, but then hydrates them on the client from local storage, causing a mismatch.
To Reproduce
Small repo following the Next.js example:
https://codesandbox.io/s/billowing-grass-z1l7t
I can't seem to reproduce the exact same error above from my app, but it still shows some warnings in the console about mismatching content. Start by saving some queries to the cache (click the 1 2 3 4 5 buttons to generate different content) and then refresh the page to persist the queries in local storage. The console flashes this warning:
Warning: Expected server HTML to contain a matching <ul> in <section>.
    in ul (at pages/index.js:34)
    in section (at pages/index.js:24)
    in SomeComponent (at _app.js:14)
    in Hydrate (at _app.js:13)
    in QueryClientProvider (at _app.js:12)
    in MyApp
    in ErrorBoundary (created by ReactDevOverlay)
    in ReactDevOverlay (created by Container)
    in Container (created by AppContainer)
    in AppContainer
    in Root

Commenting out the persist and deleting the localstorage item takes it away, but I still see some odd style mismatches:
Warning: Prop `style` did not match. Server: "display:flex;border-bottom:solid 1px #222e3e;cursor:pointer" Client: "display:flex;border-bottom:solid 1px #222e3e;cursor:pointer;background:rgba(255,255,255,.1)"
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef(ReactQueryDevtoolsPanel))
    in div (created by ForwardRef)
    in ForwardRef (created by ForwardRef(ReactQueryDevtoolsPanel))
    in ThemeProvider (created by ForwardRef(ReactQueryDevtoolsPanel))
    in ForwardRef(ReactQueryDevtoolsPanel) (created by ReactQueryDevtools)
    in ThemeProvider (created by ReactQueryDevtools)
    in footer (created by ReactQueryDevtools)
    in ReactQueryDevtools (at _app.js:16)
    in QueryClientProvider (at _app.js:12)
    in MyApp
    in ErrorBoundary (created by ReactDevOverlay)
    in ReactDevOverlay (created by Container)
    in Container (created by AppContainer)
    in AppContainer
    in Root

Expected behavior
No mismatching between server/client.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: macOS
Browser: Chrome
Version: 3.5.6

Additional context
Add any other context about the problem here.

This is a much better codesandbox showing the issue exactly how I'm experiencing it in my own app: https://codesandbox.io/s/react-query-persist-bug-4k32q
Repro instructions the same - click the buttons to shoot off some queries, refresh the page so they get saved to local storage, then open the console to see the Warning: Text content did not match. Server: "1" Client: "xxx" error.

This is a much better codesandbox showing the issue exactly how I'm experiencing it in my own app: https://codesandbox.io/s/react-query-persist-bug-4k32q
Repro instructions the same - click the buttons to shoot off some queries, refresh the page so they get saved to local storage, then open the console to see the Warning: Text content did not match. Server: "1" Client: "xxx" error.

The devtools don't really need to SSR, so we could try adding the suppressHydrationWarning prop to the highest div in the devtools?

The devtools don't really need to SSR, so we could try adding the suppressHydrationWarning prop to the highest div in the devtools?

:tada: This issue has been resolved in version 3.5.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.5.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Is there a better way than
<div suppressHydrationWarning>
  <ReactQueryDevtools />
</div>

For avoiding this SSR warning?


WIP: Added check for query execution

check added for query execution

/ok-to-test sha=3934a5e

/ok-to-test sha=3411391

/ok-to-test sha=a4b9ef9


opening gd on a backup be like: (GD crash when open)

Geode Issue

[X] I confirm that this crash is NOT related to a mod but directly to Geode Loader itself.

Platform
Windows
Geode Version
3.0.0
Mods Installed
i cant say
Steps to Reproduce
i did open
Crash Report

Additional Information
idk

note these crashes were not ai generated

i have the same issue


Different "Post settings" for each user group

In mentioned section "Post & topics / Post settings" there are settings which would be great to have adjustable based on users group.
Settings like:

Time required between posts from the same IP
Courtesy edit wait time
Maximum time after posting to allow edit

Use case: We would love to give our trusted users a bit more freedom but still keep them away from messing forum settings.
Thank you for your help.

Hi @SGOrava , thanks for the suggestion.
I see the use case and I agree.
That said, making these settings groups-based could be quite tricky, especially when it comes to mixing groups and the intent behind the group itself.
For example you could have this situation:

group 1 => normal users => wait time 10 minute
group 2 => loyal users => wait time 1 minute
group 3 => tricky users => wait time 20 minutes

If we assume the "lowest" wins then the setting for group 3 will never be used because group 1 would always win.
If we assume the "highest" wins then the setting for group 2 will never be used, again because group 1 will be the choice, unless you remove group 1 from the user.
So, in order to have something that works we'd need to delegate the overriding rules to the admin (providing also an interface to do so), and that would be not so easy. I think.

Hello emanuele45,

So, in order to have something that works we'd need to delegate the overriding rules to the admin (providing also an interface to do so)

That is how I would imagine it to work, admin could manually set the priority (number or some graphical UI) by which the rule would apply.

and that would be not so easy. I think.

I hope someone finds the time required to implement it.
Best regards.


The 'checkerboardRasterCacheImages' of 'MaterialApp' not working on master channel

The code below should show the chessboard when running, but it doesn't now.
import 'package:flutter/material.dart';

void main() {
  runApp(const MaterialApp(
    checkerboardRasterCacheImages: true,
    home: Scaffold(
      body: Example(),
    ),
  ));
}

class Example extends StatefulWidget {
  const Example({Key? key}) : super(key: key);

  @override
  State<Example> createState() => _ExampleState();
}

class _ExampleState extends State<Example> with TickerProviderStateMixin {
  late final AnimationController _controller = AnimationController(vsync: this, duration: const Duration(seconds: 1));
  late final Animation<Offset> _position = _controller.drive(
    Tween(begin: const Offset(0.0, 0.0), end: const Offset(1, 1.0)));

  @override
  void initState() {
    super.initState();
    _controller.reset();
    _controller.forward();
    _controller.addStatusListener((status) {
      if (status == AnimationStatus.completed) {
    _controller.reset();
    _controller.forward();
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    return Column(
      children: <Widget>[
        Container(height: 100),
        SlideTransition(
          position: _position,
          child: Opacity(
            opacity: 0.9,
            child: Container(
              child: Column(
                children: <Widget>[
                  Container(
                    width: 200,
                    height: 200,
                    color: Colors.red,
                    child: const Text('A'),
                  ),
                ],
              ),
            ),
          ),
        ),
      ],
    );
  }
}

The reason is that this line of code uses the wrong field.
https://github.com/flutter/engine/blob/main/flow/layers/layer_raster_cache_item.cc#L155
Here is the patch for it https://github.com/flutter/engine/pull/34424
cc @flar @JsouLiang
flutter doctor -v
[✓] Flutter (Channel master, 3.1.0-0.0.pre.1468, on macOS 12.2.1 21D62 darwin-arm (Rosetta), locale zh-Hans-CN)
    • Flutter version 3.1.0-0.0.pre.1468 on channel master at /Users/bytedance/Develop/upstream/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 1add0d790d (6 hours ago), 2022-07-01 00:39:07 -0400
    • Engine revision caec3e305a
    • Dart version 2.18.0 (build 2.18.0-242.0.dev)
    • DevTools version 2.14.1
    • Pub download mirror https://dart-pub.byted.org
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/bytedance/Library/Android/sdk
    • Platform android-32, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13F100
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

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

[✓] Connected device (3 available)
    • iPhone SE (2nd generation) (mobile) • 00008030-0018042E2E46802E • ios            • iOS 15.0 19A346
    • macOS (desktop)                     • macos                     • darwin-arm64   • macOS 12.2.1 21D62 darwin-arm (Rosetta)
    • Chrome (web)                        • chrome                    • web-javascript • Google Chrome 103.0.5060.53

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

Thanks for the report. Using code sample, I am seeing same behavior as reported on latest master.
Channel master, 3.1.0-0.0.pre.1467

fixed via linked PR


Disable foreign key checks when cleaning tables

Summary
To prevent foreign key constraint errors when executing DELETE on parent tables where child tables have foreign keys referencing them, we temporarily disable FOREIGN_KEY_CHECKS.
Other Information
Checklist

[x] By placing an "x" in the box, I hereby understand, accept and agree to be bound by the terms and conditions of the Contribution License Agreement.

Released v0.1.1


Add Aura Tracking

activeturn.php returns trap_image.auras which can be reduced using Object.keys(auras).filter( codename => auras[codename].status === 'active') to provide an array of active auras.
These can be added to the message sent to intake and recorded with the hunt. Requires backend changes laid out in https://github.com/m-h-c-t/mh-hunt-helper/issues/222

It should be acceptable to use the post message for this purpose - it is extremely unlikely the aura would have switch to/from active during the time between the hunt and the response.


WIP: Generic enum

Rough implementation, has some nice properties though not encoded as well as they could be:

calling enumValues fails if there is an invalid name (right now through an incomplete pattern match). enumValues is mostly internal so we can decide how we want to fail here. Should tie in with general validation.
Checks for unary constructors and doesn't compile if it's not. (Try instance GraphQLEnum A)

Two examples:
``haskell
instance GraphQLEnum B
data B = B1 | B2 | B3 deriving (Generic, Show)
data A = A1 | A2 Text | A3 deriving (Generic, Show)

Thanks! I'll merge but will keep in mind that we need to fix enumValues.


Feature/archetype client rest put

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


Application.Tests missing validation ?

Hi,
If in test related for Customer Creation I setup CustomerId as empty string test still pass, even if CustomerValidationExist. So shell you include in tests Validation or in handler better and just throw an validationexception ?

Thank you for your interest in this project. This repository has been archived and is no longer actively maintained or supported. We appreciate your understanding. Feel free to explore the codebase and adapt it to your own needs if it serves as a useful reference. If you have any further questions or concerns, please refer to the README for more information.


Updating Stride for Unity Developers documentation

I am personally one of those Unity developers that this documentation is for and when I saw the screenshots of the Unity Editor layout I laughed because it has been years since I saw a Unity Editor look like that.
So I started out by redoing the screenshots of both Stride and Unity and updated them so they looked better on dark theme.
Turns out, Stride looks a lot more like the default Unity Editor layout than the old screenshots would have betrayed.
Then I went on and updated some of the things I noticed where inaccurate in the markdown.
Before

After

Your images look very good. What tool did you use. Would you be ok to change them to .webp, if it decreases the file size of the image and you are also ok with the image quality result?
@Eideren, could you please review. I like the update very much, especially because of the styling and formatting improvements but I can't review the content.

I made them in Microsoft PowerPoint, which I do have a commercial license for.
Also added a Godot one because I know we have a page for Godot developers under construction <3

If you would like, you can finish the Godot one. I believe @IXLLEGACYIXL will be ok with that. He prepared the content https://github.com/stride3d/stride-docs/issues/128 and then I started adding it to the new page https://github.com/stride3d/stride-docs/blob/master/en/manual/stride-for-godot-developers/index.md as he is not familiar with markup and docs as I am. But I am not familiar with Godot and game dev generally 🤣🙈.
And then Eideren made additional updates and now also you.
I would suggest just to copy this page (once merged) https://github.com/stride3d/stride-docs/blob/master/en/manual/stride-for-unity-developers/index.md and update accordingly based on the files above, including adding or removing the sections.

I am ok to merge this.

If you would like, you can finish the Godot one. I believe @IXLLEGACYIXL will be ok with that. He prepared the content https://github.com/stride3d/stride-docs/issues/128 and then I started adding it to the new page https://github.com/stride3d/stride-docs/blob/master/en/manual/stride-for-godot-developers/index.md as he is not familiar with markup and docs as I am. But I am not familiar with Godot and game dev generally 🤣🙈.
And then Eideren made additional updates and now also you.
I would suggest just to copy this page (once merged) https://github.com/stride3d/stride-docs/blob/master/en/manual/stride-for-unity-developers/index.md and update accordingly based on the files above, including adding or removing the sections.

im fine if someone else wants to make the godot to stride


Unintended Error in case of file write error

If the file is not writeable, an unintended Error message throw er; // Unhandled 'error' event is printed on console.
I can handle this error when setting a "error" handler on stream.theStream. I would prefer to set an error handler on stream instead of manipulation an inner property (theStream). I have also seen, that writing to this "invalid" stream ist possible without errors. But the written string never finds the way into the file (which is not writeable).
What's the intended error handling? Why you can call write to an unwriteable file without any errors?

That's not something I've ever tested, to be honest, which explains why it's not doing what you expect. I'll take a look and see if I can come up with something sensible.

Published to npm in v0.2.2 - you can now add an error handler to the streamroller stream.


Fix "A request has failed" dialog that can not be dismissed

Take into account the user choice and only open the output channel if
user has clicked "Go to output".
Fixes #786

Thanks!


Make contract version mandatory in checkpoint file

We have added a contract version to every checkpoint file in
app-interface. We can now make it mandatory
Part of APPSRE-4788
Signed-off-by: Rafael Porres Molina<EMAIL_ADDRESS>

To be merged/applied after - https://gitlab.cee.redhat.com/service/app-interface/-/merge_requests/37839
This is a breaking change


Update scala-library to 2.13.8

Updates org.scala-lang:scala-library from 2.13.7 to 2.13.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #207 (c5c4fb6) into main (3744d17) will decrease coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #207      +/-   ##
==========================================
- Coverage   59.65%   59.44%   -0.22%
==========================================
  Files         157      157
  Lines        3252     3252
  Branches       90       90
==========================================
- Hits         1940     1933       -7
- Misses       1312     1319       +7

Impacted Files
Coverage Δ

.../surge/kafka/streams/KafkaStreamManagerActor.scala
57.14% <0.00%> (-10.39%)
:arrow_down:

...StreamsUpdatePartitionsOnStateChangeListener.scala
82.85% <0.00%> (-8.58%)
:arrow_down:

...a/surge/kafka/KafkaPartitionShardRouterActor.scala
58.38% <0.00%> (-0.68%)
:arrow_down:

.../surge/internal/kafka/KafkaProducerActorImpl.scala
79.56% <0.00%> (+1.07%)
:arrow_up:

...health/windows/actor/HealthSignalWindowActor.scala
93.98% <0.00%> (+1.50%)
: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 3744d17...c5c4fb6. Read the comment docs.


[cluster utilization] get the full list of jobs in 7 days

Sorting by completionTime is supported in #5375, we can thus get the whole list of jobs within 7 days

Coverage remained the same at 34.07% when pulling 9ff9d33f8cb040b0df961b70e2ffde6c46585dff on suiguoxin:job-list into 9be9ea68627a4104f973b2706034877cd5ddf21c on microsoft:master.

Can you link the rest-server change?

Can you link the rest-server change?

Can you link the rest-server change?

The changes is implemented in #5375. The new API can be previewed here


⚠ Bofrost.es has degraded performance

In d9d674a, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1689 ms

Resolved: Bofrost.es performance has improved in 1ef1b69 after 6 minutes.


fix issue #9 list gets corrupted when backspace delete selected item …

fix issue #9 list gets corrupted when backspace delete selected item from typeahead input

Thank you @j1ch.  Merging into master.