Errors with gcc-5.2.0 wide-int.h when compiling esp32 toolchain (crosstool-NG) - tried multiple host (IDFGH-278)

See https://github.com/jcmvbkbc/crosstool-NG/issues/55
I am running Manjaro (Arch) Linux with 4.18.0-1 kernel. I tried setting my environment vars and ./configure to use gcc, g++, and cpp 8.1.1+20180531-1 and 7.3.1+20180406-2 and with both I got the same errors mentioned here. I also tried 5.4.1-1 but got a different error, I didn't save the logs in that case.
The 8.1.1 and 7.3.1 errors occur during the pass 2 core C gcc compile step. They all seem to be with the wide-int.h header file for gcc-5.2.0. Errors include, but are not limited to:
error: too many template-parameter-lists
error: invalid use of incomplete type 'struct wi::int_traits<generic_wide_int >'
error: no type named 'result_type' in 'struct wi::unary_traits<generic_wide_int<wide_int_storage> >'
error: incomplete type 'wi::int_traits<generic_wide_int<trailing_wide_int_storage> >' used in nested name specifier
...and other similar errors.
I turned debug logging on with verbosity at the highest possible level - the build.log is attached in a .zip file. It expands to just over 10MB.  This is from host gcc version 7.3.1.
esp32-crosstoolng-build-debugenabled.zip
Please let me know if any more information is required or if this is better a fit for the jcmvbkbc repo.  Thanks.

