Added small timing test to test_integrators.py, just to compare execu…

Just a small check, not shown by default, of the execution time of "local peak integration" vs. "next-neighbor peak integration" (the latter is currently very slow). The test just uses time.time(), I could not manage to use timeit to test just the integration part, without all the needed preparations like subtracting pedestals or reading in the camera geometry.

Apparently the test functions  cannot be run with python (instead of py.test), it complains about relative imports.
Also: I think it would be good to have some speed tests of specific functions included in the standard, automatic tests - is this possible?  I mean, instead of just running the profiler  manually.

There is a relative import in line 7, which should be replace by from ctapipe.calib.camera import ...
There is a py.test benchmark extension:
https://pypi.python.org/pypi/pytest-benchmark
Which we could used, but I never tried it.

python -m cProfile -o output.txt script.py
Ok, it works once the relative import is replaced, but the "-o" output is not plain text. If instead I redirect the stdout to a file, then I can read it, but it is a 4700 lines file, in which there is no reference to the functions I am interested in. Hence I think this does not replace the simple test I wanted to have - its goal being to allow me to quickly check the effect of modifications of the next-neighbor-peak search algorithm on its speed.

Ah, sorry. Yes. The output is binary. You can look at it using the pstats module.
E. g.
import pstats

stats = pstats.Stats('<filename>')
stats.sort_stats('cumulative').print_stats()

The issue with astropy_helpers should be gone (I reverted the commit, though I do not understand how could it happen in the first place). About pstats, it gives the same output that goes to stdout if the -o switch is not used, and as I said, it does not seem to be of much help for the simple comparison of the execution speed of two different pulse integrators.

About the astropy_helpers problem:
it seems after the change you did yesterday in astropy_helpers,  I should have done a "make develop" to get it updated (git pull did not do it because it is a Submodule I think). Instead, I did a "git add" which added astropy_helpers to the subsequent commit.
Now I no longer get the message about "new commits" in astropy_helpers when I do git_status.

Ah, yes. You have to do git submodule update (which is also done by make init and thus by make develop)
To be safe, do not do git add ., add the single files. And do not add the git submodules as long as you do  not wish to change the version of the submodules.

@moralejo I am working to improve the speed of the neighbour_peak_integration scheme at the moment. I have already developed a faster neighbour_peak_integration() in calib.camera.charge_extractor.NeighbourPeakIntegration(container) #219 (which I am still developing).
I also intend to only obtain the neighbours instead of the whole camera geometry in the new version, which should greatly improve the speed.


Cannot copy Text from a Code Block

Summary
Cannot copy text from a rendered code block.
Environment Information

Mattermost App Version: 2.9.0 (Build 48903) from F-Droid
Mattermost Server Version: 9.0.0

Steps to reproduce

Send a formatted message like this.```nim
echo "Hello World"
```

Open the message & this code block.
You cannot copy its text.

Expected behavior
I can copy the code.
Observed behavior (that appears unintentional)
Cannot copy the code.
Possible fixes
Make it copyable or at least add a Copy button in the top right corner, just as in the Web UI.

You ahould be able to copy the entire code block by long oressing instead of pressing

You ahould be able to copy the entire code block by long oressing instead of pressing

Okay, now I get it.
I was always opening the code, reading it, then tried to copy it. Never worked. Not even with long press. Just tested again, right now, with the same problem.
Long press only works on the not yet opened code block.
Might this be implemented into the code view, when viewing it full screen?

+1, this is also a problem I frequently run into. I often get shown a code block and I want to copy a part to edit and reply but not being able to select makes it very tricky to manage because then I need to copy the whole message and remove everything around it instead. Very tedious.

@amyblais could this get triaged? I think it's not "Awaiting Submitter Action".

Opened https://mattermost.atlassian.net/browse/MM-56802.


Issue with the OpenAI Moderation Servers

Device and Browser Information
Device: Macbook
OS: MacOS 14.2
Browser: All browser encounters the same issue
Describe the bug
I always met with the following issue and could not get any response when using big-AGI:
There was an error while checking for harmful content. TRPCClientError: Error: [Issue] OpenAI/openai: Service Unavailable (503) - 当前分组 default 下对于模型 text-moderation-latest 无可用渠道
But there's no problem when applying the api with python, are there any solution to this problem?
Screenshots and Additional Context
No response
Willingness to Contribute

[ ] 🙋♂ Yes, I would like to contribute a fix.

Hi @lincolnlyj - the "moderation" API is giving an error, but can be disabled by the UI. It's used to check for harmful content.
The issue is that the OpenAI service is unavailable on the "text-moderation-latest" model. OpenAI Server Issue. Please just disable the Moderation API while the issue persists.
Disabling Moderation API

Go to Preferences > Models > OpenAI > Advanced
Turn off the "Moderation" button

It's solved, thanks a lot for your help


Tikzplotlib error on 3D surface plot

Problem Description
Trying to plot a simple 3D surface plot and then save the results with tikzplotlib throws an error.
Minimum working example:
from matplotlib import pyplot as plt
import tikzplotlib
import numpy as np

X, Y = np.meshgrid(np.linspace(0, 1), np.linspace(0, 1))

fig, ax = plt.subplots(subplot_kw={"projection": "3d"})
ax.plot_surface(X, Y, X + Y)

tikzplotlib.save("C:/Users/User/Downloads/rosen.tex")

plt.show()

Results in an AttributeError thown by tikzplotlib:
Traceback (most recent call last):
  File "C:\Users\User\anaconda3\lib\site-packages\IPython\core\interactiveshell.py", line 3437, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-2-c3ca481ad9a6>", line 1, in <module>
    runfile('C:/Users/User/AppData/Roaming/JetBrains/PyCharm2021.1/scratches/scratch_35.py', wdir='C:/Users/User/AppData/Roaming/JetBrains/PyCharm2021.1/scratches')
  File "C:\Program Files\JetBrains\PyCharm 2020.1\plugins\python\helpers\pydev\_pydev_bundle\pydev_umd.py", line 197, in runfile
    pydev_imports.execfile(filename, global_vars, local_vars)  # execute the script
  File "C:\Program Files\JetBrains\PyCharm 2020.1\plugins\python\helpers\pydev\_pydev_imps\_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "C:/Users/User/AppData/Roaming/JetBrains/PyCharm2021.1/scratches/scratch_35.py", line 11, in <module>
    tikzplotlib.save("C:/Users/User/Downloads/rosen.tex")
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_save.py", line 260, in save
    code = get_tikz_code(*args, filepath=filepath, **kwargs)
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_save.py", line 209, in get_tikz_code
    data, content = _recurse(data, figure)
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_save.py", line 353, in _recurse
    data, children_content = _recurse(data, child)
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_save.py", line 378, in _recurse
    data, cont = _draw_collection(data, child)
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_save.py", line 325, in _draw_collection
    return _patch.draw_patchcollection(data, child)
  File "C:\Users\User\anaconda3\lib\site-packages\tikzplotlib\_patch.py", line 81, in draw_patchcollection
    ecs = ensure_list(obj.get_edgecolor())
  File "C:\Users\User\AppData\Roaming\Python\Python38\site-packages\mpl_toolkits\mplot3d\art3d.py", line 883, in get_edgecolor
    return self._edgecolors2d
AttributeError: 'Poly3DCollection' object has no attribute '_edgecolors2d'

The associated figure:

Version Info

Windows 10
Python 3.8.8, Anaconda install
Tikzplotlib 0.9.8 (latest)
Matplotlib 3.4.1 (latest)

Duplicate of https://github.com/nschloe/tikzplotlib/issues/119.

UPDATE:
Following another issue here https://github.com/nschloe/tikzplotlib/issues/416, I tried adding a plt.savefig() before the tikzplotlib.save(). Now, when I run it, no AttributeError is produced and the .tex file is created.
Specifically, the input looks like:
from matplotlib import pyplot as plt
import tikzplotlib
import numpy as np

X, Y = np.meshgrid(np.linspace(0, 1), np.linspace(0, 1))

fig, ax = plt.subplots(subplot_kw={"projection": "3d"})
ax.plot_surface(X, Y, X + Y)

plt.savefig("C:/Users/User/Downloads/rosen.png")  # THIS IS THE NEW LINE ADDED
tikzplotlib.save("C:/Users/User/Downloads/rosen.tex")

plt.show()

@nschloe Are we sure that this is a matplotlib issue and that this issue should be closed? Seems strange that a plt.savefig would change tikzplotlib behavior.

Wait, it works and produces the correct result for you? A 3D plot?


podman: output of ps with a conatiner publishing 1000 ports is sub-optimal

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
Description
If I publish many ports, the output of docker ps gets unreadable.
Steps to reproduce the issue:

podman run -it -p 1000-2000:1000-2000 --rm --name manyports centos /bin/bash

podman ps

Describe the results you received:
The output contains information about every port for both protocols.
Describe the results you expected:
I guess the same information which is used to start the container would be enough - 1000-2000:1000-2000.
Additional information you deem important (e.g. issue happens only occasionally):
issue happens always
Output of podman version:
Version:       0.8.3
Go Version:    go1.10.3
OS/Arch:       linux/amd64

Output of podman info:
host:
  Conmon:
    package: podman-0.8.3-1.git9d09a4d.fc28.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 1.12.0-dev, commit: c72f69ce3f3fd7e46dced78dd99b67ab5441441e-dirty'
  MemFree:<PHONE_NUMBER>6
  MemTotal:<PHONE_NUMBER>4
  OCIRuntime:
    package: runc-1.0.0-50.dev.git20aff4f.fc28.x86_64
    path: /usr/bin/runc
    version: 'runc version spec: 1.0.0'
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 4
  hostname: brql33992173a
  kernel: 4.17.18-200.fc28.x86_64
  os: linux
  uptime: 34m 5.58s
