An alternative way to make this work without adding dependencies is to use Node's `--es-module-specifier-resolution=node` flag. For example, `node --es-module-specifier-resolution=node dist/index.js`, where `index.js` would itself have ES-style imports without the .js file extension.


Hello, i understand this way for images.
Is there a similar way to do ir from video files?


@TheJoshuaTerry With GCC and the -std=c11 switch it compiles well, but VSCode marks it as an error.


Thanks for brining this up. I'm really unsure what the desired output type is.

There is also no generic and safe conversion
* **Decimal -> Uint128:** because information after the decimal point get lost
* **Uint128 -> Decimal:** because the range of Decimal is smaller since 18 digits are reserved for the data behind the decimal point

This makes it hard to say: Use this output type that can easily be converted.


Looking at URL it feels like this should not be implemented at all.


Yes, this is the same as URL and should be fixed in our next insiders and the root cause is being tracked by an internal bug (see URL


You should be able to work around it by adding a compilerArg of -fno-ms-extensions


@bobbrow We could ship 1.8.0-insiders3 this week instead of next week if we think a lot of users are hitting this (or related regressions).


There's a lot of stuff in flight for insiders3 so I'd like to wait until @Colengms is back and do it next week. There is a known work around for this issue (or folks can jump back to the stable release if it's severely impacting). We'll be in a much better place to do quick insiders updates when we start using the Marketplace features next week.


It also needs the hwsync suport which is already merged in LLVM.


Can someone who had CPU usage problem before to test this v4.13.2 release candidate build?

Changelog draft:
- Bundle proton-vpn-settings web client into the app (#470).
- Update @ProtonMail web clients stack. The `session.bin` file produced or modified by the v4.13.2+ app version won't be compatible with the previous app versions.
- Upgrade @electron.


Another idea that would improve our visibility of telemetry is URL What do you think?


Just tried the RC, and the issue has returned on my Arch Linux machine. One of the processes is again maxing out one thread. (Even after a restart)


@brandon-doornbos, thanks. That RC build is based on recently released @electron 16.0.6 which includes @chromium bump so I thought maybe the issue got fixed somewhere upstream in @chromium. So will be releasing a new version built on old/v15 @electron.

Doesn't happen to me on Linux for some reason.


It's Manjaro (Arch based). I would not ask someone to test the build if I could reproduce the issue at my side.

To face the issue, do I need to perform a specific action in the app or just start it and login into the proton account?

Please list them here. I don't believe though that @electron contributors will start actively looking into it until the minimal repro project gets provided (which normally hard to do for such kind of issues).

Btw. Notice the below note. So if you use persistent session feature you will have to keep using that RC build or login again if you prefer downgrading to a stable release (new release is coming soon). The reason is that @protomail changed the session credentials storage format in a web clients.


I tried it fresh on my laptop today, and the only thing I did was install the RC pacman file and then login. This did not do anything so then I closed the app and opened it again and upon logging in, one full thread utilized. On my PC, where I already had the previous version, I just installed the RC and it immediately did it upon logging in.

 URL which lists URL which I can't read. The other one I found was for a different version, sorry.

I just can't fathom what would cause this, as it is consistently happening to both my Arch machines but not your Arch based machine.
Is there something else that I could do to help with finding the cause? Are there debugging tools or something?


The app's code need to be compiled in "dev" mode in order to be able to open dev tools (I think it's a web/renderer process i a problematic one). There is no documentation on this matter. It's not a complex process but time-consuming, similar to what described in URL Debugging of the main process can be achieved as listed in URL but I tend to think that it's not the main process causes the problem.


Also starting from @electron v16 facing an abnormally high CPU load issue, see URL So had to downgrade to v15. Could not yet narrow down the scope.


Yes it's clear that it's a renderer process since we got screenshot provided in URL


What about this build? if it runs well I will be publishing it as a new release then.


Yep, no problems.

BTW, i built the thing and a dev build, so I'll see if I can find something.


+1, the type rendering is really bad, and as typography is the principal interface element of a terminal, it's hard to get excited to try using it, when my perfectly rendered Terminal.app is sitting right there.


@yolile Can you share an example with Sabah, in case she hasn't seen a good one before?


I have some examples in Spanish but not so many in English. But maybe the UK one is a good one URL and Zambia URL

In Spanish some examples are:
- URL
- URL
- URL


Yes, we can use Apache Phoenix to convert the SQL if needed.
Could you provide the design if we using Apache Phoenix in ShardingSphere?


Hello Miroslav @miroslavpejic85
Thank you for the suggestion, `MiroTalk` will be available on _Best of JS_ very soon.

About tagging:

- we have a `video` tag: URL
- we don't have `p2p` but we have `decentralized`: URL does it make sense to assign it to `MiroTalk`? Or should I rename it `p2p`, it would be better?

Thank you for your help! (tagging is so difficult 😅 )


Hello @michaelrambeau, thank you very much.

For this version, in case you could also add the video tag, so

bash
WebRTC, Websocket, Video, Real-Time

You're right, sorry, decentralized is fine in place of p2p.

In theory there are two versions of MiroTalk, this one (SFU) and the MiroTalk P2P (Decentralized)

## MiroTalk P2P

Best of JS is for the most popular open-source projects related to the web platform and Node.js.

What is the URL of the project you'd like to add to Best of JS?

GitHub: URL
Demo: URL

Before submitting the request to add a new project, please check the following points:

- ✅ The project is related to the web platform or Node.js
- ✅ The project has more than 100 stars on GitHub
- ✅ The project has thorough documentation in English
- ✅ The project is not deprecated and actively maintained

How would this project be tagged? (Pick one or several existing tags from this list: URL

WebRTC, Decentralized, Websocket, Video, Real-Time

Also you can suggest new tags to add if you think Best of JS is missing useful tags.

---

Does it make sense to add both of them, or just the first one ?

The difference between 2 you can check out here

Thanks to you and nice to meet you :)


@miroslavpejic85 Nice to meet you too 😄

Thank you for the explanations.

Just to confirm, there will be two projects on _Best of JS_:

- MiroTalk SFU
- MiroTalk P2P (this one will have the tag `decentralized`... that I should rename `P2P`maybe, I'm not sure which term makes more sense for most of the users)


@michaelrambeau Yeah :)

`MiroTalk SFU` - Tags: WebRTC, Websocket, Video, Real-Time
`MiroTalk P2P` - Tags: WebRTC, Decentralized (or p2p as you prefer), Websocket, Video, Real-Time

Thank you again!


Hi 5833tP2,

Did you find any solution to this? I've been spending two days trying to resolve the same issue looking at the Indexhibit forum, but I haven't found any solution and I've made too many attempts at changing so nothing works anymore.

Slightly panicked too :)
Thanks !
Trd


No solution at all, I'm afraid @TandiRD. I got no response to my posting. In depseration, I migrated my site to another platform. I hated having to do it but there was no other option for me. You could try emailing Vaska directly at studio@vaska.com. Sorry I don't have better news.


This has happened to me over time, with various hosts deprecating EOL'ed PHP versions. I think I recall trying to get in touch with the devs directly as well. Tragically I decided to move away from indexhibit as it seems more or less retired by the devs. Unfortunate loss of an elegant and fun tool.


Currently all the wheels are built by GitHub Actions, in this job: URL

GitHub doesn't directly support ARM runners as far as I know (but I could be wrong), so getting additional wheels up probably requires some sort of virtualization. I'm sure something with QEMU is possible, but I don't have a ton of experience with this. Things might get a lot easier if we could use URL directly for this, but I'm not sure.


Thank you both @5833tP2 & @kees- for the fast reply! I'll try e-mailing Vaska and if not migrating to another site. That would be a pitty though, Indexhibit is such a good tool. I don't understand how the passage to php 8 could mess it all up. I thought it was an advantage to always have the last version.


Hello Miroslav @miroslavpejic85 , done, please check!

You look like the super star of the `Video` section 😄 : URL

image


...but sorry I made a mistake with the tagging, I'm going to fix it.


...done, please check again. The screenshot has been edited.


Good progress last week, we are close to the end of the first version I think (improvements will be needed):
Cypress_ok
We are now more familiar Cypress so coding new scenarios is faster.


Hello again, well I could not find anything with just the normal debugging tools, and if I would want to debug electron itself, well, debug symbols. The whole electron repository doesn't even fit on my drive so that's a no.

Let's hope that this gets fixed accidentally someday.


I cannot reproduce it in my environment, FreeBSD 13, Python 3.9.8, Pygments 2.7.2, GNU diff 3.8, with standalone server.

My viewvc.conf:

[general]
cvs_roots = irregular-rcs-test: /home/cvs/irregular-rcs-test
svn_roots = test_repo: /home/futatuki/tmp/svn-test/testrepo,
 svn_cython: /home/futatuki/tmp/svn-test/svn_cython,
 (ommit some repos for privacy)
 bad-utf8-test: /home/futatuki/tmp/svn-test/bad-utf8-test
[utilities]
diff = /usr/local/bin/gdiff
[options]
allowed_views = annotate, co, diff, markup, roots, tar
use_rcsparse = 1
stacktraces = 1
[templates]
[cvsdb]
[vhosts]
[authz-forbidden]
[authz-forbiddenre]
[authz-svnauthz]

Could you tell us about your environment in detail?

P.S.

It is not correct. Subversion 1.14.x still supports Python 2 bindings, although it needs SWIG and extra steps for building. I also personally provide a Subversion 1.14.x package for el7 with both of Python 2 and Python 3 bindings, on URL (but no warranty).


... however, I found "full color diff" does not work correctly in my environment. It shows "- No changes -" even other formats show changes.


Similar issue: URL

I currently use GitHub Actions to build all the wheels. If there's an easy way to get Actions (and particularly the `actions/setup-python@v2` helper that we use here) to install these versions of Python, I'd be happy to add that. According to these docs there might be:

 URL
 URL

That said, if we add something like `3.11.0-alpha.3`, we might want to think a bit about what our update policy is. As new alphas come out, do we expect to add them to the build "whenever"? Or is there some way to automate this? Maybe check for new Python versions persistently, like once a day, rather than tying them exclusively to versions bumps of this library? Not sure what's the most reasonable solution here.


True, I've honestly been only building wheels for linux, but most of my projects have no building deps so it doesn't make much of difference (which is why I haven't tried anything else yet).
Gonna give you a hand later today


Thanks for looking into this, @futatuki. I have edited by original post above with the system details and the stripped down ViewCS configuration file.

Thanks for the link to your site. We will be reviewing the information.


Just noticed @futatuki is using the "stacktraces" option.

Here's the full "trackback" for the "colored" diffs:

Python Traceback
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 5521, in main
 request.run_viewvc()
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 457, in run_viewvc
 self.view_func(self)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 4117, in view_diff
 generate_page(request, "diff", data)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 1024, in generate_page
 template.generate(server_fp, data)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 347, in generate
 self._execute(self.program, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 582, in _cmd_if_any
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 625, in _cmd_for
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 604, in _cmd_is
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 624, in _cmd_for
 for item in list:
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/idiff.py", line 32, in sidebyside
 fromlines = list(map(_stripnl, fromlines))
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/idiff.py", line 30, in _stripnl
 return line.rstrip("\n")
TypeError: a bytes-like object is required, not 'str'

We had to switch to the "default" template to get the stacktraces option to work.

For the "unidiff" view, the full traces are as follows:

Python Traceback
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 5521, in main
 request.run_viewvc()
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 457, in run_viewvc
 self.view_func(self)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 4117, in view_diff
 generate_page(request, "diff", data)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/viewvc.py", line 1024, in generate_page
 template.generate(server_fp, data)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 347, in generate
 self._execute(self.program, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 582, in _cmd_if_any
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 625, in _cmd_for
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 604, in _cmd_is
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/ezt.py", line 624, in _cmd_for
 for item in list:
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/idiff.py", line 86, in unified
 for row in _trim_context(diff, context):
 File "/usr/local/viewvc-1.3.0-dev-f97ea61/lib/idiff.py", line 123, in _trim_context
 for line in lines:
 File "/usr/lib64/python3.6/difflib.py", line 907, in compare
 yield from g
 File "/usr/lib64/python3.6/difflib.py", line 1014, in _fancy_replace
 yield from self._qformat(aelt, belt, atags, btags)
 File "/usr/lib64/python3.6/difflib.py", line 1059, in _qformat
 yield "- " + aline
TypeError: must be str, not bytes


Looks like hr_intraline needs to be set to reproduce the errors. I've edited my original post once more.


Thank you for finding out it. With `hr_intraline = 1`, I can reproduce the issue in "full color diff". However, in "unidiff" view, I got another exception:

 File "/home/futatuki/work/viewvc/lib/viewvc.py", line 5521, in main
 request.run_viewvc()
 File "/home/futatuki/work/viewvc/lib/viewvc.py", line 457, in run_viewvc
 self.view_func(self)
 File "/home/futatuki/work/viewvc/lib/viewvc.py", line 4117, in view_diff
 generate_page(request, "diff", data)
 File "/home/futatuki/work/viewvc/lib/viewvc.py", line 1024, in generate_page
 template.generate(server_fp, data)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 347, in generate
 self._execute(self.program, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 582, in _cmd_if_any
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 625, in _cmd_for
 self._execute(section, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 604, in _cmd_is
 self._do_if(value, t_section, f_section, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 615, in _do_if
 self._execute(section, fp, ctx)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 524, in _execute
 method(method_args, fp, ctx, filename, line_number)
 File "/home/futatuki/work/viewvc/lib/ezt.py", line 624, in _cmd_for
 for item in list:
 File "/home/futatuki/work/viewvc/lib/idiff.py", line 86, in unified
 for row in _trim_context(diff, context):
 File "/home/futatuki/work/viewvc/lib/idiff.py", line 123, in _trim_context
 for line in lines:
 File "/usr/local/lib/python3.9/difflib.py", line 872, in compare
 yield from g
 File "/usr/local/lib/python3.9/difflib.py", line 979, in _fancy_replace
 yield from self._qformat(aelt, belt, atags, btags)
 File "/usr/local/lib/python3.9/difflib.py", line 1015, in _qformat
 atags = _keep_original_ws(aline, atags).rstrip()
 File "/usr/local/lib/python3.9/difflib.py", line 717, in _keep_original_ws
 return ''.join(
 File "/usr/local/lib/python3.9/difflib.py", line 718, in
 c if tag_c == " " and c.isspace() else tag_c
AttributeError: 'int' object has no attribute 'isspace'

but it seems the root cause of the exception is same.

I'll investigate it.


If you use Nginx to reverse proxy a quick fix would be to add this line to it's location block:

`proxy_hide_header X-Frame-Options;`


At this moment in time its:

root@222b35f401b9:/# lighttpd -v
lighttpd/1.4.53 (ssl) - a light and fast webserver

So you should be good to go

There are still a few things to look at around env vars before we can think about looking at this, but it is probably worth noting that `lighttpd` will be dropped in the future with Pi-hole 6.0 (no ETA) - so not 100% sure it's worth the work for this particular use case which has a perfectly adequate workaround in using `external.conf` for now


The world of updating software architecture is not comparable to the end user experience, where updating to the latest app, the newest operating system, buying the newest phone is all generally safe practice.

Creating a piece of software involves depending on all sorts of _things_ related to computers. Nothing is ever created from scratch. Even the earliest calculating machines relied on stable formal systems: the laws of math, physics.. Think about how when you do something as simple as arithmetic, you're trusting that the rules of combining some numbers to get a new result haven't changed, because that would break your calculations. So back to computer science, the design process is about where you place your trust among a large stack of tools, rules, and systems that you must rely on. One thing, in one time and place, must do exactly what you command it to.

With the countless things needed to develop software in the modern environment, you need to organize collections of them as they exist in specific times and places. These are called your **dependencies**. Dependencies can be languages, libraries, frameworks etc, all the way down to hardware.

In contrast to the essentially stable rules of arithmetic, active software is constantly being updated by developers to work better and do more. Security and user experience are also omnipresent concerns.

The web is all over the place in that regard. Things developed so quickly that certain tools have now been nearly unchanged for decades, while other efforts big and small can be downright ramshackle. When there's no precedent in a space, all something has to do to be widely adopted is work well enough for now. For major software like PHP, cleaning it up later involves rewriting lots of code and patching problems that compromise the security of its dependents. Largely for that reason, versioning is used to sort out what will work in one time and place, and what won't.

All this is just to spell out why deprecation happens. Stuff can't always be backwards compatible. Sometimes the effort to keep up is semantic, but sometimes involves so much refactoring that it plays a significant role in devs retiring fading projects.

Vaska has written about letting go of indexhibit. I do believe its only chance would be if it was picked up (more likely, completely recreated) by new dev(s). I hope this answer isn't pandering, I just wanted to explain it comprehensively because you were curious.


It's amazing how much people know about me. The projects fail because it takes time and money. Where were all of you when I was trying to find donations? How many have emailed me begging for free help - not offering to hire me or pay me for working on your personal site? It's totally unfair that I am responsible and underappreciated. Can you afford to work for over a decade for free? I simply can't. When I have time...I have time...this is the reality. I really do not appreciate that my personal email was posted in this thread...


@kees- I appreciate the comprehensive explanations. I was thinking it was something along those lines, but the forum incentivising php update got me confused.

@Indexhibit those are very fair and valid points, food for thought on internet and labor. For what it’s worth: thank you for all your work and time. I understand however that gratitude doesn’t pay the bills and will keep that in mind for the future.


We're thinking about plugin systems, we'll probably do it in v2.1. It may or may not be esbuild plugins.


Note that for 3.10 (and 3.11) support, you still need to set `LIBCST_PARSER_TYPE=native` env var for now. We'll be removing this restriction in a future release (soon (tm)).


Per URL an upcoming release will enable their new Rust-based parser for 3.10 & 3.11 grammar by default :tada:

(maybe this will also make it faster?)


I too have noticed this issue -- it's notable because I think it's only appearing when the Warp window is on an external Monitor, the fonts don't look blurry on the main laptop display, so I'm wondering if a Screen-flag isn't being updated properly per display.


I've created a pull request wich wich solve this for raltive imports, see:

 URL

I've added a compiler switch:

 appendModuleExtension


With D115419 applied and Linux at commit 112450df61b7 ("Merge branch 'i2c/for-mergewindow' of git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux"), we get closer to building a `powernv_defconfig` kernel with `LLVM=1`:

$ make -skj"$(nproc)" ARCH=powerpc LLVM=1 powernv_defconfig all
/usr/sbin/ld: unrecognised emulation mode: elf64lppc
Supported emulations: elf_x86_64 elf32_x86_64 elf_i386 elf_iamcu elf_l1om elf_k1om
clang-14: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [arch/powerpc/kernel/vdso64/Makefile:44: arch/powerpc/kernel/vdso64/vdso64.so.dbg] Error 1
...

This is URL If I quickly hack around that error:

diff
diff --git a/arch/powerpc/kernel/vdso64/Makefile b/arch/powerpc/kernel/vdso64/Makefile
index 3c5baaa6f1e7..45dc62ba1541 100644
--- a/arch/powerpc/kernel/vdso64/Makefile
+++ b/arch/powerpc/kernel/vdso64/Makefile
@@ -39,6 +39,8 @@ asflags-y := -D__VDSO64__ -s
 targets += vdso64.lds
 CPPFLAGS_vdso64.lds += -P -C -U$(ARCH)

+vdsold-$(CONFIG_LD_IS_LLD) := -fuse-ld=lld
+
 # link rule for the .so file, .lds has to be first
 $(obj)/vdso64.so.dbg: $(src)/vdso64.lds $(obj-vdso64) $(obj)/vgettimeofday.o FORCE
 $(call if_changed,vdso64ld_and_check)
@@ -53,4 +55,4 @@ include/generated/vdso64-offsets.h: $(obj)/vdso64.so.dbg FORCE

 # actual build commands
 quiet_cmd_vdso64ld_and_check = VDSO64L $@
- cmd_vdso64ld_and_check = $(CC) $(c_flags) -o $@ -Wl,-T$(filter %.lds,$^) $(filter %.o,$^); $(cmd_vdso_check)
+ cmd_vdso64ld_and_check = $(CC) $(c_flags) $(vdsold-y) -o $@ -Wl,-T$(filter %.lds,$^) $(filter %.o,$^); $(cmd_vdso_check)

I get another one:

ld.lld: warning: cannot find entry symbol _start; not setting start address
objcopy: Unable to recognise the format of the input file `vmlinux'
make[2]: *** [arch/powerpc/boot/Makefile:391: arch/powerpc/boot/zImage.pseries] Error 1
objcopy: Unable to recognise the format of the input file `vmlinux'
make[2]: *** [arch/powerpc/boot/Makefile:391: arch/powerpc/boot/zImage.epapr] Error 1
make[2]: Target 'arch/powerpc/boot/zImage' not remade because of errors.
make[1]: *** [arch/powerpc/Makefile:283: zImage] Error 2

Looks like `arch/powerpc/boot/wrapper` has hardcoded references to the GNU tools (e.g. `${CROSS}objcopy`), so we cannot omit `CROSS_COMPILE` for now. After adding `CROSS_COMPILE=powerpc64le-linux-gnu-` back to the command line, I get a kernel that boots in QEMU:

$ boot-qemu.sh -a ppc64le -k . -t 30s
QEMU location: /qemu/bin

QEMU version: QEMU emulator version 6.2.50 (v6.2.0-39-g0da6106883)
...
[ 0.000000][ T0] Linux version 5.16.0-09670-g112450df61b7-dirty (nathan@archlinux-ax161) (ClangBuiltLinux clang version 14.0.0 ( URL 1344e35c9822db4998d9eec7f219ecab700ecaa1), LLD 14.0.0) #1 SMP Fri Jan 14 17:53:20 UTC 2022
...

`ppc64le_defconfig` builds as well.

Very close!


Hmmm, `unref` has been around in node for awhile. Are you doing anything special? It seems like a lot of the errors with unref happen when you accidentally execute in a browser based context rather than node.


When I looked last time I explored this for hermetic builds a couple of years ago, it was not super apparent what the fix should be because it sounds like `arch/powerpc/boot/wrapper` is used in other projects so we cannot just convert those references over to `${OBJCOPY}` or the like (@mpe can correct me if I am wrong). It looks like @gwelymernans touched this area in 5.11, perhaps he could shed some light on how we might work around this.


Nothing special afaik, just show the shared process window via F1:

image

Keep in mind that the shared process is a browser window, so `setTimeout` does not return a function but a number!

image


The root cause of this issue is ambiguous specification of DiffDescription._get_diff() interface: `get_lines` is a function to obtain a list of strings, and `get_fp` is a function to obtain a IOstream. However when I rewrote for Python 3, I didn't determine explicitly which the IOstream and string are, bytes or str.

Perhaps they should be str, which might contain surrogate-escaped non-unicode sequences, for raw diff output (view=patch) needs it.


`black` also now supports 3.10+ syntax with patma / parenthesized with statements.


Black now works, so we're just waiting for enabled-by-default `native` parser in libCST :tada:


Is there any way to upvote this issue at Microsoft? Because the old module SharePointPnPPowerShellOnline still works for me. But it seems that it will be retired. And the new method doesn't work. That doesn't feel right for a production environment.


hm, maybe api-platform should avoid php8-only syntax until php8 is required?


yeah, but phpstan parses all referenced files anyway and then fails. And phpstan doesn't provide a way to skip files before parsing, only after parsing :(


This is enough to trigger the error:

php
<?php

declare(strict_types=1);

namespace App\Tests;

use ApiPlatform\Core\Bridge\Symfony\Bundle\Test\ApiTestCase;
use ApiPlatform\Core\Bridge\Symfony\Bundle\Test\Client;

class Test extends ApiTestCase
{
 protected function setUp(): void
 {
 parent::setUp();
 static::createClient();
 }
}


Do you have a link to the discussion from a couple of years ago?

AFAIK the wrapper is not used in any other projects, although that was the idea of it originally.

It is potentially called by other scripts from outside the kernel tree. I think in the old days maybe some distro scripts called it, but I think the modern distros don't. Possibly some 32-bit embedded stuff still uses it.

Also eg. see torvalds/linux@528229d210781b2da66c6d257a326c21099982b5, which talks about "the signing tool" calling the wrapper script. I'm not sure that signing tool was ever released, and it's basically dead now, but that's the kind of thing we have to keep in mind, external scripts that call the wrapper and expect it to behave a certain way.

So the main thing is to make any change backward compatible, if possible. ie. so that an existing caller will get the same behaviour it used to.

What is the LLVM alternative to `objcopy` ?


The repetition could be caused by URL And the fix will ship in `8.0.0`.

In the meanwhile, I'd recommend upgrading to `7.16.2` to make use of the caching mechanism so it will save many ES requests.

After looking at the APM data, I also identified 2 potential improvements so we can reduce the amount of time it takes to generate the telemetry report:
- URL
- URL

I also added them to our Meta issue for Telemetry performance improvements URL


Since URL says this is a phpstan issue I've opened a bug report with phpstan: URL


Hi, can you please create a small reproducing repository that shows this problem? Thanks.


Thank you, perfect. I'm gonna look into it in the next few days.


With AWS Lambda now supporting top level await ( URL I imagine a lot more will run into this parsing error. It looks like `eslint@8` ( URL has been released.


@willfarrell you can follow Standard 17 (which uses ESLint 8) progress here: URL


I know this one has been open for quite some time already and that there are a lot of organizations that are hitting this issue. I can say that we're closer than ever on getting this addressed. I'm not at liberty to give any timelines on it, but know that we are still actively working on it internally to get it resolved. Thank you for your patience everyone.


No need to. It has priority already.

You're okay with using the SharePointPnPPowerShellOnline library for now. If it works, it works. It will likely also still work for you with PnP.PowerShell as long as you use the same login method, i.e. -UseWeblogin. Nothing has changed with regards to that.


I'm having a similar issue. I'm trying to force docker to use a build profile that would force build_requirements to be in Release mode even if the recipe itself is built in Debug mode (for 1) performance reasons, and 2) working around an issue I have with m4 that throws debug asserts URL

The idea to pass a build profile like so

include(default)
[settings]
build_type=Release

I've been uselessly trying to patch conan-package-tools to correctly pass `CONAN_BASE_PROFILE_BUILD` to docker but I haven't managed to make it work. I have opened a draft PR with my failed attempts at URL in the hope that it'll spark a conversation. #596 will be either cleaned if possible, or just closed if not.


This is going to be fixed in PHPStan 1.4.2 which is going to be released soon.


Think I covered the last of your feedback this morning, so yes think ready for review again


I don't think this can run in Expo. Our SDK requires platform-specific features; Bluetooth and BLE to name a few.
I don't think platform specific-code can run in Expo.


It should work with an Expo development client.
You probably won't even need a config plugin looking at the install instructions
Most likely just infoPlist/permission settings
It would require some testing of course. Maybe @mnm458 or others have a device and wouldn't mind trying it out?
If there are issues, please share with the Expo community via Discord.
This could be a nice addition to expo.


This should have closed itself really, keeping it open until we verified that everything works.


@madebr is this `"reb"` on purpose? URL

The 1.4.18 version has `"rb"` (which is familar to me, unlike reb...): URL


The patch is adding `'b'` (it is already `"re"`).
It looks like it is a GNU extension:

 e (since glibc 2.7)
 Open the file with the O_CLOEXEC flag. See open(2) for more information. This flag is ignored for
 fdopen().

The problem you're seeing with debug 2019 is probably the same we saw when adding m4/1.4.19.
See URL for our analysis at that time.

We have a short reproducer.


I just got the same issue building bison/3.7.6 in debug FYI

image


The problem is with m4. The bison version is kinda irrelevant.
m4 is only used as a build requirement since it provides no library.
I think you can work around the problem by adding `-s:b m4:build_type=Release`.


I'm having this same issue after deploying in Heroku. In local is working perfectly, but in Heroku it fails. I've followed the
guidelines adding the buildpack and so, but same error.

This is how I initialize the browser:

` browser = await puppeteer.launch({
 headless: true,
 args: ['--no-sandbox', '--disable-setuid-sandbox'],
 });`

The error I get:
`Error: Failed to launch the browser process! `

Here the buildpacks added in Heroku
image


With the latest package code, there is a wordaround for XeTeX users:

latex
\makeatletter
\AddToHook{cmd/TblrAlignBoth/after}{\@rightskip=-1sp \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignLeft/after}{\@rightskip=-1sp plus 1fil \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignCenter/after}{\@rightskip=-1sp plus 1fil \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignRight/after}{\leftskip=-1sp plus 1fil}
\makeatother

And it doesn't break any existing test files.

latex
\documentclass[11pt]{article}
\usepackage{tabularray}
\begin{document}

\begin{tblr}{jj}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{ll}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{cc}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{rr}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\bigskip
\makeatletter
\AddToHook{cmd/TblrAlignBoth/after}{\@rightskip=-1sp \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignLeft/after}{\@rightskip=-1sp plus 1fil \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignCenter/after}{\@rightskip=-1sp plus 1fil \rightskip=\@rightskip}
\AddToHook{cmd/TblrAlignRight/after}{\leftskip=-1sp plus 1fil}
\makeatother

\begin{tblr}{jj}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{ll}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{cc}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\begin{tblr}{rr}
\hline
Src-Addr & Dest-Addr \\
Src-Addr & Dest-Addr1111 \\
\hline
\end{tblr}

\end{document}

image


I'd like to do that, but unfortunately all my attemps of forcing the build_requires to be in Release mode failed when using CPT and docker (locally it works plently fine if I issue the conan create command manually)

 URL


@holgerd77
- it is happened for me on Node v14.17.3
- Installed via another dependency
- Using `npm`

image

└─┬ @amfi/connect-wallet@1.1.21
 └─┬ @walletconnect/web3-provider@1.7.1
 └─┬ web3-provider-engine@16.0.1
 └─┬ eth-sig-util@1.4.2
 └── ethereumjs-abi@0.6.8 (git+ssh://git@github.com/ethereumjs/ethereumjs-abi.git#ee3994657fa7a427238e6ba92a84d0b529bbcde0)

I have just created new app on `heroku`, then made a setup via `github repository` to deploy, and then it showed me these logs

 Spoiler warning

-----> Building on the Heroku-20 stack
-----> Using buildpack: mars/create-react-app
-----> React.js (create-react-app) multi app detected
=====> Downloading Buildpack: URL
=====> Detected Framework: Multipack
=====> Downloading Buildpack: URL
=====> Detected Framework: Node.js

-----> Creating runtime environment

 NPM_CONFIG_LOGLEVEL=error
 NODE_VERBOSE=false
 NODE_ENV=production
 NODE_MODULES_CACHE=true

-----> Installing binaries
 engines.node (package.json): unspecified
 engines.npm (package.json): unspecified (use default)

 Resolving node version 14.x...
 Downloading and installing node 14.18.3...
 Using default npm version: 6.14.15

-----> Restoring cache
 - node_modules

-----> Installing dependencies
 Installing node modules
 npm ERR! Error while executing:
 npm ERR! /usr/bin/git ls-remote -h -t ssh://git@github.com/ethereumjs/ethereumjs-abi.git
 npm ERR!
 npm ERR! Host key verification failed.
 npm ERR! fatal: Could not read from remote repository.
 npm ERR!
 npm ERR! Please make sure you have the correct access rights
 npm ERR! and the repository exists.
 npm ERR!
 npm ERR! exited with error code: 128

 npm ERR! A complete log of this run can be found in:
 npm ERR! /tmp/npmcache.3QAnL/_logs/2022-01-19T07_02_45_160Z-debug.log
-----> Build failed

 We're sorry this build is failing! You can troubleshoot common issues here:
 URL

 Some possible problems:

 - Node version not specified in package.json
 URL

 Love,
 Heroku

 ! Push rejected, failed to compile React.js (create-react-app) multi app.
 ! Push failed

 No matter what it says, there is no problem with `buildpack`, it's just something that is here `git ls-remote -h -t ssh://git@github.com/ethereumjs/ethereumjs-abi.git`

 Anyway, you can try this command locally and it will show you this error.

But, if I run my project locally, everything is working (this could be the GitHub policy about SSH, dunno)

#### // SOLVED: using `yarn` instead of `npm` will give you the pleasure


@jmarrec have you already tried asking in m4 mail list, as it was discussed in #7369? it seems like there is no configure option to bypass the check, and proper fix may require to patch m4 sources.


@dr-shorthair , this is very insightful. Turning the question around, would you recommend QUDT for trade/commerce interoperability? Or should we rather stick with CEFACT Rec20? Interpreting your point, it might seem like QUDT is would be overly generalized and Rec20 purpose build for the trade industry?

Noting that CEFACT is now also expressed with IRIs, including Rec20, ex:
 URL


Yes, second this!

I just found out via a random tutorial... no way of knowing this feature even exists.
And when using it the second time after a while I forgot the "magical" key combination.. so I needed to spend some time again searching to find it.

I would be very nice to have an "advanced" button. Maybe a bit hidden or bind a "are you sure?" modal if you must.


I have started prototyping swift package manager support for Bolts and Parse-SDK-iOS-OSX in a similar way as @drdaz.

_[For new projects it may be the obvious choice to use URL but for existing projects migrating to a new client side SDK may pose more troubles then integrating subset of old Objective-C SDK via swift package manager.]_

To simplify things I removed all Carthage, Cocoapods, rake, and Xcode related scripts and files and only left the headers, sources, and added super simple Package.swift.

My version of Bolts is here: URL

You can `swift build` and `swift test` it, I temporarily removed all the app link and webkit stuff. If you compare it against the parse-community forked main branch of Bolts-ObjC, you will see that I basically only fixed all includes to be fully qualified.

My version of Parse-SDK-iOS-OSX is here: URL

You can `swift build` it for all platforms. Tests are not yet incorporated. Build is not clean and produces warnings, mainly because it always tries to compiles all files for all platforms, and many files are platform specific and should be excluded.

FacebookUtils, TwitterUtils, and ParseUI are ignored and not supported for now.

Looking at tree comparison, I again only left sources, headers, and added simple Package.swift file, fixing all public API includes to be fully qualified.

I will continue using these branches in my own projects and keep them up to date over time. If you are interested I can open a PR against master and try to continue working on getting this integrated, but first we probably need to agree on scope and goals for the effort. Parse-SDK-iOS-OSX is rather complex and contains lot of things that I believe should be split out as separate packages that depend on Parse.

FacebookUtils, TwitterUtils, and ParseUI are obvious choices.

My personal goal is to make `swift build` and `swift test` pass cleanly on all supported platforms, that is iOS, macOS, tvOS, watchOS, macCatalyst.

Just my .2 euro cents, opinions?


Both URL and URL when built locally allow me to build bison/3.7.6 (both in debug) without the popup


Not sure which solution we prefer. Perhaps combining them both actually...


I personally prefer URL as it doesn't require patching sources


I'm less certain that this HAVE_MSVC_INVALID_PARAMETER_HANDLER actually fixes it in all cases though. And you wrote on URL


Hey,

@ghollingworth

Er - I am actually considering making my own version, since there are about 6 standing ``[OS Request]`` issue with no answers (filter to requests).
Does it make sense to you guys there? I don't want to step on anyone toes, though it seems like all other users in the thread might welcome a "unofficialpi" fork.
I am also in the works of adding json generation in CustomPiOS (related URL ). And knowing what is the stand on that would help me decide if a fork is worth having.

(I was actually got here thinking we could join efforts and make a smoother CI/CD using github actions or something more accessible)


Hey,
If you want this perhaps you can tell me what you think about an unofficial fork, it seems like its what Rpi foundation suggests there:
 URL


Fixed with URL or 1.8.0 (via using VS Code's "Pre-Release Version" UI or URL ).

Unless you're explicitly adding -fms-extensions, in which case that bug fix is still pending ( URL ).


The reason I raise this issue is because it is inaccessible to those that
don't previously know of these settings. Making a fork does NOT improve
visibility.

While I'm sure using a terminal to set up WiFi is the "correct" way, for
most users clicking a box in an application on a computer that already
knows the password is easier, especially when they might not have a monitor
& keyboard to attach to the Pi.

On Wed, 19 Jan 2022 at 7:30 pm, Guy Sheffer ***@***.***>
wrote:


You have a point regarding visibility. Unless the fork becomes more common knowledge.
If there are more community OSes onboard that use such a fork, it might make it more widely known. Since it seems keeping the UI simple makes sense if you want to be educational. Rpi Foundation people wrote in the issue there:
#180 (comment) they don't want to do is.
It means there might be enough reason to make a community fork with more advanced options in general.

For example, you could add custom fields as a feature in the advanced tab (domain names, static IPs, you name it, more images to pick from).


There is code in git that will display an extra button (cog icon) if the user selected an image that advertises support for advanced settings.

To advertise support add to the images in your json the option:

"init_format": "systemd"

(or "init_format": "cloudinit" if your image is based on Ubuntu Server)


@maxnet Cool, I understood that is in the works (from our talk here URL .


Just no distributions in the repository that advertise support right now.
But since you are maintaining your own .json file, you do can add the option to make it work for your distro...


I don't have an Ubuntu-based distro on the official JSON atm.
Also my Ubuntu-based distros can also handle wifi settings from the raspbian distro format thanks to CustomPiOS network module. So if you pick them as a custom images advanced settings for wifi do work.


If you have RPI OS based distros the setting would be "init_format": "systemd"

(instead of cloudinit)


@ggriffiths How to set the backoff to the snapshot-controller?


In general, those requests have sat idle while I think about how best to put them in. In the end, the more images that do the same thing (home automation or 3D printer for example), I'm just going to add in a secondary list. For example:

Other Specific Purpose OSs
 -> OctoPi
 -> Other 3D printer OSs
 --> ABC
 --> Simply etc


Now I've solved it！install libXScrnSaver in the server and can run it!

sudo yum -y install libXScrnSaver-1.2.2-6.1.el7.x86_64


Hello. As I understand your OS is Windows.
Could you describe steps to create such files, to reproduce the situation?

There is a FR #97 to support special symbols in the filenames, and it is partly implemented (only verification part) by 757942e2d68c4527d37b8a6310d2dbf781d9225b.
But, unitl now, I thought that the problem was only Linux/Unix-related.
To support Windows, we need a corresponding test-case.


No, actually. Oh, was it my reference to "AppData"? Sorry for the confusion, I use "AppData" as a shorthand for "any files created by applications after installation, and not explicitly named/saved by the user, regardless of OS" - savegames, browser profiles, logs, etc. The files in question were indeed created on Linux, by Google Earth, going by the paths. Don't take that as repro step, these are >10 year old backups and I no longer use Linux on the desktop to know/check if this behaviour still exists.

As for windows, though - IIRC NTFS drivers on Linux (ntfs-3g?) do not enforce Windows-style filename restrictions, which actually originate in the API (Win32?), not in the filesystem spec. So I think it would be possible to encounter such a file on windows after creating it in Linux. This is just a guess, though.


We may be moving straight to SPM support and skip fixing the carthage build altogether, see discussion in URL In the meantime, I found a rather complex way to build with carthage on Xcode 13.2.1:

1. Use carthage build script `carthage.sh` for Xcode >12 compatibility
2. Build all xcframeworks; do not use `--no-use-binaries` as `facebook-ios-sdk` is required as dependency of Parse SDK but cannot be built from source in Xcode 13; run: `./carthage.sh update --use-xcframeworks --platform iOS`
3. Add built xcframeworks to Xcode project, except `Parse.xcframework`
4. Open `Carthage/Checkouts/facebook-ios-sdk/samples/SmoketestSPM/SmoketestSPM.xcodeproj` and wait for SMP to download the dependency; see here.
5. Build Parse SDK frameworks because `ParseFacebookUtilsV4.xcframework` requires `Parse.framework` (not as xcframework), so it needs to be built and added via `carthage copy-frameworks` in the Xcode project's build phases; run: `./carthage.sh update Parse-SDK-iOS-OSX --platform iOS`


I'm keeping this issue open as a thread to look for help when building with carthage, but with a note that we intend to focus on Swift Package Manager support ( URL instead of fixing carthage build process.


Due to the accumulating difficulties regarding carthage and xcframework building on Xcode >=12 I've added a bounty to SPM support in the hopes to incentivize and revive this effort. I've also marked the issue Carthage Xcode >=12 compatibility as bug that won't be fixed, so we can fully focus on SPM support.


I have been able to re-introduce Parse SDK test files into URL and make them compile for macOS, and iOS. tvOS, and watchOS need to be done.

Quick run of `swift test` makes majority of the tests pass, with couple failing for various "assumption" reasons that were valid in the Xcode days (always present Info.plist, always having hosting UIApplication, etc).

Will continue working on them


Updating this issue to cover adding a mention for how to glob image files in both esbuild and Webpack frontend bundler configs.


- Dont want to parse the entire disk if we can avoid it
- A large number of bazel workspaces will be siblings to the bazel repo you are working on right now. Should be able to easily see those caches without checking the entire disk
- Want to remove some combination of largest / "longest since last used" bazel caches first
- Prompt user before removing anything
- Will need to support windows as well but can be done as a separate pass later. Make sure to make a ticket for tracking purposes


I've introduced `macosx-x86_64` builds in commit URL
Please give it a try with the snapshots: URL


I've introduced `macosx-arm64` builds for FFmpeg in commit URL
Please give it a try with the snapshots: URL


@xing-yang @ggriffiths Maybe ecause of the URL to update the snapshotcontent.

After the snapshot was created failed, it will to remove the "snapshot.storage.kubernetes.io/volumesnapshot-being-created" and update the snapshotcontent.


image
If we don't remove the annotion "snapshot.storage.kubernetes.io/volumesnapshot-being-created" and not update the snapshotcontent, the retry interal is 1s. 2s, 4s, 8s,16s,32s,64s,128s,256s, 5min.


I think it depends on URL Till we cannot do it automatically with smoke testing it will be tedious to review so many PRs.


@EliteTechnicalCare can you either “correct” or “delete” your comments about the Swift SDK? Neither were true when you posted them. This particular issue is currently pinned and will get more attention. I don’t want people coming across your comments perceiving them as facts when they are not. This is synonymous to when people tweet or post saying, “parse server is dead,” and others believe it.

What is true is what @mman posted:


@cbaker6 Have you come across any plans / demands for adding SPM support to the Parse Swift SDK? I think once we support SPM, we could also end support for all other dependency managers such as cocoapods and carthage? The 2 repos (ObjC, Swift) don't have to be aligned, but it would be interesting to know.


The Swift SDK has always supported SPM along with Cocoapods and Carthage. More info in the readme: URL SPM has always been labeled as the preferred way for the Swift SDK.


Amazing, I haven't noticed that. Maybe @drdaz could get in touch in case there are any obstacles in URL


I think that's not valid for me in Heroku. Thanks anyway for your answer. I'll keep searching


Thanks @davicente lets see what we can do.

First can you post the rest of the error too please?


I see. So it is not really a normal requeue due to the failure but it is a new update that triggers the requeue. If we don't remove the annotation "snapshot.storage.kubernetes.io/volumesnapshot-being-created" and don't update the snapshotcontent, how does the snapshotter know the creation has failed? If the annotation is not removed, the snapshotter will think the storage system is still working on the snapshot creation. CreateSnapshot will be called to query the snapshot status. One thing to explore is to see if we can use ListSnapshots instead of CreateSnapshot (if ListSnapshots is supported by CSI driver) to check snapshot status.


Another idea to explore is to compare the old obj vs the new obj when update is triggered. If the annotation "snapshot.storage.kubernetes.io/volumesnapshot-being-created" is the only thing being removed, maybe we don't need to go through CreateSnapshot again.


They are just there for people who don't want to use SPM and are more comfortable the others. For the Swift SDK, it's not hard to keep support for Cocoapods and Carthage. SPM is definitely the easiest to use.


This is kind of a big deal. It means I won't have to dig into the challenges I was describing here. Running the tests using swift test make an awful lot more sense than what I was talking about 👍🏼

These things used to be separate GitHub projects not too many years ago, and I think they got reincluded in the main package because the other thing was a PITA - multiple CI's, dependencies to be maintained etc. Also, nobody is going to be interested in those packages that aren't using the main Parse SDK. Can you explain what benefits you see in splitting them out?


Hi @jontewks,
first of all, thanks for your fast reply.

This is the stack:

Error: Failed to launch the browser process!
ERROR:platform_thread_posix.cc(148)] pthread_create: Resource temporarily unavailable (11)
FATAL:browser_task_executor.cc(405)] Failed to start BrowserThread:IO
host app worker.1 - #0 0x56251b45c029 base::debug::CollectStackTrace()
host app worker.1 - #1 0x56251b3c3623 base::debug::StackTrace::StackTrace()
host app worker.1 - #2 0x56251b3d68f0 logging::LogMessage::~LogMessage()
host app worker.1 - #3 0x56251938bba6 content::BrowserTaskExecutor::CreateIOThread()
host app worker.1 - #4 0x56251af5e408 content::ContentMainRunnerImpl::RunBrowser()
host app worker.1 - #5 0x56251af5e117 content::ContentMainRunnerImpl::Run()
host app worker.1 - #6 0x56251af5b985 content::RunContentProcess()
host app worker.1 - #7 0x56251af5c45e content::ContentMain()
host app worker.1 - #8 0x56251afba7ce headless::HeadlessBrowserMain()
host app worker.1 - #9 0x56251afba4fd headless::HeadlessShellMain()
host app worker.1 - #10 0x562517d01133 ChromeMain
host app worker.1 - #11 0x7fb491ed50b3 __libc_start_main
host app worker.1 - #12 0x562517d00f6a _start
host app worker.1 -
host app worker.1 - Received signal 6
host app worker.1 - #0 0x56251b45c029 base::debug::CollectStackTrace()
host app worker.1 - #1 0x56251b3c3623 base::debug::StackTrace::StackTrace()
host app worker.1 - #2 0x56251b45bb01 base::debug::(anonymous namespace)::StackDumpSignalHandler()
host app worker.1 - #3 0x7fb492da63c0 (/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+0x153bf)
host app worker.1 - #4 0x7fb491ef418b gsignal
host app worker.1 - #5 0x7fb491ed3859 abort
host app worker.1 - #6 0x56251b45ad95 base::debug::BreakDebuggerAsyncSafe()
host app worker.1 - #7 0x56251b3d6d1f logging::LogMessage::~LogMessage()
host app worker.1 - #8 0x56251938bba6 content::BrowserTaskExecutor::CreateIOThread()
host app worker.1 - #9 0x56251af5e408 content::ContentMainRunnerImpl::RunBrowser()
host app worker.1 - #10 0x56251af5e117 content::ContentMainRunnerImpl::Run()
host app worker.1 - #11 0x56251af5b985 content::RunContentProcess()
host app worker.1 - #12 0x56251af5c45e content::ContentMain()
host app worker.1 - #13 0x56251afba7ce headless::HeadlessBrowserMain()
host app worker.1 - #14 0x56251afba4fd headless::HeadlessShellMain()
host app worker.1 - #15 0x562517d01133 ChromeMain
host app worker.1 - #16 0x7fb491ed50b3 __libc_start_main
host app worker.1 - #17 0x562517d00f6a _start
[...]

Let me know if you have any idea about the problem.
Regards


I have tried to find it but I do not recall ever bringing this up to upstream, so I could be misremembering something... _shrugs_

Ack. I have hacked something up that works for `powernv_defconfig` when building `zImage.epapr`:

 URL

$ make -skj"$(nproc)" ARCH=powerpc LLVM=1 distclean powernv_defconfig zImage.epapr
ld.lld: warning: cannot find entry symbol _start; not setting start address

$ boot-qemu.sh -a ppc64le -k . -t 30s
QEMU location: /usr/bin

QEMU version: QEMU emulator version 6.2.0
...
[ 0.000000][ T0] Linux version 5.16.0-11415-gc1a97611aaa2 (nathan@dev-arch.archlinux-ax161) (ClangBuiltLinux clang version 14.0.0 ( URL d4ffb6ec65d7173ee63fa0e70eedd049944ceeff), LLD 14.0.0) #1 SMP Fri Jan 21 12:16:52 MST 2022
...

However, the build fails when building `zImage.pseries` (included in the `all` target, obviously related to the new use of `ld.lld`):

$ make -skj"$(nproc)" ARCH=powerpc LLVM=1 distclean powernv_defconfig all
...
ld.lld: error: relocation R_PPC64_ADDR64 cannot be used against symbol '_start'; recompile with -fPIC

ld.lld: error: relocation R_PPC64_ADDR64 cannot be used against symbol '_etext'; recompile with -fPIC

ld.lld: error: relocation R_PPC64_ADDR64 cannot be used against symbol '__bss_start'; recompile with -fPIC

ld.lld: error: relocation R_PPC64_ADDR64 cannot be used against symbol '_end'; recompile with -fPIC

make[2]: *** [arch/powerpc/boot/Makefile:400: arch/powerpc/boot/zImage.pseries] Error 1
...

If I apply the same fix as commit 4c078c86b4a4 ("powerpc/boot/wrapper: Add "-z notext" flag to disable diagnostic") to the `pseries` case in `arch/powerpc/boot/wrapper`, `zImage.pseries` builds successfully and I can boot it in QEMU, just like `zImage.epapr`.

There was one other issue I noticed with `ppc44x_defconfig` (the 32-bit config that we test and boot) related to `relro`. I solved this by adding `-z norelro`.

`llvm-objcopy` :)


### Describe the solution you'd like?

shell
To configure the text line height.
Discord - feature-requests - 2021.11.03:
"FR: Reduce the line-height (or add an option). I don't mind the UI taking up more space than a normal terminal, but you lose too much space to each line. I would accept whatever line-height: normal is for the current font. Based on the Fira Code repo, it's still substantially tighter than in Warp."

### Is your feature request related to a problem? Please describe.

shell
N/A

### Additional context

 URL


From @pf1gura via #352

I like to set my line height to something bigger than the standard. I find too much text in one view to be distracting. In iTerm, my preferable value is 200. I suppose I am not alone in this and it would be nice to have that option.

CleanShot 2021-11-05 at 21 13 52


From @argai via #352

I've just downloaded warp and have the same issue, line height needs to be configurable.

image
On the left there is warp, on the right iterm. While this might be ok on a desktop and big screen, on a 13" laptop its way too much space wasted.


From @lnking81 via #352

Not only the line height but also all font rendering options: name, size, the interval between letters, ligatures, anti-aliasing, etc.


Just in case anyone comes here with same problem for Heroku, I created an issue in the libpack library for Heroku. Hopefully it will be discuss there:
 URL


CuPy relies on `cuSolver` for implementing these linear algebra routines. However, there are no routines in cuSolver for non-symmetric matrices, so this requires implementing Cuda kernels or custom routines to solve this.


I think we might be able to steal MAGMA's kernels for this purpose 😄


yeah, I njust checked and actually torch uses MAGMA for this!


If we can only compare the annotations of the snapshotcontent, if they are different, we don't re-queue.


I think we need to check if the annotation "snapshot.storage.kubernetes.io/volumesnapshot-being-created" is the only thing being removed and if that's the only change. If there are other changes, we still need to process it.


The problem is here: URL

OpenApi calls `.values()` to get the values of the enum. This calls (for Java) the following in core URL

The problem is that inside that code (even if we copy it to the openapi module) we don't have access to any bean metadata that Micronaut produces. All the `Element`s in the stream are javax elements and not Micronaut. I don't see a way to check if those element have the appropriate annotation to generate the right value instead of the `toString()` that it's done at this moment.

@graemerocher any thoughts if there is a way to do this?


I think we can close this epic, upgrade and CI will be done in there own cards.


I'm sorry to disappoint but MAGMA's eigenvalue solver for non-symmetric matrices is really bad. There's no specialized GPU-only path, it uses a mix of LAPACK calls with a tiny bit of CUDA kernels. Eigenvalues are computed using LAPACK.
See lots of `lapack77` calls in URL

Up to about 3k x 3k matrices, it's faster to compute on CPU.


Both of these depend on 3rd party SDKs that may get broken at various stages of life blocking the updates and release of core Parse iOS SDK. It also makes the resulting binary bigger, it also then links your project to SDKs that you do not use and perhaps do not want to have linked at all (for example if I am not mistaken, just linking a facebook SDK to your app did in the past trigger various red flags during review, like linking against location, ads frameworks, etc., and IIRC facebook SDK used to track app usage and correlate with other apps usage just by being included in the app). /me do not like that.

Just my .2 cents, I like things to be lean and focused (my UNIX roots :)


Everyone - I'm working at Microsoft Support, and with @KoenZomers and Engineering on this issue.
Microsoft Engineering has analyzed this issue and is currently working on a fix. It requires collaboration between multiple teams and there is no ETA for the moment. I will update this thread as updates occur


Seems editing `nextcloud/custom_apps/news/lib/Db/ItemMapperV2.php` does not work anymore, still getting wrong order when viewing a folder:

obrazek


@davicente I was going to say I haven't seen that error before but I see you closed it. Mind mentioning what your fix was here just in case anyone else comes across this in the future?


@davicente I haven't seen this error before. Have you tried clearing the heroku build cache by chance?
 URL

If that doesn't work, try starting a new heroku app with the same repo, just to be sure we can rule heroku out of the equation.


SPM allows to select only the needed subpackages. Would that allow to add only the main Parse SDK without Facebook Utils and without the FB SDK as 3rd party dependency?


Thanks @IvanYashchuk!!

I was looking into MAGMA code and saw the very same as you, I am just thinking of naively throwing this into a QR solver despite being slow just to avoid CPU sync.


As @mman says, yes it should. I believe the only install route that suffers from everything always being installed is Carthage.

It's a legitimate concern, but since we specify which version of the FBSDK we use, the breakage generally won't catch us unawares. Moving between FB dep versions is an explicit, conscious action, and the developer should be able to see if the update breaks anything.

The only place I see this causing issues is when an Apple SDK update breaks whatever version of the FB SDK we're using. And if that happens, it's likely to be because we're hanging on an old version; FB seems to keep up to speed with Apple's newest stuff pretty well. Even then, the move to a newer Apple SDK is a conscious move.


Is there something special about exploration builds? I just added a try catch


@lramos15 yeah maybe how uncaught exceptions are handled and reported. This one you cannot really catch as it happens from an event handler:

image


Yeah like I said not sure what we should do here as one module expects node and another module expects window and the shared process is a bit in between


Hey, so I started looking in to making a fork, for now It already uses its own json list and merges ones in another repo:

 URL

And it takes it from:
 URL
Which already has a github action to merge the official .json and add on top of it.

If I get Ci/CD for this running we could have a less restricted and more advanced version of rpi-imager. Perhaps even make it support other SBCs.
It could also be a space to see what works and then merge it up to mainstream.


Nice work guysoft! @Raspberry Pi why did you delete his message? If there's a good reason then you should probably say before people make assumptions. If there isn't then I would strongly consider reinstating it ASAP before people realise!


I tested using SharePointPnPPowerShellOnline legacy module and it works at my end, although it is older module than PnP.PowerShell.


@SavoInfostream Are you using the version of `MySqlConnector` that is referenced by Pomelo `6.0.1` (which is `2.1.2`), or are you using a newer version?

What OS is your app running on (or is it executed serverless)?


See URL for some background. Are you using something like ProxySQL?


@lauxjpn I tries with 2.0.0, 2.1.4 (latest currently) and 2.1.2. Same things happens.
Client app is running on Windows 10. It is a local dev environment.


@SavoInfostream Okay, so the app is running on your local Windows 10 machine, and is directly connected to a Google Cloud hosted MySQL instance, correct?

I would suggest to log the SQL statements generated by the failing `SaveChanges()` call. Then replay those statements (in a transaction) in one go from your local dev machine to the Google Cloud hosted MySQL instance using the `mysql.exe` command line tool to see, whether this issue is potentially a Pomelo/MySqlConnector issue or an issue with the setup of the MySQL instance.

Also, check the MySQL error log for additional information.


Verified ticket on test-de2.sormas.netzlink.com and test.sormas.netzlink.com.

I have discussed with @BarnaBartha and the ticket will be reopened due to the following:

1. Person search option needs to be added to the 'Create new travel entry' form;

2. Person search option should not be displayed in forms where the person related information is already filled in by the system:
- 'Create new contact' form (that is accessed from the 'Cases' directory - 'Epidemiological data' tab - 'Contacts with source case' card);
- 'New immunization' form (that is accessed from the 'Persons' directory - 'Person' page - 'Immunizations' card);
- 'Create new contact' form (that is accessed from the 'Events' directory - 'Event Participant' tab - 'Contacts' card).


Also see MySql Long Running Query Fails on Docker .NET Core for a possible solution.


Thanks for reporting this and helping to make Electron better!

Because of time constraints, triaging code with third-party dependencies is usually not feasible for a small team like Electron's.

Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

I'm adding the `blocked/need-repro` label for this reason. After you make a test case, please link to it in a followup comment.

Thanks in advance! Your help is appreciated.


@BarnaBartha @adinaflorea9 These are some UI issues that I have found when testing:

|current|desired|
|:-|:-
|<img width="378" alt="personSearchUI" src=" URL width="383" alt="personSearchUiFix" src=" URL
|<img width="620" alt="personSearchUI2" src=" URL width="622" alt="personSearchUiFix2" src=" URL


Well, I have found a bug in MySQL.
One of my commands was a DELETE command which was causing the error. Google Cloud MySql log was showing:
"The manual page at URL contains information that should help you find out what is causing the crash."

Anyways, this DELETE statement would try to delete a row from a table, and do a CASCADE delete from another table (foreign key). Besides cascade delete, another interesting thing is that the child table has a multi-valued index on one of its json columns. These two things combined, with or without transaction, crash the MySql.

If I delete the child row manually, it works. If I drop the index and delete the parent row, it deletes the parent and the child row.

Thanks for the help, everyone.
I will try and report this to MySql people.


@SavoInfostream Nice detective work! Thanks for letting us know and for reporting it to the MySQL team.


While testing the ticket a new issue has been observed. After a discussion with @BarnaBartha it has been decided that a comment should be added to detail the behavior observed.

Logging the comment in the same format as a bug:

Bug description:
Using the 'Person search option' allows the user to set 1 person as multiple event participants for the same event.

Steps to reproduce:
1. Open or create an event;
2. Click ‘Add Participant’ and create a new event participant (e.g. Person1);
3. Afterwards, add a second event participant to the same event;
4. When creating the new event participant, instead of entering person details manually, use the search for person feature;
5. Search for Person1 (the first event participant added at step 2) and select them from the list below;
6. Save the new event participant;
7. Person1 is now listed twice as event participant in the same event.

Actual Behavior:
The same person is listed as 2 event participants in the same event.

Expected Behavior:
The same person can not be listed as 2 event participants in the same event.

Additional information:
If a user tries to add Person1 as event participant manually (by entering the name and sex in the ‘create new event participant’ form) then they trigger the duplicate detection; if they pick the existing person from the list and try to save, they get an error that informs them that this person is already an event participant.

Screenshot of the error message that appears:
enter 1 person 2 times as event participant manually - you get an error saying that they can not be event participant twice


@kwa20 I'd suggest to not fix the first very minor UI issue (the left-aligned button) because finding a way to fix it would take some time and is in no way worth the effort we'd need to put into it, in my opinion.


While testing the ticket on test-de1.sormas.netzlink.com and test.sormas.netzlink.com., a new issue has been observed. After a discussion with @BarnaBartha it has been decided that a comment should be added to detail the behavior observed.

Logging the comment in the same format as a bug:

Bug Description:

An error message stating ‘An error has occurred. An unexpected error occurred. Please contact your supervisor or administrator and inform them about it’ appears in the ‘Immunizations’ directory and ‘Lab messages directory’.

Steps to reproduce:
1. Create a person by creating a new immunization from the ‘Immunizations’ directory;
2. Create a second person by creating a new case from the ‘Cases’ directory (when creating this person through the new case, in the person related fields, input the same data as for the person created at step 1);
3. Duplicate detection is triggered; select ‘Create new person’ form the pop-up;
4. Go to the ‘Immunizations’ tab and open the ‘Create new immunization’ form;
5. Select a different disease than the previously selected ones (i.e. the diseases used when creating the persons from step 1 and step 2);
6. For the person related fields use the ‘Person search option’ and search using the name of the persons from steps 1 and 2;
7. Click to select either of the persons;

Actual behavior:
User is not able to pick either of the persons from the list and an error message appears, stating ‘An error has occurred. An unexpected error occurred. Please contact your supervisor or administrator and inform them about it’.

Expected behavior:
User is able to successfully pick either of the persons from the list.

Screenshots:
Screenshot of the error message:
Second time the error reproduced - you also have two persons

Additional information:
The same error message can be observed in the ‘Samples’ directory when attempting to process a lab message.
Steps to reproduce:
1. Pick an unprocessed lab message;
2. From the first pop-up pick select matching person and pick a person from the list;
3. From the second pop-up pick create new case and click confirm – error message appears;
(if here the user picks create new contact no error message appears)
(if here the user picks create new event participant no error message appears)
 Or,
1. Pick an unprocessed lab message;
2. From the first pop-up pick ‘select a different person’ and pick a person from the list;
3. From the second pop-up pick create new case and click confirm – error message appears;
Or,
1. Pick an unprocessed lab message;
2. From the first pop-up pick ‘create new person’;
3. From the second pop-up pick create new case and click confirm - error message appears;
(if here the user picks create new contact no error message appears)
(if here the user picks create new event participant no error message appears)


Today, I've pushed a first test and all is green!
 URL
Now I have to add more scenarios and improve workflows.


Prerelease `17.0.0-0` of `standard` is now released: URL

We will be checking the stability of this ourselves, but would love for as many of our users to test it out as well and report back to us whether it's time to party or time to head back into the workshop and reshape things. Thanks 🙏


Prerelease `17.0.0-0` of `standard` is now released, containing ESLint 8 support, which should fix this issue. See: URL

Would love if you could all test this and report back here if this is still an issue 🙏 We'll reopen this if its still an issue.


@voxpelli Something wrong is not right

js
// main.js
await new Promise(resolve => resolve())

sh
Sandbox $ standard --version
17.0.0-0
Sandbox $ standard .\main.js
standard: Use JavaScript Standard Style ( URL
 .\Sandbox\main.js:1:1: Parsing error: Cannot use keyword 'await' outside an async function (null)

Furthermore, VSCode (`standard.vscode-standard v2.0.1`) don't show Standard errors anymore.


@NemoStein Right, thanks, I'll reopen. Have you tested in plain ESLint 8 and seen if it works there? Maybe we need to explicitly allow it?

In regards to the VSCode extension, that one needs an update, I highlighted that in URL now 🙏


just had a quick look and standard 17 doesn't support class instance fields, either (which eslint 8 does)

js
class Test {
 something = 1
}

export default Test

$ standard instance-field.js
standard: Use JavaScript Standard Style ( URL
 /Users/lloyd/Documents/instance-field:2:13: Parsing error: Unexpected token = (null)


@voxpelli Ok, here goes my 2 cents.
Using only ESLint, if you don't set the `parserOptions.ecmaVersion` to `"latest"` it also triggers the error

js
// .eslintrc.js

module.exports = {
 env: {
 es2021: true,
 },
 parserOptions: {
 ecmaVersion: 'latest', // resolve())

With `parserOptions.ecmaVersion: "latest"`

sh
$ eslint .\main.js
$

Without

sh
$ eslint .\main.js

.\main.js
 1:1 error Parsing error: Cannot use keyword 'await' outside an async function

✖ 1 problem (1 error, 0 warnings)

$


@NemoStein Yeah, I arrived at the same conclusion, will merge and release URL when another maintainer gives me a review 👍


I'm cleaning the assignees so it can be back to the pool of available `short projects`.


@NemoStein @75lb We just released `17.0.0-1` with a fix for this. Unless URL overrides that fix, then it should work now, else we'll try to get a fix in for that issue and releases a `17.0.0-2` tomorrow. Both me and @Divlo needs some sleep now 😅


Still patiently waiting on Microsoft to fix this (not the community).


Sadly it does, but I can confirm that updating the `eslint-config-standard-jsx/eslintrc.json` to `"ecmaVersion": 2022` works.


First steps are done, one test was triggered last night and all was green!
 URL
Let's create other small cards to avoid this one to become too big.
Fixed by URL


All of the INAI's publications publish a good publication policy, more examples: URL
 URL
etc

And this is another example from Honduras URL


Hey, just to update that I spoke to Gordon and all is good. No need to make any assumptions :)
I might start working on a "packed with distros rpi-imager" once I get OctoPi and FullPageOS RCs out.


@lizozom I was going to ask the same since we covered most of it. I'll go ahead and close it. Feel free to reopen if needed.


A similar error message that was reproducing for 'Immunizations' and 'Samples - Lab messages' directories was logged in the comments from above.

@MateStrysewske has asked in a comment from ticket #7840 that I log the following as a comment here:

Bug description:
An error message stating ‘An error has occurred. An unexpected error occurred. Please contact your supervisor or administrator and inform them about it’ appears when the user goes through the following flows:

- create a case for a contact person;

- if a sample with a positive pathogen test result is added to a contact, a pop-up to create a resulting case is triggered; if the user selects 'Yes', the error message appears;

- create a case for an event participant;

- if a sample with a positive pathogen test result is added to an event participant, a pop-up to create a resulting case is triggered; if the user selects 'Yes', the error message appears;

- create a case for a travel entry;

- send a case to the reporting tool.

Actual Behavior
An error message stating ‘An error has occurred. An unexpected error occurred. Please contact your supervisor or administrator and inform them about it’

Expected Behavior
No error message appears when the user goes through the flows described above.

Screenshots:
Create case from an event participant error message

System Details
Device: Windows 10
SORMAS version: 1.68.0-SNAPSHOT
Android version/Browser: Chrome
Server URL: test-de1.sormas.netzlink.com
User Role: Admin, NatUser


@mman I've been bashing my head against against something for a minute now... I've got my branch rebased with mainline, but it seems like no matter what I do, I can't get the tests to see the main source files. You're doing it with cSettings I gather, but when I do similar, they seem to be ignored.

Do you know of any reason why this might be? The only differences I can see are that I use the path and publicHeadersPath attributes.


@drdaz Do you have any error messages?

The line: URL here shows that tests must depend on Parse, Bolts, and OCMock, and we only use .headersSearchPath to actually lookup internal header files that are not public


What about this build (built on recently released @electron v18.0.0-alpha.1 from wip-electron-18 branch)? Still causing issue?


Thanks for the test. So it's confirmed that newest @electron v18 alpha is unfortunately also affected.


Tested the ticket on test-de1.sormas.netzlink.com and after a discussion with @BarnaBartha it has been decided that a comment should be added to detail the behavior observed.

1. Person search option should not be displayed in forms where the person related information is already filled in by the system:
- [ ] 'Create new travel entry' form (that is accessed from the 'Persons' directory - 'Person' page - 'Travel Entries' card);
- [ ] 'Create new travel entry' form (that is accessed from the 'Cases' directory - 'Epidemiological data' tab - 'Travel Entries' card);

2. Person search option needs to be added to:
- [ ] the 'Add new event participant' form that is accessed from the 'Samples' directory - via 'Lab messages' - unprocessed lab message - 'Create new event participant';

- [ ] Error message stating ‘An error has occurred. An unexpected error occurred. Please contact your supervisor or administrator and inform them about it’ appears when the user goes through the following flow:
 - create or open an existing event;
 - open the 'Add new event participant' form;
 - input data in the mandatory fields;
 - click 'Save';
 - observe the error message.

Screenshot of the error message:
Created new event - tried to add a brand new event participant - error message appears on my local host


`17.0.0-2` should finally be fixing this + we now have tests that ensures that ensures that's the case


This should be implemented. I'd expect `decimal * uint128` to do a simple multiplication. Equivalent to `decimal(decimal.0 * uint128)` or `decimal * decimal::from_ratio(uint128, 1)` but more gas efficient than constructing a `int/1` fraction then multiplying two fractions together.


i.e. I have `$0.05` dollars (internally, stored as `5` cents, the lowest possible fraction, with a `DECIMALS` value of 2). I double my money (`2 * 5`) => `$0.10`


reactie Manuel Betermans (RWS)
Ik ben het met jullie eens dat de lijst in de tabel van het Bkl en die uit het IMEV overeen zouden moeten komen; mij is niet bekend waarom hier een verschil in zou moeten zitten. Een tijd geleden hebben Hans de Waal en Wim Makaske (nu niet meer bij ministerie en bij ons werkzaam) een inventarisatie gemaakt van kenmerken die in de IMEV’s moesten. Op pagina 5 hebben ze dit voor tabel B3 gedaan, maar daar mis ik bijvoorbeeld in hun opsomming ook een Automatische hi-ex outside-air installatie; mij is niet duidelijk waarom dat zo is. Ik zou dus toch tabel B3 en de aanvullingen die Paul heeft gedaan als uitgangspunt nemen.
Wat uit dit document wel naar voren komt, is dat bijvoorbeeld een veld als ‘Oppervlakte opslagplaats in m2’ ook in het IMEV terug zou moeten komen. De uiteindelijk afstand uit tabel B3 hangt namelijk ook mede daarvan af; daarom is ook het beschermingsniveau als extra kenmerk voorgesteld (zie issue Opname Beschermingsniveau #18).

zie ook doc:


This might be caused by the GDAL error handler defined by the `sf` package. The GDAL error handler (set with
`CPLSetErrorHandler`) might be called from threads created by gdalcubes but the error handler calls `Rf_warning()` (see URL which is not thread-safe. However, a single-thread test, where all computations run in the main thread should clarify further.


These two are the trickiest (and the other projects using them). I'm not yet sure how and if we'll handle them because the NPM packages referenced in them need to be restored too. Loading something from NuGet that has a package.json which in


I think we should keep esbuild as an internal implementation. Enabling esbuild specific plugins would make it harder to switch to an alterntaive build step.


Verified ticket on the local machine and test-de2.sormas.netzlink.com using the latest version of Sormas 1.68.0-SNAPSHOT.

3 follow up issues that were initially logged on the 3rd of February in a comment on this ticket, have been moved into a separate ticket #7903.


The simulator uses QMC (Quine and McCluskey) to simplify logic equations, and the problem with QMC is that while it always provides an exact minimum solution, the memory consumption and computing time increases exponentially with the number of input variables. Therefore QMC is not suitable for functions with many inputs. To avoid that it takes too long until the result is available, the calculation is not performed if there are more than 12 inputs.
With such a large number of inputs you would have to use e.g. the heuristic Espresso algorithm, which is faster and uses less memory, but does not always provide the minimum solution.
Unfortunately, I have not yet got around to implementing the Espresso algorithm.

see also #495


Is there a way to increase the number of inputs at your own risk?


Yes! You can start the simulator with the command line argument `experimental`.
This avoids the error message. But in this case you should also increase the allowed max memory consumption.

java -Xmx8192m -jar Digital.jar experimental


You could import the package.json as part of the nuget, as a content spec.

not sure how / if you can kick of an npm install during the nuget install process though.


Yep, having the file there is doable but the rest seems tricky and/or really hackish. Gulp Extensions is pretty much an NPM package as well, so perhaps it should be as such too but I really don't want to go into that (perhaps only some local NPM package coming from NuGet-like trick).


I terminated the program after about 4 hours. Memory consumption was up over 10 GB. I really like the program but will have to use it for logic simulations and smaller CPLD's only.


Apparently I didn't finish my reply to Seth. I wanted to add, that flat local files need to be referenced from Gulp Extensions from JS modules within the consumer project (namely, form a Gulpfile.js). I don't know how this can work well, I think you can only make those files end up in the build output folder (since you have to use the from JS, you can't used embedded files and such).


As I said before: Exact solution algorithms are of order O(2^n). These are not suitable for minimizing equations with more than 12-14 variables. And this is sufficient for the application for which the simulator is intended (teaching).
But without a heuristic, non-exact solution method like e.g. the Espresso algorithm, it is not possible to find a solution in many cases.


While it is possible, it's not ideal. Here's a blog post URL

The problem is that using content files in a nuspec means they are just copied in during the install process.
They are not maintained by NuGet afterwards. So you can delete / modify them etc

They do get recopied during an upgrade.

Not sure how you can do them without writing your own nuspec, i.e. from a csproj generated nuspec. Probably possible, but the last time I had to do this, was before we had csproj style nuspecs. Used to do it to copy linker .cs files in from Xamarin, which often needed further modification afterwards.


Commit e79f4ed seems to fix the issue by calling `CPLPushErrorHandler()` before threads are started (or as a first call within a thread). Hoever, the issue will remain open until changes are merged into master.


Bovenstaande laatste opmerking beschrijft het wijzigingsverzoek.
Deze 2 objecttypen komen voor als subtype van BLKActiviteit:
<img width="420" alt="image" src=" URL


Hmm, I used contentFiles before (Lombiq.Tests.UI has them) and to me it seems that while they appear as local files in the project from the Solution Explorer of VS, they are actually referencing the files in the package. I.e. if you want a path to them from outside of your .NET project (where you can reference them with a relative path from C#) you'll need to use the absolute path to the package in the NuGet package cache. They can be made copied to the output folder but then you have to reference the output folder which isn't really a good solution either.


You can use our `trtexec` from Nvidia's TensorRT container release to convert onnx to trt model. The generated model would be compatible with corresponding release of Triton. For instance, model generated with 22.01 TRT container will work with 22.01 Triton container.
 URL


would be a bit weird to add a uberon specific AP to CL. I've previously used exact synonym in CL but do understand that there might be use cases for that - thoughts on this @dosumis?


You can find more about the difference here: URL
Closing the issue now. Please re-open if you have any other questions.


Hi,

I'm currently experiencing more or less the same issue as the author of the ticket URL .
I'm compiling a project in Kotlin through gradle while using your libs

 javacpp_version = '1.5.7-SNAPSHOT'
 ffmpeg_version = "4.4.1-$javacpp_version"

 runtimeOnly "org.bytedeco:ffmpeg:$ffmpeg_version:macosx-x86_64"
 runtimeOnly "org.bytedeco:javacpp:$javacpp_version:macosx-arm64"

I also tried with other mixes of version (4.4-1.5.6/ 4.3.1-1.5.4)

The project used to run perfectly on intel Macs with version 4.3.1-1.5.4
But now, on a Mac M1 whatever the versions used I always get the same error

├─ org.bytedeco.ffmpeg.global.avutil. (avutil.java:14)
├─ org.bytedeco.javacpp.Loader.load(Loader.java:1123)
├─ org.bytedeco.javacpp.Loader.load(Loader.java:1300)
├─ org.bytedeco.javacpp.Loader.loadLibrary(Loader.java:1683)
├─ java.lang.System.loadLibrary(System.java:1989)
├─ java.lang.Runtime.loadLibrary0(Runtime.java:818)
├─ java.lang.ClassLoader.loadLibrary(ClassLoader.java:2429)
│
↑ no jniavutil in java.library.path: /Users/faw/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. (UnsatisfiedLinkError)
├─ java.lang.ClassLoader.loadLibrary(ClassLoader.java:2429)

I was wondering if you had directions to provide to fix this issue? Specific versions to use or different packages to use?

For reference here is the java version I currently use :

openjdk 17.0.2 2022-01-18
OpenJDK Runtime Environment (build 17.0.2+8-86)
OpenJDK 64-Bit Server VM (build 17.0.2+8-86, mixed mode, sharing)


I encounter a pahole (my `apt info dwarves` is `1.20-1+gl0`) issue.

 LD .tmp_vmlinux.btf
 BTF .btf.vmlinux.bin.o
[750483] INT DW_ATE_unsigned_56 Error emitting BTF type
Encountered error while encoding BTF.
 LD .tmp_vmlinux.kallsyms1
 KSYMS .tmp_vmlinux.kallsyms1.S
 AS .tmp_vmlinux.kallsyms1.S
 LD .tmp_vmlinux.kallsyms2
 KSYMS .tmp_vmlinux.kallsyms2.S
 AS .tmp_vmlinux.kallsyms2.S
 LD vmlinux
 BTFIDS vmlinux
FAILED: load BTF from vmlinux: Invalid argument
make[2]: *** [/home/maskray/Dev/linux/Makefile:1155: vmlinux] Error 255
make[2]: *** Deleting file 'vmlinux'
make[1]: *** [/home/maskray/Dev/linux/Makefile:350: __build_one_by_one] Error 2
make[1]: Leaving directory '/tmp/linux/ppc64le'
make: *** [Makefile:219: __sub-make] Error 2

The change refactored how `DT_RELACOUNT` (shown as `RELACOUNT` in `readelf -d` output), which is defined for `-z combreloc` (default): the number of `R_*_RELATIVE` relocations in the beginning of `.rela.dyn`. I can find some `RELACOUNT` usage in arch/powerpc/ . Is the `DT_RELACOUNT` value now wrong?

% rg RELACOUNT
include/uapi/linux/elf.h
108:#define DT_RELACOUNT 0x6ffffff9

arch/powerpc/kernel/reloc_64.S
11:RELACOUNT = 0x6ffffff9
30: * Scan the dynamic section for the RELA and RELACOUNT entries.
41:2: addis r6,r6,(-RELACOUNT)@ha
42: cmpdi r6,RELACOUNT@l
44: ld r8,8(r11) /* get RELACOUNT value in r8 */
47:4: cmpdi r7,0 /* check we have both RELA and RELACOUNT */

arch/powerpc/boot/crt0.S
11:RELACOUNT = 0x6ffffff9
68: * We need the RELA and RELACOUNT entries. */
78:11: addis r8,r8,(-RELACOUNT)@ha
79: cmpwi r8,RELACOUNT@l
81: lwz r0,4(r12) /* get RELACOUNT value in r0 */
88: * The R_PPC_RELATIVE ones come first and there are RELACOUNT
163:10: addis r12,r12,(-RELACOUNT)@ha
164: cmpdi r12,RELACOUNT@l
166: ld r8,8(r11) /* get RELACOUNT value in r8 */
170: cmpdi r13,0 /* check we have both RELA and RELACOUNT */


`vmlinux` has some position-independent long branch thunks which need `R_*_RELATIVE` relocations. In such a case, ld.lld generated `DT_RELACOUNT` value is smaller than the actual value. I can make it correct but.. well, it's just more code without many benefits.

glibc logic is the following and a smaller DT_LACOUNT value will still work.

c
Treat the DT_RELACOUNT relocations as R_PPC64_RELATIVE. Don't check their type

For the rest relocations, check the type and perform R_PPC64_RELATIVE/R_PPC64_ADDR64/...

The arch/powerpc code just seems to assume that there is no `R_PPC64_RELATIVE` after the first `DT_RELACOUNT` relocations.


There's probably some important context as _why_ the number of that type of relocation is hard coded in the source...


FWTW, similar issues does NOT affect `JsonNode`, as of Jackson 2.13.0 and later on.
Should have created separate issue to point to, but iterate version of `JsonNodeDeserializer` was merged in at around March 2021.
Would be great to achieve the same here for 2.14.


All right, I changed the FFmpeg versions for the project and adapted it from v4 to v5, but then I have a new error :

├─ org.bytedeco.ffmpeg.global.postproc. (postproc.java:182)
│ org.bytedeco.ffmpeg.global.postproc.LIBPOSTPROC_VERSION_INT(postproc.java:-2)
│
↑ 'int org.bytedeco.ffmpeg.global.postproc.LIBPOSTPROC_VERSION_INT()' (UnsatisfiedLinkError)

My FFmpeg -version output :

ffmpeg version 5.0 Copyright (c) 2000-2022 the FFmpeg developers
built with Apple clang version 13.0.0 (clang-1300.0.29.30)
configuration: --prefix=/opt/homebrew/Cellar/ffmpeg/5.0 --enable-shared --enable-pthreads --enable-version3 --cc=clang --host-cflags= --host-ldflags= --enable-ffplay --enable-gnutls --enable-gpl --enable-libaom --enable-libbluray --enable-libdav1d --enable-libmp3lame --enable-libopus --enable-librav1e --enable-librist --enable-librubberband --enable-libsnappy --enable-libsrt --enable-libtesseract --enable-libtheora --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libxvid --enable-lzma --enable-libfontconfig --enable-libfreetype --enable-frei0r --enable-libass --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libspeex --enable-libsoxr --enable-libzmq --enable-libzimg --disable-libjack --disable-indev=jack --enable-videotoolbox --enable-neon
libavutil 57. 17.100 / 57. 17.100
libavcodec 59. 18.100 / 59. 18.100
libavformat 59. 16.100 / 59. 16.100
libavdevice 59. 4.100 / 59. 4.100
libavfilter 8. 24.100 / 8. 24.100
libswscale 6. 4.100 / 6. 4.100
libswresample 4. 3.100 / 4. 3.100
libpostproc 56. 3.100 / 56. 3.100

libpostproc seems to be installed correctly


I've fixed that in the just released version. Try again with "5.0-1.5.7" (without "-SNAPSHOT"):
 URL


Werkgroep:
- wat is de argumentatie achter keuze van de huidige waarden in de waardelijst
- alleen die (11) opnemen waar niet te berekenen achterstaat (tabel B3, Bkl) blz 264, bijlage VII
- kom met voorstel


We can work around by committing the wwwroot folder to the repo to be able to publish projects that utilize Gulp Extensions. However, GE itself and the Vue module won't be usable from NuGet.


I'm in favor of moving away from `master`.

I'd say, for now, lets just move to `main` ASAP (since we're making other soft-breaking changes to our dev environment anyway).

We can always move to something more elaborate when needed.

My 2⃣🪙


Hello! We're actively working on porting Reanimated to Fabric but it's not completely ready yet. In fact, Reanimated integrates quite closely with the renderer system so we need to rewrite some parts specifically for Fabric and that's exactly what we have been doing for the past few months.

The good news is that in parallel we're porting react-native-gesture-handler and react-native-screens to Fabric as well so hopefully the developers will be able to enable Fabric in their apps as soon as possible.


System config and cache directories were moved under `/workspace` folder as a part of URL

We need to add ability to include JB backend into prebuilds. There following things to consider:
- indexes created by one backend is mostly not reusable by created by another backend, so there should be a way to configure for which backend indexes should be created per repo/project
- there are different places where we could configure it, like in .gitpod.yml or in settings of project.

As a prototype, for the start we could support only IntelliJ indexing and it in .gitpod.yml as an experimental feature.


It should be in `.gitpod.yml` if we create a dependency from the init task.
Would it as an intermediate solution be ok to simply download the binaries (in docker or init task) instead of configuring the IDE on project level?


The author had mention it’s not being maintained due to exhaustion of resource: he was doing it for free anyway, and if you look at the earlier post, you’d understand you should not expect updates and supports.

said earlier post

Then again if you need a responsive site you shouldn’t be looking at indexhibit, it is a platform designed from the time of simpler sites.


Hmm, it's interesting... Is this tape really brand new?

The `mkltfs` checks the tape was already formatted or not before formatting it. Normally, the `mkltfs` checks there are two partitions format and then tries to mount the tape for checking. There are two funny points in this case.

1. The `mkltfs` didn't detect non-partitioned tape at all. Is this tape really brand new?
2. The `mkltfs` tried to seek to the end of data but the drive returned an error `End-of-Data (EOD) not found`. This is clearly drive fault if this tape really brand new. It shall find a EOD at the beginning of the tape.

You can use `--force` option to skip the LTFS format check if it is sure you can erase everything of this tape.


There's a go implementation of persistent priority queue backed by leveldb here: URL It can be used as a reference for this.

Our priority queue needs to by default maintain order, because we do want to know the sorted list of jobs. But also allow us to add a special priority number on top.

From my imagination:

This reminds me of the indexing problem, where you can ask for a list of rows sorted by several columns. The first column would dictate the base sort, then subsequent columns would sort any ambiguous sub-orders.

Imagine we had 2 indexes. The first being your priority index using an arbitrary number, the second being the monotonic time index using `IdSortable`. You could sort on the priority index first, then sort on `IdSortable` second.

Maybe this then has a relationship to #188.


Yes, it's absolutely new - unpacked it some days ago.

Tried to use `--force` argument (but not sure if in the right way, no I see another error

root@office:~# mkltfs -d /dev/sg --force
LTFS15000I Starting mkltfs, LTFS version 2.5.0.0 (Prelim), log level 2.
LTFS15041I Launched by "mkltfs -d /dev/sg --force".
LTFS15042I This binary is built for Linux (x86_64).
LTFS15043I GCC version is 10.2.1 20210110.
LTFS17087I Kernel version: Linux version 5.13.19-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.13.19-4 (Mon, 29 Nov 2021 12:10:09 +0100) i386.
LTFS17089I Distribution: PRETTY_NAME="Debian GNU/Linux 11 (bullseye)".
LTFS15003I Formatting device '/dev/sg'.
LTFS15004I LTFS volume blocksize: 524288.
LTFS15005I Index partition placement policy: None.

LTFS11337I Update index-dirty flag (1) - NO_BARCODE (0x0x565238a7fc20).
LTFS17085I Plugin: Loading "sg" tape backend.
LTFS30209I Opening a device through sg-ibmtape driver (/dev/sg).
LTFS30288I Opening a tape device for drive serial /dev/sg.
LTFS12012E Cannot open device: failed backend open call.
LTFS15009E Cannot open device '/dev/sg' (-21711).
LTFS15023I Formatting failed.


I believe it is a known HBA issue. Need to recompile with `--enable-buggy-ifs`.

See #157 and URL


@shawntanzk (cc @bvarner-ebi )

While OBO members may not all agree on how strict we should be with the "exact" synonym scope, I do think that in CL there are plenty of use cases for the "abbreviation" annotation property. E.g. ESC, Treg, TAC... Abbreviations and acronyms are also discussed in the OBOOK here, so we wouldn't be going against consensus practice if we imported that AP. (Uberon has way more APs than CL and I think we've imported at least one before - location grouping - but I can't find mention of it.)