Hi @jasonc0, at the moment we use Debian Jessie (when building toolchains for Linux), and Debian Stretch (when building toolchains for Mac/Windows). Such old version is used to allow folks who have older glibc versions to run resulting binaries (e.g. https://github.com/espressif/arduino-esp32/issues/950).
I suspect that our version of crosstool-NG is missing some patches to allow GCC 5.2 to be built on more recent host GCC versions. We are in the process of switching to crosstool-NG master branch, and also switching to a more recent GCC version for the target. Once that is done, i think you will be able to build the toolchain using host GCC 7.3. In the meantime, you may use an older version of host GCC (e.g. via docker).

Hi @jasonc0 and @igrr , I'm facing the same trouble too, always I try to build the ct-ng file, it shows to me a ERROR 2.
Here is my build.log.
I'm using:
LSB Version:	n/a
Distributor ID:	 ManjaroLinux
Description:	 Manjaro Linux
Release:	         17.1.11
Codename:	Hakoila`
And GCC:
gcc (GCC) 8.1.1 20180531
I installed Manjaro recently, so I don't have the GCC 7.3 package, and when I use the ./ct-ng build CC=gcc-7.3 CXX=gcc-7.3 command, it fails in the ncurses step. That is the folowing build.log of this error.
What can I do to build it without error?

You might be able to get a little further by installing ncurses 5 from AUR but it sounds like you'll then get the same error as myself.  Perhaps try building with crosstool in an Ubuntu vm or with docker as suggested.  Personally I just downloaded the precompiled tarball from espressif.  I can't stand Ubuntu or Debian personally, they take "stable" too far and so every package is 5 versions old...

I had the same problem compiling with gcc 8.1.1 under arch linux. I found a workaround that let me compile and install the esp32 toolchain (i'm not sure if it works properly, needs some tests). The problem/solution was explained here :
https://stackoverflow.com/questions/3595859/too-many-template-parameter-lists-error-when-specializing-a-member-function
There are several consecutive template definitions in wide-int.h that should be adapted as described in stackoverflow. Just removed the consecutive "template<> template<....>" definitions and the error disappeared. I'll test the toolchain in the following days, but i believe that it should work.

I also use Arch Linux (Manjaro) with gcc 8.1.1 and experienced the same problems building the toolchain as follows:
Download crosstool-NG and build it:
cd ~/esp # OK
git clone -b xtensa-1.22.x https://github.com/espressif/crosstool-NG.git # OK
cd crosstool-NG # OK
./bootstrap && ./configure --enable-local && make install # OK
Build the toolchain:
./ct-ng xtensa-esp32-elf # OK
./ct-ng build # ERROR - Build fails at this point (see below build fail output messages)
chmod -R u+w builds/xtensa-esp32-elf # This point is never reached
On my system, there are 2 wide-int.h files:
first one here:
/home/luc/crosstool-NG/.build/src/gcc-5.2.0/gcc/wide-int.h
and the second other one here:
/home/luc/.arduino15/packages/esp32/tools/xtensa-esp32-elf-gcc/<IP_ADDRESS>.g64433a-5.2.0/lib/gcc/xtensa-esp32-elf/5.2.0/plugin/include/wide-int.h
Both files are exactly the same.

Build-Failed.txt

@nuvalo wrote:

There are several consecutive template definitions in wide-int.h that should be adapted as described in stackoverflow. Just removed the consecutive "template<> template<....>" definitions and the error disappeared. I'll test the toolchain in the following days, but i believe that it should work.

Did you check that the toolchain works using that workaround?
Can you explain more how to modify wide-int.h?
It is not clear to me what to do. What parts exactly of the code shall be removed?
Shall the two wide-int.h files be modified?
Thanks

Rather than modifying wide-int.h as suggested @nuvalo, I used an older version of gcc to run ./ct-ng build successfully.
I encountered the compiling issues with gcc version 8.3.0 (Debian 8.3.0-6).
I had no compiling issues using gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1).
To check gcc version: gcc -v
To install gcc version 6: sudo apt install g++-6 gcc-6
To switch between gcc6 and gcc8:
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 1 --slave /usr/bin/g++ g++ /usr/bin/g++-8
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-6 2 --slave /usr/bin/g++ g++ /usr/bin/g++-6
update-alternatives --config gcc

For my purposes, I applied this patch to GCC 5.2.0, which allowed it to compile via GCC 8.3.0 with seemingly no ill effects.

Hello @jasonc0,
thank you for reporting this issue. At Espressif we really appreciate it when our users report issues as it helps us make our products better. Unfortunately there hasn't been any progress with this issue for the last 2 years and we are closing it to keep our backlog manageable.
If you don't agree with this decision, please feel free to reopen the issue or contact me directly.
Regards,
Tomas


onPaymentResult callback always returning pending status as pending and not redirecting to webview.

Describe the bug
I am using the sandbox environment to test khalti payment integration. The code seems to have worked for the first couple of times but afterwards the payment status returns 'pending' and the webview is not loading.
To Reproduce
I have used bloc to initialize khalti like this:
class KhaltiBloc extends Bloc<KhaltiEvent, KhaltiState> {
  KhaltiBloc() : super(KhaltiInitial()) {
    on<InitializeKhalti>(_initializeKhalti);
  }

  PaymentResult? paymentResult;

  FutureOr<void> _initializeKhalti(
      InitializeKhalti event, Emitter<KhaltiState> emit) async {
    emit(KhaltiLoading());
    final context = event.context;
    final payConfig = KhaltiPayConfig(
      publicKey:
          event.publicKey, // This is a dummy public key for example purpose
      pidx: event.pidx,
      environment: Environment.test,
    );
    try {
      final khalti = await Khalti.init(
        enableDebugging: true,
        payConfig: payConfig,
        onPaymentResult: (paymentResult, khalti) {
          log('--pay info ------');
          log(paymentResult.toString());
          paymentResult = paymentResult;
          khalti.close(context);
        },
        onMessage: (
          khalti, {
          description,
          statusCode,
          event,
          needsPaymentConfirmation,
        }) async {
          log(
            'Description: $description, Status Code: $statusCode, Event: $event, NeedsPaymentConfirmation: $needsPaymentConfirmation',
          );
          khalti.close(context);
        },
        onReturn: () {
          log('Successfully redirected to return_url.');
        },
      );
      emit(KhaltiInitalizeSuccess(khalti: khalti));
    } catch (e) {
      emit(KhaltiInitializeError());
    }
  }
}

[!NOTE]
the test credentials I used the first few times were:
Test Khalti ID<PHONE_NUMBER>
Test MPIN 1111
Test OTP 987654

Try generating a new pidx, then initiate a new purchase. The payment process may not have been verified on the testing server so it might have returned that response.
With a new pidx, the payment status should not return pending as its status.


Can't get Merge Request list from Gitlab Platform

When tries to get the Merge Requests list, use the state param with the value open but Gitlab only supports the value opened.
https://github.com/singapore/renovate/blob/d2cd755f3704bb69c551549cf3be6f82edcedb43/lib/workers/repository/onboarding/branch/check.js#L39

Thank you for the bug report. I have confirmed from the GitLab API:

I think the best way to fix this is to implement the same getPrList() concept in GitLab that we have in GitHub, and massage the data so that merged is rewritten to closed and opened is rewritten to open.


Add custom CSS to funding checkbox

When the divider was passed as the first element to the checkbox component, the for id given to the next checkbox had a -2 at the end. This meant that if there was an error summary it was not able to link to the first checkbox.
I couldn't see a way to override the index-based attributes given to the checkbox items, so this is a bit of a hacky way of adding a divider without adding it to the items.
Screenshots of UI changes
Before

After

Release checklist
As part of our continuous deployment strategy we must ensure that this work is
ready to be released at any point. Before merging to main we must first
confirm:
Pre merge checklist

[ ] Are any changes required to the e2e tests?
[ ] If you've added a new route, have you added a new
auditEvent? (see server/routes/apply.ts for examples)
[ ] Are there environment variables or other infrastructure configuration which needs to be included in this release?
[ ] Are there any data migrations required. Automatic or manual?
[ ] Does this rely on changes being deployed to the CAS API?

Post merge checklist
Once we've merged it will be auto-deployed to the dev environment.
Find the build-and-deploy job in CircleCI.
Should a release fail at any step, you as the author should now lead the work to
fix it as soon as possible.

https://trello.com/c/mi2mDYP4/483-alternative-id-documents-question


Why capitalized alternatives are bad

When I try using capitalized alternatives (['Alt1', 'Alt2']), the client throws an exception: Bad alternative name.
Two issues here.

This is a very bad error message. It does not say why the alternative name is bad, one is forced to find this place in the source code to figure it out.
Why are capitalized alternative names prohibited? What's the motivation behind this?

Please let me know if you'd submit a PR fixing this.

You're correct, the exception thrown isn't great. I'd gladly accept a PR. The motivation is to avoid accidental errors.
i.e. You participate the test with Alt1, but accidentally convert with alt1.

Fixed in https://github.com/seatgeek/sixpack-rb/commit/c48842111563a7033e0e1822fa0918585025fa49


hover on thumbnails stops autoplay and slides to image after a short …

…delay

@twanschik awesome stuff!


amplify remove env cannot delete deployment bucket

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.16.0
Amplify CLI Version
4.45.2
What operating system are you using?
Windows
Amplify Categories
Not applicable
Amplify Commands
env
Describe the bug
Changing the local-aws-info.json to remove an environment in a separate account (workaround) with amplify remove env results in delete the backend successfully but fails deleting the deployment bucket in the specified account "× remove env failed: The bucket you tried to delete is not empty". Also the team-provider-info.json still maintains the deleted environment.
Expected behavior
The deployment bucket should be deleted when there is no other backend or frontend in the specified account. Also the environment should be deleted from the team-provider-info.json file.
Reproduction steps

amplify env add
amplify push
amplify env checkout (e.g. dev)
amplify remove env (e.g. sandbox)

Log output
# Put your logs below this line
? Are you sure you want to continue? This CANNOT be undone. (This will delete 'testenv' environment of the project from the cloud) Yes
- Deleting resources from the cloud. This may take a few minutes...
Deleting env:testenv
| Deleting resources from the cloud. This may take a few minutes...
Error in deleting env:testenv
The bucket you tried to delete is not empty
× remove env failed: The bucket you tried to delete is not empty
The bucket you tried to delete is not empty
BucketNotEmpty: The bucket you tried to delete is not empty
    at Request.extractError (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\services\s3.js:712:35)
    at Request.callListeners (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:106:20)
    at Request.emit (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:78:10)
    at Request.emit (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:688:14)
    at Request.transition (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:22:10)
    at AcceptorStateMachine.runTo (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\state_machine.js:14:12)
    at C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\state_machine.js:26:10
    at Request.<anonymous> (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:38:9)
    at Request.<anonymous> (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\request.js:690:12)
    at Request.callListeners (C:\Users\Eric.Wolf\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\aws-sdk\lib\sequential_executor.js:116:18)

Hi @ericwolf08-wp , thanks for taking the time to submit this.
If I understand correctly, you are trying to remove an environment that is associated with another AWS account/profile?
If thats the case, and you have both profiles/credential, can you:

Use amplify configure project which will give you the option to select a different profile for the CLI
Swap to, and then from, the profile with permissions to amplify env remove, etc.?

Also, can you confirm that the problem still exists with the most recent version of the CLI?

Just to confirm - I ran through a typical flow (single profile) below and that behaves as expected.

amplify init
amplify push
amplify env add testenv
amplify status -> testenv
amplify env checkout dev
amplify status -> dev
amplify env remove testenv

✔ Successfully removed environment from the cloud
 Successfully removed environment from your project locally

Hey there,
i can confirm that reconfiguring the whole project to work in a separate account with amplify configure project works (yet more annoying than just changing the json to use a different profile) can remove the cloudformation stack.
But the problem remains, that the deployment bucket cannot be deleted. Also the team-provider-info.json does not delete the information about the deleted environment (perhaps because it was not successful).
I tried the same steps you proposed, yet without success resulting again in
× remove env failed: The bucket you tried to delete is not empty
Is further information needed here?

Hello there,
i can confirm that reconfiguring the Amplify Project works, yet changing the local-aws-info.json to use a different account is far easier.
I updated to the newest version 4.45.2 but the problem remains. The Cloudformation Stack is deleted successfully but the deployment bucket remains, since its not empty:
× remove env failed: The bucket you tried to delete is not empty
Also, the application is still visible in the Amplify Management Console (yet empty) and the team-provider-info.json also still has the information about the test environment.
Is there any further information needed?

Hi! Thanks for the follow up:
Can you try editing amplify/.config/local-aws-info.json and temporarily change the value profileName of the current env to the one you need to use for deletion.
Then retry amplify env remove ...

I already tried that without success :(

Was/is there any additional configuration done for this project, or are these the first things that were done when initializing the project?

its a fully working application with frontend and backend (api, lambda, cognit, s3). The additional environments are for features and testing.

Is there anything left in the account profile's S3 buckets (deployment or storage) that the test env is associated with?

the labels are correct. the storage bucket gets delete through cloudformation. the -deployment bucket still contains
#current-cloud-backend.zip, amplify-meta.json and backend-config.json. amplify-meta.json for example still has the provider information for roles etc.

@ericwolf08 Can you check if there is versioning on the objects in the s3 bucket?

the versioning is disabled in the s3 bucket

@ericwolf08-wp We were able to root-cause the issue. It might be due to a missing policy - s3:DeleteObjectVersion which was missing in our docs. Did you use Admin UI or a custom IAM role/user based on our docs to setup your project?

I am using the AdministratorAccess-Amplify AWS managed Policy in my Role for the Amplify CLI. And yes, s3:DeleteObjectVersion is actually missing. I will try this again.


add supported chains for 1inch

replace with 1inch api v4
add missing chains

@mikoim sorry for the delay, life you know, I will try and get this tested and reviewed next week. Sorry for the delay!


[SPARK-11093] [Core] ChildFirstURLClassLoader#getResources should return all found resources, not just those in the child classloader

Can one of the admins verify this patch?

ok to test

Merged build triggered.

Merged build started.

Test build #43694 has started for   PR 9106 at commit 87cf157.

Test build #43694 has finished for   PR 9106 at commit 87cf157.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43694/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #1897 has started for   PR 9106 at commit 87cf157.

Test build #1897 has finished for   PR 9106 at commit 87cf157.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM, aside from minor style nit.

Fixed

Merged build triggered.

Merged build started.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43724/
Test FAILed.

Merged build finished. Test FAILed.

2nd time on this PR for test failure due to (seemingly) network issues

retest this please

retest this please

Merged build triggered.

Merged build started.

Test build #43728 has started for   PR 9106 at commit d0aa6aa.

Test build #43728 has finished for   PR 9106 at commit d0aa6aa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43728/
Test PASSed.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

retest this please

Merged build triggered.

Merged build started.

Test build #43752 has started for   PR 9106 at commit 8f1b6d9.

Test build #43754 has started for   PR 9106 at commit 8f1b6d9.

Test build #43752 has finished for   PR 9106 at commit 8f1b6d9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43752/
Test FAILed.

Merged build finished. Test FAILed.

Test build #43754 has finished for   PR 9106 at commit 8f1b6d9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43754/
Test PASSed.

Merging to master

Closed but not merged?

@alewando no it was merged; see above https://github.com/apache/spark/commit/0f62c2282bb30cb4fb6eea9d28b198d557a79b22


duplicate and missing alpha

duplicate: Hierarchical Encoder with Auxiliary Supervision for Table-to-text Generation: Learning Better Representation for Tables
missing alpha: cene -> Scene

This is a cool repository for OCR studying, and I wish to contribute more.


Compiled app?

Hi, I was looking to find an installation instruction or something.. Is there a DMG or compiled app available?

You can easy build with Xcode.
To launch a CP/M program, locate its .COM in the Finder and double click.

Apologies, missed this somehow. Compiled builds are hidden in the 'Releases' tab; this is the latest.


[Named Blob] Filter out expired/deleted entries in listing named blob

Filter out expired/deleted entries in listing named blob

Please add some test cases

Ok, just added. thanks!

Codecov Report
Patch coverage: 100.00% and project coverage change: -2.75% :warning:

Comparison is base (827d592) 72.88% compared to head (5499e9d) 70.13%.
Report is 1 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2534      +/-   ##
============================================
- Coverage     72.88%   70.13%   -2.75%
+ Complexity    11237    10838     -399
============================================
  Files           792      792
  Lines         63701    63726      +25
  Branches       7788     7793       +5
============================================
- Hits          46426    44692    -1734
- Misses        14725    16514    +1789
+ Partials       2550     2520      -30

Files Changed
Coverage Δ

.../java/com/github/ambry/named/MySqlNamedBlobDb.java
70.91% <100.00%> (-15.08%)
:arrow_down:

... and 92 files with indirect coverage changes

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


Update to VS19

Update to VS19. It's OK to leave previous versions, but current version instructions should always come first.

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

ID: 660b0f7c-9941-2db3-63bf-fc8a97765b1e
Version Independent ID: 5aa1e6f6-534a-05b9-c44a-1f62b24c201a
Content: Hello, Android: Quickstart - Xamarin
Content Source: docs/android/get-started/hello-android/hello-android-quickstart.md
Product: xamarin
Technology: xamarin-android
GitHub Login: @conceptdev
Microsoft Alias: crdun

Amen!

Thanks for submitting an issue and we apologize for the delayed response. The requested updates haven't been made since the creation of the issue, and the timeline for resolution may vary based on resourcing, so the issue is being moved to an internal repo to better track it.


[3pt]  - Create feature: add  new like - Student A

When the user clicks on the Like button of an item (on Homepage), the interaction is recorded in the Involvement API and the screen is updated.

https://github.com/businesskaniki/microflix/pull/34


Add details for enabling In-Memory Columnar processing on XE

This blog post presents a memory setup to enable In-Memory Columnar processing (SIMD vectorized CPU instructions...) with XE:
-- Connect to CDB as DBA
connect / as sysdba
-- Edit following init.ora parameters
alter system set sga_target=1568M scope=spfile;
alter system set pga_aggregate_target=412M scope=spfile;
alter system set inmemory_size=1G scope=spfile;
shutdown immediate;
startup;

It would be worth highlighting this inside the image documentation.

Merged


Support UTF-8 and Update vendor

Support UTF-8
Update vendor

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Prevent divergent migrations from being merged by concurrent, not-rebased PRs

Problem

See https://github.com/WordPress/openverse-api/pull/810 and the description for the issue.
Description

We need some way to prevent this.
Here are some suggestions I left in this comment, copied below: https://github.com/WordPress/openverse-api/pull/810#issuecomment-1191503799

How can we prevent this? Is there any way we can ensure PRs with migrations are always rebased before merging? Could we run an action triggered by pushes that introduce new migrations using https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#running-your-workflow-only-when-a-push-affects-specific-files and the iterate through all open, non-draft PRs and request changes on them if there is a migration in them?
We'd also need a similar job in the CI + CD workflow to check for migration conflicts against main any time the PR is pushed to.

Marked as high due to the risk it introduces.
Implementation

[ ] 🙋 I would be interested in implementing this feature.

I think this can be implemented automatically using merge queues (provided we ensure that maintainers put PRs with migrations into a merge queue instead of merging directly).
From the docs

The merge queue will ensure the pull request's changes pass all required status checks when applied to the latest version of the target branch and any pull requests already in the queue.

This would mean that the merge queue would run CI + CD right before merging the PR which means

the migration is either valid and CI + CD passes and the PR is immediately merged into main
the migrations have diverged, CI + CD would fail and the merge would be cancelled.

This differs from regular branch checks in that the merge queue checks are run just before merging (and can cancel a merge in progress), whereas branch checks run at PR creation or update time and the state of main can have changed between the branch checks being run and the PR getting merged.

A simple approach is this plugin which we've been using for a year now: https://github.com/crux-lab/django-migrations-git-conflicts
It writes the latest migration to a text file, so if migrations aren't merged, that file will have a git conflict.


solars rotate slower

closes #11486
About the PR
Screenshots

Changelog

:cl:

tweak: solar control system updates every 5 seconds instead of 1

I do think there's a better way of doing it. If so, then let me know

This touches the UI and not the solars?


Consider using O_TMPFILE

O_TMPFILE is a Linux-specific flag that seems suited for exactly the purpose of atomic file creation + renaming.
From the manpage:

There are two main use cases for O_TMPFILE:

Improved tmpfile(3) functionality: race-free creation of temporary files that (1) are automatically deleted when closed; (2) can never be reached via any pathname; (3) are not subject to symlink attacks; and (4) do not require the caller to devise unique names.
Creating a file that is initially invisible, which is then populated with data and adjusted to have appropriate filesystem attributes (fchown(2), fchmod(2), fsetxattr(2), etc.)  before being atomically linked into the filesystem in a fully formed state (using linkat(2) as described above).

I just learned that there's no way to replace an existing file using an O_TMPFILE. The only way to persist it is with linkat, which doesn't provide a way to overwrite the destination file (yet).
I'm closing this issue. Sorry for the spam!


rename sfz folders and files

@Lucarda

i think this will be a better pattern with one sfizz~ folder
pd-else/
   ├──sfz~/
      ├──sfizz~/
      ├──example.sfz
      ├──Makefile
      ├──sfz~.c
      ├──sfz~install.sh
      ├──sfz~make.sh
      ├──sfz~-help.pd

note we can do a rename for sfz~.c
is this ok for you?
i'll wait for your answer.

the subfolder named "sfizz~" is also weird, maybe just "sfizz"

the sfizz_puredata.c file should also be renamed to "sfz~.c"

the sfizz_puredata.c file should also be renamed to "sfz~.c"

yes as i proposed above.
i'll have to leave home and not sure if I get this done in the weekend. may be.

ok, I updated the code

i'm ready to start the PR. I prefer to do it while your not working on else.
i'll be awake 8hrs more. it wont take me long. tell me when to start.
:)

go ahead, I'm done :)

i'm done with https://github.com/porres/pd-else/pull/1686

what changed now, how do I build this?

Alexandres-MacBook-Air:pd-sfizz porres$ make sfizz
make: Nothing to be done for `sfizz'.
Alexandres-MacBook-Air:pd-sfizz porres$ make sfz~
cc     sfz~.c   -o sfz~
sfz~.c:11:10: fatal error: 'm_pd.h' file not found
#include <m_pd.h>
^~~~~~~~

Alexandres-MacBook-Air:pd-sfizz porres$ make sfizz

why are you standing at pd-sfizz instead of pd-else ?

I tried changing pd-sfizz and it all got ruined

maybe you can also change things at pd-sfizz and give me instructions for both

oh no, :) yo should be able to figure how to update pd-sfizz yourself :)