insecure registries:
  registries: []
registries:
  registries:
  - docker.io
  - registry.fedoraproject.org
  - quay.io
  - registry.access.redhat.com
  - registry.centos.org
store:
  ContainerStore:
    number: 1
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mountopt=nodev
  - overlay.override_kernel_check=true
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
  ImageStore:
    number: 1
  RunRoot: /var/run/containers/storage

Additional environment details (AWS, VirtualBox, physical, etc.):
physical Fedora 28

@baude PTAL

This still seems to be an issue. I am going lilo through our issue, sorry to be noisy today. @baude, do you find time to work on this or shall we re-assign?

I'm working on a fix on and off (other urgent things keep intruding)
On Mon, Nov 19, 2018, 08:17 Valentin Rothberg<EMAIL_ADDRESS>wrote:

This still seems to be an issue. I am going lilo through our issue, sorry
to be noisy today. @baude https://github.com/baude, do you find time to
work on this or shall we re-assign?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/containers/libpod/issues/1358#issuecomment-439889359,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHYHCNXs9f-DHl97e0R_H1RYI1pXR52Wks5uwq9_gaJpZM4WO6KP
.

@mheon Are you still working on this?

@rhatdan Yes, hope to get to it sometime during January

@mheon Any updates?

This is a solid week of work to get right due to the need for DB changes. I'd like to get it resolved, but it's lower priority than... most other things?

This need parsing ports and formatting like
<snip>   centos    "/bin/bash"  <snip>    <IP_ADDRESS>:1000-2000->1000-2000/tcp   manyports

@mheon, I can work on this, If you are busy.

Awesome @kunalkushwaha Thanks

@rhatdan Thank you for the invitation :)

Were glad to add you to the contributors.

And now I can assign you to issues.  :^)

This issue is fixed with https://github.com/containers/libpod/pull/2664 & https://github.com/containers/libpod/pull/2685.
Hence closing the issue.


error：cmake .

S:\phoenix\phoenix>cmake .
-- Selecting Windows SDK version 10.0.19041.0 to target Windows 10.0.19045.
-- Microsoft SEAL -> Version 3.6.6 detected
-- Microsoft SEAL -> Targets available: SEAL::seal
CMake Error at CMakeLists.txt:11 (find_package):
By not providing "Findhcephes.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "hcephes", but
CMake did not find one.
Could not find a package configuration file provided by "hcephes" with any
of the following names:
hcephesConfig.cmake
hcephes-config.cmake

Add the installation prefix of "hcephes" to CMAKE_PREFIX_PATH or set
"hcephes_DIR" to a directory containing one of the above files.  If
"hcephes" provides a separate development package or SDK, be sure it has
been installed.
-- Configuring incomplete, errors occurred!
See also "S:/phoenix/phoenix/CMakeFiles/CMakeOutput.log".
See also "S:/phoenix/phoenix/CMakeFiles/CMakeError.log".

I have the same error

My solution：

Open CMakeLists.txt

Add  set(hcephes_DIR /home/rain/anaconda3/envs/phoenix_env/lib/cmake/hcephes)
before  find_package(hcephes REQUIRED)

You should find your own path.

It seems that you have had some success in running the Phoenix program. I'm currently working on the same and have encountered a few difficulties. I'm convinced that your insights and experience could be instrumental in helping me navigate through some of these technical challenges.
If it's not too much to ask, I'd appreciate the opportunity to discuss these matters with you in detail. We could delve into specific aspects of the project and possibly exchange ideas on various technical implementations, which I believe could be mutually beneficial.
Please feel free to reach out to me at your convenience at<EMAIL_ADDRESS>Thank you for your time and consideration. I look forward to possibly collaborating with you on this project.

My solution：

Open CMakeLists.txt
Add  set(hcephes_DIR /home/rain/anaconda3/envs/phoenix_env/lib/cmake/hcephes)
before  find_package(hcephes REQUIRED)

You should find your own path.

My solution：

Open CMakeLists.txt
Add  set(hcephes_DIR /home/rain/anaconda3/envs/phoenix_env/lib/cmake/hcephes)
before  find_package(hcephes REQUIRED)

You should find your own path.

@pshizheng, it seems that you have had some success in running the Phoenix program. I'm currently working on the same and have encountered a few difficulties. I'm convinced that your insights and experience could be instrumental in helping me navigate through some of these technical challenges.
If it's not too much to ask, I'd appreciate the opportunity to discuss these matters with you in detail. We could delve into specific aspects of the project and possibly exchange ideas on various technical implementations, which I believe could be mutually beneficial.
Please feel free to reach out to me at your convenience at<EMAIL_ADDRESS>Thank you for your time and consideration. I look forward to possibly collaborating with you on this project.


Event information

Gabriel,
Is it possible to get the event information directly through the evenEmitter (in isIdle() / isActive())? Currently, I am trying to switch to the active state on keyup (which works) however because IdleVue also listens for this event I get double events every time I keyup is emitted.

Hey, sorry for missing out the question. Could you give an example usage ?here : https://codesandbox.io/s/vue

@hugohil any thoughts on this ?

No example and no more news. closing for now.

Hi gabriel,
I have this need as well, and I could use some help.
In my case, I have a form.
I use idle-vue in order to lazy tabs in the form (I use a bootstrap-collapse).
Nevertheless, I use idle-vue in order to autosave the form.
Currently, the autosave is initiated every time the user is idle.
If I can use event (as in hook onIdle(event) for instance), I can inspect the event and check if it is a typing event, etc.
That way, I could differentiate when the user changes anything in the form (and initiate autosave only then).
I thought of using a variable that changes when @keypress event is fired, but some of my forms are recursive and it's impossible to track all changes..
Thanks in advance! 👍

hello !
Could you share part of your code ? A simple example. I understand the use case but I do not get how idle-vue could help. thanks

Trying to make it briefly, here it comes:
HTML:
<div>
    <template v-for="tab in form">
        <template v-if="tab.fields !== undefined">
            <b-card>
                <b-card-header>
                    {{ tab.title }}
                </b-card-header>
                <b-collapse>
                    <b-card-body>
                        <recursive-tabs :props="props" /> <!-- Recursive call to myself -->
                    </b-card-body>
                </b-collapse>
            </b-card>
        </template>

        <template v-else>
            <b-row>
                <b-col>
                    {{ tab.Name }}
                </b-col>
                <b-col>
                    <input type="text" :value="tab.value">
                </b-col>
            </b-row>
        </template>
    </template>
</div>

JS:
export default {
  name: "recursive-tabs",

  // requested help here! I did it with hooks but can work great with computed too;
  // see comment under computed
  onIdle() {
    if (this.mouseWasActive === true) { this.DoSomeWorkWhileIdle(); }
    if (this.formdataWasChanged === true) { this.Autosave(); }
  }
  onActive(event) {
    if (event.type === "mousemove") {
      this.mouseWasActive = true;
    }
    if (event.type === "keypress") {
      this.formdataWasChanged = true;
    }
  }

  props: [...],
  data(){
    return {
      mouseWasActive: false,
      formdataWasChanged : false,
      ...
    }
  },
  computed: {
  // example of using event in computed idle
  //  DoAutoSaveIfIdle() {
  //    if (this.isAppIdle !== undefined) {
  //      if (this.isAppIdle.type === "keypress") {
  //        this.formdataWasChanged = true;
  //      }
  //    }
  //  }
  }
}

Please notice that in the optional commented computed-property (isAppIdle), I gave an alternative to its value - so that it's undefined if not idle (or if options object has no store field of course), or equals to the event.type if idle (instead of just true or false or undefined).


Rename tests, extensions and configs

Describe your changes
Refer to #724

Search "adxe" (0 hits in 0 files of 7993 searched) done! there are no occurrences of adxe in the entire engine folder

Please prefer follow setp for any PRs yo avoid unexpect behavior, once new branch created, don't use merge from your branch migrate-engine-name, just copy modified files from it into new branch.
# Goto your local repo dir
cd axis
# add a remote name `official`
git remote add official https://github.com/axis-project/axis.git
# fetch remote `official`
git fetch official
# create new branch named `my-feature` from branch `official/dev`
git checkout -b my-feature official/dev

# do your modifications in branch `my-feature`

# commit and push your modifications branch my-feature to your own github repo
git add . && git commit -m "Example commit message"
git push origin my-feature

# Then you can goto upstream github webpage to create the PR with your plain branch `my-feature`

But you can merge it right? don't worry I just accidentally merged in the wrong branch and undoing this is pain

Close as #739


Use graphql query can not get cliams

Bug description
when i use @fromClaim(name: USERID) to get userid in graphql quey, it return null
How to reproduce

config auth0

2: config datasource

3: config operation

# to create user
mutation MyQuery($id: String @fromClaim(name: USERID), $createdAt: DateTime @injectCurrentDateTime, $email: String @fromClaim(name: EMAIL)) {
  mysql_createOneUser(data: {id: $id, createdAt: $createdAt, email: $email}) {
    id
    email
    createdAt
  }
}

4: i use http method can get userid

5: i user graphql can not get userid

Expected behavior
No response
WunderGraph information

Environment & setup

OS:
Go version:
Database:
Node.js version:

WunderCtl Version
commit:193b974eb415d80837b8f752c00f257a61f5db2e

use graphql can not get claims

The GraphQL endpoint is only exposed to explore the GraphQL schema. Features like injectClaims can only be used safely in the RPC layer, so we've never implemented them in the GraphQL handler.
Can you explain why it's needed in the GraphQL handler? Are you exposing the GraphQL API or the RPC API?

in my biz logic, i do not want to use api, i want exposing the grahoQL and use graphql query directly

