RfC: Ideas for Venezuela

Request for Comment
Request for Comment from the community about how Universe may assist Venezuelan's with their quest in a regime change and rebuilding their government and economy.
I attended a Galaxy Digital event last night and ran into Santiago Siri, Founder of Democracy Earth.  https://twitter.com/santisiri. Santiago used to work out of our offices at Blockstack.
@dant and I attended a “Help Venezuela” workshop at Consensus on Tuesday morning. Someone from Democracy Earth was on one of the 3 panels they had. DE is looking to provide Venezuelans with decentralized voting. They currently use Blockstack ID’s for their identity.
Dan and I were chatting and thinking of ways Universe can assist Venezuelans with ID’s and at the event last night, I asked Santiago how we can help and he said we should get together and brainstorm.
One ambitious long term goal is to provide them with decentralized Blockstack/Universe ID cards. Physical cards.. and digital cards.
I know David Kelts from https://www.idemia.com/ and can reach out to him. David produces 48 states driver’s license ID cards, all of Canada’s and quite a few of Europe’s as well. I’ve had conversations with David at past IIW https://internetidentityworkshop.com/ events about this.
I'd love for everyone to assist.
Consensus session
Tue May 14/ 10:00 AM - 12:00 PM  ( 2 Hours )
Not the Petro: Bottom-Up Blockchain Ideas for Venezuela
Room A, Concourse Level
Cryptocurrency has become a lifeline for many Venezuelans seeking respite from the country's dramatic collapse. Hear first-hand from the projects operating on the front lines, and contribute to a broader discussion on how blockchain technology can help rebuild Venezuela's economy and institutions.
Workshop
Speakers
Joe Waltman
Executive Director
GiveCrypto.org
Speaker
Ruben Galindo
CEO
Airtm
Speaker
Eduardo Medina
Lead Developer
Democracy Earth Foundation
Speaker
Mariano Di Pietrantonio
Community Lead Latin America
MakerDAO
Speaker
Jonathan Kohn
CEO and Co-founder
Cripto Conserje
Speaker
Daniel Knobelsdorf
Blockchain Strategist
Kruger Corp
Speaker
Moises Rendon
Associate Director & Associate Fellow
Center for Strategic & International Studies
Moderator
Bailey Reutzel
Multimedia Editor
CoinDesk
Moderator
Yaya Fanusie
Senior Felllow
Foundation for Defense of Democracies
Speaker
Fernando Cutz
Senior Associate
The Cohen Group
Speaker
Elena Sofia Giralt
Meetup Organizer
Blockchain Latinx
Speaker
Alex Gladstein
Chief Strategy Officer
Human Rights Foundation
Speaker
Daniel Sierra
Public Policy Advisor
Venezuelan Embassy
Speaker
Armando Armas
Congressman
Venezuela National Assembly
Speaker
Betilde Muñoz-Pogossian
Director of the Department of Social Inclusion of the Secretariat for Access to Rights and Equity
Organization of American States
Speaker
Josh Swihart
Vice President, Marketing and Business Development
Electric Coin Company
Speaker

This is how one currently logs in on Democracy Earth.. https://democracy.earth/


Images for Wiki pages

Hi @asijbers, here you can find some instructions on how to embed images in Wiki.

I've also added a directory to store images per use case here.


Add android exoplayer disableBufferNoConnection

Adds disableBufferNoConnection to prevent buffering while there is no internet connection
Jira: VEX-6518
Reviews

Major reviewer (domain expert): @armadilio3
Minor reviewer: @gabriel-rivero

Closing in favor of https://github.com/crunchyroll/react-native-video/compare/master...crunchyroll:vex-6518-fix-disconnect-bypass?expand=1, since this appears to not work on all devices


Make sink-classes public to allow sink registration using dependency injection

We register our sinks using dependency injection. Unfortunately SeqSink and related classes are all internal and the only possibility to create a sink seems to be to add it to the logger-configuration directly using the extension method.
Please provide an alternative!

Thanks for the ticket!
I don't think registering sinks by dependency injection is a well-supported scenario across Serilog. (It seems like there are a few potential gotchas, such as how to then log errors in your IoC configuration.)
One thing you could do to work around this currently, is to do something like this, if you're using Autofac:
// Assumes you're also registering a singleton `LoggingLevelSwitch` that
// is shared with the root logger
builder.Register(c => new LoggerConfiguration()
    .MinimumLevel.ControlledBy(c.Resolve<LoggingLevelSwitch>())
    .WriteTo.Seq(..., controlLevelSwitch: c.Resolve<LoggingLevelSwitch>())
    .CreateLogger())
    .As<ILogEventSink>();

It looks a little bit overblown, but it should work on the current API.
It's possible SeqSink and so-on could eventually be made public, but since they're not currently designed or reviewed with long-term API maintainability in mind that would likely take a while. How's the workaround go for you?

Hey,
thank you for your answer. At the end I did something similar, writing my own sink that internally delegates to a Logger created with the Seq-Sink.
I thought Seq was an exception in that it did not provide a public constructor, because the others sinks we were using (namely application insights and windows event log) did provide so. This was why I raised the ticket.
Best regards,
Thomas

Thanks for the reply, Thomas. The Seq sink probably is in the minority - there are quite a few that do provide public sink classes 👍
I think for now I'll close this but it's something I might come back to and re-think. Thanks again!


Support for v3?

Feature request
Summary
Supporting Strapi v3 until it is deprecated.
Why is it needed?
Considering how young Strapi v4 is and how the migration guide is still in progress, I think it's a good idea to support v3 for now. I'm sure me and other developers are willing to help. It would be great if you can guide us where to start.
Suggested solution(s)

Related issue(s)/PR(s)

Hi @alvitoraidhy
Totally agree with you on this one.
Though I'm gonna say it up front; this is gonna take some effort.
I could for sure help in guiding and facilitating, but we will need more man-power to finish the job in a reasonable time.
From my side a small list of what I think should be done:
Must haves

