Issue launching AppImage

Howdy!
When I launch lovr.AppImage it returns this:
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  4
  Serial number of failed request:  265
  Current serial number in output stream:  276

I have no clue why it does that, I even reinstalled it.

This looks very similar to this problem: https://github.com/bjornbytes/lovr/discussions/792
I have no idea what is causing it.  Our GLFW is kind of old, I'll try upgrading it out of desperation.

The weird thing is the program worked on this same driver version a few weeks ago, so I don't get what is going wrong here. I did update to a new, untested nvidia driver and it still doesn't work.

I just pushed the GLFW upgrade if you wanna see if that helps.  Also if you can post any system details like the driver version, distro, etc. it might help others that get the same issue or help with a potential fix.

For your info, here are my system specs:
OS: Ubuntu 24.04 LTS x86_64
Host: ASUS TUF Gaming F15 FX506HE_FX506HE 1.0
Kernel: 6.8.0-39-generic
Uptime: 3 hours, 22 mins
Packages: 2351 (dpkg), 16 (flatpak), 28 (snap)
Shell: bash 5.2.21
Resolution: 1080x1920, 1920x1080, 1920x1080
DE: GNOME 46.0
CPU: 11th Gen Intel i5-11400H (12) @ 4.500GHz
GPU: NVIDIA GeForce RTX 3050 Ti Mobile
GPU: Intel TigerLake-H GT1 [UHD Graphics]
Memory: 7224MiB / 15730MiB
Also, when I tried recompiling it gave me this error:
[  0%] Built target xr_global_generated_files
[  0%] Built target generate_openxr_header
[  0%] Building CXX object openxr/src/loader/CMakeFiles/openxr_loader.dir/api_layer_interface.cpp.o
In file included from /home/gungu/lovr/deps/openxr/src/loader/loader_platform.hpp:16,
                 from /home/gungu/lovr/deps/openxr/src/loader/api_layer_interface.hpp:19,
                 from /home/gungu/lovr/deps/openxr/src/loader/api_layer_interface.cpp:10:
/home/gungu/lovr/deps/openxr/src/common/xr_dependencies.h:60:10: fatal error: xcb/glx.h: No such file or directory
   60 | #include <xcb/glx.h>
      |          ^~~~~~~~~~~
compilation terminated.
gmake[2]: *** [openxr/src/loader/CMakeFiles/openxr_loader.dir/build.make:90: openxr/src/loader/CMakeFiles/openxr_loader.dir/api_layer_interface.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:1960: openxr/src/loader/CMakeFiles/openxr_loader.dir/all] Error 2

Luckily it isn't this version, since I also got this error a few hours ago when I compiled it for the second time.

To fix that compile error you can install libxcb-glx0-dev, full list of required packages is here.  The AppImage from CI is also available if that's easier

Thanks! I compiled the whole thing but sadly it still gives the same error.

Both people experiencing this issue are on dual iGPU/dGPU setups.  Apparently disabling the iGPU in BIOS fixes it.  Hopefully we can find a better workaround though.

Yeah, I'm hoping for a better workaround, because I have an Asus tuf 15 laptop, and they don't allow disabling the iGPU in the bios, since they got rid of the MUX switch.

Hi!
Got another update on this issue. The app works perfectly fine with noveau drivers, my only issue is that I've got a usb-c display which doesn't work with noveau drivers, but I'm gonna get that figured out. Maybe it also works on older driver version, I'm also gonna try that.

Another crazy discorvery, I downgraded drivers and I even tried with current driver versions, and it worked completely fine, up until I used the command
sudo prime-select nvidia
which ended up stopping the application from working. I'm just gonna leave out that function because I don't play games on linux anymore, and I guess it'll work. I'll still not close this issue though, since it isn't technically fixed

To prevent duplicate issues, I decided to come here. I tried both latest release, AppImage and manual build of manual development version, but it all leads to similar error:
X Error of failed request:  136   Major opcode of failed request:  148 ()   Minor opcode of failed request:  1   Serial number of failed request:  270   Current serial number in output stream:  270
The error was taken with manually initiated window(under lovr.load), so it may have some part different.
GLFW version on the development version is 3.50.(found in CMakeLists)

Thank you for the info.  If you're building from source you could try building with -DLOVR_USE_GLFW=OFF, I'm curious if this would change anything (this uses raw xcb instead of GLFW).