in my biz logic, i do not want to use api, i want exposing the grahoQL and use graphql query directly

Do you use the GraphQL API from the frontend or from another service?

from the frontend

in my biz logic, i do not want to use api, i want exposing the grahoQL and use graphql query directly

Do you use the GraphQL API from the frontend or from another service?

So, do you will support cliams in Graphql query.

It's currently not planned to support injecting claims or similar features into GraphQL queries directly. This only works through the RPC layer.


[KeyVault] - Enable multi-version tests for KV certificates

What

Add support for multi-version testing for keyvault-certificates

Why
Our commitment is to support the last N versions of the KeyVault service. To ensure neither we nor the service introduce breaking changes to prior versions, multi-version test support was added. We ported keys over and have already reaped the benefits of version based filtering.
This commit adds the same support for keyvault-certificates
Resolves #17890

/azp run js - keyvault-certificates - tests

/azp run js - keyvault-certificates - tests


How to modify the convolution property to same.

I converted onnx to h5, but found that the padding property in the convolution is valid, how to modify the property to same. Whether this property affects the speed when post quantized model runs on the SnapDragon 855 DSP.

You can do this by modifying the mode of Conv Op in def convert_conv of this tool.

I have not tested the performance of this modification, I am looking forward to hearing your test result whether it does improve the speed.


Added Occlusion culling to the frustum culling script

Some missing or dangling .meta found. Fix commits are needed.

Status
File

Not removed
Assets/Scenes/Testing/FrustumCulling.meta

Some missing or dangling .meta found. Fix commits are needed.

Status
File

Not removed
Assets/Scenes/Testing/FrustumCulling.meta

Some missing or dangling .meta found. Fix commits are needed.

Status
File

Not removed
Assets/Scenes/Testing/FrustumCulling.meta

Some missing or dangling .meta found. Fix commits are needed.
Status	File
Not removed	Assets/Scenes/Testing/FrustumCulling.meta

De bot heeft het fout. Klopt gewoon.

Some missing or dangling .meta found. Fix commits are needed.

Status
File

Not removed
Assets/Scenes/Testing/FrustumCulling.meta


componentDidUnmount not getting called

🐛 Bug Report

To Reproduce

Expected Behavior

Code Example

Environment

@mehtanishant2010 componentDidUnmount is not part of the component lifecycle methods.
You have to use componentWillUnmount

Hey @mehtanishant2010 please could you add more information on any further issues; it's helpful for maintainers and helps triage issues quicker.
Also please see @AntoineDoubovetzky response.
Thanks


Use new-style config mechanism for the scheduler

Also removed _create_scheduler

It's pretty annoying how inconsistent the configuration options are. Some use dashes, some use underscores.
I think we should move to use underscores consistently. With #726 we will throw a deprecation warning if config_path is actually being used. We can probably remove config_path sometimes next year :)

LGTM


Add availability check to ease importing code in projects with lower …

…deployment targets

@rivera-ernesto
Thanks for the PR!
Merge to master!


Add "Thank you page" after order is sent to the server

Do we have designs for that?

Under construction, however, it will be a very simple one, based on the design of static page:

@filrak we have to have this thank you page after order is placed

For now there is a simple thank you page on checkout, @karolbzik if that's ok for now please close the issue


Update README.md

Given this PR has been merged, I think 3.1.x is supported now? The readme still said 3.0.x
https://github.com/thephpleague/openapi-psr7-validator/issues/163
https://github.com/thephpleague/openapi-psr7-validator/pull/185

Probably want to make it clear it supports both 3.0.x and 3.1.0 instead of less than 3.1.X since I don't think that version 2 is supported by this tool? (But I might be mistaken)

Sure thing, changed it, never saw your comment.


Drop [Main] from snippet references

[Main] was apparently copied early from DocFX markdown doc examples and habitually persisted. Since they aren't usually accurate or helpful, I just did a quick find-and-replace to knock them out.
I scanned all of these, and they look fine ... but get the eye drops out again! 👁

This PR is sponsored by Visine eye drops 😄

This removes the link to the code within GitHub. Not sure if this was intended/acceptable.

@ovation22

This removes the link to the code within GitHub.

Not sure what u mean ... can you elaborate?

When navigating the Docs/MD in GitHub the [Main] appears as a link to the code. Removing Main removes the link when navigating the MD in GitHub. This isn't a concern if navigating the Docs from the main site, but removes the ability to easily navigate to the code in question with the link removed. This causes a slight issue as the code isn't displayed when viewing the MD in GitHub, but not an issue when viewing the Docs from the main site.
GitHub:
https://github.com/aspnet/Docs/blob/master/aspnetcore/fundamentals/dependency-injection.md
[!code-csharp] <-- used to have a link
GitHub History:
https://github.com/aspnet/Docs/blob/a4aa4ebb98e5788bf78254e4f4a1b518a1f2454f/aspnetcore/fundamentals/dependency-injection.md
[!code-csharpMain] <-- link to code
Docs:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection
Not sure it's an issue, was discussed, or even noticed before.

@ovation22 Thanks for explaining. We anticipate that the vast majority of doc consumers will browse the built pages. The lack of snippet rendering (and now linking) isn't the only issue: All of the relative links, all of the API links, and at least some of the xref doc cross-links are also broken. There's no handy TOC. The unstyled markdown is rough on the :eye: :smile:. It's just never going to be a good general experience.
@scottaddie @Rick-Anderson I'm not too concerned about it; but since it's your show and you might be, an OPS solution might be possible before we go with something like [LINK], [See snippet], or something along those lines. I mean if you have a concern about it ... personally, I wouldn't sweat it.


Accessing the JSON String from inside an Kafka Engine

I have a table of Engine=Kafka(), and the kafka_format = 'JSONEachRow'. Is there a way to access the JSON String from inside the table definition:
create table kafka_ingest (
jsonString  String, (This is the JSON value that we are trying to ingest)
jsonField1 String,
jsonField2 UInt64
) Engine=kafka()
Settings kafka_broker_list = '......' , kafka_format='JSONEachRow'
Thanks a lot for your help

I'm not sure that is, but you can try to use another kafka_format, eg TSV if there no tabs in data,  and extract fields using JSON functions.
create table kafka_ingest (
jsonString String,
jsonField1 String DEFAULT JSONExtractString(jsonString, 'field1'),
jsonField2 UInt64 DEFAULT JSONExtractUInt(jsonString, 'field2')
) Engine=kafka()
Settings kafka_broker_list = '......' , kafka_format='TSV'

Thank you so much, appreciate much your help. I will try and update this thread.

Hi,
If somebody wants to do the same thing, suggestion from @millin works pretty well, just need to also add the kafka_row_delimiter='\n' parameter:
create table kafka_ingest (
jsonString String,
jsonField1 String DEFAULT JSONExtractString(jsonString, 'field1'),
jsonField2 UInt64 DEFAULT JSONExtractUInt(jsonString, 'field2')
) Engine=kafka()
Settings kafka_broker_list = '......' , kafka_format='TSV', kafka_row_delimiter='\n'

@StephenSorriaux hi, I use the same Settings but saw the following error.
DB::Exception: Cannot parse input: expected \t at end of stream.: (at row 1)
have you seen it?


 Switching to simpler (but slower) update.

Merging now. Want to get this in today for people to test with.


#27 Stabilize code of Web forms services: finish implementation and w…

…rite tests

@rultor merge

@rultor merge

@proshin-roman OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@proshin-roman Done! FYI, the full log is here (took me 2min)


Support Request: Curtain not moving

Describe Your Problem
The curtain device is not moving and also closed in HomeKit
Relevant log output
[30/12/2022, 14:38:31] [SwitchBot] [DEBUG] Curtain: Curtain No Changes, Set TargetPosition: 100
[30/12/2022, 14:38:31] [SwitchBot] [DEBUG] Curtain: Curtain value: 100, CurrentPosition: 0
[30/12/2022, 14:38:31] [SwitchBot] [DEBUG] Curtain: Curtain updateRate: 5
[30/12/2022, 14:38:34] [SwitchBot] [DEBUG] Curtain: Curtain Refresh Status When Moving, PositionState: 1
[30/12/2022, 14:38:34] [SwitchBot] [DEBUG] Curtain: Curtain openAPIRefreshStatus
[30/12/2022, 14:38:34] [SwitchBot] [DEBUG] Curtain: Curtain sign: ****************************************
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain statusCode: 200
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain d: {"statusCode":100,"body":{"deviceId":"***********","deviceType":"Curtain","hubDeviceId":"***********","calibrate":true,"group":false,"moving":false,"slidePosition":100},"message":"success"}
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain refreshStatus: {"statusCode":100,"body":{"deviceId":"************","deviceType":"Curtain","hubDeviceId":"**********","calibrate":true,"group":false,"moving":false,"slidePosition":100},"message":"success"}
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain openAPIparseStatus
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain Curtain CurrentPosition: 0
[30/12/2022, 14:38:35] [SwitchBot] Curtain: Curtain Checking Status ...
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain Standby, CurrentPosition: 0
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain Stopped
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain CurrentPosition: 0, TargetPosition: 0, PositionState: 2,
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain updateCharacteristic CurrentPosition: 0
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain updateCharacteristic PositionState: 2
[30/12/2022, 14:38:35] [SwitchBot] [DEBUG] Curtain: Curtain updateCharacteristic TargetPosition: 0
[30/12/2022, 14:38:36] [SwitchBot] [DEBUG] Curtain: Curtain setNewTarget true timeout
[30/12/2022, 14:38:36] [SwitchBot] [DEBUG] Curtain: Curtain OpenAPI pushChanges
[30/12/2022, 14:38:36] [SwitchBot] [DEBUG] Curtain: Curtain No OpenAPI Changes, CurrentPosition & TargetPosition Are the Same. CurrentPosition: 0, TargetPosition  0