you should be able to figure how to update pd-sfizz yourself :)

I ruined it for good now, it's useless

anyway, I really have no idea how to build this now with the changes, please help :0

also, why do we have these copied files?

those files are in the original repo https://github.com/sfztools/sfizz-ui/tree/develop/plugins/puredata and i think we should leave them or the build will fail, dunneo, try it.

anyway, I really have no idea how to build this now with the changes, please help :0

standing at pd-else:
build:
make sfizz
install (always needed)
make sfizz-install objectsdir=./out extension=d_amd64
you can also do both (better)
make sfizz && make sfizz-install objectsdir=./out extension=d_amd64
the object is placed: pd-else/out/else
clean:
make sfizz-clean

cool, I guess we can forget about pd-sfizz


Root to element

🎉 New feature
Summary
Adds Root::ToElement, similar to the other ToElement functions. This does change the API of World::ToElement, which I think is okay because sdf12 has not been released with the original World::ToElement function.
Test it
Run the tests.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Updated documentation (as needed)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Codecov Report

Merging #842 (99ad462) into root_mutable_accessors (10fcc38) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@                    Coverage Diff                     @@
##           root_mutable_accessors     #842      +/-   ##
==========================================================
+ Coverage                   90.71%   90.73%   +0.01%
==========================================================
  Files                          78       78
  Lines                       12459    12482      +23
==========================================================
+ Hits                        11302    11325      +23
  Misses                       1157     1157

Impacted Files
Coverage Δ

src/Model.cc
91.50% <100.00%> (+0.04%)
:arrow_up:

src/Root.cc
93.92% <100.00%> (+0.84%)
:arrow_up:

src/World.cc
94.55% <100.00%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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

Can you resolve the conflicts?

Can you resolve the conflicts?

Resolved.

Since using ToElement(true) won't capture the effects of the param passing functionality, it would be good to mentiona that in ToElement's documentation.

I've add documentation to the ToElement functions.

