SEPG Automated Release - v4.0.1

SEPG Details
Release Build Link: https://sou-jenkins2.swinfra.net/job/Auto-Release/553/
Build Token: github.com/CAFapi/opensuse-base-images/main/1d07332826e45d6b4ca021ca66b62e917863ea54
Versioning Behaviour: Roll on to next minor
Artifacts For Release
Docker

cafapi/opensuse-base:4.0.1 (Static Tag)
cafapi/opensuse-base:4.0 (Dynamic Tag)
cafapi/opensuse-base:4 (Dynamic Tag)
cafapi/opensuse-base:latest (Dynamic Tag)
cafapi/opensuse-dotnet6-aspnet:4.0.1 (Static Tag)
cafapi/opensuse-dotnet6-aspnet:4.0 (Dynamic Tag)
cafapi/opensuse-dotnet6-aspnet:4 (Dynamic Tag)
cafapi/opensuse-dotnet6-aspnet:latest (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:4.0.1 (Static Tag)
cafapi/opensuse-dotnet6-runtime:4.0 (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:4 (Dynamic Tag)
cafapi/opensuse-dotnet6-runtime:latest (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:4.0.1 (Static Tag)
cafapi/opensuse-dotnet6-sdk:4.0 (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:4 (Dynamic Tag)
cafapi/opensuse-dotnet6-sdk:latest (Dynamic Tag)
cafapi/opensuse-jdk11:4.0.1 (Static Tag)
cafapi/opensuse-jdk11:4.0 (Dynamic Tag)
cafapi/opensuse-jdk11:4 (Dynamic Tag)
cafapi/opensuse-jdk11:latest (Dynamic Tag)
cafapi/opensuse-jdk17:4.0.1 (Static Tag)
cafapi/opensuse-jdk17:4.0 (Dynamic Tag)
cafapi/opensuse-jdk17:4 (Dynamic Tag)
cafapi/opensuse-jdk17:latest (Dynamic Tag)
cafapi/opensuse-jdk8:4.0.1 (Static Tag)
cafapi/opensuse-jdk8:4.0 (Dynamic Tag)
cafapi/opensuse-jdk8:4 (Dynamic Tag)
cafapi/opensuse-jdk8:latest (Dynamic Tag)
cafapi/opensuse-jre11:4.0.1 (Static Tag)
cafapi/opensuse-jre11:4.0 (Dynamic Tag)
cafapi/opensuse-jre11:4 (Dynamic Tag)
cafapi/opensuse-jre11:latest (Dynamic Tag)
cafapi/opensuse-jre17:4.0.1 (Static Tag)
cafapi/opensuse-jre17:4.0 (Dynamic Tag)
cafapi/opensuse-jre17:4 (Dynamic Tag)
cafapi/opensuse-jre17:latest (Dynamic Tag)
cafapi/opensuse-jre8:4.0.1 (Static Tag)
cafapi/opensuse-jre8:4.0 (Dynamic Tag)
cafapi/opensuse-jre8:4 (Dynamic Tag)
cafapi/opensuse-jre8:latest (Dynamic Tag)
cafapi/opensuse-nodejs18:4.0.1 (Static Tag)
cafapi/opensuse-nodejs18:4.0 (Dynamic Tag)
cafapi/opensuse-nodejs18:4 (Dynamic Tag)
cafapi/opensuse-nodejs18:latest (Dynamic Tag)
cafapi/opensuse-python3:4.0.1 (Static Tag)
cafapi/opensuse-python3:4.0 (Dynamic Tag)
cafapi/opensuse-python3:4 (Dynamic Tag)

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

RETRY

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Auto-Release/554/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

 Build Stage
Action
Status

Release Checks
completed
:heavy_check_mark:

Gather Release Data
completed
:heavy_check_mark:

QA Documentation Site Deployment
n/a
:heavy_check_mark:

QA Deployment Branch Promotion
n/a
:heavy_check_mark:

Docker Image Promotion
in progress
:x:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Release2/1373/

Build Stage
Action
Status

Release Checks
failed
:x:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

The Auto-Release has failed. Check the build log using the link provided below to identify the issue. Once the issue is resolved the Auto-Release can be re-commenced by adding a new comment containing just the word RETRY. This comment will be picked up by the build machine and the automated release process will pick up where it left off, skipping the already completed steps and updating the PR with completion statuses of the remaining steps.
view the build log here

This pull request has an approved review but is not in a mergable state, this is likely due to some protection rule that hasn't been satisfied.
Check the bottom of this pull request for details.
Once all protection rules have been met, if an new Auto-Release run is not automatically triggered, add a comment that says RETRY to re-commence the auto-release.

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Release2/1375/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Release2/1377/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here

Retrying Auto-Release.....
Release Build Continuation: https://sou-jenkins2.swinfra.net/job/Release2/1378/

Build Stage
Action
Status

Release Checks
in progress
:clock130:

Gather Release Data

:white_small_square:

QA Documentation Site Deployment

:white_small_square:

QA Deployment Branch Promotion

:white_small_square:

Docker Image Promotion

:white_small_square:

Maven Artifact Promotion (Closed Source)

:white_small_square:

NuGet Artifact Promotion

:white_small_square:

Artifactory Release Artifact Tagging

:white_small_square:

Generic Artifact Promotion

:white_small_square:

Maven Artifact Promotion (Open Source)

:white_small_square:

Maven Staging Repository Removal (Open Source)

:white_small_square:

Git Tagging

:white_small_square:

Git Release

:white_small_square:

Git Release Asset Deployment

:white_small_square:

Pull Request Merge

:white_small_square:

Release Branch Deletion

:white_small_square:

view the build log here


netease-music-tui: 0.1.2 -> 0.1.3

Add update-cargo-lock.sh as well.

Motivation for this change
Update version.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Should I do something else, such as rebase these commit?

Should I do something else, such as rebase these commit?

Not required. I just squash merge it.


fix: remove dead code

leftover from https://github.com/fedimint/fedimint/pull/1899

Codecov Report
Patch coverage has no change and project coverage change: +0.01 :tada:

Comparison is base (7f04069) 62.94% compared to head (a49fce1) 62.96%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1912      +/-   ##
==========================================
+ Coverage   62.94%   62.96%   +0.01%
==========================================
  Files         137      137
  Lines       26517    26517
==========================================
+ Hits        16692    16697       +5
+ Misses       9825     9820       -5

Impacted Files
Coverage Δ

fedimint-testing/src/bin/fixtures.rs
0.25% <ø> (ø)

... and 7 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Linting of generated output

Do you intend to merge this, or https://github.com/adsharma/py2many/pull/160 and then I can rebase.


Command should not be available for files

Thanks again for this @Tyriar! I am just reporting some small things after my first testing:
The command "Open in Windows Terminal" should not be available for files, but only for folders since opening a file with a shell does not make any sense.

Or instead of now being available, it should just open the Terminal in the directory of the file.


Support auto-joining multiple arguments

Given the following code:
foo(bar)
foo(baz)
foo(bongo)

We'd like to support issuing the command "bring arg zip and gust to after bat", resulting in the following:
foo(bar, baz, bongo)
foo(baz)
foo(bongo)

This behaviour is briefly described in https://github.com/pokey/cursorless-vscode/issues/60#issuecomment-873100970

Closed by #339


Is it proper to deprecate submarine-cloud ?

There are two submarine-cloud in Submarine and the introduction of submarine-cloud-v2 is complete.
Could we deprecate submarine-cloud ?
Please feel free to correct me if I missed something, thanks.

The related jira is filed.


udp: limit number of reads per event loop

Commit Message: To prevent long event loop if too many UDP packets are in queue, limit how many packets to read in each event loop. If haven't finished reading, artifacts a READ event to continue in the next event loop.
Additional Description: add numPacketsExpectedPerEventLoop() callback to UdpListenerCallback, so that QUIC listener can tell how many packets it wants to read in each loop. The actually number of packets read are still bound by MAX_NUM_PACKETS_PER_EVENT_LOOP.
Risk Level: low
Testing: added udp listener unit tests.

Still seeing compile errors.
/wait
opt/bin/include/envoy/server/overload/_virtual_includes/thread_local_test/common/network/udp_fuzz.cc:68:30: error: variable type 'Envoy::(anonymous namespace)::FuzzUdpListenerCallbacks' is an abstract class
2021-05-05T16:48:52.3387670Z     FuzzUdpListenerCallbacks fuzzCallbacks(this);
2021-05-05T16:48:52.3388166Z                              ^
2021-05-05T16:48:52.3389409Z bazel-out/k8-opt/bin/include/envoy/network/_virtual_includes/listener_interface/envoy/network/listener.h:337:18: note: unimplemented pure virtual method 'numPacketsExpectedPerEventLoop' in 'FuzzUdpListenerCallbacks'
2021-05-05T16:48:52.3390197Z   virtual size_t numPacketsExpectedPerEventLoop() const PURE;
2021-05-05T16:48:52.3390618Z                  ^
2021-05-05T16:48:52.3391158Z 1 error generated.

/retest

also if this solves https://github.com/envoyproxy/envoy/issues/16335 does it also fix any of
https://github.com/envoyproxy/envoy/issues/16278 (flaky quic_http_integration_test)
https://github.com/envoyproxy/envoy/issues/16493 (flaky QuicHttpIntegrationTest)
https://github.com/envoyproxy/envoy/issues/16198 (slow tests)
basically I wonder if the others were caused by looping/starvation?

also if this solves #16335 does it also fix any of
#16278 (flaky quic_http_integration_test)

Yeah, this PR should fix these two.

#16493 (flaky QuicHttpIntegrationTest)

There is another data race in FakeUpstream needs to be addressed in the test helper function.

#16198 (slow tests)
basically I wonder if the others were caused by looping/starvation?

It didn't fully resolve the slowness as I retried to remove the TSAN timeout factor and extra upstream timeout, the tests still failed, though at a much lower rate.

/lgtm api


add licensing info, both repo and contributions

We need a license, and I guess this is the standard thing.

Is the policy right and wording good?

Do we want user contributions to be SA/copyleft?  Perhaps that is
more comfortable for audience contributions...

Is the policy right and wording good?

Very good, thanks!

Do we want user contributions to be SA/copyleft?  Perhaps that is
more comfortable for audience contributions...

Should I make a follow-up issue with the questions?


Update camtwist beta checksum

Not sure how often this changes - should we keep updating or just set to :no_check?

@iggyvolz Plan on updating/rebasing this?

Sorry about this, looks like I lost it in the shuffle and I got overwhelmed by a server problem today so I couldn't check my GitHub.  I'll look back into it later tonight and/or this weekend.

It looks like this has been resolved in the meantime in #631.


when users whispers are off !$timeout does not work

here are the logs:
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,255] [DEBUG  ] Cache Miss: api:twitch:helix:user:by-id:95676405
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,256] [DEBUG  ] Successfully loaded OAuth token from storage
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,403] [DEBUG  ] Cache Miss: api:twitch:helix:user:by-id:885591395
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,492] [DEBUG  ] Cache Miss: api:twitch:helix:user:by-id:794213329
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,575] [DEBUG  ] Loaded config
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,633] [INFO   ] PostgreSQL Server notice: NOTICE:  relation "schema_version" already exists, skipping
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,635] [DEBUG  ] migrate db: current revision ID is 17
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,635] [DEBUG  ] migrate db: 0 revisions to run
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,638] [DEBUG  ] migrate redis: current revision ID is 3
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,639] [DEBUG  ] migrate redis: 0 revisions to run
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,865] [INFO   ] Set current stream chunk here to <pajbot.models.stream.StreamChunk object at 0x7f2f0c9b8100>
Mar 12 17:44:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:40,987] [INFO   ] Loaded 0 timers (0 online/0 offline)
Mar 12 17:44:41 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:41,653] [INFO   ] Try to load submodule with ID None
Mar 12 17:44:41 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:41,654] [INFO   ] Granting admin privileges to mr_cheeezz (505216805)
Mar 12 17:44:41 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:41,822] [DEBUG  ] Successfully loaded OAuth token from storage
Mar 12 17:44:42 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:42,254] [INFO   ] Successfully connected and authenticated with IRC
Mar 12 17:44:43 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:44:43,041] [INFO   ] WebSocket connection open
Mar 12 17:45:00 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:45:00,779] [DEBUG  ] Cache Miss: api:twitch:helix:stream:by-id:95676405
Mar 12 17:45:06 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:45:06,800] [DEBUG  ] UserRanksRefreshManager::_refresh function took 158.458 ms
Mar 12 17:45:08 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:45:08,803] [DEBUG  ] Replacing $(1) with
Mar 12 17:46:24 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:46:24,988] [DEBUG  ] Replacing $(1) with
Mar 12 17:46:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:46:40,905] [DEBUG  ] Cache Miss: api:twitch:helix:channel-information:95676405
Mar 12 17:46:48 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:46:48,908] [DEBUG  ] Replacing $(1) with
Mar 12 17:46:52 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:46:52,514] [DEBUG  ] Replacing $(1) with @ウシウィ
Mar 12 17:47:45 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:47:45,075] [DEBUG  ] Replacing $(1) with
Mar 12 17:48:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:48:40,829] [DEBUG  ] Cache Miss: api:twitch:helix:channel-information:95676405
Mar 12 17:49:30 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:49:30,401] [DEBUG  ] Replacing $(1) with @ウシウィ
Mar 12 17:49:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:49:40,770] [DEBUG  ] Cache Miss: api:twitch:helix:videos:by-id:95676405
Mar 12 17:50:20 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:20,886] [DEBUG  ] Cache Miss: api:twitch:helix:stream:by-id:95676405
Mar 12 17:50:23 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:23,803] [DEBUG  ] Rebuilding commands...
Mar 12 17:50:23 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:23,805] [DEBUG  ] Done rebuilding commands
Mar 12 17:50:29 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:29,395] [DEBUG  ] Cache Miss: api:twitch:helix:user:by-login:wussiwy
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:33,801] [ERROR  ] Logging an uncaught exception (ActionQueue)
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]: Traceback (most recent call last):
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]:   File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]:     result = self.fn(*self.args, **self.kwargs)
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]:   File "/opt/pajbot/pajbot/utils/time_method.py", line 22, in wrap
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]:     ret = f(*args, **kwargs)
Mar 12 17:50:33 vmi1065408 pajbot@maycris[72126]: TypeError: _refresh() missing 1 required positional argument: 'action_queue'
Mar 12 17:50:40 vmi1065408 pajbot@maycris[72126]: [2023-03-12 17:50:40,725] [DEBUG  ] Cache Miss: api:twitch:helix:channel-information:95676405

