Less lines on console

I output the lager logs on console and it is flooded with poor formatted outputs
Formatting with ~p tries to break after 80 chars, so my output looked like this:
09:07:23.201 [error] Lager failed to install handler lager_journald_backend into lager_event, retrying later : {'EXIT',
                                                                                {undef,
                                                                                [{lager_journald_backend,
                                                                                init,
                                                                                [[{level,
                                                                                debug}]],
                                                                                []},
                                                                                {gen_event,
                                                                                server_add_handler,
                                                                                4,
                                                                                [{file,
                                                                                "gen_event.erl"},
                                                                                {line,
                                                                                434}]},
                                                                                {gen_event,
                                                                                handle_msg,
                                                                                5,
                                                                                [{file,
                                                                                "gen_event.erl"},
                                                                                {line,
                                                                                279}]},
                                                                                {proc_lib,
                                                                                init_p_do_apply,
                                                                                3,
                                                                                [{file,
                                                                                "proc_lib.erl"},
                                                                                {line,
                                                                                240}]}]}}

This commit changes it to
09:18:08.396 [error] Lager failed to install handler lager_journald_backend into lager_event, retrying later :
  {'EXIT',{undef,[{lager_journald_backend,init,[[{level,debug}]],[]},
                  {gen_event,server_add_handler,4,[{file,"gen_event.erl"},{line,434}]},
                  {gen_event,handle_msg,5,[{file,"gen_event.erl"},{line,279}]},
                  {proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,240}]}]}}

which does not flood the console so fast.

If the newline is not wanted then we need a higher number, like ~230p .

I'm sympathetic to this change, but I'm wary of using 100 columns. Can we make it "~n~p" and add a comment that we're using a newline so the stack trace is easier to read?

@Vagabond pointed out that lager has a formatter for this kind of message already which is in error_logger_lager_h:format_reason/1 so we should use that.

I'm going to close this PR due to lack of activity.  Thanks for the patch.


reorganize turnup directory structure

@colemickens is this going to be a hassle for you to rebase on top of?

No, shouldn't be a problem at all.


HURL v0.9.0-alpha-2 Not Respecting Windows Shutdown/Restart - Uknown Error

Hi,
Went to reboot my Win11 23H2 box after installing the Aug Windows Security updates and got an error trying to reboot and then realized it was HURL:

Win11 23 H2
HURL v0.9.0-alpha-2
Was only showing one of the errors. I right clicked hurl's notification (system tray) icon and it displayed a 2nd error.
Tried a few times as can be seen in the screenshot. After about 20 tries or so, hurl crashed. Then of course my machine could reboot fine.
So, looks like need to test if windows is being rebooted or shutdown and close out correctly beforehand.
Looks like need to be watching for the SystemEvents.SessionEnding Event @  https://learn.microsoft.com/en-us/dotnet/api/microsoft.win32.systemevents.sessionending?view=net-8.0&redirectedfrom=MSDN
Best,
Will

This is the weirdest error/behavior I've seen for Hurl yet 😅. I do restart/shutdown frequently with Hurl always in background, never seen it so far.
I suspect this related to how I am handling Exit calls for threads, currently I just forcefully kill threads and main process for Hurl. I want to fix this before stable release.
I could be wrong about this completely.

Implemented better exit behaviour: https://github.com/U-C-S/Hurl/commit/abbbbdeba0a9f9f8155354f8e245add80bd54c2b

I am closing this cause there is no way of verifying if the supposed fix works.
but if this appears again, Just comment here and I am ready to open this again.


Using your evaluation script (compute_metrics.py)

Hi, thanks for the repository.
I wanted to use your metrics script to evaluate generated structures from mp_20 dataset. I have the training dataset and the generated dataset both in .cif format. I wish to ask, how may I use your script to evaluate the performance of my model?
As per my understanding we need of compute_metrics.py in order to get the crystal list we need to convert the .cif structure to a data dictionary with keys : {frac_coords, atom_types, lengths, angles, num_atoms}.
How to get these values for the above keys from my .cif file ?
compute_metrics.py : https://github.com/txie-93/cdvae/blob/f857f598d6f6cca5dc1ea0582d228f12dcc2c2ea/scripts/compute_metrics.py#L267
def get_crystal_array_list(file_path, batch_idx=0):

    data = load_data(file_path)

    crys_array_list = get_crystals_list(
        data['frac_coords'][batch_idx],
        data['atom_types'][batch_idx],
        data['lengths'][batch_idx],
        data['angles'][batch_idx],
        data['num_atoms'][batch_idx])

Hi, I think if you have the .cif structure, you could get all these parameters by feeding the cif to the 'Structure' class in pymatgen. Details can be found in cdvae/common/data_utils.py


FromJsonSchema?

It seems feasible to parse a json Schema into a zap Schema. But do we need that usecase?

Perhaps this should be done as a zap-codegen project. Also generate types from openApi.


sql: enhance dbeaver docs to show insecure connection

Our current documentation focuses only on secure mode using ssl. This is a blocker for people testing out the tool and cockroachdb. We should show how to connect not using secure mode.
Its as simple as removing ssl:

Also, dbeaver has a different look with their update so we could update our images at the same time.

Also, we should include a section on doing it with cockroach demo
This requires finding your host on demo:
root@<IP_ADDRESS>:63302/movr>
9:20
<IP_ADDRESS>:63302
Note, the host is random so we will have to clarify that

this is a reminder to myself of what the setup looks like with demo:

We are de-emphasizing/removing "insecure" mode from all Cockroach docs.
See #6574 and #7772.


FIX: Ensure the entire URL is used when check for page subject

Fix for #8 part 2 https://github.com/micschk/silverstripe-liveseo/issues/8

Thanks, and sorry for not replying to your earlier comment about this -- the way you described and how your fix makes the checking work, is exactly how I think it should

No problem re reply speed, I do realise it's a holiday weekend


zlib_util_c.h:2:18: fatal error: zlib.h: No such file or directory

Robotgo version (or commit ref): newest
Go version: 1.11
Gcc version: 5.1.0
Operating system and bit: Windows 10
Resolution:
Can you reproduce the bug

[x ] Yes (provide example code)
[ ] No
[ ] Not relevant

Every time I want to try robotgo I get the following error:
github.com/go-vgo/robotgo
In file included from ./bitmap/../base/str_io_c.h:2:0,
from ./bitmap/goBitmap.h:17,
from ..\go\src\github.com\go-vgo\robotgo\robotgo.go:45:
./bitmap/../base/zlib_util_c.h:2:18: fatal error: zlib.h: No such file or directory
compilation terminated.
exit status 2
Process exiting with code: 1
I have already found the similar issue here: https://github.com/go-vgo/robotgo/issues/100
But their solution to use MingW is not working for me or am I doing something horrible wrong here? Any ideas?
my gcc config:
C:\Users\Alf>gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=C:/TDM-GCC-64/bin/../libexec/gcc/x86_64-w64-mingw32/5.1.0/lto-wrapper.exe
Target: x86_64-w64-mingw32
Configured with: ../../../src/gcc-5.1.0/configure --build=x86_64-w64-mingw32 --enable-targets=all --enable-languages=ada,c,c++,fortran,lto,objc,obj-c++ --enable-libgomp --enable-lto --enable-graphite --enable-cxx-flags=-DWINPTHREAD_STATIC --disable-build-with-cxx --disable-build-poststage1-with-cxx --enable-libstdcxx-debug --enable-threads=posix --enable-version-specific-runtime-libs --enable-fully-dynamic-string --enable-libstdcxx-threads --enable-libstdcxx-time --with-gnu-ld --disable-werror --disable-nls --disable-win32-registry --prefix=/mingw64tdm --with-local-prefix=/mingw64tdm --with-pkgversion=tdm64-1 --with-bugurl=http://tdm-gcc.tdragon.net/bugs
Thread model: posix
gcc version 5.1.0 (tdm64-1)

Provide example code:

package main
import (
"github.com/go-vgo/robotgo"
)
func main() {
robotgo.ScrollMouse(10, "up")
robotgo.MouseClick("left", true)
robotgo.MoveMouseSmooth(100, 200, 1.0, 100.0)
}

I may have fixed this in Go 1.13.
env GOOS=windows \
       GOARCH=amd64 \
       CGO_ENABLED=1 \
       CC=x86_64-w64-mingw32-gcc-posix \
       CXX=x86_64-w64-mingw32-g++-posix \
       CGO_CFLAGS="-g -O2 -I/usr/local/x86_64-w64-mingw32/include" \
       CGO_LDFLAGS="-g -O2 -L/usr/local/x86_64-w64-mingw32/lib -L/usr/local/x86_64-w64-mingw32/lib" \
       go build -trimpath -ldflags="-w -s -extldflags -static" -x