Config for homebridge-switchbot
{
            "name": "SwitchBot",
            "credentials": {
                "token": "*******************************************************************",
                "secret": "**********************************+",
                "notice": "Keep your token a secret!"
            },
            "options": {
                "devices": [
                    {
                        "deviceId": "**************",
                        "configDeviceName": "Curtain 2",
                        "hide_device": true,
                        "configDeviceType": "Curtain",
                        "curtain": {
                            "set_minStep": 1,
                            "set_min": 10,
                            "set_max": 90,
                            "updateRate": 1,
                            "hide_lightsensor": true
                        },
                        "logging": "debug"
                    },
                    {
                        "deviceId": "***************",
                        "configDeviceName": "Bot FA Bot",
                        "configDeviceType": "Bot",
                        "bot": {
                            "mode": "press",
                            "deviceType": "switch",
                            "allowPush": false,
                            "doublePress": 1
                        },
                        "logging": "standard"
                    },
                    {
                        "deviceId": "***************",
                        "configDeviceName": "Curtain",
                        "configDeviceType": "Curtain",
                        "connectionType": "OpenAPI",
                        "curtain": {
                            "set_min": 10,
                            "set_max": 90,
                            "updateRate": 5,
                            "setOpenMode": "0",
                            "setCloseMode": "1",
                            "hide_lightsensor": true
                        },
                        "history": false,
                        "refreshRate": 360,
                        "logging": "debug"
                    }
                ],
                "irdevices": [
                    {
                        "deviceId": "*******************",
                        "configRemoteType": "Light",
                        "logging": "debug"
                    }
                ],
                "refreshRate": 360,
                "pushRate": 5,
                "logging": "debug"
            },
            "platform": "SwitchBot"
        }

Screenshots
The curtain is not moving after trigger via HomeKit. According to the logs the API calls are successful, but one line was interesting: [30/12/2022, 14:38:36] [SwitchBot] [DEBUG] Curtain: Curtain No OpenAPI Changes, CurrentPosition & TargetPosition Are the Same. CurrentPosition: 0, TargetPosition  0
It seems to me that the plugin isn't even considering to move the curtain. What does this mean and is this in connection to the problem that the curtain is not moving?
The curtain can be controlled without any problem from the SwitchBot App, and the state is correctly displayed there.
But the logs inside the SwitchBot App don't show any actions from today (Dec. 30)

Device & Model
SwitchBot: Curtain, Firmware V3.9
Node.js Version
v14.21.2
NPM Version
v6.14.17
Homebridge Version
v1.6.0
Homebridge SwitchBot Plugin Version
v2.4.0
Homebridge Config UI X Plugin Version
v4.50.2
Operating System
Raspbian GNU/Linux Buster (10)

Can you try the latest beta:

Click here to find out how to install Beta
and set the config for your curtain to Disable Caching? Then push a change and post the logs.

I tested on the latest beta with disabled caching, after restart Homebridge the first action is working (open or close). After that the device state remains a very long time, but a restart of Homebridge updates the state immediately. At the timepoint where the correct state is updated it is working again.
},
"options": {
"devices": [
{
"deviceId": "",
"configDeviceName": "Curtain",
"hide_device": true,
"configDeviceType": "Curtain",
"connectionType": "OpenAPI",
"curtain": {
"set_minStep": 1,
"set_min": 10,
"set_max": 90,
"updateRate": 1,
"hide_lightsensor": true
},
"logging": "debug"
},
{
"deviceId": "",
"configDeviceName": "Bot FA Bot",
"configDeviceType": "Bot",
"bot": {
"mode": "press",
"deviceType": "switch",
"allowPush": false,
"doublePress": 1
},
"logging": "standard"
},
{
"deviceId": "",
"configDeviceName": "Curtain 2",
"configDeviceType": "Curtain",
"connectionType": "OpenAPI",
"curtain": {
"set_minStep": 0,
"set_min": 10,
"set_max": 90,
"updateRate": 30,
"setOpenMode": "0",
"setCloseMode": "0",
"hide_lightsensor": true
},
"disableCaching": true,
"history": false,
"refreshRate": 360,
"logging": "debug"
}
],
"irdevices": [
{
"deviceId": "",
"configRemoteType": "Light",
"logging": "debug"
}
],
"refreshRate": 360,
"pushRate": 5,
"logging": "debug"
},
"platform": "SwitchBot"
}
The affected device is "Curtain 2" (2nd Generation)
"Curtain" (1st Generation) isn't moving at all.

please try v2.5.0

v2.5.0 is working. There is still some delay in state but not as much as before.

Looks like @dnicolson has submitted some PRs so hopefully that will help as well.


Update setup script version

Travis builds were failing.

Nice catch, but the build is still failing. It looks like it's hitting into some issue while compiling transmission.

@SavageCore Travis is still failing. Do you think you have the time to fix the build?

@karamanolev Well my change to -march=corei7-avx seems to get it most of the way there. Now there is a python error to deal with.


When clicking on a folded statement list, unfold statement list

... in the same way as if the user clicked on the button:

@davidzbiral Do you mean to make the header of the statement list clickable?

@Ptrhnk Yes, to make the header clickable, and upon click, the statement list will unfold. I followed a user when working and he was visibly expecting this functionality :-)


Work pixi-viewport with react-pixi

Description
I try connect pixi-viewport and react-pixi for work together, but can't.
In my codesandbox work event on drag-start, but image won't move or zoom.
Help me get to work together these packages
Steps to reproduce

try move image
see drag-start event in console

Additional info

@inlet/react-pixi version: 1.1.0
React version: 16.8.6
ReactDOM version: 16.8.6
PIXI version: 5.1.5
pixi-viewport version 4.2.3

@gespispace How odd that I am looking at the exact same combination for the first time. Thank you providing a sandbox, it's been very useful.
I was able to get your demo to work by making the <Text /> component a child of the <Viewport /> - I've forked your sandbox with the required changes here: https://codesandbox.io/s/elated-liskov-pdcd6

@warrenseymour Thank you very much.

Awesome guys!

@wms @inlet @gespispace In this setup—which I've copied and gotten to work—how do I run methods on the viewport?


files mkdir is not supported

Describe the bug
files mkdir is not supported

Thanks. It's scoped to be in a future testing release by issue #108 - since this is a known issue I am going to go ahead and close this ticket.


Update jscs to 3.0

Jscs is now deprecated and will no longer be updated.
It will only have bug fixes for three months and instead they are moving to eslint.

Could you please take a look on the errors that are going on in the unit tests?

@paladox would you mind reviewing your PR? I'm interested in your update!

Yeah, i was waiting to do the support for 3.x release since it was shaky for a while, still is though, i'm hoping incoming 3.0.4 release would cover most of the issues

Ok, I'm not sure why it is failing
236Testing methods.js...............Warning: Object # has no method 'getSourceCodeLength' Use --force to continue.

I used verbose and tracked it down to this line
https://github.com/jscs-dev/grunt-jscs/blob/master/test/methods.js#L279
per https://travis-ci.org/jscs-dev/grunt-jscs/jobs/130201258


fix IRCFirehoseFactory json name/nick mismatch

Now it is nick as per wikipedia example

Closing to test real quick

Ok, seems to join fine


[IMPROVEMENT] Use isVisible Ktx function rather than extension function

@RocketChat/android

@divyanshub024 There are some conflicts here to be solved... can you take a look please?


PD-72 add packing dependency

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.39%. Comparing base (9835df7) to head (0b9cfec).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
+ Coverage   93.14%   93.39%   +0.24%
==========================================
  Files          10       10
  Lines         321      333      +12
  Branches       58       61       +3
==========================================
+ Hits          299      311      +12
  Misses         14       14
  Partials        8        8

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


Add support for animating all properties using native driver

Summary
Native animation only supports properties that can be updated through the shadow view tree, limiting it to a small subset of properties and styles available for animation. Whenever a developer wants to animate something like size, color etc. they revert to JS based animation leading to complaints about stutters in the UX.
Inspired by the wide usage of Reanimated I've created a solution that uses the same principles as Reanimated. This is basically two separate paths to update a property - one is for shadow tree properties that can be synchronously updated through UIManager .synchronouslyUpdateViewOnUIThread, and one that uses a batched update queue that is updated through UIManager.updateView.
This might have some performance issues, but the result will be much smoother and faster than using JS based animation.
I'm aware that a Fabric based animation library is in the works, but believe that this PR can add value for developers until Fabric is available.
Changelog

[iOS][Added] Added support for animating unsupported props with useNativeDriver
[General][Added] Added support for animating all props using native driver
[Android][Added] Added support for animating all props with useNativeDriver

Test Plan

Added examples that shows native animations of size and color in RNTester
Removed unit tests for illegal native properties

Hey @chrfalch, thanks for doing this! In general I think this is something I'm supportive of, and seems like a fine thing to do. I'll need to spend some time with this to see if it has implications on native driver animations in Fabric, since they share most code currently. I'll try to set aside some time this week to play around with it.

