missing runtime_dependency on json

rubocop gemspec should specify runtime depency on json as it is required to run
$ ruby -v
ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
$ rubocop -v
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- json (LoadError) 	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require'
from /usr/local/share/gems/gems/rubocop-0.31.0/lib/rubocop/formatter/json_formatter.rb:3:in <top (required)>' 	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require' 	from /usr/local/share/gems/gems/rubocop-0.31.0/lib/rubocop.rb:308:in <top (required)>'
from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require' 	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in require'
from /usr/local/share/gems/gems/rubocop-0.31.0/bin/rubocop:6:in <top (required)>' 	from /usr/local/bin/rubocop:23:in load'
from /usr/local/bin/rubocop:23:in `'

json is part of the standard library. See https://github.com/bbatsov/rubocop/pull/755

I see,  then we can close this issue.


No vibration or pop-up

When I send a Push Notificaion from phone (API 24) to my LG Sports Wear (Wear 2.0), it does not vibrate or even show the small slide up notification. The user has no idea that a push notification is there. The same problem is also happening in my app.
The vibration works fine for apps like Gmail.
Here's my notification builder:
 //Create android wear dismissal sync id
            NotificationCompat.WearableExtender wearableExtender = new NotificationCompat.WearableExtender()
                    .setDismissalId(messageKey);
            // Construct notification
            NotificationCompat.Builder mBuilder = new NotificationCompat.Builder(context)
                    .extend(wearableExtender)
                    .setSmallIcon(R.drawable.statusbar_icon)
                    .setColor(ContextCompat.getColor(context, R.color.colorAccent))
                    .setContentTitle(contentTitle)
                    .setContentText(collapsedSummary)
                    .setAutoCancel(true)
                    .setLights(Color.BLUE, 100, 1900)
                    .setPriority(NotificationCompat.PRIORITY_HIGH)
                    .setDefaults(NotificationCompat.DEFAULT_SOUND | NotificationCompat.DEFAULT_VIBRATE)
                    .setCategory(Notification.CATEGORY_MESSAGE)
                    .setVisibility(Notification.VISIBILITY_PRIVATE);

Update 1:
The notification was silent because I had the following meta-data in wear manifest.
        <meta-data
            android:name="com.google.android.wearable.notificationBridgeMode"
            android:value="NO_BRIDGING"/>

Just to clarify, this sample only includes NO_BRIDGING as a comment in the Wear Manifest (not as an element), so it should not impact your app unless you specifically uncommented it to disable bridged notifications when your Wear app is installed (common practice for devs using GCM to create Notifications). All that should be called out in the surrounding comments.
I am glad you solved the issue, but the code you pasted doesn't seem to be from the sample. I think this is more a general question about fixing your code? I am going to resolve this issue (reopen if that isn't the case).
You probably want to use stackoverflow.com for those type of issues. I hope that helps, thanks!

Just in case, I will also add setDefaults() in the next push this month so it includes vibrate for bridged notifications..

I will close when push is live.

This was pushed several weeks ago, thanks!


Unable to stop a run

I'm trying to use the API to stop a run:
curl -x POST http://localhost:4400/v1/jobs/prod.example.app/runs/20170119180720D4gdl/action/stop -H "Content-Type: application/json"

I get back
{"message":"","requestPath":"/v1/jobs/prod.example.app/runs/20170119180720D4gdl/action/stop"}

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-1659. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


CodeQL check isn't effective

The CodeQL check doesn't seem to be really running, as there's a build step missing. This can be seen by comparing the time it spent running on this repository against the time spent in a far smaller repository:
https://github.com/jaegertracing/jaeger/runs/1350093965 (1 second)
https://github.com/observatorium/opentelemetry-collector-builder/runs/1332531786 (1 minute 28 seconds)

cc @jhutchings1

👋🏻  Hey folks, I had a look at your runs, and it looks good from my end. The check you linked above for jaeger, @jpkrohling, is actually the results check, which is where we post analysis asynchronously after it's been analyzed. The one where you'll see the build effort is here:  https://github.com/jaegertracing/jaeger/actions?query=workflow%3A"Code+Scanning+-+Action"
With that said, we've updated some of our best practices, so you can actually improve your performance a bit if you make an update to your workflow as follows. This will switch to matrix analysis of Python and Go, and switch from head commit to merge commit analysis.
name: "CodeQL"

on:
  push:
    branches: [ master ]
  pull_request:
    # The branches below must be a subset of the branches above
    branches: [ master ]
  schedule:
    - cron: '31 6 * * 1'

jobs:
  analyze:
    name: Analyze
    runs-on: ubuntu-latest

    strategy:
      fail-fast: false
      matrix:
        language: [ 'go', 'python' ]
        # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
        # Learn more...
        # https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection

    steps:
    - name: Checkout repository
      uses: actions/checkout@v2

    # Initializes the CodeQL tools for scanning.
    - name: Initialize CodeQL
      uses: github/codeql-action/init@v1
      with:
        languages: ${{ matrix.language }}
        # If you wish to specify custom queries, you can do so here or in a config file.
        # By default, queries listed here will override any specified in a config file.
        # Prefix the list here with "+" to use these queries and those in the config file.
        # queries: ./path/to/local/query, your-org/your-repo/queries@main

    # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
    # If this step fails, then you should remove it and run the build manually (see below)
    - name: Autobuild
      uses: github/codeql-action/autobuild@v1

    # ℹ Command-line programs to run using the OS shell.
    # 📚 https://git.io/JvXDl

    # ✏ If the Autobuild fails above, remove it and uncomment the following three lines
    #    and modify them (or add more) to build your code if your project
    #    uses a compiled language

    #- run: |
    #   make bootstrap
    #   make release

    - name: Perform CodeQL Analysis
      uses: github/codeql-action/analyze@v1

Sorry, my bad! I guess it's confirmation bias kicking in, as I found suspicious that there was no build step in the action itself: no autobuild and no alternative run step. It does indeed take around the same amount of time as the one I have as reference: 14m38s (https://github.com/jaegertracing/jaeger/actions/runs/344443399).
Sorry for the noise!


Network isolation of VirtualMachines for KubeVirt provider

When creating a guest cluster with kubevirt provider, we need to enforce isolation on the virtual machines that they won't be able to access other control plane pods or other pods in the management cluster. This PR restricts access only for the required services:

guest's kube-apiserver
ignition server
DNS server
router-ingress
other guest nodes (virt-launchers)

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/hold
/test e2e-kubevirt-aws-ovn

@orenc1 is possible to add some tests for this ?

@orenc1 is possible to add some tests for this ?

you mean functional tests?
wouldn't it be better to cover it in a [sig-kubevirt] conformance test?

kubevirt lane fails due to ODF installation issue
 Error from server (NotFound): deployments.apps "noobaa-operator" not found

/test e2e-kubevirt-aws-ovn

/approve


Remove unnecessary DLCS calls from dashboard collection view

This dropdown menu on multiple manifestations is generated from DigitalManifestations (which includes DLCS asset info) - it doesn't need to do this, and could be generated from MetsManifestations. For multiple manifestations with many members this would speed up the page generation time significantly.

Fixed in https://github.com/wellcomecollection/iiif-builder/pull/204/commits/3959c54b6f4b780c018819d61fd51c0ce27cbd47 as part of DDS/DLCS rollout, rather than leave till later, as everything is being tested now.


[Apple Music] SFSymbols displaying as broken Unicode box character on macOS Ventura

Extension
https://github.com/raycast/extensions/tree/main/extensions/music
Description
The quick lozenge notifications from Raycast after an Apple Music function is performed (e.g. Volume Up via keyboard shortcut) show a broken Unicode character box symbol instead of the intended icon, noted in the code as SFSymbols.SPEAKER_FILL_MINUS.
This is true for all Apple Music commands (Volume Down, Play/Pause, etc.).
Steps To Reproduce

In macOS Ventura 13.4.1 (c)
Install Raycast latest stable (1.56.0)
Install Apple Music extension
Record a Hotkey for Apple Music’s Volume Up command
Press the hotkey and observe Raycast’s notification content

Current Behaviour

Expected Behaviour
It should render a nice speaker icon for Volume Up and the appropriate icons for the various other commands.

Thanks - this has been a reoccurring issue as I don't think SFSymbols are intended to be used outside of xcode.
A fix for now is to download and install SFSymbols from the Apple Developer website.
I'll submit a pr to remove these symbols very soon.

This is now resolved


⚠ Bofrost.at has degraded performance

In 91cc528, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1214 ms

Resolved: Bofrost.at performance has improved in b37f8bf.


Build Framework script not able to unarchive Detox-ios-src.tbz

Description

Installing Detox 6.0.1 results in a broken install as scripts/build_framework.ios.sh fails with;
tar: Ignoring unknown extended header keyword 'SCHILY.dev'
tar: Ignoring unknown extended header keyword 'SCHILY.ino'
tar: Ignoring unknown extended header keyword 'SCHILY.nlink'

bzip2: Compressed file ends unexpectedly;
	perhaps it is corrupted?  *Possible* reason follows.
bzip2: Inappropriate ioctl for device
	Input file = (stdin), output file = (stdout)

It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.

You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.

tar: Ignoring unknown extended header keyword 'SCHILY.dev'
tar: Ignoring unknown extended header keyword 'SCHILY.ino'
tar: Ignoring unknown extended header keyword 'SCHILY.nlink'

Steps to Reproduce

Install Detox 6.0.1 via package manager

Detox, Node, Device, Xcode and macOS Versions

Detox: 6.0.1
Node: v8.9.0
Device: N/A
Xcode: 9.1 (9B55)
macOS: 10.13.1 (17B48)

Device and verbose Detox logs

Fixed in 6.0.2


Introduce a move-session operation to the domain

The moved session map is created eagerly, even if moving is impossible. I'm assuming that most real-life invocations will lead to a valid move so  it shouldn't be a problem.
Fixes #26.
I'm also thinking about a patch that aliases spacy.domain as domain instead of sut. Then I'd shorten all those domain keywords, e.g. :spacy.domain/error → ::domain/error. What do you think?

I'd prefer ::domain/error to :spacy.domain/error 👍


AGP version to 8.2

@bentrengrove It's for compatibility with IntelliJ IDEA and Fleet, which don't support the latest AGP yet.


Important and preference changes

Can you look through these changes? Some are quite important, but some are just preference.

I am new to Github, so I hope I did nothing wrong

Hey gizzmicbob please add me on steam
id = newbrict


Defer closing the gitrepo until the end of the wrapped context functions (#15653)

Backport #15653
There was a mistake in #15372 where deferral of gitrepo close occurs before it should.
This PR fixes this.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

@zeripath please resolve conflict :)

resolved

ugh I messed up with that resolve commits - now fixed


Usage of @EnableCircuitBreaker

can this annotation be targeted at METHODs as well? A @SpringBootApplication can enclose (or reference) multiple services, so applying this annotation to select services could make better sense.
Maybe I misunderstood what this annotation is meant for?

No it is just to be used on classes or interfaces
https://github.com/spring-cloud/spring-cloud-commons/blob/master/spring-cloud-commons/src/main/java/org/springframework/cloud/client/circuitbreaker/EnableCircuitBreaker.java#L33
Also we will no longer be requiring this annotation at some point in the future, see #246

yes, I looked at the src code first and that's why the question being asked. Is there any reason it does not apply to METHODs?
I understand this annotation is not going to be used in the future, but I'm looking to understand the rationale behind the ElementTypes it's being TARGETed at

It doesn't make any sense to have it on a method since it's only meant to
be used once.
Spencer Gibb
On Aug 29, 2017 3:13 PM, "A S Gowri Sankar"<EMAIL_ADDRESS>wrote:

yes, I looked at the src code first and that's why the question being
asked. Is there any reason it does not apply to METHODs?
I understand this annotation is not going to be used in the future, but
I'm looking to understand the rationale behind the ElementTypes it's
being TARGETed at
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spring-cloud/spring-cloud-commons/issues/247#issuecomment-325766571,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAkQpWH6mOyS6jRJx5_p12qDGfbgfLlVks5sdGLbgaJpZM4PEKVc
.

Oh, so this annotation is like a flag for Spring to know whether the circuit breaker feature needs to be enabled or not? That is, it applies to the entire application?

That is correct


Implement createTable functionality

Description
This pull request introduces the create_table and create_external_table methods to the catalog module:

Added create_table method to catalog for creating managed tables.
Added create_external_table method to catalog for creating external tables.
Added tests for managed and external table creation with schema validation and data assertions.

Related Issue(s)

closes #55

Documentation

createTable
createExternalTable

@lexara-prime-ai  going forward can you make separate branches or squash your old changes? right now it says there are 36 commits for this change, but it's actually only < 5

@lexara-prime-ai  can you run cargo clippy over your changes? It's part of the precommit config, and clippy is showing some errors and recommendations when I run it over your branch

@lexara-prime-ai can you run cargo clippy over your changes? It's part of the precommit config, and clippy is showing some errors and recommendations when I run it over your branch

Doing that right away. I also pulled in some changes from upstream as well.  I'll see what I can do.

@lexara-prime-ai going forward can you make separate branches or squash your old changes? right now it says there are 36 commits for this change, but it's actually only < 5

I had a separate branch but pulled all updates into main. Maybe we can re-open the pr from said branch after resolving the change requests.


greengrass-core: Ignore commented sysctl variables

The /etc/sysctl.conf file may contain commented 'protected_.*links' lines.
If these lines exist, postinst() will no longer enable protection for
hardlinks and softlinks. This patch fixes this by ignoring these
commented lines.
Signed-off-by: Codrin Ciubotariu<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for your contribution!


Mixing: removeRecipe(< Any fluid: not working

It seems that this isnt working anymore:
recipetype:create:mixing.removeRecipe(fluid:create:tea);
The script is taken directly from https://docs.blamejared.com/1.16/de/mods/Create/Mixing/
Ingame it says Parameter 0: cannot cast IFluidStack to IItemStack
I guess it doesnt recognize Fluids as an recipe output anymore. This script used to work on older versions tho

full script and log (/ct log) on pastebin please.

Fixed on discord, was using an old createtweaker


BUTTON_RELEASED events issue

See thread starting at https://github.com/nsensfel/relabsd/issues/1#issuecomment-331918515.
Quick fix is likely to still be a special case for that event, but a more general understanding of why the issue occurs would be nice.

Resolved in https://github.com/nsensfel/relabsd/commit/3e76054f937f471e352233f00a5c8ccfee8a78b9


Fix  for issue 78 in aem-eclipse-developer-tools project

Removed executions tag and its subtags.According to this issue, this extra execution step interferes with m2eclipse plugin configurator. the plugin does not ignore this step which generates illegalArgumentException during the create/import of the AEM project in/to Eclipse.

Manually applied in 919d98e582583e1b5bf1676963ab39fa558f8354, thanks!


SWARM-1071 - Restore swarm.project.stage and swarm.project.stage.file

Motivation
In some environments, it's easier to set Java system properties than
to use command-line arguments (oddly).
Modifications
Restore previous support for project-stages.yml (multi-document type)
of YAML configuration via pointing to Files or URLs via a system property.
Additionally, allow activation of stage(s) via system property.
Result
Should work as it used to, and better on OpenShift.

[X] Have you followed the guidelines in our Contributing document?
[X] Have you created a JIRA and used it in the commit message?
[X] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[X] Have you built the project locally prior to submission with mvn clean install?

retest this please

retest this please

retest this please

retest this please

retest this please


[Bug]: Pocketbase is experiencing issues.

Description
nstallation completed without any intervention in the files, just clicking and proceeding to the next step.
Both in the Cloud and self-hosted.
Minimal Reproduction (if possible, example repository)
https://github.com/user-attachments/assets/5705b5bc-07d1-44f4-b749-4dab10686ae1
Exception or Error
2024-07-26T10:17:53.508808986Z 2024/07/26 10:17:53 Server started at http://<IP_ADDRESS>:8080
2024-07-26T10:17:53.509060864Z ├─ REST API: http://<IP_ADDRESS>:8080/api/
2024-07-26T10:17:53.509072186Z └─ Admin UI: http://<IP_ADDRESS>:8080/_/
Version
4.0.0-Beta.3.18
Cloud?

[ ] Yes
[X] No

u should go to http://YOUR_URL/_/
to access the admin UI

This is certainly not a bug and @ItsTarikBTW is correct, you're access is at /_/ for the admin panel.
In my case, I assigned to the same domain as my website with /api/, so I must append the URL to look like. /api/_/.
Pocketbase has no endpoint defined for /, which is why you are seeing the 404.


StartAddress member in SYSTEM_THREAD_INFORMATION is the same for most threads

I took the definition of the struct from process hacker nt headers as follows :
  typedef struct _SYSTEM_THREAD_INFORMATION { 	  LARGE_INTEGER KernelTime; 	LARGE_INTEGER UserTime; 	LARGE_INTEGER CreateTime; 	ULONG WaitTime; 	PVOID StartAddress; 	CLIENT_ID ClientId; 	LONG Priority; 	LONG BasePriority; 	ULONG ContextSwitches; 	ULONG ThreadState; 	ULONG WaitReason; } SYSTEM_THREAD_INFORMATION, *PSYSTEM_THREAD_INFORMATION;
but the StartAddress member is wrong , it's really the same for most threads or 0 for others
I use this code to get the threads info :
`void ** ProcessCore::all_thread_full(unsigned long pid)
{
void all_thread_collected = nullptr;
if (!pid) return all_thread_collected;
void process_buffer = nullptr;
unsigned long required_size = 0;
ntapi::query_sys_info(SystemProcessInformation, 0, 0, &required_size);
if (!required_size) return all_thread_collected;
process_buffer = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, required_size);
bool result = ntapi::query_sys_info(SystemProcessInformation, process_buffer, required_size, 0);
if (!result) {
HeapFree(GetProcessHeap(), 0, process_buffer);
return all_thread_collected;
}
PSYSTEM_PROCESS_INFO pinfo = (PSYSTEM_PROCESS_INFO)process_buffer;
while (pinfo->NextEntryOffset)
{
pinfo = (PSYSTEM_PROCESS_INFO)((uintptr_t)pinfo + pinfo->NextEntryOffset);
if ((unsigned long)pinfo->ProcessId == pid) {
if (pinfo->NumberOfThreads) {
all_thread_collected = (void)HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, sizeof(void) * (pinfo->NumberOfThreads + 1));
for (unsigned long i = 0; i < pinfo->NumberOfThreads; ++i) {
SYSTEM_THREAD_INFORMATION *pthread = (SYSTEM_THREAD_INFORMATION *)HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, sizeof(SYSTEM_THREAD_INFORMATION));
memcpy(pthread,&pinfo->Threads[i], sizeof(SYSTEM_THREAD_INFORMATION));
all_thread_collected[i] = pthread;
}
}
}
}
HeapFree(GetProcessHeap(), 0, process_buffer);
return all_thread_collected;
}
PSYSTEM_THREAD_INFORMATION all_threads = (PSYSTEM_THREAD_INFORMATION)ProcessCore::all_thread_full(836);
while (all_threads)
{
cout << "[] thread id : " << (unsigned long)(all_threads)->ClientId.UniqueThread << endl
<< "[] thread process : " << (unsigned long)(all_threads)->ClientId.UniqueProcess << endl
<< "[] start address : " << (unsigned long long)(all_threads)->StartAddress << endl
<< "[] state : " << (*all_threads)->ThreadState << endl;
++all_threads;
}`
the ids and pids are the same as shown in process hacker but the start address isn't as it in ph

the code format isn't being showed right here so these are the codes as screen shots


Visual C++ 2017 problem

compiled with vc2017  report  template function error!

I noticed that VC requires the following changes:

Add #include <stdlib.h>
Comment out/remove make_unique function definition in concaveman.h
Add:

using std::make_unique;
instead.
4) Replace calls to random() with rand()

In dense points cases, concaveman cannot get correct results!

It isn't a self-tuning algorithm unfortunately. You have to adjust minimum
edge length and curvature in order to allow short edges which I presume is
what you need if you have a dense point cloud.
On Fri, Jun 7, 2019, 2:51 AM manuel76413<EMAIL_ADDRESS>wrote:

In dense points cases, concaveman cannot get correct results!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/sadaszewski/concaveman-cpp/issues/2?email_source=notifications&email_token=AAKQRXKCDOMUXDAI6OL4PXLPZGWJTA5CNFSM4HSAIDAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXESISY#issuecomment-499721291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKQRXPTQEELGNBWCJ7E523PZGWJTANCNFSM4HSAIDAA
.


Build Error (US)

Just thought I'd give this a shot.
I feel like I'm pretty close in getting this to decompile, but I'm running into the following error during the build process:
/qemu-irix/irix-linux-user/qemu-irix -silent -L tools/ido5.3_compiler tools/ido5.3_compiler/usr/bin/cc -c -Wab,-r4300_mul -non_shared -G 0 -Xcpluscomm -Xfullwarn -g -signed -I include -I build/us/include -I src -D_LANGUAGE_C -DVERSION_US=1 -mips2 -32 -DF3D_OLD -o build/us/src/engine/surface_collision.o src/engine/surface_collision.c
cc: full_path: Invalid argument
make: *** [Makefile:430: build/us/src/engine/surface_collision.o] Error 1

OS: Debian (Latest) and Ubuntu (Latest)
Packages Installed: git build-essential zlib1g-dev pkg-config libglib2.0-dev binutils-dev libboost-all-dev autoconf libtool libssl-dev libpixman-1-dev libpython-dev python-pip python-capstone virtualenv flex bison binutils-mips-linux-gnu python3 libaudiofile-dev
QEMU-Irix: Compiled from source using configure --target-list=irix-linux-user,irixn32-linux-user,irix64-linux-user,solaris-linux-user && make && make install.
Base ROM: baserom.us.z64
Let me know if you need any more information.

Seems like a problem with your qemu_irix, I would suggest you get the binary from the releases tab on this repository.

Awesome. I'll give that a whirl tonight. I'm putting together a Docker container that can automate the decompiling process a little more and abstract some of the lower-level concepts away. I'll follow up with everything.

Sadly, still the same error.
Here's the list of Docker command instructions I'm using:
FROM debian:latest

RUN apt-get update && \
    apt-get install -y wget git binutils-mips-linux-gnu python3 \
    build-essential pkg-config zlib1g-dev libaudiofile-dev

RUN wget -O /usr/local/bin/qemu-irix https://github.com/n64decomp/sm64/releases/download/irix2/qemu-irix && \
    chmod +x /usr/local/bin/qemu-irix
ENV QEMU_IRIX=/usr/local/bin/qemu-irix

RUN git clone https://github.com/n64decomp/sm64.git

# Copy the baserom into the image
COPY baseroms/baserom.us.z64 /sm64/baserom.us.z64
WORKDIR /sm64
ENTRYPOINT ["make"]

Nothing here is standing out to me as particularly problematic, so I'm thinking that perhaps my own baserom might be somehow malformed or problematic in some way.

The baserom sha1 should be 9bef1128717f958171a4afac3ed78ee2bb4e86ce for the US version.

@chungy The wording of the README led me to believe that sha1 was what we ended up with, not what we started with. But that makes sense since we're decompiling a ROM. Not ending up with one. I'll see what I can find.

Marking this issue as closed pending further investigation

might want to make sure that you have full permissions for the directory the decompilation is in
that was the problem for me

I encountered this problem when trying to use a virtual machine to compile the source stored on an external USB drive. Copying the source from the external drive to the VM's disk fixed the problem. I tried to figure out why that fixed it, but didn't make any headway.


avoid that winget mixed up updates for LibreOffice v. 7.x with the v. 24.x

Brief description of your issue
winget mixed up updates for LibreOffice v. 7.x with the v. 24.x
what would happen if we would mix up Office 2019 with Office 365 ?
The results would be similar.
winget list --upgrade-available  (the result is false)
Name      - -           ID          - -              Update Version
LibreOffice <IP_ADDRESS> - - - TheDocumentFoundation.LibreOffice <IP_ADDRESS>  - - - <IP_ADDRESS>
correct would be eg. based on the previous version:
LibreOffice <IP_ADDRESS> - - - TheDocumentFoundation.LibreOffice <IP_ADDRESS>  - - - <IP_ADDRESS>
or is it caused by the strange ID?
TheDocumentFoundation.LibreOffiÔÇª
or caused by the name?
winget show "LibreOffice <IP_ADDRESS>" = no result
winget show "LibreOffice" = shows result of v. 24
this could lead to a wrong match
Steps to reproduce
please follow as described above
Expected behavior
Please follow with your provided winget update information the given rules on
https://www.libreoffice.org/download/download-libreoffice/
and please treat the versions separately.
v. 24 is not equal v.7
even a future version v. 25 will never be a v. 8
further infos about the v. 24.2.2
https://download.documentfoundation.org/libreoffice/stable/24.2.2/win/x86_64/LibreOffice_24.2.2_Win_x86-64.msi.mirrorlist
further infos about the v. 7.6.6
https://download.documentfoundation.org/libreoffice/stable/7.6.6/win/x86_64/LibreOffice_7.6.6_Win_x86-64.msi.mirrorlist
Thank you
Actual behavior
please suppresses the false update message for the version 7
Environment
winget --info
Windows-Paket-Manager v1.7.10861

Windows: Windows.Desktop v10.0.19045.4170
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.22.10861.0

WinGet-Folders
- - -
Protokolle %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
Benutzereinstellungen %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Verzeichnis für portierbare Links (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Links
Portables Linkverzeichnis (Computer) C:\Program Files\WinGet\Links
Portierbarer Paketstamm (Benutzer) %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portierbarer Paketstamm C:\Program Files\WinGet\Packages
Portierbares Paketstamm (x86) C:\Program Files (x86)\WinGet\Packages
Installationsprogrammdownloads %USERPROFILE%\Downloads

Administrator-Settings                  Status
- - -
LocalManifestFiles                        Deaktiviert
BypassCertificatePinningForMicrosoftStore Deaktiviert
InstallerHashOverride                     Deaktiviert
LocalArchiveMalwareScanOverride           Deaktiviert

I believe version 7 manifests have been moved into TheDocumentFoundation.LibreOffice.LTS. Are you still seeing the issue?

or is it caused by the strange ID?
TheDocumentFoundation.LibreOffiÔÇª

This might be from a separate bug.

@stephengillie
... 10 hours later
winget list
AND
winget list --upgrade-available
both offers the wrong v.24 again
We can never unchecked believe anything in winget.
Without having checked it on the winget db servers, such statements like to believe anyone has related the correct upddate are demonstrably worthless.
Any allegedly partially correct results at the moment can return to their original incorrect state after a few hours.
winget is still just a gamble and therefore is only one possibility:
no matter what result winget shows you. never trust winget

Please understand that we're working with a system with a huge variety of inputs. We're not actively trying to sneak pre-release versions into mainline PackageIdentifiers, but instead doing our best to mitigate and handles these situations once they're identified.
This is why we've worked to move v24 into a separate PackageIdentifier. Your posts are something of a bug report, and would be much more helpful if they had more technical data. Copy-pasting WinGet output is recommended.
Feel free to join our efforts to mitigate these issues, and also feel free to use the package manager of your choice.


Review and improve regex rules

There was a recent white paper released (summary, source).
What's most interesting is on page 15, they list a variety of explicit regexes that we may be able to incorporate into our scanning. I think we already cover like 80% (mostly with the high entropy scanner), but there are some interesting ones to extract from that. e.g.:

finance related tokens
Facebook access tokens

We should go through this list and create new plugins for the ones that we're missing.

I love the idea. Be able to more deterministically identify the type of the token can also support #153

A couple of notes from this paper worth mentioning (for posterity):

Section III, Part E: talks about some interesting ideas on how to better filter out junk keys (e.g. XXXX, has EXAMPLE in the text)

Section V, Part D: notes that multi-factor secrets (e.g. username and password) has an 80% chance that they both can often be found within 5 lines of context, before and after a secret.

Section VII, Part D: entropy checks still catch more than just regex rules. This is good to know, and allows users to decide how conservative they want to be (accuracy v recall trade-off).

I thought this part was another cool thing to experiment with:
Section III, Part D:

Note that each regular expression was prefixed with negative lookbehind (?<![\w]) and suffixed with negative lookahead (?![\w]) to ensure that no word characters appeared before or after the regular expression match and improve accuracy.


[FR] The implementation of Resnet in Plato needs to be revised

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
That is pretty strange to implement the ResNet, i.e., plato/models/resnet.py in Plato to only support the CIFAR-related dataset with input size 32. The pooling layer before the fc layer in plato is F.avg_pool2d, which is less effective.
Maybe the current implementation is to support the 'cut_layer'?
But, still, this is unnecessary to reimplement a model by ourselves as the torchvision has provided many models. Once we want to remove some layers, just use nn.Identity() to replace them without any risk.
Describe the solution you'd like
A clear and concise description of what you want to happen.
The most effective way is to follow the implementation of ResNet in torchvision. They utilize the:
    self.avgpool = nn.AdaptiveAvgPool2d((1, 1))

to support any input size.
I know the current implementation of ResNet replaces the kernel_size of conv1 7x7 with 3x3, and removes first max pooling to maintain spatial information for input with small sizes, such as 32x32 for CIFAR10.
However, this can be easily achieved by using the torchvision's implementation while setting:
  encoder.conv1 = nn.Conv2d(3,
                                  64,
                                  kernel_size=3,
                                  stride=1,
                                  padding=2,
                                  bias=False)
  encoder.maxpool = nn.Identity()

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Just reuse torchvision's implementations.
Additional context
Add any other context or screenshots about the feature request here.
In my own work, I directly utilize torchvision's implementations and revise the torchvision's model slightly based on my own requirement. It works well on many different datasets without error. See the models/encoders_register.py in the contrastive_adaptation branch.

With the recently redesigned model registry, torchvision's ResNet model can be directly used by loading it from torch.hub:
./run -c configs/CIFAR10/fedavg_resnet18_torchhub.yml

Once torchvision releases 0.14 officially, its get_model() can also be used to load torchvision's model directly.


Incorrect Version in Title

Hi!  Dependabot is great, and I use it at work and personal projects.  In this one instance (https://github.com/grouparoo/grouparoo/pull/1088) the title Depenabot created was wrong.
Package manager/ecosystem

Javascript

What you expected to see, versus what you actually saw
The title should have been: Bump uuid from 8.3.1 to 8.3.2
The title was: Bump uuid from 3.4.0 to 8.3.2
You can see in the PR that the versions in the monorepo were all moving from v8.3.1 to v8.3.2
Images of the diff or a link to the PR, issue or logs
https://github.com/grouparoo/grouparoo/pull/1088

Also happened, https://github.com/Cezerin2/Cezerin2/pull/287/files and broke the project sadly. Hope this gets fixed quickly.

Also happened in https://github.com/Cezerin2/Cezerin2/pull/461, where the title was feat: Package bump @types/node from 17.0.41 to 17.0.42 but also included ws updated from 8.7.0 to 8.8.0.

👋 sorry for the slow followup here. We're finally catching up on some of our backlog.
For the original issue, it's been 2+ years since it was filed and we've pushed a lot of fixes since then. I'm guessing this is fixed but tougher to repro since underlying repo is archived. I don't think it's worth tracking down at this point, if you see it again please file a new issue and we can hopefully jump on it faster.
For the second cases in April / June of last year, we had some internal instability around this time IIRC, and that may have resulted in races--for example I see the broken PR happened at same time as a correct-looking PR, but they had the same content just different descriptions. Unlikely to be a logic bug in dependabot-core library itself given there are two PR's and one had the right content and the other didn't.., so probably a race on the back-end infra. Don't know for sure, but unfortunately logs are long gone at this point so would be tough to track down.
For the final PR you posted, I don't see the bump in ws in that PR description? Only the @types/node...
I'm going to close this as can't repro, but if you see it again please file a new issue and we can try to track it down before the logs expire.


DiffUtil.ItemCallback no working in sample "PagingWithNetworkSample"

When I just get data from the web,DiffUtil is not triggered when loading more data.
LiveData<PagedList> trigger adapter.submitList(it) when acquiring data for the first time.
How should I use Paging correctly
Please forgive my bad English！

anyone answer me?

@XiaoQiWen, I think this is the expected behavior.
The PagedList internally grows larger as new items are loaded and it has nothing to do with onChanged() in your view.
The onChanged() comes into play when you invalidate the DataSource and prepares a new set of PagedList and its producer(DataSource), then your view will receive a callback in onChanged() giving you the new object of PagedList which contains the updated pages of data.


Add Player Achievements API

Hi!
Thanks for creating such a great tool and making it available for everyone (:
I'm wondering if you have in plan to add an API to request Player Achievements. I'm working on a quiz app and this would be highly appreciated.

Hi @enricobottazzi! I'm glad to know that you liked this project! To be honest I haver never considered developing a player achievements endpoint, but maybe we can work together on it! Could you please take a player as example and propose a payload output that you'd expect from this endpoint? So we can start the discussion from there. Thanks!

Hey @aminel91! Actually there was no progress in this issue, but if you don't mind proposing an initial example payload it would be great to start from there!

Hi @felipeall. Here's a link to an initial payload. The json is here and the source is here. I'm not exactly sure if you already have competition ids or can get them from the api, or if you have cup ids already in the competitions, but queryying the vercel demo for FRC for example, the french cups doesn't return the expected data. So this payload assumes none of that and might be a good start. Please let me know what you think.

Thanks for the input @aminel91! I just opened a PR with the new Players Achievements endpoint, could you please take a look and test it to see what you think? https://github.com/felipeall/transfermarkt-api/pull/60

Hi @felipeall. Thanks so much, I've just tested it, and I think it's great. I had played with multiple payloads but I think this one is easy enough to use while getting around some achivements not having a club or competition attached to them. Thanks so much for the great work once again, and for the entire awesome project.


dev dependancies vs dependancies

Describe the bug
Error report -
"You are using SvelteKit-specific imports in your code, but you have not declared a dependency on @sveltejs/kit in your package.json
This was a test with new install to try to get all the dependancies and dev dependancies working correctly specifically with Tailwind Typescript on Sveltekit
npm create svelte@latest my-test-all-in-one
Library Typescript prettier lint
cd my-test-all-in-one
npm install
npx svelte-add@latest tailwindcss
Static Site
npm i -D @sveltejs/adapter-static
add to +layout.js export const prerender = true;
npm run build builds but throws error - (above)
Searching docs I cannot find the correct setups to which packages should be
devDependencies and which should load as Dependencies
Does anyone have any pointers on this?
Its not breaking but I would like to correct if possible.
Seems there is another mention on a closed post
Re closed #7685
Reproduction
"devDependencies": {
"@sveltejs/adapter-auto": "^2.0.0",
"@sveltejs/adapter-static": "^2.0.2",
"@sveltejs/kit": "^1.5.0",
"@sveltejs/package": "^2.0.0",
"@typescript-eslint/eslint-plugin": "^5.45.0",
"@typescript-eslint/parser": "^5.45.0",
"autoprefixer": "^10.4.14",
"eslint": "^8.28.0",
"eslint-config-prettier": "^8.5.0",
"eslint-plugin-svelte": "^2.26.0",
"postcss": "^8.4.23",
"postcss-load-config": "^4.0.1",
"prettier": "^2.8.0",
"prettier-plugin-svelte": "^2.8.1",
"publint": "^0.1.9",
"svelte": "^3.54.0",
"svelte-check": "^3.0.1",
"svelte-preprocess": "^5.0.3",
"tailwindcss": "^3.3.2",
"tslib": "^2.4.1",
"typescript": "^5.0.0",
"vite": "^4.3.0"
},
"svelte": "./dist/index.js",
"types": "./dist/index.d.ts",
"type": "module",
"dependencies": {
"svelte-video-player": "^1.2.5",
"vidstack": "^0.5.6"
}
}
Logs
No response
System Info
System

Severity
annoyance
Additional Information
No response

If you're just trying to create a static site, you probably shouldn't be using the Library template. With the Library template, npm run build also invokes https://kit.svelte.dev/docs/packaging - That warning is coming from there.

OK thankyou for your comments.
Reason I use library instead of skeleton is the build from skeleton goes into (dot) ".svelt-kit" folder
where library builds in "dist" folder
This is in both cases before and after i have added static adapter to make static page site as you have mentioned.
I have not been able to find a way to change this distribution path and I see it still is an outstanding issue for others https://github.com/sveltejs/kit/issues/4052
the .svelte-kit causes issues in the cloud dynamic built as I assume the system does not want to look inside a dot folder
So if you know how I am able to achieve this I would be much appreaciated.


fix for issue when forever.js ignore workingDir option

Fix for issue when forever.js ignore workingDir option from json config file when assign cwd param.

Any idea why this isn't merged yet?


Cannot install at laravel 5.0.35

Laravel Version:5.0.35
PHP Version: 5.6.40
Database Driver & Version:

Description:
- illuminate/encryption v5.8.9 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.8.8 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.8.4 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.8.36 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.35 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.34 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.33 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.32 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.31 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.30 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.3 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.8.29 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.28 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.27 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.24 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.22 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.20 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.2 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.8.19 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.18 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.17 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.15 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.14 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.12 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.11 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.8.0 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.9 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.8 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.7 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.6 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.5 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.4 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.3 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.28 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.27 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.26 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.23 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.22 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.21 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.20 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.2 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.15 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.11 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.10 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.7.1 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.7.0 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.9 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.8 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.7 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.6 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.5 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.4 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.39 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.38 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.37 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.36 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.35 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.34 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.33 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.32 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.31 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.30 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.3 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.29 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.28 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.27 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.26 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.25 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.24 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.23 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.22 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.21 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.20 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.2 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.19 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.17 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.16 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.15 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.14 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.13 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.12 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.11 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.10 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.

- illuminate/encryption v5.6.1 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.6.0 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.44 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.43 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.41 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.40 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.39 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.37 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.36 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.35 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.34 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.33 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.28 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.2 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.17 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.16 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption v5.5.0 requires php >=7.0 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption 5.7.19 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption 5.7.18 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- illuminate/encryption 5.7.17 requires php ^7.1.3 -> your PHP version (5.6.5) does not satisfy that requirement.
- Installation request for laravel/passport 2.0 -> satisfiable by laravel/passport[v2.0.0].
- Conclusion: remove laravel/framework v5.0.35
- Conclusion: don't install laravel/framework v5.0.35
- laravel/passport v2.0.0 requires illuminate/encryption ~5.4 -> satisfiable by illuminate/encryption[5.7.17, 5.7.18, 5.7.19, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39, v5.5.40, v5.5.41, v5.5.43, v5.5.44, v5.6.0, v5.6.1, v5.6.10, v5.6.11, v5.6.12, v5.6.13, v5.6.14, v5.6.15, v5.6.16, v5.6.17, v5.6.19, v5.6.2, v5.6.20, v5.6.21, v5.6.22, v5.6.23, v5.6.24, v5.6.25, v5.6.26, v5.6.27, v5.6.28, v5.6.29, v5.6.3, v5.6.30, v5.6.31, v5.6.32, v5.6.33, v5.6.34, v5.6.35, v5.6.36, v5.6.37, v5.6.38, v5.6.39, v5.6.4, v5.6.5, v5.6.6, v5.6.7, v5.6.8, v5.6.9, v5.7.0, v5.7.1, v5.7.10, v5.7.11, v5.7.15, v5.7.2, v5.7.20, v5.7.21, v5.7.22, v5.7.23, v5.7.26, v5.7.27, v5.7.28, v5.7.3, v5.7.4, v5.7.5, v5.7.6, v5.7.7, v5.7.8, v5.7.9, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9].
- don't install illuminate/encryption v5.4.0|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.13|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.17|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.19|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.27|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.36|don't install laravel/framework v5.0.35
- don't install illuminate/encryption v5.4.9|don't install laravel/framework v5.0.35
- Installation request for laravel/framework (locked at v5.0.35, required as 5.0.*) -> satisfiable by laravel/framework[v5.0.35].

Installation failed, reverting ./composer.json to its original content.
Steps To Reproduce:
composer require laravel/passport=4.0

Laravel 5.0 isn't supported anymore, you could try updating to 5.5 (LTS) or a higher supported version.
See: https://laravel.com/docs/7.x/releases#support-policy

Passport doesn't support Laravel 5.0. Pasport version 4 should work with Laravel 5.5 LTS, however.
Note that laravel/passport=4.0 is bad syntax. You need laravel/passport:^4.0.

noted with thanks


Change to a new folder from integrated terminal without losing terminal window

When using vscode's integrated terminal, I'll typically switch folders by doing:

cd some-folder-name
code -r .
or
code -r /path/to/some-folder

This works great, and I know that -r is a total reload (has to reload to reuse the same window), but the problem with a reuse is that I have to open all my terminals again (in a way, this could be considered a bug). Could you add a feature to support the same kind of workflow but not reload the whole instance? Maybe just the file explorer and leave the instance as is? I know about the -a command, but that adds a folder. I want the same functionality as "code -r ." but without losing my terminals and loading a new instance. Basically, the top most folder in file explorer should be the only thing that changes (and yes, you'll probably need to load it as a workspace)

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

I face the same inconvenience

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Quantization node

This PR introduces a node to perform image compression with high retention of visual details

I don't see the node in the Add Nodes menu, or is that not the intention here?

@Keavon The node is #[cfg(feature = "quantization")] which is not enabled by default.


docs: automatically sync quickstart tutorial with codebase

At present, there is a risk of the documentation and the codebase becoming out of sync. To mitigate this risk, ensure that the output of the Jupyter notebooks is cleared before committing. Subsequently, allow ReadTheDocs to rerun the notebook. For now, apply this process solely to the Quick Start tutorial. (address part of #130)

Codecov Report
Attention: 66 lines in your changes are missing coverage. Please review.

Comparison is base (0f95d04) 94.21% compared to head (ec42f2f) 94.31%.
Report is 50 commits behind head on main.

Files
Patch %
Lines

xeofs/utils/numba_utils.py
20.96%
49 Missing :warning:

xeofs/data_container/data_container.py
88.88%
3 Missing :warning:

xeofs/preprocessing/stacker.py
72.72%
3 Missing :warning:

xeofs/models/_base_cross_model.py
96.07%
2 Missing :warning:

xeofs/models/_base_model.py
96.07%
2 Missing :warning:

xeofs/models/decomposer.py
86.66%
2 Missing :warning:

xeofs/preprocessing/preprocessor.py
88.88%
2 Missing :warning:

xeofs/utils/xarray_utils.py
88.88%
2 Missing :warning:

xeofs/utils/io.py
97.95%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #136      +/-   ##
==========================================
+ Coverage   94.21%   94.31%   +0.09%
==========================================
  Files          71       73       +2
  Lines        5823     6083     +260
==========================================
+ Hits         5486     5737     +251
- Misses        337      346       +9

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

@nicrie try to save the notebook with the default kernel (Python 3) instead of the one you've been using locally.
I.e., this metadata should look like this:
 "metadata": {
  "kernelspec": {
   "display_name": "Python 3 (ipykernel)",
   "language": "python",
   "name": "python3"
  }

Thanks @malmans2 that did the trick!


[WFLY-17983][WFLY-17984] Upgrade Jakarta Activation 2.1.2 and Angus Activation 2.0.1

Built on top of #16807
Bug fix release
Jira issue:
https://issues.redhat.com/browse/WFLY-17983
https://issues.redhat.com/browse/WFLY-17984

Thanks @yersan


Local use of exported functions are (sometimes) ignored

I'm having issues with Knip configuration.
The project is a monorepo, yet issues are often "local" to a single workspace. In a workspace I have a package called "f-commons" 1) I try to run the project only for that package: npx knip  --fix --workspace packages/f-common
2) Some exports are correctly identified as unused and removed, some are removed despite they are used locally in the package.
Example:
/**
 *  No change the following import is properly recognized
 * import { httpV2RequestFunction } from "../../utils";
**/
export const httpV2RequestFunction = <T>(
  options: httpsv2.HttpsOptions,
  aFunction: (req: Request) => Promise<T>
) => {
  return httpsv2.onRequest(options, (request, response) => {
    return cors(request, response, () => {
      const scenario = aFunction(request);
      return sendResultOrMeaningfulError(scenario, response);
    });
  });
};

/**
 *  change: "export" is removed, despite an import in another file
 * import { withApiPermissions, httpFunction } from "../utils/network";
**/
export const withApiPermissions =
  <T extends BaseApiRequest>(permissions: string[], action: (a: T) => any) =>
  (t: T) => {
    return authActions
      .checkPermissions(t.parkingId, t.apiKey, permissions)
      .then(() => action(t));
  };

Further troubleshooting:

I tried to import withApiPermissions not directly from the file, but via index.ts, and nothing changed - the export is still being marked as unused. Those are the only imports of both functions, and I cannot spot why one is treated differently than the other one.

To look into an issue like this I would need a minimal repro: https://knip.dev/guides/troubleshooting/#minimal-reproduction

Closing due to inactivity


Exception is thrown if $ref value is not a string

Issue is reported by user in
https://asyncapi.slack.com/archives/CQVJXFNQL/p1666700935030749
Shani Alaluf Shamah
We have an issue in bundle version 0.3.4 using parser 1.17.1
When adding the feature referenceIntoComponents: true
we get the following error:
TypeError: Cannot read property 'startsWith' of undefined
    at isExternalReference (/Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/parser.js:41:17)
    at /Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/parser.js:58:13
    at Array.forEach (<anonymous>)
    at resolveExternalRefs (/Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/parser.js:56:8)
    at parse (/Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/parser.js:80:43)
    at async resolve (/Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/util.js:62:13)
    at async bundle (/Users/shani.shamah/IdeaProjects/data-model-schemas/node_modules/@asyncapi/bundler/lib/index.js:42:27)
    at async createApiSpecforService (/Users/shani.shamah/IdeaProjects/data-model-schemas/scripts/generate-api-spec.js:12:15) {stack: 'TypeError: Cannot read property 'startsWith' …l-schemas/scripts/generate-api-spec.js:12:15)', message: 'Cannot read property 'startsWith' of undefined'}

it doesn’t work with 0.3.3 either
With 0.2.3 I am getting the following error:
TypeError: bundle is not a function

I’m using JS, require (CJS) syntax:
const bundle = require('@asyncapi/bundler').default;

switched to 0.2.3 with
const bundle = require("@asyncapi/bundler")

but still getting the Cannot read property 'startsWith' of undefined error.
Maciej Urbańczyk
https://github.com/asyncapi/bundler/blob/master/src/parser.ts#L44 we should check if $ref exists and then check if starts with #
in old code this same https://github.com/Souvikns/bundler/blob/ef574b8620f12c075d89bfc742070748941a45e0/lib/parser.js#L51 :sweat_smile:
Lukasz Gornicki
@Shani Alaluf Shamah
ok so mistery solved
imho change is to just extend condition from https://github.com/asyncapi/bundler/blob/master/src/parser.ts#L64, to if (ref && isExternalReference(ref))
Maciej Urbańczyk
we use isExternalReference in several places, we should check if $ref  exist inside isExternalReference function:
function isExternalReference(ref?: string): boolean {
  return typeof ref === 'string' && !ref.startsWith('#');
}

Lukasz Gornicki
makes sense :+1::skin-tone-2:

Shani Alaluf Shamah
Can you please clarify what value are you passing to $ref, because I have tried passing to $ref in YAML

array, YAML object, number, boolean, but all I get is

TypeError: ref.startsWith is not a function

with absence of value (NOT '') and null I get

TypeError: Cannot read properties of null (reading 'startsWith')

with an empty string '' the value is simply ignored (no exception thrown, execution successful)

with ./, /, https..., function, undefined Node.js gives various errors of failing to open or fetch file.

But no TypeError: Cannot read property 'startsWith' of undefined
So for now I cannot reproduce exactly your bug, to begin fixing it, on Node.js v16.17.0 and Node.js v18.9.0.
Maciej Urbańczyk solution
function isExternalReference(ref: string): boolean {
  return typeof ref === 'string' && !ref.startsWith('#');
}

works - it makes bundler ignore any value that is not a string, thus might fix exactly your issue indirectly, so it definitely should be merged.
After this change is merged, please comment if exactly your issue was fixed.

User did not provide feedback, assuming issue fixed, resolved and closed.


chore(master): release 1.1.42

:robot: I have created a release beep boop
1.1.42 (2023-08-22)
Bug Fixes

deps: update dependency wayofdev/laravel-webhook-client to v1.1.31 (d97b597)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v1.1.42 :sunflower:


"i" next to checkbox

Small nit here but I can't help to notice the checkmark and "i" are not vertically centered in many places. Hopefully if fixed, it will cascade.

Applied minor changes.

Awesome!


kill goal

Since users will no longer receive payments directly, there's no need for them to be able to publish a personal goal. Our goal implementation was half-baked anyway. If we want goals for teams we should implement them properly (a la Kickstarter, Patreon, Salt, etc.).
Incorporates #3402 and #3403.

At this point I'm planning to rebase this one a couple other PRs are landed first. See https://github.com/gratipay/gratipay.com/issues/3399#issuecomment-101391534.

We want to turn off tipping (#3406) before we land this, because without this someone could tip a "patron-no-tips."

Tipping has been disabled, I'm merging this.

!m @rohitpaulk


buggy regex

Played with mixing CSS according to BEM and JavaScript. The regex to find classes is buggy.
Source file:
.search-area {

}

.search-area__label {

}

.search-area__search-box {

}

.search-area__search-box .description {

}

.register {

}

.register__name {

}

.register__name .description {

}

.name {

}

const person {
    name: "John Doe"
}

Result:

.A03 {

}

.A03__A00 {

}

.A03__A04 {

}

.A03__A04 .A0B {

}

.A09 {

}

.A09__A0F {

}

.A09__A0F .A0B {

}

.A0F {

}

A0D A0E {
    A0F: "JA0G DA08"
}

In commit https://github.com/davidxcheng/ruin/commit/d0115330d9c08d2a1556ec5125cc76c78cd698c4 the source list of class names was improved. Updating content is still buggy.

Replace of content now tighter. In commit https://github.com/davidxcheng/ruin/commit/ac1de261c5f458c2edc4ca44852c01852e3c4a71 the above file now looks as follows:
.A {

}

.A0 {

}

.A00 {

}

.A00 .A01 {

}

.A02 {

}

.A03 {

}

.A03 .A01 {

}

.A04 {

}

const person {
    name: "John Doe"
}

Think we can close this issue, at least for the moment.


wildcard file-types in ale_fixers

Hey there,
I started working with your plugin earlier after years of using something else. When going trough the features I noticed you even have an auto-fix feature!
Man that's just awesome!
among the generic ones I quickly noticed that there is support for the removal of trailing whitespaces and trailing lines, that's pretty awesome and I've applied it to a bunch of file types already.
Problem being, that I would actually love to apply the auto-fix for whitespaces to every known filetype except markdown.
Is there a way, or a plan to allow "a wildcard file type" making the config like:
let g:ale_fixers = {
\   'javascript': ['eslint'],
\   '"*"': ['trim_whitespace', 'remove_trailing_lines'],
\}

or maybe even exceptions (like MD, though this would just be a bonus)
let g:ale_fixers = {
\   'markdown': ['!trim_whitepace'],
\   "*": ['trim_whitespace', 'remove_trailing_lines'],
\}

or
let g:ale_fixers = {
\   "(?!markdown)": ['trim_whitespace', 'remove_trailing_lines'],
\}

Definitely going to read a bit more on the inner workings of this and see if I can perhaps come to a solution ;)

You can use g:ale_pattern_options to set different options based on regular expressions. You can use g:ale_fixers to set options for everything, and override the option with b:ale_fixers. You'll have to construct the whole lists of things you want to run yourself.

It might make sense to use '*' for setting a default list.

\o/
THANKS!

I was looking exactly for this just now. Thank you.


Limit calculation is not probabilistic

Adding this just to remind myself to do the math and update the code soon. : )

Fixed by 11854da.
We use the Chernoff bound to calculate a limit to ensure we fetch all necessary triples on the first trial with 99.9% probability. We model whether a triple has been removed as a random variable 'ti', that is 0 if a triple with index i has been removed, and 1 otherwise; and we define tN = t0+t1+t2+ ... + tn.
We want to minimize the probability that tN < limit.
We have:
P[tN < limit] = P[exp(-tN) > exp(-limit)]  <- Here we need to use negative exponents for the Chernoff bound
P[exp(-tN) > exp(-limit)] < E[exp(-tN)]/exp(-limit)
If tN < limit, then we must fetch triples again, and thus we have failed.
Let P[exp(-tN) > exp(-limit)] = PrFail
Also, E[exp(-tN)] = E[exp(-t1-t2-...-tn)] = E[-ti]^N = (PrRemoved + PrNotRemoved*exp(-1))^N
PrFail < E[exp(-ti)]^N/exp(-limit)
Applying natural logarithm on both sides:
ln(PrFail) < N*ln(E[exp(-ti)])+limit
Solving for N: N > (ln(PrFail)-limit) / ln(E[exp(-ti)])
We choose 99.9% probability of success, and therefore 0.1% probability of failure.
N > (ln(0.001)-limit) / ln(PrRemoved + PrNotRemoved*exp(-1))
Which is the calculation that we do in the code.

Great stuff!


How can i skip all these conll files and make a simple prediction with an input text file

here's my problem with conll_eval_path , lm_path,conll_test_path,  files that I don't need to make prediction
(aracoref) souid@aymen:~/aracoref$ python evaluate.py arabic_cleaned_bert
Running experiment: arabic_cleaned_bert
max_top_antecedents = 50
max_training_sentences = 50
top_span_ratio = 0.4
filter_widths = [
3
4
5
]
filter_size = 50
char_embedding_size = 8
char_vocab_path = "/home/souid/aracoref/bert-base-arabertv01/vocab.txt"
context_embeddings {
path = "/home/souid/aracoref/cc.ar.300.vec"
size = 300
}
head_embeddings {
path = "/home/souid/aracoref/cc.ar.300.vec"
size = 300
}
contextualization_size = 200
contextualization_layers = 3
ffnn_size = 150
ffnn_depth = 2
feature_size = 20
max_span_width = 30
use_metadata = true
use_features = true
model_heads = true
coref_depth = 2
lm_layers = 4
lm_size = 768
coarse_to_fine = true
max_gradient_norm = 5.0
lstm_dropout_rate = 0.4
lexical_dropout_rate = 0.5
dropout_rate = 0.2
optimizer = "adam"
learning_rate = 0.001
decay_rate = 0.999
decay_frequency = 100
train_path = "/home/souid/aracoref/best_models_crac2020/best-models/data/train.arabic.pred.mentions.jsonlines"
eval_path = "/home/souid/aracoref/best_models_crac2020/best-models/data/dev.arabic.pred.mentions.jsonlines"
conll_eval_path = "dev.arabic.v4_gold_conll"
lm_path = "bert_arb_conll12_cleaned_features.hdf5"
test_path = "/home/souid/aracoref/best_models_crac2020/best-models/data/test.arabic.pred.mentions.jsonlines"
conll_test_path = "test.arabic.v4_gold_conll"
genres = [
"bc"
"bn"
"mz"
"nw"
"pt"
"tc"
"wb"
]
eval_frequency = 500
report_frequency = 100
log_root = "logs"
max_step = 400000
use_joint_coref = true
use_e2e_annealing = false
log_dir = "logs/arabic_cleaned_bert"
Loading word embeddings from /home/souid/aracoref/cc.ar.300.vec...
Traceback (most recent call last):
File "evaluate.py", line 18, in
model = cm.CorefModel(config)
File "/home/souid/aracoref/coref_model.py", line 24, in init
self.context_embeddings = util.EmbeddingDictionary(config["context_embeddings"])
File "/home/souid/aracoref/util.py", line 174, in init
self._embeddings = self.load_embedding_dict(self._path)
File "/home/souid/aracoref/util.py", line 194, in load_embedding_dict
assert len(embedding) == self.size
AssertionError

If you set official_stdout=False it will not try to create CoNLL files but you will need to write your own output parts in order to output the predictions.

even setting it to false, this error keeps showing, there is a problem with the length of the embedding
len(embedding)=1
len(self.size)=300

I thought you asked about how to skip conll files? The error is not related to that, I think for this error you need to remove the first line for the cc.ar.300.vec as the first line of fasttext has only two numbers (the number of words and the dimension) The reader didn't try to skip this.

do you have an idea how to solve this after loading word embeddings ?


Update PersistanceType.cs

src/Simple.CredentialManager/PersistanceType.cs

Do not merge this.
According to Microsoft Docu, @Ashikur41 suggestion is wrong.
LocalComputer should be 2 and Enterprise should be 3, as it is. This commit makes it wrong.


✨ Added getTransaction function

Closes #16.

Added getTransaction function
Added getTransaction inline documentation

To-do before merging (will unmark as draft when ready)

Add docs to readme
Add testing

Commit 9af489ac6d35299ae913cc8c1d44b1c380c04658 fails testing locally as well. The testing is currently setup for the Transaction v to be a hex string; ethers currently turns into into a Number. Just wanted to commit what I had, and I'll let @dawsbot decide whether it should be a string or number


Add variant-level metadata from CIViC and DoCM

should be part of #148

There is a huge amount of variant data for many CIViC genes and this level of meta-data, for a relatively small fraction of DGIdb drug-gene interactions seem unnecessary. Instead we should just link to appropriate CIViC gene or variant pages from CIViC interaction claims.


Simplify check and return handling

Why not simplify:
            call check(error, all(input == expected))
            if (allocated(error)) return

to:
            if (check(error, all(input == expected))) return

Beyond that, the only other way to simplify is using macros, but I like that this is very usable without macros.

Using subroutines instead of functions for test-drive was a deliberate choice, but I'm open to discuss and reevaluate this decision.
The optimal unit test should not require a return statement at all. Instead we should encourage aiming for smaller tests, the best in my opinion is to have a unit test like
subroutine test_something(error)
  type(error_type), allocatable, intent(out) :: error
  ! ... calculate something
  call check(error, actual, expected)
end subroutine test_something

In this scenario there is no need for a return statement at all. We get one test which tests exactly one thing.
In reality, of course, things are more complicated and one might need several check calls in one subroutine, especially if IO resources are involved, which have to be closed again. An example for such case would be test_stdlib_bitset_64. In this case one would end up with constructs like if (.not.check(error, ...)) then to continue testing, which I find unintuitive.
Maybe Brad @everythingfunctional can comment on this issue and his choice for vegetables, which is based on a somewhat similar logic to organize unit tests.


Change to gradient

Seemed like the slowest thing was the COBYLA maximisation call. I swapped this out for a gradient and was able to run M=40 on my laptop (although it was quite slow - maybe 10mins per step - I think due to the intense memory requirements).
Stepsize still needs tuning and possibly can do different stepsizes for propagate_params and update_params.

Yeah sorry about that, my formatter (Ruff) did that. Might be worth running Ruff on the discrete-coles-discrete branch too haha
For M=10 it won't change much for larger M I found the many calls to negative_expected_log_obs_dens were the time bottleneck so replacing this with just the single grad improved the speed. Although memory quickly becomes the issue.
I barely changed anything, just added some checking to lambdas_rate_computation to avoid nans - this was needed to get a valid gradient. Otherwise it was just swapping COBYLA for a gradient step, changing negative_expected_log_obs_dens to do mean over matches rather than sum and maybe adding some jits.


logaritmic operations with units and decibel

Hi,
first I would like to express my gratitude and love to this tool.
But one things that is missing for me is decibel units and operations like this:
>>> 100 W -> dBW
  = 20 dBW
>>> ans - 60 dBm
  = -10 dB
>>> ans -> W/W
  = 0.1 W/W

Is there plan or possibility of implementation?
From my brief overview of code log and log10 functions only take scalar numbers as inputs.
Thank you

Thank you for the feedback!
Did you see https://github.com/sharkdp/numbat/issues/217?


Added prelim plots on azure VM

Addresses #126

Thanks @harsha-simhadri.
I think that #126 is probably talking about the NeurIPS 2021 challenge? @KShivendu


clippy lints

Many many lints. Notably:

Remove unneeded Result wrapping some function return types.
if ... { panic! } to assert!
Replaced if let with map_or and similar.
Make fn const if possible.
ptr::addr_of! instead of &T as *const T
`.cast() instead of `*const T as *const U`
.cast_mut() instead of *const T as *mut T
U::from(T) instead of T as U
"{}". foo -> "{foo}"
Use Self
...