All code tests and C dependencies use MinGw-64, TDM-GCC has not been tested.


Refactor EnFile to speed it up

The PR refactors EnFile to speed it up
benchmark before
Benchmark           Mode  Cnt     Score   Error   Units
JmhTest.initFaker  thrpt    5    44.192 ± 0.733  ops/ms

and after
Benchmark           Mode  Cnt    Score   Error   Units
JmhTest.initFaker  thrpt    5  138.761 ± 2.593  ops/ms

benchmark'c code
@Benchmark
@BenchmarkMode(Mode.Throughput)
public void initFaker(Blackhole blackhole) {
    blackhole.consume(new Faker());
}

Nice!!

For naming conventions, I don't mind that much, but I use this as my guide:
https://stackoverflow.com/questions/1417190/should-a-static-final-logger-be-declared-in-upper-case

Ok, thanks for letting know
in fact the main thing I did here with logger is making it static since it was in profiler's output


Add table of contents

Description
Add table of contents in Read me file so that contributors and maintainers can get a overview about project in a nutshell.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I agree to follow this project's Code of Conduct

Please assign this issue to me @maityamit

I want to contribute to this issue ,kindly assign me under JWOC

Hi, @Code1705
ya continue with this...


Minor typo

This is silly and kinda minor, mostly just because I really, really appreciate this project and am thrilled to help a little, even if it's just copyediting. Thanks for your hard work, Dr Nelson.

Nothing silly about copyediting! Thanks.


Memory leak issue in when converting JPEG via cjxl

Describe the bug
During testing, several samples were found to cause consumption of all RAM. However, this did not cause memory corruption, except for one sample, which possibly caused a read outside of the allocated memory.
To Reproduce
Steps to reproduce the behavior:
./cjxl ./id_000010,src_002666_time_68141275_execs_10591653_op_flip32_pos_163 --disable_output

Output:
==13412== LEAK SUMMARY:
==13412==    definitely lost: 0 bytes in 0 blocks
==13412==    indirectly lost: 0 bytes in 0 blocks
==13412==      possibly lost: 52,830,275,144 bytes in 41 blocks
==13412==    still reachable: 25,776,811,852 bytes in 68,748 blocks
==13412==         suppressed: 0 bytes in 0 blocks
==13412==
==13412== For lists of detected and suppressed errors, rerun with: -s
==13412== ERROR SUMMARY: 26 errors from 26 contexts (suppressed: 0 from 0)

Expected behavior
At run util with current sample is expected сontrolled memory consumption
Screenshots
launch visualization to memory use:

Environment

OS: tested at 5.15.78-2.el7.3.x86_64 (Centos based system) ;
Compiler version: clang version 12.0.1 ;
CPU type: x86_64 ;
cjxl version string: 0.8.1

Additional context
The area causing the problem could probably be in lib/jxl/image.cc on line 94, where the JXL_CHECK() macro is used in bytes_.get() (probably problem is caused by the PlaneBase constructor).
link to a sample (github-url):
id_000010_poc
link to a valgrind  log (github-url):
/id_000010_valgind.log

We are facing it when we try to use this with libvips. Any luck with this one?


Use http datasource for local urls

Currently all local urls are retrieved by the DefaultDataSourceFactory. However, in my case I want to use localhost urls that return a redirect (302) to the actual mp3.
Therefore, since they are http/https urls, they should be handled by DefaultHttpDataSource so the redirect is followed.
This PR fixes the check isLocalUri to match local file uris only.
I have tested this with React Native Track Player.

@dcvz Would it be possible to take a look at this PR? Thanks a lot!

@janwiebe-jump I'm ready to merge this but the sample is failing to build. Looks like there's a syntax error in Utils.kt:

e: /Users/admin/actions-runner/_work/KotlinAudio/KotlinAudio/kotlin-audio/src/main/java/com/doublesymmetry/kotlinaudio/utils/Utils.kt: (15, 254): Unexpected tokens (use ';' to separate expressions on the same line)

Merged! Thanks for the contribution @janwiebe-jump


Release 4.37.2 breaks our ci

New fonttools release has broken our google/fonts CI:
https://github.com/google/fonts/actions/runs/3066331513/jobs/4951379192#step:6:421
INFO:gftools.qa:Running Diffenator
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.8.13/x64/bin/gftools-qa.py", line 263, in <module>
    main()
  File "/opt/hostedtoolcache/Python/3.8.13/x64/bin/gftools-qa.py", line 240, in main
    qa.googlefonts_upgrade()
  File "/opt/hostedtoolcache/Python/3.8.13/x64/lib/python3.8/site-packages/gftools/qa.py", line 216, in googlefonts_upgrade
    self.diffenator()
  File "/opt/hostedtoolcache/Python/3.8.13/x64/lib/python3.8/site-packages/gftools/qa.py", line 109, in diffenator
    font_before = DFont(self.instances_before[style]['filename'])
  File "/opt/hostedtoolcache/Python/3.8.13/x64/lib/python3.8/site-packages/diffenator/font.py", line 100, in __init__
    self.recalc_glyphset()
  File "/opt/hostedtoolcache/Python/3.8.13/x64/lib/python3.8/site-packages/diffenator/font.py", line 144, in recalc_glyphset
    inputs = InputGenerator(self).all_inputs()
  File "/opt/hostedtoolcache/Python/3.8.13/x64/lib/python3.8/site-packages/diffenator/hbinput.py", line 41, in __init__
    elif hasattr(glyph._glyph, 'xMax'):
AttributeError: '_TTGlyphGlyf' object has no attribute '_glyph'

Im guessing https://github.com/fonttools/fonttools/commit/b818e1494ff2bfb7f0cd71d827ba97578c919303 may be the culprit.

This change also broke babelfont and beziers.py. Yes, I know it's a scary underscore class, but it was the only sensible way to get at the font's glyphs.

hm, but the symbols where prefixed with an underscore which in Python land means they are presumed to be private so you kind of did that at your own risk?

we can provide a public method if clients need that. Want to send a PR?

I wonder if we even need it. font.getGlyphSet()[glyphname] returns an object with a draw method, and that's probably all that it takes. I'm not sure if that does the right thing with components, but presumably it does.

yeah, that's the intended public interface. If one wants to access the raw glyphs underneath, then one can go and get them directly from the tables. The TTGlyphSet is supposed to be a higher level API.


Feature Request: Integrate User Authentication System for Tracking Personalized Contributions

Is your feature request related to a problem? Please describe.
I often feel frustrated when I cannot easily track my individual contributions within this repository. Without a dedicated authentication system, there is no straightforward way for users to access or monitor their personalized activity, see their past contributions, or understand the impact they have made. This makes it challenging to stay motivated and see my progress over time.
Describe the solution you'd like
I would like to see an integrated user authentication system within the repository. This system would enable users to log in and access a personalized dashboard displaying their contribution history and other relevant metrics. Key features could include:
Tracking individual contributions by commits, issues, and pull requests.
Visual summaries of activity (e.g., graphs, recent contributions, milestones).
Notifications or highlights for significant contributions.
This would give users a clear view of their contributions and progress, enhancing engagement and motivation.
Describe alternatives you've considered
An alternative could be to integrate with existing GitHub contribution tracking, but this lacks personalized metrics specific to this repository. Another option might be using third-party contribution-tracking tools, but these do not provide a seamless, integrated experience directly within the project and may miss specific custom metrics valuable for this repository

@rajutkarsh07 Can I assign me this


genabi: add complete uint support

the solidity docs specify that solidity has support
for uints with M bits, where 0 < M <= 256 and
M % 8 == 0.

legend. These types need to be added to the goType function as well.

ack, will do later when i have time


Small issue on Linux.

Hello, i'm really sorry to ask this here because thats not completely related with the cheat himself, the cheat works really fine on Manjaro.
So yeah, i use the cheat on Linux Manjaro and i followed these instructions:
https://github.com/danielkrupinski/Osiris/pull/2853/commits/9f75020c880e899687db5c505a0a70d7dd18168c
It works fine, but i have a small problem. There's the build_arch file and the load_osiris file.
Both of them doesnt run, i get this error trying to run them into my terminal:
Warning: Could not find '/home/nameofuser/Bureau/Osiris/load_osiris', starting '/bin/bash' instead.  Please check your profile settings.
I'm kinda tired to open the console into the release folder and copy and paste the code of the load_osiris file everytimes i want to inject the cheat. Is there a way to run it directly please? Thank you. And again, sorry to ask this here. The cheat works fine on Manjaro.

make a shortcut?

make a shortcut?

what do you mean make a shortcut? it doesnt change anything, or maybe i dont understand

make a shortcut?

what do you mean make a shortcut? it doesnt change anything, or maybe i dont understand
nvm fixed ty