it does work it just does not whisper them.


code cleanp and enable services auto-start on reboot.

Following items are being addressed under this PR.
abstracting upstart and systemd service definitions in services roles/defaults. This will cut down duplicated code for service setup, service restart, service start, etc by OS. Also, will help managedthe systemd/upstart conf file information in one place.

generate systemd for centos and rhel (for rhel am making sure it matches up to what rhel rpm writes minus args to rhel specific config fragments)

avoid some skip tasks by logically grouping tasks under block by OS where it make sense

ensure services are enabled to autostart on reboot

For now am focusing on, keystone, glance, cinder, nova, neutron

Got following comments on this PR. I will work on making those changes soon.
1: rename service role to openstack_meta
2: update the variable structure in openstack_meta to follow - openstack_meta.keystone[os].service_name
3: we will rely on set_facts for os which is currently done in pre-flight role.

retest

retest

retest


Notepadplusplus

This is from @ferventcoder.
I updated all 3 packages, but can't push as I am not maintainer.  I will use in the future version 0.0 do denote that it is intented to run the updater.

I had to use NoCheckUrl although I don't want to becasue my current implementation of this AU feature timeouts quite frequently. See https://github.com/majkinetor/au/issues/35
@gep13, can you reproduce this behavior or is it location specific ?
I can't figure out how to do this so far, everything I tried either downloads the entire file or doesn't work, so any help is highly appreciated. This check is very important in order not to push spoiled packages (it protects from vendor site changes). For some sites its OK to use NoCheckUrl (for example FossHub).

@majkinetor yes, I am seeing the same issue with the URL Checking as you mentioned.

@gep13
Thx for verifying. So this would definitelly need to get inproved.... i have no idea why that call timesout


🎉 2.0.2

ℹ About this release

Version: 2.0.2
Type: patch
Last Release: 2.0.1 (5/2/2023, 7:19:46 PM) [?]
Commits to merge: 13 [?]

📦 Dependencies

Update @prisma/client from ^4.13.0 to ^4.14.0
Update prisma from ^4.13.0 to ^4.14.0

📦 Development Dependencies

Update @types/node from ^18.15.11 to ^18.16.3
Update @typescript-eslint/eslint-plugin from ^5.57.0 to ^5.59.2
Update @typescript-eslint/parser from ^5.57.0 to ^5.59.2
Update eslint-plugin-jsonc from ^2.7.0 to ^2.8.0
Update typedoc from ^0.24.6 to ^0.24.7

:tada: This PR is included in version 2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
Docker container (sebbo2002/fhem-log2db:2.0.2)
v2.0.2

Your semantic-release bot :package::rocket:


[FR] Purchase Order Variables

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

Problem statement
Looking for the Purchase order Variable Names for Purchase order Templates.
On the Docs page under purchase orders there are non of the Variables listed, where could i find the list of the variables.
Suggested solution
Can we get a update to the Docs? Or where in the code can i find a list of the variables available,
Describe alternatives you've considered
..
Examples of other systems
No response
Do you want to develop this?

[ ] I want to develop this.

Closed due to lack of activity


Fix silent FFMPEG failure

This pull request addresses issue #26 by ensuring an error message is displayed when the trimesh, pyrender, and/or JITRenderer modules fail to import due to a missing ffmpeg library, rather than allowing the process to fail silently.
Note that this use of try/except is still problematic and should probably be addressed in future updates. But at least this temporary fix will keep people from spending a lot of time trying to figure out the issue.

SOLUTION:

install ffmpeg on your system
put this in your main runtime to make sure that your code points correctly to your ffmpeg binary

import os
os.environ["IMAGEIO_FFMPEG_EXE"] = "/usr/bin/ffmpeg"


add base solvers to docs and fix solver tutorial

Description
Fix docs
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Key checklist:

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

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

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

Codecov Report

Merging #317 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #317   +/-   ##
=======================================
  Coverage   96.72%   96.72%
=======================================
  Files          53       53
  Lines        3269     3269
=======================================
  Hits         3162     3162
  Misses        107      107

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 afebdce...56527f0. Read the comment docs.


Fix run ci from pr comment

What this PR does / why we need it?
This PR ...
What is the impact of this PR?
No Breaking Change
PR relation:

Ref #

CI Settings

CI Usage
Tip: Check the CI you want to run below, and then comment /run-ci.
CI Switch

[ ] E2E Tests
[x] Web3 Compatible Tests
[ ] OCT 1-5 And 12-15
[ ] OCT 6-10
[ ] OCT 11
[ ] OCT 16-19
[ ] v3 Core Tests

CI Description

CI Name
Description

Chaos CI
Test the liveness and robustness of Axon under terrible network condition

Cargo Clippy
Run cargo clippy --all --all-targets --all-features

Coverage Test
Get the unit test coverage report

E2E Test
Run end-to-end test to check interfaces

Code Format
Run cargo +nightly fmt --all -- --check and cargo sort -gwc

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OCT 1-5 | 6-10 | 11 | 12-15 | 16-19
Run the compatibility tests provided by OpenZeppelin

/run-ci

/run-ci

/run-ci

/run-ci

/run-ci

/run-ci


Remove PropertyKey.Template.MASTER_JOURNAL_UFS_OPTION

MASTER_JOURNAL_UFS_OPTION is not a template, so moving it to normal PropertyKey.
Also fixing a test that's supposed to test when PropertyKey is null but is no
longer true because "fs.obs.endpoint" is a valid PropertyKey now.

alluxio-bot, merge this please