One overall observation is that we have recently made efforts to avoid printing default elements and attributes (see #575) when calling sdf::Element::ToString. However, this currently doesn't work if the ElementPtr is obtained using ToElement. Should I ticket an issue?

Yes please.

Ticketed https://github.com/ignitionrobotics/sdformat/issues/867

This pull request has been mentioned on Gazebo Community. There might be relevant details there:
https://community.gazebosim.org/t/new-ignition-releases-2022-04-13-fortress-edifice/1367/1


Convert multi dimensional numpy array to pyarrow array

data = np.zeros((10,8), dtype=np.uint8)
out = pa.array(list(data))
out.type # ListType(list<item: uint8>)
data = np.zeros((3,4,6), dtype=np.uint8)
out = pa.array(list(data)) # Throws error ArrowInvalid: Can only convert 1-dimensional array values
Even though it's working on 2D numpy arrays perfectly, it doesn't work on N-Dimensional numpy arrays (where N > 2). Is possible to extend the current feature for inner elements with dimension greater than 1?
Reporter: Bhavitvya Malik
Note: This issue was originally created as ARROW-11600. Please see the migration documentation for further details.

It seems that, the reason it does not work is that, the list conversion is only applied to the first dimension of your numpy array. You can fix your exemple by doing the following:
 out = pa.array(data.tolist()) # Throws error ArrowInvalid: Can only convert 1-dimensional array values

This is however not ideal as calling tolist() is quite slow if we compare to first calling ravel and using numpy->pyarrow default conversion.
Check
now = time.time();a = data.tolist();print((time.time() - now) * 1000)
## print: 0.0059604644775390625 ms

# And

now = time.time();a = data.ravel();print((time.time() - now) * 1000)
## print: 18.219709396362305 ms

# And further reconverting to pyarrow

now = time.time();a = pa.array(data.tolist());print((time.time() - now) * 1000)
## print: 51.234 ms

# Compared to

now = time.time();a = pa.array(data.ravel());print((time.time() - now) * 1000)
## print: 0.09 ms

Wonder if there is anyone working on the issue: ArrowInvalid: Can only convert 1-dimensional array values
to be able to convert numpy.ndarray to pyarrow.array


Issue in the nav bar links

Go to the Event tab or any other tab and click on the recode hive logo
404 page shows.

Sir i want to work on that

sir the previous link replacement was done by nishant so i leave that


Support full suite of cel-go extensions

Feature Description
Support cel-go extensions and document the set of extensions supported.

https://github.com/google/cel-go/tree/master/ext

Better yet, allow an option box in the playground that enables/disables extensions (atleast cel-go extensions)
eg right now only the "strings" is supported
https://github.com/undistro/cel-playground/blob/main/eval/eval.go#L31
so this works now but not the stuff like base64.*
jwt.iss.lowerAscii()  ==  'auth.acme.com:12350'

Hi @salrashid123
Thank you for the suggestion!
Your idea makes a lot of sense, and we appreciate your contribution to the project.
We'll definitely consider implementing it. Any PR is welcome here!


devicemapper under ubuntu flaky?

Since upgrading to docker 1.7.1 which made devicemapper the defualt graph driver under ubuntu 14.04.2 LTS I've noticed some strange failures. Here is the latest:
+ docker pull registry.customer.io:443/ruby_build
latest: Pulling from registry.customer.io:443/ruby_build
511136ea3c5a: Already exists
5bd56d818842: Already exists
b21b50f44582: Already exists
465cca257df8: Already exists
62b5b5c398f7: Already exists
4a65e9bf4f14: Already exists
4a65e9bf4f14: Already exists
Digest: sha256:954baf25bd0f4b954b244667cc8912a3ab812de11a4284086150a308f7d96f46
Status: Image is up to date for registry.customer.io:443/ruby_build:latest
+ docker run -i --rm -v /home/deploy/deployed/jenkins/jobs/app/workspace:/source registry.customer.io:443/ruby_build
Error response from daemon: Cannot start container 33c51732316f6dde5645f2654abb35c1a1d938f41e1d50498e24e642e5e07572: Error getting container 33c51732316f6dde5645f2654abb35c1a1d938f41e1d50498e24e642e5e07572 from driver devicemapper: Error mounting '/dev/mapper/docker-9:3-97255531-33c51732316f6dde5645f2654abb35c1a1d938f41e1d50498e24e642e5e07572' on '/home/docker/devicemapper/mnt/33c51732316f6dde5645f2654abb35c1a1d938f41e1d50498e24e642e5e07572': no such file or directory
Build step 'Execute shell' marked build as failure
Finished: FAILURE

I just tried this (6 hours later) and with NO changes everything is back to working? How can I help diagnose the root of this issue?
OS: Ubuntu 14.04.2 LTS (GNU/Linux 3.14.32-xxxx-grs-ipv6-64 x86_64)
Docker version: 1.7.1 (from lxc-docker-1.7.1).

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Actually, the default graphdriver for Ubuntu 14.04 is AUFS, which can be seen in the install script: hack/install.sh#L162-L181
How did you install / upgrade docker? Did you use the script at https://get.docker.com/ubuntu ? Because that will only perform a minimal install and will not install AUFS.
It's possible that you're now running devicemapper without Udev-sync support, which is known to cause issues, and strongly discouraged. Also, the default settings for devicemapper are not recommended for production use, and require additional manual configuration for improved performance and stability.
I suggest to switch to AUFS as graph driver, which is currently the recommended configuration. You will have to clean your current graph directories.
In case you missed; we very recently launched official apt and yum repositories, more information on that can be found here: http://blog.docker.com/2015/07/new-apt-and-yum-repos/
I'm going to close this issue now, but feel free to comment here after I've closed this

I updated with apt-get. The original installation was not from a script, that is unacceptable on a production machine and used the docker defaults.
See https://github.com/docker/docker/issues/14707 for some history on upgrading from 1.7.0 to 1.7.1.
I solved this problem by switching to ufs and changing the deployment scripts to exclicitely set the graph driver to aufs.

Thanks @newhook, good to hear you managed to resolve it. Reading the linked issue, I agree that the description in the changelog is cryptic and doesn't cover the possible consequences. It may be "late to the party", but perhaps you have a suggestion on how to improve that and are willing to create a pull request to update the CHANGELOG.md?


Add Qualification class to applicant

Codecov Report

Merging #77 (d1ad7f8) into master (3c19869) will decrease coverage by 0.55%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master      #77      +/-   ##
============================================
- Coverage     70.87%   70.32%   -0.56%
  Complexity      401      401
============================================
  Files            73       74       +1
  Lines          1267     1277      +10
  Branches        128      129       +1
============================================
  Hits            898      898
- Misses          337      347      +10
  Partials         32       32

Impacted Files
Coverage Δ

...a/seedu/address/model/applicant/Qualification.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Failed to Create CT

unable to create CT 101 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/101/rootfs --skip-old-files --anchored --exclude './dev/'' failed: exit code 2

unable to create CT 101 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/101/rootfs --skip-old-files --anchored --exclude './dev/'' failed: exit code 2

Full Console Output:
Logical volume "vm-101-disk-0" created.
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: 124d5ea7-4f5b-4e16-976b-b3c5c3055e07
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
extracting archive '/root/proxmox-dietpi-lxc.tar.gz'
tar: ./mnt/dietpi_userdata/docker-data/volumes/backingFsBlockDev: Cannot mknod: Operation not permitted
Total bytes read:<PHONE_NUMBER> (984MiB, 210MiB/s)
tar: Exiting with failure status due to previous errors
Logical volume "vm-101-disk-0" successfully removed.
unable to create CT 101 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/101/rootfs --skip-old-files --anchored --exclude './dev/'' failed: exit code 2

Hi @MekayelAnik,
did you use the proxmox-vm-to-ct script to generate this? If so what were the arguments sent to the script? (mask any passwords/sensitive things).

Hi @MekayelAnik,
did you use the proxmox-vm-to-ct script to generate this? If so what were the arguments sent to the script? (mask any passwords/sensitive things).

Yes, I have used proxmox-vm-to-ct to generate this.
No, there was no arguments sent to this script as everything was at it's default root : dietpi.
Your script is very good. I was able to convert vm to ct when there was no installations were made i.e. Just created the VM not even started it for once, then the script works as a charm.
But at the 1st time I wanted to convert a VM with all the intended software installed through dietpi-software, in my case docker.
Then the script will finish rsync but will throw error when it will try to launch the converted image to container.
That's why I had to convert the raw untouched VM to CT, after that I installed all my things and made it a template.
Also one other thing, I tried to stop the CLEANUP after the failed Container deployment. Edited the script to do so, but it didn't.
Thanks a lot. You did an outstanding job. The most straight forward Conversion Procedure I have encountered. It just needs a little touch ups.
Regards

Hey mate,
Thank-you for your very kind words, and thanks to bug reports like this, you're finding cases that will make it even better! So thank-you for opening the issue :)
Oh I see, I haven't installed docker into my 'base' VM prior to CT - that's done after, only the bare essentials (like tmux, some config changes). Docker may be a complication and haven't looked into that yet - but will now. One does need to enable nesting and keyctl features and I'm sorry I haven't had a chance to add the flags for non-default options yet due to work life.
Will try and reproduce this tonight.
So that I understand, you have the latest DietPi in a VM  and via dietpi-software installed:

Docker
(nothing else?)

Then used the script to convert the said VM to a CT.
Also to avoid cleaning up, you can use the --source-output, --output or -o switch and save it somewhere, for example:
./proxmox-vm-to-ct.sh --source <IP_ADDRESS> \
                      --target the-matrix-reloaded \
                      --storage local-lvm \
                      --default-config \
                      --prompt-password \
                      --output ~/dietpi-dockerised.tar.gz

The idea was that with a saved output, a future feature would continue to use that *.tar.gz to create containers instead of having to repeat this every time (on the TODO list!). Apologies.

Hey mate,
Thank-you for your very kind words, and thanks to bug reports like this, you're finding cases that will make it even better! So thank-you for opening the issue :)
Oh I see, I haven't installed docker into my 'base' VM prior to CT - that's done after, only the bare essentials (like tmux, some config changes). Docker may be a complication and haven't looked into that yet - but will now. One does need to enable nesting and keyctl features and I'm sorry I haven't had a chance to add the flags for non-default options yet due to work life.
Will try and reproduce this tonight.
So that I understand, you have the latest DietPi in a VM and via dietpi-software installed:

Docker
(nothing else?)

I had installed tmux as you mentioned that tmux or something like that is a must. Done some changes in dietpi-config such as Time-Zone, DNS in the NETWORK section. Things like that.
Note: I was able to make the container without installing tmux . I didn't touch the VM. Just imported the dietpi.qcow2. That's it. Didn't even gave first run.

Also to avoid cleaning up, you can use the --source-output, --output or -o switch and save it somewhere, for example:
./proxmox-vm-to-ct.sh --source <IP_ADDRESS> \
                      --target the-matrix-reloaded \
                      --storage local-lvm \
                      --default-config \
                      --prompt-password \
                      --output ~/dietpi-dockerised.tar.gz

I think yes. Not certain. I was in stress that time. Please have a look in the Cleanup section. Maybe I have done something wrong then. When it wasn't working, I edited the script: OPT_CLEANUP in the place of OPT_SOURCE_OUTPUT. My lousy head at that moment. Unbelievable!

The idea was that with a saved output, a future feature would continue to use that *.tar.gz to create containers instead of having to repeat this every time (on the TODO list!). Apologies.

This was my first time converting VM into LXC. Thanks to you, it was way Easier than I thought it would be.

I had installed tmux as you mentioned that tmux or something like that is a must. Done some changes in dietpi-config such as Time-Zone, DNS in the NETWORK section. Things like that.

Ah no, not required, tmux is like screen in the old days, makes working in terminal so much easier, have a look at tmux features and you can also see my tmux config to get started :-)

I think yes. Not certain. I was in stress that time. Please have a look in the Cleanup section. Maybe I have done something wrong then. When it wasn't working, I edited the script: OPT_CLEANUP in the place of OPT_SOURCE_OUTPUT. My lousy head at that moment. Unbelievable!

No  problemo. It could be handled better, I just like to keep things clean and operate on, if i take a dump (of a temporary file) somewhere, i clean up.
The good news is I've gone all out and created a DietPi 8 with what you installed (and maybe more, because why not!):

Then I reproduced your issue:

(that green bar at the bottom is tmux btw, really basic, allows you to tab between bash sessions I have...)
I suspect because the VM->CT for docker one needs:

nesting
keyctl
privileged container

I will have to do some work and look at how to solve it nicely.

I think I've got it @MekayelAnik, unfortunately to enable this, you need to run a privileged container with a few more features as mentioned above.
Opened #3 which has all the details, are you able to grab that branch and try that and see if it works for you with the new switch?
This is what I get with the new --default-config-containerd switch I added in that branch:

Thanks.

@thushan Thanks a lot Brother.
Inshallah, I will do and let you know.

Sorry brother, the issue remains. I have recorded the issue.

Error Log:
  Logical volume "vm-100-disk-0" created.
Creating filesystem with 5242880 4k blocks and 1310720 inodes
Filesystem UUID: e69664e8-6efe-4fb9-b028-f8a61f9e8aad
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
extracting archive '/tmp/proxmox-vm-to-ct/<IP_ADDRESS>.tar.gz'
tar: ./mnt/dietpi_userdata/docker-data/volumes/backingFsBlockDev: Cannot mknod: Operation not permitted
Total bytes read: 657152000 (627MiB, 202MiB/s)
tar: Exiting with failure status due to previous errors
  Logical volume "vm-100-disk-0" successfully removed.