How did you make a shortuct?


Deprecation warnings for ClusterRole / ClusterRoleBinding / Ingress

Hi, I'm running kubernetes 1.19 with RKE and when i'm installing the chart, These deprecations appears:
W1208 21:07:40.172608  495469 warnings.go:67] networking.k8s.io/v1beta1 Ingress is deprecated in v1.19+, unavailable in v1.22+; use networking.k8s.io/v1 Ingress
W1208 21:07:40.589121  495469 warnings.go:67] rbac.authorization.k8s.io/v1beta1 ClusterRoleBinding is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRoleBinding
W1208 21:07:40.644555  495469 warnings.go:67] rbac.authorization.k8s.io/v1beta1 ClusterRole is deprecated in v1.17+, unavailable in v1.22+; use rbac.authorization.k8s.io/v1 ClusterRole

1.22 is scheduled for mid 2021

This appears to be currently causing installation to fail?

Yes, on 1.22 it seems to be.

Maybe change the title to Kubernetes 1.22 support? :)
Also note that there's a new warning for PDB:
W0209 18:20:45.140203   43895 warnings.go:70] policy/v1beta1 PodDisruptionBudget is deprecated in v1.21+, unavailable in v1.25+; use policy/v1 PodDisruptionBudget

Per my investigation, this was caused by a few things:

Ingress was using the unsupported v1beta1 version in web-ingress.yaml
An old version of Prometheus was causing the ClusterRoleBinding errors
PDB created by ES was also out of date (warning for 1.25)

There still remains one PDB issue caused by Grafana, but we have about 6-9 months before 1.25 and will have to wait on them.


Example shows only C#. Not everybody uses C# or want to use C#

The example does not make anything clear and it should not be about C#

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 03b00e4d-3af1-d053-373e-7724bc81113b
Version Independent ID: e0e54223-efc3-f69f-efc1-e19ba0010760
Content: Azure Service Bus Subscription Rule SQL Filter syntax - Azure Service Bus
Content Source: articles/service-bus-messaging/service-bus-messaging-sql-filter.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

Hello @sijucm,
Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

@sijucm - Thanks for the feedback. Is this feedback on the Samples article: https://docs.microsoft.com/en-gb/azure/service-bus-messaging/service-bus-filter-examples? Thanks.

We will track this via an internal work item. Thanks. #please-close


Refactor config imports

Replace "import urls from config" by "import config from config"

resolve #72

Hi @PiotrBlachnio, thanks for contributing to this repo. We want to save issues with the "good first issue" label for new student developers who are going to be joining our team soon. I will be closing this PR, but I encourage you to take up other issues without that label if you are interested 🙂


Fixed no volumes returned on empty list

This commit fixes an error that was being returned to Docker when
there were no volumes returned from a list operation.

Testing this further.

Are you testing this further, or is it assigned to me? If you're testing it, please assign it back to yourself until you're ready for it to be merged. Thanks.

My fault, this is good to go.
Before
[root@localhost vagrant]# docker volume ls
list rexray: VolumeDriver.List: {"Error":"No volumes returned"}

DRIVER              VOLUME NAME

After
[root@localhost vagrant]# docker volume ls
DRIVER              VOLUME NAME
[root@localhost vagrant]# docker volume create --driver=rexray --name=test
test
[root@localhost vagrant]# docker volume ls
DRIVER              VOLUME NAME
rexray              test


Negative slices + cool range syntax

This allows negative slices for ranges, and adds a new syntax.
The following is now possible:

_a == all()
_e == ellipsis()
_n == newaxis()
_r =>  to be used with operator| to create ranges, e.g. _r|0|10|2 etc.

using namespace xt::placeholders;
xt::strided_view(a, {_r|_|_|-1|, _a});
xt::strided_view(a, {_r|-1|-5|-1|, _a});
xt::strided_view(a, {_r|-1|-5|-1|, _a});
xt::strided_view(a, {1, _r|3|_|-1});

This still needs fixes, a warning pass and tests -- which is why we defer the release to 0.16.1 (discussed with @JohanMabille)

@JohanMabille any chance you could have a look at the AppVeyor MSVC 2015 problem?
Should we remove GCC 4.9 compatibility for the "fancy" range syntax? @SylvainCorlay @JohanMabille

@wolfv I'm having a look now. I need to fix it before implementing the dynamic_view.


Issue in centos image generation

What's the issue?

Issue in centos base and docker image creation

System Under Test/Environment

Centos 8

Steps to reproduce the issue

make build-all

Error Log :
==> qemu: Executing Ansible: ansible-playbook -e packer_build_name=qemu -e packer_builder_type=qemu -e packer_http_addr=<IP_ADDRESS>:8114 --ssh-extra-args '-o IdentitiesOnly=yes' -e ansible_ssh_private_key_file=/tmp/ansible-key201182752 -i /tmp/packer-provisioner-ansible263575807 /ibmcloud-image-builder/img/centos-7-base/ansible/playbook.yml
    qemu:
    qemu: PLAY [play Hello World] ********************************************************
    qemu:
    qemu: TASK [Gathering Facts] *********************************************************
    qemu: fatal: [default]: FAILED! => {"msg": "Timeout (12s) waiting for privilege escalation prompt: "}
    qemu:
    qemu: PLAY RECAP *********************************************************************
    qemu: default                    : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0
    qemu:
==> qemu: Provisioning step had errors: Running the cleanup provisioner, if present...
==> qemu: Deleting output directory...
Build 'qemu' errored: Error executing Ansible: Non-zero exit status: exit status 2

==> Some builds didn't complete successfully and had errors:
--> qemu: Error executing Ansible: Non-zero exit status: exit status 2

==> Builds finished but no artifacts were created.
make[1]: *** [Makefile:39: build-image] Error 1
make[1]: Leaving directory '/root/ibmcloud-image-builder'
make: *** [Makefile:30: centos-7-base] Error 2


gnupg22: fix tests eval

Without the change tests attribute fails to resolve testsuite:
$ nix build --no-link -f. gnupg22.tests
error: attribute 'nixosTests' missing

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] 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.

Add a :+1: reaction to pull requests you find important.

I doubt if nixosTests.gnupg is actually useful for gnupg22 :shrug:


Update Reason
After alignment meeting with IDTA and TC4S, the Assset Tracking Use Case have decided to change/update the aspect model IotSensorData. This update will keep the solution ATP interoperable and open.

The sensor's data attributes will be changed from static to dynamic.
Conversion from BAMM to SAMM

MS1 Criteria

[x ] The model that should be updated exists
[x ] The referenced use case exists
[x ] The potential updates are discussed with all stakeholders
[ x] A decision on versioning was made in consensus with the affected parties according to the guidelines.
[x ] The potential update will be either

[ ] backward compatible or
[x ] a (chain of) migration strategy(-ies) from all non-deprecated previous versions to the new model will be developed

[ x] A modeling steward has been assigned

@modeling_team

Modifying https://github.com/eclipse-tractusx/sldt-semantic-models/blob/main/io.catenax.iot_sensor_data


chore: make test more timing resilient

This test case is causing flakyness on windows. The previous delay(100) is too sensitive to timing differences.
There is a longer backstory to this and something puppeteer hasn't addressed in the past years. For context: I worked on a custom e2e test runner based on puppeteer for a client a couple of years back (around 2019-ish). At the time playwright wasn't really a thing so puppeteer was the only option.
A common source of problems in e2e testing is that it's not obvious when an element can be safely clicked. Sure, you can always simulate a click on a DOM node, but that doesn't account for the framework potentially not having attached an event listener yet. It's an internal race condition as to when the click is fired. The cypress blog has a good post about the problem. To work around that I've added a clickWhenListenerReady helper function that waits until Preact has added a listener before firing the click.
Then there is a very related race condition in that firing the click doesn't mean that the changes have been immediately applied to the DOM. The framework (here Preact) might do some scheduling or maybe something inside puppeteer or even Chrome took a bit longer. It's hard to pinpoint where exactly the issue is, but this leads to cases where the click has fired but the new value has not been written to the DOM yet. A much more reliable way is to instead wait until the expected string is present in the DOM.
I did a couple of local runs on windows and with the changes in this PR I get way less flukes.

Well, looks like I celebrated too early. The CI failed again 😅

Re-ran the CI and all is green again. I had hoped to eliminate any flukes completely, but looks like some are still there. Nonetheless I feel like the changes here are worth merging as the flukes seem to happen less frequently.

Adding support for retries is a great idea. We should look into that 👍


License

Where to download MIT Xenko?
I recently downloaded Xenko and it was written in license that the developer of Xenko would cooperate with law enforcement agencies or something similar, sue and etc.
But this is unacceptable for an open project.