Weirdly, I got a blank window with this on "no game" display.
Text looks normal on my project, but it is just a black screen, and the log(my logging system) is stopping from certain place.
I enabled debug log, this is the output:
Error [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : RuntimeInterface::LoadRuntimes - unknown error
Error [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : RuntimeInterface::LoadRuntimes - failed to load a runtime
Error [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Failed to find default runtime with RuntimeInterface::LoadRuntime()
Error [GENERAL | xrEnumerateInstanceExtensionProperties | OpenXR-Loader] : Failed querying extension properties
Warning: GPU debugging is enabled, but validation layer is not installed```
This happened with "no game". For my project, it only shows the last warning(Due to lovr.headset being disabled?).

Note: The weird text issue did not occur on 0.17.1 with GLFW, where the software crashes.

Has anyone tried the __NV_PRIME_RENDER_OFFLOAD environment variable?
__NV_PRIME_RENDER_OFFLOAD=1 lovr

Nothing changed, with both GLFW and XCB.


[silx view] Cannot use menu "File > Open"  if fabio is missing

ERROR:silx.gui.qt._qt:<type 'exceptions.ImportError'> No module named fabio   File "/users/knobel/.local/lib/python2.7/site-packages/silx/app/view/Viewer.py", line 365, in open
    dialog = self.createFileDialog()
  File "/users/knobel/.local/lib/python2.7/site-packages/silx/app/view/Viewer.py", line 394, in createFileDialog
    import fabio

Should we add fabio and h5py as strong dependencies of silx? or at least of silx view and silx convert. We heavily relies on them and they meet our requirements in terms of packaging...
There is support for "extra dependencies" and even entry point dependencies but I don't how much this solves issues: http://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies

h5py is for sure mandatory now. Most widget and convert functions can't work without. Especially cause of the use of h5py "special types".


lodash.find breaks proxy?

immer does not modify the draft value on using lodash.find on 1.0.0.
The test code is below:
        it("processes with lodash.find", () => {
            const base = [{id: 1, a: 1}, {id: 2, a: 1}]
            const result = produce(base, draft => {
                const obj1 = find(draft, {id: 1})
                const obj2 = find(draft, {id: 2})
                obj1.a = 2
                obj2.a = 2
            })
            expect(result[0].a).toEqual(2)
            expect(result[1].a).toEqual(2)
        })

result:
    Expected value to equal:
      2
    Received:
      1

      130 |                 obj2.a = 2
      131 |             })
    > 132 |             expect(result[0].a).toEqual(2)
      133 |             expect(result[1].a).toEqual(2)
      134 |         })
      135 |

for reproduce: https://github.com/iruca3/immer/tree/bug_with_lodash_find
It reproduces on 1.0.0, but does not reproduce on 0.8.5.
I tried to fix this, but I couldn't find out why this is caused.

I tried with 0.8.5 but doesn't seem to work either. Can it be a difference in lodash version? the find gets me back a weird LodashWrapper object, and not the actual object from the draft

I tried the repository below with 0.8.5: https://github.com/iruca3/immer/tree/lodash_find_test_on_0.8.5
It passes all tests.
I reproduced on lodash 4.17.4. (lodash.find is 4.6.0)
also reproduced on using lodash.findIndex.
BTW, this code passes the test.
diff --git a/__tests__/base.js b/__tests__/base.js
index b53c2d3..e929abc 100644
--- a/__tests__/base.js
+++ b/__tests__/base.js
@@ -122,8 +122,8 @@ function runBaseTest(name, useProxies, freeze) {
             const base = [{id: 1, a: 1}, {id: 2, a: 1}]
             const result = produce(base, draft => {
                 const obj1 = find(draft, {id: 1})
-                const obj2 = find(draft, {id: 2})
                 obj1.a = 2
+                const obj2 = find(draft, {id: 2})
                 obj2.a = 2
             })
             expect(result[0].a).toEqual(2)

I hope this will help.

I found that lodash is not related on this issue.
The test case below also failed. Hmmm....
        it("processes with for loop", () => {
            const base = [{id: 1, a: 1}, {id: 2, a: 1}]
            const findById = (collection, id) => {
                for (const item of collection) {
                    if (item.id === id) return item
                }
                return null
            }
            const result = produce(base, draft => {
                const obj1 = findById(draft, 1)
                const obj2 = findById(draft, 2)
                obj1.a = 2
                obj2.a = 2
            })
            expect(result[0].a).toEqual(2)
            expect(result[1].a).toEqual(2)
        })


Lifecycle issue with Serializer and StateRepository

For clustering support, we changed the contract of Serializer that need to support persistent state by adding the StateRepository API.
However, we kept injecting this at Serializer construction time, which while working in practice, has several downsides:

The StateRepository really belongs to the AuthoritativeTier.Provider when thinking about it, which is what gives guarantees to have the same persistence level.
The Serializer really benefits from being created once and passed in to all Store so that it can be final.

From these two competing requirements, the current scheme is not working. We need to find another way of wiring the StateRepository inside the Serializer.
Sadly this means breaking the SPI so this can only be done for 3.2. And since we are breaking the SPI, should we consider moving away from exposing a ConcurrentMap to a custom type in the StateRepository?

From initial investigations on this issue, the solution I came up with is a construct / initialise for stateful Serializer.
Something like adding a specific interface: StatefulSerializer which has an initialise(StateRepository) method.
And the way you make a Serialzier stateful is by implementing that interface.
When the Authority gets initialised, it can then properly initialise the Serializer if needed by passing the StateRepository at the correct point in initialisation.


logic on username/as_user dep is flipped

Fixes incorrect value set for as_user when username is set.  Should be setting as_user to false instead of true per the Slack API Docs:
https://api.slack.com/methods/chat.postMessage

Coverage remained the same at 90.576% when pulling 4bc70646b201c8d448452c0658757efcf28688b7 on username-as_user-bug into 8f9cc202aefc952778af7b7d79ef02c3791702d2 on master.

Coverage increased (+1.6%) to 92.147% when pulling 3d16d488d099280f193ea4e61e3e2bba63839e9c on username-as_user-bug into 8f9cc202aefc952778af7b7d79ef02c3791702d2 on master.


[OKD-Core] Add pf4-charts dependency

Closed in favour of: https://github.com/kubevirt/web-ui/pull/309


exclude docker0/ virtual eth from IP check and DHCP check

for users that do more with their raspiblitz ;)

@phenomeus I am rejecting the #1337 PR because it was targeted to master branch instead to v1.6 branch and changing the base to v1.6 for that PR already had too many merge conflicts. But no worry - I made the changes to the local IP detection again on the v1.6 branch and with this commit: https://github.com/rootzoll/raspiblitz/commit/9c99093574ecb3106dbdec933e31c4388e8c44ea ... so consider this merged :)


Remove gulp and rely on a simple npm script

Type of PR

[x] Documentation changes
I checked the readme.md and there is no mention of gulp. It was an implementation detail. The tsc command is executed as part of the npm build script that happens in the docker build. The audience of the readme shouldn't need to know about that.

[x] Code changes

[ ] Test changes

[ ] CI-CD changes

[ ] GitHub Template changes

Purpose of PR
Review notes
Issues Closed or Referenced

Closes #95

Funny you should ask. I determined that there were no changes in there that necessitated a change to the package-lock.json yet it showed up in my original commit as a changed file. I jumped through hoops to rebase the changes such that the package-lock was not a part of the PR. I hope I was right about that. I see the value of package-lock, but it sure drives me nuts.

@tobiaswright, regarding adding a build-watch task... yes.
Regarding adding linting to the build task, I would recommend we keep a pure lint, a pure build, a pure test, etc. and then either add composite tasks (like lint-build) if it's for dev convenience or simple call multiple scripts if we're doing it through a pipeline or in a Dockerfile.


DOC: Not properly aligned the content and updated photos are not add

What's wrong with the existing documentation
Not properly aligned the content and updated photos are not add in the readme
Please assign me under #gssoc24
Add ScreenShots
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign this task to me under GSSOC'24

It will be updated after the program ends.


gopass*: build with Go with CL417615

gopass fails to build with 1.18.4 due to
https://github.com/gopasspw/gopass/issues/2280.
Apply the revert from upstream CL411617, CL417615.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I don't agree with merging this but I assume you will merge it anyway.

I don't agree with merging this but I assume you will merge it anyway.

No :-D The main idea here is to unbreak the gopass attribute. We can use 1.18.4, but applying the backport queued for 1.18.5. That's probably still less obstrusive than a big rebuild due to applying it for all of go 1.18.4.
I'll update the PR.

Can you do this:

apply the backport here for gopass
apply the backport on staging for go
revert the gopass from this PR backport on staging

This now properly includes the revert for CL411617, CL417615.
Once that's merged, and master merged into staging, happy to send a PR there reverting this commit and shipping the patch in the go 1.18 expression itself.

@ofborg build gopass git-credential-gopass gopass-hibp gopass-jsonapi gopass-summon-provider

Can you do this:
* apply the backport here for `gopass`

* apply the backport on `staging` for `go`

* revert the `gopass` backport from this PR on `staging`

PR applying this to go_1_18 directly, then reverting this commit is at https://github.com/NixOS/nixpkgs/pull/182839.


warp-packer windows-x64 on linux

Tried to run the following command on Ubuntu 18.04:
warp-packer --arch windows-x64 --input_dir ./bin/Release/netcoreapp2.2/win-x64/publish --exec nvidia-dicom.exe --output nvidia-dicom.exe
and got the following error:

Downloading runner from https://github.com/dgiagio/warp/releases/download/v0.1.1/windows-x64.warp-runner...
Error: Inner { kind: ClientError(404), url: Some("https://github.com/dgiagio/warp/releases/download/v0.1.1/windows-x64.warp-runner") }

Q: is this supported? packing a Windows build on Linux or vice versa?
Also, the link printed with the error points to 404 page.

It seems like the URL is missing the ".exe" extension in this case (probably because it thinks its a linux binary, running on linux).


Add prelude

Instead of importing lots of submodules, maybe offer a prelude to easily import most important stuff.

Done in f28ac264f11155eb1fc1e90019f8c55c726247a3.


GACGD instead of ACGD?

I noticed that the GMRES-based CGDs.GACGD optimizer (general sum game) is used instead of  the CGDs.ACGD optimizer (zero-sum game), even though CPINNs play zero-sum games. I also find that the ACGD is slightly faster (at least in the initial learning phase).
Is there any particular reason why GACGD is used? Probably because it results in a lower L2 error?

In our experiments we found the GMRES-based version of ACGD takes less number of forward passes to solve for the matrix inverse than the CG-based ACGD. GMRES-based version of ACGD also reaches lower L2 error than


feat(312): support adding comment in test run request

Relates to #312
Adding comment support for test runs as an optional property.

@dimitriharding thank you for contribution!


Vite fails to build/run because of "global is not defined"

🐛 Bug Report
Uncaught ReferenceError: global is not defined when running dev mode with https://vitejs.dev/.
For the build i may use the solution from https://github.com/gilbarbara/react-floater/issues/75
I also get the error Cannot call a namespace ('equal') during build, but i can't finde out if it is related to react-floater or react-joyride.
To Reproduce
Steps to reproduce the behavior:

Create a new project with https://vitejs.dev/
Try to use https://github.com/gilbarbara/react-joyride (which depends on react-floater)

Expected behavior
Should run/build

I am getting both of those error with Vite app. Have you had any progress with it? I will dig around a bit and report back if I find something useful.

Hello, I created a repo, where I tested this.
react-floater@latest - https://github.com/Pernick/react-floater-global-not-defined/tree/floater-latest

global is not defined error is seen here

react-floater@next - https://github.com/Pernick/react-floater-global-not-defined/tree/floater-next

global is not defined no longer her
equal3 is not a function error is new here

I am unfortunately busy right now with different task, so I put this in a background for a bit, but hopefully I can get to it this evening.

Just ran into this issue, too. I tried to enable various polyfills without any success with Vite.

Fixed in 0.8.0

In 0.8.0 I am getting equal3 is not a function

Getting same problem in 0.8.0 Uncaught TypeError: equal3 is not a function

Getting same problem in 0.8.0 Uncaught TypeError: equal3 is not a function

This is issue was about the global variable...


Ollama: parameters and instruction templates

Issue with current documentation:
It's not clear from the documentation whether when calling Ollama, langchain will take care of formatting the template correctly or if I have to supply the template by myself.
For example, in https://ollama.ai/library/mistral:instruct
we have:
parameter
stop "[INST]"
stop "[/INST]"
stop "<<SYS>>"
stop "<</SYS>>"

template
[INST] {{ .System }} {{ .Prompt }} [/INST]

Do I have to take care of formatting my instructions using these parameters and template, or langchain will take care of it?
Idea or request for content:
If this is not implemented, would be very useful to have definitely

@dosubot, what is the difference between ChatOllama and Ollama? In the documentation I've seen mentioned only the Ollama class..

To add to the discussion, if you are using ChatPromptTemplate to supply a history of messages, you should use ChatOllama and not Ollama.
from langchain.chat_models import ChatOllama
from langchain_core.prompts import ChatPromptTemplate

llm = ChatOllama(model="mistral:instruct")

prompt = ChatPromptTemplate.from_messages(
    [
        ("human", "When was Abraham Lincoln born?"),
        ("ai", "Abraham Lincoln was born on February 12, 1809."),
        ("human", "How old was he when he died?"),
        ("ai", "Abraham Lincoln died on April 15, 1865, at the age of 56."),
        ("human", "{question}"),
    ]
)

chain = prompt | llm

ans = chain.invoke({"question":"Where did he die?"})

print(ans)

This will send the correct API request. I verified this with tcpdump.
{
    "messages": [
        {
            "role": "user",
            "content": "When was Abraham Lincoln born?",
            "images": []
        },
        {
            "role": "assistant",
            "content": "Abraham Lincoln was born on February 12, 1809.",
            "images": []
        },
        {
            "role": "user",
            "content": "How old was he when he died?",
            "images": []
        },
        {
            "role": "assistant",
            "content": "Abraham Lincoln died on April 15, 1865, at the age of 56.",
            "images": []
        },
        {
            "role": "user",
            "content": "Where did he die?",
            "images": []
        }
    ],
    "model": "mistral:instruct",
    "format": null,
    "options": {
        "mirostat": null,
        "mirostat_eta": null,
        "mirostat_tau": null,
        "num_ctx": null,
        "num_gpu": null,
        "num_thread": null,
        "num_predict": null,
        "repeat_last_n": null,
        "repeat_penalty": null,
        "temperature": null,
        "stop": [],
        "tfs_z": null,
        "top_k": null,
        "top_p": null
    },
    "system": null,
    "template": null
}

In the same situation if you use Ollama the request will look like this.
{
    "prompt": "Human: When was Abraham Lincoln born?\nAI: Abraham Lincoln was born on February 12, 1809.\nHuman: How old was he when he died?\nAI: Abraham Lincoln died on April 15, 1865, at the age of 56.\nHuman: Where did he die?",
    "images": null,
    "model": "mistral:instruct",
    "format": null,
    "options": {
        "mirostat": null,
        "mirostat_eta": null,
        "mirostat_tau": null,
        "num_ctx": null,
        "num_gpu": null,
        "num_thread": null,
        "num_predict": null,
        "repeat_last_n": null,
        "repeat_penalty": null,
        "temperature": null,
        "stop": [],
        "tfs_z": null,
        "top_k": null,
        "top_p": null
    },
    "system": null,
    "template": null
}

This may or may not work well depending on the target model. But this is not an ideal situation. ChatOllama will work better.


PayPal creates salt for nonces longer than 40 chars

PayPal recently upgraded their OpenID service, and as part of this update they now use very long salt values, for example, "0e00b1a53a40de0a558c8378b4c51f3d58e4b90d845292226741797e9edb8dcb". This string is longer than 40 characters and thus does not work with current nonce salt column which is set to 40 characters.
The fix is to change "salt CHAR(40)" to something larger (I'm using "salt CHAR(80)") in the following files:
Auth/OpenID/MDB2Store.php (also need to change "salt" => array(... "length" => 40,...);)
Auth/OpenID/MySQLStore.php
Auth/OpenID/PostgreSQLStore.php
Auth/OpenID/SQLiteStore.php

This repo is being archived. Closing issue.


Add August blog post

Signed-off-by: Daniel Holbach<EMAIL_ADDRESS>

→ https://deploy-preview-435--fluxcd.netlify.app/blog/2021/08/august-2021-update/
Can you please land it on Monday and then work through the Comms Plan doc to get the word out? (As I'll be off...)
cc @alisondy @scottrigby @staceypotter


Is there sample code that show how to implement RSA_meth_new() series of functions used in an engine to a provider?

Since the ENGINE interface is depreciated in 3.0, is there a sample code that show how to make a conversion from an engine code to an provider like the used of RAS_meth_new()?

I'd start by reading these two pages:
https://www.openssl.org/docs/manmaster/man7/provider.html
https://www.openssl.org/docs/manmaster/man7/provider-base.html
There is an example provider on the second of those pages.

I have read that and have implemented a simple RNG provider, that works. For this RSA method, let's say I just need to replace the bn_mod_exp method function, I am having a hard time to find a suitable entry point in provider. Is there anyway the existing code in bn_mod_exp could be reused, or it is totally not usable under current provider?

Unfortunately there is no simple way how to modify only some part of the RSA implementation via a new provider. You would have to do a whole new RSA implementation in the provider.


Pass content of messages to helper functions, Add new UI_ types, Add read of params table

ok, so whilst updating the wiki, I was thinking about how to make the protocol a little more accessible.  Thought that ability to read information ABOUT the protocol, using the protocol, may be useful; how useful I'm not entirely sure.
Anyway, that lead me to this PR.
Main features:
1/ it passes the msg content to the helper functions, as well as the content len.  This allows us to pass parameters into read - for example to read an entry in an array (what i needed to read the params entries).
2/ Adds more UI_ defines, and a suggested structure for how to define them.
3/ adds human descriptions for each params entry (make it easier to get into?).
4/ adds a params entry which allows you to read (using the protocol) entries from the params table, getting variable type (UI_ define), variable size, and description.  You can read from a 'first' entry for a count, and it will try to fill a message, which will include first, and the actual count it fitted in.
I'm not sure 4/ is actually useful (unless more variables are of simple type), but it's a good illustration of use of the new content passing.
@p-h-a-i-l  - your thoughts; as you use this at both ends....  I've tested, and the protocol still works :), as does the new function

Main features:
1/ it passes the msg content to the helper functions, as well as the content len. This allows us to pass parameters into read - for example to read an entry in an array (what i needed to read the params entries).

Uh, wow. Nice feature, didn't think about that. Now that we have it, I want it :)

2/ Adds more UI_ defines, and a suggested structure for how to define them.

Cannot contribute a lot as I only use the ASCII protocol for debugging and testing- Probably useful :+1:

3/ adds human descriptions for each params entry (make it easier to get into?).

Very good, much needed.

4/ adds a params entry which allows you to read (using the protocol) entries from the params table, getting variable type (UI_ define), variable size, and description. You can read from a 'first' entry for a count, and it will try to fill a message, which will include first, and the actual count it fitted in.

I like it. This way we can validate if a specific capability is available on the other side. (Ok, this would also be possible by reading and chekcing for a response, but I was already thinking about adding 10 empty spots to params which can be filled dynamically at runtime)


Upgrade versions in version.json

Description

Upgrade versions in version.json
Jira Ticket

Changes

Breaking Changes

-<EMAIL_ADDRESS>Checks

[ ] Project Builds
[ ] Project passes tests and checks
[ ] Updated documentation accordingly
[ ] Breaking changes have been correctly tagged and notified, and reported into the release notes in doc folder

Additional information

closing this PR, will be done by SDK team


AssignTargetPath task is not deterministic

If an EmbeddedResource has Link metadata set to a full path, AssignTargetPath task uses this full path as the value of EmbeddedResource.TargetPath metadata, which in turn is used by CreateCSharpManifestResourceName task to calculate a ManifestResourceName. This value is used as a resource name in the assembly metadata.
This makes the content of the built binaries dependent on the directory the repository was built from.
In addition AssignTargetPath task calls Directory.GetCurrentDirectory().
Note: xliff-build task sets Link to a full path: https://github.com/dotnet/xliff-tasks/blob/master/src/XliffTasks/Tasks/GatherTranslatedSource.cs#L49
Steps to reproduce
Build the following project:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <EmbeddedResource Include="..\Resources\Resources.resx" Link="$(MSBuildThisFileDirectory)..\Resources\Resources.resx" />
  </ItemGroup>
</Project>

Directory contents:
C:\temp\repro\Resources\Resources.resx // some resources
C:\temp\repro\ClassLibrary1\ClassLibrary1.csproj

Command line
msbuild /bl

Actual behavior
The .resources file generated to obj directory includes the full (sanitized) path:
ClassLibrary1.C_.Temp.repro.ClassLibrary1....Resources.Resources.resources
which also ends up being the manifest resource name embedded in the assembly:

Expected behavior
The manifest resource name does not include the full path.
Environment data
msbuild /version output:
Microsoft (R) Build Engine version 16.6.0-preview-20110-08+b2a011d16 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.

<IP_ADDRESS>08

I was sure that I saw code in MSBuild make sure that the current path was always set to the current project.

Two questions:

Do you have a priority on this?
Should the fix be to teach CreateCSharpManifestResourceName to respect the path-prefix-stripping option that the compiler does?


lockToLandscape() applies landscape mode for the previous screen

I have component A which I set to portrait mode:
class A extends Component {
    ...
    componentDidMount(){
        Orientation.lockToPortrait();
    }
}

I press some button and open component B which I set to landscape mode:
class B extends Component{
    ...
    componentDidMount(){
        Orientation.lockToLandscape();
    }
}

When I press hardware BACK button on Android I see component A in the landscape mode.
Any suggestions? Please help me.

@valerybodak I dealt with that in one of my applications too, my workaround was to have a Orientation.lockToPortrait() call running together with my navigator.pop() call so that I force the Portrait orientation when routing back to my previous screen.

@andrerfneves
Yes. it works for Android. Thank you.

Glad it worked. Closing this as there is a known workaround.


Undefined __atomic_* symbols when cross-compiling OpenSSL 1.1.1t to 32-bit ARM using Zig toolchains

I have installed Zig 0.10.1 on x86_64 Linux host,
cloned OpenSSL repository and checked out OpenSSL_1_1_1t tag.
I created the following script outside the tree:
#!/bin/sh
TARGET=arm-linux-musleabi
export CC="zig cc -target $TARGET"
export CXX="zig c++ -target $TARGET"
export LD="zig cc -target $TARGET"
export AR="zig ar"
export RANLIB="zig ranlib"
./Configure -no-tests linux-armv4
make -j4

When running this script, I get the following errors:
...
${LDCMD:-zig cc -target arm-linux-musleabi} -pthread -Wa,--noexecstack -Qunused-arguments -Wall -O3 -L.   \
        -o apps/openssl apps/asn1pars.o apps/ca.o apps/ciphers.o apps/cms.o apps/crl.o apps/crl2p7.o apps/dgst.o apps/dhparam.o apps/dsa.o apps/dsaparam.o apps/ec.o apps/ecparam.o apps/enc.o apps/engine.o apps/errstr.o apps/gendsa.o apps/genpkey.o apps/genrsa.o apps/nseq.o apps/ocsp.o apps/openssl.o apps/passwd.o apps/pkcs12.o apps/pkcs7.o apps/pkcs8.o apps/pkey.o apps/pkeyparam.o apps/pkeyutl.o apps/prime.o apps/rand.o apps/rehash.o apps/req.o apps/rsa.o apps/rsautl.o apps/s_client.o apps/s_server.o apps/s_time.o apps/sess_id.o apps/smime.o apps/speed.o apps/spkac.o apps/srp.o apps/storeutl.o apps/ts.o apps/verify.o apps/version.o apps/x509.o \
         apps/libapps.a -lssl -lcrypto -ldl -pthread
ld.lld: error: undefined symbol: __atomic_store
>>> referenced by ssl_cert.c:60 (ssl/ssl_cert.c:60)
>>>               ssl_cert.o:(ssl_cert_new) in archive ./libssl.a
>>> referenced by ssl_cert.c:84 (ssl/ssl_cert.c:84)
>>>               ssl_cert.o:(ssl_cert_dup) in archive ./libssl.a
>>> referenced by ssl_lib.c:695 (ssl/ssl_lib.c:695)
>>>               ssl_lib.o:(SSL_new) in archive ./libssl.a
>>> referenced 15 more times

ld.lld: error: undefined symbol: __atomic_fetch_sub_4
>>> referenced by refcount.h:50 (include/internal/refcount.h:50)
>>>               ssl_cert.o:(ssl_cert_free) in archive ./libssl.a
>>> referenced by refcount.h:50 (include/internal/refcount.h:50)
>>>               ssl_lib.o:(SSL_free) in archive ./libssl.a
>>> referenced by refcount.h:50 (include/internal/refcount.h:50)
>>>               ssl_lib.o:(SSL_CTX_free) in archive ./libssl.a
>>> referenced 14 more times

ld.lld: error: undefined symbol: __atomic_fetch_add_4
>>> referenced by refcount.h:34 (include/internal/refcount.h:34)
>>>               ssl_lib.o:(SSL_new) in archive ./libssl.a
>>> referenced by refcount.h:34 (include/internal/refcount.h:34)
>>>               ssl_lib.o:(SSL_new) in archive ./libssl.a
>>> referenced by refcount.h:34 (include/internal/refcount.h:34)
>>>               ssl_lib.o:(SSL_CTX_up_ref) in archive ./libssl.a
>>> referenced 26 more times

ld.lld: error: undefined symbol: __atomic_load
>>> referenced by bio_lib.c:689 (crypto/bio/bio_lib.c:689)
>>>               bio_lib.o:(BIO_free_all) in archive ./libcrypto.a
>>> referenced by bio_lib.c:689 (crypto/bio/bio_lib.c:689)
>>>               bio_lib.o:(BIO_dup_chain) in archive ./libcrypto.a
>>> referenced by eng_ctrl.c:133 (crypto/engine/eng_ctrl.c:133)
>>>               eng_ctrl.o:(ENGINE_ctrl) in archive ./libcrypto.a

ld.lld: error: undefined symbol: __atomic_is_lock_free
>>> referenced by threads_pthread.c:166 (crypto/threads_pthread.c:166)
>>>               threads_pthread.o:(CRYPTO_atomic_add) in archive ./libcrypto.a
make[1]: *** [Makefile:6334: apps/openssl] Error 1

...

Here is the output of perl configdata.pm --dump:

Command line (with current working directory = .):

    /usr/bin/perl ./Configure -no-tests linux-armv4

Perl information:

    /usr/bin/perl
    5.36.0 for x86_64-linux-thread-multi

Enabled features:

    afalgeng
    aria
    asm
    async
    autoalginit
    autoerrinit
    autoload-config
    bf
    blake2
    camellia
    capieng
    cast
    chacha
    cmac
    cms
    comp
    ct
    deprecated
    des
    dgram
    dh
    dsa
    dso
    dtls
    dynamic-engine
    ec
    ec2m
    ecdh
    ecdsa
    engine
    err
    filenames
    gost
    hw(-.+)?
    idea
    makedepend
    md4
    mdc2
    multiblock
    nextprotoneg
    pinshared
    ocb
    ocsp
    pic
    poly1305
    posix-io
    psk
    rc2
    rc4
    rdrand
    rfc3779
    rmd160
    scrypt
    seed
    shared
    siphash
    sm2
    sm3
    sm4
    sock
    srp
    srtp
    sse2
    ssl
    static-engine
    stdio
    threads
    tls
    ts
    ui-console
    whirlpool
    tls1
    tls1-method
    tls1_1
    tls1_1-method
    tls1_2
    tls1_2-method
    tls1_3
    dtls1
    dtls1-method
    dtls1_2
    dtls1_2-method

Disabled features:

    asan                    [default] OPENSSL_NO_ASAN
    buildtest-c++           [default]
    crypto-mdebug           [default] OPENSSL_NO_CRYPTO_MDEBUG
    crypto-mdebug-backtrace [default] OPENSSL_NO_CRYPTO_MDEBUG_BACKTRACE
    devcryptoeng            [default] OPENSSL_NO_DEVCRYPTOENG
    ec_nistp_64_gcc_128     [default] OPENSSL_NO_EC_NISTP_64_GCC_128
    egd                     [default] OPENSSL_NO_EGD
    external-tests          [default] OPENSSL_NO_EXTERNAL_TESTS
    fuzz-libfuzzer          [default] OPENSSL_NO_FUZZ_LIBFUZZER
    fuzz-afl                [default] OPENSSL_NO_FUZZ_AFL
    heartbeats              [default] OPENSSL_NO_HEARTBEATS
    md2                     [default] OPENSSL_NO_MD2 (skip crypto/md2)
    msan                    [default] OPENSSL_NO_MSAN
    rc5                     [default] OPENSSL_NO_RC5 (skip crypto/rc5)
    sctp                    [default] OPENSSL_NO_SCTP
    ssl-trace               [default] OPENSSL_NO_SSL_TRACE
    tests                   [option]  OPENSSL_NO_TESTS
    ubsan                   [default] OPENSSL_NO_UBSAN
    unit-test               [default] OPENSSL_NO_UNIT_TEST
    weak-ssl-ciphers        [default] OPENSSL_NO_WEAK_SSL_CIPHERS
    zlib                    [default]
    zlib-dynamic            [default]
    ssl3                    [default] OPENSSL_NO_SSL3
    ssl3-method             [default] OPENSSL_NO_SSL3_METHOD

Config target attributes:

    AR => "ar",
    ARFLAGS => "r",
    CC => "gcc",
    CFLAGS => "-Wall -O3",
    CXX => "g++",
    CXXFLAGS => "-Wall -O3",
    HASHBANGPERL => "/usr/bin/env perl",
    RANLIB => "ranlib",
    RC => "windres",
    aes_asm_src => "aes_cbc.c aes-armv4.S bsaes-armv7.S aesv8-armx.S",
    aes_obj => "aes_cbc.o aes-armv4.o bsaes-armv7.o aesv8-armx.o",
    apps_aux_src => "",
    apps_init_src => "",
    apps_obj => "",
    bf_asm_src => "bf_enc.c",
    bf_obj => "bf_enc.o",
    bn_asm_src => "bn_asm.c armv4-mont.S armv4-gf2m.S",
    bn_obj => "bn_asm.o armv4-mont.o armv4-gf2m.o",
    bn_ops => "BN_LLONG RC4_CHAR",
    build_file => "Makefile",
    build_scheme => [ "unified", "unix" ],
    cast_asm_src => "c_enc.c",
    cast_obj => "c_enc.o",
    cflags => "-pthread",
    chacha_asm_src => "chacha-armv4.S",
    chacha_obj => "chacha-armv4.o",
    cmll_asm_src => "camellia.c cmll_misc.c cmll_cbc.c",
    cmll_obj => "camellia.o cmll_misc.o cmll_cbc.o",
    cppflags => "",
    cpuid_asm_src => "armcap.c armv4cpuid.S",
    cpuid_obj => "armcap.o armv4cpuid.o",
    cxxflags => "-std=c++11 -pthread",
    defines => [  ],
    des_asm_src => "des_enc.c fcrypt_b.c",
    des_obj => "des_enc.o fcrypt_b.o",
    disable => [  ],
    dso_extension => ".so",
    dso_scheme => "dlfcn",
    ec_asm_src => "ecp_nistz256.c ecp_nistz256-armv4.S",
    ec_obj => "ecp_nistz256.o ecp_nistz256-armv4.o",
    enable => [ "afalgeng" ],
    ex_libs => "-ldl -pthread",
    exe_extension => "",
    includes => [  ],
    keccak1600_asm_src => "keccak1600-armv4.S",
    keccak1600_obj => "keccak1600-armv4.o",
    lflags => "",
    lib_cflags => "",
    lib_cppflags => "-DOPENSSL_USE_NODELETE",
    lib_defines => [  ],
    md5_asm_src => "",
    md5_obj => "",
    modes_asm_src => "ghash-armv4.S ghashv8-armx.S",
    modes_obj => "ghash-armv4.o ghashv8-armx.o",
    module_cflags => "-fPIC",
    module_cxxflags => "",
    module_ldflags => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    padlock_asm_src => "",
    padlock_obj => "",
    perlasm_scheme => "linux32",
    poly1305_asm_src => "poly1305-armv4.S",
    poly1305_obj => "poly1305-armv4.o",
    rc4_asm_src => "rc4_enc.c rc4_skey.c",
    rc4_obj => "rc4_enc.o rc4_skey.o",
    rc5_asm_src => "rc5_enc.c",
    rc5_obj => "rc5_enc.o",
    rmd160_asm_src => "",
    rmd160_obj => "",
    sha1_asm_src => "sha1-armv4-large.S sha256-armv4.S sha512-armv4.S",
    sha1_obj => "sha1-armv4-large.o sha256-armv4.o sha512-armv4.o",
    shared_cflag => "-fPIC",
    shared_defflag => "-Wl,--version-script=",
    shared_defines => [  ],
    shared_extension => ".so.\$(SHLIB_VERSION_NUMBER)",
    shared_extension_simple => ".so",
    shared_ldflag => "-Wl,-znodelete -shared -Wl,-Bsymbolic",
    shared_rcflag => "",
    shared_sonameflag => "-Wl,-soname=",
    shared_target => "linux-shared",
    thread_defines => [  ],
    thread_scheme => "pthreads",
    unistd => "<unistd.h>",
    uplink_aux_src => "",
    uplink_obj => "",
    wp_asm_src => "wp_block.c",
    wp_obj => "wp_block.o",

Recorded environment:

    AR = zig ar
    ARFLAGS =
    AS =
    ASFLAGS =
    BUILDFILE =
    CC = zig cc -target arm-linux-musleabi
    CFLAGS =
    CPP =
    CPPDEFINES =
    CPPFLAGS =
    CPPINCLUDES =
    CROSS_COMPILE =
    CXX = zig c++ -target arm-linux-musleabi
    CXXFLAGS =
    HASHBANGPERL =
    LD = zig cc -target arm-linux-musleabi
    LDFLAGS =
    LDLIBS =
    MT =
    MTFLAGS =
    OPENSSL_LOCAL_CONFIG_DIR =
    PERL =
    RANLIB = zig ranlib
    RC =
    RCFLAGS =
    RM =
    WINDRES =
    __CNF_CFLAGS =
    __CNF_CPPDEFINES =
    __CNF_CPPFLAGS =
    __CNF_CPPINCLUDES =
    __CNF_CXXFLAGS =
    __CNF_LDFLAGS =
    __CNF_LDLIBS =

Makevars:

    AR              = zig ar
    ARFLAGS         = r
    CC              = zig cc -target arm-linux-musleabi
    CFLAGS          = -Wall -O3
    CPPDEFINES      =
    CPPFLAGS        =
    CPPINCLUDES     =
    CXX             = zig c++ -target arm-linux-musleabi
    CXXFLAGS        = -Wall -O3
    HASHBANGPERL    = /usr/bin/env perl
    LD              = zig cc -target arm-linux-musleabi
    LDFLAGS         =
    LDLIBS          =
    PERL            = /usr/bin/perl
    RANLIB          = zig ranlib
    RC              = windres
    RCFLAGS         =

NOTE: These variables only represent the configuration view.  The build file
template may have processed these variables further, please have a look at the
build file for more exact data:
    Makefile

build file:

    Makefile

build file templates:

    Configurations/common0.tmpl
    Configurations/unix-Makefile.tmpl
    Configurations/common.tmpl

I also tried OpenSSL_1_1_1l and it has similar problems.
I also tried OpenSSL 3 on the master branch (commit<PHONE_NUMBER>64b5a9bb09711de8e885fef546a0ac). I got this error at the attempt of linking libcrypto.so.3:
LLD Link... ld.lld: error: unable to find library -latomic

zig toolchains don't provide cross-complied libatomic.
There is a similar issue https://github.com/openssl/openssl/issues/16551 where @ecnepsnai says the bug was resolved, but apparently now -libatomic is required.
In any case, I would like to be able to cross-compile OpenSSL 1.1.1t using zig musl toolchain, is it possible?
There was an attempt to get rid of atomics at https://github.com/openssl/openssl/pull/16584 but apparently it is stalled.

We don't just use __GNUC__, the check is:
defined(__GNUC__) && defined(__ATOMIC_RELAXED) && __GCC_ATOMIC_INT_LOCK_FREE > 0.
Most likely, by default you get the C11 version of the code. On an architecture like armv4 that does not have native atomic support, this requires library support, which is actually implemented with the help of the kernel.
If you don't use the C11 atomics, you will probably fall back to the intrinsics, which really is just the same.
You now seem to completely disable the use of atomics, and fall back to to using a lock, which will be slower than what is possible with the help of the kernel.
You really should look fixing your setup so that atomics work.

@link2xt So if this is an issue with Zig, can this GitHub issue be closed?


[HIPIFY] Errors when processing the NVIDIA sample "simpleSurfaceWrite"

Ran hipify-clang /path/to/NVIDIA_CUDA-10.2_Samples/0_Simple/simpleSurfaceWrite/simpleSurfaceWrite.cu --skip-excluded-preprocessor-conditional-blocks  -- -I/path/to/NVIDIA_CUDA-10.2_Samples/common/inc and got error:
warning: Unknown CUDA version 10.2. Assuming the latest supported version 10.1 [-Wunknown-cuda-version]
/tmp/simpleSurfaceWrite.cu-8cd6ee.hip:226:21: warning: CUDA identifier is deprecated.
    checkCudaErrors(cudaMemcpyToArray(cuArray,
                    ^
/tmp/simpleSurfaceWrite.cu-8cd6ee.hip:68:5: error: use of undeclared identifier 'surf2Dwrite'
    surf2Dwrite(gIData[y * width + x],
    ^
In file included from <built-in>:1:
In file included from /usr/lib/llvm-10/lib/clang/10.0.1/include/__clang_cuda_runtime_wrapper.h:324:
/usr/local/cuda-10.2/include/texture_indirect_functions.h:145:4: error: use of undeclared identifier '__nv_tex_surf_handler'
   __nv_tex_surf_handler("__itex2D", ptr, obj, x, y);
   ^
/usr/local/cuda-10.2/include/texture_indirect_functions.h:154:3: note: in instantiation of function template specialization 'tex2D<float>' requested here
  tex2D(&ret, texObject, x, y);
  ^
/tmp/simpleSurfaceWrite.cu-8cd6ee.hip:96:29: note: in instantiation of function template specialization 'tex2D<float>' requested here
    gOData[y * width + x] = tex2D<float>(tex, tu, tv);
                            ^
1 warning and 2 errors generated when compiling for host.
Error while processing /tmp/simpleSurfaceWrite.cu-8cd6ee.hip.

The issue is because __nv_tex_surf_handler built-in is still not implemented in clang. Here is the latest activity on the subject: https://reviews.llvm.org/D76365. Mark this bug as clang specific bug.

Duplicate of #134

The original bug: https://bugs.llvm.org/show_bug.cgi?id=26400, which was finally fixed in clang only in Sept 2021 by https://reviews.llvm.org/D110089.
hipify-clang should be built against trunk LLVM 14.0.0git.
The command line to test:
hipify-clang --print-stats --cuda-path="c:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.5" "c:\ProgramData\NVIDIA Corporation\CUDA Samples\v11.5/0_Simple/simpleSurfaceWrite/simpleSurfaceWrite.cu" --skip-excluded-preprocessor-conditional-blocks -I"c:\ProgramData\NVIDIA Corporation\CUDA Samples\v11.5\common\inc" -- -D_ALLOW_COMPILER_AND_STL_VERSION_MISMATCH

Output:
C:\Users\TT\AppData\Local\Temp\simpleSurfaceWrite.cu-ee3765.hip:228:21: warning: CUDA identifier is deprecated.
    checkCudaErrors(cudaMemcpyToArray(cuArray,
                    ^
1 warning generated when compiling for host.

[HIPIFY] info: file 'c:\ProgramData\NVIDIA Corporation\CUDA Samples\v11.5/0_Simple/simpleSurfaceWrite/simpleSurfaceWrite.cu' statistics:
  CONVERTED refs count: 48
  UNCONVERTED refs count: 0
  CONVERSION %: 100.0
  REPLACED bytes: 981
  TOTAL bytes: 11425
  CHANGED lines of code: 41
  TOTAL lines of code: 318
  CODE CHANGED (in bytes) %: 8.6
  CODE CHANGED (in lines) %: 12.9
  TIME ELAPSED s: 12.11
[HIPIFY] info: CONVERTED refs by type:
  device: 3
  memory: 7
  texture: 3
  surface: 2
  device_function: 4
  include_cuda_main_header: 1
  type: 13
  numeric_literal: 11
  define: 1
  kernel_launch: 3
[HIPIFY] info: CONVERTED refs by API:
  CUDA RT API: 48
[HIPIFY] info: CONVERTED refs by names:
  cosf: 2
  cudaAddressModeWrap: 2
  cudaArray: 1
  cudaArraySurfaceLoadStore: 1
  cudaBoundaryModeTrap: 1
  cudaChannelFormatDesc: 1
  cudaChannelFormatKindFloat: 1
  cudaCreateChannelDesc: 1
  cudaCreateSurfaceObject: 1
  cudaCreateTextureObject: 1
  cudaDestroySurfaceObject: 1
  cudaDestroyTextureObject: 1
  cudaDeviceProp: 1
  cudaDeviceSynchronize: 2
  cudaFilterModeLinear: 1
  cudaFree: 1
  cudaFreeArray: 1
  cudaGetDeviceProperties: 1
  cudaLaunchKernel: 3
  cudaMalloc: 1
  cudaMallocArray: 1
  cudaMemcpy: 2
  cudaMemcpyDeviceToHost: 1
  cudaMemcpyHostToDevice: 2
  cudaMemcpyToArray: 1
  cudaReadModeElementType: 1
  cudaResourceDesc: 4
  cudaResourceTypeArray: 2
  cudaSurfaceObject_t: 2
  cudaTextureDesc: 2
  cudaTextureObject_t: 2
  cuda_runtime.h: 1
  sinf: 2


Leveraging SystemD to replace nohop for binary(rpm/deb) package

There is no way to detect/know the status of each service in the current demonization implementation
Logging could be revisited(now in /root/logs)

supported


Another bugfix.

Fixes #2844.
Also, @aidancbrady you probably should release a 8.1.7 soon with the bugfixes. This is the second bug that crashes minecraft in singleplayer (bin bug was first), and will pretty much crash any server which uses logistical sorters on anything that uses sided inventories.

Thanks!


[Feature Request & question] Accessing Dom element in onStart() & onRest()

Hello, thank you for this amazing and wonderful library!
I have a small idea but I don't know if it is appropriate.
Right now, I want to animate transform scale 1 to 1.2, and I want to set opacity at beginning and end.
It looks like this.

class Example extends Component {
  constructor(props) {
    super(props);
    this.ref = React.createRef();
  }

  render() {
    return (
      <Spring
        native
        from={{ transform: 'scale(1)' }}
        to={{ transform: 'scale(1.2)' }}
        onStart={() => {
          this.ref.current.node.style.opacity = 1;
        }}
        onRest={() => {
          this.ref.current.node.style.opacity = 0;
        }}
      >
        {transformStyle => (
          <animated.div ref={this.ref} style={transformStyle} />
        )}
      </Spring>
    );
  }
}

export default Example;

I was wondering if we can have dom element passed into onStart() and onRest() function, and we can now have code like this.
const Example = () => {
  return (
    <Spring
      native
      from={{ transform: 'scale(1)' }}
      to={{ transform: 'scale(1.2)' }}
      onStart={element => { // dom element passed, no need to set ref additionally
        element.style.opacity = 1;
      }}
      onRest={element => {
        element.style.opacity = 0;
      }}
    >
      {transformStyle => <animated.div ref={this.ref} style={transformStyle} />}
    </Spring>
  );
};

Thank you for your listening!

@lasseborly Wow, Keyframe is a wonderful feature in react-spring.
Thank you for providing the beautiful example for me.


Fixed PWM for ECAP (P9_28 and P9_42)

Hi,
Latest master is not working with kernel 4.4.* when pins P9_28 and P9_42 are used so I created fix for that. P9_28 wants that pin mode is pwm2 instead of pwm and in bone.js P9_28 index was 2 when correct index is 0 as ecaps are having only 1 outputs both. I used several days to get all 8 pwm channels working at the same time so if somebody is trying to achieve same, I am happy to help!
Br,
Janne

Coverage remained the same at 30.976% when pulling 7fee6177def213b5e98e4992dfec01a03c200bbd on jtjk:master into 23bf4431d965b33c88f4b8f185da3a8235e8862d on jadonk:master.

hi i wonder if i can contact u to talk in telegram,i have the same problem,i need 5 pwm with diferenet period,and i only got 4 of them.actualy one of that 4 keep turning off during work(p9_42),i realy need ur help

this is my telegram id ,plz msg me if u see this,plz,@Moc_Rektor

Hi, I am not using telegram, but I can help here and it will be better for community as well. What kernel version you are using? And what is your distribution? Debian Jessie?

hi,thanks for response,i just solved the pwm problem,thanks again for
feedback,i jus have a question,i need to read 4 linear encoders data,any
idea how can i do that and bring them to bbb?if answer is pru,please
explain some if possible.
thanks again
regards.
On Tue, Jan 31, 2017 at 10:52 PM, Janne Koskinen<EMAIL_ADDRESS>wrote:

Hi, I am not using telegram, but I can help here and it will be better for
community as well. What kernel version you are using? And what is your
distribution? Debian Jessie?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jadonk/bonescript/pull/143#issuecomment-276463793,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYSPW0Q2N3-g3GPWVYUW2ZmoFmuMdQjaks5rX4negaJpZM4KLEd4
.


Update bqml_vertexai_model_registry.ipynb

REQUIRED: Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.

XAI is now available for BQML models added to the Vertex AI Model Registry. This change adds an example of running XAI on the BQML model.

REQUIRED: Fill out the below checklists or remove if irrelevant

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[ ] Use the notebook template as a starting point.
[ ] Follow the style and grammar rules outlined in the above notebook template.
[ ] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[ ] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[ ] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[ ] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

If you are opening a PR for Community Notebooks under the notebooks/community folder:

[ ] This notebook has been added to the CODEOWNERS file under the Community Notebooks section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

If you are opening a PR for Community Content under the community-content folder:

[ ] Make sure your main Content Directory Name is descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content
[ ] The main content directory has been added to the CODEOWNERS file under the Community Content section, pointing to the author or the author's team.
[ ] Passes all the required formatting and linting checks. You can locally test with these instructions.

Failed: notebooks/official/model_registry/bqml_vertexai_model_registry.ipynb FAILED in 00:00:00: Expecting ',' delimiter: line 775 column 8 (char 24963)

/gcbrun

/gcbrun


mathjax in markdown

I would like to use mathematical formulas in markdown (such as readme.md) being displayed in gitea.
The Config Cheat Sheet mentions external renderers -- but using for example pandoc -f html -t markdown -mathjax doesn't seem to work as the javascript MathJax.js is not included in the head of the html document. Can you provide templates / or documentation how to achieve this?

See https://codeberg.org/Codeberg/build-deploy-gitea/commit/9532f25178438cde904bc82fc8a9ec04f821c625 for sample integration into header.tmpl

There is information at https://docs.gitea.io/en-us/customizing-gitea/ as well, above example is a simple/good one for this issue


Readme: adding gocard

Gocard includes most of the go style checking tools that we care about. This is a good indicator for us.

lgtm


Android - Error shown even when a workspace is selected on android

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to android
Create a new workspace
Click on FAB icon and click on new room
Enter the room name
On workspace, select the newly created workspace from the dropdown and notice that even when we have selected the workspace, it throws an error 'Please select a workspace'
If you again select a new workspace from the dropdown, this time no error will be shown

Expected Result:
Error should not be shown when a workspace is selected on android
Actual Result:
Error shown even when a workspace is selected on android
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.29-11
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/6cdbbd03-7a2b-4b93-aa04-010cccae4171
Expensify/Expensify Issue URL:
Issue reported by: @priya-zha
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687430155296719
View all open jobs on GitHub

Applause could not reproduce this. since neither Applause nor I could repro, I'm going to close this one.
https://github.com/Expensify/App/assets/38016013/32dcc714-2395-4812-8768-fc464ef765cf


Use provide instead of PropType<Ref<...>>

I'm already feeling much better about this pattern vs. what we had before. I think this is the right way to go.  This also allowed me to discover many new type mistakes and resovle some of the typing pain where types are lost at prop boundaries.
Before, input types weren't validated for props, now they are.

Rewrites several components in composition api
Add typescript to several plain components
Use provided state where appropriate

During this process, I found several unrelated bugs through type checking, and Vetur's template interpolation service seems to work better when you use composition api, so I even found some type-related bugs in templates.  I'm going to consider that a sign that this is the right path forward.

Updates @vue/composition/api to 1.0.0-beta-14
Minor upgrade of vuetify to 2.3.10

@BryonLewis fixed.  I'll have a follow-up PR to restructure some component trees since they're wrong according to https://vuetifyjs.com/en/components/application/#api


⚠ Bofrost.be has degraded performance

In 95debbe, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1052 ms

Resolved: Bofrost.be performance has improved in d003c58.


[New Rule] constrain use of tslint rule disabling

Apologies if this already exists, I tried googlearching, but the recursive nature of this feature made it hard to determine.
It would be great to have a tslint rule that allowed one to enforce some policy on how disabling can be used.
For our usages of tslint we generally expect to only use tslint:disable-next-line with some explicit listing of rules.  This is the most constrained/pinpoint usage of disabling.  All other forms are unused and should be replaced with the most specific form.  This is a manual code review endeavor at the moment, obviously suboptimal.
If we had such a rule, it should also support recognizing when it has been itself disabled, presumably by
one of the allowed forms of disabling.  For example:
// tslint:disable-next-line tslint-disable-policy
// tslint:disable
... defiant code here ...

I did find a related SO discussion, which could be formulated as the most restrictive form of this rule, that is disallow all forms of disabling.  https://stackoverflow.com/questions/48146695/disalow-developper-to-disable-any-tslint-rule/48146772

@ryan-gustafson not sure if you still need this, but I've implemented such a rule for a project I'm working on, the rule is provided by the italia-tslint-rules package (source code is here)

💀 It's time! 💀
TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱
If you'd like to see this change implemented, you have two choices:

Recommended: Check if this is available in ESLint + typescript-eslint ✅
Not Recommended: Fork TSLint locally 🤷♂

👋 It was a pleasure open sourcing with you!
If you believe this message was posted here in error, please comment so we can re-open the issue!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


sharedown: unbreak build, sitespeed-io: unbreak build, add passthru.updateScript, 27.3.1 -> 33.0.0

Description of changes
Those packages taunt me each time I nixpkgs-review on chromium or chromium-related work/PRs.
They have been broken for months.
This PR unbreaks them (in case of sharedown again #266866) in hope that they will continue to work from now on.
sharedown lacks a maintainer entirely, while sitespeed-io's is @Misterio77.
To make this clear: I do not intend to maintain those packages.
I just hope that it is easier due to those fixes for someone else to pick them up now.
Please see commit messages for details and motivation for each change.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

ofborg times out (1h limit) because it has to build chromium as well.
This is because I merged chromium only a few hours before creating this PR and thus chromium hasn't been built by hydra.nixos.org yet back then.
@ofborg eval
Result of nixpkgs-review pr 288928 run on x86_64-linux 1

2 packages built:

sharedown
sitespeed-io


깃허브 코멘트 테스트 스크립트 추가

dd

Pull Request Test Coverage Report for Build 199

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

Totals

Change from base Build 197:
0.0%

Covered Lines:
273

Relevant Lines:
344

💛  - Coveralls

Hello world


Random [Error unmarshalling response back from AWS]

It seem like when I return large json data from aws to client. Sometimes it will cause this error. It happen not from specific call but can happen with any large chunk of json
Expected Behavior
Never have this error
Current Behavior
This error can popped up randomly when call lambda to get data
Steps to Reproduce (for bugs)
Return a data larger than 40kb
Your Environment
AWS Lambda dotnet core as server
AWSSDK.Lambda Version 3.3.*
Amazon.Lambda.Core Version 1.0.*
Amazon.Lambda.Serialization.Json Version 1.1.*
Unity3D as client
AWSSDK.Lambda, Version=<IP_ADDRESS>
AWSSDK.CognitoIdentity, Version=<IP_ADDRESS>

Could you capture what exactly is being returned by lambda?

@sstevenkang
This is some sample of log error I got recently. It not so often but it randomly popped up

Is the reporting tool cutting off the response at the end?  If it is not doing that, it does look like an invalid json object.  Also, is there anyway you could provide the text response body instead of a screenshot?

@sstevenkang Yes the response was cut from the logger. I think the actual message was fully intact
But is it possible that the unmarshalling error would came from an invalid json?

Hmmm.  It was a guess.  There's not enough information to say.  Could you provide a small sample that repros this problem?

@sstevenkang As I was state that it would randomly came from trying to return large data from lambda server while client calling lambda.InvokeAsync


⚠ Samsung has degraded performance

In 215bb50, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2652 ms

Resolved: Samsung performance has improved in 2bdd5c0.


v1 vs v3 are not about public vs private calls, and ticker calls use obsolete API

v1 and v3 are treated as if they were related to public vs private (and widthraw) calls:
https://github.com/sammchardy/python-binance/blob/852b2561b62702524dba37926fc720a2f399de09/binance/client.py#L17-L19
I believe this is a mistake, proven by that the v1 ticker endpoints (used by the client) have been retired in favor of v3 versions with the same functionality:

v1/ticker/allPrices => v3/ticker/price
v1/ticker/allBookTickers => v3/ticker/bookTicker

#270 may be the result of undocumented changes to the (now unofficial) v1 endpoints that the client is still using:
https://github.com/sammchardy/python-binance/blob/852b2561b62702524dba37926fc720a2f399de09/binance/client.py#L407
https://github.com/sammchardy/python-binance/blob/852b2561b62702524dba37926fc720a2f399de09/binance/client.py#L438
Both of the above functions reference documentation that no longer exists.
EDIT: the v3 version is probably just an alias to v1 because it exhibits the same bug that #270 is about.

Is there any progress in this issue?


Losing params open in new tab

Version
2.7.0
Reproduction link
codepen / jsfiddle don't support open in new tab. But for the idea:
http://jsfiddle.net/yo62z2o5/
Steps to reproduce
ctrl   click on a router-link with params.
or right click -> open in tab / open in window.
What is expected?
The route opens in a new tab containing the params.
What is actually happening?
the params are empty.

You need to specify the param on the route defiintion { path: '/foo/:foo', name: 'foo', component: Foo }

In my case i don't want to use url parameters.
The data being loaded on the page is private, and only accessible by the logged in user.
So because Vue creates a new instance when you open a new tab or window, to only way out for me seems to use localStorage.


feat: add to corpus when any comparisons are closer

This duplicates the CmpFeedback effort on the corpus.
The idea being that adding values to the corpus when the input reverts can still be useful to overcome comparisons.
ie: in this toy example, the magic value of 8650 is difficult to guess (without concolic).
pragma solidity ^0.8.13;
contract debug {
    function foo(uint x) public {
        if (x == uint(200000 / uint(23))) {
            assert(false);
        }
    }
}

However, if the input gets closer, the corpus will keep that input and mutate off that.
Concerns:

The corpus will probably hugely over-inflate. I only tested this on the toy example.
The map comparison takes a significant time. I went from ~62k exec/sec to ~50k exec/sec on this pr. This pr is dumb in the sense that it does all the comparisons once in Infant feedback and then again in Corpus feedback.

Pros:

It works really well alongside the gaussian mutator. In debug target I went from finding the magic number in 6m22s to 29s with both

drafting this bc this isn't a good solution. it inflates the corpus too much and should have logic for corpus replacement on closer comparisons.

After experimenting more I think doing this in should_replace() is probably better. No need for a Feedback
https://github.com/fuzzland/ityfuzz/blob/2ffa214e8eb67490366ac8f27ffe81ab8196bee8/src/fuzzer.rs#L169-L188


doc(CONTRIBUTING): Remove text about JIRA and ICLA

...add .vscode for users to avoid checking that in

Platforms affected
Contributing docs
Motivation and Context

This PR removes old information from the Contributing doc. AFAIK an ICLA is not required for trivial contributions, JIRA has been discontinued for Cordova. @purplecabbage Correct ?
Testing

npm test
Checklist

[x] I've run the tests to see all new and existing tests pass
[x] I added automated test coverage as appropriate for this change
[x] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[x] I've updated the documentation if necessary

I would keep the iCLA text, but mention it is ‘recommended, only required for more substantial contributions’
Instead of removing jira issue link why not recommend they create a gh-issue in the relevant repo?
Jira is still required for security issues as we cannot make private gh-issues

@purplecabbage Thanks for pointing that out. I was just checking how to do some things in docs and this file did not help or make any sense to me at the moment.
I just checkend and all repos use the exact same file. So changing this should be something global. Closing this now.


plex: <IP_ADDRESS>52-219a9974e -> <IP_ADDRESS>35-79e214ead

Motivation for this change
New version as usual.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Looks like this is a duplicate of https://github.com/NixOS/nixpkgs/pull/90336.


React native build failed for init RN 0.63.4 xcode 12.4 RN 0.61.5 working fine

System:
OS: macOS 11.2.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 1.70 GB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.15.1 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
Android SDK: Not Found
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>42882
Xcode: 12.4/12D4e - /usr/bin/xcodebuild
Languages:
Java: 15.0.1 - /usr/bin/javac
Python: 3.7.6 - /Users/rejovarghese/opt/anaconda3/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Error shown
The following build commands failed:
CompileC /Users/xxxx/Library/Developer/Xcode/DerivedData/testProj-gttdtokougyaeyaukpnbpyhshzvf/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/Flipper.build/Objects-normal/x86_64/FlipperRSocketResponder.o /Users/xxxx/Dafidy/Testing/testProj/ios/Pods/Flipper/xplat/Flipper/FlipperRSocketResponder.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
getting error by doing
react-native init testProj
cd testProj
npx react-native run-ios

You may want to check this issue https://github.com/facebook/react-native/issues/30836

You may want to check this issue #30836
and especially this comment : #30836 (comment)

I replaced <use_flipper!> with <use_flipper!({ 'Flipper-Folly' => '2.3.0' })> still problem exists

Hi, I'm having the same problem.
After migrating to RN 0.63.4 from 0.61.5, I can't build my project. For the past 2 days, I'm researching for a solution but still no luck.
I tried to comment out the flipper related code in the Podfile and this works on a freshly init RN project. My team still don't use Flipper so for the moment this would be sufficient.
But, when I comment the flipper related code in my work project, I get the following build error:
ld: warning: directory not found for option '-L-L/Users/dimitar.kolev/Library/Developer/Xcode/DerivedData/cc-avxgovnmtpzxrcfkmekdjdlsmxlz/Build/Products/Debug-iphoneos/DoubleConversion' ld: library not found for -lDoubleConversion clang: error: linker command failed with exit code 1 (use -v to see invocation)
Any suggestions?

@DKolev Same as you. I feed no hope right now.

Flipper is absolutely not the cause here. The issue happens because of RCT-Folly lib.

For anyone having this issue. Disabling hermes on iOS and commenting out flipper in the Podfile will remove the error until there's a fix released.

what is weird is that I was able to make it work and then it stopped working for a reason i still ignore

is this solved

Still having the same issue. Driving me crazy.


Request: put license to the repository

Please Apache or similar?

@souramoo Great info @ https://help.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository & http://choosealicense.com/

I like the one that just says "do whatever you wish with it" . I don't remember its name though, but it was funny.

I have added an Apache license as seems to be standard for open source java projects these days for the repo with the latest commit :)

BTW, TPS, can I please contact you? I have something important to tell you.

@AndroidDeveloperLB I can't seem to find any mutual messaging forum where 1 can DM.  Your best bet is to message me (same nick) via the F-droid Forum or perhaps open an issue on 1 of your private repos here.

Thank you very much.
What I wrote was a joke, BTW. I hope you are not offended.


chore(deps): update common-dev-assets digest to 65b2a12

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
42619d8 -> 65b2a12

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

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


Update stable version in repo from 1.1.0 to 1.2.0

Think about update stable version to 1.2.0
Version: stable=1.1.0 (190 days old) => latest=1.2.0 (15 days old)
Installs: stable=53 (86.89%), latest=4 (6.56%), total=61
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 1.2.0 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.2.0 but the current stable version is already 1.2.0.
So this issue should be closed.
@mcm1957 for evidence


fix(shell): fix schema requiring sidecar property even though it is optional

schema noob here: Is it possible to say that either cmd or sidecar is required? Because now only name is required and that alone doesn't do anything. No biggie if this is not possible but wanted to ask just in case it is.

schema noob here: Is it possible to say that either cmd or sidecar is required? Because now only name is required and that alone doesn't do anything. No biggie if this is not possible but wanted to ask just in case it is.

It is probably possible with a custom JsonSchema implementation, I don't think we can do it with the derive macro

@FabianLars actually we could just use untagged enum, take a look and see if that's what you meant

I don't have access to a computer until tomorrow so I can't check out the generated schema but I assume this is what I meant, or at least close enough x)

Okay so I got my hands on my laptop for a minute 😂 It seems to work, cool. vscode just seems to think that args is always required though.
Laptop is gone again so now I really can't test again until tomorrow but with just the args thing I don't think that's a problem

alright, fixed that one as well


Close all tasks by column is closing all open and closed items, thus, completed times updating.

Expected behaviour
Close all tasks by column
all OPEN tasks are closed and completed time updated
Actual behaviour
Close all tasks by column
All OPEN and CLOSED tasks are closed and completed time updated
Steps to reproduce

Have a closed task in a column
Have an open task or tasks in a column
Close all tasks by column

This is affecting our analytics and changed it here on my end:
I've looked at the code and here is the fix in the TaskStatus.php file in app/Model
Just need to add eq(Task::TABLE.'.is_active',Task::STATUS_OPEN) when getting applicable tasks
public function closeTasksBySwimlaneAndColumn($swimlane_id, $column_id)
{
    $task_ids = $this->db->table(Task::TABLE)->eq('swimlane_id', $swimlane_id)->eq('column_id',    $column_id)->eq(Task::TABLE.'.is_active',Task::STATUS_OPEN)->findAllByColumn('id');
    $this->closeMultipleTasks($task_ids);
}

Thanks to report this issue. It's now fixed in master.


Labels instead of IDs for data format

Describe the improvement
Currently, the lengthy data formats from IANA are used.
application/...
text/csv
...
Can we show the label to the user instead, but still save the ID in the database?
related https://github.com/ugent-library/biblio-backend/issues/239

@sdebodt what should these values translate too?
I found this list: https://www.iana.org/assignments/media-types/media-types.xhtml but I'm not sure which values are preferred.

Thanks! Will reopen when the need arises.


Getting error on startup, but not always

I'm getting the following error most of the times when I try to start this up:
ssp    | [cont-init.d] 99-container: executing...
ssp    | **********************************************************************************************************************
ssp    | **********************************************************************************************************************
ssp    | ****                                                                                ****
ssp    | ****       ERROR - All scripts have not initialized properly - All services are now halted                        ****
ssp    | ****             - Please enter the container find out why the missing *-init state file hasn't been written      ****
ssp    | ****                                                                                ****
ssp    | **********************************************************************************************************************
ssp    | **********************************************************************************************************************

But when this error does not come up, SSP works fine.
Here's my docker-compose file:
version: "3"
services:
  ssp:
    image: tiredofit/self-service-password:latest
    container_name: ssp
    labels:
      - traefik.enable=true
      - traefik.frontend.rule=Host:ssp.${DOMAIN}
    volumes:
      - ./data/ssp-data:/www/ssp
      - ./data/ssp-logs:/www/logs
    environment:
      ## LDAP
      - LDAP_SERVER=ldap://openldap
      - LDAP_STARTTLS=false
      - LDAP_BINDDN=${LDAP_ADMIN_USER}
      - LDAP_BINDPASS=${LDAP_ADMIN_PASS}
      - LDAP_BASE_SEARCH=${LDAP_SEARCH_BASEDN}
      - LDAP_LOGIN_ATTRIBUTE=${LDAP_USERNAME_FIELD}
      - LDAP_FULLNAME_ATTRIBUTE=${LDAP_NAME_FIELD}
      ## SSP Password Settings
      - PASSWORD_HASH=CRYPT
      - PASSWORD_MIN_LENGTH=12
      - PASSWORD_NO_REUSE=true
      - PASSWORD_SHOW_POLICY=always
      - PASSWORD_SHOW_POLICY_POSITION=below
      ## SSP Other Settings
      - WHO_CAN_CHANGE_PASSWORD=user
      - QUESTIONS_ENABLED=false
      - IS_BEHIND_PROXY=true
      - SHOW_HELP=true
      - LANG=en
      - DEBUG_MODE=false
      - SECRETEKEY=${SSP_SECRETEKEY}
      - USE_RECAPTCHA=false
      - DEFAULT_ACTION=change
      - USE_TOKENS=false
    networks:
      - traefik
    restart: always
networks:
  traefik:
    external:
      name: traefik_webgateway

Can anyone help? I'd like to follow the hint "Please enter the container find out why the missing *-init state file hasn't been written" but I don't know where in the container to look. I've tried to look at log files but couldn't find anything.
Thanks!

Can I get the rest of that error banner? Or even better the full logs? If worried about privacy send to the email address that is listed in the Changelog..

Thanks for your reply, here you go. This is the output when I run docker-compose up, both a working and a non working log (both with the exact same docker-compose file and the same conditions, nothing changed between the runs as far as I know).

ssplog-working.txt
ssplog-notworking.txt

I also found out that this does not happen with version 4.0, but it happens with 4.1.0.
I hope that helps. If you need more verbose logs, I'd be grateful for a hint on how to get them, I'm pretty new to this whole docker thing.

The error is reproducible if you kill the container (docker stop -t 0 containerid) and start it again.

The root cause is:

the script counts number of init scripts to execute
the script counts number of state files (meaning how many services are actually started)
expects that script counts is one less than script count (because the script itself has no state file yet).

After a restart, /tmp/state is not clean, so it sees it's previous state file and fails.
Solution: use tmpfs for /tmp (on docker-compose add tmpfs: ["/tmp"] )

Sorry for the lack of reply, I didn't get a notification that you had and missed this entirely.
What you described definitely makes sense, that is the sanity test functionality that was put in with an update of my base images. There are a couple of things you can do immediately:

SKIP_SANITY_CHECK=TRUE should skip that routine and bypass it when restarting a container
Alternatively, docker-compose down/docker-compose up -d instead of docker-compose restart

Now, if worried about losing custom configuration and such there's also the capability of using /assets/custom as a volume mapped for every container start to overwrite the files in /www/ssp. Simply put your files into that folder and follow the normal file structure to have them copied/overwritten. Also, if you want to skip writing the configuration file for ssp you can also use SETUP_TYPE=MANUAL.
I think I'm going to have to find a way to determine if a container is cold/hot started to solve this once and for all. The Sanity test is quite useful when we have multiple services running - This nginx-php-fpm based one isn't too complex but I maintain a few others that have half a dozen services started and there for debugging purposes/support requests.

I should also add that version >5.0.0 supports the /assets/custom and SETUP_TYPE variable.

@tiredofit both suggested workarounds have drawbacks:

SKIP_SANITY_CHECK=TRUE should skip that routine and bypass it when restarting a container

That would disable the check completely, so real startup failures won't be detected.

Alternatively, docker-compose down/docker-compose up -d instead of docker-compose restart

This is not an option if the host had an unclean restart (crash or hard reset) - in that case, the existing container is restarted by docker, leaving it in a non-working state.
You should fix your base image to clean /tmp/state before running the init scripts.

I just had a good think about it while walking the dog and have a potential solution, which involves doing some checks right at container start. Let me think this through further and try to implement within next 48 hours.

Thank dog ;-)

Ha. I've made the change and updated the base images. Docker Hub is busy churning away and rebuilding everything relying on them. I'd expect that its going to be 24-36 hours before you'll be able to see.
What I do, is check for existence of /tmp/state and assume that the container has been hot restarted and delete the contents of the folder before proceeding. A notification is also produced in the event that it encounters this.

Docker Hub rebuilt the current latest. Can you give that a try and see if it solves the issue?

@tiredofit Seems to be working, thanks!


upgrade pymongo to 3.2.2, log URI when connecting

MongoLab now evidently uses v3, which made a backward incompatible change to the auth protocol, so we need a v3 client to connect.
btw, thanks for making shamer! we're using it at our work now and really enjoying it. i had to make a number of small changes to get it running, so i'm going to try to send PRs for each of them individually. feel free to accept or reject any of them. thanks again!

@snarfed awesome, thanks for this! will take a look at your other PRs soon.


[ERROR]: The Data consistency number in the comparison document is wrong, some content in the Chinese document needs to be updated

Is there an existing issue for this?

[X] I have searched the existing issues.

Issue
The Data consistency data in the comparison document is wrong, some content in the Chinese document needs to be updated.
Suggestion
I submitted a simple PR to fix:
https://github.com/milvus-io/milvus-docs/pull/1447
Anything else?
No response

Thank you for fixing this problem, closing the issue


enroll error with 0.21.0

When registering a face If you don't rotate your face and just stare at the camera, it won't be a problem.
When rotating the face, the error occurs as shown in the photo below.
I compiled the code from source on window10, I checked that the serial number matches SKU1 and updated the firmware to F450_<IP_ADDRESS>_SKU1_SIGNED.bin.

I am working with custom C#/.NET code on Windows 10. The latest version was running successfully on SDK V 0.18.1. I just installed and updated my code for SDK V 0.21.0.  I'm using the F455 SKU1 hardware and the firmware has been updated to V<IP_ADDRESS> SKU1.  I am seeing the same problem with enrollment using my custom software as has been reported here.  As soon as I move my head, during the enrollment operation, the SKD returns an error of either faceprint not found or spoof.  If I hold my head very still at about 4 inches away from the sensor, I can get a successful enrollment, but it it difficult.  Authentication seems to work. I thought I had a bug in my code adaptation to the new faceprint structures, but after seeing this post, I tested the RealSense ID Viewer, and I see the same problem with that software. I have not seen a response to this post nor any other comments verifying the same problem. I can confirm that this is not a one-off. I hope you will look into what has changed in V 0.21.0 and post a solution.

@donghyun999
Thank for your issue report, this issue will be fixed in the next release.
for now, if you make sure that the first frame of enrollment contain a frontal face, it should work perfectly.

next release is expected end of this week

Fixed in release 0.22.0


Getting Started Docs Failing

Trying to setup a new full Icinga2 installation on a host which will be the first Master using: https://github.com/Icinga/ansible-collection-icinga/blob/main/doc/getting-started.md
-> Example Playbooks -> "This is a example on how to install Icinga 2 server with Icinga Web 2 and Icinga DB."
I couldn't find newer playbooks / examples so I used the one found within the docs directory.
Collection 0.3.4 Error
TASK [icinga.icinga.icinga2 : collect all config objects in play vars tmp_objects={{ tmp_objects| default([]) + lookup('list', icinga2_objects) }}] ***************************************************************************************************************************************************************************
fatal: [tlp87.net]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ tmp_objects| default([]) + lookup('list', icinga2_objects) }}): can only concatenate list (not \"dict\") to list"}

Collection 0.3.3 Error
RUNNING HANDLER [icinga.icinga.icingadb_redis : icingadb-redis-restart name={{ icingadb_redis_service_name }}, state=restarted] ***********************************************************************************************************************************************************************************************
fatal: [tlp87.net]: FAILED! => {"changed": false, "msg": "Unable to restart service icingadb-redis: Job for icingadb-redis.service failed because the control process exited with error code.\nSee \"systemctl status icingadb-redis.service\" and \"journalctl -xeu icingadb-redis.service\" for details.\n"}

Output from icingadb-redis
× icingadb-redis.service - Redis database for Icinga DB
     Loaded: loaded (/lib/systemd/system/icingadb-redis.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2024-08-12 15:19:06 CEST; 40s ago
    Process: 167483 ExecStart=/usr/bin/icingadb-redis-server /usr/share/icingadb-redis/icingadb-redis-systemd.conf (code=exited, status=1/FAILURE)
   Main PID: 167483 (code=exited, status=1/FAILURE)
        CPU: 49ms

Aug 12 15:19:06 tlp87 systemd[1]: Starting Redis database for Icinga DB...
Aug 12 15:19:06 tlp87 icingadb-redis-server[167483]: *** FATAL CONFIG FILE ERROR (Redis 7.0.15) ***
Aug 12 15:19:06 tlp87 icingadb-redis-server[167483]: Can't open the log file: No such file or directory
Aug 12 15:19:06 tlp87 systemd[1]: icingadb-redis.service: Main process exited, code=exited, status=1/FAILURE
Aug 12 15:19:06 tlp87 systemd[1]: icingadb-redis.service: Failed with result 'exit-code'.
Aug 12 15:19:06 tlp87 systemd[1]: Failed to start Redis database for Icinga DB.

/usr/share/icingadb-redis/icingadb-redis-systemd.conf -> /etc/icingadb-redis/icingadb-redis.conf
Log line: logfile /var/log/icingadb-redis/redis.log
No folder: ls: cannot access '/var/log/icingadb-redis/': No such file or directory

Playbook:
- hosts: tlp87.net
  become: yes
  roles:
    - int.env
    - int.apt
    # - { role: int.certbot, tags: ['certbot'] }
    - { role: geerlingguy.mysql, tags: ['mysql'] }
    - icinga.icinga.repos
    - icinga.icinga.icinga2
    - icinga.icinga.icingadb
    - icinga.icinga.icingadb_redis
    - icinga.icinga.monitoring_plugins
    - icinga.icinga.icingaweb2

Vars:
# Variables for collection icinga
icinga_repo_apt_stable_deb: "deb [signed-by={{ icinga_repo_apt_keyring }}] https://artifactory.net/artifactory/icinga-generic-remote/{{ ansible_distribution|lower }} icinga-{{ ansible_distribution_release|lower }} main"
icinga_repo_apt_testing_deb: "deb [signed-by={{ icinga_repo_apt_keyring }}] https://artifactory.net/artifactory/icinga-generic-remote/{{ ansible_distribution|lower }} icinga-{{ ansible_distribution_release|lower }}-testing main"
icinga_repo_apt_snapshot_deb: "deb [signed-by={{ icinga_repo_apt_keyring }}] https://artifactory.net/artifactory/icinga-generic-remote/{{ ansible_distribution|lower }} icinga-{{ ansible_distribution_release|lower }}-snapshots main"
icinga_repo_gpgkey: "https://artifactory.net/artifactory/icinga-generic-remote/icinga.key"
icinga_repo_stable: true
icinga_repo_testing: false
icinga_repo_snapshot: false

icinga_monitoring_plugins_check_commands:
    - "all"

icingaweb2_db:
  type: mysql
  name: icingaweb
  host: <IP_ADDRESS>
  user: icingaweb
  password: abcd
icingaweb2_db_import_schema: true

icingadb_database_type: mysql
icingadb_database_host: localhost
icingadb_database_user: icingadb
icingadb_database_password: efgh
icingadb_database_import_schema: true

icinga2_constants:  # Set default constants and TicketSalt for the CA
  TicketSalt: "{{ lookup('ansible.builtin.password', '.icinga-server-ticketsalt') }}"
  NodeName: "{{ ansible_fqdn }}"
  ZoneName: "main"
icinga2_confd: false # Disable example configuration
icinga2_purge_features: yes # Ansible will manage all features
icinga2_config_directories:  # List of directories in which the role will manage monitoring objects
  - zones.d/main/commands
  - zones.d/main/hosts
  - zones.d/main/services
icinga2_features:
  - name: icingadb
    host: <IP_ADDRESS>
  - name: notification
  - name: checker
  - name: mainlog
  - name: api
    ca_host: none
    endpoints:
      - name: "{{ ansible_fqdn }}"
    zones:
      - name: "main"
        endpoints:
          - "{{ ansible_fqdn }}"
icinga2_objects:
  '{{ ansible_fqdn }}':
    - name: root
      type: ApiUser
      file: conf.d/apiusers.conf
      password: ijkl
      permissions:
        - '*'

# Variables for geerlingguy.mysql
mysql_innodb_file_format: barracuda
mysql_innodb_large_prefix: 1
mysql_innodb_file_per_table: 1
mysql_packages:
  - mariadb-client
  - mariadb-server
  - python3-mysqldb
mysql_users:
  - name: icingaweb
    host: "%"
    password: "{{ icingaweb2_db['password'] }}"
    priv: "icingaweb.*:ALL"
  - name: icingadb
    host: "%"
    password: "{{ icingadb_database_password }}"
    priv: "icingadb.*:ALL"
mysql_databases:
  - name: icingadb
  - name: icingaweb
  - name: vspheredb
    encoding: utf8mb4
    collation: utf8mb4_unicode_ci
  - name: director

Hi
thanks for your quick response! Could have sworn this is possible with ansible but I guess I confused it with another situation. With 0.3.3 the playvar worked perfectly fine.
I tried it again with 0.3.4., same error
fatal: [tlp87.lp.rsint.net]: FAILED! => {"msg": "Unexpected templating type error occurred on ({{ tmp_objects| default([]) + lookup('list', icinga2_objects) }}): can only concatenate list (not \"dict\") to list"}
with
icinga2_objects:
  tlp87.net:
    - name: root
      type: ApiUser
      file: conf.d/apiusers.conf
      password: ikjl
      permissions:
        - '*'

Did you configure icinga2_objects somewhere else again? Or is it the only occurrence?
Can you define the var in a host_vars?
This is a bug, you can only define the objects variable with the fqdn as Key in host_vars. If outside of the host_vars we expect the other syntax.
icinga2_objects:
  - name: root
    object_type: ApiUser
    ...

It is not configured elsewhere. As per my opener I am working on a completely fresh setup (on a newly spawned vm).
The vars provided reside in host_vars/tlp87.net which is a symlink to inventory/host_vars and I invoke the play via ansible-playbook playbooks/site.yml --limit tlp87.net.

@mkayontour I installed 9a0e874800e093fcdc57e46b29c8e70326e9999e for a test and it looks like the issue has been fixed (as per https://github.com/Icinga/ansible-collection-icinga/pull/311 I think, no error anymore).
But unfortunately the task is being skipped for the host and the object is not being deployed. Probably the reason I do not get an error :)

Hi @thesefer
as per
https://github.com/Icinga/ansible-collection-icinga/blob/9a0e874800e093fcdc57e46b29c8e70326e9999e/roles/icinga2/defaults/main.yml#L18
you can actually use inventory_hostname.
This variable is basically meant for use cases like yours.
If you change it to inventory_hostname, your situation could look like this:
Inventory:
[icingahosts]
icinga-master
; actual fqdn e.g. being "master.example.com"

(Host) Vars:
icinga2_config_host: "{{ inventory_hostname }}"
icinga2_objects:
  icinga-master:
    - name: root
      type: ApiUser
      file: conf.d/apiusers.conf
      password: ijkl
      permissions:
        - '*'

Hi @Donien
Thanks for your explanation. You are right, I could use this variable! Maybe I have overlooked it in the documentation, I searched for it due to the output log.

Oftentimes - at least from what I've seen - the name in your inventory is the FQDN of the host.
So using the FQDN for icinga2_config_host seems like a reasonable default to me.

This is what I am doing, too. In my inventory the host looks like this, i.e.:
[test_services]
tlp87.intern.example.net ansible_host=<IP_ADDRESS>

So the inventory_hostname would be correct. But the ansible_fqdn is gathered from the system and the hostname is tlp87 only.
It's interesting how different things are. I have never seen a FQDN as the hostname on a machine. Instead I always see inventory_hostname_short in this case.
Thank you very much for your help and support! I will continue testing everything now :-)


Zoning support for in-cluster mode

Currently, kube-loxilb supports service-zoning for external mode but does not support it for in-cluster mode.

Usage guide has been updated.


Upgrade HTTP Core with the Fixes done

Description
$subject
We've forked HTTP Core and done several fixes, but these are not available in master. Need to upgrade to latest apache http core version with the fixes or fork and use this in master.
Affected Component
APIM
Version
4.2.0
Related Issues
https://github.com/wso2-enterprise/wso2-apim-internal/issues/142
Suggested Labels
No response

Apache HttpCore NIO 4.4.16 has been released [1]. Therefore, APIM-4.2.0 and related components will be updated to use this direct dependency org.apache.httpcomponents:httpcore-nio:4.4.16 and the associated orbit [2]. Also, since there will be no usage for version 4.4.15-wso2v2, it will be dropped in near future.
[1] - https://mvnrepository.com/artifact/org.apache.httpcomponents/httpcore-nio/4.4.16
[2] - https://github.com/wso2/orbit/pull/863


Use new let-else syntax where possible

Objective
Let-else syntax is now stable!
Solution
Use it where possible!

Is there a lint for this yet? If so, can we enable it to ensure consistent style?
Do we want to merge this before automatic formatting is working?

Is there a lint for this yet? If so, can we enable it to ensure consistent style?

There is a lint for it, but it's only available on nightly so far.

Do we want to merge this before automatic formatting is working?

I'm cool with letting people use the better syntax now with whatever looks ok and letting auto formatting work itself out, when it comes. The formatting discussion appears to have been going on for a long time and idk how long it will take to resolve itself. This way we don't accumulate "refactoring debt", whereas formatting style fixes will be automatic when they come.

bors r+


Pull Request Guideline Draft

Draft a PR guideline for STRA
https://github.com/bcgov/nr-spar/wiki/Pull-Request-Guideline

@chris-prince-cgi  would you mind reviewing please?


feat(server): add NumericPropertyBoundsRule #944

Closes #944

:+1:

:+1:

@roxspring can you please correct the commit message for 01c3609.

@roxspring can you fix the klint problems:
/home/travis/build/zalando/zally/server/src/test/java/de/zalando/zally/rule/zally/NumericPropertyBoundsRuleTest.kt:4:1: Unused import
/home/travis/build/zalando/zally/server/src/test/java/de/zalando/zally/rule/zally/NumericPropertyBoundsRuleTest.kt:6:1: Unused import
/home/travis/build/zalando/zally/server/src/test/java/de/zalando/zally/rule/zally/NumericPropertyBoundsRuleTest.kt:8:1: Unused import

I assume these are consequences of the latest kotlin update in our last PR.

Codecov Report

Merging #945 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #945      +/-   ##
============================================
+ Coverage     86.28%   86.32%   +0.04%
- Complexity      948      953       +5
============================================
  Files           172      173       +1
  Lines          2668     2677       +9
  Branches        417      419       +2
============================================
+ Hits           2302     2311       +9
  Misses          162      162
  Partials        204      204

Impacted Files
Coverage Δ
Complexity Δ

...ando/zally/rule/zally/NumericPropertyBoundsRule.kt
100% <100%> (ø)
5 <5> (?)

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 fa71926...103891a. Read the comment docs.

:+1:

:+1:


This allows to specify the HTTP client (cUrl or file_get_contents)

cURL allows more control over timeouts (connection vs. read timeout), however it was not possible to specify the HTTP client to be used without fallback.
This PR adds the possibility to define the HTTP client to be used (either cURL or file_get_contents) and not allow a fallback.
The default behaviour (fallback from fopen to curl is not touched).

The master branch now has v3 dev work. Check it out if you want to dig into this again.