Thanks so much for the feedback. I’m currently unavailable for a few days :( will set a side time as soon as possible to fix the issues you pointed out.

Hi, @JoshuaGross and @janicduplessis - how should we continue with this PR? I see that some of the tests are failing, but I think the test_ios_frameworks test is failing for everyone these days, and the test_android fail seems to be an infrastructure failure?

@chrfalch Looks like we got a part wrong. In the original implementation only style props are validated, this means that any regular prop should still go through synchronouslyUpdateViewOnUIThread. However we don't have this context anymore in RCTPropsAnimatedNode.
I suggest we invert our list and instead of having uiProps which are props that can be updated with synchronouslyUpdateViewOnUIThread we go with something like layoutProps which are props that need to use the regular UIManager pipeline (enqueueUpdateViewOnUIManager ). The list of layout props can be found here https://github.com/facebook/react-native/blob/master/React/Views/RCTViewManager.m#L339.

@chrfalch Looks like we got a part wrong. In the original implementation only style props are validated, this means that any regular prop should still go through synchronouslyUpdateViewOnUIThread. However we don't have this context anymore in RCTPropsAnimatedNode.
I suggest we invert our list and instead of having uiProps which are props that can be updated with synchronouslyUpdateViewOnUIThread we go with something like layoutProps which are props that need to use the regular UIManager pipeline (enqueueUpdateViewOnUIManager ). The list of layout props can be found here https://github.com/facebook/react-native/blob/master/React/Views/RCTViewManager.m#L339.
An example of this is animating the value of a slider https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js#L661. With the current changes it would go through enqueueUpdateViewOnUIManager instead of synchronouslyUpdateViewOnUIThread.

Great! Thanks - will see if I can make the required changes. Thanks for the pointers as well.

@chrfalch Looks like we got a part wrong. In the original implementation only style props are validated, this means that any regular prop should still go through synchronouslyUpdateViewOnUIThread. However we don't have this context anymore in RCTPropsAnimatedNode.
I suggest we invert our list and instead of having uiProps which are props that can be updated with synchronouslyUpdateViewOnUIThread we go with something like layoutProps which are props that need to use the regular UIManager pipeline (enqueueUpdateViewOnUIManager ). The list of layout props can be found here https://github.com/facebook/react-native/blob/master/React/Views/RCTViewManager.m#L339.
An example of this is animating the value of a slider https://github.com/facebook/react-native/blob/master/RNTester/js/examples/NativeAnimation/NativeAnimationsExample.js#L661. With the current changes it would go through enqueueUpdateViewOnUIManager instead of synchronouslyUpdateViewOnUIThread.

Great! Thanks - will see if I can make the required changes. Thanks for the pointers as well.

Should be fixed now, @janicduplessis :)

Hmm maybe we could just expose the layoutProps array to make it possible to add to it from objc / java by getting the native animated module instance with bridge.moduleForClass. It can also be possible to add a new method on the native animated module like addLayoutProp. We might want to address this is a separate PR though.

As for SVG, afaik it already works with the current implementation using synchronouslyUpdateViewOnUIThread.

Hmm maybe we could just expose the layoutProps array to make it possible to add to it from objc / java by getting the native animated module instance with bridge.moduleForClass. It can also be possible to add a new method on the native animated module like addLayoutProp. We might want to address this is a separate PR though.

What about adding support for updating it from JavaScript to make it easier for devs to use it?

Left a few more comments, after those are resolved it is good to ship for me, I looked mostly at the iOS implementation. I'll let @JoshuaGross pick it up from here.

Thanks so much for helping out - @JoshuaGross: Ping me on discord or here if you have questions.

Had a chat with @chrfalch offline, will summarize here:
While I see the value in this, this native Animated library may not be the right solution for animations longterm. It (and LayoutAnimations) have a number of issues in their current incarnation; aside from the APIs not being the nicest to use, it's very easy to get an app into a bad state (visual glitches or crashing) using these libraries, in ways that aren't super trivial to solve.
At the same time, as we're preparing for Fabric to be released, any major breaking changes to the core need to be supported in Fabric, and this increases the workload for the core team substantially and does actually push out the ship date of Fabric with every change we need to port to Fabric. With this change in particular, changing layout props requires a Yoga relayout, which in Fabric requires a C++ commit of a new shadow node - simply not possible at all with the current version of native Animated. This isn't a matter of "it would take a few weeks", we would have to completely rewrite Animated for Fabric to support this.
So our options are:

Merge this and live with a big inconsistency between this version of RN and Fabric... forever
Rewrite LayoutAnimations and Animated for Fabric
and/or, create a new animation API for Fabric

Since the current version of native Animated is compatible with Fabric, and because I want the migration to Fabric to be as trivial as possible, I'm very hesitant to merge this. At the same time, if we did rewrite Animated to support this in Fabric, it's not clear that we would even want that with the current API; if we're spending that amount of effort it makes sense to build a new, modern animation system with an API we can put more thought into. (I plan to do just that, but can't promise anything wrt timing)
I realize this is probably disappointing for some people, so I figured it would be helpful to see our rationale.


fix list browser issue

this fixes the --xxx_list_browsers not functioning in magellan@11

Codecov Report

Merging #259 into master will decrease coverage by 0.09%.
The diff coverage is 50%.

@@            Coverage Diff            @@
##           master     #259     +/-   ##
=========================================
- Coverage   97.29%   97.19%   -0.1%
=========================================
  Files          31       31
  Lines         960      962      +2
=========================================
+ Hits          934      935      +1
- Misses         26       27      +1

Impacted Files
Coverage Δ

src/cli.js
94.44% <50%> (-0.5%)
:arrow_down:

src/test_runner.js
97.92% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Love2d game engine issue with save game state

Describe the Issue (If applicable)
filesystem save doesn't work for Love2d game
How can the issue be reproduced? (If applicable)
I am creating a simple game and I am trying to save the score
It works fine in love-11.5-win64.exe
But save doesn't work in my handheld device
love.filesystem.newFile(scoreFile, "w") returns nil
local scoreFile = "highscoresnakegame.txt"

local function saveHighScore()
    local file = love.filesystem.newFile(scoreFile, "w")
    file:write(tostring(highScore))
    file:close()
end

local function loadHighScore()
    if love.filesystem.getInfo(scoreFile) then
        local file = love.filesystem.read(scoreFile)
        highScore = tonumber(file) or 0
    end
end

I also tried a different variation. I don't think it created the file. It doesn't load/find the file
love.filesystem.write(scoreFile, tostring(highScore))

What device are you using? (Only the Gameforce Chi, RK2020, OGA 1.0, OGA 1.1, RG351MP, RG351V, RGB10, R35s, RG353V/VS, RG353M, RG503, RGB30, and RK2023 units are officially supported)
RG353PS
What version of ArkOS are you on?
ArkOS_RG353M_v2.0_09292024.img
Anything else you'd like to include that may help to review this issue or feature request?
Love2d error on rg353ps

game
-- alt + l
-- compact main.lua to zip file and rename to .love extension
-- Key mappings from controls/main.gptk
local controls = {
    back = "escape",
    start = "return",
    a = "z",
    b = "lshift",
    x = "space",
    y = "b",
    l1 = "l",
    l2 = "x",
    l3 = "\"",
    r1 = "r",
    r2 = "y",
    r3 = "\"",
    up = "w",
    down = "s",
    left = "a",
    right = "d",
    left_analog_up = "up",
    left_analog_down = "down",
    left_analog_left = "left",
    left_analog_right = "right",
    right_analog_up = "mouse_movement_up",
    right_analog_down = "mouse_movement_down",
    right_analog_left = "mouse_movement_left",
    right_analog_right = "mouse_movement_right"
}

local gameOverTimer = 0
local gridSize = 20
local snake = {}
local apple = {}
local direction = "right"
local nextDirection = "right"
local gameState = "playing"
local blueSquare = {x = 8, y = 6}
local yellowSquare = {x = 24, y = 18}
local currentLevel = 0
local score = 0
local highScore = 0
local scoreFile = "highscore_snakegame.txt"
local isHighestScore = false

local function saveHighScore()
    local file = love.filesystem.newFile(scoreFile, "w")
    file:write(tostring(highScore))
    file:close()
end

local function loadHighScore()
    if love.filesystem.getInfo(scoreFile) then
        local file = love.filesystem.read(scoreFile)
        highScore = tonumber(file) or 0
    end
end

function love.load()
    love.window.setMode(640, 480, { resizable = false })
    love.graphics.setBackgroundColor(0.1, 0.1, 0.1)
    loadHighScore()
    resetGame()
end

function resetGame()
    snake = {
        {x = 10, y = 10, l = 0},
        {x = 9, y = 10, l = 0},
        {x = 8, y = 10, l = 0},
    }
    direction = "right"
    nextDirection = "right"
    gameState = "playing"
    currentLevel = 0
    score = 0
    isHighestScore = false

    spawnApple()
end

function spawnApple()
    apple.x = love.math.random(1, love.graphics.getWidth() / gridSize - 1)
    apple.y = love.math.random(1, love.graphics.getHeight() / gridSize - 1)
end

function love.update(dt)
    if gameState == "scoreDisplay" then
        gameOverTimer = gameOverTimer - dt
        if gameOverTimer <= 0 then
            gameState = "gameover"
        end
        return
    elseif gameState ~= "playing" then
        return
    end

    if (love.keyboard.isDown(controls.up) or love.keyboard.isDown(controls.left_analog_up)) and direction ~= "down" then
        nextDirection = "up"
    elseif (love.keyboard.isDown(controls.down) or love.keyboard.isDown(controls.left_analog_down)) and direction ~= "up" then
        nextDirection = "down"
    elseif (love.keyboard.isDown(controls.left) or love.keyboard.isDown(controls.left_analog_left)) and direction ~= "right" then
        nextDirection = "left"
    elseif (love.keyboard.isDown(controls.right) or love.keyboard.isDown(controls.left_analog_right)) and direction ~= "left" then
        nextDirection = "right"
    end

    if love.timer.getTime() % 0.2 < dt then
        moveSnake()
    end
end

function endGame()
    if score > highScore then
        isHighestScore = true
        highScore = score
        saveHighScore()
    end
    gameState = "scoreDisplay"
    gameOverTimer = 2 -- 2 seconds delay