Hello,
License is MIT (the one you downloaded too).
You probably reference to the Privacy Policy which is mostly a leftover from when the engine was commercial and needs to be updated to reflect new state of the project. Sorry for the confusion.

I have updated the Privacy Policy
Should be much less scary.
Please reopen issue if you still see points of concerns.

@Degaron metrics are public: https://metrics.xenko.com/

Each user should be able to disable this feature.

you can make a pull request that adds an option, if you feel that that it is needed: https://github.com/xenko3d/xenko/tree/master/sources/metrics

I did it here, and now the developers will decide.

And where are the official compiled versions?
Where is windows 64 bit?
Today, no one will compile the program, it's just absurd.

https://xenko.com/download/
Please, stick to the issue's subject.

All of the annoying vibration because of this?
If you affair of metrics that Xenko collect then don't use it. Seriously.
If you are affair of compiling the source code then visit xenko.com/download.
32 bit or 64 bit architecture program run just fine on x64 architecture Windows!

I am totally fine to make the metrics collection optional (somebody need to spend time to do it, I have some other things that are higher priority).
Users would still have to accept it if they send a crash report though.


Ctrl-C

catching sigint is a bit strange UX. (good old quit vim jokes anyone?)
that might be an unintentional side effect of terminal raw mode,
so i it would be ok to add a keyhandler for ctrl+c i guess, but Event::Input lacks a modifier.

Hi,
I managed to have the ctrl + c in my application, to do that, it's as simple as that:
 if let Key::Ctrl('c') = input {
   break; // Break the ui loop (same as 'q' in examples)
}

As mentioned on the README, this crate does not provide any input handling directly since it is usually provided by the terminal backend you choose. Thus you may refer to those crates for how sigint may be handled.
I know that the examples might not be the best illustration of this fact as they include a fair amount of input handling. But this is done for the sake of having a more dynamic content. Therefore Event is just a convenient way of dealing with different source of events but it is not part of the crate directly (defined inside this file).
Closing this since @Catvert has proposed a valid solution IMO


Markers not displayed