unable to create CT 100 - command 'lxc-usernsexec -m u:0:100000:65536 -m g:0:100000:65536 -- tar xpf - -z --totals --one-file-system -p --sparse --numeric-owner --acls --xattrs '--xattrs-include=user.*' '--xattrs-include=security.capability' '--warning=no-file-ignored' '--warning=no-xattr-write' -C /var/lib/lxc/100/rootfs --skip-old-files --anchored --exclude './dev/*'' failed: exit code 2

Hey mate,
Thanks for the video & trying it. Apologies, I should have mentioned it only needs --default-config-containerd, not both. If you remove the --default-config I have feeling it should be good.
When the script runs, before the password prints, it should show default config: 2, right now it's 1. I'll fix that up too.
Thanks again for trying it.

Alhamdulillah. I am glad to help a little. But I am really sorry, still facing the same problem. Don't know why. :(
I am UPLOADING another video as well as the SHELL FILE I am using for the conversion. Please have a look,if I have done something wrong.

Oh my goodness, I just realised what has happened. I misspelt the argument, you're using --default-config-containered instead of --default-config-containerd. it's containerd not  containered.
I think my mac autocorrects containerd to containered.
Try it like this:
./proxmox-vm-to-ct.sh --source <IP_ADDRESS> \
                      --target test-ct    \
                      --storage local-lvm \
                      --ignore-prep       \
                      --default-config-containerd

Or even easier:
./proxmox-vm-to-ct.sh --source <IP_ADDRESS> \
                      --target test-ct    \
                      --storage local-lvm \
                      --ignore-prep       \
                      --default-config-docker

I will check if I made those mistakes in the script. Though I think the autocorrect is only in my Firefox. So sorry, completely missed this.

hi
Thanks for this script! It has been very valuable to us because we had lots of issues manually doing. We can confirm this works for me with dietpi9 vm to container compared to main branch.
We could use
./proxmox-vm-to-ct.sh --source voxel-engine-master-image \
                      --target voxel-engine-ct-node-1    \
                      --storage local-zfs \
                      --default-config-containerd

dietpi preparation was also very welcome, we had no idea. we also used again with debian12 images with --ignore-prep and works wunderbar gut!
thank you again.

thanks for the comments @rusticslayer good to see someones tried this with dietpi9 that was released only a few days ago!! will merge that PR but will leave this open for @MekayelAnik to comment when they're ready.


Use OAuth instead of API-Key for Google Sheets access

Authorize Google Sheets requests

Closing since the Annotation Interface is meant to replace the Google Sheet.


Updates to Deploy Script and Package

I updated the deploy setup script to include the jamf binary lookup method.
Rebuilt package with Packages.

Thanks !


Fix java template

This will fix the java template generated from tkn pac
Submitter Checklist

[ ] ♽  Run make test lint before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI
[ ] 📖 If you are adding a user facing feature or make a change of the behavior, please verify that you have documented it
[ ] 🧪 100% coverage is not a target but most of the time we would rather have a unit test if you make a code change.
[ ] 🎁 If that's something that is possible to do please ensure to check if we can add a e2e test.
[ ] 🔎 If there is a flakiness in the CI tests then don't necessary ignore it, better get the flakyness fixed before merging or if that's not possible there is a good reason to bypass it. (token rate limitation may be a good reason to skip).

/retest

Error from server (InternalError): error when creating "/home/pipelines/GIT/pipelines-as-code-infra/templates/paac/repositories.yaml": Internal error occurred: failed calling webhook "validation.pipelinesascode.tekton.dev": failed to call webhook: Post "https://pipelines-as-code-webhook.pipelines-as-code.svc:443/validate?timeout=10s": no endpoints available for service "pipelines-as-code-webhook"
Error from server (InternalError): error when creating "/home/pipelines/GIT/pipelines-as-code-infra/templates/paac/repositories.yaml": Internal error occurred: failed calling webhook "validation.pipelinesascode.tekton.dev": failed to call webhook: Post "https://pipelines-as-code-webhook.pipelines-as-code.svc:443/validate?timeout=10s": no endpoints available for service "pipelines-as-code-webhook"
Error from server (InternalError): error when creating "/home/pipelines/GIT/pipelines-as-code-infra/templates/paac/repositories.yaml": Internal error occurred: failed calling webhook "validation.pipelinesascode.tekton.dev": failed to call webhook: Post "https://pipelines-as-code-webhook.pipelines-as-code.svc:443/validate?timeout=10s": no endpoints available for service "pipelines-as-code-webhook"
paac: Fri 19 May 07:00:09 CEST 2023 :: stop
upload: profiles/paac/auth/gpg/kubeadmin.passw

/retest


[wxwidgets] Build Failed with x64-mingw-dynamic on Windows 10

Package: wxwidgets[core,sound]:x64-mingw-dynamic -> 3.1.6#2
Host Environment

Host: x64-windows
Compiler: GNU 10.3.0
vcpkg-tool version: 2022-06-17-9268e366206712e38102b28dbd1617697a99ff2e
vcpkg-scripts version: 4826ede84 2022-07-01 (2 days ago)

To Reproduce
vcpkg install wxwidgets
Failure logs
-- Using cached wxWidgets-wxWidgets-35a6d7b15fedfdb5198bb6c28b31cda33b2c2a76.tar.gz.
-- Cleaning sources at C:/dev/vcpkg/buildtrees/wxwidgets/src/a33b2c2a76-d7830df458.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/dev/vcpkg/downloads/wxWidgets-wxWidgets-35a6d7b15fedfdb5198bb6c28b31cda33b2c2a76.tar.gz
-- Applying patch install-layout.patch
-- Applying patch relocatable-wx-config.patch
-- Applying patch nanosvg-ext-depend.patch
-- Applying patch fix-libs-export.patch
-- Applying patch fix-pcre2.patch
-- Using source at C:/dev/vcpkg/buildtrees/wxwidgets/src/a33b2c2a76-d7830df458.clean
-- Using cached msys-mingw-w64-i686-pkg-config-0.29.2-3-any.pkg.tar.zst.
-- Using cached msys-mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>73.5be8fcd83-1-any.pkg.tar.zst.
-- Using msys root at C:/dev/vcpkg/downloads/tools/msys2/9a1ec3f33446b195
-- Found external ninja('1.10.2').
-- Configuring x64-mingw-dynamic
-- Building x64-mingw-dynamic-dbg
-- Building x64-mingw-dynamic-rel
CMake Error at ports/wxwidgets/portfile.cmake:111 (file):
  file RENAME failed to rename

    C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/bin/wx-config

  to

    C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/tools/wxwidgets/wx-config

  because: �t�Χ䤣����w���ɮסC

Call Stack (most recent call first):
  scripts/ports.cmake:146 (include)

Additional context
I have tried git pull and vcpkg upgrade in the vcpkg root directory, but I still can not build wxWidgets completely.  I have tried vcpkg install wxwidget --triplet=x64-windows and it works, but I want use the x64-mingw-dynamic triplet.
And I don't know why my error message looks like in the wrong encoding, I've tried chcp 65001 which didn't work. I have confirmed that message is "No such file or directory".
I've checked the folder C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/bin/wx-config which didn't exist, and the folder C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/tools/wxwidgets/wx-config is empty.

Confirmed

I've checked the folder C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/bin/wx-config which didn't exist, and the folder C:/dev/vcpkg/packages/wxwidgets_x64-mingw-dynamic/tools/wxwidgets/wx-config is empty.

It is a script, not folders. And the source (bin/wx-config) is missing now.

Please test #25572.

Please test #25572.

I've tested this PR #25572, and vcpkg installs wxWidgets with x64-mingw-dynamic triplet successfully. However, there is another problem that I'm getting error at cmake configuration with my project.
CMake Error at C:/Program Files/CMake/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find wxWidgets (missing: wxWidgets_LIBRARIES
  wxWidgets_INCLUDE_DIRS)
Call Stack (most recent call first):
  C:/Program Files/CMake/share/cmake-3.23/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  C:/Program Files/CMake/share/cmake-3.23/Modules/FindwxWidgets.cmake:1025 (find_package_handle_standard_args)
  C:/dev/vcpkg/installed/x64-mingw-dynamic/share/wxwidgets/vcpkg-cmake-wrapper.cmake:49 (_find_package)
  C:/dev/vcpkg/scripts/buildsystems/vcpkg.cmake:778 (include)
  CMakeLists.txt:41 (find_package)

-- Configuring incomplete, errors occurred!

I've tried setting the wxWidgets_LIB_DIR and wxWidgets_ROOT_DIR variables according to this discussion but with no luck: https://groups.google.com/g/wx-dev/c/i06WTStk2Nw/m/YtXWgpM3BAAJ

You shouldn't set any variables. share/wxwidgets/vcpkg-cmake-wrapper.cmake  is doing the work for you.
I can test mingw on Windows later.

https://groups.google.com/g/wx-dev/c/i06WTStk2Nw/m/YtXWgpM3BAAJ

This is an old discussion and doesn't know about the wrapper. (FindwxWidgets doesn't seem to work well MinGW, but the wrapper was tested with wxWidgets 3.1.5.)

I was able to reproduce the new problem on Windows ... when sh was not in the PATH.

Can you test again? For native mingw builds (on windows), I switched to the MSVC layout, so that the find module can operatore in win32 mode, not needing sh for wx-config.
Downside: there is no wx-config for mingw on windows.

Can you test again? For native mingw builds (on windows), I switched to the MSVC layout, so that the find module can operatore in win32 mode, not needing sh for wx-config. Downside: there is no wx-config for mingw on windows.

Now the cmake configuration problem is fixed, but unfortunately, I am getting numerous "undefined reference to" errors at linking status, and I am sure that I'm exactly following the cmake integration instruction add these code in CMakeLists.txt:
find_package(wxWidgets REQUIRED)
target_compile_definitions(${MY_EXECUTABLE} PRIVATE ${wxWidgets_DEFINITIONS} "$<$<CONFIG:DEBUG>:${wxWidgets_DEFINITIONS_DEBUG}>")
target_include_directories(${MY_EXECUTABLE} PRIVATE ${wxWidgets_INCLUDE_DIRS})
target_link_libraries(${MY_EXECUTABLE} PRIVATE ${wxWidgets_LIBRARIES})

The cmake log reports that it had found the libraries of wxWidgets (but some components are missing):
-- Found wxWidgets: C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxmsw31ud_core.a;C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxbase31ud.a;winmm;comctl32;uuid;oleacc;uxtheme;rpcrt4;shlwapi;version;wsock32 (found version "3.1.7") found components: core base missing components: png tiff jpeg zlib regex expat
-- Found wxWidgets: debug;C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxmsw31ud_core.a;optimized;C:/dev/vcpkg/installed/x64-mingw-dynamic/lib/libwxmsw31u_core.a;debug;C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxbase31ud.a;optimized;C:/dev/vcpkg/installed/x64-mingw-dynamic/lib/libwxbase31u.a;winmm;comctl32;uuid;oleacc;uxtheme;rpcrt4;shlwapi;version;wsock32 (found version "3.1.7") found components: core base missing components: png tiff jpeg zlib regex expat
-- Configuring done
-- Generating done

And there is the compile log:
====================[ Build | wxwidghets_hello | Debug ]========================
"C:\Program Files\CMake\bin\cmake.exe" --build C:\Users\user\Desktop\OpenGL\ProgramPlayground\Wxwidget\out\debug --target wxwidghets_hello -j 16
[0/2] Re-checking globbed directories...
[1/1] Linking CXX executable wxwidghets_hello.exe
FAILED: wxwidghets_hello.exe
cmd.exe /C "cd . && C:\dev\TDM-GCC-64\bin\c++.exe -g  CMakeFiles/wxwidghets_hello.dir/src/auidemo.cpp.obj -o wxwidghets_hello.exe -Wl,--out-implib,libwxwidghets_hello.dll.a -Wl,--major-image-version,0,--minor-image-version,0  C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxmsw31ud_core.a  C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/lib/libwxbase31ud.a  -lwinmm  -lcomctl32  -luuid  -loleacc  -luxtheme  -lrpcrt4  -lshlwapi  -lversion  -lwsock32  -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 && cmd.exe /C "cd /D C:\Users\user\Desktop\OpenGL\ProgramPlayground\Wxwidget\out\debug && "C:\Program Files\PowerShell\7\pwsh.exe" -noprofile -executionpolicy Bypass -file C:/dev/vcpkg/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary C:/Users/user/Desktop/OpenGL/ProgramPlayground/Wxwidget/out/debug/wxwidghets_hello.exe -installedDir C:/dev/vcpkg/installed/x64-mingw-dynamic/debug/bin -OutVariable out""
C:/dev/TDM-GCC-64/bin/../lib/gcc/x86_64-w64-mingw32/10.3.0/../../../../x86_64-w64-mingw32/bin/ld.exe: CMakeFiles/wxwidghets_hello.dir/src/auidemo.cpp.obj: in function `MyFrame::MyFrame(wxWindow*, int, wxString const&, wxPoint const&, wxSize const&, long)':
C:/Users/user/Desktop/OpenGL/ProgramPlayground/Wxwidget/src/auidemo.cpp:652: undefined reference to `__imp__ZN12wxAuiManagerC1EP8wxWindowj'
...
...
(a lot of undefined reference to errors)
...
...
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

I don't why it crashed by this problem, and I've tried use x64-windows and MSVC, I got the same linking issues.
PS: I use TDM-GCC, does it cause the influence?

missing components: png tiff jpeg zlib regex expat

These components are implicitly added in win32 mode of FindwxWidgets but it is not an error if they are missing unless requested explicitly. Maybe this eventually needs to be resolved, for explicit requests. But do the linking errors point to these libs?

C:/Users/user/Desktop/OpenGL/ProgramPlayground/Wxwidget/src/auidemo.cpp:652: undefined reference to '__imp__ZN12wxAuiManagerC1EP8wxWindowj'

I'm not an wxWidgets expert. I guess you need to also request the aui component with the find_package(wxWidgets call. IIRC each lib is a separate component in wxWidgets. From the CI file list:
wxwidgets:x64-windows:/lib/wxbase31u.lib
wxwidgets:x64-windows:/lib/wxbase31u_net.lib
wxwidgets:x64-windows:/lib/wxbase31u_xml.lib
wxwidgets:x64-windows:/lib/wxmsw31u_adv.lib
wxwidgets:x64-windows:/lib/wxmsw31u_aui.lib
wxwidgets:x64-windows:/lib/wxmsw31u_core.lib
wxwidgets:x64-windows:/lib/wxmsw31u_gl.lib
wxwidgets:x64-windows:/lib/wxmsw31u_html.lib
wxwidgets:x64-windows:/lib/wxmsw31u_media.lib
wxwidgets:x64-windows:/lib/wxmsw31u_propgrid.lib
wxwidgets:x64-windows:/lib/wxmsw31u_qa.lib
wxwidgets:x64-windows:/lib/wxmsw31u_ribbon.lib
wxwidgets:x64-windows:/lib/wxmsw31u_richtext.lib
wxwidgets:x64-windows:/lib/wxmsw31u_stc.lib
wxwidgets:x64-windows:/lib/wxmsw31u_webview.lib
wxwidgets:x64-windows:/lib/wxmsw31u_xrc.lib

The default components were printed by CMake: found components: core base.
Cf. https://docs.wxwidgets.org/trunk/overview_cmake.html#cmake_find_package


Can't add extension to Firefox, after the Firefox support release

Describe the bug
Trying to add the extension to Firefox via "Install from file" fails because "the app appears to be corrupt":

To Reproduce
Try adding the newest release to Firefox
Expected behavior
A clear and concise description of what you expected to happen.
Environment

Firefox Version 124.0.1 (64-bit)
Devtools version 2.2.0 .zip Release [e.g. 1.3.1, built from master]

Additional context
Running on Windows 11

You need to add this through Load Temporary Add-on in about:debugging:
https://extensionworkshop.com/documentation/develop/temporary-installation-in-firefox/

Yes, please load it as a temporary add-on for the time being. We're still in the process of validating the extension before it can be loaded from "Install from file". I'll adjust the title to reflect it clearer.

Per v2.2.1 release, .xpi files are now available to download and install for Firefox.

Looks like README still needs to be updated to reflect the xpi files being available

@rdrpenguin04 thanks! #221


Worked on list file entries script and documentation

Codecov Report

Merging #12 (e81507c) into main (abbc0bf) will increase coverage by 0.55%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   77.04%   77.60%   +0.55%
==========================================
  Files           2        2
  Lines         122      125       +3
==========================================
+ Hits           94       97       +3
  Misses         28       28

Impacted Files
Coverage Δ

imagetools/file_entry_lister.py
90.09% <100.00%> (+0.30%)
:arrow_up:

Continue to review full report at Codecov.

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


My Feed has gone down but been working fine for months prior

Hey
I'm Currently getting the following console error, I have tried this across multiple different network connections both hardwired and over Wifi in different location and on a few different machines so I'm sure it's not just my network connection. I'm using the latest jQuery cdn and not changed my Instagram details at all.

Note this is happening on all browsers not just chrome, has anyone experienced this or know of any updates Instagram has made to their API recent to cause this.
Resource (console link)
https://www.chromestatus.com/feature/5718547946799104
Website
http://www.prepre73.co.uk/
Thanks

seems to be related to my web host getting attacked I have contacted them


running jar like in example creates empty directory

When I run the builder-jar like in the provided example, on pbf-files generated by the sharedstreets-matcher, a lot of lines appear in the terminal (see example below), but no files are created in the designated output directory. What could be the reason for this? How can I fix this?
Sample of terminal output:
02/13/2019 10:22:16     DataSink (io.sharedstreets.tools.builder.tiles.ProtoTileOutputFormat@275710fc)(1/8) switched to SCHEDULED 02/13/2019 10:22:16     DataSink (io.sharedstreets.tools.builder.tiles.ProtoTileOutputFormat@275710fc)(1/8) switched to DEPLOYING 02/13/2019 10:22:16     Partition(1/8) switched to FINISHED 02/13/2019 10:22:16     DataSink (io.sharedstreets.tools.builder.tiles.ProtoTileOutputFormat@275710fc)(5/8) switched to RUNNING 02/13/2019 10:22:16     DataSink (io.sharedstreets.tools.builder.tiles.ProtoTileOutputFormat@275710fc)(2/8) switched to RUNNING 02/13/2019 10:22:16     DataSink (io.sharedstreets.tools.builder.tiles.ProtoTileOutputFormat@6b53e23f)(3/8) switched to RUNNING

builder-jar is not intended to be run on pdf-files created by sharedstreets-matcher, but on OSM-pbf files to extract SharedStreets tiles, which themselves serve as input to sharedstreets-matcher.


.jar file of this library

How can i use this library on eclipse,how to get .jar file.
Thank you.

In Eclipse you can import these java files in your project.
https://github.com/Cutta/MultipleImagePicker/tree/master/app/src/main/java/com/cunoraz/pickImages
After that for using it , follow here:
https://github.com/Cutta/MultipleImagePicker#usage

Thank you(Tesekurler)

You are welcome


add bundle

This pull request adds the disgo.go bundle with fieldalignment.

Does adding a copy of wrapper (the bundle) make the binary larger? No. To start, the number is lower than stated because I forgot to import the cost of importing fmt. In addition, the compiler will ignore certain packages that remain unused. Such that importing fmt and disgo totals 6.5 MB. Importing disgo and wrapper only increases the amount slightly more. So either the method to achieve this measurement is extremely wrong, or disgo only adds 4.7 MB (rounded up to 5 MB).
The command example is only 10.8 MB despite importing a bit more than fmt and disgo.

The main concern with using fieldalignment is that it removes comments. This occurs presumably due to https://github.com/golang/go/issues/20744 which prevents the tool from maintaining comment positions. One way to solve this is to add an additional step to the bundle (disgo) tool to replace fieldaligned structs with removed comments with field aligned structs that maintain comments.
>fieldalignment -fix disgo.go
disgo.go:92:20: struct with 96 pointer bytes could be 88
disgo.go:135:14: struct with 48 pointer bytes could be 24
disgo.go:203:14: struct with 40 pointer bytes could be 32
disgo.go:312:28: struct with 32 pointer bytes could be 24
disgo.go:463:26: struct with 32 pointer bytes could be 24
disgo.go:928:12: struct with 88 pointer bytes could be 64
disgo.go:978:36: struct with 128 pointer bytes could be 112
disgo.go:1047:26: struct with 72 pointer bytes could be 64
disgo.go:1057:24: struct with 40 pointer bytes could be 32
disgo.go:1086:18: struct with 24 pointer bytes could be 16
disgo.go:1093:21: struct with 24 pointer bytes could be 16
disgo.go:1120:21: struct with 24 pointer bytes could be 16
disgo.go:1127:24: struct with 24 pointer bytes could be 16
disgo.go:1140:24: struct with 112 pointer bytes could be 80
disgo.go:1152:22: struct with 24 pointer bytes could be 16
disgo.go:1159:22: struct with 24 pointer bytes could be 16
disgo.go:1221:24: struct with 40 pointer bytes could be 32
disgo.go:1235:19: struct with 112 pointer bytes could be 88
disgo.go:1272:20: struct with 40 pointer bytes could be 32
disgo.go:1280:24: struct with 48 pointer bytes could be 32
disgo.go:1288:25: struct with 72 pointer bytes could be 64
disgo.go:1299:28: struct with 64 pointer bytes could be 56
disgo.go:1309:31: struct with 40 pointer bytes could be 32
disgo.go:1317:33: struct with 48 pointer bytes could be 40
disgo.go:1326:21: struct with 72 pointer bytes could be 56
disgo.go:1354:18: struct with 72 pointer bytes could be 64
disgo.go:1376:24: struct with 40 pointer bytes could be 32
disgo.go:1391:21: struct with 48 pointer bytes could be 24
disgo.go:1400:28: struct with 32 pointer bytes could be 16
disgo.go:1545:15: struct with 96 pointer bytes could be 88
disgo.go:1579:26: struct with 72 pointer bytes could be 48
disgo.go:1590:30: struct with 24 pointer bytes could be 16
disgo.go:1599:28: struct with 40 pointer bytes could be 32
disgo.go:1632:22: struct with 64 pointer bytes could be 24
disgo.go:1765:37: struct with 88 pointer bytes could be 72
disgo.go:1786:35: struct with 88 pointer bytes could be 72
disgo.go:1814:34: struct with 24 pointer bytes could be 16
disgo.go:1822:36: struct with 96 pointer bytes could be 80
disgo.go:1844:34: struct with 96 pointer bytes could be 80
disgo.go:1905:32: struct with 40 pointer bytes could be 32
disgo.go:1914:37: struct with 24 pointer bytes could be 16
disgo.go:1922:38: struct with 104 pointer bytes could be 88
disgo.go:1944:28: struct with 192 pointer bytes could be 176
disgo.go:1964:25: struct with 40 pointer bytes could be 32
disgo.go:1973:26: struct with 120 pointer bytes could be 104
disgo.go:1997:23: struct with 48 pointer bytes could be 40
disgo.go:2025:31: struct with 112 pointer bytes could be 104
disgo.go:2078:27: struct with 32 pointer bytes could be 24
disgo.go:2087:25: struct with 176 pointer bytes could be 160
disgo.go:2134:25: struct with 48 pointer bytes could be 40
disgo.go:2153:20: struct with 184 pointer bytes could be 168
disgo.go:2207:19: struct with 64 pointer bytes could be 56
disgo.go:2235:18: struct with 104 pointer bytes could be 88
disgo.go:2266:29: struct with 48 pointer bytes could be 40
disgo.go:2284:26: struct with 64 pointer bytes could be 56
disgo.go:2344:26: struct with 56 pointer bytes could be 48
disgo.go:2362:29: struct with 64 pointer bytes could be 56
disgo.go:2373:32: struct with 64 pointer bytes could be 56
disgo.go:2396:31: struct with 144 pointer bytes could be 128
disgo.go:2455:32: struct with 32 pointer bytes could be 24
disgo.go:2464:33: struct with 32 pointer bytes could be 24
disgo.go:2473:39: struct with 32 pointer bytes could be 24
disgo.go:2507:23: struct with 48 pointer bytes could be 40
disgo.go:2525:18: struct with 136 pointer bytes could be 120
disgo.go:2543:15: struct with 24 pointer bytes could be 16
disgo.go:2558:18: struct with 192 pointer bytes could be 168
disgo.go:2598:25: struct with 152 pointer bytes could be 144
disgo.go:2628:43: struct with 40 pointer bytes could be 32
disgo.go:2653:23: struct with 32 pointer bytes could be 24
disgo.go:2662:25: struct with 40 pointer bytes could be 32
disgo.go:2671:21: struct with 96 pointer bytes could be 80
disgo.go:2684:24: struct with 80 pointer bytes could be 72
disgo.go:2698:26: struct with 24 pointer bytes could be 16
disgo.go:2732:19: struct with 40 pointer bytes could be 32
disgo.go:2750:21: struct with 40 pointer bytes could be 32
disgo.go:2774:22: struct with 72 pointer bytes could be 64
disgo.go:2795:40: struct with 24 pointer bytes could be 16
disgo.go:2803:22: struct with 88 pointer bytes could be 80
disgo.go:2834:25: struct with 32 pointer bytes could be 24
disgo.go:2843:22: struct with 40 pointer bytes could be 24
disgo.go:2903:24: struct with 24 pointer bytes could be 16
disgo.go:2912:26: struct with 24 pointer bytes could be 16
disgo.go:2940:31: struct with 40 pointer bytes could be 32
disgo.go:2950:34: struct with 40 pointer bytes could be 32
disgo.go:2960:27: struct with 56 pointer bytes could be 48
disgo.go:2970:34: struct with 24 pointer bytes could be 16
disgo.go:2978:32: struct with 112 pointer bytes could be 96
disgo.go:2994:29: struct with 40 pointer bytes could be 32
disgo.go:3003:32: struct with 112 pointer bytes could be 104
disgo.go:3029:34: struct with 64 pointer bytes could be 56
disgo.go:3048:35: struct with 40 pointer bytes could be 32
disgo.go:3064:26: struct with 40 pointer bytes could be 32
disgo.go:3081:26: struct with 48 pointer bytes could be 40
disgo.go:3099:16: struct with 40 pointer bytes could be 32
disgo.go:3116:26: struct with 48 pointer bytes could be 40
disgo.go:3133:26: struct with 32 pointer bytes could be 24
disgo.go:3187:25: struct with 56 pointer bytes could be 48
disgo.go:3256:20: struct with 32 pointer bytes could be 16
disgo.go:3274:20: struct with 40 pointer bytes could be 32
disgo.go:3312:20: struct with 40 pointer bytes could be 32
disgo.go:3322:29: struct with 48 pointer bytes could be 40
disgo.go:3347:21: struct with 200 pointer bytes could be 184
disgo.go:3368:36: struct with 48 pointer bytes could be 40
disgo.go:3378:37: struct with 48 pointer bytes could be 40
disgo.go:3388:24: struct with 56 pointer bytes could be 48
disgo.go:3398:25: struct with 120 pointer bytes could be 104
disgo.go:3414:27: struct with 56 pointer bytes could be 48
disgo.go:3485:14: struct with 48 pointer bytes could be 40
disgo.go:3495:25: struct with 144 pointer bytes could be 136
disgo.go:3520:31: struct with 176 pointer bytes could be 152
disgo.go:3612:13: struct with 48 pointer bytes could be 40
disgo.go:3637:17: struct with 104 pointer bytes could be 80
disgo.go:3650:23: struct with 56 pointer bytes could be 48
disgo.go:3660:16: struct with 72 pointer bytes could be 56
disgo.go:3680:18: struct with 144 pointer bytes could be 120
disgo.go:3715:29: struct with 88 pointer bytes could be 64
disgo.go:3727:27: struct with 32 pointer bytes could be 24
disgo.go:3753:46: struct with 64 pointer bytes could be 40
disgo.go:3763:25: struct with 56 pointer bytes could be 40
disgo.go:3773:26: struct with 24 pointer bytes could be 16
disgo.go:3824:18: struct with 216 pointer bytes could be 192
disgo.go:3863:20: struct with 32 pointer bytes could be 24
disgo.go:3882:20: struct with 80 pointer bytes could be 56
disgo.go:3969:21: struct with 56 pointer bytes could be 48
disgo.go:3980:25: struct of size 256 could be 248
disgo.go:4031:27: struct with 16 pointer bytes could be 8
disgo.go:4053:14: struct with 336 pointer bytes could be 320
disgo.go:4129:14: struct of size 432 could be 416
disgo.go:4198:22: struct with 16 pointer bytes could be 8
disgo.go:4244:15: struct with 24 pointer bytes could be 8
disgo.go:4252:26: struct with 48 pointer bytes could be 40
disgo.go:4261:21: struct of size 64 could be 56
disgo.go:4288:15: struct with 64 pointer bytes could be 48
disgo.go:4316:21: struct with 40 pointer bytes could be 32
disgo.go:4334:17: struct with 40 pointer bytes could be 32
disgo.go:4350:18: struct with 40 pointer bytes could be 32
disgo.go:4359:18: struct with 32 pointer bytes could be 24
disgo.go:4367:17: struct with 40 pointer bytes could be 32
disgo.go:4387:17: struct with 112 pointer bytes could be 96
disgo.go:4428:12: struct with 80 pointer bytes could be 64
disgo.go:4441:12: struct of size 416 could be 384
disgo.go:4588:19: struct with 136 pointer bytes could be 120
disgo.go:4604:26: struct with 16 pointer bytes could be 8
disgo.go:4622:18: struct with 112 pointer bytes could be 88
disgo.go:4673:29: struct with 64 pointer bytes could be 56
disgo.go:4697:27: struct with 40 pointer bytes could be 32
disgo.go:4706:26: struct with 152 pointer bytes could be 136
disgo.go:4756:30: struct with 32 pointer bytes could be 24
disgo.go:4764:20: struct with 152 pointer bytes could be 136
disgo.go:4780:13: struct with 96 pointer bytes could be 88
disgo.go:4803:21: struct with 56 pointer bytes could be 24
disgo.go:4813:20: struct with 80 pointer bytes could be 64
disgo.go:4831:14: struct with 112 pointer bytes could be 96
disgo.go:4871:18: struct with 104 pointer bytes could be 88
disgo.go:4883:11: struct with 144 pointer bytes could be 136
disgo.go:4955:17: struct of size 88 could be 80
disgo.go:4983:14: struct with 104 pointer bytes could be 88
disgo.go:5060:11: struct of size 104 could be 96
disgo.go:5084:11: struct with 80 pointer bytes could be 72
disgo.go:5095:17: struct with 56 pointer bytes could be 32
disgo.go:5119:15: struct with 128 pointer bytes could be 104
disgo.go:5157:20: struct with 32 pointer bytes could be 24
disgo.go:5291:46: struct with 48 pointer bytes could be 32
disgo.go:5306:28: struct with 24 pointer bytes could be 16
disgo.go:5325:26: struct with 64 pointer bytes could be 56
disgo.go:5335:18: struct with 64 pointer bytes could be 56
disgo.go:5345:43: struct with 48 pointer bytes could be 40
disgo.go:5354:27: struct with 80 pointer bytes could be 64
disgo.go:5365:50: struct with 72 pointer bytes could be 64
disgo.go:6532:19: struct with 96 pointer bytes could be 88
disgo.go:6595:24: struct with 48 pointer bytes could be 40
disgo.go:6645:19: struct with 32 pointer bytes could be 24
disgo.go:6663:22: struct with 48 pointer bytes could be 40
disgo.go:10088:20: struct with 48 pointer bytes could be 32
disgo.go:10526:16: struct with 48 pointer bytes could be 32
disgo.go:10971:13: struct with 72 pointer bytes could be 56
disgo.go:16959:14: struct with 80 pointer bytes could be 64
disgo.go:17526:16: struct with 24 pointer bytes could be 16
disgo.go:17799:14: struct with 64 pointer bytes could be 40

The following structs have their field comments removed.
Authorization
Request
Gateway

ErrorRequest
ErrorEventHandler
ErrorSession
ErrorDisconnect

BotAuthParams

RateLimit
Bucket
Session

heartbeat (unexported)
manager (unexported)

GetGuildWidgetImage
GetGuildAuditLog
Message
Guild

The following structs have their field comments removed.
Gateway
Session

heartbeat (unexported)
manager (unexported)

GetGuildWidgetImage
GetGuildAuditLog
Message
Guild

Failure explained by https://stackoverflow.com/questions/54090404/what-is-causing-this-data-race


Update devcontainer.json reference to mirror spec

Pulls in changes from devcontainers/spec#122, devcontainers/spec#124

Thanks so much for opening! I explain within these PRs, but I propose using https://github.com/devcontainers/devcontainers.github.io/pull/54 (or pulling its changes into this PR - totally fine with either getting merged).

Closing in favor of #54


Resend webhook payloads from everywhere the result is displayed

Feature Description
While it is possible to resend webhooks from the webhook configuration page, it is not very convenient. If a build fails for technical reasons (timeout, build server problems, dependency problems or whatever that has not to be fixed by fixing the code itself, it would be very helpful if it could be triggered again from where the result is display (be it the commit history or pull request). Especially, since the build may have failed while the webhook itself is succesful, so it is very complicated to find the correct one from the recent deliveries.
Screenshots
No response

Webhooks != Statuses on commits. You can set statuses on commits without even needing a webhook active on a repo.

Webhooks != Statuses on commits. You can set statuses on commits without even needing a webhook active on a repo.

I don't see how answer relates to the feature request. Everywhere the webhook result is displayed, there is also a link to the "Details". I don't see why it should not be possible to add a replay button. Could you please elaborate and/or reopen the issue?

It would be very nice if you could explain why this is not a valid feature request.

Because you don't know the commit statuses come from which webhook or a cron task. At least you cannot track that both in Github and Gitea.


Driving the target person with an audio input

Hello,
Given an audio input, how do I render the full length of animation of the target person? I tried the command in the README, but it seemed only part of the animation was rendered.
python NeRFs/TorsoNeRF/run_nerf.py --config dataset/$id/TorsoNeRFTest_config.txt --aud_file=${deepspeechfile.npy} --test_size=-1

Hi, please refer to #44

Thank you for your answer. It works now


Fatal Error when creating DB with hive

Hi, I have question on connecting superset with hive server or Apache Spark SQL.
I have initialized a Spark cluster with hive server which I can already connect with beeline as you can see in the following image.

I try to first startup a superset instance located at the same instance of spark master node. However, I got a Fatal Error message without any detail information. In the following image, you can see that connection looks good.

However, when clicking on Connect, you can see that there is a Database Creation Error.

What does it mean ?
I also attach ERROR message obtained from superset instance.
2023-05-11 22:25:08,222:ERROR:flask_appbuilder.api:Object of type bytes is not JSON serializable
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/flask_appbuilder/api/__init__.py", line 110, in wraps
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/superset/views/base_api.py", line 122, in wraps
    raise ex
  File "/usr/local/lib/python3.8/dist-packages/superset/views/base_api.py", line 113, in wraps
    duration, response = time_function(f, self, *args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/superset/utils/core.py", line 1586, in time_function
    response = func(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/superset/utils/log.py", line 266, in wrapper
    value = f(*args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/superset/views/base_api.py", line 85, in wraps
    return f(self, *args, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/superset/databases/api.py", line 345, in post
    return self.response(201, id=new_model.id, result=item)
  File "/usr/local/lib/python3.8/dist-packages/flask_appbuilder/api/__init__.py", line 769, in response
    _ret_json = jsonify(kwargs)
  File "/usr/local/lib/python3.8/dist-packages/flask/json/__init__.py", line 302, in jsonify
    f"{dumps(data, indent=indent, separators=separators)}\n",
  File "/usr/local/lib/python3.8/dist-packages/flask/json/__init__.py", line 132, in dumps
    return _json.dumps(obj, **kwargs)
  File "/usr/lib/python3.8/json/__init__.py", line 234, in dumps
    return cls(
  File "/usr/lib/python3.8/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/usr/lib/python3.8/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
  File "/usr/local/lib/python3.8/dist-packages/flask/json/__init__.py", line 51, in default
    return super().default(o)
  File "/usr/lib/python3.8/json/encoder.py", line 179, in default
    raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type bytes is not JSON serializable

It seems that even with Database Creation Error, there is still a Database Connection created.

However, there is error which can not recognize correctly database and table. I try to use dataset function however it only detect database-level item.

i have the same error

Me too, I have the same problem with Apache Hive in version 2.1.0

Finally, we solved this problem by following Usiel's solution:
https://github.com/Usiel/PyHive/commit/fb692d956758bca9d4aba980a8c418cc5788768d?diff=split
by changing those two lines in the sqlalchemy_hive.py file:
class HiveDialect(default.DefaultDialect):
name = b'hive'
driver = b'thrift'
to this:
class HiveDialect(default.DefaultDialect):
name = 'hive'
driver = 'thrift'
Alternatively, you can simply use the latest version of PyHive, which already contains these changes.

Finally, we solved this problem by following Usiel's solution:
Usiel/PyHive@fb692d9?diff=split
by changing those two lines in the sqlalchemy_hive.py file:
class HiveDialect(default.DefaultDialect): name = b'hive' driver = b'thrift'
to this:
class HiveDialect(default.DefaultDialect): name = 'hive' driver = 'thrift'
Alternatively, you can simply use the latest version of PyHive, which already contains these changes.

Amazing! Thanks a lot.

It seems to be a duplicate of https://github.com/apache/superset/issues/22316
Give pyhive 0.7.0 a try, as I recall there was a contribution fixing this issue.


Made changes to editor's toolbox.

Made the toolbox more uniform and fixed the design.
Fixes #879

@anushbhatia Please give your feedback for this

Please review it @smaranjitghose @ashuvssut @anushbhatia

How to resolve this merge conflict?

ok
i will give u pr that resolves this

this should solve ur issue

I am sorry but still not getting how to solve the issue because I can't just delete the code that it's highlighting.
Is it up to the maintainers to check and solve this issue?
Or I have to make a new commit?

@Rishab-j  see my dm in discord server.

I reviewed you code. And in the deploy preview I can see that you have messed up the Navbar in mobile screen

Your work was to make changes to editor's toolbox. you unnecessarily made changes to "navbar"

Alright, I'll review my code and make a new PR.


Fix inconsistancy on + and / commands

This is quite confusing, for example, the info command only works if you do /info but not +info, but the help command only works if you do +help but not if you do /help command!?!?!?
(p.s. this isn't me just bitching, it's also kinda a todo list for if i wanna do stuff for kitebot :trollface:)

That is because /info is a completely different kind of command. Slash commands are different from prefixed commands


Fix git push error for protected CLA branch

The pull request is created from master636964775633815331 to master to fix git push error for protected CLA branch

@gewarren : Thanks for your contribution! The author(s) have been notified to review your proposed change. @gewarren, @bytesguy


Module 1.1 Assignment

Given what you have learned about Git, why would you want to use Git in your classroom?

Efficiency, Version Control.


Right-click on Apply Changes list for a "Reset status for all packages" option.

This would allow people to retry installation with different settings without having to re-open the Apply Changes window.

Maybe an option for resetting a selected package's status would be helpful, too. That would require checking how many packages are "ready" and only include "ready" packages in the bulk apply changes thing, though. Could be a bit too much work at the moment.

Delaying this since it would be too much to fully test this late in development.

This is now complete enough for the issue to be closed.


refactor(SuperMediaPlayer): stop demuxer asap on stop

Signed-off-by: pingkai<EMAIL_ADDRESS>

Codecov Report

Merging #76 into develop will decrease coverage by 0.44%.
The diff coverage is 95.65%.

@@             Coverage Diff             @@
##           develop      #76      +/-   ##
===========================================
- Coverage    68.08%   67.63%   -0.45%
===========================================
  Files          200      200
  Lines        10580    10583       +3
===========================================
- Hits          7203     7158      -45
- Misses        3377     3425      +48

Impacted Files
Coverage Δ

mediaPlayer/SuperMediaPlayer.cpp
75.78% <95.65%> (+2.04%)
:arrow_up:

framework/tests/dataSource/ipList.h
0% <0%> (-100%)
:arrow_down:

framework/tests/demuxer/demuxerUnitTest.cpp
0% <0%> (-100%)
:arrow_down:

framework/tests/decoder/decoderUnitTest.cpp
0% <0%> (-93.48%)
:arrow_down:

framework/tests/dataSource/dataSourceUnitTest.cpp
0% <0%> (-93.34%)
:arrow_down:

framework/tests/demuxer/demuxerUtils.cpp
0% <0%> (-76%)
:arrow_down:

framework/data_source/ffmpeg_data_source.cpp
9.37% <0%> (-65.63%)
:arrow_down:

framework/demuxer/AVBSF.cpp
25.27% <0%> (-42.86%)
:arrow_down:

framework/data_source/curl/CURLShareInstance.cpp
69.44% <0%> (-27.78%)
:arrow_down:

mediaPlayer/system_refer_clock.cpp
79.16% <0%> (-16.67%)
:arrow_down:

... and 30 more

Continue to review full report at Codecov.

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


Fix aks get-credentials command

Replace
az aks get-credentials --resource-group  -name
by
az aks get-credentials --resource-group  --name
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 43ee195b-c035-b21c-fdd1-9f60d4a75446
Version Independent ID: d1211d43-ca7a-94bd-5c8b-2feffa3a4b2e
Content: Azure Kubernetes Service (AKS) managed NGINX ingress with the application routing add-on - Azure Kubernetes Service
Content Source: articles/aks/app-routing.md
Service: azure-kubernetes-service
Sub-service: aks-networking
GitHub Login: @asudbring
Microsoft Alias: allensu

@AndreiMatrosau
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:schaffererin


M5-0-*: Ignore explicit casts when identifying cvalues by parent

Description
Fixes https://github.com/github/codeql-coding-standards/issues/602.
Function argument expressions and return expressions are both considered to be cvalues. However, they shouldn't be considered as cvalues if they are explicitly casted.
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[x] Query files (.ql, .qll, .qls or unit tests)
[ ] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[ ] No rules added
[ ] Queries have been added for the following rules:

rule number here

[x] Queries have been modified for the following rules:

M5-0-3
M5-0-7
M5-0-8
M5-0-9

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[x] Yes
[ ] No

🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.

[ ] Confirmed

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[x] Have all the relevant rule package description files been checked in?
[x] Have you verified that the metadata properties of each new query is set appropriately?
[x] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[x] Are the alert messages properly formatted and consistent with the style guide?
[x] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[x] Does the query have an appropriate level of in-query comments/documentation?
[x] Have you considered/identified possible edge cases?
[x] Does the query not reinvent features in the standard library?
[x] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

@MichaelRFairhurst ready for re-review.


Document default filetypes

autolist.nvim is great! However, both the README and the help are a bit vague on what a 'list marker' is or what syntax is supported. Having read through some of the code, I now know it's targeted at Markdown files primarily. However, there are other markup formats, like AsciiDoc, LaTeX, etc. which could all be potentially supported by autolist.nvim. I don't know if you have any plans to support them, but highlighting what's supported today might make it easier for folks to adopt your plugin. Just a thought.
Thanks for working hard to create this!

Hi, I'm currently debating on whether to support all lists, like latex HTML, but that increases the complexity of the plugin, which is made to be minimal. The other option is to make a new repository, but it would be a hassle to keep both up to date. What do you think?

Well, FWIW, I would definitely not split these out into separate plugins. There are plugins a lot more complex than this one! You might have to do some modularization, but I think improving the "quality of living" for lists generally is worthy of a single plugin. I think you'll find there's more commonality than difference between those filetypes.
Just to be clear though, that wasn't my original motivation for the issue; that was simply a suggestion to clarify the documentation so that folks understand what it does today :) It's not even 100% clear what you mean by "list" - do you mean the quickfix list, for example? I would just suggest a few examples and some clarification over what filetype(s) are supported today...

Thanks for that, I will now commit to one plugin, and to answer the main issue, I will put in a filler video, and create a better one when I have the time.


React app not rendering inside react-native-webview

Recently I am facing an issue. I tried stackoverflow but no one help me to find the actual solution.
I am planning to show my react app inside react-native-webview. I implement the code for WebView. When I put URL https://www.w3schools.com , It works perfectly. But when I used my react app URL https://jshossen.com/ it not rendering anything. It only shows a white screen. Anyone help me with whats I have to do to run React App inside WebView?
This is the question details

Its working fine. Problem in my .htaccess file. I set all url redirect to index.html file and it is working perfectly.


[CHERRYPICK] allow sequence fill for v2 AA scripted

#7919
Let's wait for CI in #7159 to show that the bug is indeed resolved.

Looks good on #7159.