end

function moveSnake()
    direction = nextDirection
    local head = snake[1]
    local newLevel = head.l

    if (currentLevel == 0 and yellowSquare.x == head.x and yellowSquare.y == head.y) then
        newLevel = 1
        currentLevel = 1
        spawnApple()
    elseif (currentLevel == 1 and blueSquare.x == head.x and blueSquare.y == head.y) then
        newLevel = 0
        currentLevel = 0
        spawnApple()
    end

    local newHead = {x = head.x, y = head.y, l = newLevel}

    if direction == "up" then
        newHead.y = newHead.y - 1
    elseif direction == "down" then
        newHead.y = newHead.y + 1
    elseif direction == "left" then
        newHead.x = newHead.x - 1
    elseif direction == "right" then
        newHead.x = newHead.x + 1
    end

    -- Check collision with walls
    if newHead.x < 0 or newHead.y < 0 or newHead.x >= love.graphics.getWidth() / gridSize or newHead.y >= love.graphics.getHeight() / gridSize then
        endGame()
        return
    end

    -- Check collision with self
    for _, segment in ipairs(snake) do
        if newHead.x == segment.x and newHead.y == segment.y and newHead.l == segment.l then
            endGame()
            return
        end
    end

    -- Move snake
    table.insert(snake, 1, newHead)

    -- Check if apple is eaten
    if newHead.x == apple.x and newHead.y == apple.y then
        score = score + 1
        spawnApple()
    else
        table.remove(snake) -- Remove tail
    end
end

function love.draw()
    if gameState == "playing" then
        -- Draw apple
        love.graphics.setColor(1, 0, 0)
        love.graphics.rectangle("fill", apple.x * gridSize, apple.y * gridSize, gridSize, gridSize)

        -- Draw snake
        love.graphics.setColor(0, 1, 0)
        for _, segment in ipairs(snake) do
            if (segment.l == currentLevel) then
                love.graphics.rectangle("fill", segment.x * gridSize, segment.y * gridSize, gridSize, gridSize)
            end
        end

        if currentLevel == 0 then
            love.graphics.setColor(1, 1, 0)
            love.graphics.rectangle("fill", yellowSquare.x * gridSize, yellowSquare.y * gridSize, gridSize, gridSize)
        elseif currentLevel == 1 then
            love.graphics.setColor(0, 0, 1)
            love.graphics.rectangle("fill", blueSquare.x * gridSize, blueSquare.y * gridSize, gridSize, gridSize)
        end

        -- Draw score
        love.graphics.setColor(1, 1, 1)
        love.graphics.print("Score: " .. score, 10, 10)
        love.graphics.print("High Score: " .. highScore, 350, 10)
    elseif gameState == "scoreDisplay" then
        if isHighestScore then
            love.graphics.setColor(1, 1, 0)
            love.graphics.printf("Highest Score: " .. score, 0, love.graphics.getHeight() / 2 - 20, love.graphics.getWidth(), "center")
        else
            love.graphics.setColor(1, 1, 1)
            love.graphics.printf("Score: " .. score, 0, love.graphics.getHeight() / 2 - 20, love.graphics.getWidth(), "center")
        end
    elseif gameState == "gameover" then
        love.graphics.setColor(1, 0, 0)
        love.graphics.printf("Game Over\nPress Enter to Restart", 0, love.graphics.getHeight() / 2 - 20, love.graphics.getWidth(), "center")
    end
end

function love.keypressed(key)
    if key == controls.start and gameState == "gameover" then
        resetGame()
    end
end

It works with this code
local function saveHighScore()
    local file = io.open(scoreFile, "w")

    if file then
        file:write(tostring(highScore))
        file:close()
    end
end

local function loadHighScore()
    local file = io.open(scoreFile, "r")

    if file then
        local content = file:read("*all")
        highScore = tonumber(content) or 0
        file:close()
    end
end

love2d is a mess with the current implementation in the OS.  I don't know how to solve it either since I don't understand how Love2D is supposed to work with Joysticks.  Also, Love2D engines don't seem to be backward compatible with some titles which is also confusing to me.


[Enhancement] Make the output of StarRocks version more clear

If we build the StarRocks in the main branch, the output of select current_version() will be UNKNOWN. It's a misunderstanding. The pull request changes the behavior of gen_build_version.py. It will output the version using the branch-commithash in the build time.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/GlobalVariable.java
1
1
100.00%
[]


[Regression] [iOS] fails to run app via npx rnv

Describe the bug
Fails to run app via npx rnv on ios. Note npx rnv run -p ios works fine
To Reproduce
Steps to reproduce the behavior:

Install rnv via npm
Create new project
Do npx rnv
Choose run
Pick web platform ->  rnv asks to update packages - update -> pass
Do npx rnv
Choose run
Pick ios-> error

Expected behavior
App launches on simulator
Screenshots or copy&paste
➜  naujas git:(master) ✗ npx rnv

┌─────────────────────────────────────────────────────────────────┐
│ ██████╗ ███████╗███╗   ██╗ █████╗ ████████╗██╗██╗   ██╗███████╗ │
│ ██╔══██╗██╔════╝████╗  ██║██╔══██╗╚══██╔══╝██║██║   ██║██╔════╝ │
│ ██████╔╝█████╗  ██╔██╗ ██║███████║   ██║   ██║██║   ██║█████╗   │
│ ██╔══██╗██╔══╝  ██║╚██╗██║██╔══██║   ██║   ██║╚██╗ ██╔╝██╔══╝   │
│ ██║  ██║███████╗██║ ╚████║██║  ██║   ██║   ██║ ╚████╔╝ ███████╗ │
│ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═══╝╚═╝  ╚═╝   ╚═╝   ╚═╝  ╚═══╝  ╚══════╝ │
│ $ npx rnv                                                       │
└─────────────────────────────────────────────────────────────────┘
? Pick a command run...
?  Will be used to generate assets.
info: Skipping pod action. Reason: Podfile.checksum matches current value
task: ✔ configure
✔ Executing: xcrun simctl list --json
task: ○ start ↺1
task: ○ configureSoft ↺1
task: ○ app configure ↺2
info: Current app config: app
task: ✔ app configure
info: Current Build Scheme: debug
task: ✔ configureSoft

Dev server running at: http://<IP_ADDRESS>:8082/index.bundle?platform=ios