Copy the CLI from v4 to v3 (should be fairly easy)
Export the i18n-locales as wel (to fix #8)
Windows support (#14)

Nice to haves

Partial import/export (#22)
Sync admin roles/permissions (#20)
Custom types (#21)

I've pushed the latest v3 release of the plugin (0.1.6) to a new branch:
https://github.com/boazpoolman/strapi-plugin-config-sync/tree/v3
You can use that branch to fork and create PR's to.

Thanks. I'll see what I can contribute

Hey @alvitoraidhy
Did you find some time to work on this?
I wanted to suggest another approach to this; forking the v4 plugin and updating that for v3.
It might take a bit more time but the plugin would be much more feature rich and bug free.

Hey @alvitoraidhy
Did you find some time to work on this?
I wanted to suggest another approach to this; forking the v4 plugin and updating that for v3. It might take a bit more time but the plugin would be much more feature rich and bug free.

Hi. I haven't found a time to work on this unfortunately.
Forking the v4 and then updating it all at once could work, but I believe adding the features incrementally is the more appropriate approach for this so if the progress were to stale midway, at least there would be some new features for everyone to use.
But that's just my thought and I haven't even started working on it anyway.

It's been a while and Strapi v3 has since been deprecated.
I'm gonna close this issue, as well as delete the v3 branch.
This plugin will no longer get updates for v3.


Allow specifying mangle options

Uglifyjs supports options passed into the mangle_names method: https://github.com/mishoo/UglifyJS2/blob/4761d07e0bc3d4c53e0c9c72fc9c322c95cb090e/lib/scope.js#L394
This PR changes the mangle option to optionally take an object and pass options.

Thanks, it might be nice if we rather retain the existing functionality, but just add an extra uglifyOpts.mangle option? We support builder.build('x', { uglify: { compress: {...custom compressor options..}, beautify: {...} } } so could just extend that to { uglify: { compress: {...}, mangle: {...}, ... } }.


How do I launch the extension?

Sorry for the newbie question but for the life of me I cannot figure out how the variable inspector is supposed to launch on Jupyterlab. Is there a button somewhere to launch it or should it be appearing on its own? It does not seem to be doing the latter.
Thanks

Right click the notebook and click variable inspector, I didn't see it because it took me some time to find the demo.


Logging steps to migrate from sqlite to postgres

Implemented this on two different nodes - follow at your own risk
Just logging the steps here to carefully record what needs to be done to migrate from LNDg sqlite to postgres. This is for advanced users, and I just want to kick off the convo here with ngu to ensure all grounds are covered properly
Preparation

check your locale is set to LANG=en_US.UTF-8

Postgress

install postgres with sudo apt install postgresql
login via sudo su - postgres and check locale again to ensure your global settings are not tricking you for all you non-US users out there
login to postgres with psql and create the database
create user lndg;create database lndg LOCALE 'en_US.UTF-8' TEMPLATE template0;alter role lndg with password '<psql_password>';grant all privileges on database lndg to lndg;alter database lndg owner to lndg;
exit with \q
exit from postgres user, back to your main-user

Additional Requirements

cd lndg
sudo .venv/bin/pip install --upgrade setuptools
sudo apt install libpq-dev
.venv/bin/pip install psycopg2

Exectution

Stop lndg systemctl services
sudo systemctl stop htlc-stream-lndg.service && sudo systemctl stop rebalancer-lndg.timer && sudo systemctl stop jobs-lndg.timer
adjust database connections: cd lndg and nano lndg/settings.py

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'NAME': 'lndg',
        'USER': 'lndg',
        'PASSWORD': '<psql_password>',
        'HOST': 'localhost',
        'PORT': '5432',
    }
}

Dump your existing data into a jason file
cd lndg && .venv/bin/python manage.py dumpdata gui.channels gui.peers gui.rebalancer gui.localsettings gui.autopilot gui.autofees gui.failedhtlcs > dump.json
.venv/bin/python manage.py migrate

Remove some noise
.venv/bin/python manage.py shell
from django.contrib.contenttypes.models import ContentType
ContentType.objects.all().delete()
exit()

Import

import dump data into postgres: .venv/bin/python manage.py loaddata dump.json
recreate your login user with data from lndg/data/lndg-admin.txt: .venv/bin/python manage.py createsuperuser
user: lndg-admin
pwd: cat lndg/data/lndg-admin.txt

Tiny adjustments

nano jobs.py
Required temporary change for payment/invoice messages on lines 52, 93, 112 of jobs.py (find/replace in nano via ALT-R)
.decode('utf-8', errors='ignore')
.decode('utf-8', errors='ignore').replace("\x00", "\uFFFD")

Put it together

Restart uwsgi via sudo systemctl restart uwsgi
Start all lndg-background services: sudo systemctl start htlc-stream-lndg.service && sudo systemctl start rebalancer-lndg.timer && sudo systemctl start jobs-lndg.timer

Verify & Conclude
Login to your GUI and verify all is working

tables payments and invoices may need some time repopulating. Those haven't been migrated
in case for my instance, I had 60,000 entries, so it's running backwards from 8 months and took 1.5hrs. If you have a slow machine, this is going to take a long time (couple of hours, at least)

Also was required for compilation of psycopg2:  sudo apt install gcc python3-dev
Was able to create a database without template or LOCALE data.
create user lndg;create database lndg;alter role lndg with password '<psql_password>';grant all privileges on database lndg to lndg;alter database lndg owner to lndg;


Module organization in lib/utils?

So I have a question about code organization in lib/utils: how does it work/what is the structure behind it?
I wondered this for a long time. From my perspective, it just looks like a mess. Of course, I never understood the file layout, so I very much contributed to that mess.
What confuses me the most are index.ts files with function/class/type definitions. index.ts files in my projects typically only re-export other modules to define an API. I pretty much never put definitions in index.ts files, because e.g. a/b.ts cannot import a function from a/index.ts (cyclic import).

As an example: I want to add new util function:
function assertNever(value: never): never {
  throw new Error("Unsupport value: " + value)
}

This might be most util of util method. It has no dependencies, and I will need it in a lot of places (see #575 for more info).
Importantly, many util methods also need this, so I can't define it in lib/util/index.ts (cyclic import). But I also don't really want to make a lib/util/util.ts. Where should I put this function?
Also, we have around 5 copies of assertNever in various files already.

Maybe a bit of background. In my JS/TS projects, I typically go for a flat hierarchy for internal modules (= files that don't define functions/classes/types of the public API). So each of those internal modules just exports their functions/classes/types and that's it. Those internal modules might be in different folders, but there is no hierarchy between them. So internal modules never re-export things from other internal modules and there are no internal index.ts files.
I do this because it makes it easy to extract out common functionality into a module. I don't have to worry about internal hierarchies and can just create a new file.
Again, I'm only talking about internal modules. I use index.ts files and re-exports to define the public API of a package like everybody else. Although my index.ts files only re-export other modules, I don't define any functions/classes/types in them.

As you say, I think the structure of lib/utils is a mess😓 I think lib/utils needs to be refactored.
I checked the structure of your project and I think it's good to organize it like that.


added code generated attribute to file response

edited the template so the FileResponse is annotated with the GeneratedCodeAttribute
#2653

Thx for the pr.


Chapter 4 - utils directory is referenced as scripts directory

In the book, in Chapter 4, the utils(https://github.com/HyperledgerHandsOn/trade-network/tree/master/bash/utils) directory is referenced as scripts.

BTW, I don't know if this is the right place for reporting about such topics

I see it. We used scripts as a placeholder in the early stages of the project and renamed the folder to utils later. Thanks for pointing this out. I'll try to get in touch with the publisher.
It's perfectly fine to draw our attention to errors here. Alternatively, you can also email the publisher, who in turn will get in touch with us.

Added a note in the Errata Wiki for our readers and users. Thanks for pointing it out!


ResourceRecordsSets not deleted before HostedZone makes "Pre-clean Test Account" job fail

Examples:

https://github.com/iasql/iasql-engine/actions/runs/3763114831/jobs/6396406787#step:7:14276

ERROR:  Error: HostedZone cloud delete error: The specified hosted zone contains non-required resource record sets and so cannot be deleted.
Another example:
https://github.com/iasql/iasql-engine/actions/runs/3821846846/jobs/6501437111
Account: 29
Region: ap-south-1

We should also include the full error and description for the future errors, since the CI logs are deleted from time to time:


Stop non-js tracking on the homepage

This code was meant to be temporary, #452:

To be removed one week from merge.

It's been running 2.5 years. We might also want to revert https://github.gds/gds/puppet/pull/978
Revert "Merge pull request #452 from alphagov/add-non-js-tracking". This reverts commit 9d2bca43cc69ee4cfafbeff2bf64473a2b9f817d, reversing changes made to bfd5f6b2a71aa32395d31b72594e2ee34c0d14c8.
cc @tombye

WIP branch to remove on puppet too, it'd be good to get a sanity check on that:
https://github.com/alphagov/govuk-puppet/compare/revert-non-js-tracking

And the puppet change looks good too, so raise a PR for that when you're ready 👍


Error: `GLIBC_2.34' not found

We are getting intermittent errors in our CI pipeline during the snok/install-poetry@v1 task:
Run snok/install-poetry@v1

Run $GITHUB_ACTION_PATH/main.sh

Setting Poetry installation path as /github/home/.local

Installing Poetry :builder:

python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by python3)
python3: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /__w/_tool/Python/3.11.1/x64/lib/libpython3.11.so.1.0)
python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /__w/_tool/Python/3.11.1/x64/lib/libpython3.11.so.1.0)
python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /__w/_tool/Python/3.11.1/x64/lib/libpython3.11.so.1.0)
python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /__w/_tool/Python/3.11.1/x64/lib/libpython3.11.so.1.0)
Error: Process completed with exit code 1.

What does your workflow definition look like?

Thanks for your prompt reply. It was an issue with a Playwright base image that we were extending in CI.


add house name under Avaible placeholders

Added a line to include a house number under Available placeholders

@binaryberry Thanks so much for helping with this!


[Ace] Fix statusbar max width

Fix for super long filenames breaking statusbar layout.

Hi @snobu, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

FYI. it's live in Azure, along with all previous changes!


chore(ci): fix BrowserStack timeouts

Assuming that the issue is concurrent jobs attempting to interact with BrowserStack using the same build ID, this solution attempts to solve it by only interacting with BrowserStack in one of the jobs.
Updated build definition:

runs complete build on the latest Node
runs simplified build (without commit validation, lint, test:client and test:integration) on earlier versions on Node

It is not very valuable to run omitted test suits multiple times as they supposed to catch issues, which are usually Node-independent: client code fails in some browsers and API breaking changes, which will affect popular Karma plugins.
Fixes #3468

Ignore the failed travis-ci/push build. Have no idea why GitHub picked it up, given that this is a branch from my fork.

Thanks!


fogros2: 0.1.2-2 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository fogros2 to 0.1.2-2:

upstream repository: https://github.com/BerkeleyAutomation/FogROS2.git
release repository: https://github.com/ros2-gbp/fogros2-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.1
previous version for package: null

fogros2
* removed unique name generator and fixed package.xml

I'll merge this, and if you decide you want to add in source info, you can open another PR!
CH3EERS!


Coredump after pushing new branch with an invalid webhook (RasbperryPi 3)

Gitea version (or commit ref): 1.11.4
Git version: 2.26.2
Operating system: archlinuxARM ($uname -srmo : Linux 5.6.7-1-ARCH aarch64 GNU/Linux)
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

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

Log gist:
https://pastebin.com/0PGUayjD

Description
I run a private gitea instance with the systemd service of the archlinux package.
I am the only user on this instance. I have I think 6 quite small repos.
I locally created a new branch in a repo.
I pushed it by executing : git push origin {BranchName}
Gitea has been restarting every 20 seconds since, and generating tons of coredumps (following longer intervals are due to reboots and config tweaks that did not help) :
$ sudo coredumpctl
TIME                            PID   UID   GID SIG COREFILE  EXE
Mon 2020-04-27 23:59:57 CEST    856   973   973  31 missing   /usr/bin/gitea
Tue 2020-04-28 00:01:51 CEST    958   973   973  31 missing   /usr/bin/gitea
Tue 2020-04-28 00:09:17 CEST   1139   973   973  31 missing   /usr/bin/gitea
Tue 2020-04-28 00:25:34 CEST   1344   973   973  31 missing   /usr/bin/gitea
Tue 2020-04-28 00:25:55 CEST   1375   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 00:58:50 CEST   1046   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 00:58:59 CEST   1074   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:07:54 CEST   1174   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:08:47 CEST   1212   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:10:03 CEST   1257   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:13:44 CEST   1288   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:13:54 CEST   1322   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:20:49 CEST   1384   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:21:38 CEST   1419   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:56:11 CEST   2937   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 01:59:21 CEST   2964   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 02:01:40 CEST   2994   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 02:02:17 CEST   3017   973   973  31 present   /usr/bin/gitea
Tue 2020-04-28 02:02:29 CEST   3041   973   973  31 present   /usr/bin/gitea

I tried to gdb the coredumps but I think its output is not very useful :
(sorry, this is the first time I ever launch gdb, I may not be very aware of what's useful or not. Saw it in another issue ...)
$ sudo coredumpctl gdb 3017
           PID: 3017 (gitea)
           UID: 973 (gitea)
           GID: 973 (gitea)
        Signal: 31 (SYS)
     Timestamp: Tue 2020-04-28 01:58:01 CEST (29min ago)
  Command Line: /usr/bin/gitea web -c /etc/gitea/app.ini
    Executable: /usr/bin/gitea
 Control Group: /system.slice/gitea.service
          Unit: gitea.service
         Slice: system.slice
       Boot ID: b2c2901b20dd4532adcc64fe2f8f5ef3
    Machine ID: e9924b3339eb455fbe8473f0fb3250c3
      Hostname: rpi3
       Storage: /var/lib/systemd/coredump/core.gitea.973.b2c2901b20dd4532adcc64fe2f8f5ef3.3017.1588031881000000000000.lz4
       Message: Process 3017 (gitea) of user 973 dumped core.

                Stack trace of thread 3033:
                #0  0x0000aaaadb4ffcd0 n/a (gitea + 0x9e5cd0)
                #1  0x0000aaaadb4fe224 n/a (gitea + 0x9e4224)
                #2  0x0000aaaadb595fc4 n/a (gitea + 0xa7bfc4)
                #3  0x0000aaaadb5a8d40 n/a (gitea + 0xa8ed40)
                #4  0x0000aaaadb4cc1c4 n/a (gitea + 0x9b21c4)
                #5  0x0000aaaadb597b70 n/a (gitea + 0xa7db70)
                #6  0x0000aaaadb5a6054 n/a (gitea + 0xa8c054)
                #7  0x0000aaaadb5a6710 n/a (gitea + 0xa8c710)
                #8  0x0000aaaadb4b40a4 n/a (gitea + 0x99a0a4)
GNU gdb (GDB) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gitea...
(No debugging symbols found in /usr/bin/gitea)
[New LWP 3033]
[New LWP 3019]
[New LWP 3020]
[New LWP 3023]
[New LWP 3022]
[New LWP 3021]
[New LWP 3024]
[New LWP 3017]
[New LWP 3025]
[New LWP 3026]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/gitea web -c /etc/gitea/app.ini'.
Program terminated with signal SIGSYS, Bad system call.
#0  0x0000aaaadb4ffcd0 in ?? ()
[Current thread is 1 (Thread 0xffff6ffff1a0 (LWP 3033))]
(gdb) bt
#0  0x0000aaaadb4ffcd0 in ?? ()
#1  0x0000000000000007 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I thinks something broke during the push command, and now gitea is trying to redo this at boot and constantly failing ?

Screenshots
Not relevant

Is the last line of the logs genuinely:
2020/04/28 01:59:25 ...er/issues/indexer.go:142:func2() [I] PID 3041: Initializing Issue Indexer: bleve

?
If so then you could try just deleting the indexer files - Gitea will just recreate them.
The other thing is to try to run git gc across your repos from the command line. You probably need to set your .gitconfig options for pack.packSizeLimit and related options.

Thanks for your quick answer !
Yes it is, and the log then reset and coredump etc...
2020/04/28 01:59:25 ...er/issues/indexer.go:142:func2() [I] PID 3041: Initializing Issue Indexer: bleve is always the last log line.
I have the following :
# pwd
/var/lib/gitea/indexers
# ls -la
total 16
drwxr-x--- 4 gitea gitea 4096 May 18  2019 .
drwxr-xr-x 8 gitea gitea 4096 Apr 28 01:59 ..
drwx------ 2 gitea gitea 4096 May 18  2019 issues.bleve
drwxr-xr-x 2 gitea gitea 4096 Feb 13 01:56 issues.queue

Just to confirm that I understood correctly, you're telling me that I can delete them safely ?

I did both :

starting with the git gc of all repos : no luck
moving /var/lib/gitea/* elsewhere : no luck

I join the journalctl message that shows the same error after both try :
Apr 28 03:18:30 rpi3 gitea[3726]: 2020/04/28 03:18:28 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column data db default is 'NULL', struct default is
Apr 28 03:18:30 rpi3 gitea[3726]: 2020/04/28 03:18:28 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column created_unix db default is NULL, struct default is
Apr 28 03:18:30 rpi3 gitea[3726]: 2020/04/28 03:18:28 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column updated_unix db default is NULL, struct default is
Apr 28 03:18:30 rpi3 gitea[3726]: 2020/04/28 03:18:28 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column expires_unix db default is NULL, struct default is
Apr 28 03:18:31 rpi3 gitea[3726]: 2020/04/28 03:18:31 ...er/issues/indexer.go:142:func2() [I] PID 3726: Initializing Issue Indexer: bleve
Apr 28 03:18:31 rpi3 audit[3726]: SECCOMP auid=4294967295 uid=973 gid=973 ses=4294967295 pid=3726 comm="gitea" exe="/usr/bin/gitea" sig=31 arch=c00000b7 syscall=163 compat=0 ip=0xaaaae602fcd0 code=0x80000000
Apr 28 03:18:31 rpi3 audit[3726]: ANOM_ABEND auid=4294967295 uid=973 gid=973 ses=4294967295 pid=3726 comm="gitea" exe="/usr/bin/gitea" sig=31 res=1
Apr 28 03:18:31 rpi3 kernel: audit: type=1326 audit(1588036711.068:1046): auid=4294967295 uid=973 gid=973 ses=4294967295 pid=3726 comm="gitea" exe="/usr/bin/gitea" sig=31 arch=c00000b7 syscall=163 compat=0 ip=0xaaaae602fcd0 code=0x800000>
Apr 28 03:18:31 rpi3 kernel: audit: type=1701 audit(1588036711.068:1047): auid=4294967295 uid=973 gid=973 ses=4294967295 pid=3726 comm="gitea" exe="/usr/bin/gitea" sig=31 res=1
Apr 28 03:18:31 rpi3 audit: AUDIT1334 prog-id=52 op=LOAD
Apr 28 03:18:31 rpi3 audit: AUDIT1334 prog-id=53 op=LOAD
Apr 28 03:18:31 rpi3 systemd[1]: Started Process Core Dump (PID 3747/UID 0).
Apr 28 03:18:31 rpi3 kernel: audit: type=1334 audit(1588036711.178:1048): prog-id=52 op=LOAD
Apr 28 03:18:31 rpi3 kernel: audit: type=1334 audit(1588036711.188:1049): prog-id=53 op=LOAD
Apr 28 03:18:31 rpi3 kernel: audit: type=1130 audit(1588036711.198:1050): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@20-3747-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succ>
Apr 28 03:18:31 rpi3 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@20-3747-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

I'm currently trying to run gitea in gdb but I'm stuck with permission errors :
$sudo -u gitea gdb --args gitea web -c /etc/gitea/app.ini
... (same as system service log)
2020/04/28 14:55:42 routers/init.go:99:GlobalInit() [I] ORM engine initialization successful!
2020/04/28 14:55:42 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column data db default is 'NULL', struct default is
2020/04/28 14:55:42 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column created_unix db default is NULL, struct default is
2020/04/28 14:55:42 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column updated_unix db default is NULL, struct default is
2020/04/28 14:55:42 ...orm@v0.8.1/engine.go:1352:Sync2() [W] Table oauth2_session Column expires_unix db default is NULL, struct default is
2020/04/28 14:55:43 ...les/queue/setting.go:60:CreateQueue() [W] Unable to create queue for issue_indexer: mkdir data: permission denied
2020/04/28 14:55:43 ...les/queue/setting.go:61:CreateQueue() [W] Attempting to create wrapped queue
2020/04/28 14:55:43 ...les/queue/setting.go:60:CreateQueue() [W] Unable to create queue for task: mkdir data: permission denied
2020/04/28 14:55:43 ...les/queue/setting.go:61:CreateQueue() [W] Attempting to create wrapped queue
2020/04/28 14:55:43 ...er/issues/indexer.go:142:func2() [I] PID 5524: Initializing Issue Indexer: bleve
2020/04/28 14:55:43 routers/init.go:122:GlobalInit() [I] SQLite3 Supported
2020/04/28 14:55:43 ...eue/queue_wrapped.go:67:setInternal() [W] [Attempt: 1] Failed to create queue: level for  cfg: [123 34 65 100 100 114 101 115 115 101 115 34 58 34 49 50 55 46 48 46 48 46 49 58 54 51 55 57 34 44 34 66 97 116 99 104 76 101 110 103 116 104 34 58 50 48 44 34 66 108 111 99 107 84 105 109 101 111 117 116 34 58 49 48 48 48 48 48 48 48 48 48 44 34 66 111 111 115 116 84 105 109 101 111 117 116 34 58 51 48 48 48 48 48 48 48 48 48 48 48 44 34 66 111 111 115 116 87 111 114 107 101 114 115 34 58 53 44 34 68 66 73 110 100 101 120 34 58 48 44 34 68 97 116 97 68 105 114 34 58 34 100 97 116 97 47 100 97 116 97 47 113 117 101 117 101 115 47 116 97 115 107 34 44 34 77 97 120 87 111 114 107 101 114 115 34 58 49 48 44 34 78 97 109 101 34 58 34 116 97 115 107 34 44 34 78 101 116 119 111 114 107 34 58 34 34 44 34 80 97 115 115 119 111 114 100 34 58 34 34 44 34 81 117 101 117 101 76 101 110 103 116 104 34 58 50 48 44 34 81 117 101 117 101 78 97 109 101 34 58 34 116 97 115 107 95 113 117 101 117 101 34 44 34 87 111 114 107 101 114 115 34 58 49 125] error: mkdir data: permission denied
2020/04/28 14:55:43 routers/init.go:46:checkRunMode() [I] Run Mode: Production
2020/04/28 14:55:43 ...er/issues/indexer.go:199:func3() [I] Issue Indexer Initialization took 13.938819ms
2020/04/28 14:55:43 ...eue/queue_wrapped.go:67:setInternal() [W] [Attempt: 1] Failed to create queue: level for  cfg: [123 34 65 100 100 114 101 115 115 101 115 34 58 34 49 50 55 46 48 46 48 46 49 58 54 51 55 57 34 44 34 66 97 116 99 104 76 101 110 103 116 104 34 58 50 48 44 34 66 108 111 99 107 84 105 109 101 111 117 116 34 58 49 48 48 48 48 48 48 48 48 48 44 34 66 111 111 115 116 84 105 109 101 111 117 116 34 58 51 48 48 48 48 48 48 48 48 48 48 48 44 34 66 111 111 115 116 87 111 114 107 101 114 115 34 58 53 44 34 68 66 73 110 100 101 120 34 58 48 44 34 68 97 116 97 68 105 114 34 58 34 100 97 116 97 47 100 97 116 97 47 113 117 101 117 101 115 47 105 115 115 117 101 95 105 110 100 101 120 101 114 34 44 34 77 97 120 87 111 114 107 101 114 115 34 58 49 48 44 34 78 97 109 101 34 58 34 105 115 115 117 101 95 105 110 100 101 120 101 114 34 44 34 78 101 116 119 111 114 107 34 58 34 34 44 34 80 97 115 115 119 111 114 100 34 58 34 34 44 34 81 117 101 117 101 76 101 110 103 116 104 34 58 50 48 44 34 81 117 101 117 101 78 97 109 101 34 58 34 105 115 115 117 101 95 105 110 100 101 120 101 114 95 113 117 101 117 101 34 44 34 87 111 114 107 101 114 115 34 58 49 125] error: mkdir data: permission denied
2020/04/28 14:55:44 cmd/web.go:161:runWeb() [I] Listen: unix:///run/gitea/gitea.socket
2020/04/28 14:55:44 ...s/graceful/server.go:55:NewServer() [I] Starting new server: unix:/run/gitea/gitea.socket on PID: 5524
2020/04/28 14:55:44 ...s/graceful/server.go:79:ListenAndServe() [E] Unable to GetListener: listen unix /run/gitea/gitea.socket: bind: no such file or directory
2020/04/28 14:55:44 cmd/web.go:204:runWeb() [C] Failed to start server: listen unix /run/gitea/gitea.socket: bind: no such file or directory
2020/04/28 14:55:44 cmd/web.go:206:runWeb() [I] HTTP Listener: /run/gitea/gitea.socket Closed

Are those gdb related or is it what is really happening on my system ?

I'm changing the title as the multiple coredumps are due to the restart parameter of the gitea.service file. A single coredump is observed when restart is set to "no".

2020/04/28 14:55:43 ...les/queue/setting.go:60:CreateQueue() [W] Unable to create queue for issue_indexer: mkdir data: permission denied

That's the hint. You need to allow Gitea to create the queues directories.

Ok I managed to get it working by adding :
ReadWritePaths=/var/lib/gitea
in /usr/lib/systemd/system/gitea.service
What I don't get is why it is not working outside of systemd, when I launch the gitea app manually ?
# pwd
/var/lib/gitea
# ls -l
total 20
srw-rw-rw- 1 gitea gitea    0 May 18  2019 <IP_ADDRESS>
drwxr-x--- 2 gitea gitea 4096 May 18  2019 attachments
drwxr-x--- 5 gitea gitea 4096 Feb 20 23:34 data
drwxr-x--- 3 gitea gitea 4096 Apr 28 14:36 indexers
drwxr-x--- 3 gitea gitea 4096 May 18  2019 repos
drwxr-x--- 2 gitea gitea 4096 May 18  2019 tmp

I reported the bug to archlinux as it is more related to systemd than to gitea.
https://bugs.archlinux.org/task/60669
Issue solved I guess ...

Huh, not that fixed though, because now I have a coredump everytime I push on this new branch. Pushing to master in other repos is OK.
r 29 04:31:33 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:31:33: Completed POST /api/internal/hook/post-receive/belette/socket 200 OK in 145.211576ms
Apr 29 04:31:33 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:31:33: Started POST /api/internal/ssh/5/update/12 for @
Apr 29 04:31:33 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:31:33: Completed POST /api/internal/ssh/5/update/12 200 OK in 13.630955ms
Apr 29 04:32:30 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:30: Started GET /api/internal/serv/command/5/belette/unicodeparser?mode=2&verb=git-receive-pack for @
Apr 29 04:32:30 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:30: Completed GET /api/internal/serv/command/5/belette/unicodeparser?mode=2&verb=git-receive-pack 200 OK in 16.187553ms
Apr 29 04:32:30 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:30: Started POST /api/internal/hook/pre-receive/belette/unicodeparser for @
Apr 29 04:32:30 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:30: Completed POST /api/internal/hook/pre-receive/belette/unicodeparser 200 OK in 6.447615ms
Apr 29 04:32:31 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:31: Started POST /api/internal/hook/post-receive/belette/unicodeparser for @
Apr 29 04:32:31 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:31: Completed POST /api/internal/hook/post-receive/belette/unicodeparser 200 OK in 107.111974ms
Apr 29 04:32:31 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:31: Started POST /api/internal/ssh/5/update/9 for @
Apr 29 04:32:31 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:32:31: Completed POST /api/internal/ssh/5/update/9 200 OK in 12.708982ms
Apr 29 04:33:06 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:33:06: Started GET /api/internal/serv/command/5/belette/minecraftmanager_server?mode=2&verb=git-receive-pack for @
Apr 29 04:33:06 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:33:06: Completed GET /api/internal/serv/command/5/belette/minecraftmanager_server?mode=2&verb=git-receive-pack 200 OK in 17.004788ms
Apr 29 04:33:06 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:33:06: Started POST /api/internal/hook/pre-receive/belette/minecraftmanager_server for @
Apr 29 04:33:06 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:33:06: Completed POST /api/internal/hook/pre-receive/belette/minecraftmanager_server 200 OK in 7.521984ms
Apr 29 04:33:07 rpi3 gitea[11384]: [Macaron] 2020-04-29 04:33:07: Started POST /api/internal/hook/post-receive/belette/minecraftmanager_server for @
Apr 29 04:33:52 rpi3 systemd[1]: gitea.service: Main process exited, code=killed, status=31/SYS
Apr 29 04:33:52 rpi3 systemd[1]: gitea.service: Failed with result 'signal'.

Additionally, I can restart the gitea service successfully but I have to do so after each push on this branch.
I'll do some more testing tomorrow (branch master in this repo, non-master branches in other repos)

Just in case, make sure you've got only one copy of gitea around, and hooks and authorized_keys point to it correctly (there's a site admin menu for rebuilding those).

I finally found it !!
Additional info : my ssh server is listening to port 2223 instead of the default 22.
First, after a coredump, running sudo -u gitea gdb --args gitea web -c /etc/gitea/app.ini, running the debugger, stopping gdb and restarting the service works : the gitea instance starts successfully and the pushed commit is found in the gitea repo. However, it is not listed in the activity dashboard.
I created a test repository and :

committed a file in master -> OK
committed a file in a new branch -> OK

So then I asked myself what the hell is the difference between my "coredump" repo and this one ??
The reason why this repo coredumped after commits is an invalid webhook : I hosted a while ago a drone instance on another raspberry and linked it to my gitea instance, but it took too much resources, so I temporarily disabled it. A invalid webhook was still enabled on this repository (with a red cross next to it in the {repo}/settings/hooks page). After deleting it, no more coredumps happen. Why was it working in the master branch ? I don't know.
As the manual gitea command seems to work, I think systemd hardening is wrong somewhere, regarding webhooks. I join my gitea systemd setup :
/etc/systemd/system/multi-user.target.wants/gitea.service
===========================================
[Unit]
Description=Gitea (Git with a cup of tea)
After=syslog.target
After=network.target
After=mysqld.service
After=postgresql.service
After=memcached.service
After=redis.service

[Service]
User=gitea
Group=gitea
Type=simple
WorkingDirectory=~
RuntimeDirectory=gitea
LogsDirectory=gitea
StateDirectory=gitea
Environment=USER=gitea HOME=/var/lib/gitea GITEA_WORK_DIR=/var/lib/gitea
ExecStart=/usr/bin/gitea web -c /etc/gitea/app.ini
Restart=always
RestartSec=2s
CapabilityBoundingSet=
NoNewPrivileges=True
PrivateUsers=true
PrivateDevices=true
PrivateTmp=true
ProtectHome=true
ProtectSystem=strict
ProtectControlGroups=yes
ProtectKernelTunables=true
ProtectKernelModules=yes
ReadWritePaths=/etc/gitea/app.ini
LockPersonality=true
MemoryDenyWriteExecute=true
RestrictRealtime=true
SystemCallArchitectures=native
SystemCallFilter=@system-service

[Install]
WantedBy=multi-user.target

/etc/systemd/system/gitea.service.d/override.conf
=====================================
[Service]
AmbientCapabilities=CAP_NET_BIND_SERVICE
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
PrivateUsers=false
Restart=no
ReadWritePaths=/etc/gitea/app.ini
ReadWritePaths=/var/lib/gitea

Do you have any idea on your end about why would this happen ?

I'm glad you pinpointed the problem and could have it fixed for you.
The webhook was invalid how? What kind of response was getting Gitea? An HTTP error? A timeout?

Gitea was receiving a 404 response from my non existing drone instance adress.

and in response to the 404 there is a core dump?!

@Ouack23 we really need to see the logs just prior to the core dump if there are any available.

@zeripath I joined the gitea logs in my original post and the system logs in this message.
No other log was available ...

Please see if https://github.com/go-gitea/gitea/issues/9792#issuecomment-691291999 solves the issue for you as well.


Issue 638 process post solve

Description
Changes model.process_parameters_and_discretise to accept parameter values and a discretisation so that users can define new expressions in scripts to be processed and discretised.
Fixes #638
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Key checklist:

[x] No style issues: $ flake8
[x] All tests pass: $ python run-tests.py --unit
[x] The documentation builds: $ cd docs and then $ make clean; make html

You can run all three at once, using $ python run-tests.py --quick.
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works
[x] Any dependent changes have been merged and published in downstream modules

yeah exactly. think it would be a very tidy way of keeping track of things


Customize Attachment Handlers Throws error

When trying to implement a Customize Attachment Handler the same way the example is shown in the docs,  an error is thrown due to the lack of Field being passed in. However, you're unable to pass the Froala $field to the class from the Nova Resource.
Do you have any recommendations for this?
Froala::make('description')
    ->attach(new StorePendingMedia)
    ->detach(new DetachMedia)
    ->delete(new DeleteMedia)
     ->discard(new DiscardPendingMedia)
     ->images(new AttachedMediasList)
     ->options([
             'toolbarBottom'=>true,
             'height' => 400
     ]),

Need more details about error and your custom attachment handler implementation.

Feel free to reopen an issue with more details


Documentation for Azure Deployment

Motivation and Context (Why the change? What's the scenario?)
High level description (Approach, Design)

@dluc

@dluc ready, please review


Allow gcp_scanner to work with more scopes

As for now, gcp_scanner only supports retrieving and using OAuth2 tokens with cloud-platform scope granted. All other scopes will raise an error. However, some scopes would allow to retrieve partial information (e.g. https://www.googleapis.com/auth/devstorage.read_only to read GCS buckets and files)

Implemented in 6e2ff4be5f6886e094bab2d171dea3ed8ce68333


Support the notification coming from Parse.com when the background

Such as the push notification request from Parse.com, usually with different types of data will be sent.
Unfortunately, the current of this plug is not able to correspond to the format.
So, we added a program so as to correspond to Parce.com.

@Hikaru-Ito I appreciate this PR but I may not merge it. I need to look at way in which I can support different push data formats without having to write a bunch of if/else code.

@Hikaru-Ito thanks for the PR, I'm not going to merge it as #220 takes care of all the possible properties not just message. Please consider contributing in the future.

ok. thanks!


Revert "deps: Upgrade ESLint to ^6.8.0, and related deps."

See details in commit message; this follows from discussion.

Thanks for tracking this down!


Fixes gh-308

Motivation:
Explain the context, and why you're making that change.
To make others understand what is the problem you're trying to solve.
Modification:
Describe the idea and modifications you've done.
Result:
Fixes #.
If there is no issue then describe the changes introduced by this PR.

Hi @XCXCXCXCX, Please sign Contributor License Agreement!
After you signed CLA, we will automatically sync the status of this pull request in 3 minutes.

@XCXCXCXCX pls signed CLA


[Aio] Support tuple and aio.Metadata interaction

Fixes: https://github.com/grpc/grpc/issues/23554
aio.Metadata is introduced to ease the modification of gRPC metadata. In the past, we only accept tuple-in-tuple data structure, so many unit tests implicitly expect it to have tuple interfaces. This PR tries to make aio.Metadata compatible with tuple. Suggestions are welcomed.


Stacks JS- Add how-to guide for post conditions

This issue is created based on @hugocaillard's findings to add a how-to guide for Post conditions.
Reference: https://dev.to/stacks/understanding-stacks-post-conditions-e65Z
@hugocaillard Please add your thoughts and inputs to this issue.

Writing PCs (post conditions) can be difficult. Not because the code is hard to write, but because it's hard for developers to understand what they are trying to achieve with PCs (beyond "make transactions safe for users").
The only resources for that are unofficial, unmaintained, outdated and/or misleading (article by [Kenny](https://dev.to/stacks/understanding-stacks-post-conditions-e65, misleading doc on hiro.so).
I think we need one or two resources (blog post and doc maybe) to explain to main aspects:

what are PCs, what can we do with it, why is it important?
use cases references (kind of the go to doc when trying to write a PC) with real world use case

transfer STX / FT to a contract or an address
mint an NFT
transfer an NFT to a contract or an address
...

Note: some improvement might occurs on Stacks.js in the coming week, so the work on docs should reflect that (cc @janniks )

Yes, a comprehensive library of all the available post conditions and some example implementations would be huge.

We have a blog. Need to pull the content from there to include in the docs.

I couldn't find a blog post, can you share the link @LakshmiLavanyaKasturi?

@sabbyanandan, I remember you mentioned a blog somewhere about Post conditions. Can you please help post the link here? Thanks!

Just a little something I wrote regarding contracts with a single token or
NFT. The syntax for Post-conditions is designed for contracts that contain
any number of tokens or NFTs, therefore for a singl-token contract there is
some redundancy in the syntax, which can be confusing at first.
https://discord.com/channels/621759717756370964/623217767356694547/1138651620314451969
On Thu, Sep 7, 2023 at 7:39 AM Lavanya Kasturi @.***>
wrote:

@sabbyanandan https://github.com/sabbyanandan, I remember you mentioned
a blog somewhere about Post conditions. Can you please help post the link
here? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/hirosystems/docs/issues/331#issuecomment-1709999931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHJDL6GGLHPRGK4IX32TC3XZGW7VANCNFSM6AAAAAAWECKVIU
.
You are receiving this because you commented.Message ID:
@.***>

--
Justin Enjo
+1.619.869.3336 (mobile)

closing: https://docs.hiro.so/stacks/stacks.js/guides/post-conditions


Setup in Window 11 (without WSL)

Set up the project on my local Windows 11 system but encountered issues
I have been setting up this project on my local system running Windows 11. However, I am facing some issues that need to be resolved in order for me to contribute effectively. Can anyone help me resolve these issues?

Hello, can you detail your issues? What are you trying to do? What is the detailed error? What's the logs?

GitHub Codespaces support haas been added: https://codespaces.new/microsoft/call-center-ai?quickstart=1. You can use this environment to code in this automatically configured environment, without using your laptop.

Unable to access this url.


fix(canary-checker): upgrade to v0.38.170

Needed for the RBAC fixes

Blocked by https://github.com/flanksource/canary-checker/issues/646


App icon not showing up on KDE endeavor OS (Arch based) distro.

Describe the bug
The app logo should appear in the app drawer when the application opens.
To Reproduce
Steps to reproduce the behavior:

Run this application with cargo run on a KDE based system
You should see the app logo in the bottom menu bar, but its not showing up for me

Expected behavior
The app logo should appear in the app drawer/menubar
Screenshots

Desktop (please complete the following information):

OS: EndeavorOS
Browser N/A
Version Latest

Additional context
This works on Linux Mint, Windows, and FreeBSD, the logo shows up on all of these.
The code for loading the logo
fn load_icon(path: &str) -> egui::IconData {
  let (icon_rgba, icon_width, icon_height) = {
      let image = image::open(path)
          .expect("Failed to open icon path")
          .into_rgba8();
      let (width, height) = image.dimensions();
      let rgba = image.into_raw();
      (rgba, width, height)
  };

  egui::IconData {
      rgba: icon_rgba,
      width: icon_width,
      height: icon_height,
  }
}

Likely related to https://github.com/emilk/egui/issues/3992 ?

Likely related to #3992 ?

Yes it is indeed, I confirmed by logging into an X11 session and testing my program, and the Icon is visible.  It does seem to be a Weyland problem.  Closing since this is a known problem.


PwdHash Sidebar listed in mobile addon directory

Review on AMO

This doesn't seem to do anything in Mobile Firefox version 54.

Firefox for Android lacks support for sidebars but this extension is still listed there.

Fixed with version 2.1.0 on AMO


Fix typo in example/src/App.jsx

(user) => this.setState({isSignedIn: !!user}
should be
(user) => this.setState({isSignedIn: !!user})
In its current form the example fails to build.

I signed it!

Thanks @natejenkins !


[Feature request] Supporting Vash (expressjs view-engine)

Hello,
I know there is tones of Feature requests, but because I love vscode, I want to this editor support everything !
If is possible please add syntax highlighting and intellisense for .vash files.
Thank you !

Great idea to create the extension.

@MehdiDehghani, I see that the syntax highlighting in the Sublime is outdated and, I think, that I'm able to write his own. You can provide any real file with Vash syntax?

As you know Vash engine offers Razor like syntax, so if you want something official, I think you need to take a look on Razor example in ASP.NET MVC, here is screenshot of a Razor file in VS2015:

The very important feature that you should care about in your extension, is mixing Vash + HTML in .vash files. and intellisense  would be great too.
I'm looking forward to hear about your extension !

@MehdiDehghani,
First, sorry for delay, this is my first tmLanguage file and I need to understand how it works.
I published a preview version of extension to the VS Code marketplace. Now this extension support only syntax highlighting (HTML and JS in @keyword() and @{}) and Emmet (VS Code 1.5+).
About intellisense, please create an issue in the repository with a detailed description of what is meant by this term in the Vash.
https://github.com/mrmlnc/vscode-vash

@mrmlnc, Don't worry, thanks for that, I just checked the preview and looks like you made it !!
I'm sorry, in your post, you mentioned VS Code +1.5, but current version of VS Code is 1.4, that was a mistyping or means I should wait for v1.5 for using the extension? =p

@MehdiDehghani, nope. Just Emmet will work only in version 1.5+. it's related to #9500.


Library with command line arguments always returns 301

I have the following code:
use curl::easy::Easy;
use std::env::args;

fn main() {
    let mut easy = Easy::new();
    let args: Vec<String> = args().collect();
    easy.url(&args[1]).unwrap();
    easy.perform().unwrap();
    println!("{}", easy.response_code().unwrap());
}

but when I run it no matter which website I pass into the command line, it always returns 301 for some reason. Is this an issue or did I do something wrong? Thanks!
UPDATE: I tried changing the code back by commenting out the lines that get command line arguments, and it still returned 301 after that for some reason.

Curl does not follow redirects by default. You'll need to include easy.follow_location(true) to enable it.

But shouldn't websites such as google.com not be saying I need to redirect anyway?

google.com redirects to www.google.com. You can test these things on the command-line with curl -v https://google.com/.

thanks, I was dumb.


code-tunnel still broken on Ubuntu 18.04

          Sorry for the silence, I was on vacation. I will address the tunnel binary dependency this week.

Originally posted by @deepak1556 in https://github.com/microsoft/vscode/issues/181720#issuecomment-1628636628
ubuntu@oracle-vm:~$ code tunnel
/usr/share/code/bin/code-tunnel: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /usr/share/code/bin/code-tunnel)
/usr/share/code/bin/code-tunnel: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /usr/share/code/bin/code-tunnel)

Checked in a few months later and this still seems to be causing issues, unfortunately.

Tracked in https://github.com/microsoft/vscode/issues/192685


Determine if current project is a Quarkus project before adding Quarkus extensions.

Fixes #45
With this PR: https://github.com/redhat-developer/quarkus-ls/pull/205, the projects in the current workspace are being checked if they are Quarkus projects, before the Quarkus: Add extensions to current project command becomes available.
Signed-off-by: David Kwon<EMAIL_ADDRESS>

Works on Windows 10

The microprofile/java/projectLabels command is called whenever the workspace folders are changed (new folder is added or removed from the workspace) and makes the Quarkus: Add extensions to current project command availible accordingly.
If there are no Quarkus projects in the workspace, the command appears in the command palette (Ctrl + Shfit + P). If there are Quarkus projects, the command appears.

In my latest push, per @angelozerr 's suggestion, I am also retrieving project labels when the microprofile/propertiesChanged notification is sent from the MicroProfile ls to vscode-quarkus .
Project labels are only being retrieved when receiving the microprofile/propertiesChanged notification IF the type indicates a dependency change: https://github.com/redhat-developer/quarkus-ls/blob/0ff91b4d0fe4670584a3ad23fe645c8141df7f3d/microprofile.ls/com.redhat.microprofile.ls/src/main/java/com/redhat/microprofile/commons/MicroProfilePropertiesChangeEvent.java#L23
Therefore as a result, if you change your Quarkus project's pom.xml so that it is not longer a Quarkus project, the Quarkus: Add extensions to current Quarkus project command should not appear.
Demo:

Please do not merge this yet, I am quickly editing it so that we can have: https://github.com/redhat-developer/vscode-quarkus/issues/215 in this PR, but with parent folder name instead of project name.

Done:

@xorye everything works very good (with maven and gradle) except for multiple project.
I have the same window than you:

But when I try to select a project, it does nothing. I have not tried to debug it. if you have some information how to debug it, please tell me.

@angelozerr fixed

@xorye works like a charm.


fix well layers rendering artifacts

simplify createNormal and offsetPoints
remove unneeded interpolation from createOffsetCoords()
remove unneeded actualPoints()
improve code for debugging
add esModuleInterop to tsconfig.json to load Vector2 in Jest tests

Now that Vector2 is available in tests we can uncomment some tests from reference-system.test.ts.

Some of the new names used are not very good. IntersectionReferenceSystem::curtainTangent() for instance. But as there will be a refactor with new consistent vocabulary based on what is learned from creating a vocabulary in REP I think we can wait on that process for renaming stuff.


feat(vercel): incremental static generation + swr

🔗 Linked issue

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[x] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Like https://github.com/unjs/nitro/pull/540, this PR adapts the vercel preset to automatically support ISG strategies based on the swr/static route rule.
For example, the following config would create prerender functions for the blog & articles routes. The blog routes would be generated only once and then persisted; the articles routes would be regenerated every 360 seconds.
export default defineNitroConfig({
  routes: {
    '/blog/**': { static: true },
    '/articles/**': { swr: 360 }
  }
})

Here's a deployment using this preset: https://verc-danielroe.vercel.app/
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Hello :wave:
Will this support a way to refresh a static page manually? For example with a  bypassToken?

That is planned, but not part of this PR. (It's a straightforward enhancement, so it should be fairly quick to implement, and I already have a local proof-of-concept.)

We should be good to merge now - @tootallnate fixed the upstream bug and also spotted an issue with a regexp. Sample deployment running with Vercel ISG: https://verc-danielroe.vercel.app.
cc: @pi0

Hi Daniel, sorry to bother you again on this question, but is there a way to refresh a static page manually (on-demand ISR) for a Nuxt project deployed on Vercel ?
I couldn't find anything in the current Nuxt documentation 😕
Thanks again !

This isn't yet implemented but will be 😊

OK, thanks ! Is there some public road map or an issue I could follow to be alerted when this is implemented ?


Update tfjs-core to 0.12.8 and add new ops

Update tfjs-core to 0.12.8 and add new ops.

This change is

This should fix https://github.com/tensorflow/tfjs/issues/560


Upgrade ASM from 1.4 to 1.6+

We are currently using ASM 1.4. Docs currently recommend 1.6.
https://cloud.google.com/service-mesh/docs/gke-install-asm
I don't think 1.4 is still supported.
kubeflow/kubeflow#5313 is tracking ISTIO 1.6 in Kubeflow

Agree, added to https://github.com/kubeflow/gcp-blueprints/issues/139.
We need to confirm the CRDs we are relying on, like Istio RBAC are still supported on 1.6.

I think I didn't realize how important this is, the fact that ASM 1.4 is no longer supported make this a high priority for us to migrate.

Documentation to refer:
https://cloud.google.com/service-mesh/docs/scripted-install/asm-onboarding
https://cloud.google.com/service-mesh/docs/enable-optional-features

Official doc to refer: https://istio.io/latest/docs/concepts/what-is-istio/

/assign @zijianjoy

Latest istioctl-asm download page: http://cloud/service-mesh/docs/downloading-istioctl#mac-os

Attempted to run make apply directly after upgrading istioctl-asm. See the following error for command:
command:
istioctl manifest generate -f $(MANIFESTS_DIR)/gcp/v2/asm/istio-operator.yaml -o $(BUILD_DIR)/istio
error:
#************************************************************************************
# hydrate asm
istioctl manifest generate -f ./upstream/manifests/gcp/v2/asm/istio-operator.yaml -o .build/istio
Error: validation errors (use --force to override):
unknown field "env" in v1alpha1.ProxyConfig
make: *** [hydrate-asm] Error 1

Exploring applying https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages/blob/master/asm/istio/istio-operator.yaml

Making changes in Makefile to simulate manual steps in https://cloud.google.com/service-mesh/docs/scripted-install/gke-install.
Currently facing issues:

sni_hosts are not recognized because validation has been enforced on this field. Changing them to sniHosts in kf-istio-resources.html fixes the issue.

There is no match for ClusterRbacConfig in "rbac.istio.io/v1alpha1", because it has been deprecated. Reading https://istio.io/latest/blog/2019/v1beta1-authorization-policy/ to learn more.

Need to follow up with csm lifecycle team about how to maintain ASM revision namespace label because its version can get deprecated easily.

We also need to document the steps to upgrade ASM if user wants to.

@zijianjoy If Kubeflow 1.3 uses ASM1.9, it would be better if 1.9.3-asm.2 or higher is used by default. This is because a security issue, ISTIO-SECURITY-2021-003, was recently resolved in version 1.9.3-asm.2. Please refer to the Release Note here.

@zijianjoy Okay, when the document PR is created, I'll try it. Thanks !

Thank you so much @rky0930!

@rky0930 Hello Gyoung-yoon, we have released Kubeflow 1.3 on Google Cloud and you can refer to https://www.kubeflow.org/docs/distributions/gke/deploy/overview/ for the installation.
As part of this release, I have upgraded ASM to the latest available version v1.9.3-2. So the security issue mentioned by you should be covered. For future ASM release, you can refer to https://www.kubeflow.org/docs/distributions/gke/deploy/upgrade/#upgrade-asm-anthos-service-mesh to upgrade ASM in your Kubeflow cluster. Feedback on the deployment and upgrade processes are welcomed!


Added an implementation of lazy_static without std in stable Rust

Currently, lazy static has an implementation for no_std crates which requires nightly. I have added a new implementation of lazy_static which works on stable Rust.
Question: I have added a new feature and a new implementation. Should we keep it as a new implementation or should we overwrite nightly spin implementation?

Use
Okay. I confess this is not something I need. I don't want to be redundant, but imagine you are writing a Kernel and you do not want to have to use nightly but need to initialize some... lazy static. I mean, you would have to introduce some instability by using nightly.
Some differences
I think the main important is: I did not wrote some generic API shared between all static variables. I wrote inside the __lazy_static_create a specific type for that static. This removes the need of having a const fn.
Another difference is: spin's implementation does not store a T. It stores an Option<T>. I think there is a little overhead on checking Option<T> every time the static is accessed. My implementation used a trick in order not to have this overhead. I used core::mem::size_of to make a byte array with the size of T. I have also used a zero-sized array of T to force alignment.
However, the spinning over the initialization status works in the same way as spin's implementation of Once. I thought they used a Mutex to write Once, but it is more like a RwLock (just like I did). Not sure why the Mutex was in my head, maybe it was like that one day.
I do recognize there is not too much difference. The real reason I implemented this is so we can have a stable API with no_std. Importing it from another crate does not allow us avoiding const fn.
NOTE: the size_of trick only works on non-generic types. This is the one of the reasons I wrote a specific type for each static.

Well, there is another option. I was thinking: spin could expose Once::<T>::INIT. This would allow lazy_static to use it on stable.

I have merged a PR on spin which allows Once to be initialized via constant on stable Rust. This custom implementation of lazy_static is not needed anymore. We may simply rewrite the spin version.

Thanks for chasing this up @brunoczim! A no-std spin-based implementation that also works on stable sounds great to me :+1:

@brunoczim now that

@brunoczim now that https://github.com/mvdnes/spin-rs/pull/55 is merged and released on crates.io would you be interested in refactoring our existing no_std impl to work on stable Rust using spin?

Yes I am. Count me in.

I am closing this in favor of #130


Server not responding when using TC

BkCommonLib version: Build #561
TrainCarts version: Build #471
Paper version: Paper-68 (1.14.2)

Problem or bug: Console spams this error and stops server from responding
https://pastebin.com/FpBs8jvR

Signlink doesnt work with 1.14 yet. There's many problems of chunks being loaded from inside a chunk load event freezing the server. See: https://hub.spigotmc.org/jira/browse/SPIGOT-5032

1.14.4 will fix this issue, as well as using the latest builds of signlink


notebook 7.1.1

Hi! This is the friendly automated conda-forge-webservice.
I've started a version update as instructed in #147.
I'm currently searching for new versions and will update this PR shortly if I find one! Thank you for waiting!
Fixes #147

Waiting until it settles, but needs:
jupyterlab>=4.1.1,<4.2


Search is case sensitive

Search is case sensitive. When we search for EBiSC we have to be specific with case.

it seems the search function is not working, (not only cases).
searching with "BridgeDb" returns 0 results

Search is using labels for search. Since we are using RDF to search, I will look how we can search without case in RDF.

Label search is not case sensitive anymore.


Chain promises when handling comm_open

Fixes ipython/ipywidgets#561

Other part of fix: https://github.com/ipython/ipywidgets/pull/594

Thanks for fixing this @jhpedemonte .

Thanks!

Released as v0.10.2.


[Bug]: undefined reference to `absl::lts_20211102::

Describe the issue
Hi, I have built abseil from source, but when I compile other projects using absl, I got a lot undefined reference to absl::lts_20211102:: .....` errors.
git clone https://github.com/abseil/abseil-cpp.git --recursive
cd abseil-cpp
git checkout 20211102.0
git submodule update --init --recursive
mkdir build && cd build
cmake -DCMAKE_CXX_STANDARD=17 -DABSL_CXX_STANDARD=17 -DABSL_USE_GOOGLETEST_HEAD=ON -DCMAKE_MODULE_LINKER_FLAGS=\"-Wl,--no-undefined -Wl,--no-undefined\" -DCMAKE_INSTALL_PREFIX=$PWD/install -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE -DBUILD_SHARED_LIBS=ON -DNDEBUG=1 ..
make -j
make -j install

I notice that after I built it, for example, there is a
absl::variant_internal::ThrowBadVariantAccess()

in the file, but is there any way we can set the namespace to be as defined in /mydir/abseil-cpp/absl/base/options.h, Line 208~209:
#define ABSL_OPTION_USE_INLINE_NAMESPACE 1
#define ABSL_OPTION_INLINE_NAMESPACE_NAME lts_20211102

As when compiling my other project, it always raises the error like this:
../libtritonserver.so: undefined reference to `absl::lts_20211102::variant_internal::ThrowBadVariantAccess()'

Steps to reproduce the problem
As listed above
What version of Abseil are you using?
20211102.0, but I have also tried multiple other versions
What operating system and version are you using?
RHEL 8
What compiler and version are you using?
gcc 8.5
What build system are you using?
cmake 3.26
Additional context
No response

I think this is unlikely to be an Abseil bug and probably has nothing to do with the namespace. It's more likely that your build command is missing linker inputs. You need to provide instructions to build your whole project for us to look into this.

Hi, @derekmauro ,
thanks for the reply.
Sure, so my project does not directly use Absl, but instead, it has dependencies on GRPC, GoogleTest, and Google-cloud-cpp. After building absl, I also built them using the following command:
For GRPC:
export absl_DIR=/mydir/abseil-cpp/build/install/lib64/cmake/absl
git clone --recurse-submodules -b v1.48.0 https://github.com/grpc/grpc.git
cd grpc
mkdir build && cd build
cmake -DCMAKE_CXX_STANDARD=17 -DgRPC_INSTALL=ON -DgRPC_BUILD_TESTS=OFF -DCMAKE_INSTALL_PREFIX=$PWD/install -DCMAKE_PREFIX_PATH=/mydir/abseil-cpp/build/install ..
make -j
make -j install

For GoogleTest,
export absl_DIR=/mydir/abseil-cpp/build/install/lib64/cmake/absl
git clone https://github.com/google/googletest.git
cd googletest
git checkout v1.8.x
git submodule update --init --recursive
mkdir build
cd build
cmake -DCMAKE_CXX_STANDARD=17 -DCMAKE_INSTALL_PREFIX=$PWD/install -DCMAKE_CXX_FLAGS="-lboost_regex" -DCMAKE_PREFIX_PATH="/mydir/boost_1_78_0/install" ..
make -j
make -j install

For google-cloud-cpp,
git clone https://github.com/googleapis/google-cloud-cpp.git --recurse-submodules
cd google-cloud-cpp
git checkout v2.8.0
git submodule update --init --recursive
mkdir build && cd build
cmake -DCMAKE_CXX_STANDARD=17 DCMAKE_PREFIX_PATH=/mydir/abseil-cpp/build/install -DgRPC_ROOT=/mydir/grpc/build/install -DGTest_ROOT=/mydir/googletest/build/install -DGMOCK_ROOT=/mydir/googletest/build/install -DCMAKE_POSITION_INDEPENDENT_CODE=TRUE ..
make -j
make -j install

And finally, when compiling my project, I pass googletest, grpc, google-cloud-cpp dir to CMAKE_PREFIX_PATH.

Hey @YJHMITWEB did you managed to solve your problem ?


create arm64 image tag

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to 0dns?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation Update
[ ] Other (Please describe):

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

also change the runner to arc-runner

i tried already but on arc-runner it is failing let me check the issue


Ensure version files are created at same path as store

Addresses #99
I did not have the time yet to verify the result. However, these changes should pretty much ensure that the version file will always be created at the same location as the store itself, having the ".version" suffix.
Therefore, if the targeted directory is write-accessable on android, there shall be no more errors during the creation of such versioned stores.

Hi @JanTie Thanks for the contribution!
Little curious as to how this failed to create the version file before this patch. Could you share how the store was created?

Hi @JanTie Thanks for the detailed explanation. It does make sense why it would fail in some scenarios. However, I'm unsure how the change to Path.name from Path.toString() could help this use case.
Perhaps a better way to handle this would be to let the codec manage the version file instead, so that it can create this file wherever it needs to go.
For example, something like
public class VersionedCodec<T: @Serializable Any>(
  private val file: Path,
  private val version: Int = 0,
  private val json: Json,
  private val serializer: KSerializer<T>,
  private val migration: Migration<T>,
  private val versionFile: Path = "$$file.version".toPath() // TODO: Save to file metadata instead
): Codec<T> { .. }

Any thoughts with this approach?

I added your feedback. I also provided the exact same default in the storeOf function so it can actually be set from the caller side if needed.
I just had to change the $$file to just $file. Otherwise we would run into the exact same issues as before, because the first Dollar sign would not be escaped/replaced.
PS: Sry for minor reformats, i guess my autoformat kicked in. We may want to use some sort of code formatting tool at some point.

Hi @JanTie Can we also update the API? you can do this by running ./gradlew apiDump

updated the api


Not working anymore?

Hello i've got server time out message on all domains :(

Yep, same issue for me too. :(

The issue comes from the PHP version. Works fine with PHP 7.0 and 7.1.
Fails everywhere due to deprecated PHP functions in a bundled library:
PHP message: PHP Deprecated:  array_key_exists(): Using array_key_exists() on objects is deprecated. Use isset() or property_exists() instead in /www/xxx/xxxx/vendor/jeremykendall/php-domain-parser/src/Pdp/Parser.php on line 166
Looks like the library is still maintained https://github.com/jeremykendall/php-domain-parser so probably merging them and a couple of tweaks should do the job. If time allows I will fork and try.


Homepage does not work

When I click on the homepage here: https://rubygems.org/gems/extralite - it takes me to https://digital-fabric.github.io/extralite/ that is a 404

Fixed in v0.2.1. Thanks for reporting!


App views

Steps taken to complete this milestone

Created the _user partial and the user index page
Added functionality to show one user and their details
Created the post index page
Added functionality for the posts show view page
Setup sass for styling
Included the link_to functionality to show one user
Styled the individual pages

Screenshots

Thanks @emmanuellekamwa


Google Maps SDK pod fails to compile every time

Hello,
I have been trying to compile google maps iOS SDK for a few months now with no clear solutions or answers.
Setup:
Gemfile:
source 'https://rubygems.org'

gem 'rake'
gem 'cocoapods'
gem 'motion-cocoapods'

Pods:
app.pods do
    pod 'GoogleMaps'
end

The latest version of Google Maps SDK is 1.10.5.
Mac OS X: 10.10.5
RubyMotion: 4.4 (paid license, been using it since v2 and I love it)
iOS 9.1 SDK
When I run rake, the result I get is the following:
Installing GoogleMaps (1.10.5)
Generating Pods project
Pod installation complete! There is 1 dependency from the Podfile and 1 total pod installed.
username$ rake
     Build ./build/iPhoneSimulator-8.0-Development
     Build ./Pods.xcodeproj [Pods - Release]
   Compile ./Target Support Files/Pods/Pods-dummy.m
   Compile ./Target Support Files/Pods/Pods-dummy.m
      Link ./Users/username/Desktop/my_maps/vendor/build/Pods.build/Release-iphonesimulator/Pods.build/Objects-normal/i386/libPods.a
      Link ./Users/username/Desktop/my_maps/vendor/build/Pods.build/Release-iphonesimulator/Pods.build/Objects-normal/x86_64/libPods.a
    ERROR! Building vendor project `vendor/Pods' failed to create at least one `.a' library.

This is the case if GoogleMaps is the only pod in Rakefile.
If I add another pod, e.g.:
app.pods do
    pod 'GoogleMaps'
    pod 'MBProgressHUD'
end

The other pod does compile fine, but then I get a different error:
...
...
duplicate symbol __ZN7gmscore8renderer15GLScopedContextD1Ev in:
    ./vendor/Pods/GoogleMaps/Frameworks/GoogleMaps.framework/GoogleMaps(GLScopedContext.o)
duplicate symbol __ZN7gmscore8renderer15GLScopedContextD2Ev in:
    ./vendor/Pods/GoogleMaps/Frameworks/GoogleMaps.framework/GoogleMaps(GLScopedContext.o)
ld: 706 duplicate symbols for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
rake aborted!
Command failed with status (1): [/Applications/Xcode.app/Contents/Developer...]
/Library/RubyMotion/lib/motion/project/builder.rb:357:in `build'
/Library/RubyMotion/lib/motion/project/app.rb:78:in `build'
/Library/RubyMotion/lib/motion/project/template/ios.rb:68:in `block (2 levels) in <top (required)>'
/Library/RubyMotion/lib/motion/project/template/ios.rb:186:in `block in <top (required)>'
Tasks: TOP => build:simulator
(See full trace by running task with --trace)

Running the command again with --trace, I get:
...
...
duplicate symbol __ZN7gmscore8renderer15GLScopedContextD2Ev in:
    ./vendor/Pods/GoogleMaps/Frameworks/GoogleMaps.framework/GoogleMaps(GLScopedContext.o)
ld: 706 duplicate symbols for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
rake aborted!
Command failed with status (1): [/Applications/Xcode.app/Contents/Developer...]
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/file_utils.rb:66:in `block in create_shell_runner'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/file_utils.rb:57:in `call'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/file_utils.rb:57:in `sh'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/file_utils_ext.rb:37:in `sh'
/Library/RubyMotion/lib/motion/project/builder.rb:357:in `build'
/Library/RubyMotion/lib/motion/project/app.rb:78:in `build'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/motion-cocoapods-1.7.4/lib/motion/project/cocoapods.rb:53:in `build_with_cocoapods'
/Library/RubyMotion/lib/motion/project/template/ios.rb:68:in `block (2 levels) in <top (required)>'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:240:in `call'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:240:in `block in execute'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:235:in `each'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:235:in `execute'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:179:in `block in invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:165:in `invoke'
/Library/RubyMotion/lib/motion/project/template/ios.rb:186:in `block in <top (required)>'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:240:in `call'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:240:in `block in execute'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:235:in `each'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:235:in `execute'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:179:in `block in invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:201:in `block in invoke_prerequisites'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:199:in `each'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:199:in `invoke_prerequisites'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:178:in `block in invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/task.rb:165:in `invoke'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:150:in `invoke_task'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:106:in `block (2 levels) in top_level'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:106:in `each'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:106:in `block in top_level'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:115:in `run_with_threads'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:100:in `top_level'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:78:in `block in run'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:176:in `standard_exception_handling'
/Users/username/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rake/application.rb:75:in `run'
/Users/username/.rbenv/versions/2.2.3/bin/rake:33:in `<main>'
Tasks: TOP => build:simulator
username$

I really tried everything I came across but nothing fixed this problem.
I also used GoogleMaps version 1.9.2 a few months ago and it worked (compiled fine) but I remember it gave me tons of errors when submitting to iTunesConnect that I gave up on it later.
I am currently building the app using Xcode and Objective-C with no problems, but I am willing to move the code to RubyMotion as soon as I find a working solution (or even a workaround).
I hope I included all necessary information for this issue.
I love RubyMotion so much and thank you guys for all the hard work you're doing.

I found hipbyte/motion-cocoapods#124 which was created 3 days ago and might be the solution to this problem.


[WIP]: Update Conda package requirements

Removing  Panoptes
rio-mbtiles needs update

Waiting on https://github.com/mapbox/rio-mbtiles/pull/83.  Shapely and numpy fail to install.

Replaced by #161


PHP 8.2 deprecated creation of dynamic property

I surprisingly get Deprecated: Creation of dynamic property React\MySQL\Commands\QueryCommand::$resultFields is deprecated warning in this specific line of code in 5.7 version
https://github.com/friends-of-reactphp/mysql/blob/c36b92f1ede95f49036b6ba1805736f80fa4d4e0/src/Io/Parser.php#L340

This belongs to #161 issue

Hey @hasanparasteh, this has been fixed in #170 and is currently part of the v0.6.0 milestone which is not released yet. You can either check out the current development branch (0.6.x) in order to make use of our recent changes, or wait for the upcoming releases.
To give you some more insights, we're planning to work towards the release of  v0.6.0, which will involve some API refactoring and other changes. With this in mind and all the other stuff we're currently working on, it might take a while before we get to release this version, but I don't want to push a release too far into the future. Maybe it makes sense to release a v0.5.8 before the bigger release, WDYT?

I see. Because there'd be breaking changes in the future and people may want to stick with 5.x version for a while (it takes time to fully upgrade all services to new API), it makes sense to release a new version with the latest patches.
This way, people have 100% compatibility with PHP 8.2, and it's an End Of Life release which means there's no more 5.x version in the future and everybody should upgrade.
I think it's good practice to approach future breaking changes like this.

I see. Because there'd be breaking changes in the future and people may want to stick with 5.x version for a while (it takes time to fully upgrade all services to new API), it makes sense to release a new version with the latest patches.

There's already one BC-break merged (#165) that we're going to introduce in v0.6.0, but we're always trying to make these major switches between (major) versions as comfortable as possible.
Releasing a v0.5.8 will also be a temporary solution before v0.6.0 is going to be released. We may also want to invest the time in releasing v0.6.0 without an additional release before that. I have to run this through the team and see what approach makes the most sense.
I think the original question in here is answered, so I'll close this ticket :+1:


Crash on pbr_opaque_mesh_pipeline with opengl backend

Bevy version
bevy = "0.10.0" also tried the (3d_scene) example with 0918b30e2925b2ce628d3e89f6e120e68c61a06c.
Relevant system information

cargo 1.67.0 (8ecd4f20a 2023-01-10)
os: "Linux 22.0.4 Manjaro Linux", kernel: "5.15.94-1-MANJARO"

`AdapterInfo { name: "AMD BARTS (DRM 2.50.0 / 5.15.94-1-MANJARO, LLVM 15.0.7)", vendor: 0, device: 0, device_type: Other, driver: "", driver_info: "", backend: Gl }`

What I did
So far I was able to use bevy for some 2d-setups. But when I try to run a 3d example  I am constantly running into the same errors.
I tried to run the  3d_scene example locally with bevy = "0.10.0" in my Cargo.toml and I also tried running the same example in the repo's example folder. The results are always the same.
This might be related to #841 see this comment.
What went wrong
This is the output I get before the app crashes:

2023-03-13T16:37:07.490477Z  INFO bevy_render::renderer: AdapterInfo { name: "AMD BARTS (DRM 2.50.0 / 5.15.94-1-MANJARO, LLVM 15.0.7)", vendor: 0, device: 0, device_type: Other, driver: "", driver_info: "", backend: Gl }
2023-03-13T16:37:08.396321Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Linux 22.0.4 Manjaro Linux", kernel: "5.15.94-1-MANJARO", cpu: "Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz", core_count: "2", memory: "7.7 GiB" }
2023-03-13T16:37:08.634536Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 2 : GL_INVALID_ENUM in glTexStorage2DMultisample(target=GL_TEXTURE_2D)
2023-03-13T16:37:08.634845Z ERROR wgpu_hal::gles::egl: GLES: [API/Error] ID 2 : GL_INVALID_ENUM in glTexStorage2DMultisample(target=GL_TEXTURE_2D)
2023-03-13T16:37:09.024041Z ERROR wgpu::backend::direct: Shader translation error for stage FRAGMENT: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias
2023-03-13T16:37:09.024083Z ERROR wgpu::backend::direct: Please report it to https://github.com/gfx-rs/naga
2023-03-13T16:37:09.024150Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (0)' panicked at 'wgpu error: Validation Error
Caused by:
In Device::create_render_pipeline
note: label = pbr_opaque_mesh_pipeline
Internal error in FRAGMENT shader: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias

I faced the same issue, this is likely related to https://github.com/gfx-rs/naga/issues/1619 but the comments on that naga bug are a bit confusing.

I can reproduce this running
WGPU_BACKEND=gl cargo run --example 3d_scene

On the linked commit and current main (a4323d5)


Add manifest support

The idea here is to extract the manifest conversion from the manifest loading. The manifest will first be converted, the converted version saved and then the converted one actually applied.
The major thing missing from this right now is the writing back of manifests when things are changed in the UI but the infrastructure is there to preserve comments and formatting.
procfile
t0: /home/ben/Programming/exo/bin/tick

exo: "0.1"
components:
  - name: t0
    type: process
    spec:
        program: /home/ben/Programming/exo/bin/tick
        environment:
            PORT: "5000"

docker-compose
services:
  t0:
    image: bash
    command: "sleep infinity"
    env_file: my-env

exo: "0.1"
components:
  - name: default
    type: network
    spec:
        driver: bridge
        name: tmpMQvlHcwsZ4_default
  - name: t0
    type: container
    spec:
        command: sleep infinity
        container_name: tmpMQvlHcwsZ4_t0_1
        env_file: my-env
        image: bash
        labels:
            com.docker.compose.project: tmpMQvlHcwsZ4
            com.docker.compose.service: t0
        networks:
            tmpMQvlHcwsZ4_default:
                network: tmpMQvlHcwsZ4_default
    depends_on:
      - default

Reverted merging master since it's currently broken for me.

Going to close this because it's pretty far out of date now & I'm on a massive refactor journey that will eventually culminate in a new manifest format.


validateParameters raises warning when nextflow schema contains nested parameters

This issue is likely tied to the others involving nested parameters but it is worth documenting. If a nextflow_schema.json file contains a group of nested parameters you will get a warning involving access to undefined parameters even if those parameters are initialized.

A minimal example of this issue can be found here: https://github.com/mattheww95/bug_report

Hi @mattheww95
Thanks for reporting this! Nested parameters currently are not supported by the plugin. We plan on adding this in the future though.


parse more complex interface type constraints

Here is an example of code that should parse:
package Foo

type MyConstraint interface {
	[]*MyStruct | []MyInterface
}

This currently works though:
package Foo

type MyConstraint interface {
	MyStruct | MyInterface
}

I think the interface_body tree-sitter rule need to be adjusted.
See the spec here: https://go.dev/ref/spec#InterfaceType

Interface type has been simplified and generalized actually.
The grammar should actually become smaller after fixing this bug.

this doesnt work either
package Foo

import "bar"

type MyConstraint interface {
	bar.MyStruct | bar.MyInterface
}


close #186: Remove redundant _SHOW variables

This commit removes all _SHOW variables for showing/hiding segments. Now Hg/Mercurial completely disappears  - should I also remove (now empty) variable table from README?
Two remaining SHOWs are:

BULLETTRAIN_STATUS_EXIT_SHOW - we may consider changing this from boolean into enum, as described in #179.
BULLETTRAIN_DIR_CONTEXT_SHOW

What about default BULLETTRAIN_PROMPT_ORDER variable? Should I change it to conform default _SHOWs? Or, as this is anyway quite invasive change, we can leave it by?
Any suggestions are welcome :smile:

Is this fine? What do you think?

I like it.
Makes the code simpler.
@vadviktor Thoughts about this?

This is a must have refactor. I for one found myself using only the ordering array to switch on/off features. Great PR!

Great, merging.

Looks like we have a new major release with this 🎉


Remove legacy setup.py

This PR removes the legacy setup.py and replaces it entirely using the standard pyproject.toml. As in the Python packaging tutorial, it uses hatchling as the build backend.

LGTM


Tutorial has some steps missing

In order to get the tutorial working, I had to make the following changes (Visual Studio 16.6.2 / .NET Core 3.1.301):

Index.cshtml
For the Html.ActionLinks (Edit, Details, Delete), I had the change "new { /* id=item.PrimaryKey */ }" to new { id = item.Id }"
Note: after creating the "Index" view, there is the following text:
"Once done, Visual Studio opens the cshtml file that it creates. You can close that file in Visual Studio. We'll come back to it later."
I suspect that there was an intention to come back to update the key later, and this step was missed.
Add a "Details" view
This step was not specified when creating the views.
2a. Details.cshtml
For the Html.ActionLink (Edit), I had to change "new { /* id = Model.PrimaryKey */" to "new {  id = Model.Id }"
Add a "Delete" view
This step was not specified when creating the views.
ItemController.cs
The "using.Models" statement should be "using todo.Models"

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

ID: c8d9b842-de22-59e7-e36a-662e2060ae7a
Version Independent ID: bda934c5-a268-721f-1a3e-1f73fc25c15f
Content: ASP.NET Core MVC web app tutorial using Azure Cosmos DB
Content Source: articles/cosmos-db/sql-api-dotnet-application.md
Service: cosmos-db
Sub-service: cosmosdb-sql
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@jeremybytes Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@jeremybytes thanks for pointing out the issues. Sorry for the long delay, I added the missing views and their code. The changes will be live tomorrow. We will now close this issue.
#please-close


⚠ ClamAV has degraded performance

In 3984680, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 203 ms

Resolved: ClamAV performance has improved in 54d1737.


SfM reconstruction failed

Hi
I try the latest docker image and run the pipeline_SfM.ipynb.
Everything looks good until reconstruction step. I only use 30 image for reproducing reconstruction error.
Here is error message

Thanks for your time!

Thanks for reporting this! I just pushed to master a fix that prevents crashing when the reconstruction fails. This however does not explain why it fails. Can you share the colmap logs printed in the Jupyter console?

I think there are no matches found.
I ran docker without any GPU support. The script seems to use GPU for matching.
Is it possible to reconstruct the model with only CPU support on docker?

Thanks for quick reply

Could you please post the full log, including the match importer? It is possible that the match importer is silently failing because of the lack of GPU. Could you please add the flag --SiftMatching.use_gpu 0 to the geometric verification in triangulation.py? See issue https://github.com/cvg/Hierarchical-Localization/issues/65 for reference.


DTSPO-17071 - remove use of PAT token

Jira link (if applicable)
Change description
Checklist

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)
[ ] Does this PR introduce a breaking change

we would not be able to update PAT token to Service Principal, documented here - https://github.com/hmcts/azure-enterprise?tab=readme-ov-file#known-issues


RSDK-3956 - update buf plugin

This isn't actually ready to be merged, trying to figure out why the buf auto-generate is refusing to generate the generic component API code (and whether this matters)

Ok, now it's ready


Updated Icons for Workflows

Is your request related to a problem? Please describe.
Workflows currently have a very limited subset of icons that can be set.
Describe the solution you'd like
Introduced better icons for Workflows from Carbon with a greater range and description of what they mean. Similar to the clear distinctions for Tasks.
Describe the benefits or justification for this request
A clear and concise list of benefits for this change
Additional context
Add any other context or screenshots about the feature request here.

Hey @LucasGrimauth what new icons did we choose? can you take a screenshot? how are the icon names linked i.e. did we just add additional? did we deprecate any and if we did, what will workflows that referenced that icon use?

Hey @tlawrie it looks like Lucas did not deprecate any Icons, but did add a good bit more from Carbon. It looks good to me so I am going to merge in.

@BenjaminRuby is making an update to the default icon choice to be the Bot... once that is up we can mark this item as verified


[ASCII-2222] Fix serverless log level logic

What does this PR do?

Fix logger initialization in serverless agent when using lowercase level strings (eg. "debug").
Motivation

Have the logger and log level working as expected.
Additional Notes

Was broken by https://github.com/DataDog/datadog-agent/pull/27547 which introduces automatically updating the log level when the configuration is updated.
The issue here is that the serverless agent forced the initialization to error, and then updated the log level to its actual value.
It means that when the actual value was the same, there was no change, and so the logger was not updated.
Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Tested manually with "debug", "DEBUG", and "Debug", running in a Linux container (not even the lambda emulator).
I'd rather have someone from serverless making sure it works as expected in AWS too, both without specifying the variable and with specific values.

/merge

/merge -c

/merge


Generate SBOMs for .NET components

We have SBOMs currently for Java and Go. We could use them here as well. I recommend this utility: https://github.com/marketplace/actions/cyclonedx-net-generate-sbom (we're using the clyclonedx format elsewhere and it's popular).
Definition of done:

SBOMs generated and attached to release artifact in GH, or otherwise made publicly available (for every release)
only includes dependencies of module in question (not of repo)

I'll take a stab at this.


Remove bootloader config overrides for JACDAC on pybadge/gamer

This PR removes config overrides for the JACDAC pin on pybadge and pygamer.
The reason for the original override is that the current hardware layout for PA23 (D13), used for JACDAC communications, has an LED that causes a voltage drop bringing the idle state of the line to ~1.6v:

(top trace shows digital equivalent of bottom analog trace)
As the microcontroller does not register 1.6v as a logical one, it is not a valid idle condition in JACDAC. Instead, we defined PA23 to be used as the COMM_LED for JACDAC, and PA04 (A4) to be used for JACDAC comms as PA04 does not have any additional hardware components that causes a drop in voltage.

@mmoskal


boto3-stubs[iam,sts] from 1.24.24 to 1.24.43 upgrade breaking boto3 Session import

Describe the bug
In my poetry.lock before upgrade boto3-stubs[iam,sts] was set to 1.24.24 and project was working fine, after upgrade to 1.24.43 I started receiving following error from mypy
error: Module "boto3"
has no attribute "Session"; maybe "session"?
    from boto3 import Session
    ^

To Reproduce
Steps to reproduce the behavior:

Install<EMAIL_ADDRESS>Run mypy/pyright on the following code sample

from boto3 import Session

...

Actual output
error: Module "boto3"
has no attribute "Session"; maybe "session"?
    from boto3 import Session
    ^

Expected output
Success
Additional context
Your OS, boto3-stubs installation method, boto3 version, etc.

Thank you for the report!
Fixed in boto3-stubs 1.24.43.post1. Please let me know if it works for you as it should.

I have the same issue.
Seems 1.24.43.post1 (and also 1.24.44) fixes boto3.Session, but not for boto3.session.Session,
which is described in boto3 docs:
import boto3

# OK
session = boto3.Session()

# NG
# (module) session
# "session" is not a known member of module Pylance(reportGeneralTypeIssues)
session2 = boto3.session.Session()

Well, this is not the best way to use imported module. I will take a look if I can type this correctly.

Fixed, should be included in boto3-stubs 1.24.45 once it is out. Please check and let me know if it works as intended.

@sarisa boto3-stubs 1.24.45 is out. Please check.

@vemel checked 1.24.45 and boto3.session.Session is now working again.
Thank you for fixing the issue quickly!

@vemel sorry for bothering you again, but I'm just curious,
in commit https://github.com/youtype/mypy_boto3_builder/commit/68feda6629d6d80306452abe91cc373270797351,
why changing import boto3.session as session to from boto3 import session as session
fixes this kind of errors?
Is this a behaviour defined in somewhere in PEP, or is this just the implementation-specific
behaviour of pyright / pylance?

I am not sure to be honest. But pyright looks happy with the second option. Maybe it makes sense to create a question/bug report in pyright repo.

OK, this seems really odd to me, so I'll raise an issue to Pyright later.
Thank you for maintaining this amazing project!