As many of these are subjective, feel free to modify/request modifications.

Many many lints. Notably:

Remove unneeded Result wrapping some function return types.

I would accept this only for non-public API. Can you check and make sure you've done this change for private and crate-private methods only? If Clippy complains in public stuff, we should suppress its warnings there.

if ... { panic! } to assert!
Replaced if let with map_or and similar.
Make fn const if possible.
ptr::addr_of! instead of &T as *const T
`.cast() instead of `*const T as *const U`
.cast_mut() instead of *const T as *mut T
U::from(T) instead of T as U
"{}". foo -> "{foo}"
Use Self
...

As many of these are subjective, feel free to modify/request modifications.

The rest is fine. I don't have strong feelings for doing it one way or the other. These are stylistic changes and as you say, sometimes subjective.
As long as Clippy stays silent, I'm happy.

Actually one more thing: None of your improvements seem to address the actual clippy complaints which are currently failing the CI? All of the failures in the CI seem to be related to Clippy demanding that we use explicit turbofish typecasts when using core::mem::transmute. I think these should be addressed with priority.

And... your PR has come flicts. You need to rebase your PR on top of master. As in git checkout <your-branch>. Then git pull. Then git rebase master --interactive. ... and resolve all conflicts and upon resolving git rebase --continue until no conflicts are left and all your commits are on top of master.

... where upstream/master is the upstream master branch of esp-idf-svc. You can create the upstream remote repo with git remote add https://github.com/esp-rs/esp-idf-svc.

Ok conflicts seem to be fixed now, but clippy is still not happy. See the failing CI. I think given that this PR addresses Clippy lints, the CI should -as a minimum - be passing.

Can you confirm that you've done these changes in an automatic fashion, and how exactly?

Unfortunately not as clippy --fix only works with a small subset of lints. Additionally it can't reason about as *const _ as *mut _ -> .cast().cast_mut() without type hints. If you don't want to merge the changes due to this I completely understand. If you like I could submit multiple smaller PRs so the changes can be more easily reviewed.
Would you consider removing the unnecessary Result on the EthDriver callbacks in the next major/API update?

Can you confirm that you've done these changes in an automatic fashion, and how exactly?

Unfortunately not as clippy --fix only works with a small subset of lints. Additionally it can't reason about as *const _ as *mut _ -> .cast().cast_mut() without type hints. If you don't want to merge the changes due to this I completely understand. If you like I could submit multiple smaller PRs so the changes can be more easily reviewed.

Splitting into multiple smaller PRs would help then.

Would you consider removing the unnecessary Result on the EthDriver callbacks in the next major/API update?

Not sure. Why do you need that so much?

Not sure. Why do you need that so much?

I don't need it per se, I just think it's bloat since it always returns Ok(()).

Not sure. Why do you need that so much?

I don't need it per se, I just think it's bloat since it always returns Ok(()).

I think this is insignificant in the grant scheme of things. And it is not worth it to break backwards compatibility - even for a new API - because of this. Not to mention that in future we might need a result-returning API after all.

Closing this, will split into smaller PRs.


Adding newly available regions

#sign-off knowing I'll need to follow up :)

@iainfoulds: I'm sorry - only the author of this article, @stepro, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


rancher-server consumes lot of cpu when large number volumes are purged.

Rancher server version - v1.1.0-storage-2
Set up has 3 ROS hosts.
Had about 10 Vm that had ROOT and DATA volumes in longhorn driver.
Had snapshots taken for many of these volumes.
reverttosnapshot and restorefrombackup where performed for many of the volumes.
Deleted all the VMs.
Deleted and purged all the "Inactive" volumes.
After few seconds , one of the hosts in the set up got rebooted .Host went from Active->Reconnecting->Active. - This issue is tracked in https://github.com/rancher/longhorn/issues/132
We also notice that the UI becomes non responsive during this time and cpu usage for  rancher-server is very high:
Rancher server box had 2 processor , 2 GHZ cpu.
top - 18:54:30 up  5:47,  2 users,  load average: 48.73, 28.82, 13.16
Tasks:  93 total,   2 running,  91 sleeping,   0 stopped,   0 zombie
%Cpu(s): 85.4 us, 11.8 sy,  0.0 ni,  0.2 id,  0.0 wa,  0.0 hi,  2.7 si,  0.0 st
KiB Mem:   2049916 total,  1821328 used,   228588 free,   120660 buffers
KiB Swap:        0 total,        0 used,        0 free.   399996 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
20075 root      20   0 2786136 951376  17404 S 154.2 46.4   8:05.45 java
20090 message+  20   0 1362768 175908   7452 S  42.1  8.6   1:31.19 mysqld
  140 root      20   0       0      0      0 S   1.7  0.0   0:33.87 jbd2/vda1-8
20215 root      20   0  191996  11916   4676 S   1.0  0.6   0:03.67 websocket-proxy
    7 root      20   0       0      0      0 S   0.3  0.0   0:13.46 rcu_sched
   17 root      20   0       0      0      0 S   0.3  0.0   0:05.87 ksoftirqd/1
20668 root      20   0       0      0      0 S   0.3  0.0   0:00.04 kworker/u4:0
    1 root      20   0   33464   2012    660 S   0.0  0.1   0:01.90 init

In fact it won't need to purge tons of volume to reproduce. Just start 10 vms with both root and data disk at longhorn at the same time can freeze the UI. I got >80% CPU utilization on GCE n1-standard(1vcpu, 4gb memory).


conflict between -P and -o parameters ?

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2021.12.27. (update instructions)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Until now, I have been working in Windows with yt-dlp.exe in my download directory and it worked without any problems
Yt-dlp downloads my videos into the same directory as yt-dlp.exe.
My -o output templates have also been working fine.
Now however, I have to specify a download location different from the yt-dlp.exe location, but my --path and -o parameters don't seem to like each other:
command: yt-dlp gr51aVj-mLg -v --ignore-config --paths "c:\Users\User\Downloads\yt" -o "%(playlist|)s\file.%(ext)s"
results:
    ❌ "WARNING: --paths is ignored since an absolute path is given in output template" although no absolute path is used
    ❌ C:\ is used instead of the requested download dir
log:
yt-dlp gr51aVj-mLg -v --ignore-config --paths "c:\Users\User\Downloads\yt" -o "%(playlist|)s\file.%(ext)s"
[debug] Command-line config: ['gr51aVj-mLg', '-v', '--ignore-config', '--paths', 'c:\\Users\\User\\Downloads\\yt', '-o', '%(playlist|)s\\file.%(ext)s']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2021.12.27 [6223f67] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg N-105208-gb24f0c82b3-20220108 (setts), ffprobe N-105208-gb24f0c82b3-20220108
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
[debug] [youtube] Extracting URL: gr51aVj-mLg
[youtube] gr51aVj-mLg: Downloading webpage
[youtube] gr51aVj-mLg: Downloading android player API JSON
[youtube] gr51aVj-mLg: Downloading MPD manifest
[youtube] gr51aVj-mLg: Downloading MPD manifest
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] gr51aVj-mLg: Downloading 1 format(s): 244+140
WARNING: --paths is ignored since an absolute path is given in output template
WARNING: Requested formats are incompatible for merge and will be merged into mkv
[download] c:\file.mkv has already been downloaded

If I remove the "|" character in my output template, the warning disappears:
command: yt-dlp gr51aVj-mLg -v --ignore-config --paths "c:\Users\User\Downloads\yt" -o "%(playlist)s\file.%(ext)s"
results:
    ✅ the specified download dir is respected
log:
yt-dlp gr51aVj-mLg -v --ignore-config --paths "c:\Users\User\Downloads\yt" -o "%(playlist)s\file.%(ext)s"
[debug] Command-line config: ['gr51aVj-mLg', '-v', '--ignore-config', '--paths', 'c:\\Users\\User\\Downloads\\yt', '-o', '%(playlist)s\\file.%(ext)s']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2021.12.27 [6223f67] (win_exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.19043-SP0
[debug] exe versions: ffmpeg N-105208-gb24f0c82b3-20220108 (setts), ffprobe N-105208-gb24f0c82b3-20220108
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
[debug] [youtube] Extracting URL: gr51aVj-mLg
[youtube] gr51aVj-mLg: Downloading webpage
[youtube] gr51aVj-mLg: Downloading android player API JSON
[youtube] gr51aVj-mLg: Downloading MPD manifest
[youtube] gr51aVj-mLg: Downloading MPD manifest
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] gr51aVj-mLg: Downloading 1 format(s): 244+140
WARNING: Requested formats are incompatible for merge and will be merged into mkv
[download] c:\Users\User\Downloads\yt\NA\file.mkv has already been downloaded

There seems to be a problem, because the "|" is allowed and used in the README examples and aside from that, the (more complex) output formats I am using have always been working well when I have not used the --path parameter.

There is a tricky situation going on here. When playlist is not present, your output template -o "%(playlist|)s\file.%(ext)s" becomes \file.mkv. Because of the \, it gets interpreted as an absolute path. I am not sure how to "fix" this, or if it even can be fixed unambiguously
You can workaround by passing .\%(playlist|)s\file.%(ext)s or  %(playlist|.)s\file.%(ext)s to clarify to yt-dlp that it is in fact a relative path

Thanks for your quick reply.

Because of the \, it gets interpreted as an absolute path.

Ok. Sorry, I did not know that. This is the first I see it interpreted it that way. I am only used to absolute paths including drive letters.

 That seems to solve the issue, judging from a quick test.

Thanks for your quick reply.

Because of the \, it gets interpreted as an absolute path.

Ok. Sorry, I did not know that. This is the first I see it interpreted it that way. I am only used to absolute paths including drive letters.

 That seems to solve the issue, judging from a quick test.

This is the first I see it interpreted it that way. I am only used to absolute paths including drive letters.

On UNIX, / points to the root
and on windows, it points to the root of the current drive

That seems to solve the issue, judging from a quick test.

Since that fixes your issue, I am closing this. I honestly don't know whether to treat it as a bug or not. But either way, it's not clear how to resolve this unambiguously. If more people have this issue, we can  see if anything can be done. Right now, I dont think it is worth trying to fix it

ok, thanks for the feedback


Bugfix doc as attr #78

Adresses #78

Codecov Report

Merging #79 (f9ec69b) into main (b816d73) will decrease coverage by 0.61%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
- Coverage   97.12%   96.51%   -0.62%
==========================================
  Files          11       11
  Lines         870      861       -9
==========================================
- Hits          845      831      -14
- Misses         25       30       +5

Impacted Files
Coverage Δ

...rib/autodoc_pydantic/directives/autodocumenters.py
98.78% <100.00%> (+<0.01%)
:arrow_up:

.../autodoc_pydantic/directives/options/validators.py
77.14% <0.00%> (-5.72%)
:arrow_down:

...xcontrib/autodoc_pydantic/directives/directives.py
97.46% <0.00%> (-2.54%)
:arrow_down:

sphinxcontrib/autodoc_pydantic/utility.py
45.83% <0.00%> (-2.17%)
:arrow_down:

.../autodoc_pydantic/directives/options/composites.py
97.36% <0.00%> (-1.34%)
:arrow_down:

sphinxcontrib/autodoc_pydantic/inspection.py
100.00% <0.00%> (ø)

.../autodoc_pydantic/directives/options/definition.py
100.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 b816d73...f9ec69b. Read the comment docs.


Add function to count all meals on home page

In this PR, we added a function to count all meals displayed on the home page and display the total meal count in the header.

Hi @dennis-every, there is nothing else to say other than... it's time to merge it :shipit:


Script test helper

This adds a simple test helper used to run scripts via the SDK.
As the project grows we'll have more an d more tests running scripts, and every time the SDK releases breaking changes we'll have to update the syntax in numerous places.
This adds the script_runner() function which can be used in SDK tests like this:
use test_helpers::script_runner;

#[tokio::test]
async fn contract_id_eq_implementation() {
    let path_to_bin = "test_projects/contract_id_type/out/debug/contract_id_type.bin";
    let return_val = script_runner(path_to_bin).await;
    assert_eq!(1, return_val);
}

Curent limitations: ATM, it just returns a  u64 value to compare against, which works well for scripts that return bool values or u64s.
A future improvement would be to have script_runner return an array of Receipts perhaps.

My first thoughts seeing this was 'if you have a script oriented test then just add it to the E2Es' but this is more to have some supplementary tests attached to other std-lib tests, and to keep them all localised?

@otrho yeah, some of the stdlib tests don't require contracts, and running a script is perfectly adequate.
I'd like to keep all the stdlib tests in one place though, and as the SDK allows testing scripts as well as contracts we've been doing these kind of tests under the sdk-harness. Basically organizing the tests by what we're testing rather than how we're testing if that makes sense.


[SPARK-45024][PYTHON][CONNECT] Filter out some configurations in Session Creation

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/42694 filtered out static configurations in local mode
This filter out some configurations in both local mode and non-local mode, since the configurations are actually set after session creation, so configurations like spark.remote always take no effect.
Why are the changes needed?
avoid unnecessary RPCs and warnings
Does this PR introduce any user-facing change?
no
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
no

CI link: https://github.com/zhengruifeng/spark/actions/runs/6032019013

cc @HyukjinKwon

thanks, all tests passed, merged to master


simple_job_models.py

Hi
I am trying to understand the code because so far it is not working for me. I am still stuck at the first iteration.
I have a DB of 4.8M compounds. I am using a smaller DB because I want to make sure it is working to some extents before committing to a larger DB. I have docked ~24000 compounds (8000 each for training set, validation set and test set)
The training_labels.txt, validation_labels.txt and test_labels.txt files are created to store the docking scores and IDs.
python phase_2/simple_job_models.py -n_it 1 -mdd green_DB_MorganFP/ -time 00-60:00 -file_path deep-docking-v2/proteinx -nhp 12 -titr 8 -n_mol 8000
and ran the 24 scripts generated. For each of them, it firstly says "Training size not specified, using entire dataset..." (I am not sure if this is normal) then always ends with "There are not enough hits... exiting."

I then changed the n_mol to 100000
python phase_2/simple_job_models.py -n_it 1 -mdd green_DB_MorganFP/ -time 00-60:00 -file_path deep-docking-v2/proteinx -nhp 12 -titr 8 -n_mol 100000

It does not help.
I realised the code may only work for training size = 1M, so I then changed all "1000000" number in progressive_docking.py file to 8000 which is my training set size but it did not help at all. It still complains about not enough hits. But from my understanding there will always be some "hits" based on how many top score compounds I defined them as hits
Apart from this, I actually want to understand this bit
line 75 to 79 in simple_job_models.py
# sums the first column and divides it by 1 million
## is this the average score for the molecules? Why divide by 1000000?
### [[0]] would return a dataframe and .sum() is buggy on dataframes (see: https://stackoverflow.com/questions/52912693/pandas-sum-return-the-infinite-value)
### replace with => pd.to_numeric(df[0]).sum()  # returns a single number representing the sum
t_mol = pd.read_csv(mdd+'/Mol_ct_file.csv',header=None)[[0]].sum()[0]/1000000 # num of compounds in each file is mol_ct_file

what is this t_mol suppose to be or play any role in the training?
Can you comment on the comments, does it need to correct?

Hi,
it looks like your train and validation sets were not read correctly (their shape is just 0,1). This causes the "not enough hits" problem. Could you check the size of training morgan fingerprints (in morgan folder) and labels (in iteration folder)? Also, did you create those with the provided scripts?

Hi Albert,
the per million thing should work fine, no need to change it. It just tells how many compounds will be sampled per million from each file, but if you specify less sampling molecules it will be rescaled. We used that in an earlier version of the program and we kept it just in case we need in the future. To confirm, just check that your *set.txt files are populated as you expect.
Regarding the percentage, you just need to specify initial one and final one. It is gradually decreased in the script for later iterations (not directly on the percent value but see line 124
good_mol = int(((100-first_mols)*n_it + titr*first_mols-100)/(titr-1))

Let us known if this makes sense and if you encounter other issues.

How large should the first training, test, and validation set be.  I was just testing the package to see how/if I could get it to work.  After using a threshold to keep docked molecules, I had (not including header line) only 143 molecules for training_labels.txt, 51 for testing_labels.txt , and  47 for validation_labels.txt.  I also get this below.  Also not sure why shape is 1 less molecule for train (see below 142) and test (see below 50)
Data acquired...
Train shape: (142, 1) Valid shape: (47, 1) Test shape: (50, 1)
Data Augmentation iteration 1 data shape: (142, 1)
Training labels shape:  (142, 1)
There are not enough hits... exiting.
qqq