task: ✔ start
⠇ Waiting for bundler to finish...warn =================================================================================================
warn From React Native 0.73, your project's Metro config should extend '@react-native/metro-config'
warn or it will fail to build. Please copy the template at:
warn https://github.com/facebook/react-native/blob/main/packages/react-native/template/metro.config.js
warn This warning will be removed in future (https://github.com/facebook/metro/issues/1018).
warn =================================================================================================
info Welcome to React Native v0.73
info Starting dev server on port 8082...

                        ▒▒▓▓▓▓▒▒
                     ▒▓▓▓▒▒░░▒▒▓▓▓▒
                  ▒▓▓▓▓░░░▒▒▒▒░░░▓▓▓▓▒
                 ▓▓▒▒▒▓▓▓▓▓▓▓▓▓▓▓▓▒▒▒▓▓
                 ▓▓░░░░░▒▓▓▓▓▓▓▒░░░░░▓▓
                 ▓▓░░▓▓▒░░░▒▒░░░▒▓▒░░▓▓
                 ▓▓░░▓▓▓▓▓▒▒▒▒▓▓▓▓▒░░▓▓
                 ▓▓░░▓▓▓▓▓▓▓▓▓▓▓▓▓▒░░▓▓
                 ▓▓▒░░▒▒▓▓▓▓▓▓▓▓▒░░░▒▓▓
                  ▒▓▓▓▒░░░▒▓▓▒░░░▒▓▓▓▒
                     ▒▓▓▓▒░░░░▒▓▓▓▒
                        ▒▒▓▓▓▓▒▒

                Welcome to Metro v0.80.9
              Fast - Scalable - Integrated

⠙ Waiting for bundler to finish...info React Native v0.74.1 is now available (your project is running on v0.73.4).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.74.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.74.1
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".
✔ Waiting for bundler to finish...
✖ FAILED: npx react-native run-ios --scheme=RNVApp --mode=Debug --no-packager --simulator iPhone\ 15
error: ⨯ ○ run: COMMAND:

npx react-native run-ios --scheme=RNVApp --mode=Debug --no-packager --simulator iPhone\ 15

FAILED with ERROR:

❌ error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')
▸ Compiling RCTTextInputUtils.mm
 Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
 Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')
info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor
UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".

Error: Command failed with exit code 1: npx react-native run-ios --scheme=RNVApp --mode=Debug --no-packager --simulator iPhone 15

  WARNING: You should run npx react-native@latest to ensure you're always using the most current version of the CLI. NPX has cached version (0.73.4) != current release (0.74.1)

UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".
info Found Xcode workspace "RNVApp.xcworkspace"
info Launching iPhone 15 (iOS 17.2)
info Building (using "xcodebuild -workspace RNVApp.xcworkspace -configuration Debug -scheme RNVApp -destination id=7BAAF5DC-D50A-483A-87D0-BB3D69D25E38")
▸ Running script '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed'
▸ Processing ResourceBundle-RCTI18nStrings-React-Core-Info.plist
▸ Compiling UIView+ComponentViewProtocol.mm
▸ Compiling React-RCTFabric-dummy.m
▸ Compiling RCTViewComponentView.mm
▸ Compiling RCTImageLoader.mm
▸ Compiling RCTImageBlurUtils.mm
▸ Compiling RCTAnimatedImage.mm
▸ Compiling RCTUnimplementedViewComponentView.mm
▸ Compiling RCTBundleAssetImageLoader.mm
▸ Compiling RCTUnimplementedNativeComponentView.mm
▸ Compiling RCTThirdPartyFabricComponentsProvider.mm

❌  error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')

▸ Compiling RCTTextInputUtils.mm
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
    Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

    at makeError (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

  WARNING: You should run npx react-native@latest to ensure you're always using the most current version of the CLI. NPX has cached version (0.73.4) != current release (0.74.1)

info Found Xcode workspace "RNVApp.xcworkspace"
info Launching iPhone 15 (iOS 17.2)
info Building (using "xcodebuild -workspace RNVApp.xcworkspace -configuration Debug -scheme RNVApp -destination id=7BAAF5DC-D50A-483A-87D0-BB3D69D25E38")
▸ Running script '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed'
▸ Processing ResourceBundle-RCTI18nStrings-React-Core-Info.plist
▸ Compiling UIView+ComponentViewProtocol.mm
▸ Compiling React-RCTFabric-dummy.m
▸ Compiling RCTViewComponentView.mm
▸ Compiling RCTImageLoader.mm
▸ Compiling RCTImageBlurUtils.mm
▸ Compiling RCTAnimatedImage.mm
▸ Compiling RCTUnimplementedViewComponentView.mm
▸ Compiling RCTBundleAssetImageLoader.mm
▸ Compiling RCTUnimplementedNativeComponentView.mm
▸ Compiling RCTThirdPartyFabricComponentsProvider.mm

❌  error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')

▸ Compiling RCTTextInputUtils.mm
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
    Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".

┌─────────────────────────────────────────────────────────────────┐
│ ⨯ SUMMARY | 5/22/2024, 4:30:18 PM | rnv@                        │
│ $ npx rnv                                                       │
├─────────────────────────────────────────────────────────────────┤
│ Project<EMAIL_ADDRESS>                                         │
│ Workspace: rnv                                                  │
│ Platform (-p): ios                                              │
│ Engine: @rnv/engine-rn                                          │
│ Template: @rnv/template-starter                                 │
│ App Config (-c): app                                            │
│ Build Scheme (-s): debug                                        │
│ Target (-t): iPhone 15                                          │
│ Supported Platforms: web, ios, android, androidtv, firetv, tvos, macos, linux, windows, windows, tizen, webos, chromecast, kaios, androidwear, tizenwatch
│ Env Info: darwin | arm64 | node v18.19.0                        │
│ Executed Time: 0h:0m:24s:263ms                                  │
│ error: ⨯ ○ run: COMMAND:

npx react-native run-ios --scheme=RNVApp --mode=Debug --no-packager --simulator iPhone\ 15

FAILED with ERROR:

❌ error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')
▸ Compiling RCTTextInputUtils.mm
 Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
 Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')
info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor
UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".

Error: Command failed with exit code 1: npx react-native run-ios --scheme=RNVApp --mode=Debug --no-packager --simulator iPhone 15

  WARNING: You should run npx react-native@latest to ensure you're always using the most current version of the CLI. NPX has cached version (0.73.4) != current release (0.74.1)

UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".
info Found Xcode workspace "RNVApp.xcworkspace"
info Launching iPhone 15 (iOS 17.2)
info Building (using "xcodebuild -workspace RNVApp.xcworkspace -configuration Debug -scheme RNVApp -destination id=7BAAF5DC-D50A-483A-87D0-BB3D69D25E38")
▸ Running script '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed'
▸ Processing ResourceBundle-RCTI18nStrings-React-Core-Info.plist
▸ Compiling UIView+ComponentViewProtocol.mm
▸ Compiling React-RCTFabric-dummy.m
▸ Compiling RCTViewComponentView.mm
▸ Compiling RCTImageLoader.mm
▸ Compiling RCTImageBlurUtils.mm
▸ Compiling RCTAnimatedImage.mm
▸ Compiling RCTUnimplementedViewComponentView.mm
▸ Compiling RCTBundleAssetImageLoader.mm
▸ Compiling RCTUnimplementedNativeComponentView.mm
▸ Compiling RCTThirdPartyFabricComponentsProvider.mm

❌  error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')

▸ Compiling RCTTextInputUtils.mm
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
    Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

    at makeError (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

  WARNING: You should run npx react-native@latest to ensure you're always using the most current version of the CLI. NPX has cached version (0.73.4) != current release (0.74.1)

info Found Xcode workspace "RNVApp.xcworkspace"
info Launching iPhone 15 (iOS 17.2)
info Building (using "xcodebuild -workspace RNVApp.xcworkspace -configuration Debug -scheme RNVApp -destination id=7BAAF5DC-D50A-483A-87D0-BB3D69D25E38")
▸ Running script '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed'
▸ Processing ResourceBundle-RCTI18nStrings-React-Core-Info.plist
▸ Compiling UIView+ComponentViewProtocol.mm
▸ Compiling React-RCTFabric-dummy.m
▸ Compiling RCTViewComponentView.mm
▸ Compiling RCTImageLoader.mm
▸ Compiling RCTImageBlurUtils.mm
▸ Compiling RCTAnimatedImage.mm
▸ Compiling RCTUnimplementedViewComponentView.mm
▸ Compiling RCTBundleAssetImageLoader.mm
▸ Compiling RCTUnimplementedNativeComponentView.mm
▸ Compiling RCTThirdPartyFabricComponentsProvider.mm

❌  error: Build input file cannot be found: '/Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/React/Fabric/RCTThirdPartyFabricComponentsProvider.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it? (in target 'React-RCTFabric' from project 'Pods')

▸ Compiling RCTTextInputUtils.mm
    Run script build phase 'Bundle React Native code and images' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RNVApp' from project 'RNVApp')
    Run script build phase '[CP-User] [Hermes] Replace Hermes for the right configuration, if needed' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'hermes-engine' from project 'Pods')

info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

UnhandledPromiseRejection: 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(). The promise rejected with the reason "Error: Failed to build iOS project. "xcodebuild" exited with error code '65'. To debug build logs further, consider building your app with Xcode.app, by opening 'RNVApp.xcworkspace'.".

│ Project location: ./platformBuilds/app_ios/RNVApp.xcworkspace   │
└─────────────────────────────────────────────────────────────────┘
error: ⨯ ○ run: COMMAND:

node /Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/local-cli/cli.js start --port 8082 --no-interactive --config=metro.config.js

FAILED with ERROR:

Error: Command was killed with SIGTERM (Termination): node /Users/gabriele/Desktop/nauji/naujas/node_modules/react-native/local-cli/cli.js start --port 8082 --no-interactive --config=metro.config.js
    at makeError (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/Users/gabriele/Desktop/nauji/naujas/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)

➜  naujas git:(master) ✗

Desktop (please complete the following information):

OS: macOS Ventura 13.6.4 (M2)
Node Version 18.19.0
RNV Version 1.0.0-rc.19
@rnv/template-starter 1.0.0-rc.19

can't reproduced anymore


During the demo, if the user is on invited list, it doesn't say it is actually on the invited list on the event page.

Ellis mentioned he refactored this page?

Fixed by #90


[ingest]: getProjDB argument

Looks like getProjDB expects the token for a project, not the project name...
(from ndproj/ndproject.py)
class NDProject:

  def __init__(self, token_name ) :

In webservices/ndwsingest.py, there are a few instances where the getProjDB method is called...
  def getProjDB(project_name):
    """Return a the kvengine object"""

    pr = NDProject(project_name)

There's a bit of obfuscation, but I believe the project object always operates on token, not project name.
@kunallillaney can you confirm? If so, let's merge this, fix the rest of the issues in web services, and write a test that uses a project with a non-matching token (which is where this issue came up).
@Aeusman I think you wrote the ndwsingest code, right? Wanna take a look and confirm I didn't mess any of your stuff up?
Thanks!

@alexbaden "I believe the project object always operates on token, not project name" is incorrect. You can fetch a project object based on the project name or the token name aka it has 2 constructors. @Aeusman did not write any of this code. This is all me and that is meant to be that way for a reason and is tested. This code is part of creating channels via RESTful interfaces.

https://github.com/neurodata/ndstore/issues/371

Issue has been fixed and pushed. Tests have been updates as a proof of concept.


Remove config creator

This PR removes the config creator from sparsify and replaces the functionality with calls to the Neural Magic API.
Note that in this PR the calls to the API are directed to local host. This address will be properly updated before merging sparsify.alpha into main, once the API goes live.
Testing
covered by automatic pytest testing and integration tests
Ran a manual test by running ./bin/run-local within this repo, followed by sparsify.auto --task object_detection --data coco128.yaml in sparsify

@corey-nm great call on the trial management testing. Added testing of the main flow in test_main.py

Thanks for the thorough comments. Addressed 🙂
@rahul-tuli I updated the NM API calls to be centralized, which touched sparsify.package. Please take a look


Arch Linux: PKGBUILD source line broken

The source line within PKGBUILD seems to be invalid/outdated/broken.

Fixed by a2905c6a2de447c08d4795594ba2c8a1f2465cff merge request commit.


ENH: Initial pass at implementing DataFrame.asof, GH 2941

Fixes #2941
This can almost certainly be made quicker, still digging into the
internals to understand the various underlying indexers.
There are 4 distinct logics you can apply to how to deal with the
missings (as opposed to the Series asof, wheres theres just two,
either skipna or dont skipna). The default is to be equivalent to
df.apply(lambda s: s.asof(where)).
Likely not ready to actually be merged, but at a stage where I could
use some feedback on both the logic and implementation.

pls rebase on master and repush had an issue with some builds

Sorry about that, must've been some changes between my rebase and the travis  build. Anyway, it's green now.

Reworked this using take_2d_multi, thoughts?

Is there a good reason why this is restricted to timestamps? I suspect not, and it would be nice to generalize things a bit.
I recently cleaned up the related Index.asof method -- your method here depends on Index.asof_locs, which could also definitely use another look. That would be greatly appreciated and would make me more confident in your new feature. Note, for example, that Index.asof_locs currently has no tests.

.asof is really just an implementation of reindexing. In fact, this is simply a one-sided method='nearest' (the right side). Any reason why we are not simply doing that? E.g. this should just be a generalized method to Index, and then the front end is just simple wrappers around .reindex(method='asof').

@jreback Indeed, this does almost work already with .reindex(method='pad') (or maybe it's method='backfill', I can't keep those straight). The difference here is that asof will drop missing values, though perhaps that's better done explicitly with .dropna(). Also, this version lets you do asof across multiple columns simultaneously.

no I get that this handles multiple versions, and maybe that's a reason to special case somewhat, however, this should be an internal type of method (meaning implemented in the Index) as its simply a reindexer

Thanks for the feedback. The motivation for df.asof was largely that there already is a series.asof. But as @shoyer points out, there's really no reason this needs to be specialized to timestamps (any sortable index should work).
Making it a part of index functionality as @jreback suggests, seems a natural choice to make the behaviour available to both frame and series, and also to non timeseries indexes.
There's really only two fundamental cases: either skip missings everywhere .reindex(method='ffill'), or skip them no where (not currently available), the other options can be achieve by the latter and fillna.
I'll take a stab at implementing a method='asof' for reindex to handle the latter case, and let's abandon this PR. Might also make sense to deprecate series.asof in favor of series.reindex(method='ffill'). I'll confirm that it passes the tests for asof and open a seperate issue.

@bwillers I think you have it backwards -- .reindex(method='ffill') will not skip any missing values in the existing series/frame.
Here's my mapping from this method to reindex:

.asof(where, skipna='percolumn') -> .reindex(where, method='ffill').fillna(method='ffill')
.asof(where, skipna='none') -> .reindex(where, method='ffill')
.asof(where, skipna='all') -> .dropna(how='all').reindex(where, method='ffill')
.asof(where, skipna='any') -> .dropna(how='any').reindex(where, method='ffill')

Which case would .reindex(method='asof') cover?  For some reason I was under the impression that .reindex(where, model='ffill') is ignored rows with missing values when it tries to find what to pull forward. Demonstrably however, this is not so:
print(df)
            a   b
2008-01-02  1   1
2008-01-09  2 NaN
2008-01-16  3   3

print(df.reindex(new_dates, method='ffill'))
             a   b
2008-01-01 NaN NaN
2008-01-08   1   1
2008-01-15   2 NaN
2008-01-22   3   3

I was expecting that bottom right NaN to be a 1 - I must have somehow conflated method='ffill' in reindex and fillna.
So since all the df.asof varieties can be achieved using the existing .reindex(where='ffill') approach, all this PR does is avoid an intermediate frame, but that's probably not worth cluttering the API for.
Sorry for the cycles wasted on my poor understanding.

@bwillers No worries! We would still appreciate documentation updates and/or cleanup/deprecation for Series.asof


Unresolvable dependency

Got a Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\Manager after upgrading to latest laravel 5.7.16.
Stack trace
Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\Support\Manager {"exception":"[object] (Illuminate\\Contracts\\Container\\BindingResolutionException(code: 0): Unresolvable dependency resolving [Parameter #0 [ <required> $app ]] in class Illuminate\\Support\\Manager at /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php:960)
[stacktrace]
#0 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(898): Illuminate\\Container\\Container->unresolvablePrimitive(Object(ReflectionParameter))
#1 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(839): Illuminate\\Container\\Container->resolvePrimitive(Object(ReflectionParameter))
#2 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(807): Illuminate\\Container\\Container->resolveDependencies(Array)
#3 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(658): Illuminate\\Container\\Container->build('Illuminate\\\\Noti...')
#4 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(609): Illuminate\\Container\\Container->resolve('Illuminate\\\\Noti...', Array)
#5 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(735): Illuminate\\Container\\Container->make('Illuminate\\\\Noti...', Array)
#6 /myproject/vendor/laravel/framework/src/Illuminate/Container/Container.php(1222): Illuminate\\Foundation\\Application->make('Illuminate\\\\Noti...')
#7 /myproject/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(161): Illuminate\\Container\\Container->offsetGet('Illuminate\\\\Noti...')
#8 /myproject/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(130): Illuminate\\Support\\Facades\\Facade::resolveFacadeInstance('Illuminate\\\\Noti...')
#9 /myproject/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php(217): Illuminate\\Support\\Facades\\Facade::getFacadeRoot()
#10 /myproject/vendor/laravel/nexmo-notification-channel/src/NexmoChannelServiceProvider.php(27): Illuminate\\Support\\Facades\\Facade::__callStatic('extend', Array)
#11 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(574): Illuminate\\Notifications\\NexmoChannelServiceProvider->register()
#12 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php(75): Illuminate\\Foundation\\Application->register(Object(Illuminate\\Notifications\\NexmoChannelServiceProvider))
#13 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(550): Illuminate\\Foundation\\ProviderRepository->load(Array)
#14 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/RegisterProviders.php(17): Illuminate\\Foundation\\Application->registerConfiguredProviders()
#15 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Application.php(204): Illuminate\\Foundation\\Bootstrap\\RegisterProviders->bootstrap(Object(Illuminate\\Foundation\\Application))
#16 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(297): Illuminate\\Foundation\\Application->bootstrapWith(Array)
#17 /myproject/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(120): Illuminate\\Foundation\\Console\\Kernel->bootstrap()
#18 /myproject/artisan(35): Illuminate\\Foundation\\Console\\Kernel->handle(Object(Symfony\\Component\\Console\\Input\\ArgvInput), Object(Symfony\\Component\\Console\\Output\\ConsoleOutput))
#19 {main}

Did you try the solution from https://github.com/laravel/framework/issues/26766?

Sorry, this bug appears on my laravel even with that service provider listed.
I have overridden Illuminate\Notifications\NotificationServiceProvider to App\OverridingLibraries\Illuminate\Notifications\NotificationServiceProvider, load it in app.php (because I need to override some Laravel libraries to have custom code) and the error appears again.

delete cache file in bootstrap/cache/*
and run composer update


⚠ Bofrost.de has degraded performance

In 3d49390, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1355 ms

Resolved: Bofrost.de performance has improved in 78fbe03 after 7 minutes.


Generated script-tags does not check for customer templates

Problem
The js bundle files for customer pages do not load.
The generated script-tags.liquid file has the following liquid statement that tests which template it is on:
{%- if template == 'login' -%}
<script type="text/javascript" src="{{ 'template.login.js' | asset_url }}" defer="defer"></script>
{%- else -%}
<link rel="prefetch" href="{{ 'template.login.js' | asset_url }}" as="script">
{%- endif -%}

However, the template name for customer pages starts with customers/. The above statement should be:
{%- if template == 'customers/login' -%}
<script type="text/javascript" src="{{ 'template.login.js' | asset_url }}" defer="defer"></script>
{%- else -%}
<link rel="prefetch" href="{{ 'template.login.js' | asset_url }}" as="script">
{%- endif -%}

Replication steps
Create a login js file at src/assets/scripts/templates/customers/login.js and a login liquid file at src/templates/customers/login.liquid and run the command yarn deploy

I also had this problem as well. Switching from template.name to template in the script-tags.liquid snippet broke this but the fix is relatively benign.


Cleaned branch

Code formatted and cleaned unused using directives

This is huge it's hard to review, I suggest closing this, @nirzaf please move it into smaller manageable PRs


Add FAQ menu/page to Spin documentation

The Cloud documentation has FAQ under the support menu.
In Spin's case, we could add a top-level menu called FAQ, and inside that accordion will sit FAQ and Troubleshooting pages.

This Spin issue "Add issue template that points people to FAQs and troubleshooting material" is directly related
https://github.com/fermyon/spin/issues/1501

Relevant subsets also need to sit on the topic pages.  For example, problems with Rust targets need to be mentioned on the Rust page: readers should not have to know to go to a separate troubleshooting page.  I am not sure of a good way to coordinate a centralised page with topic subsets though...


x/pulumi: add support for stack outputs

This adds support to the pulumi package for obtaining stack outputs, which is very useful for getting the values of resources created by pulumi, e.g. an AWS Lambda URL.
There also appears to have been a typo in up.sh in the pulumi package where a
non-existent env var "STACK_NAME" was referenced. This fixes it to what
was likely intended, "PULUMI_STACK".

cc @rawkode


test(scan4): Slice 2: (Prefactoring) Support patching down resources

Description
While working on the multi-namespace tests for Scanner V4 I had to fix a couple of issues along the way. This is the third slice, which contains support within the scanner v4 installation tests for patching down deployed resources. This is important, because deploying the complete stack including scanner V2 & V4 in two separate namespaces plus all other components requires a lot of resources. In the worst case workloads cannot be scheduled because they don't fit on the nodes in the best case we are just waiting a lot of computing power just for testing installation scenarios.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/retest


[8.x] add schedule:clear-mutex command

Currently there is no way to clear the mutex files created when using withoutOverlap(). The only way to clear them is using php artisan cache:clear however this is dangerous since it clears all other cache as well.
If your server restarts while a task is running, the mutex file does not get deleted. Then when the server comes up, it could take up to 24 hours (default value) for your task to re-run because the mutex file still exists. The only way currently to solve this is just running cache:clear however this is not optimal.
In order to delete only mutex files I added a schedule:clear-mutex command.

Adding an option like:
schedule:clear-mutex {signature?} would also be useful. I can add that too if there is a willingness for this feature.

just FYI Taylor renamed the method to schedule:clear-cache