D (view changes log) opens empty window (Startify compatibility problem).

After :PlugUpdate executed from Startify window, when some updates were pulled vim-plug does open an empty vertical split to the right after pressing D to display changes log. That does not happen when no Startify window is present.

NVIM 0.1.2
Build type: RelWithDebInfo
Compilation: /usr/local/Library/ENV/4.3/clang -Wconversion -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-pa
rameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DEC
LARATIONS -DHAVE_CONFIG_H -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/build/config -I/tmp/neovim20160222-36194-1m
ereup/neovim-0.1.2/src -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/deps-build/usr/include -I/tmp/neovim20160222-3
6194-1mereup/neovim-0.1.2/deps-build/usr/include -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/deps-build/usr/inclu
de/luajit-2.0 -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/deps-build/usr/include -I/tmp/neovim20160222-36194-1mer
eup/neovim-0.1.2/deps-build/usr/include -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/deps-build/usr/include -I/tmp
/neovim20160222-36194-1mereup/neovim-0.1.2/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/u
sr/include -I/tmp/neovim20160222-36194-1mereup/neovim-0.1.2/build/src/nvim/auto -I/tmp/neovim20160222-36194-1mereup/ne
ovim-0.1.2/build/include

Optional features included (+) or not (-): +acl   +iconv    +jemalloc
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.1.2/share/nvim"

Type:

[x] Bug
[ ] Enhancement
[ ] Feature Request
[ ] Question

OS:

[ ] All/Other
[ ] Linux
[x] OS X
[ ] Windows

Vim:

[x] Terminal Vim
[ ] GVim
[ ] Neovim

@mhinz Do you know why this happens?

Start vim with no arg
We see startify window (buffer num: 1)
PlugInstall opens vertical split (buffer num: 2)
Doing PlugInstall again replaces buf 2 with empty buf 3 and opens another split for the installer

Hmm, it seems that s:prepare() calls s:new_window() which does:
  execute get(g:, 'plug_window', 'vertical topleft new')

And there's no g:plug_window after doing :PlugInstall. :-)

@mhinz Okay, we don't even need vim-plug in this picture.

vim with no args
startify window
new to open a split
bd does not close the split

I don't know if it's the expected behavior or not, but that's what's causing the extra split window.

I just remembered a related issue regarding startify:
https://github.com/junegunn/fzf/issues/225

Hmm, it seems that :bd won't close the last listed buffer.

vim -u NONE -N
:set buflisted
:new
:bd won't close the buffer (and therefore the window)

Yeah, that's what I noticed in the above issue, that I just remembered.
Here I can simply change bd to close, since bufhidden of plug window is already "wipe".

Hmm, nope, that is not ideal when let g:plug_window = 'enew'.
@kwinczek I think I'm just gonna close this issue as wontfix since it's not really critical and the solution is going to be unnecessarily complex. Sorry about that but thanks for letting me know of the issue.

No problem @junegunn. Thanks for looking into it anyway! Did set up plug to use enew and problem is gone now. Well…

@kwinczek FWIW, this works just as well.
autocmd User Startified setlocal buflisted

It might break other plugins though, which is the reason I use nobuflisted in the first place.
I didn't know about g:plug_window so far, but setting it to tabnew works well for me.

setting g:plug_window to enew? But it won't split then? That doesn't really solve the problem does it?
For now @mhinz solution works well.

We didn't "solve" the issue but instead suggested a few workarounds. As pointed above, the root cause of the problem is an odd behavior of Vim which may or may not be a bug. A proper workaround for this "behavior" will not be as trivial as I'd like it to be, so I decided not to do it.

@nhooyr Technically q works, it's just that the Startify buffer is gone by then.
I added a FAQ to Startify: https://github.com/mhinz/vim-startify/commit/44f876f4e9c95d86033257fcd85f71fc4d5f90d0


[ZEPPELIN-1552] Search button goes to next line when display's width shortens.

What is this PR for?
In document page(http://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/), the search button goes to next line when display's width shortens.
What type of PR is it?
[Improvement]
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1552
Screenshots (if appropriate)

when (768px ≤ width < 992px)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

LGTM

@hyonzin Thanks for your contribution and good catch :)
Actually I added this search feature in #1266 so it's my bad.. Appreciate for taking care of this.
Just tested and it seems not working as expected in my 13 inch screen. (FYI 13inch -> about 1248px)

So I worked around a bit to fix this, you can check it in my branch: please check this out. With my change it will be like this.

If you have time, please check this and let me know how it is! :D

@AhyoungRyu Thank you for your reply and good suggestion. I checked that in your branch and It seems to work very well!

@AhyoungRyu Thank you for your reply and good suggestion. I checked that in your branch and It seems to work very well!

@hyonzin Thx for your prompt response!
Seems the CI is not happy now with below reason
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.

The build has been terminated

LGTM 👍

CI  is green light!
Merge please @AhyoungRyu ! 😄

Yeah true! Thanks for your quick verification @tae-jun :)
And thanks again @hyonzin!
Merge if there are no more discussions.

@AhyoungRyu @tae-jun Thanks for you verification 😀


Source for views not getting registered via fetch call

H1,
I was trying to register attribution sources based of your article https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/register-attribution-source/
This is my code
const attributionReporting = {
          eventSourceEligible: true,
          triggerEligible: false,
        };

fetch(attributionUrl, { keepalive: true, attributionReporting });

I am able to get the navigation (click) source type registration working but the event (view) source type is not getting registered in chrome://attribution-internals
I do see the endpoint getting invoked and I see the response header with Attribution-Reporting-Register-Source:
{"source_event_id":"9759258831728736887","destination":"https://linkedin.com/","expiry":"2592000","priority":"0","event_report_window":"3600"}
PS the source registration for views works fine if an img tag is used.

Hi @kravish1 ,
Would you be able to share your setup or sample page where the code is working? Tried to work this out and I can see event (view) level source getting registered on my end. Would be happy to see what might be going on.
My code uses both a script tag for the dsp js where the js calls the register-source url. And also a script where the publisher calls the register-source url. Both used fetch and window.fetch.

@maybellineboon, I was able to get window.open working. Is there an api to pass attributionsrc for links that transition in-app (does not navigate to a new tab).

Hi @kravish1 ,
You can use the "_self" option for window.open if you want to open it in the current tab or use the target in window.open(url, target) to place your iframe's name in.
https://developer.mozilla.org/en-US/docs/Web/API/Window/open

@maybellineboon , for my specific case, we don't use window.open for opening the page in-app, instead we use the ember framework's router.transitionTo. I've 2 questions

Is window.open the only javascript api for us to pass the attributionsrc?
can we use fetch call or XMLHttpRequest to pass the attributionsrc for click through conversion?

Hi @kravish1 ,
From our explainers, Javascript will have the fetch and open method. Would like to understand if fetch addresses this issue? fetch should be able to call your attributionsrc and register a source without opening a new window.

@maybellineboon , fetch addressed the view through conversion by calling it in the below manner.
const attributionReporting = {
          eventSourceEligible: true,
          triggerEligible: false,
        };

fetch(attributionUrl, { keepalive: true, attributionReporting });

However, I wanna know if fetch can be used for click through conversion by setting  eventSourceEligible to false?

Hi @kravish1 ,
Looked into this further. Here's a few findings:

For the initial question on why fetch is registering clicks and not event, we can confirm that fetch performs only event.
Window.open will register click or navigation.
fetch and XMLHttpRequest (this is available) will register event or views.