Very new to this world, please forgive me if not appropriate to ask questions here but unfortunately the
stackoverflow's Vue2Leaflet community is not yet active.  (Where should I be posting questions, if not here?)
Could someone please tell me why this simple component page does not display any markers (just a map).  I have tried multiple variations by so far not seen a single marker.
I understand there WAS an issue with the default marker icon and webpacks (which I'm using). Has this be corrected in latest versions?

<template>

 {{ title }}

    <l-map  ref="map" :zoom="zoom" :center="center" style="height:800px" >
      <l-tile-layer :url="url" :attribution="attribution"></l-tile-layer>
      <l-marker :lat-lng="[51.81416, -2.27936]"></l-marker>
      <l-marker v-for="marker in markers"
         :key="marker.id"
         :visible="marker.visible"
         :lat-lng="marker.position"
         :icon="marker.icon">
      </l-marker>
    </l-map>

</template>

Browsers Affected

[X ] Chrome

Versions

Leaflet: v1.3.4
Vue: v2.5.17
Vue2Leaflet: v1.1.1

this.myMarkerIcon isn't existing yet when you return the object in your data function, because it is only available after the object in data was returned :D Try it the following way (first put your icon in a temp variable, this you can then assign to your markers ans if wished also return in your data object for later use):
data() {
    const myMarkerIcon = L.icon({
         iconUrl: require('leaflet/dist/images/marker-icon.png'),
         shadowUrl: require('leaflet/dist/images/marker-shadow.png'),
         iconRetinaUrl: require('leaflet/dist/images/marker-icon-2x.png')
    });

    return {
        ...
        myMarkerIcon: myMarkerIcon,
        markers: [ { id: 'm1',
                  position: [51.81416, -2.27936],
                  visible: true,
                  icon: myMarkerIcon
        },
        { id: 'm2',
                  position: [51.81416, -2.2799],
                  visible: true,
                  icon: myMarkerIcon
        }]
      };
}

@BryTack Glad that @byWulf managed to help you right away! Worry not we all started somewhere!
feel free to open more issues if you need help or reach out!
Closing this since is solved !


fixed typos on paths

some typos breaking npm

I change the 3 images in range.css from Nis to NIS based on your advice as well. If that was really the issue just... 🤦 thank you so much. I wasn't aware of that quirk.


extend documentation [wip]

Improving the documentation. In particular

make left content table more granular
top titles can be linked to left menu items

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
the actual version is https://torch-lightning.readthedocs.io/en/docs

@williamFalcon @jeffling @Ir1d @neggert ^^

These changes are a net good, though I found a small grammar error.

Not good? so what other changes do you recommend?

Reading through the docs, I think the
formatting is broken.

is it a specific error or is it on multiple places?

I couldn't find any other examples of that formatting, so maybe it's just isolated


Custom builds are created in the cloud

Problem: Custom builds  and Booking builds currently require engineers to check out branches and run scripts on their local machines. This requires every engineer in the guild to have to install and set up a lot of dependencies such as grafana-build, docker, push permissions for GCP etc. The build job also takes a long time to complete and often fails on some machines for reasons unique to that engineer's personal device and set up. This also makes hand off difficult as some artifacts only exist on one person's machine until it is pushed.
Goal: Instead of running scripts locally we should build automation tooling that can be run in the cloud. Whether this is built with Drone or some other tool is TBD. This will eliminate the need for any local set up and thusly any bugs related to individual device set ups. This will also enable non-release engineers to be able to create custom builds themselves. This is currently a need specifically with the Booking releases as a non-release guild squad is going to take ownership of creating the Booking releases moving forward.
Requirements:

The new tooling has no local steps
A UI exists that is easy to use
Service account exists for the automation so that it has the correct permissions
Automation creates the built Grafana images and uploads them to GCP
Automation can build RPM packages
Documentation is updated
Runbooks are updated

Solution: We will need to add a new promotion pipeline in Grafana's drone.yml that will run grafana-build artifacts -a ....
It needs to be configurable with:

grafana-ref
enterprise-ref
artifacts (like rpm:linux/amd64:grafana)
version


[Feature Request] Support linux powerpc64le

I ran into following error when trying to compile under Linux powerpc64le:
~/Work/rustc_codegen_cranelift$ ./y.sh build
[BUILD] build system
[BUILD] rustc_codegen_cranelift
    Finished `release` profile [optimized] target(s) in 0.05s
[BUILD] sysroot Clif
[COPY] stdlib source
[PATCH] "stdlib" <- "0027-stdlib-128bit-atomic-operations.patch"
[PATCH] "stdlib" <- "0029-stdlib-rawdylib-processprng.patch"
   Compiling core v0.0.0 (/home/tle/Work/rustc_codegen_cranelift/build/stdlib/library/core)
   Compiling std v0.0.0 (/home/tle/Work/rustc_codegen_cranelift/build/stdlib/library/std)
   Compiling rustc-std-workspace-core v1.99.0 (/home/tle/Work/rustc_codegen_cranelift/build/stdlib/library/rustc-std-workspace-core)
error: can't compile for powerpc64le-unknown-linux-gnu: Support for this target has not been implemented yet

   Compiling compiler_builtins v0.1.106
   Compiling libc v0.2.153
error: could not compile `rustc-std-workspace-core` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `core` (lib) due to 1 previous error
error: could not compile `compiler_builtins` (lib) due to 1 previous error
error: could not compile `libc` (lib) due to 1 previous error
CARGO_BUILD_INCREMENTAL="true" CARGO_ENCODED_RUSTDOCFLAGS="" CARGO_ENCODED_RUSTFLAGS="-Zforce-unstable-if-unmarked\u{1f}-Cpanic=abort\u{1f}-Zcodegen-backend=/home/tle/Work/rustc_codegen_cranelift/./dist/lib/librustc_codegen_cranelift.so\u{1f}--sysroot\u{1f}/home/tle/Work/rustc_codegen_cranelift/./build/rtstartup\u{1f}-Zinline-mir" CARGO_PROFILE_RELEASE_DEBUG="true" RUSTC="/home/tle/.rustup/toolchains/nightly-2024-03-26-powerpc64le-unknown-linux-gnu/bin/rustc" RUSTDOC="/home/tle/.rustup/toolchains/nightly-2024-03-26-powerpc64le-unknown-linux-gnu/bin/rustdoc" __CARGO_DEFAULT_LIB_METADATA="cg_clif" "/home/tle/.rustup/toolchains/nightly-2024-03-26-powerpc64le-unknown-linux-gnu/bin/cargo" "build" "--manifest-path" "/home/tle/Work/rustc_codegen_cranelift/./build/stdlib/library/sysroot/Cargo.toml" "--target-dir" "/home/tle/Work/rustc_codegen_cranelift/./build/stdlib_target" "--locked" "--target" "powerpc64le-unknown-linux-gnu" "--release" "--features" "compiler-builtins-no-asm backtrace panic-unwind" exited with status ExitStatus(unix_wait_status(25856))

It would be awesome if this architecture is supported

This will need Cranelift support first: https://github.com/bytecodealliance/wasmtime/issues/1183


how can I upload DICOM file from modality to viewer.

Hello everyone.!, I'm working on a PACS project, I want to connect my front-end UI to viewer in doing this I'm facing problem in uploading DICOM images and pdfs, actually I'm unable to figure out from where I should start.

The viewer itself does not store DICOM files, you need to upload the files into the database which the viewer accesses, like orthanc or dcm4che, etc.

You need to have a dicomweb setup and OHIF connect to that


Release 0.2.1

@rultor release it; the tag is 0.2.1.

@rultor release it; the tag is 0.2.1.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it; the tag is 0.2.1.

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


Package errors looking for new maintainers

Hello,
Quite clearly this package has been unmaintained for a long time. There are two main reasons for this (along with several others — waves in the general direction of life)

I had hoped that with the integration of some of the ideas from this package into Go 1.8 (I think) then the use of and need for this package would decrease. Sadly for whatever reason Go errors did not obtain the feature that this package was built for — stack traces on errors, so the need for this package remained.
I no longer use this package, in fact I no longer wrap errors. This sounds like a grandiose claim, and it may be my quirky coding style (my other views on error handling are hardly commonplace), so I don’t mean this comment to be a judgement on anyone who uses this package and enjoys it. It’s simply that it’s hard to make time to work on something which I no longer believe in.

To that end, I welcome expressions of interest in the comments below.
Thank you

Curious, this package is under the pkg organization with a few well-respected folks from the Go community (at least those that are public), could them collectively lightly maintain pkg/errors in its current form? Having used this package from the very beginning one could argue its feature complete and doesn't need much maintenance.
For what it's worth I still use this package, and will continue to do so until the standard library is at least feature parity with pkg/errors. This was the premise of xerrors, but in my opinion it removed too many useful features, namely stack traces on errors.

@mfridman you are correct that this package pretty much does what it says on the tin, and at this point can’t really do something different without the trauma of introducing errors/v2.
Perhaps the better solution is to archive this project and let development continue in forks.

Pretty much any way its sliced will be a breaking change. The ideal scenario would have been for the Go team to provide a smooth transition to the standard library while offering the most common feature set among error packages, but that's not here nor there.
My vote goes towards sunsetting (archiving) this package with a short blurb on what this package is and maybe a small blurb on the history of how we got here.
If a fork spawns, and gains popularity .. it is what it is. But I'd rather see this package live another day in its current form, as opposed to new maintainers who (quite often) get feature happy.


added dap dashboard

Description:
Ticket number:
[OBS-XXX]
Checklist:

[ ] Is my change backwards compatible? Please include evidence
[ ] I have tested this and added output to Jira Comment:
[ ] Documentation added (link) Comment:

You'll need to add a corresponding module into the dashboards.tf file as well

@chrisdodd93 I have added.


Release v2.13.0+rev1

Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

Superseded by https://github.com/resin-os/resin-imx6ul-var-dart/pull/50


fix(resources): change time values to pointers

What this PR does / why we need it
Apparently, k8s does not handle well its own dateTime zero time values. Converter changes zero Time{} to "null" string - and from some unknown to me reason, K8S itself fails to accept 'null' as a valid dateTime value. This PR attempts to use ptr instead with omitempty as an attempt to fix this issue.

JIRA ID: [QSS-00]

Notes for your reviewers

Pull Request Test Coverage Report for Build 781

5 of 26 (19.23%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.5%) to 65.481%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/k8s/resources/resource_status.go
5
26
19.23%

Totals

Change from base Build 775:
-0.5%

Covered Lines:
1639

Relevant Lines:
2503

💛  - Coveralls

apparently, this fix is no longer needed, close it. the root cause of errors were incorrect definition of the dateTime in CRD:
wrong: { type: 'dateTime' }
right: {type: 'string', format='date-time' nullable: true}


Ensure merge transition block contains 🐼

Given the importance of graffitis for representing significant moments in blockchain history, e.g., Bitcoin and beacon chain genesis blocks, the merge transition block's graffiti MUST refer to the panda as the universally agreed mascot. This patch ensures that all implementations adhere to this convention.

I really appreciate the Idea. Feels strange that this hasn't been in the specs since beginning...
Anyway I'd suggest to allow "🐼" at any position in the Graffiti (even multiple times). We should just enforce it's there at least once 😄

Allow 🐼 anywhere in graffiti
Add unit tests

I really appreciate the effort! Imagine the Merge is stumbling because proposers are failing to put panda into the right place 😂 Btw, PR misses corresponding changes to validator.md. Even though they are done I can't give any promise on this change making it's way into the spec 😄

Update validator.md to delay the merge if the configured graffiti lacks 🐼 by proposing a regular block without ExecutionPayload instead.

Just tell Mr. F. to change his graffiti.

The nice thing about this PR is that individual node operators, and even consensus layer implementations, can opt-in to support it on their own. Having a --graffiti-special flag in nodes would allow staking pools etc to collaborate and try to get a message in for special occasions such as this one. The flag could be re-used in the future as well, and the marketing aspects are also valid factors (some people care more than others). Certain clients already implement panda art as well to celebrate the merge, so having a flag to override graffitis does not seem too far off: https://github.com/sigp/lighthouse/blob/aa72088f8fc91d41106a8afce7a0179cde64ce5d/beacon_node/beacon_chain/src/block_verification.rs#L85-L107
Regarding the consensus-layer rule: The way how it is proposed here is simple enough to implement, and makes inconsistencies between different Unicode libraries irrelevant – it is a simple check against a static sequence of data, and it does not interpret the graffiti or run expensive string validation. It could be fun to see both false-negatives of people trying to apply skin-tone modifiers to other bears and getting rejected for trying to be too smart, or false-positives of people trying to make the panda-sequence appear as part of other characters but rely on different segmentation to have it actually rendered differently.
In the end, the miners are able to collaborate and decrease global hashrate to push the TTD far into the future (they would still have to buy up all the GPU stock to avoid others pumping hashrate), and with the panda PR, stakers could then proceed to delay the merge by avoiding the panda, because maybe they want to finish pruning their EL or whatever. This moves the authority to answer "when merge" entirely to the community (for both the EL and the CL).
🐼

It's another thing that could go wrong during launch.

On the other hand, allowing non-panda merge transition blocks would enable panda maxis to potentially trigger heavy forking around the transition period by orphaning those branches that they deem unviable. This PR mitigates this risk by allowing non-panda blocks to continue build a canonical chain as usual, until a panda is found. Should we really trust node operators who are unable to properly configure their graffiti with such a critical role during the PoS upgrade process?
🐼

https://user-images.githubusercontent.com/89844309/169840163-a406cc7b-9b97-4be0-9151-f0cd8f426b60.mov

🐼 art has been integrated into Nimbus: https://github.com/status-im/nimbus-eth2/pull/3670

🐼 viewing in Windows command prompt, or Linux/macOS Terminal:
curl https://raw.githubusercontent.com/status-im/nimbus-eth2/v22.6.0/beacon_chain/consensus_object_pools/vanity_logs/blink-version.ans

(there is no | sudo bash in it, no worries).

closing due to insurmountable complexity and liveness issues

** sad panda sounds **

GitHub has added a little banner on top of PRs from branches containing emoji (and Unicode RTL-overrides!), and appears to also have fixed the display of pandas in the little messages through the conversation when force-pushing such branches.


CUDA OUT OF MEMORY

Hi, I'm trying to run inference as you mentioned, but instead I've gotten this error every time;
RuntimeError: CUDA out of memory. Tried to allocate 602.00 MiB (GPU 0; 5.70 GiB total capacity; 2.97 GiB already allocated; 340.50 MiB free; 3.57 GiB reserved in total by PyTorch) If reserved memory is >> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF
Can you help me about it?
Thanks

Hi @feritstar
Sorry for the late reply. Unfortunatelly I can't help with such hardware issue, could you try the code to the GPU with better capacity? Alternatively, you could run the code on the images with lower resolution.
Thanks for you interest.
Cheers,
Yuyuan


[HIPIFY] Multiple files in-place hipification issue

After using hipconvertinplace-perl.sh command I'm getting following warning:

According to my observation this is because of this following two functions:
template
global
void cudaEncode(const uint maxbits,
const Scalar* scalars,
Word *stream,
const uint3 dims,
const int3 stride,
const uint3 padded_dims,
const uint tot_blocks) { Some commands written over here}
.
.
.
hipLaunchKernelGGL(cudaEncode, dim3(grid_size), dim3(block_size), 0, 0, maxbits,
d_data,
stream,
dims,
stride,
my_pad,
my_blocks);
Will you please tell me exactly what is the problem. Because of this warning, while testing the application I'm getting following error:
Error: Missing metadata for global function

If I'm replacing cudaEncode with hipEncode the warnings got resolved. But while testing the ported application, still I'm getting the error: missing metadata for global function

It's a known issue with multiple in-place hipification; there is a feature request for it: #1246. I'm working on it currently. Could you please hipify not in-place till the feature is implemented?

while using with hipify-perl also there is an issue with hipLaunchKernelGGL(as above comment), and replacing cudaEncode with hipEncode the warnings got resolved
cuda_]$ /opt/rocm/hip/bin/hipify-perl  decode1.cuh > decode1.cpp
warning: decode1.cuh:#32 : cudaDecode1(Word *blocks,
warning: decode1.cuh:#116 :   hipLaunchKernelGGL(cudaDecode1,dim3(grid_size),dim3(block_size),0,0,stream, d_data, dim, stride, zfp_pad, zfp_blocks,maxbits);
decode1.cpp