As for click sources, you will need to use window.open or <a> tags. And both will need a click event and will need to `navigate

@maybellineboon , thanks a lot for your inputs. This is helpful.


question: what's the difference between instance prompt and prompt?

The instance prompt was merely an optional field intended to include the activation_word from the instance_token. I apologize for any confusion caused by the terminology. I have deleted that feature in the latest update.

Thank you for your help!


New features

Input FASTQ files supported outside the working directory
Support SGE mode
Lint functions into separate smk files


( SP: ) check videolink types and ensure it is saved on backend after we click the Update button on the EditProfile page

[ ] check videolink types
[ ]  ensure the videolink is saved on backend after we click the Update button on the EditProfile page

fixed by #2259


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Applications/Utilities (Other)/Atom.app/Contents/Resources/app/src/atom.js:54:11)
Object.activate (/Users/peterwalker/.atom/packages/fold-comments/lib/fold-comments.coffee:3:9)

Thanks for finding this and sending in a PR. Just shipped a new version with your changes!


[Docs] Add Spark Structured Streaming docs to Spark quick start guide

Change Logs
Add Spark Structured Streaming to quick start guide.
Hudi supports Strucrured Streaming reads starting from Hudi 0.8 and writes with async table services starting from Hudi 0.9.
Impact
None
Risk level (write none, low medium or high below)
None
Documentation Update
Modified spark quick start, starting from versioned doc 0.8 to current
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[x] CI passed

@bhasudha could you take a look and merge? Thanks


Update readme for Xcode 9 / Swift 4 / iOS 11

Update the requirements section, and any other sections of the readme that should change.

Complete with e580a85533033d49bdcf610073d37b022852a2f8


How to access all load balancers from Spring context

I want to create some actuator endpoints with Spring Boot and Zuul, displaying information about my load balancers. They are created by org.springframework.cloud.netflix.ribbon.SpringClientFactory, but in a child context of my application. I can access SpringClientFactory, but without knowing the name of the load balancer, I am not able to fetch it.
How would it be possible to access all load balancers from my application, without knowing their names?
I could use reflection to access org.springframework.cloud.context.named.NamedContextFactory#contexts, but I would like a less fragile solution.
I could create a pull request that would create a public get'er for the contexts, or maybe only for the keyset.
What do you think?
The question was also posted on stackoverflow, to no response.

I noticed that the class NamedContextFactory is part of https://github.com/spring-cloud/spring-cloud-commons, I will create a pull request there.


The integration pipeline does not necessarily start from normalized data.

The integration pipeline can start from “processed”, not necessarily “normalized”, data. Perheps we can call it 'merged' data here?
scvi-tools approaches even work with raw counts.

Done as this fihure is no longer included


Add support for arrays

What the PR does

Add support for Arrays
Add test cases for Arrays
Reenables test on CI

CI instanciates PG
PG is running on local on the runner
Tests are run against the real PG installation

Add a README to help running tests

Issues

Closes #12

Could you rebase on main and update the changelog please? Amusingly I can't figure out how to do it myself as your remote branch is also called main

Could you rebase on main and update the changelog please?

Sure! I don't have access to a computer right away, but count on me to do it asap!

Done!


tx-generator: add literate keys and manual funds.

This PR adds support for literate keys in benchmarking scripts
and manual definition of funds.

bors r+

bors r-

bors r+


Use content MD5 instead of file mtime to rebuild cache

Awesome library!
While the existing mtime strategy works great for local rebuilds, it does not lend itself well to environments where code is checked out on the machine right before a build - like our CI pipeline. When a build starts, the code is freshly checked out on a machine and loaded with the previous build's cache, and since the mtimes have changed on the assets, it was rebuilds from scratch, even if there were no changes.
This change uses an md5 of the uncompiled source contents as the key for a module, and determines if a new cache should be saved or if the existing cache should not be used by examining the contents of the module in question.
Open to comments and feedback - thanks!

@mzgoddard can this code https://github.com/mzgoddard/hard-source-webpack-plugin/blob/master/index.js#L426-L434 be removed?
It's being used down here: https://github.com/mzgoddard/hard-source-webpack-plugin/blob/master/index.js#L473 but this just looks like its checking that the file exists (given that when it doesn't is the only time that is set to 0). Wanted to double check before taking it out

This is something we've had several requests around at Netlify to support incremental builds. Hope this gets merged in since it would make supporting incremental builds much simpler...

@mzgoddard thanks for the detailed review and feedback! Appreciate the context here, will go back to the drawing board and combine with the mtime check

@mzgoddard I've reimplemented these changes taking into account your feedback - let me know what you think!
I've moved the md5 values out into their own cache, generated them up front when possible, made sure to record any new values (or all the values if the data cache did not exist) when the module cache is record.

I haven't looked at the implementation here, but would it be possible to mtime/checksum the entire build chain? That way you can know for sure if something needs rebuilding. Maybe something that ties into require()?

@mzgoddard any update on this PR?

Hey @nikhilmat sorry for the delay. Been going back and forth on some changes to this so I'm going to merge your work with some further changes. https://github.com/mzgoddard/hard-source-webpack-plugin/tree/337c6dab37c568ea900bf53477041539af68904e My changes break down into fixing a bug the checksums would have with some loaders, some code structure that'll make my life easier with the plugin stuff, and using cached md5s unless timestamp is newer. (Most of the delay is on that last change.)

would it be possible to mtime/checksum the entire build chain?

@wmertens That's in essence what this change is doing. Webpack Modules recognize that they are the outcome of loaders on a list of file dependencies. So webpack in watch mode checks the mtimes of those files to determine if those the derived modules are out of date. HardSource does the same but we need the checksums to deal with false positives.
Webpack's build chain comes down to finding Dependencies and building Modules for those and grouping them into Chunks. This is webpack's "make" phase. And then everything else is cake (or the "seal" and "after-compile" phases). HardSource just deals with the Modules part. We serialize the Module state that is used by most of built-in and external plugins and "templates" to produce webpack's output.

Maybe something that ties into require()?

Webpack parses require calls and notes them as Dependencies. Then it calls the Module factory for each Dependency. In the case of CommonJS require calls thats the NormalModuleFactory. HardSource hooks into NormalModuleFactory to return HardModule instances when our check says the HardSource version of a Module is still acceptable. Otherwise NormalModuleFactory does its regular thing or possibly another plugin.
By adding the checksum check to HardModule we'll be essentially hooking into require.


📎 Implment no-duplicate-selectors

Description
Implmenet no-duplicate-selectors
Want to contribute? Lets you know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.

Hi, I would like to contribute to this issue! 🙇

Still working on this one, will do a status update as soon as I can 🙇

Wrote a visitor to return the Selector groupings in a sheet.

Since we need to compare the all the selectors in the sheet against each other, as well as being able to compare whether selectors are equivalent I need to do some things to "resolve" the selector.

I created a draft PR (https://github.com/biomejs/biome/pull/2660)
Working on trying to get the selector resolver to properly resolve the & case, and then to work with AtRule.
I think the implementation is going to end up much larger than I anticipated, mainly to resolve selectors so they can be compared for equivalents.
I want to eventually remove the Visitor but right now it's the easiest way to get the nodes of interest, my other option is to get the entire list and handle it (seems like a lot of traversing for the run).
If there is some way to persist State between multiple runs that I can uses to track the resolved selectors then it may be easier to compare. 🤔

Update: working on another solution that does not rely on recursion (see the PR for context). Will attempt to reduce the scope covered by it so it's easier to review.

I think having the new semantic model will help with my solution to this. Hope to continue with it if there's no rush, but feel free to assign to someone else if they really need this!

Thanks @abidjappie. Feel free to ping me if you have the question about the model. Also, I'll write the documentation.
About this rule, you can use model.rules() to get all top-level css rules, iterate over them recursibly and check all selectors.

@togami2864 thank you!
I played around with the model yesterday and it definitely makes it a lot easier since I don't have to handle all the types of Selectors myself and I can just use the name directly for comparison.
I used type Query = SemanticServices to query it.
"Resolving" the selectors to their equivalent is still the main challenge, and I've found a few ways to achieve it but I still need to get it to pass the test cases.
I'm using a stack to avoid recursion (I was advised to avoid recursion before)!

I think that losing some of the data to the semantic model is going to make resolving them a bit difficult orz, e.g.
// selector group 1
.a, .b {
  c {}
}

// selector group 2
.d .e {
  f {}
}

These are both represented as (not true code):
[{
  Selectors: [ ".a", ".b" ]
  Child: {
    Selectors: ["c"]
  }
},{
  Selectors: [ ".d", ".e" ]
  Child: {
    Selectors: ["f"]
  }
}]

Currently, the model does not classify conditions in detail.
https://github.com/biomejs/biome/blob/a0f00fd3da235178067380899169209721199c60/crates/biome_css_semantic/src/events.rs#L109-L126
@abidjappie
About descendant Selector, how about representing like the following?
[{
  // .a .b {} (Descendant Selector)
  Selectors: [ ".a .b" ]
},{
  // .d, .e (Grouping selector)
  Selectors: [ ".d", ".e" ]
}]

And are there any other selectors or patterns need to be addressed besides the descendant combinator when implementing this rule?

@togami2864 thanks for the response.
How about something like this:
(Selectors is the same representation you mentioned above... and Resolved just demonstrates how I intend to use it)
/* Descendant combinator (space) */
.foo .bar  {}
/* Selectors: [".foo .bar"] */
/* Resolved: [".foo .bar"] */

/* Child combinator (`>`) */
/* Probably treated same as descendant, namespace, etc. */
.foo > .bar  {}
/* Selectors: [".foo > .bar"] */
/* Resolved: [".foo > .bar"] */

/* Selector list (comma) */
.a, .b { div {} }
/* Selectors: [".a",".b"], ["div"] */
/* Resolved: [".a", ".b", ".a div", ".b div"] */

/* `&` nesting selector */
.foo { .bar &:hover }
/* Selectors: [".foo"], [".bar &:hover"] */
/* Resolved: [".foo", ".bar .foo:hover"] */

/* Attribute, Class, ID selector */
type[attribute].class#id, div {}
/* Selectors: ["type[attribute].class#id", "div"] */
/* The details probably don't matter for these */

I think these cases would probably suffice for this rule. I'm not sure these are the kind of details we would want to add into the semantic model though?


Nether and End not loading chunks

When entering the end or the nether, no chunks are loaded, you just see void.  I don't know if this is possible to fix because of the mechanical changes to worlds, but it's still worth a shot to submit the report.  Thanks for the work you guys are putting into this.

Fixed in 0.3.7 see above.


Fix asn check constraints

Before this self-called recursive functions were generated:
`
int
SignedEeEnrollmentCertResponse_constraint(const asn_TYPE_descriptor_t *td, const void *sptr,
asn_app_constraint_failed_f *ctfailcb, void *app_key) {
// ...
return td->encoding_constraints.general_constraints(td, sptr, ctfailcb, app_key);
}
Now it calls parent ASN1 object if no checks were made:
int
SignedEeEnrollmentCertResponse_constraint(const asn_TYPE_descriptor_t *td, const void *sptr,
asn_app_constraint_failed_f *ctfailcb, void *app_key) {
// ...
return asn_DEF_SecuredScmsPDU.encoding_constraints.general_constraints(td, sptr, ctfailcb, app_key);
}
`


Cast boolean json fields to numbers

echo '{"bool": false}, {"bool":"true"}' | clickhouse --client  -q 'INSERT INTO test FORMAT JSONEachRow'
clickhouse --client --port 9001  -q 'select * from test;'
0
1

This is not zero-cost modification. (Anyway, test for performance degradation is missing.)
But for this feature, I expect zero cost in all cases except JSONEachRow format.
It means, that if should be somewhere in DataTypeNumber::readJSONText.

Missing test (in tests directory).


Progress Indicator while cloning stripe samples

Add a progress indicator when the cloning happens so the user gets some feedback after they've went through the samples workflow. Right now the screen just disappears and the user needs to wait for a few seconds before the workspace opening prompt pops up.

The progress indicator should be added somewhere here: https://github.com/stripe/vscode-stripe/pull/241/files#diff-a616251b82da1a5810330163f4c1ea7ab585905b04f6e9bf0b18f6fba86b1707R174
I think vscode.window.showQuickPick will show progress when a Promise is passed as the first argument.


Fix loginkit dependency

Bumps the version of FBSDKLoginKit fixing a problem when solving transitive dependencies after a pod update.
Since the version of FBSDKCoreKit is not locked, a pod update downloads the latest version (4.42.0) which introduces breaking changes for the 4.39.0 version of the FBSDKLoginKit pod used by the flutter_facebook_login package.

Another future proof strategy could be fixing the FBSDKCoreKit pod as well

Pull Request Test Coverage Report for Build 127

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.06%) to 90.476%

Totals

Change from base Build 124:
1.06%

Covered Lines:
76

Relevant Lines:
84

💛  - Coveralls

Is there something I still need to do in order to trigger the travis build? Or we just wait for @roughike approval?

It looks like FB changes its FBSDKLoginKit really fast and the latest version is already 4.43.0.
Today I had to make
s.dependency 'FBSDKLoginKit', '4.43.0'
to get the build working

Confirmed it fixes it as well via:

pinning in podspec.yaml
flutter packages get
cd ios && pod update
cd .. && flutter clean && flutter build ios

Override reference:
dependency_overrides:
  flutter_facebook_login:
    git:
      url: https://github.com/qurami/flutter_facebook_login.git
      ref: fix-loginkit-dependency

i still getting an error :(
/Users/User1/AndroidStudioProjects/my_app/ios/Pods/FBSDKLoginKit/FBSDKLoginKit/FBSDKLoginKit/Internal/FBSDKLoginCompletion.m:272:10: error: use of undeclared
identifier 'FBSDKSystemAccountStoreAdapter'
        [FBSDKSystemAccountStoreAdapter sharedInstance].forceBlockingRenew = YES;
         ^
1 error generated.

@skatzbizarro as @simeonzv mentioned, there has been further releases of the pod, this repo needs a better way for pinning that so updates of a dependency don't break that.
In the meantime, building off @dev-mush's contributions, I bumped the version in a branch of our fork, pin via:
dependency_overrides:
  flutter_facebook_login:
    git:
      url: https://github.com/AnyKindaApp/flutter_facebook_login.git
      ref: fbloginkit-fix

@skatzbizarro as @simeonzv mentioned, there has been further releases of the pod, this repo needs a better way for pinning that so updates of a dependency don't break that.
In the meantime, building off @dev-mush's contributions, I bumped the version in a branch of our fork, pin via:
dependency_overrides:
  flutter_facebook_login:
    git:
      url: https://github.com/AnyKindaApp/flutter_facebook_login.git
      ref: fbloginkit-fix

using this dependency override worked for me, Thank you very much!!!!!

Seems it's broken again:
               /Users/builder/clone/ios/Pods/FBSDKLoginKit/FBSDKLoginKit/FBSDKLoginKit/FBSDKDeviceLoginManager.m:148:31: error: no known class method for selector 'extractPermissionsFromResponse:grantedPermissions:declinedPermissions:'
                       [FBSDKInternalUtility extractPermissionsFromResponse:permissionResult
                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
               /Users/builder/clone/ios/Pods/FBSDKLoginKit/FBSDKLoginKit/FBSDKLoginKit/FBSDKDeviceLoginManager.m:151:67: error: no visible @interface for 'FBSDKAccessToken' declares the selector 'initWithTokenString:permissions:declinedPermissions:appID:userID:expirationDate:refreshDate:dataAccessExpirationDate:'
                       FBSDKAccessToken *accessToken = [[FBSDKAccessToken alloc] initWithTokenString:tokenString
                                                        ~~~~~~~~~~~~~~~~~~~~~~~~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
               2 errors generated.

I ended up creating my own fork that:

bumps to SDK v5
bumps to iOS 9 as deployment target (required due to SDK bump)
removes login behavior customization (SDK 5 just doesn't seem to support the option any more)

  flutter_facebook_login:
    git:
      url: https://github.com/kentcb/flutter_facebook_login.git
      ref: fixes

I believe this is superseded by #169. Thanks for the effort and sorry for not getting back on this earlier.


Python lint: Replace flake8 with ruff

https://docs.astral.sh/ruff is an extremely fast Python linter and code formatter, written in Rust. With over 800 linting rules, ruff can be used to replace Flake8 (plus dozens of plugins), Black, isort, pydocstyle, pyupgrade, autoflake, and more, all while executing tens or hundreds of times faster than any individual tool.

See

#806


Created a switch to disable SSL copy task

Thank you for creating the role. It was really helpful.
By default keeps the current functionality, but gives the possibility to disable the SSL copy task.

This role is going to be deprecated (see #12), so closing out this PR.


[Feature Request]Delta kernel can not get file stats

Feature request
Which Delta project/connector is this regarding?

[✓] Kernel

Overview
Since the delta-standalone has been deprecated, we are migrating out project using delta-kernel instead of delta-standalone.
But we found that delta-kernel can not get file stats when scanning file lists.
In delta-standalone, we can get file stats in this class : . And we can get the change logs
using "Iterator getChanges" in io.delta.standalone.DeltaLog which can not be list in delta-kernel too.
Motivation

out project need min&max stats of each file to do some optimization
the change logs will be used to maintain the file list cache incremental(since we can not list all file each time we scanning this table)

Further details
Willingness to contribute

[✓] No. I cannot contribute this feature at this time.

FYI @scottsand-db

Hi @wgtmac -- can you please tell me a bit more about your use case for file stats and for getChanges?
We allow you to include a filter during the ScanBuilder -- what more would you need the file stats for?
Could you also please look at this internal (not public) API for getChanges in Kernel and see if that fits your use case? We can consider making it public.
https://github.com/delta-io/delta/blob/6ae4b62845ed579bb5a19f4646831c4ee2931c02/kernel/kernel-api/src/main/java/io/delta/kernel/internal/TableImpl.java#L182

Thanks for the reply from @scottsand-db and help from @nastra!
We use the delta kernel as a metadata client in our proprietary lakehouse to read from delta lake tables. To efficiently make splits at any snapshot and cache the file lists, we need to get following metadata from the API which is available in delta standalone:

Column stats: Carry the column stats (at least the min/max values, if available) of each parquet file, therefore we can prune the list of files to scan at our best effort.
Get latest snapshot version: A cheap way to return the current version without actually replaying the delta logs.
Get change logs between arbitrary snapshots: sometimes we need to cache file list of a specific version and then incrementally sync it to the latest version. It would be great if the delta client supports incremental scan to return file list changes between a specified version range.
Stateful table object: This is similar to the request 3 above. The current table object is pined to a snapshot and cannot call update() to incrementally sync to the latest version, which the standalone library supports.

Hopefully my explanation makes sense.


Error: Disconnected occurring only on VPS

I understand that you guys HATE people posting their issued on here, but I'm totally dumbfounded at why I'm getting this error.
I have a script for handling trade offers running perfectly locally from my terminal, however, on my VPS I get the [Error: Disconnected], I've been pulling my hair out all night looking for an answer to this because I have no idea why this would be happening, thanks for any help.

No 'HATE', just question issues do not belong here because this is not a help desk. Besides, your question has nothing to do with steam-tradeoffers module anyway.


too many locals: locals exceed maximum when running component new

I'm trying to convert a component but I run into an error when running the following command:
wasm-tools component new target/wasm32-wasi/debug/fundamental_analyzer_template.wasm -o fundament-component.wasm --adapt wasi_snapshot_preview1.reactor.wasm

The error is as follows:
error: failed to encode a component from module

Caused by:
    0: failed to validate component output
    1: too many locals: locals exceed maximum (at offset 0x764c)

The error is caused thrown at this line https://github.com/bytecodealliance/wasm-tools/blob/188de0fd412dd01dd41bf91c897935934282c13d/crates/wasmparser/src/validator/operators.rs#L287 and is caused by the MAX_WASM_FUNCTION_LOCALS which is set to 50000.
When I increase the MAX_WASM_FUNCTION_LOCALS constant the problem goes away, but it doesn't seem right that I have more than 50000 local functions.
The wasm file is generated based on this wit definition: https://github.com/jeroenvervaeke/wit-issue-reproducer/blob/master/wit/fundaments_analyzer.wit
The full reproducer can be found here: https://github.com/jeroenvervaeke/wit-issue-reproducer
These are the commands to run to if you want to reproduce the issue locally: https://github.com/jeroenvervaeke/wit-issue-reproducer/blob/master/build-component.sh
Do you think this is an issue with the generated WIT code, or is it expected that this many local functions are generated?
If it's expected that so many local functions are generated, should MAX_WASM_FUNCTION_LOCALS be increased?

Thanks for the report!
This looks like it's due to a few things in play here. Fundamentally though this is an issue with wit-bindgen, LLVM, and/or Rust. If you take wit-component out of the picture  the core wasm module produced by LLVM is the one that has too many locals and is causing the validation failure. The failure here is cropping up a bit late because nothing ended up validating the input prior.
On one hand this is wit-bindgen's problem. It's generating a function so large that rustfmt is choking on it and that's one of the issues here. The generated output should be broken up a bit to avoid blowing limits in wasm/llvm/etc. (it'd also make it much faster to compile)
On the other hand this is a Rust/LLVM issue (moreso LLVM than Rust). It's known that LLVM's wasm backend is pretty good but not optimal in a lot of regards. It's likely that this same code could be translated with far fewer locals. For example compiling with optimizations does fix things but it's still not great.
Overall, though, I think this is the right place for the issue. I don't think that wit-bindgen should generate a 14kloc file from this input WIT file that's pretty small, and resolving that would fix the issue here.

Unfortuantely I think this is going to be a pretty difficult issue to solve. That being said it definitely needs a solution in wit-bindgen. The problem here stems from a foundational building block of how wit-bindgen works which is that the lowering/lifting code generated is done by walking over the "shape" of the input type. In this case it's a very large type as there's lots of recurisve fields each of which have their own recursive fields. This causes wit-bindgen to generate an exponential amount of code, causing the locals to be exceeded.
The "fix" here I believe is to move lifting/lowering into helper functions, enabling sharing and reuse. For example loading a record from memory would be a simple delegation of loading each of its fields from memory and then placing them all in a struct. This should generate a linear amount of code with respect to the input types rather than an exponential amount of code. Current use cases today shouldn't be hurt due to inlining and cases such as this should work naturally as a result.
The recursive nature of wit-bindgen is currently pretty deeply baked into the lifting/lowering, however. That will need to be extracted from the wit-parser crate most likely and refactored to support this sort of load/store pattern.
In theory there's four pieces of functionality: lifting from a flat repr, lifting from memory, lowering to a flat repr, and lowering to memory. I think the flat representations can stay as they are today though and continue to be inlined at function sites. Flat representations are only used if things "fit" which means that the real complexity comes with types stored in memory, so having helper functions for loads/stores I think is all that's necessary.
For example one change could be for wit-parser to assume that all types have a load/store function associated with them. One of the primitive instructions would then become "load this type" or "store this type" and then that helper function would get generated on the side as necessary and would internally be defined in terms of "lift this type" or "store this type"


Recommended filters from Mutect2 Filtermutectcalls

Hi,
In your current snakemake pipeline, the FILTER columns to remove from Mutect output (for example 'str_contraction' and 'multiallelic') are based on prior versions of Mutect. What FILTER values do you recommend to remove before input into MF from Mutect2 FilterMutectCalls?
base_qual
clustered_events
contamination
fragment
germline
haplotype
map_qual
multiallelic
orientation
panel_of_normals
position
slippage
strand_bias
weak_evidence
Thanks.

Hi,
In your current snakemake pipeline, the FILTER columns to remove from Mutect output (for example 'str_contraction' and 'multiallelic') are based on prior versions of Mutect. What FILTER values do you recommend to remove before input into MF from Mutect2 FilterMutectCalls?
base_qual
clustered_events
contamination
fragment
germline
haplotype
map_qual
multiallelic
orientation
panel_of_normals
position
slippage
strand_bias
weak_evidence
Thanks.

Hi @gevro ,
You could use multiallelic as the filter. The set of filters might not be so essential, since I've tried other callers (GATK, Strelka, MosaicHunter) with their default settings and still the precisions were high.
Best wishes,
Yanmei

Thank you.


Add maps with relevant nearby locations

add maps with relevant nearby locations
tweaked some markup
moved news section upward

@pya do you have merge access?

Yes.


Extension not able to be installed in VSCode

Would love to try this extension out in VSCode. However, on the marketplace site it seems like the plugin in no longer supported. Just a message:
"This extension is now unpublished from Marketplace. You can choose to uninstall it."
Can you republish? Can I help with anything?

Actually, seems like I can now 😂 Thanks!


Update to avoid the null scheduleTable

On my laptop, the resize message arrive very early before CEF initialization.
Signed-off-by: rtoslab<EMAIL_ADDRESS>

Another solution has been used in 1.6 beta


knockoutjs Replacement Syntax

Would be nice to see this work as a replacement to knockoutjs for those using RxJS.

Thank you very much for your interest and support. Unfortunately this project hasn't been maintained in quite a while, and there are much better tools for accomplishing this kind of thing now. :)


added line-height: 1; to class "no-notifications"

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


Provide a gravity lesson

[ ] concepts
[ ] code examples
[ ] incorporate examples with Mr L, specifically with Monkey character

Hi Mr. Mortensen,
Here is the Jupyter Notebook lesson that Rohan and I created: https://nighthawkcoders.github.io/teacher//2023/10/12/animations-and-layers_IPYNB_2_.html. Please let us know what you think.

This is nice to see!!!   I do think the code examples would be better if we started to work toward alien world for a little more theory and structure.   We have worked hard to try to restructure a Game project into OOP.   We should talk about it today.

FYI, notebook link in this thread is dead.

New notebook:https://nighthawkcoders.github.io/teacher//2023/10/12/animations-and-gameobjects_IPYNB_2_.html
game object and character have been separated into different js files. However, we still need to do the inheritance part.

There is gravity in game now.  Perhaps a good time to figure out if we are going to do a lesson.  Or enhance gravity to match lesson.


Open either *.xcodeproj or *.xcworkspace from a single directory

First of all, thanks for this awesome utility. I had built something similar as a Zsh function, but it had its quirks.
One thing that is a bit annoying in your version is that the default behavior opens too much.
When a project has both one or many *.xcodeproj files alongside a *.xcworkspace, everything is being opened. The preferred behavior in my opinion would be to open the workspace if it there and ignore the project files.
After reading the source code I suspected that you came to a similar realization since you added undocumented subcommands (ws in particular).
One potential solution – apart or in addition to from changing the default behavior – would be to adopt the current default behavior only when the --all flag is passed.

That sounds reasonable. Do a search for xcworkspace: if it exists, just open that.
Let me see what I can do.

@RobertAudi
Please update and test. Thank you!

Here is the offending code:
https://github.com/erica/xcopen/blob/7e0eeeb78f9b85b6c2b2f35dc775bfcd45ffb092/xcopen/main.swift#L31-L41
If there is no arguments then you only check for either a workspace or a project.
What do you think about this behavior instead:

If no arguments are passed

If there is a workspace, open it
Otherwise, fallback to the previous default behaviour

It there are arguments

Use the same behavior as before

It's a mix of intentional behavior and bug (playgrounds), as I was intending to open flat files and not directories as named arguments.
I think I have an approach to work with this though. Instead of ignoring directories, I'll use the other open style. I'll push another take shortly for you to try.

No arguments:
xcworkspace exists: open it. done.
otherwise, open any xcodeproj or playground.
No other xc extensions recognized
Arguments:
open any xcodeproj, xcworkspace, playground with open.
open any flat file with open -a xcode
This leaves directories/folders that cannot be normally opened with Xcode, meaning that they should either be ignored or the files inside them should be opened, and a policy has to be picked for that. What do you suggest?
Final special cases: "." and "..": how should they act?

@RobertAudi Please test new version and let me know if you disagree with the policies for arguments.

@erica The latest version works like a charm 👍🏻
As for the case of directories, I agree with you, they shouldn't be dealt with. If you try to open a directory manually with Xcode (e.g.: open -a Xcode ./tmp/) you get an error in an alert window (standard behavior). On top of my head there are two ways to approach the problem:

Run the open command and let Xcode show the error
Ignore the command and show an error/warning message on the command line

IMHO the second case is really a "nice to have" feature and it's completely fine to just ignore the command (this is the current behavior), but as far as I'm concerned the tool works really well at this point.
As an "extra nice to have" feature, you could try to apply the default behavior in the directory passed as argument but I think this is definitely out of the scope of this issue.
Anyway thanks a lot for your responsiveness and good job! 👏🏻
I'm going to replace my home-made shell function with this tool now 😁

Thanks for the feedback.


Benchmark suite

This should close #184.

I think to fix tests it could be enough to add benchmarks here: https://github.com/scrapinghub/splash/blob/master/conftest.py

@kmike is there anything else that prevents merging this?

I can't get it work :)

splash.benchmark and splash.tests imports are undefined when you execute code from benchmarks folder because these packages are not distributed with Splash.

if splash.benchmark and splash.tests are added to packages in setup.py download_sites.py raises an error while trying to start proxy server (Splash starts fine with python -m splash.server):

[-] Starting factory <splash.proxy_server.SplashProxyServerFactory instance at 0x114109710>
Traceback (most recent call last):
  File "/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/local/Cellar/python/2.7.5/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/Users/kmike/envs/splash/lib/python2.7/site-packages/splash-1.4-py2.7.egg/splash/tests/mockserver.py", line 725, in <module>
    run(opts.http_port, opts.https_port, opts.proxy_port, not opts.quiet)
  File "/Users/kmike/envs/splash/lib/python2.7/site-packages/splash-1.4-py2.7.egg/splash/tests/mockserver.py", line 698, in run
    sslport = reactor.listenSSL(sslport_num, factory, ssl_factory())
  File "/Users/kmike/envs/splash/lib/python2.7/site-packages/splash-1.4-py2.7.egg/splash/tests/mockserver.py", line 673, in ssl_factory
    return ssl.DefaultOpenSSLContextFactory(pem, pem)
  File "/Users/kmike/envs/splash/lib/python2.7/site-packages/twisted/internet/ssl.py", line 104, in __init__
    self.cacheContext()
  File "/Users/kmike/envs/splash/lib/python2.7/site-packages/twisted/internet/ssl.py", line 113, in cacheContext
    ctx.use_certificate_file(self.certificateFileName)
OpenSSL.SSL.Error: [('system library', 'fopen', 'No such file or directory'), ('BIO routines', 'FILE_CTRL', 'system lib'), ('SSL routines', 'SSL_CTX_use_certificate_file', 'system lib')]

I'm not sure how I did it, but download_sites.py was working before I installed Splash, BUT it put nothing to splash/benchmark/sites/localhost_8806/ folder, so benchmark found zero websites.

I think we shouldn't distribute splash.benchmark with other Splash code (it shouldn't be installed by installing Splash). What does it take to move benchmarks folder to the root?

it shouldn't be installed by installing Splash

if not, I'm not sure about organizing the code. The necessary subset of SplashServer functionality can probably be copy-pasted. But for the rest, there are three separate runnable scripts there: the downloader, the file server & the benchmark runner. they all use code from the file server module, so at least that module must be importable.

it worked ok for me in pip install -e . mode.


added check_session_iframe option to discovery response

https://openid.net/specs/openid-connect-session-1_0.html#OPiframe
I had to get the uri from raw response before.

thanks!
v1.1.3 has it.


backport: Merge bitcoin#23157, 24041, 20591, 22677

backporting bitcoin

Hi @UdjinM6 , This is stuck at ci/gitlab/gitlab.com Expected — Waiting for status to be reported

Hi @UdjinM6 , This is stuck at ci/gitlab/gitlab.com Expected — Waiting for status to be reported

Yes, this happens... try rebasing and force-pushing


Feature/test coverage

Adds tests for next-text-node.js
Warning
I used ember-cli-code-coverage to find some files that didn't have tests. I
left it in since it doesn't get in the way, but let me know if I should remove
it.

please do remove the log files from your request (preferably also from the history, or we can squash on merge)

done!


Adding background color to dot

Fix: #59
Added the option to insert a widget as an indicator

In the pr I have also updated the example project and linted it, so you can a lot of files in the example folder got changed.
Do you prefer that I will open a clean pr with only the change to the regular project?, I thought it is a good opportunity to combine the pr as I didn't have a lot of free time to work on it.


Some Questions about weird behavior(s)

I got this kind of weird rainbow line on the stair-like lines, and is there any way to handle this?

source

5.12x upscaled

GIF upscaling got really weird behavior (some frame could not handle transparency, and some frame lost lot's of pixels):

2-1 -> some frame could not handle transparency

source

5.12 upscaled

2-2-> some frame lost lot's of pixels

source

5.12x upscaled

a) This is an artifact of the waifu2x algorithm, nothing I can do about it.
b) I have updated it to replace transparency with transparentColor, so if you set it to #000000 for example then black will be the transparent color, avoiding that problem.
Overall I have found that the GIFEncoder does a poor job when encoding transparent gifs, I will see if I can find a better gif encoder.
c) This is caused by setting cumulative to false in the gif options (or not specifying it). Some gifs only store partial frame data per frame, so setting cumulative to true fixes this issue by layering it with previous frames. I have made it true by default in the latest version.
I recommend converting your transparent gifs to animated webp because the webp encoder is much better. The function is waifu2x.upscaleAnimatedWebp(), with same parameters as upscaleGIF() function.

Gotcha. I'll try it and give you result after testing it.
Thanks for your service :)

@Tenpi Alright. I've tried lots of ways but the best thing was converting gif to webp and upscaling. IT DO WORKS LIKE CHARM :D and it actually solved all the other problems. Thanks!


CodeMirror fails to recognize Markdown headers if they lack a space after the final '#'

CodeMirror fails to add the class cm-header to headers that lack a space between the final '#' and the title. For example:
# H1 ... has class cm-header
## H2 ... has class cm-header

#H1  ... does not have class cm-header
##H2  ... does not have class cm-header

Whether or not there technically should be a space, nearly all Markdown parsers will process #H1 without a space identically to # H1 with a space. This leads to inconsistencies when formatting is applied to the headers while editing using the cm-header class and when previews are generated using other parsers.
This issue can be tested at http://codemirror.net/mode/markdown/

Indeed:
http://johnmacfarlane.net/babelmark2/?normalize=1&text=%23foo

%23%23+bar
But it's notable that one of the few exceptions is CommonMark (the spec
says "The opening sequence of # characters cannot be followed directly by a
non-space character.")
Perhaps it's better to make it an option?
2015-06-23 8:18 GMT+03:00 Wes Cossick<EMAIL_ADDRESS>
CodeMirror fails to add the class cm-header to headers that lack a space
between the final '#' and the title. For example:
H1 ... has class cm-header
H2 ... has class cm-header
#H1  ... does not have class cm-header
##H2  ... does not have class cm-header
Whether or not there technically should be a space, nearly all Markdown
parsers will process #H1 without a space identically to # H1 with a
space. This leads to inconsistencies when formatting is applied to the
headers while editing using the cm-header class and when previews are
generated using other parsers.
—
Reply to this email directly or view it on GitHub
https://github.com/codemirror/CodeMirror/issues/3343.

Making it an option would help, certainly. I still believe the default should be that it can be followed by a non-space character, since this appears to be the most common implementation across parsers (as seen in the link above).

I'm leaning towards targeting CommonMark by default, since having a spec to compare what we are doing against (rather than a vague consensus of parsers) provides a much more firm ground. I'd be open to an option that enables parsing such headers, though.


Rspec and slim not found

Running via Spring preloader in process 4480
      invoke  active_record
      create    db/migrate/20180314125001_create_quota_assignments.rb
      create    app/models/quota_assignment.rb
       error    rspec [not found]
      insert    app/models/company.rb
      invoke  scaffold_controller
      create    app/controllers/quota_assignments_controller.rb
       error    slim [not found]
       error    rspec [not found]

Any ideas on this? rspec and slim are being used just fine in the normal scaffold generators.

I'm getting error    rspec [not found] as well.
Rails 5.2.0
rspec-rails 3.7.2
nested_scaffold 1.0.0

+1


Re-work FIFO code

Fixes #2529
I took the best features of the existing fifo implementations and merged them. The result is faster than both and has no awkward edge cases.
The only significant other change is I've allowed an item destructor to be specified when the fifo is created. This allows the fifo to be cleared or deleted without the code having to explicitly empty it first.
At the moment fifos are used for :-

sending data between the xrdp encoder thread and the main xrdp thread
Queueing incoming audio data

I've tested both of these, and also added a fifo test module to the test suite.

This looks good to me, nice work.

Thanks for that. I've updated the coding style on the wiki to correspond.


Passing variable length sentences to Tensorflow LSTM

I have a tensorflow LSTM model for predicting the sentiment. I build the model with the maximum sequence length 150. (Maximum number of words) While making predictions, i have written the code as below:
batchSize = 32
maxSeqLength = 150

def getSentenceMatrix(sentence):
    arr = np.zeros([batchSize, maxSeqLength])
    sentenceMatrix = np.zeros([batchSize,maxSeqLength], dtype='int32')
    cleanedSentence = cleanSentences(sentence)
    cleanedSentence = ' '.join(cleanedSentence.split()[:150])
    split = cleanedSentence.split()
    for indexCounter,word in enumerate(split):
        try:
            sentenceMatrix[0,indexCounter] = wordsList.index(word)
        except ValueError:
            sentenceMatrix[0,indexCounter] = 399999 #Vector for unkown words
    return sentenceMatrix

input_text = "example data"
inputMatrix = getSentenceMatrix(input_text)\

In the code i'm truncating my input text to 150 words and ignoring remaining data.Due to this my predictions are wrong.
cleanedSentence = ' '.join(cleanedSentence.split()[:150])

I know that if we have lesser length than sequence length we can pad with zero's. What we need to do if we have more length.
Can anyone suggest me the best way to do this. Thanks in advance.

Please take a look at similar questions answered on SO.
This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!

I know it's not a bug or feature request, but i couldn't found anywhere how to solve this problem, So i posted in stack overflow also,but i didn't get any response.


Cleaning up Ops Boxes and Losses :broom:

Fixes #5976
Work in Progress. Opened PR to see if I keep passing tests :)

@oke-aditya Shall we convert to draft and ping us when you are happy to review again?

Yep. :)

Not sure if I simplified the IoU tests but at least I reduced the code complexity from previous tests. I basically did not want to override a class that handles both the box_area and the IoUs. So I wrote separate test for box_area and then used a class to simplify IoU tests. i feel this keeps code bit readable and clear.
Still need to get rid of _generate().
One way is to use pytest.fixture or other is to use a few global variables.

@datumbox @NicolasHug  as discussed with phillip. I will split this PR into 2 Parts. The first part will cleanup the code. The second part will cleanup the tests :smiley: This will make merging easier.


What annotation tool are you using?

Anyone can share the annotation tool of  YouTube-VIS dataset

Anyone can share the annotation tool of YouTube-VIS dataset

Hi, now do you know the tools? I also wonder so I can how to create my own dataset

labelimg? Have you done it?


Feature/resize buffer bar scroll

created tabs.webkit-scrollbar class
reduced scrollbar height to 3px
add overflow overlay to tab bar on hover so scroll bar only appears on hover

I'm not sure whether you'd prefer for the scroll bar to always be there but smaller and overlaid or only appear on scroll, at present it only appears on scroll, but can tweak this if you'd prefer the alternative
I removed the overflow styling that was coming from the tabs.tsx component as it was overwriting what was set in the less so I've returned the wrap styles or an empty object as I didn't want to pass null or a boolean to the style prop for fear of some unexpected result.

Cool, looks good @Akin909 !

I removed the overflow styling that was coming from the tabs.tsx component as it was overwriting what was set in the less so I've returned the wrap styles or an empty object as I didn't want to pass null or a boolean to the style prop for fear of some unexpected result.

Makes sense, I tried it out and seems like it works well. I was worried we might still get a scrollbar showing when we wrap, but doesn't seem to be the case.

Seems like there is some flakiness with the autocompletion test (the travis CI failure), it does not appear to be related to your change. Need to investigate what's happening there. I'll bring this in, though - thanks for the contribution!


Fix kubeconfig YAML serialization in etcd

After switching to search and replace for the kubeconfig field in the respective kube-controller-manager and kube-scheduler ConfigMaps, we shouldn't serialize the edited kubeconfig field to YAML, as it includes an additional | character. The latter doesn't lead to an error, but it does lead to additional rollout triggers for these components.
Example kubeconfig field with the additional |:
"data": {
        "kubeconfig": "|\n  apiVersion: v1\n  clusters:\n    - cluster:\n        certificate-authority: /etc/kubernetes/static-pod-resources/configmaps/serviceaccount-ca/ca-bundle.crt\n        server: https://api-int.another-name.another.domain:6443\n      name: lb-int\n  contexts:\n    - context:\n        cluster: lb-int\n        user: kube-scheduler\n      name: kube-scheduler\n  current-context: kube-scheduler\n  kind: Config\n  preferences: {}\n  users:\n    - name: kube-scheduler\n      user:\n        client-certificate: /etc/kubernetes/static-pod-certs/secrets/kube-scheduler-client-cert-key/tls.crt\n        client-key: /etc/kubernetes/static-pod-certs/secrets/kube-scheduler-client-cert-key/tls.key\n"
    }

Lol oops

/test ?

/test baremetalds-sno-recert-cluster-rename
/test e2e-aws-ovn-single-node-recert-serial
/test e2e-aws-ovn-single-node-recert-parallel

/test e2e-aws-ovn-single-node-recert-serial


Setup appears to only accept one database credential.

Question or Issue?  When reviewing the setup instructions, the WebAPI section of config seems to only call for one user/password combo, but I believe that there is a separate set of credentials for an 'administrative rights' account that can create the tables for the application during startup.
Should there be a setting for the flyway user account?

There is an "Advanced Config" (blue) button that will expand the config for flyway. By default, the flyway datasource uses the primary credentials.

Thank you. That clears it up.


Github actions using deprecated set-output commands

Expected Behavior
Workflows should complete without warnings.
See https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/.
Actual Behavior
The workflow shows warnings.
Steps to Reproduce
Actions using old commands gives a warning like https://github.com/backstage/backstage/actions/runs/3228335759.

Closing this as we've replaced all of our own usages of set-output in #14784. There are still some warnings from external actions, but will leave those version bumps to renovate.


 Help this world and delete this repository. Thanks.

works for me bro


Renamed GApple bug

Players on my server started duping golden apples and enchanted golden apples.
It only happens with gapples with custom display name without lore, and it works like shown in the video: http://download.serb-craft.com/applebug.mp4
Can you please fix this?

Hmmm...
That is beyond weird.
Time to go sift through our code :P

Hmmm, I'm not able to duplicate it.

Yeah, I followed your exact steps.
Do you have any custom food plugins or plugins that do anything with the offhand slot? I find it very odd that the duped gapple is being put into your offhand slot.
Also our code does nothing with named items. I see no reason why it would mess it up to be renamed.

I am 100% sure that it is coming from OCM because when I remove it dupe isn't happening.
I don't have any custom food plugins or anything related to gapples. This is my OCM config: http://pastebin.com/EC7Pjv6J

I actually WAS able to reproduce the bug after sending that message. I didn't say that immediately though because my computer failed (for some reason all my memory was suddenly used??).
Aha! After further testing it's the enchanted-golden-apple-crafting option. Now that I have a starting point I'll go and check it out.

This is extremely confusing. The onItemConsume doesn't even reference enchanted-golden-apple-crafting, yet the bug is happening in onItemConsume.
I'm going to talk to the other guy that works on this plugin with me and see if I can't get some insight into this. A fresh set of eyes might help.

Okay, thank you, if you need any more info or testing you can contact me

@baticag I believe I have managed to fix this, could you try out this test version and tell us if you still get the bug?

Yes it's fixed in that version thanks!

I will be releasing this fix as version 1.0.2


[WFLY-13124][WFLY-13089] Upgrade RESTEasy to 3.11.0.Final

https://issues.redhat.com/browse/WFLY-13124
https://issues.redhat.com/browse/WFLY-13089
master PR: https://github.com/wildfly/wildfly/pull/13010

You might want to prefix the summary with [19.x] or something to differentiate from the master one.


Override Mekanism tagged blocks forge:relocation_not_supported

Is it possible to override the tagged mekanism blocks of forge:relocation_not_supported which I believe is why these blocks remain when bagging the area?
In regards to the radioactive substance issue referred to I'm not sure on the dupe issue but imo if you're playing around with the stuff then the risk is on the player.  (Radiation would still occur regardless as the machines are bagged but pressure piping, for example, remains)
    private void addBoxBlacklist() {
        addToTag(MekanismTags.Blocks.RELOCATION_NOT_SUPPORTED,
              MekanismBlocks.CARDBOARD_BOX,
              MekanismBlocks.BOUNDING_BLOCK,
              MekanismBlocks.ADVANCED_BOUNDING_BLOCK,
              MekanismBlocks.SECURITY_DESK,
              MekanismBlocks.DIGITAL_MINER,
              MekanismBlocks.SEISMIC_VIBRATOR,
              MekanismBlocks.SOLAR_NEUTRON_ACTIVATOR,
              MekanismBlocks.MODIFICATION_STATION,
              MekanismBlocks.ISOTOPIC_CENTRIFUGE,
              //Don't allow blocks that may have a radioactive substance in them to be picked up as it
              // will effectively dupe the radiation and also leak out into the atmosphere which is not
              // what people want, and means that it is likely someone miss clicked.
              MekanismBlocks.RADIOACTIVE_WASTE_BARREL,
              MekanismBlocks.PRESSURIZED_REACTION_CHAMBER,
              MekanismBlocks.BASIC_PRESSURIZED_TUBE,
              MekanismBlocks.ADVANCED_PRESSURIZED_TUBE,
              MekanismBlocks.ELITE_PRESSURIZED_TUBE,
              MekanismBlocks.ULTIMATE_PRESSURIZED_TUBE
        );

Realised they are blacklisted (tagged) on purpose.


feat: move new client script

In this PR:

Migrate new-client.py from google-cloud-java
Separate repo-level process script to library_generation/repo-level-postprocess

To verify new-client.py:

pull the branch.
pull the main branch of google-cloud-java.
copy library_generation folder to root directory of google-cloud-java.
in google-cloud-java, remove a newly added module, e.g., java-cloudquotas (PR).
regenerate the module:

python library_generation/new_client/new-client.py generate --api_shortname=cloudquotas --proto-path=google/api/cloudquotas --name-pretty="Cloud Quotas API" --product-docs="https://cloud.google.com/cloudquotas/docs/" --api-description="Cloud Quotas API provides GCP service consumers with management and
    observability for resource usage, quotas, and restrictions of the services
    they consume." --generator-version=2.31.0

use git status and git diff to verify the difference.

Note that I didn't test the script against split repositories because the main use case of this script is to generate a module in google-cloud-java.

--generator-version=2.31.0

I don't like release managers need to specify this value. Is there a way not to specify this argument?

I don't like release managers need to specify this value. Is there a way not to specify this argument?

One option is add a release-please annotation so that the version num is the same as the latest release version.
@suztomo what do you think this idea.

I don't like release managers need to specify this value. Is there a way not to specify this argument?

One option is add a release-please annotation so that the version num is the same as the latest release version.
@suztomo what do you think this idea.

Also I want to note that this is a temporary solution, we will add a new section for a new client library in the generation_config.yaml in the future. So specifying a generator version looks fine to me, and I would prefer us not to optimize too much for a temporary solution if it takes more than like 30 minutes.

I agree that Release Please is overkill for this work. Here is the shell script to get the version:
$ V=$(curl --silent 'https://raw.githubusercontent.com/googleapis/googleapis/master/WORKSPACE' |perl -nle 'print $1 if m/_gapic_generator_java_version\s+=\s+"(.+)"/')
$ echo $V
2.32.0

I agree that Release Please is overkill for this work. Here is the shell script to get the version:
# Temporary solution to get gapic-generator-java version until the configuration file is ready
$ V=$(curl --silent 'https://raw.githubusercontent.com/googleapis/googleapis/master/WORKSPACE' |perl -nle 'print $1 if m/_gapic_generator_java_version\s+=\s+\"(.+)\"/')
$ echo $V
2.32.0

Thanks for the help.

Steps to regenerate shopping CSS:

Checkout main branch of google-cloud-java and pull the latest change.
Copy library_generation to google-cloud-java's root directory.
Install python package:

Remove shopping CSS module in google-cloud-java:

rm -rf java-shopping-css

Run the generation command:

python library_generation/new_client/new-client.py generate --api_shortname="css" --proto-path="google/shopping/css" --name-pretty="CSS API" --product-docs="https://developers.google.com/comparison-shopping-services/api" --api-description="The CSS API is used to manage your CSS and control your CSS Products portfolio" --distribution-name="com.google.shopping:google-shopping-css" --destination-name=shopping-css

Verify the difference: log.
In addition, these files are removed because shopping has a types.proto that is not in the proto path (https://github.com/googleapis/sdk-platform-java/issues/2018):

deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/Channel.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/ChannelOrBuilder.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/CustomAttribute.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/CustomAttributeOrBuilder.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/Destination.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/DestinationOrBuilder.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/Price.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/PriceOrBuilder.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/ReportingContext.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/ReportingContextOrBuilder.java
deleted:    java-shopping-css/proto-google-shopping-css-v1/src/main/java/com/google/shopping/type/TypesProto.java

Verify the difference: log.

That looks good to me. Thank you.


Duplicate prompts in overall_consistency.txt and full.json

Thank you for the great work!
I noticed that there is a duplicate prompt "A fantasy landscape" in the prompts/prompts_per_dimension/overall_consistency.txt file on line 31 and line 52. A similar issue appears in the full.json file as well.
Additionally, we found only 92*5=460 videos in the provided Sampled Videos of the overall_consistency dimension, which seems to align with the duplicated prompt.
Although the differences in the results are minimal, VBench is a widely followed benchmark, and it would be great if this issue could be addressed soon.
Thanks again for your excellent work!

@ziqihuangg

You are correct that there are two similar prompts in the prompts/prompts_per_dimension/overall_consistency.txt file, differing only in upper/lower case. Due to our current video naming protocol, the later prompt’s video overwrites the earlier one during sampling. This process is consistently applied across all models under evaluation to ensure fair comparison. Thus, while it doesn’t affect fairness, it does result in extra time spent sampling one additional prompt out of the 900+ prompts. We opted not to alter the prompt list to ensure that all results remain fully reproducible. Hope this clarifies, thanks!

I got it, thank you for the quick response!


A fiber to execute ':heder_converters'  has been changed since v3.2.6

I run into an unexpected behavior when I use fiber local variable in heder_converters block.
To reproduce following:
~/csv (tags/v3.2.6)
git checkout v3.2.5
HEAD is now at 502197b Add 3.2.5 entry
~/csv (tags/v3.2.5)
bundle exec ruby -r csv -e 'p CSV::VERSION; main_fiber = Fiber.current; Thread.current[:a]="a"; CSV.new("id,name,age\n1,2,3\n", headers: true, header_converters: ->(h) { p [Fiber.current == main_fiber, Thread.current[:a]] }).to_a;'
"3.2.5"
[true, "a"]
[true, "a"]
[true, "a"]
~/csv (tags/v3.2.5)
git checkout v3.2.6
Previous HEAD position was 502197b Add 3.2.5 entry
HEAD is now at 816b48b Add 3.2.6 entry
~/csv (tags/v3.2.6)
bundle exec ruby -r csv -e 'p CSV::VERSION; main_fiber = Fiber.current; Thread.current[:a]="a"; CSV.new("id,name,age\n1,2,3\n", headers: true, header_converters: ->(h) { p [Fiber.current == main_fiber, Thread.current[:a]] }).to_a;'
"3.2.6"
[false, nil]
[false, nil]
[false, nil]

I suppose it may not a bug. If so, feel free to close it.
Thanks.

I think that acc05116c55579b78925dd27024969b9daf69135 is related.
It seems that Enumerator#each uses the same fiber but Enumerator#next uses a different fiber.