Currently, there is no solution for implementing include files dependency graph in hipify-perl. You have two options here:

Do not use --inplace option.
To form the list of input source files manually.

Can we fix this for hipify Perl?
On Nov 21, 2019, at 7:15 AM, Evgeny Mankov<EMAIL_ADDRESS>wrote:
 [CAUTION: External Email]
Currently, there is no solution for implementing include files dependency graph in hipify-perl. You have two options here:

Do not use --inplace option.
To form the list of input source files manually.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FROCm-Developer-Tools%2FHIP%2Fissues%2F1655%3Femail_source%3Dnotifications%26email_token%3DAATBEATY4STOR4NPLOGKANLQU2JXDA5CNFSM4JNLIM7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE2LRCQ%23issuecomment-557103242&data=02|01|ben.sander%40amd.com|25bc1e7449174d8ab00508d76e8d3a30|3dd8961fe4884e608e11a82d994e183d|0|0|637099425207853210&sdata=k93TrN5Ey9pGqUde1whn0su%2FLzJdfvuUk%2BuZVIULfsg%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAATBEAXXGL2VZ6PEZANEKHLQU2JXDANCNFSM4JNLIM7A&data=02|01|ben.sander%40amd.com|25bc1e7449174d8ab00508d76e8d3a30|3dd8961fe4884e608e11a82d994e183d|0|0|637099425207853210&sdata=XV%2BYQ4fkRQxLmk3iFt1jrN4lbHVIFOULSSqqUmymuT8%3D&reserved=0.

@bensander, implementing it for hipify-clang (#1246) is in progress. The upcoming solution is based on include header files dependency graph. As for hipify-perl, I will think about it more, but currently I have no solution to implement the same in it.

I think, Issue still exists with the  list of input source files manually.
Example:
[taccuser@ROCm-CentOS76-2 bin]$ ./testZfpCuda1dDouble
[==========] Running 5 test(s).
[ RUN      ] when_seededRandomSmoothDataGenerated_expect_ChecksumMatches
[       OK ] when_seededRandomSmoothDataGenerated_expect_ChecksumMatches
[ RUN      ] given_Cuda_1dDoubleReversedArray_when_ZfpCompressDecompressFixedRate_expect_BitstreamAndArrayChecksumsMatch
terminate called after throwing an instance of 'std::runtime_error'
what():  Missing metadata for global function: _ZN5cuZFP10hipEncode1IdEEvjPKT_Pyjijj
[BackTrace]
#0  0x00007ffff677c207 in raise () from /lib64/libc.so.6
#1  0x00007ffff677d8f8 in abort () from /lib64/libc.so.6
#2  0x00007ffff58537d5 in __gnu_cxx::__verbose_terminate_handler() () from /lib64/libstdc++.so.6
#3  0x00007ffff5851746 in ?? () from /lib64/libstdc++.so.6
#4  0x00007ffff5851773 in std::terminate() () from /lib64/libstdc++.so.6
#5  0x00007ffff5851993 in __cxa_throw () from /lib64/libstdc++.so.6
#6  0x00007ffff5b3ce4e in hip_impl::hip_throw(std::exception const&) () from /opt/rocm/hip/lib/libhip_hcc.so
#7  0x00007ffff5b15ce7 in hip_impl::program_state_impl::kernargs_size_align(unsigned long) () from /opt/rocm/hip/lib/libhip_hcc.so
#8  0x00007ffff5b158b9 in hip_impl::program_state::get_kernargs_size_align(unsigned long) () from /opt/rocm/hip/lib/libhip_hcc.so
#9  0x00007ffff7a830ce in hip_impl::kernarg hip_impl::make_kernarg<unsigned int, double const*, unsigned long long*, unsigned int, int, unsigned int, unsigned int, unsigned int, double const*, unsigned long long*, unsigned int, int, unsigned int, unsigned int>(void ()(unsigned int, double const, unsigned long long*, unsigned int, int, unsigned int, unsigned int), std::tuple<unsigned int, double const*, unsigned long long*, unsigned int, int, unsigned int, unsigned int>) () from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#10 0x00007ffff7a82f4f in void hipLaunchKernelGGL<unsigned int, double const*, unsigned long long*, unsigned int, int, unsigned int, unsigned int, void ()(unsigned int, double const, unsigned long long*, unsigned int, int, unsigned int, unsigned int)>(void ()(unsigned int, double const, unsigned long long*, unsigned int, int, unsigned int, unsigned int), dim3 const&, dim3 const&, unsigned int, ihipStream_t*, unsigned int, double const*, unsigned long long*, unsigned int, int, unsigned int, unsigned int) ()
from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#11 0x00007ffff7a82ddd in unsigned long cuZFP::encode1launch(unsigned int, int, double const*, unsigned long long*, int) ()
from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#12 0x00007ffff7a82b11 in unsigned long cuZFP::encode1(int, int, double*, unsigned long long*, int) ()
from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#13 0x00007ffff7a7aad7 in unsigned long internal::encode(unsigned int*, HIP_vector_type<int, 3u>, int, double*, unsigned long long*) ()
from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#14 0x00007ffff7a7a45d in cuda_compress () from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#15 0x00007ffff7a5f9f7 in zfp_compress () from /home/taccuser/Desktop/Anil_Bommareddy/zfp_old/build/lib64/libzfp.so.0
#16 0x000000000040328f in runCompressDecompressTests.constprop.8 ()
#17 0x0000000000408d26 in cmocka_run_one_test_or_fixture ()
#18 0x0000000000408fd3 in cmocka_run_one_tests ()
#19 0x00000000004093e5 in _cmocka_run_group_tests ()

I think, Issue still exists with the list of input source files manually.
Example:
[taccuser@ROCm-CentOS76-2 bin]$ ./testZfpCuda1dDouble
[==========] Running 5 test(s).
[ RUN ] when_seededRandomSmoothDataGenerated_expect_ChecksumMatches
[ OK ] when_seededRandomSmoothDataGenerated_expect_ChecksumMatches
[ RUN ] given_Cuda_1dDoubleReversedArray_when_ZfpCompressDecompressFixedRate_expect_BitstreamAndArrayChecksumsMatch
terminate called after throwing an instance of 'std::runtime_error'
what(): Missing metadata for global function: _ZN5cuZFP10hipEncode1IdEEvjPKT_Pyjijj

Nope, it is a runtime issue, definitely unrelated to in-place hipification of multiple files.

@chinchoretej, could you please confirm, that the sorting of input files is correct for hipify-clang? As for hipify-perl, I'm still thinking of how to implement the same in it.

@emankov
I have compiled the files with -fno-gpu-rdc flag and the problem is solved. I have not tried with hipify-clang.
So, I think there is no file dependency issues.
eg. hipcc -fno-gpu-rdc


Improve Recommendations

Currently, recommendations are a random pick from the top-rated items in a user's library, optionally filtered on a user-specified genre.  We can probably get more clever than that, though.
If it's at all possible, it'd be nice if a user requested a movie suggestion, the skill looked at the last N movies watched, and picked 'similar' movies.  Probably simply picking based on the mostly commonly-watched genre is the way to go, but perhaps there are other things we can do too.
Further, it'd be nice to be able to say something along the lines of play a movie like ghostbusters and have it choose a random movie that is 'similar'.
Ultimately we need to really define all of this, but it's something worth discussing.

I like that. Also, forgive me if this is possible already we could say play the next Harry Potter Movie when they are all in a collection.
Cheers

You should open a new Issue for that since it's not technically a recommendation -- it's an addition to the playback commands.

Right you are...


Added new footer section design

Description
In this pull request, I have made the following changes to the footer section design:

Updated the newsletter design to improve its visual appearance.
Added the website logo to the footer section for better branding and recognition.
Adjusted the alignment and positioning of the social media icons and other footer content for better layout and responsiveness across different screen sizes.

Related Issues

Closes #535

Type of PR

[X] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
Before:

After:

Checklist

[X] I have gone through the contributing guide
[X] I have updated my branch and synced it with project main branch before making this PR
[X] I have performed a self-review of my code
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional context:
The updates to the footer section design aim to improve the overall user experience and visual appeal of the website. The newsletter design has been updated to make it more visually appealing and encourage user engagement. The addition of the website logo in the footer section reinforces the branding and helps users quickly identify the website they are visiting. Furthermore, the adjustments made to the alignment and positioning of the social media icons and other footer content ensure a consistent and responsive layout across different screen sizes, enhancing the overall usability of the website.

why this header is disturbed in you deployment

@Anishkagupta04 I was assigned to redesign the footer section according to my idea so as per the website color theme and design I have only updated the footer section by moving the newsletter part above the footer section to make it more clearly visible and attractive and making other changes in the footer. I have made no changes to the header. It would be helpful for me if you could explain which part you are specifying.

@DebapriyaJha Resolve conflicts

@varshith257 Resolved the conflicts. Please merge the PR.
Thank you

@DebapriyaJha Good to merge after fixing conflicts. Tag me incase to get merged it

@varshith257 check once I have resolved the conflicts


feat: README update

Description
Updating CLI README, preview in branch:

[x] updated license year
[x] removed Maintainers section (is irrelevant)
[x] updated header to use homebrew badge instead of npm
[x] updated header to correspond better with OneSDK repo
[x] added links to home, docs, support etc in the header
[x] removed Support section, now linked in header
[x] updated installation command
[x] review/remove Security section (irrelevant now, the docs has guide on setting API keys)
[x] review Background section

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have updated the documentation accordingly. For updating Oclif commands documentation use oclif-dev.
[ ] I have read the CONTRIBUTION_GUIDE document.
[ ] I haven't repeated the code. (DRY)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Maybe I would keep the support section 🤷🏻♂ but it is not blocking.

Honestly I don't think it was that useful where it was (below docs). Now the header includes links to both docs and support page :)


Clarified location of swf file

Previously discussed with @jonrohan...
In order for it to work "out of the box," the .swf file must be in the same folder as the .js files. The current description of "the same folder as your web page" could be understood as the root site folder, which will not work "out of the box."

:+1: @JamesMGreene. @thadseaver sent me an email talking about the potential confusion that occurred when setting up ZC. This change just helps clarify that when the .swf and the .js are in the same directory on the web server, ZC will just work.

:star: Thanks @thadseaver

Good catch, @thadseaver.  The text you cited used to be true but not since v2.x. :+1:

@jonrohan @JamesMGreene , Glad to be able to give back, guys, no matter how small the contribution. Thank you both for the work that you do on ZeroClipboard!


[language] use u128 instead of u64 for market cap

Motivation
Testnet minting can fail when the market cap approaches U64_MAX. Changing the market cap to u128 will fix this problem.
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Functional tests still pass, should be pure refactoring.

Looks like it's failing due to CastU128 being unimplemented in bytecode-to-boogie. Disabling the test for the libra_account module in bytecode-to-boogie/tests/translator_tests.rs should fix it for now. (Only suggesting it as a last resort -- let's try to fix bytecode-to-boogie if it's easy.)

CC @shazqadeer, @DavidLDill, @wrwg to look at the Boogie changes

@bors-libra r=vgao1996

:pushpin: Commit 5b0fbea has been approved by vgao1996

:hourglass: Testing commit 5b0fbea5a7ccd1b50ea55914acac9bc43fb76714 with merge 619c9ffcaa5b6acabd0df9572343d3a374805298...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: vgao1996
Pushing 619c9ffcaa5b6acabd0df9572343d3a374805298 to master...


Phase2 (b): Perception for TurtleBot 4 Open CV and MediaPipe: 3D Objects

[In Progress] [(TODO) Update Description]
Implementation of the 3D object detection using openCV and MediaPipe

Progress:
--- setting object detection only for one class - Shoe---
ros2 run unit02_simulation_motion_planner tb4_3D_perception
Add Shoe objects in the gazebo world to detect shoes
Output:

One thing I might add, it is a bit too late now, is that it would have been nice to output the detected objects as some sort of topic. The drawback here is that doing this well is a bit of a rabbit hole in terms of what the messages should look like.

Added new publishers for detected Image and detected Pose of the Object


cmd: add view-fits

fixes #12

it would be great UI-wise, to add a help menu so users can get the basic usage commands.
it's relatively easy to do so via the flag package:
https://godoc.org/flag#example-package

PTAL

LGTM.
please squash and re-push, and then it's good to go.
(it would be great to also be able to view remote files - over http(s), ftp, ssh, etc... - but this can be for another CL)

thanks.


Add WASM Code Generator

closed by https://github.com/making/bfc/commit/0b97cb9287e920e2bde691f86f09b73fa06fdac3


chore(avm)!: make indirects big enough for relative addressing

Merge activity

Oct 3, 11:14 AM EDT: @fcarreiro merged this pull request with Graphite.


V1.0.0 docs prep

Synced chatbot, codegen, and summarizer README's in preparation for v1 release.
They should now only differ in their references to their respective directory or app name.

Documentation updates related to #262


chore(readme): add 2 beautiful badges

What type of PR is this?
/kind cleanup

Any specific area of the project related to this PR?
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 0b75d1c43e524366dca7398e2358015fa1ae3d2a

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dwindsor, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,dwindsor]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Fix Location macro to be hermetic

Fixes https://github.com/scalameta/munit/issues/382
Problem
The Location macro currently captures the absolute path of the source file, which is not hermetic, and won't cache correctly on remote cached build tools such as Bazel, Gradle, and (in development) sbt 2.x.
$ jardiff target/out/jvm/scala-3.4.2/inctest/test-backend/ ../inctest2/target/out/jvm/scala-3.4.2/inctest/test-backend/
diff --git a/example/CowTest.class.asm b/example/CowTest.class.asm
index 1b3911e..91fd219 100644
--- a/example/CowTest.class.asm
+++ b/example/CowTest.class.asm
@@ -56,7 +56,7 @@
     ]
     NEW munit/Location
     DUP
-    LDC "/Users/xxx/work/inctest/src/test/scala/example/CowTest.scala"
+    LDC "/Users/xxx/work/inctest2/src/test/scala/example/CowTest.scala"
     BIPUSH 6
     INVOKESPECIAL munit/Location.<init> (Ljava/lang/String;I)V
     INVOKEVIRTUAL example/CowTest.assert (Lscala/Function0;Lscala/Function0;Lmunit/Location;)V

Solution
This captures the relative path from the working directory instead.

Let me know if you need a release right away.

It would be great if could get a release this week or next. Thanks!

It's running! https://github.com/scalameta/munit/actions/runs/10847736559


[Dynamic Regions] many sst files left in the import directory after br restore

Bug Report

What version of TiKV are you using?

nightly
What operating system and CPU are you using?

Steps to reproduce

I used br to restore about 500GB data into a fresh cluster with partition-raft-kv enabled. After br finished I found there were about 1200 sst filed under the import dir with a total size about 55GB. And after 24h, these sst files were still not cleaned up.
And when I restart the cluster I could see a lot of ingest sst operations in the tikv log. This also make the restart much longer than expected before the foreground qps is stable.
What did you expect?
No or little sst files should be left for a long time after br restore.
What did happened?

@overvenus @tonyxuqqi  @SpadeA-Tang  Do you have any suggestions?
Also cc @3pointer

As discussed offline, one possible solution to this issue is that TiKV can periodically (or triggered by ingest sst event) manual-flush tablet so that flushed index can be advanced in time, as described in https://github.com/tikv/tikv/issues/14914

As discussed offline, one possible solution to this issue is that TiKV can periodically (or triggered by ingest sst event) manual-flush tablet so that flushed index can be advanced in time, as described in #14914

@overvenus The problem is if there's no memtable, then flush will not help.

As discussed offline, one possible solution to this issue is that TiKV can periodically (or triggered by ingest sst event) manual-flush tablet so that flushed index can be advanced in time, as described in #14914

@overvenus The problem is if there's no memtable, then flush will not help.

It does not matter whether there is a memtable or not, once (synchronously) manual-flushed is done, we know all changes that are less or equal to the modified index are persisted to disk.


Support for hostAliases

Hello,
My output has ssl => true, a certificate, and a host with an IP address. The host gave me a self-signed cert with a peer name such as 'elastic-server'.
I would rather not use ssl_certificate_verfication => false. Is it possible to get an update to values.yaml to add hostAliases? Is there a way to modify hostAliases without modifying the helm chart?
Thanks

for what it's worth, adding this to statefulset.yaml worked...
      hostAliases:
      - ip: <IP_ADDRESS>
        hostnames:
        - "foo.bar"

I know it doesnt pull in from values.yaml and it's bit of a hack, but just showing that it's possible.
# Kubernetes-managed hosts file.
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
fe00::0 ip6-mcastprefix
fe00::1 ip6-allnodes
fe00::2 ip6-allrouters
<IP_ADDRESS>      logstash-logstash-0

# Entries added by HostAliases.
<IP_ADDRESS>     foo.bar

Hi @jcon321,
Thanks for openning this request.
Adding HostAliases support to Elastic charts could be great. Are you interested in creating a PR for that?


CI failing

Hi,
hpp-doc devel branch is failing with:
[ 26%] Building CXX object CMakeFiles/hpp-constraints.dir/src/distance-between-bodies.cc.o
In file included from /workspace/src/hpp-constraints/src/distance-between-bodies.cc:20:0:
/workspace/src/hpp-constraints/include/hpp/constraints/distance-between-bodies.hh: In member function 'virtual bool hpp::constraints::DistanceBetweenBodies::isEqual(const hpp::constraints::DifferentiableFunction&) const':
/workspace/src/hpp-constraints/include/hpp/constraints/distance-between-bodies.hh:107:19: error: no match for 'operator!=' (operand types are 'hpp::constraints::DistanceBetweenBodies::GeometryData {aka pinocchio::GeometryData}' and 'hpp::constraints::DistanceBetweenBodies::GeometryData {aka pinocchio::GeometryData}')
         if (data_ != castother.data_)
             ~~~~~~^~~~~~~~~~~~~~~~~~
In file included from /workspace/install/include/pinocchio/multibody/fcl.hpp:239:0,
                 from /workspace/install/include/pinocchio/multibody/geometry.hpp:8,
                 from /workspace/src/hpp-constraints/include/hpp/constraints/distance-between-bodies.hh:23,
                 from /workspace/src/hpp-constraints/src/distance-between-bodies.cc:20:
/workspace/install/include/pinocchio/multibody/fcl.hxx:64:15: note: candidate: bool pinocchio::operator!=(const pinocchio::GeometryObject&, const pinocchio::GeometryObject&)
   inline bool operator!=(const GeometryObject & lhs, const GeometryObject & rhs)
               ^~~~~~~~
/workspace/install/include/pinocchio/multibody/fcl.hxx:64:15: note:   no known conversion for argument 1 from 'hpp::constraints::DistanceBetweenBodies::GeometryData {aka pinocchio::GeometryData}' to 'const pinocchio::GeometryObject&'

ref. https://gitlab.laas.fr/humanoid-path-planner/hpp-doc/-/merge_requests/12

Update: I forgot to upgrade pinocchio version in the devel makefile, the CI is running again.

That's fixed :)


doesn't compile using gomobile (for android/ios)

First there is an issue with pthread that I can get past, but then it seems to struggle linking with symbol conflicts.  I know sqlite and go both work on android, so i'm not sure why there is symbol duplication here.
example
// github.com/mattn/go-sqlite3/example2/test.go
package example2

import (
	"database/sql"

	_ "github.com/mattn/go-sqlite3"
)

var (
	db *sql.DB
)

func OpenDatabase(filePath string) error {
	d, err := sql.Open("sqlite3", filePath)
	if err != nil {
		return err
	}

	db = d
	return nil
}

Trying to bind without any patches
}{mhawkins:~/Library/go/src/github.com/mattn/go-sqlite3/example2}{gomobile bind                      }{master!}{
# github.com/mattn/go-sqlite3
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lpthread
collect2: error: ld returned 1 exit status
gomobile: exit status 2

Making this change (turning off pthread for android, as the link is not required)
diff --git a/sqlite3_other.go b/sqlite3_other.go
index 8d98b4a..5c96d59 100644
--- a/sqlite3_other.go
+++ b/sqlite3_other.go
@@ -9,6 +9,6 @@ package sqlite3
 /*
 #cgo CFLAGS: -I.
 #cgo linux LDFLAGS: -ldl
-#cgo LDFLAGS: -lpthread
+#cgo linux,-android LDFLAGS: -lpthread
 */
 import "C"

Gets me past the android link issue.  Now i'm having symbol conflicts, though
}{mhawkins:~/Library/go/src/github.com/mattn/go-sqlite3/example2}{gomobile bind                      }{master!}{
# command-line-arguments
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/5l: running /Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/arm-linux-androideabi-gcc failed: exit status 1
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000004.o: multiple definition of '__aeabi_uidivmod'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000001.o: previous definition here
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000004.o: multiple definition of '__aeabi_uidiv'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000001.o: previous definition here
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000004.o: multiple definition of '__udivsi3'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000001.o: previous definition here
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000004.o: multiple definition of '__aeabi_unwind_cpp_pr0'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000001.o: previous definition here
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-929937803/000004.o: multiple definition of '__gnu_Unwind_Restore_VFP_D'

...AND MANY MORE....

Any ideas?  It seems it's a cgo link issue, but I'm not sure what it is.

Please remove LDFLAGS -lpthread from sqlite3_other.go,
it's never needed. Thanks.
See golang/go#10584 for the why android doesn't need
-lpthread.

I removed the link it but even when the contrived example i get the same errors
}{mhawkins:~/Library/go/src/github.com/mattn/go-sqlite3/example2}{gomobile bind                      }{master!}{
# command-line-arguments
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/5l: running /Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/arm-linux-androideabi-gcc failed: exit status 1
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-250010074/000004.o: multiple definition of '__aeabi_uidivmod'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-250010074/000001.o: previous definition here
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: error: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-250010074/000004.o: multiple definition of '__aeabi_uidiv'
/Users/mhawkins/Library/go/pkg/gomobile/android-ndk-r10d/arm/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld: /var/folders/9s/_chc2vkd5l3d7251t9sflgk5759k1h/T/go-link-250010074/000001.o: previous definition here

This is golang/go#9510.

@minux do you mean: remove -lpthread FOR ANDROID with remaining it on linux, right?

I mean you can remove -lpthread on every platform. Cgo will automatically
link pthread if necessary.

@minux okay, thanks.

Perhaps I'm a little slow, but I don't know how to fix the compilation issue with a dummy c file per https://github.com/golang/go/issues/9510
Could any of you fine folks explain what i need to do?  I'm sort of blocked.
Thanks!

Unfortunately there is no workaround for golang/go#9510.

golang/go#9510 is related issue of go-sqlite3?

It is related to the gomobile stuff.  Which sucks, because it's a
crazy common problem of mobile app code to need sqlite.  I am not sure
if it's possible to write an adapter to the system sqlite, but without
this I cannot move forward with gomobile for app business logic.  It
would require a pure go implementation of sqlite which doesn't exist
or an adaptable binding provided by gomobile which isn't planned.
Suck :(
On 4/29/15, mattn<EMAIL_ADDRESS>wrote:

golang/go#9510 is related issue of go-sqlite3?

Reply to this email directly or view it on GitHub:
https://github.com/mattn/go-sqlite3/issues/201#issuecomment-97487248

Android Native Application (seems to work)
If you use an Android native project, e.g. package main, go-sqlite3 seems to work. Take the example project golang.org/x/mobile/example/basic and add the sql example code from https://github.com/mattn/go-sqlite3/issues/201#issue-71331035
Then run on an ARM device or ARM emulator:
gomobile build .
gomobile install .

Android SDK Library (aar) (has duplicate symbols)
Trying to build an aar using gomobile bind -target android seems to fail as mentioned in https://github.com/mattn/go-sqlite3/issues/201#issue-71331035
If you pass some compiler-args to allow duplicate symbols, it at least compiles without errors. (Have not tested yet on device)
gomobile bind -target android -ldflags "-extldflags=-Wl,--allow-multiple-definition"

See:

https://github.com/golang/go/issues/9510#issuecomment-150272401


Investigate new triangulation library

https://github.com/mapbox/seidel
Investigate for speed and robustness.
In addition to the runtime for the algorithm itself, we also care about the shape of the triangles that it produces since this will impact the speed of the Cesium subdivision step and the number of triangles it produces.
@DavidHudlow this may be of interest to you.

@pjcozzi FYI I wrote a new JS library for triangulation, this time much more robust while being many times faster. It's pretty awesome. Check it out: https://github.com/mapbox/earcut

It focuses on triangulation speed over quality though — producing less sliver triangles is something I might look into in future.

Thanks for the note @mourner.  We'll have a look when we revisit this again.