Video thumbnail used as post thumbnail looks bad (blue overlay with play button)

I've just sent a note to @heiditravels that she unnecessarily includes picture with video preview on top of a post in addition to embedded video because nowadays both steemit and busy are smart enough to make a post thumbnail using video thumbnail.
The problem is that when she does that, there are two almost similar pictures in a post body, one next to another.
Then I noticed that while it is redundant in a post body, it looks way better on a preview page.
Expected behavior
Thumbnails of posts with youtube videos should look similar to regular thumbnails of photos, i.e. without blue overlay.
Actual behavior
When user adds link to video, it is with a blue overlay and a play button on a thumbnail view, thus previews looks really bad.
How to reproduce
This looks good:
https://busy.org/@heiditravels

This looks bad:
https://busy.org/@gtg

I get that unlike Steemit, busy can play those videos straight from a preview (which is cool feature by the way) however, users have to chose whether they want good looking preview image or instant-play feature (Heidi's videos can't be played from preview because she uses thumbnails instead. Either than or playable, but ugly looking preview)
So maybe no blue overlay and much much more subtle play button?

Thanks for reporting this.
Turns out we can use different thumbnail URL to get preview in 16:9 format.
We need to update embedjs for this.
https://img.youtube.com/vi/VIDEO_ID/mqdefault.jpg - this URL returns 16:9 image.

Proposed the ratio change on https://github.com/busyorg/embedjs/pull/10.
However, it still doesn't solve the "blue ugly overlay". :)


list extensions at Marketplace

There should be a way to list extensions at Marketplace with a certain sort order. Instead of a new command this might be added to search when no query is given.

Don't quite understand what I was thinking about when creating this issue. Any this will be supported in version 3.0.0.


Operation: "Thread Safety"

This PR aggregates a series of changes made to improve Operation framework thread-safety and behavior.
Problems were identified when trying to cancel GroupOperations. Further testing and examination led to some substantial thread-safety improvements that allow a series of new Stress Tests (also included) to complete without error. (Previously, they would crash, trip asserts, etc.)
Besides thread-safety issues, several other issues were identified and fixed:

FIX: GroupOperation.operations contains the initial operations twice after beginning to execute.
FIX: Extraneous KVO Notifications were being sent for NSOperation keyPaths. KVO notifications are now explicit.
FIX: GroupOperation now only finishes once its child operations have finished.
FIX: GroupOperation now handles cancelling & finishing itself, ensuring that there are not orphaned operations on a queue that never starts if the GroupOperation is cancelled before it executes.
FIX: RepeatedOperation.addNextOperation() did not check if it was cancelled before adding a new child operation. This could lead to an endless loop.
FIX: Logging-related crashes and thread-safety issues.

Numerous new tests that previously exhibited issues, Stress Tests that previously crashed, and a new Operation KVONotification testing framework are included.
(The new Stress Tests also support a batches parameter, currently set to 1.)
Additional details on larger fixes forthcoming.

FIX: GroupOperation.operations contains the initial operations twice after beginning to execute.
Cause:
GroupOperation.execute() calls GroupOperation.addOperations(operations), which then re-adds the operations back to the operations array.
Solution:
Added a private _addOperations() method to GroupOperation with an additional flag to override this behavior - used in GroupOperation.execute().
addOperations() now calls this private implementation method.
Test:
func test__group_operation__initial_operations_only_added_once_to_operations_array() in GroupOperationTests.swift

FIX: Operation.cancel(), Operation.finish() thread-safety.
Discussion:
Operation.cancel() and Operation.finish() operate on and manipulate Operation state, but are not thread-safe.
See: comments in Issue #352
Solution:
Utilize the stateLock., but ensure that the lock is not held while notifying observers or sending KVO notifications.
(See the numerous commits.)
Tests:
func test__block_operation_cancel() in StressTests.swift
func test__group_operation_cancel() in StressTests.swift

FIX: Operation.main() thread-safety.
Discussion:
A race condition is possible in Operation.main() with the following order of operations:

The Operation checks !cancelled prior to setting state = .Executing, and cancelled == false.
Another thread cancels the operation, and this call to cancel() completes in full, not calling finish() automatically because Operation.executing still == false.
Back in Operation.main(), Operation sets the state to .Executing.
Operation.main() calls execute().
The subclass implementation of execute() checks cancelled, and returns without finishing if the Operation is cancelled (which it now is).

In this order of operations, the Operation is never finished.
Solution:
Use of the stateLock.
Tests:
Randomly detectable using:
func test__block_operation_cancel() in StressTests.swift

FIX: RepeatedOperation.cancel() can result in thread-starvation and endless loop.
Cause:
RepeatedOperation.addNextOperation() does not check cancelled status.
Solution:
Add guard !cancelled check at top of RepeatedOperation.addNextOperation().
Test:
func test__repeated_operation_cancel() in StressTests.swift //(which is also effectively a stress-test for cancelling RepeatedOperations and other thread-safety issues)

FIX: Crashes exacerbated by non-strict KVO ordering (and spurious notifications?) on mandatory NSOperation keyPaths.
Discussion:
It seems like race conditions may be introduced (or exacerbated) if an NSOperation subclass does not properly send mandatory KVO notifications (for example, for isFinished) at the exact right times. A lot of stress testing shows random crashes that go away when enforcing strict ordering and required KVO compliance.
(In #175, it was discovered that overriding .isReady can result in very rare issues.)

Revision: Some of this may be due to other thread-safety issues, like with the Logger, but converging on NSOperation behavior seems appropriate nonetheless.

Solution:
Besides other change sets that enforce thread-safety,
All KVO notifications for critical NSOperation key paths (isExecuting, isFinished, isCancelled) are now sent explicitly, at the right time.
The final didChangeValueForKey(isFinished) is sent at the very end of finish() (after didFinishObservers are called).
This reduces spurious notifications for unintended key paths, which were happening any time the state changed internally.
(For example, when internal state transitions from .Initialized -> .Pending, notifications were being generated for isExecuting and isFinished.)
It converges upon the KVO notification behavior (and frequency) of NSOperation.
It also seems to reduce random crashes of the Stress Tests over many billions of runs.

This may just be due to sending isFinished only once, after the didFinishObservers are executed, but converging on the behavior of NSOperation seems reasonable regardless.

Tests:
A test suite was added to verify that KVO notifications are being sent by Operation on the NSOperation keyPaths at the right times and in an appropriate ordering.
func test__nsoperation_kvo__groupoperation_cancel_from_initialized() in `KVONotificationTests.swift`
func test__nsoperation_kvo__groupoperation_cancelled_to_completion() in `KVONotificationTests.swift`
func test__nsoperation_kvo__groupoperation_child_cancel_from_initialized() in `KVONotificationTests.swift`
func test__nsoperation_kvo__groupoperation_execute_to_completion() in `KVONotificationTests.swift`

func test__nsoperation_kvo__operation_cancel_from_initialized() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_cancelled_to_completion() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_execute_to_completion() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_execute_with_dependencies_to_completion() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_state_transition_from_initializing_to_pending() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_state_transition_to_executing() in `KVONotificationTests.swift`
func test__nsoperation_kvo__operation_state_transition_to_executing_via_queue() in `KVONotificationTests.swift`

FIX: GroupOperations can finish() before the .finishingOperation has finished.
Symptoms:
A number of race conditions and crashes (easily triggered by cancelling GroupOperations), leaked child Operations, and more.
Cause:
GroupOperation relied on the default behavior of Operation, which can call finish() immediately in response to cancelling in:

the .cancel() method

the .start() method

the .main() method

Solution:
Added support in Operation to disableAutomaticFinishing.
Available in a new initializer: init(disableAutomaticFinishing: Bool)
When disableAutomaticFinishing is set, Operation will never call .finish() itself, and the subclass is solely responsible for triggering .finish() when appropriate (for example, when handling .cancel()).

ℹ NOTES:

The default behavior of Operation remains the same.
Automatic finishing can only be disabled.
Once disabled, it cannot be re-enabled (as this would make little sense and introduces problems).
Example: A subclass of GroupOperation, which disables Operation's automatic finishing, cannot re-enable it.

GroupOperation now calls super.init(disableAutomaticFinishing: true).
This makes the state behavior of GroupOperation in response to cancelling much easier to reason about, and much safer. (GroupOperation will now only .finish() when the finishingOperation finishes.)
Tests:
func test__operation_with_disableAutomaticFinishing_doesnt_finish_automatically_when_cancelled() in BasicTests.swift
func test__operation_with_disableAutomaticFinishing_cancelled_before_running_doesnt_finish_automatically_when_started() in BasicTests.swift
func test__operation_with_disableAutomaticFinishing_manual_cancel_and_finish_on_willexecute_does_not_result_in_invalid_state_transition_finished_to_executing() in BasicTests.swift

func test__group_operation__does_not_finish_before_child_operations_have_finished() in GroupOperations.swift
func test__group_operation__does_not_finish_before_child_groupoperations_are_finished() in GroupOperations.swift
func test__group_operation_does_not_finish_before_child_produced_operations_are_finished() in GroupOperations.swift
func test__group_operation__execute_is_called_when_cancelled_before_running() in GroupOperationTests.swift
func test__group_operation_cancellation__queue_is_empty_when_finished() in GroupOperationTests.swift

func test__group_operation__does_not_finish_before_child_operations_are_finished() in StressTests.swift

FIX: GroupOperation.addOperations thread safety().
Cause:
If GroupOperation.addOperations() is called while the operation is being cancelled, it is possible for an operation to be added that does not reflect the Group state (i.e. that is not cancelled, and will never be cancelled).
Solution:
Thread-safety changes toGroupOperation._addOperations().
Additionally, a check is done for .cancelled status and the new child operations are cancelled if the GroupOperation is already cancelled (but not yet finished).
Tests:
func test__group_operation_cancel_and_add_operation() in StressTests.swift

FIX: Operation.log (and class _Logger, etc) is not thread-safe.
Symptoms:
Crashes in objc_release, etc. With Zombies and Address Sanitizer enabled, the following is produced:
*** -[CFString release]: message sent to deallocated instance 0x604006632910

Running memory history shows (abbreviated):
Memory allocated at:
    frame #0: <...> libclang_rt.asan_osx_dynamic.dylib`__sanitizer_mz_malloc + 173
    frame #1: <...> libsystem_malloc.dylib`malloc_zone_malloc + 70
    frame #2: <...> CoreFoundation`_CFRuntimeCreateInstance + 300
    frame #3: <...> CoreFoundation`__CFStringCreateImmutableFunnel3 + 2671
    frame #4: <...> CoreFoundation`CFStringCreateWithBytes + 58
    frame #5: <...> Foundation`-[NSPlaceholderString initWithBytes:length:encoding:] + 124
    frame #6: <...> Foundation`+[NSString stringWithUTF8String:] + 135
    **frame #7: <...> Foundation`-[__NSOperationInternal _name] + 41
    frame #8: <...> Operations`NSOperation.operationName.getter(self=<unavailable>) + 44 at Logging.swift:302
    frame #9: <...> Operations`@objc NSOperation.operationName.getter + 33 at Logging.swift:0
    frame #10: <...> Operations`Operation.log.getter(self=<unavailable>) + 109 at Operation.swift:193**
    frame #11: <...> Operations`Operation.(self=<unavailable>, newState=<unavailable>).setter).(closure #1) + 1102 at Operation.swift:414
...

Cause:
Operation.log(), the _Logger class and LogManager class are not thread-safe.
Discussion:
Two immediate problems are:

_Logger.operationName is not thread-safe.

_Logger.operationName is set on the _Logger object every time that Operation.log is accessed.
A crash can be triggered in many cases - for example, with a stress test of Operations with MutualExclusionConditions (because the ExclusivityManager dispatches, in a separate thread, ExclusivityManager._removeOperation(), which calls operation.log.verbose("<<< \(category)”)).
This is the cause behind real-world intermittent crashes in built-in Operations that use Mutual Exclusivity, like ReverseGeocodeOperation.
Additionally, even if a crash doesn’t result, it has the potential to return the “wrong” data for operationName, depending on timing (and when/if the Operation’s name is changed).
The issue with Operation._log being a lazy var is also substantial. From the Swift book:

If a property marked with the lazy modifier is accessed by multiple threads simultaneously and the property has not yet been initialized, there is no guarantee that the property will be initialized only once.

Simple Repro Case for lazy var-related Crash:
func test__operations_log_trample() {
    let expectation = expectationWithDescription("Test: \(#function)")

    dispatch_async(Queue.Initiated.queue) {
        let group = dispatch_group_create()
        for i in 0..<1000000 {
            let operation = Operation()
            operation.name = "Test Operation \(i)"
            dispatch_group_async(group, dispatch_get_global_queue(0, 0), {
                operation.log.verbose("Test")
            })
            dispatch_group_async(group, dispatch_get_global_queue(0, 0), {
                operation.log.verbose("Test")
            })
        }
        dispatch_group_wait(group,DISPATCH_TIME_FOREVER)
        expectation.fulfill()
    }

    waitForExpectationsWithTimeout(60, handler: nil)
}

Initial Solution:

Operation._log must not be a lazy var.
Operation.log must be thread-safe.

Initial fix involves capturing a copy of the logging context (settings + operationName) at the time of access of Operation.log, returning that captured context as a LoggerType, and surrounding access of .log with a Read/Write lock.

LogManager properties must be thread-safe.

@swiftlyfalling - wow, just wow.
I'm reading through it all today. Looks fantastic - really happy to see many improvements here, and the stress tests to validate the fixes. Truly fantastic work - stuff like this is why I love working on open source projects!
Will squash & merge later today I expect, and then will cherry pick into the release branch - I think it makes sense to put all these improvements into v3

@swiftlyfalling - I've gone through everything, pretty much. Just a last few comments in the GroupOperation for you to give your thoughts on, then we're good to merge. 🚀
Didn't have much to comment on all the tests. Generally look really good - happy to see that you've followed and extended the testing harness that is already in place 👍.
Once this lands, I will update CI to run the stress tests on iOS too to see how it performs.

Looks great @swiftlyfalling! Just waiting for CI. Is there anything else?

That should be it for this PR. 😄

Alright - thanks @swiftlyfalling for all this work - gonna squash & merge it now to develop. Will cherry pick  it into the v3 RC too.


Update error?

Hi Dani,
While attempting to update to the latest version, my practice has been to perform cargo clean, then cargo build  --release,  in the following folders -
/galileo-osnma
/galileo-osnma/galmon-osnma
/galileo-osnma/osnma-longan-nano
/galileo-osnma/osnma-longan-nano-client
all goes well except in the /galileo-osnma/osnma-longan-nano folder where I get an error near the end of the build.
Compiling riscv-rt-macros v0.2.1
error: instruction requires the following: 'M' (Integer Multiplication and Division) or 'Zmmul' (Integer Multiplication)
mul t0, t2, t0
^
error: instruction requires the following: 'M' (Integer Multiplication and Division) or 'Zmmul' (Integer Multiplication)
mul t0, t2, t0
^
error: instruction requires the following: 'M' (Integer Multiplication and Division) or 'Zmmul' (Integer Multiplication)
mul t0, t2, t0
^
Finished release [optimized] target(s) in 13.01s
Despite this, I am able to build the firmware using the command from with the /galileo-osnma/osnma-longan-nano folder
~/riscv-binutils-gdb/binutils/objcopy -O binary target/riscv32imac-unknown-none-elf/release/osnma-longan-nano firmware.bin
Any suggestions as to why this may be happening?
Thanks,
Bob

I'm also getting that error, even in CI. It seems that it is a problem with riscv-rt, a dependency. The problem seems harmless though. The firmware image builds and works just fine. I will try to replicate this problem in a minimal case and report upstream.

Thanks Dani.  In the meantime, I'll flash the update.

Hi Dani,
Realized that I had to update the public key.  Done.
There is also a file in the /galileo-osnma/osnma-longan-nano folder called merkle_tree_root.txt.  Is this where the new string copied from the Merkl_tree XML file is to be placed or should the entire line 40256<x_ji>...</x_ji> be placed somewhere else?
I am now seeing a different error when doing a cargo clean then cargo build from the  /galileo-osnma/osnma-longan-nano folder.  This occurs near the end of the build process.  Is Rust looking for a file that's missing perhaps?  Thanks.  Bob
Compiling log v0.4.20
error: failed to run custom build command for osnma-longan-nano v0.1.0 (/home/bob/galileo-osnma/osnma-longan-nano)
Caused by:
process didn't exit successfully: /home/bob/galileo-osnma/osnma-longan-nano/target/release/build/osnma-longan-nano-701dfc9cb301faee/build-script-build (exit status: 101)
--- stdout
cargo:rustc-link-search=/home/bob/galileo-osnma/osnma-longan-nano/target/riscv32imac-unknown-none-elf/release/build/osnma-longan-nano-ff52b1e4d79b3421/out
cargo:rerun-if-changed=memory-cb.x
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', build.rs:53:74
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
bob@bob:~/galileo-osnma/osnma-longan-nano$

Thank you Dani!  Now working.  :-)

Closing, since this is working now.


Alpine edge image build failure

Image and version of the image where the issue happens
Alpine Edge
Describe the bug
See: https://github.com/toolbx-images/images/actions/runs/11883651456/job/33110735792
ERROR: net-tools-doc-2.10-r3: trying to overwrite usr/share/man/man1/hostname.1.gz owned by uutils-coreutils-doc-0.0.28-r2.

Reproduction steps
See CI above
Host distribution and version, toolbx and podman versions
N/A

Usually with a rolling release it works itself out by just waiting, I'll chase this one down though! I PRed removing the EOL alpine images: https://github.com/toolbx-images/images/pull/138 which should catch us up. Thanks!

✅ Successfully pushed "alpine-toolbox:edge" to "quay.io/toolbx-images/alpine-toolbox:edge"

Rebuild did the trick!

Thanks!


Restore compatibility with database_cleaner < 1.8.0.beta

Summary

DatabaseCleaner::VERSION didn't exist until 1.8.0.beta, so having an older version causes an uninitialized constant error instead of using the old behavior.
Details

When upgrading the cucumber-rails 2.1, my @javascript scenarios failed with uninitialized constant DatabaseCleaner::VERSION (NameError) errors. cucumber-rails has conditional logic checking if DatabaseCleaner::VERSION is greater than or equal to 1.8.0.beta, but DatabaseCleaner::VERSION didn't exist until 1.8.0.beta.
Motivation and Context

The code change that added support for newer versions of Database Cleaner was written with the intention of maintaining support for older versions of Database Cleaner, but it failed in practice. This change restores compatibility with older versions.
How Has This Been Tested?

I tested with my app still using Database Cleaner 1.7.0. It failed when using the release version of cucumber-rails 2.1, but succeeded using the versions of cucumber-rails in this pull request.
I did not add an automated test because, outside of Rails itself, the project doesn't seem to take on the overhead of testing with older versions of libraries and an automated test for backwards compatibility wasn't added with the original change. If I'm wrong in that assessment, I'm happy to add an automated test however the project would like.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist:

[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Hi @cgriego,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber


[Migration] Upgrading H2 DB Version

The H2 engine version is upgraded from 1.4.199 to 2.1.210 in the product IS. With this change, it will not be possible to interact with existing H2 databases which were created from the older H2 version.
Even though it is not recommended to use H2 databases in the production environment, if a customer who wish to migrate from 5.11.0 to 5.12.0 is using the H2 DBs, they will have to migrate these databases to the new version. A H2 migration tool created for this migration is available at https://github.com/wso2/samples-is/tree/master/h2-migration-tool.
It is required to provide the necessary instructions to use this migration tool if necessary, in the migration docs for 5.12.0.
With this upgrade, the H2 console will be removed from the product IS, and it is required to mention the removal of the H2 console and the need for H2 DB migration in the 5.12 migration docs. The removal of the H2 console should be mentioned in the What has Changed page.
Related to: https://github.com/wso2/product-is/issues/13162

Added to docs with https://github.com/wso2/docs-is/pull/2991, https://github.com/wso2/docs-is/pull/2997


[e2e] Support skipping deploying Antrea

When developing something, it should be common that Antrea is already deployed and we just want to validate it with e2e tests. For example, I usually deploy Antrea using helm which is easier to set the configurations. But running e2e always deployed Antrea and required the manifest yaml to be present in the home directory of control plane node, which adds some burden to running e2e tests.
This commit adds a flag "--deploy-antrea" to support skipping deploying Antrea. It defaults to true to keep the same behavior as before. When we just want to run e2e tests and not to redeploy Antrea. We can set "--deploy-antrea=false".

/skip-all


Issue/200 deployment improvements

Includes deployment improvements and UI tweaks as well.

@nickplace made some modifications to the PR:

Detect "No Web3 Support" when the user hits the "Deploy" button.
Instead of having "We found a saved DAO, preview?" and then having a separate preview dialog, I just combined them both into a single preview + resume/start over dialog.
Don't save or preview "empty" DAOs.
Errors weren't displaying properly in the migration log.


[Feature Request] Turn el-select into tags input if it doesnt have el-option

Existing Component
Yes
Component Name
el-select
Description
Hello ElemeFE Team,
Thank you for make this awesome ElementUI.
Please consider turn el-select into tags input if it doesnt have el-option by disabling option panel (the bottom one).
https://jsfiddle.net/Lt52grqe/

This is helpful if you want to make unique tags input.
Like following picture:

Have a great weekends,
threeid

Thank @jikkai for taking this issue. 🤗

Will, here is a tricky situation with this feature. Users can not enter two equal values with el-select, so we have to create a new TagInput component. Unfortunately now we have not enough resources to handle this case.
But you can still hide option panel by CSS which is just a workaround: https://jsfiddle.net/Lt52grqe/1/


menu on open white gap

When menu is opened for the first time on page load i get a gap between the menu and warp div showing the body color in the gap.
If i close the menu and open it  again the gap will not appear until i refresh the page and open menu.
Anyway to fix this?

@stigk do you have a link to the code? Is this happening for you at http://ascott1.github.io/bigSlide.js/?
Thanks!

@ascott1 No, it is not happening for me on  http://ascott1.github.io/bigSlide.js/
Here is my Link
Thanks for the quick reply, really like this plugin.

Thanks!
I took a look at the site and I can't see what's causing it immediately. It looks like you have a .warp class that contains everything that gets pushed, but each individual element id is given 'position: relative'. Maybe try applying that to the class to make sure nothing is missed? It seems to be an odd delay between the container transitioning and the menu transitioning.
Sorry I'm not of much help! Hopefully that gets you pointed in the right direction.

Hey, thanks for getting back.
I figured it out there were few typos .warp and .wrap my own fault not noticing it, the delay was from the width some how the width i had was causing it.changed it to lower width now it is working brilliantly smooth.
Thanks.

Glad to hear it!


KeyError: b'X-Scrapoxy-Proxyname'

Current Behavior
I am getting a KeyError: b'X-Scrapoxy-Proxyname' when a proxy is blacklisted
Expected Behavior
Not getting a KeyError
Steps to Reproduce

My scrapoxy project settings

My spider settings

# Obey robots.txt rules
ROBOTSTXT_OBEY = False

CONCURRENT_REQUESTS = 16
CONCURRENT_REQUESTS_PER_DOMAIN = 16

# Disable Telnet Console (enabled by default)
TELNETCONSOLE_ENABLED = False
EXTENSIONS = {
    "scrapy.extensions.telnet.TelnetConsole": None,  # truly disable telnet console
}

# Set settings whose default value is deprecated to a future-proof value
REQUEST_FINGERPRINTER_IMPLEMENTATION = "2.7"
TWISTED_REACTOR = "twisted.internet.asyncioreactor.AsyncioSelectorReactor"
FEED_EXPORT_ENCODING = "utf-8"

DOWNLOADER_MIDDLEWARES = {
    'scrapoxy.ProxyDownloaderMiddleware': 100,
    'scrapoxy.StickySpiderMiddleware': 101,
    'scrapoxy.BlacklistDownloaderMiddleware': 102,
}
SPIDER_MIDDLEWARES = {
    "scrapoxy.ScaleSpiderMiddleware": 100,
}

SCRAPOXY_MASTER = "http://localhost:8888"
SCRAPOXY_API = "http://localhost:8890/api"

SCRAPOXY_BLACKLIST_HTTP_STATUS_CODES = [400, 429, 503]
SCRAPOXY_SLEEP_MIN = 60
SCRAPOXY_SLEEP_MAX = 180

SCRAPOXY_WAIT_FOR_SCALE = 120
RETRY_TIMES = 5
RETRY_HTTP_CODES = [500, 502, 503, 504, 522, 524, 408]

DOWNLOAD_DELAY = 0
DOWNLOAD_TIMEOUT = 40

DOWNLOAD_FAIL_ON_DATALOSS = True

Running the spider
Every time a proxy get's blacklisted this error occurs

Failure Logs
Traceback (most recent call last):
  File "/home/tomas/programming/personal/tf2trader/.venv/lib/python3.11/site-packages/twisted/internet/defer.py", line 2003, in _inlineCallbacks
    result = context.run(gen.send, result)
  File "/home/tomas/programming/personal/tf2trader/.venv/lib/python3.11/site-packages/scrapy/core/downloader/middleware.py", line 68, in process_response
    method(request=request, response=response, spider=spider)
  File "/home/tomas/programming/personal/tf2trader/.venv/lib/python3.11/site-packages/scrapoxy/blacklist.py", line 45, in process_response
    id = response.headers["x-scrapoxy-proxyname"].decode("utf-8")
  File "/home/tomas/programming/personal/tf2trader/.venv/lib/python3.11/site-packages/scrapy/http/headers.py", line 49, in __getitem__
    return super().__getitem__(key)[-1]
  File "/home/tomas/programming/personal/tf2trader/.venv/lib/python3.11/site-packages/scrapy/utils/datatypes.py", line 41, in __getitem__
    return dict.__getitem__(self, self.normkey(key))
KeyError: b'X-Scrapoxy-Proxyname'

Scrapoxy Version
python package - 2.0.2, scrapoxy - latest from docker
Custom Version

[ ] No
[ ] Yes

Deployment

[X] Docker
[ ] Docker Compose
[ ] Kubernetes
[ ] NPM
[ ] Other (Specify in Additional Information)

Operating System

[X] Linux
[ ] Windows
[ ] macOS
[ ] Other (Specify in Additional Information)

Storage

[X] File (default)
[ ] MongoDB & RabbitMQ
[ ] Other (Specify in Additional Information)

Additional Information
No response

Turns out I'm just stupid and forgot to enable MITM, sorry! 💀

Sorry for not answering quickly.
And thank for solving the issue yourself!


Error message

/bin/bash: activate: No such file or directory
/bin/bash: activate: No such file or directory
/bin/bash: Rscript: command not found
Error in job plot_dupmetrics while creating output file output/plots/dups.pdf.
RuleException:
CalledProcessError in line 65 of /home/iegut/snakemake_GMS_MT2022/session2/Snakefile:
Command 'Rscript /home/iegut/snakemake_GMS_MT2022/session2/scripts/.snakemake.invzlaef.plot.R' returned non-zero exit status 127.
File "/home/iegut/snakemake_GMS_MT2022/session2/Snakefile", line 65, in __rule_plot_dupmetrics
File "/home/iegut/miniconda3/envs/snakemake_GMS/lib/python3.6/concurrent/futures/thread.py", line 56, in run
Will exit after finishing currently running jobs.
Traceback (most recent call last):
File "/home/iegut/snakemake_GMS_MT2022/session2/scripts/.snakemake.2czmw33n.plot.py", line 12, in
import matplotlib.pyplot as plt
ModuleNotFoundError: No module named 'matplotlib'
Error in job plot_dupmetrics_python while creating output file output/plots/dups_python.pdf.
RuleException:
CalledProcessError in line 71 of /home/iegut/snakemake_GMS_MT2022/session2/Snakefile:
Command 'python /home/iegut/snakemake_GMS_MT2022/session2/scripts/.snakemake.2czmw33n.plot.py' returned non-zero exit status 1.
File "/home/iegut/snakemake_GMS_MT2022/session2/Snakefile", line 71, in __rule_plot_dupmetrics_python
File "/home/iegut/miniconda3/envs/snakemake_GMS/lib/python3.6/concurrent/futures/thread.py", line 56, in run
Will exit after finishing currently running jobs.
Exiting because a job execution failed. Look above for error message
finished with errors

Thanks Isobel. This looks like a conda environment issue, could you 1) check that your conda is updated to latest version (you can do it with mamba update -n base conda 2) post your snakemake version 3) have a look at this issue some of those solutions may be relevant - particularly, please check where python is located (which python) and whether you have multiple installations of python..?
BW
Rao

Hi, I encounted a similar issue on a recent snakemake version (8.16.0). I think that in serveral cases it has something to do with the initialization of the bash environment. It seems that my .bashrc does not get executed and hence the proper conda (a ~/miniconda3/) does not get activated and some old conda (located in /usr/bin/ which I have no influence over) gets used, which does not have an "activate" command in the associated path.


what happened? What picture is this?

import JsonView from 'react18-json-view'
import 'react18-json-view/src/style.css'

<JsonView collapseStringsAfterLength={100000}
    src={jsonData}
    collapsed={false}
    theme="default" />

The style of your project will be lost. My project is umijs4 + antd pro.

@YYsuni

The first time I used it, it was really terrible...

Hmmm... Let me see....🧐

Don't worry, could you show a demo code? Like CodeSandbox or an online website.
@YuZongYangHi

@YYsuni  I solved it with react-json-view, but I don’t know why the style is missing in your project. The expanded and collapsed icons are abnormally large.

ok, I will continue to further research.

There is a high probability that it is a problem with my json

I am running into the same problem. Have you solved this?

@felixSchl add the style imports to the top and it was gone for me

Thanks, that worked. I misread the docs as replacing the styles import for
dark styles as opposed to adding another import.
On Mon, 8 Jan 2024, 14:30 Jinwook Shin, @.***> wrote:

@felixSchl https://github.com/felixSchl add the style imports to the
top and it was gone for me
—
Reply to this email directly, view it on GitHub
https://github.com/YYsuni/react18-json-view/issues/20#issuecomment-1880274545,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUT7TUAJWGMM7Q6ULH3ZXDYNND4NAVCNFSM6AAAAAA56UZQQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBQGI3TINJUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

I am having the same problem within my Remix app. None of the fixes here helped solving it. Any other ideas?
import JsonView from 'react18-json-view'
import 'react18-json-view/src/style.css'

const jsonObject = {
  string: "string",
  number: 123456,
  boolean: false,
  null: null,
  func: "function(){}",
  Symbol: "Symbol(JSON View)",
  obj: { k1: 123, k2: "123", k3: false },
  arr: ["string", 123456, false, null],
};

export default function MqttOptions() {
  return <JsonView src={jsonObject} />;
}

I am having the same problem within my Remix app. None of the fixes here helped solving it. Any other ideas?
@freds-dev
The latest canary version may resolve the problem, please use v0.2.8-canary.6 by npm i react18-json-view@canary.


Web UI to edit the config

It would be nice if the config can be edited by the users on the web interface.
https://github.com/g2glab/hellograph/blob/master/config.js

Excellent fix c08cae9ebf7e449e595770680770c453e2940166. Thank you!


Jumping to tab programmatically not working in iOS

Current behaviour
On changing the tab index programmatically, it only changes the tab indicator but not the scene below. The scene still renders the first screen, but the tab indicator points to the current index.
Expected behaviour
The scene should be updated as well.
Screenshots (if applicable)

Your Environment
iOS

I can't seem to recreate your issue, the code in this branch works:
https://github.com/wizebin/TabViewVelocityIssue/tree/programmatic-jumping
You could try forking this repo and demonstrating your issue.

i also canot move tab programitically with using index in IOS.android work fine.

I am also seeing a weird issue with the component not respecting a programmatic tab change only on a iOS device. An iOS emulator, and android (device/emulator) work fine.
Don't know if its related. Will try to set up an example to demonstrate

Are you using the onIndexChange callback to change your index?

To repro the issue, set the index in the initialState (in the constructor) to second or third tab. The onIndexChange callback is working though.

I had this issue when the version of react-native-tab-view I was using was v1.3.2.
Upgrading it to v2.2.0 manage to fix the issue for me. (You will need to install react-native-reanimated for this update.)

Closing due to incomplete issue template


HTTPS deployment with AWS Elastic Beanstalk

Does anyone have any idea where to begin with making the parse server https secure?
The AWS documentation has been thoroughly unhelpful.

Here's a broad outline:
Requirements:

your own domain
a load balancer at AWS

Process:
http://docs.aws.amazon.com/acm/latest/userguide/gs-elb.html

Get a certificate for *.yourdomain.com via ACM, verify it
Set up a hosted zone at Route 53 for your domain
- A Record alias with target as the load balancer
- SOA
- Will give you NS records to which you point your DNS at the registrar
Enable Beanstalk Environment to use Autoscaling and ELB
Enable ELB manually to use AWS Certificate by adding a listener to its security group
- HTTP 	port 80
- HTTPS 	port 443	HTTP		port 80	SSL certificate from ACM
Get the EC2 ID, find the corresponding EC2 security group
On that security group, set inbound rules

HTTP, TCP, port 80, load balancer
HTTPS	TCP	443	<IP_ADDRESS>/0

I recommend going for biz level AWS support for this process.


Remove __enable and __disable irq calls from mbed hal common code

This is an extension of https://github.com/mbedmicro/mbed/pull/1806
Work left to be done:
hal/targets - This is partner code and should be consulted with them
rtos - We need to look here

@mbed-bot: TEST
HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

LGTM


No NBT completions for selectors w/o type

Completions for the basic entity NBTs should be provided.

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

npm package (@latest dist-tag)
GitHub release


Banner position is something wrong

Info:

OS:
Logseq ver:0.7.6
Theme ver: 1.14.2
[ ] Do i have the same on default theme?

Description:
There's a gap between banner picture and block.
To Reproduce:
...
Expected behavior:
...
Screenshots

Attach files
Add (via drag-n-drop) .zip with .md files (if it needs) to help with bugfixind

it does not default theme settings - try to disable your customizations and write results.

I tried, but still not work.

2022年7月11日 23:24，Yuriy Piskun @.***> 写道：
it does not default theme settings - try to disable your customizations and write results.
—
Reply to this email directly, view it on GitHub https://github.com/yoyurec/logseq-solarized-extended-theme/issues/27#issuecomment-1180549938, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVVWSXURKTHHEAWU5IP6TADVTQ4ERANCNFSM53HW2W5Q.
You are receiving this because you authored the thread.

can you use devTools to inspect this element with "gap"?
`Ctrl+Shift+i" -> "Elements" and target banner (or nex element after) to find marign/padding...
https://www.loom.com/share/a78d98c73c834574acd1608e9c523b6c
and record loom video

Hope it works
https://www.loom.com/share/ad7269ae59b7410695d882158d2806b2

2022年7月12日 22:35，Yuriy Piskun @.***> 写道：
can you use devTools to inspect this element with "gap"?
`Ctrl+Shift+i" -> "Elements" and target banner (or nex element after) to find marign/padding...
https://www.loom.com/share/a78d98c73c834574acd1608e9c523b6c https://www.loom.com/share/a78d98c73c834574acd1608e9c523b6c
and record loom video
—
Reply to this email directly, view it on GitHub https://github.com/yoyurec/logseq-solarized-extended-theme/issues/27#issuecomment-1181840083, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVVWSXQ6PXR52JTXXVDVVPLVTV7ENANCNFSM53HW2W5Q.
You are receiving this because you authored the thread.

Ohhhh! You should mention "on child block page" )

working on fix...

fixed in 1.14.3!


Issue with Item Stacking after installing the mod

Hello, thank you for making this awesome mod. I love everything about it but can’t help but wonder why this glitch is occurring after installing the mod on my server. Randomly some items become impossible to stack once obtained and the only way to make it work again is to throw all the similar items on the floor and make it stack on the floor and then pickup.
I started facing this issue only after installing this mod and have tested without it installed and things seem to work again.
The mods I have installed on my server are -

Lithium - 0.7.3
Fabric Tailor - 1.6.3
Fabric API - 0.38.2
Fabric Sit - 1.6.1
BFAPI - v1.1.9

Server MC version - 1.17.1
Please let me know if you need any more details to help resolve this issue!

Sorry I forgot to add that this issue occurs when you place something on the floor, break it and then pick it up. It starts stacking separately from the original stack. I have tried removing all mods and just adding this mod and this issue only persists when I use this mod.

I will have a look now, thanks for reporting this

i accidently closed this whoops

I have found the issue, the mark provider creates an nbt tag if one is not present without checking if it should. Then the item it created the tag on is different to the originals.
This will be patched next version, for now please downgrade to 1.1.8
If this issue continues please reopen this issue

Thank you so much for your prompt response. I will downgrade like you suggested and if I face the same issue I will get back to you.
Cheers! :)


Inputs are not applied

The input vector u isn't applied (Ax + Bu is missing).

Tangentially related to #10.


Compiler tries to downcast Class

class Foo
  macro foo type
    def bar
      baz({{type.id}}.class)
    end
  end

  def baz type
    case type
    when String
      "hi"
    end
  end

  foo String
end

Foo.new.bar

I'm sure I'm doing something wrong in that code, but it would be nice if Crystal pointed out what that is ;)

Hmmm... what are you trying to do? I mean, what's the code you want to do, and how would you do it without macros?
Right now it crashes because you do String.class, and going to Class will always break the compiler now because the meta-metamodel is super broken :-(

Mmh, let me try to pseudo code it:
class Foo
  macro wrapped_getter name, type
    def {{name.id}}
     pointer = LibSome.call
     to_crystal(pointer, type)
    end
  end

  def to_crystal pointer, type
    case type
    when String
      String.new pointer as UInt8**
    when Int32
     (ptr as Int32*).value
    end
  end

  wrapped_getter foo, String
  wrapped_getter bar, Int32
end

I think that should show the idea.

I see... well, that doesn't even work in Ruby:
s = String
case s
when String
  puts 1
else
  puts 2
end

The above prints 2. String is not a String :-)
Of course, that doesn't mean we have to copy Ruby. But right now class comparison doesn't work, and less as a when inside a case.
However, what you could do, is reopen String and Int32 and add class methods to them:
class String
  def self.my_to_crystal(pointer)
    String.new pointer as UInt8**
  end
end

class Int32
  def self.my_to_crystal(pointer)
    (pointer as Int32*).value
  end
end

class Foo
  macro wrapped_getter name, type
    def {{name.id}}
      pointer = LibSome.call
      {{type}}.my_to_crystal(pointer)
    end
  end

  wrapped_getter foo, String
  wrapped_getter bar, Int32
end

But... we definitely need to fix class-related functionality.

Ugh, right. Had a brainfart there I guess. Mmh, I'm not a big fan of patching core classes, but I guess that's the cleanest solution here, thanks.

Another solution is to have associated classes. So for example, MyString, MyInt32, with class methods. Then you pass My{{type.id}}. That way you don't patch core classes.

Or just a regular method: to_crystal_{{type.id}}

This doesn't crash anymore.


No data is displayed in the visualiser client plots for any of the telemetry entries

When testing a previously working commit 45035b8 on main branch, the plots usually displaying the samples received on the visualiser are not displaying anything, although the plot view is flowing forward (Local Clock selected instead of Fixed Timespan).
How to Reproduce

Add the iCubGazeboV3 to the Gazebo world,
Run the wholebodydynamics module as usual,
Run the Open-MCT Telemetry server and client as usual,
On the client browser, navigate to http:<your-machine-IP-address>:8080,
Click on any telemetry entry on the left pane, (e.g. Legacy IMU sensor measurements),
Change time Conductor clock setting from Fixed Timespan to Local Clock,
Check the plot output. Should display no data points.

Error Log
We also get a warning on the process console:
{ status: 'OK', message: 'Opem-MCT static server process started.' }
ICubTelemetry History Server listening on http://<IP_ADDRESS>:8081/history
ICubTelemetry Realtime Server listening on ws://<IP_ADDRESS>:8081/realtime
Control Console Server listening on http://<IP_ADDRESS>:3000
(node:39941) UnhandledPromiseRejectionWarning: Error: spawn yarp ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:467:16)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:39941) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:39941) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[OPEN-MCT STATIC SERVER] stderr: Debugger listening on ws://<IP_ADDRESS>:55525/e9429927-70a4-4cc3-905e-924d440169f3
For help, see: https://nodejs.org/en/docs/inspector

...related to a spawned YARP command, probably the yarp name list.

All the relevant ports required for receiving the telemetry data appear disconnected.
Even after connecting one of the ports...yarp connect /icubSim/inertial /yarpjs/inertial:i

the problem persists.
After the connection mentioned above is restored, we can break inside the respective registered "onRead" callback and verify that the callbacks icubtelemetry.processOrDropYarpData[i] are still inactive, i.e. set to the dummy value (id,data) => {}.
This means that ICubTelemetry.prototype.connectTelemSrcToNotifier(id) was never called for any of the ports.
We realise that the calling function connectPortsAndStartNotifier isn't called either.
Actually never reach the Promise "resolve" callback in
https://github.com/ami-iit/yarp-openmct/blob/45035b8cda4af25310d1f352196da692f9912e5e/iCubTelemVizServer/iCubTelemVizServer.js#L111
...

On handling errors in async functions

We can use .catch in order to handle .reject or thrown errors[^1].
Every time a an error is handled in a .catch, an eventual subsequent .then() is treated normally as if there was no error.
We should place a .catch exactly where we wish to handle the error, and rethrow errors we cannot handle.
A .catch can be placed at the end of a sequence of cascaded .then to catch any error which occurred in between, which was the approach used in
https://github.com/ami-iit/yarp-openmct/blob/f1508ad77d95f10b70abeb312ba96b0196383f1b/iCubTelemVizServer/iCubTelemVizServer.js#L111-L113
For browsers we should use unhandledrejection event handler or alert in order to inform the user.

[^1]: If an error is not handled, a UnhandledPromiseRejectionWarning warning is thrown.
References
https://javascript.info/promise-error-handling

Error Analysis
spawn yarp ENOENT ocurs when the executable or command in question (here yarp) is not found in the working folder. yarp should be found from anywhere, unless the environment of the child process was corrupted. That environment is by default inherited from the parent, but we can always do:
spawn('<command_executable>', ['command_param_1', 'command_param_2'],{
    env: {
        PATH: process.env.PATH
    }
});

Not Reproducible
The issue was occuring on Webstorm. Running once from the terminal with npm start worked without issues, after which the issue was no more reproducible from Webstorm.


Idea: Component class as a prop instead of adapters

Now (6.0.0-alpha.14): put a string component name prop in a Field  and then attach an adapter
Proposal: put a component class in component prop without having to declare adapters and relying on a string
Current usage:
<Field
    name="username"
    component="TextField"
    floatingLabelText="Username"
/>

and then:
reduxForm({
    form: 'myForm',
    adapter,
})(Component);

Proposed usage:
<Field
    name="username"
    component={TextField}
    floatingLabelText="Username"
/>

without other work. Then Field will pass all given props to the component, with redux-form ones attached as well.
Basically instead of mounting adapters, you'd just pass the wrapped component itself. In case of redux-form-material-ui, let's say you'd do the following:
import { WrappedTextField } from 'redux-form-material-ui';

const MyForm = props =>
  <form onSubmit={props.handleSubmit}>
    <Field
      name="username"
      component={WrappedTextField}
      floatingLabelText="Username"
    />
  </form>;

export default reduxForm({
  form: 'myForm',
})(MyForm);

What you are proposing here is implemented since the first release of Redux Form 6. Adapters are just a convenient way for lib author to style a hole set of components.

Ohh I understand, I read the docs wrong - my bad. it's here at component : Component | Function | String.

I think your issue would better fit to redux-form-material-ui repository.


[FR] Moving to @firebase/admin module naming

Problem:
With the main Firebase libraries moved to @firebase/xxx naming convention (e.g. @firebase/testing), firebase-admin looks a bit like an outlier.
There may be reasons for keeping it this way, but it does look a bit odd and I double checked that it's not about a bogus module pretending to come from official Firebase.
Describe the solution you'd like
Ability to have "@firebase/admin": "^8.9.10" in package.json
Describe alternatives you've considered
Currently using the firebase-admin: "^8.21.1".

@firebase/* is strictly reserved for our client (JS) SDK packages. firebase-admin is intentionally named so to look distinct from the client SDKs. Our official documentation should answer any doubts about the authenticity of the package: https://firebase.google.com/docs/admin/setup


DGLOs Constructor take a div/body, not SVG

Have DGLOs library constructor take a div/body instead of svg and then creates svgs
Currently, timesteps manually select the body, which isn't good.
DGLOsSandwich.ts line 31

added drawlocation variable to dglos. constructor accepts width and height. drawlocation is constructor created initial SVG


Merge consumers

Pull Request Test Coverage Report for Build 599585089

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 26.892%

Totals

Change from base Build 599543083:
0.0%

Covered Lines:
1649

Relevant Lines:
6132

💛  - Coveralls


Compile individual files with separate flags

Node Version: node=v6.11.4 and npm=3.10.10
Platform: GNU/Linux
Compiler: gcc version 7.2.0 (GCC)
Module: My c++ module using v8/nan/libuv

I'm trying to compile a module I'm building, and my binding.gyp file is as I show below. But I'm not getting it, I think it's building several ".node" and the only one I need it to be is "nodefastnoisesimd". So why did I create the other targets? because I need to compile individual files with flags that will be applied only to them, as you can see in the last 3 targets. How could I then compile individual files with separate flags?
Since I do not want them to be ".node" but rather that they are normal object files to be used to compile the "nodefastnoisesimd" module.
{
    "targets": [
     {
        "target_name": "nodefastnoisesimd",
        "sources": [
            "nodefastnoisesimd.cpp",
            "async_nfns.cpp",
            "FastNoiseSIMD/FastNoiseSIMD_avx512.cpp",
            "FastNoiseSIMD/FastNoiseSIMD_internal.cpp",
            "FastNoiseSIMD/FastNoiseSIMD_neon.cpp",
            "FastNoiseSIMD/FastNoiseSIMD.cpp"
        ],
        "cflags": ["-std=c++11"],
        "include_dirs": [".", "FastNoiseSIMD", "<!(node -e \"require('nan')\")"]
     }
  ],
    "targets": [
    {
        "target_name": "avx2",
        "sources": ["FastNoiseSIMD/FastNoiseSIMD_avx2.cpp"],
        "cflags": ["-std=c++11", "-march=core-avx2"],
        "include_dirs": ["FastNoiseSIMD"]
    }
  ],
    "targets": [
    {
      "target_name": "msse4.1",
      "sources": ["FastNoiseSIMD/FastNoiseSIMD_sse41.cpp"],
      "cflags": ["-std=c++11", "-msse4.1"],
      "include_dirs": ["FastNoiseSIMD"]
    }
  ],
    "targets": [
    {
      "target_name": "msse2",
      "sources": ["FastNoiseSIMD/FastNoiseSIMD_sse2.cpp"],
      "cflags": ["-std=c++11", "-msse2"],
      "include_dirs": ["FastNoiseSIMD"]
    }
  ]
}

Give the other targets a "type": "static_library" property and depend on them in your main target with "dependencies": ["avx2", "msse2", "msse4.1"], and remove their .cpp files from its sources list.

I tried this, but it just compiled the last target.
AR(target) Release/obj.target/msse2.a
  COPY Release/msse2.a

I'm getting a file error (../FastNoiseSIMD/FastNoiseSIMD_internal.cpp) or directory not found.

What prints that?  GYP or make?  Do other files #include that file?
If it helps, here is an example of a module that builds and links against a bundled static library.

All "includes" can be seen in the image above. This appears on the console when giving a "node-gyp build".

@bnoordhuis I managed to compile here, thank you for your example.
An example of what it would look like to compile with a static library:
{
    "targets": [
     {
        "target_name": "nodemodule",
        "sources": [
            "nodemodule.cpp",
            "nodemodule_functions.cpp"
        ],
        "cflags": ["-std=c++11"],
        "include_dirs": ["<!(node -e \"require('nan')\")"],
        "dependencies": ["libmylib"]
     },

     {
     "target_name": "libmylib",
     "type": "static_library",
     "cflags": ["-O3"],
     "direct_dependent_settings": {
        "include_dirs":  ["."],
     },
     "sources": ["mylibsource.c"],
     "include_dirs": ["."]
     }

  ],
}

Just one more thing, how would you compile a library using a different compiler?

That's definite "here be dragons"1 territory:
{
  'make_global_settings': [
    ['CXX.custom', '/usr/bin/clang++'],  # must be an absolute path
  ],
  'targets': [
    {
      'target_name': 'mylib',
      'type': 'static_library',
      'toolsets': ['custom'],
      'sources': [...]
    },
    # ...
  ]
}

You can leave out the make_global_settings stanza and build with env CXX.custom=clang++ node-gyp build if you like; you don't need to use an absolute path in that case.
If you use a relative path in your binding.gyp, it's relative to the build directory.  You can (ab)use that to ship a custom compiler driver, i.e., ['CXX.custom', '../cc.py'].
1 Which is a late Medieval upgrade of the Roman expression "hic sunt leones" (here be lions) since lions weren't that special anymore in 14th century cartography.  The more you know, right?

I clicked to open the topic inadvertently. Why do you think it's dangerous?

I'm not saying it's dangerous but that you're entering mostly uncharted territory.
Note that make_global_settings is a top-level element.

My English is bad, sorry. So will it change for everyone? anyway I never see change, it's always compiling with g++, no matter what I put in "make_global_settings".

No, just for your binding.gyp.  Can you post that file and the output of env V=1 node-gyp rebuild?

  Use CC.custom for those.

And notice "-O3" being called twice, and not being called into the library.

cflags applies to both C and C++ files.  You can use cflags_c and cflags_cc (and cflags_objc and cflags_objcc for respectively Objective-C and Objective-C++ files.)

The "-03" is now right. But still I can only compile with g ++, even changing to "CC":
"make_global_settings": [
     ["CC.custom", "/usr/bin/gcc"],
],


MINOR: Remove flaky assertion in verifyCloseOldestConnectionWithStagedReceives

This seems to fail a lot in Jenkins although it always passes locally
for me. Removing the assertion to restore Jenkins stability while
we investigate in more detail.

I added the assertion above before merging 28c83d966 as Jun had suggested that in the PR review. cc @rajinisivaram

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6140/
Test FAILed (JDK 7 and Scala 2.11).

The tests actually passed for JDK 7, the failure was during the collection of findBugs analysis files:
java.io.FileNotFoundException: /x1/jenkins/tools/tomcat/apache-tomcat-9.0.0.M20/webapps/ROOT/WEB-INF/lib/libpam4j-1.8.jar (Too many open files)

Same thing happened with the JDK 8 build (tests passed, but too many files error after that step), so merging to trunk and 0.11.0 branches.


pod not updated for swift 3.0

pod 'Simplicity' gives me version 1.0.2 still

Cocoapods doesn't automatically update its cache anymore, so try running pod update first =]

Thanks for the help.

No problem!


mutt: New Package (Version 1.5.24)

Created a new Package for mutt
The PKGBUILD is mostly the same as the one from ArchLinux (https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/mutt)
The most important difference is the --with-mailpath=/var/spool/mail
The configure Script searches if a valid mail path exists. It looks for the following four directories:

/var/mail
/var/spool/mail
/usr/spool/mail
/usr/mail
The first existing directory will be used. If none of these directories exist you need to specify one with the --with-mailpath option.
I choose /var/spool/mail because it made the most sense to me.

Using 2 spaces instead of tabs

Fix trailing slash in line 35


Add a status indication to our documentation

Add status indication to our documentation. This helps readers understand if it is a work in progress, ready, out of date etc.

Won't fix


Inlay hints not working

Hi, I'm seeing problems with inlay hints since updating Rust and rust-analyzer. Every time I open a Rust file, I get this error:
Error executing vim.schedule lua callback: ...im/bundle/rust-tools.nvim/lua/rust-tools/inlay_hints.lua:199: attempt to call method 'sub' (a nil value)
stack traceback:
        ...im/bundle/rust-tools.nvim/lua/rust-tools/inlay_hints.lua:199: in function 'render_line'
        ...im/bundle/rust-tools.nvim/lua/rust-tools/inlay_hints.lua:255: in function 'render'
        ...im/bundle/rust-tools.nvim/lua/rust-tools/inlay_hints.lua:165: in function 'handler'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:1025: in function 'cb'
        vim/_editor.lua:256: in function <vim/_editor.lua:256>

The problem exists with rust-analyzer version 2023-01-16 but not with version 2022-12-05.

Sorry, somehow I failed at updating the plugin, the latest version already fixed this.


helm charts for kueue

What type of PR is this?
/kind feature
What this PR does / why we need it:
Added helm charts for kueue.
Created the same directory structure for the '/config' folder to make it easier to understand.
Made it possible to enable or disable Prometheus, CertManager, and Webhook.
Wrote a README.md file.
Which issue(s) this PR fixes:
Fixes #436
Special notes for your reviewer:
Thank you for reviewing this PR.
Please let me know if I have made any mistakes or if there are any improvements that could be made.
Your comments and feedback are appreciated.

is this still a draft or ready for review?

/assign

@Gekko0114 Let me know when this is ready for test/review.

Hi @moficodes , @alculquicondor ,
I finished creating PR. Could you take a look?
Thanks,

+1, we should target 0.3
We can probably hold the PR until we are pretty much ready to release. It might be worth including the charts as part of the release artifacts.
https://github.com/kubernetes-sigs/kueue/blob/5fbd5f1981d890537305e67ce33c7aaad9eae944/Makefile#L233-L242

Hi @moficodes , @alculquicondor ,
Thanks for your comments.
When will we plan to release 0.3.0 version?

I'm hoping tomorrow

/ok-to-test
/hold

Some few nits and best practices recommendations, overall nice work! Also Are you planning on adding a GitHub actions to publish the charts (on /site)? or where will the released charts be published?

@ArangoGutierrez ,
Thanks for your helpful comment!
To be honest, I haven't decided yet. However I am considering using GitHub actions to publish the charts.
If you have any recommendations, please let me know.

Some few nits and best practices recommendations, overall nice work! Also Are you planning on adding a GitHub actions to publish the charts (on /site)? or where will the released charts be published?

@ArangoGutierrez , Thanks for your helpful comment! To be honest, I haven't decided yet. However I am considering using GitHub actions to publish the charts. If you have any recommendations, please let me know.

Any time, happy to help.
Take a look at how we do it on NFD, we there have a branch for github pages, here is diff, but I guess you can make a few changes and take up the idea

@alculquicondor , @kerthcet , @tenzen-y , @moficodes , @ArangoGutierrez
Thank you for all your comments! I have made the changes, please take a look. If there are any mistakes or misunderstandings, please let me know.
Also, regarding the release process, I have added only Github Actions for now, but I'm not sure where and how to release it properly(current Github Actions would not work properly because gh-pages branch doesn't exist). If you have any suggestions or recommendations, please let me know. I am not very familiar with Github Actions or helm/chart-releaser- actions, so please correct me if I am wrong.

Ack, will review after kubecon

@moficodes any more comments?

Hi @alculquicondor, @tenzen-y ,
Thank you so much for your comments! I think I have addressed comments (or left a comment if I couldn't fix it)

LGTM from my side. Thanks for your effort.

Hi @alculquicondor,
Could you have a look? I need lgtm label for completing this PR.

will do. I just have a backlog of reviews

/hold cancel

/release-note-edit
Add helm charts

Hi @alculquicondor
I've made the necessary fixes to this PR based on your comments.
Could you please review it again?
Thanks in advance,

/lgtm
/label tide/merge-method-squash

@Gekko0114 @alculquicondor @ArangoGutierrez Is this release intentional?
https://github.com/kubernetes-sigs/kueue/releases/tag/kueue-0.1.0
@ Gekko0114 Also, the chart releaser failed to release the chart. So could you fix this error?
https://github.com/kubernetes-sigs/kueue/actions/runs/4885295071/jobs/8719174796

Nope, that was not intentional, thanks for flagging.
Let me remove the github workflow.

@alculquicondor Also, we may need to delete this tag.
https://github.com/kubernetes-sigs/kueue/releases/tag/kueue-0.1.0

Removed, thanks

@alculquicondor , @tenzen-y ,
I apologize, and thank you for removing the workflow.
I'll create an issue to set up the helm-chart-releaser workflow.


Published Onboard guide for Polygon

Is this an old ss? here I don't see polygon in SS

Hmm there is
P. provided these images

Updated


Add support for overriding coveragePathIgnorePatterns

As this does not appear to be a priority I will close this.


Nmap report

Adds the NMAP module report
Updates to the report formatting for module reports
Adds unit testing around html report creation
Updates and normalizes unit testing structure for existing test modules
Adds gateway capture to TLS client test.

@jhughesbiot could we remove closed ports from the table?

I can but I was under the impression we wanted to show the full results of the scan.  If this isn't the case, I can filter out for only open ports.  However, if we have an empty table with no details because nothing is open, it might look broken.

I can but I was under the impression we wanted to show the full results of the scan. If this isn't the case, I can filter out for only open ports. However, if we have an empty table with no details because nothing is open, it might look broken.

Could we perhaps remove the table and provide test stating 'No ports have been detected open' if none are found? Just with all ports open, the nmap part of the report takes up more than a page for me.

Yeah, that sounds good, I'll check for no open ports and update accordingly.  I wouldn't be too concerned with going over a page though, the DNS equivalent table can cover multiple pages.

Updated table with closed ports removed:

Updated report if no ports are detected open:


Add the expected error verification for TestRmiBlank.

Signed-off-by: Yuan Sun<EMAIL_ADDRESS>

LGTM if janky's okay

LGMT

Thank you for adding this @sunyuan3 ! Merging :tada:


PugiXML incorrectly handles char8_t in C++20

In C++20 there is a std::u8string and char8_t to make UTF-8 type-safe.
Unfortunately when calling xml_attribute::set_value(u8"a string") for example compiler chooses set_value(bool) overload which lead to a surprise when all attrubutes became juse "true".
Which makes me thing that providing an overload which accepts bool is too wide: it can be any pointer at least. Would be nice to constrain it somehow.
I'm not sure if there is a need to have a separate handling when pugi::char_t is wchar_t or simply provide such overload when it's a char.

I also thought that it may be a good idea to just use char8_t for pugixml::char_t since UTF-8 is used internally anyways.
I think if consumer could define PUGIXML_TEXT and PUGIXML_CHAR directly instead of relying on PUGIXML_WCHAR_MODE things will just work (or provide more knobs...)

Which makes me thing that providing an overload which accepts bool is too wide: it can be any pointer at least. Would be nice to constrain it somehow.

This is sensible; this can probably be achieved using a private overload with const void* argument, as you can't use enable_if or other constructs like this due to compatibility requirements. Separately, char8_t as char_t won't work because of reliance on some CRT functions like strcmp.

Separately, char8_t as char_t won't work because of reliance on some CRT functions like strcmp.

Oh, I didn't look that deep, but it feels like case for std::char_traits<char_t>::compare...
I guess I should continue sticking to reinterpret_cast for now, just use it carefully :)


parentage

I just spotted that
reorganization of cellular membranes to establish viral sites of replication
A process in intracellular membranes are reorganized by viral proteins that perturb membrane integrity and can cause an extensive rearrangement of cellular membranes, forming membranous webs, which are thought to be the site of replication or certain viruses, for example the HPV virus
is_a
biological process involved in interaction with symbiont
An interaction between two organisms living together in more or less intimate association. The term symbiont is used for the smaller (macro) of the two members of a symbiosis; the various forms of symbiosis include parasitism, commensalism and mutualism.
it seems the wrong way around? That's a symbiont process?

Hi @Antonialock
This is a host process, see https://github.com/geneontology/go-ontology/issues/22686
Please let me know how I can clarify the definition, it was hard to distinguish between the host and the symbiont version of this process.
Note also that the host role in  establishment of viral sites of replication is not an evolved pathway, we have been struggling to represent these...
@thomaspd

So isn't it out of the scope of GO then? It sounds like a pathological process?

If the targets are proteins that make some membrane molecule perhaps the viral proteins could be annotated to
regulation of X activity, regulates:human protein Y, part_of reorganization of host cellular membranes to establish sites of replication

( I don't know if that's allowed / makes sense for the targeted proteins)


Attempt to turn on build_without_cgo tests

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Looks like a real failure

Replaced by https://github.com/containers/libpod/pull/6341


"SetVariable" on ReadOnly modify the parameter

Hello,
I was trying to set some parameter of my charger, and I tried one in Read Only to try. The charger response was rejected, but the parameter in the “Variable Attribute” windows have been changed, despite the response was rejected and parameter set to “Read-only”.
Is that a bug ? Or I made something wrong ?
Thanks for your help.

Hi @DylanVautrin ! That could be a bug. There's a collection, VariableStatus, that is supposed to capture the current state of the variable attributes. When a variable fails to set, there should be a record of it in the VariableStatuses, then the VariableAttribute should be rolled back to the last successful value. The only exception to this is when the device model is updated with the 'setOnCharger' query param as true, indicating that charger already has this configuration and CitrineOS doesn't need to confirm.
If you could confirm what actions are needed to create this issue, and show some screenshots of the collections, we can investigate this further.

Hello,
By luck, I made a screenshot of my test, so here the command I've sent :

I have the response of the charger too if needed :

And here the content of Variable Statuses :

Do you need something else ?
Thanks again :)

This is definitely a bug, I see the issue in the code. There should be logic to roll back to the most recent accepted value in the 'updateResultByStationId' method of the SequelizeDeviceModelRepository when the result is rejected.
Thank you for pointing this out! If you feel comfortable fixing it yourself, please open a PR. Otherwise, I'll update this thread in the future when someone else gets to fixing the issue.

Hello,
Okay ! Unfortunately, i don't think i'm able to make the fix myself
Thanks again for your help

Hello @DylanVautrin! The bugfix has been merged to release 1.3.1.
If you have a chance, can you pull CitrineOS main (currently on release 1.4.2) and see if it fixes the bug you were facing? If so, please close this issue. Thank you!

Closing this as fixed.


add MERG table

I started implementing the MERG table.
https://github.com/schriftgestalt/fonttools/tree/add-MERG-table
Reading to XML works but writing is not. The offsets to the ClassDefs are written relative to the MergeClassDefs offset and not to the beginning of the table. I didn't find a solution that didn’t involved hacking in some key places. Does anyone has an idea?

https://learn.microsoft.com/en-us/typography/opentype/spec/merg#table-formats

Each element in the array is an Offset (unsigned 16-bit) from the start of the MERG table to a class definition table.

Hm, this is quite uncommon. Usually offsets are relative to the beginning of the parent "table", for MERG there's an offset (relative to beginning of MERG table) to an array of offsets, but then the offset elements in this array are not relative to the beginning of the array itself (as it would normally be the case) but relative to the beginning of the parent MERG table.
I'll have to think about how to deal with this within the otData machinery 🤔


About the issue with hot reloading

I have mounted a directory from Windows on a Hyper-V virtual machine. The mount command I used is: mount -t cifs -o username=xxx,password=xxxxxxx,uid=1001,gid=1001 //<IP_ADDRESS>/www /data/wwwroot. After making changes to the files, hot reloading is not working, and I have to restart for the changes to take effect.

I have the same issue. Its a mounted volume on windows and it just doesn't detect the changes at all.


Undo redo command

Allows users to undo a command, or redo a previously undone command.
The undo/redo mechanism is facilitated by UndoManager. It extends InternWatcher with an undo/redo history, stored internally as an watcherStateList and currentStateIndex. Additionally, it implements the following operations:
commitState() — Saves the current address book state in its history.
undo() — Restores the previous state from its history.
redo() — Restores a previously undone state from its history.

Still incomplete as I haven't updated the classes to accept it as a valid command.


Initial Kubernetes support

Just a ticket to track what it takes to support Kubernetes, outcome will likely be a draft PR with a working helm-chart with some quirks, which can open discussions on how to work around them.

Draft PR with PBS module support:
https://github.com/Commit-Boost/commit-boost-client/pull/92
This is currently running under Holesky. I'll simplify it a bit & add more features.

Technically it works well and we've had it running for a while in holesky, I still have to write documentation to mark it done :)


Invalid certificate authority error for self-signed certificates

Attempting to access service with self-signed certificates throws the following: "The certificate authority is invalid or incorrect."
Will look into bypassing certificate checking in WinHttpRequest and cURL. If it's possible, default will remain checking the certificate with option added to override.

To ignore invalid certificate authority errors (and other SSL errors), use:
Client.Insecure = True


Scrolling content

Hi,
First just wanted to say I love your component and really want to use it in a project.
I'm having an issue combining it with scrolling content though. I have div component holding a timeline. It is set to overflow-y:scroll but it almost impossible to scroll the content without activating the slide.
Can this be done at present?
Thanks,
David

I think I got the behaviour I was looking for. I checked the x movement within _onPointerMove and I only call this._requestDragTick() if it was significant enough that the user was obviously not just scrolling through content on the current slide.

Hey @ctpresales , it looks like you already found where to look in the code.
At the moment, x-slider is not production ready yet (I need to handle a couple of edge cases/bugs, write tests for them, and have a final round of QA).
Until that time, I don't think I'll publish it on the npm registry, but please if you have time have a go with it and let me know about your feedback (including docs, bugs or feature requests)


SVG/dot output limits specified via command line arguments

Partially addresses #377 by allowing the number of functions/calls per function to be specified via the command line. Preserved current behaviour if user does not specify limits.
Very happy to consider alternative approaches that may be more widely applicable.

The CI is failing. Could you also fix the web demo?

Oh yes, missed that one. Should be fixed now.

Thanks!

Thank you for this!


Release Google.Cloud.Batch.V1Alpha version 1.0.0-alpha08

Changes in this release:
New features

Support custom scopes for service account in v1 (commit 7e2eb5a)
Add boot disk field in InstanceStatus (commit 7e2eb5a)
Add boot disk and image source fields to v1 InstancePolicy (commit 7e2eb5a)

Created release for Google.Cloud.Batch.V1Alpha-1.0.0-alpha08


chore(*): set nx.json semantic-release

Description
Not sure why its OK locally and not CI though.
Found following dependencies: “” for project “@polymeshassociation/azure-signing-manager”
https://github.com/PolymeshAssociation/signing-managers/actions/runs/11277009656/job/31363290848#step:6:130
Breaking Changes

JIRA Link

Checklist

[ ] Updated the Readme.md (if required) ?

/fast-forward


add where_cond f32 for metal

Make sure we have where_u32_f32 for metal

Thanks!

Pleasure !!!
Le dim. 2 juin 2024 à 14:30, Laurent Mazare @.***> a
écrit :

Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/candle/pull/2236#issuecomment-2143829279,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAENB4DDTZKZDVKG2G7IF63ZFMF6XAVCNFSM6AAAAABIU7UQUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTHAZDSMRXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>


⚠ LPDM Handbook (hosted on Divio) has degraded performance

In f31a273, LPDM Handbook (hosted on Divio) (https://repohubdev.tk) experienced degraded performance:

HTTP code: 500
Response time: 6526 ms

Resolved: LPDM Handbook (hosted on Divio) performance has improved in b482326.


the "Url to app installation" field doesn't make sence for services. Please make it optional or update the documentation with workaround.

Could you please enhance description for the URL to app installation field from https://docs.microsoft.com/en-us/azure/marketplace/partner-center-portal/create-new-business-central-offer#url-to-app-installation
Current:
URL to app installation
If you selected Connect above, provide the URL for your app installation here.
Suggestion:
URL to app installation
If you selected Connect above, provide the URL for your app installation here. For connected  services that doesn't require installation, provide the URL for your service landing or sign-up page.

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

ID: b50ce1d1-fc0b-0d5d-ff42-8da5baa3b8c2
Version Independent ID: f53d7482-5aa1-de0b-68c0-f302161568a1
Content: Create a new Dynamics 365 Business Central offer in the Commercial Marketplace
Content Source: articles/marketplace/partner-center-portal/create-new-business-central-offer.md
Service: marketplace
Sub-service: partnercenter-marketplace-publisher
GitHub Login: @ChJenk
Microsoft Alias: v-chjen

@AndreiPanko Thanks for the feedback.
Assigning content owner @ChJenk for visibility, review and document enhancement consideration.

#reassign:dsindona

@AndreiPanko thanks for the suggestion. The field is not optional, so instead I am adding some clarifying text as you suggested. It will publish later today.
#please-close


Update SDK to OpenAPI spec

Changes

Generate SDK to latest OpenAPI specification
Tests

Unit Tests

Superseded by #297.


gke pipelines-as-code immediately maxes out Persistent Disk SSD (GB) quota on Compute Engine API

When I apply the following Kubernetes manifests on the default GKE cluster:
# Install tekton pipelines and tasks
kubectl apply --filename https://storage.googleapis.com/tekton-releases/pipeline/latest/release.yaml

# Install tekton operators for tekton config
kubectl apply -f https://storage.googleapis.com/tekton-releases/operator/latest/release.yaml

# Install Tekton dashboard
kubectl apply --filename https://storage.googleapis.com/tekton-releases/dashboard/latest/release.yaml

# View Tekton dashboard
kubectl proxy

# Install pipelines-as-code on Kubernetes
kubectl apply -f https://raw.githubusercontent.com/openshift-pipelines/pipelines-as-code/stable/release.k8s.yaml

As well as creating the following Ingress:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
    pipelines-as-code/route: controller
  name: pipelines-as-code
  namespace: pipelines-as-code
  annotations:
    kubernetes.io/ingress.class: gce
spec:
  defaultBackend:
    service:
      name: pipelines-as-code-controller
      port:
        number: 8080

My cluster immediately hits the following quota

Why is this? What in Tekton is using so much Persistent Disk SSD storage? Nothing else is running on this project.

I am not so sure what is the issue with GKE but i am running this same setup under kind (with more services) and definitively don't reach that same size:

maybe try to contact the GKE support?

can you try without pipelines-as-code does this takes way less ?

pipelines-as-code images should not take much as well:


Add ctx timeouts to all sinks

Hey @jakthom, I'm thinking to take on that issue, if that's ok..?
Do you mean the user should add a timeout to the ctx (when calling the publish funcs)?
if so then, inside each sink we'll handle the timeout gracefully ( if it's not already doing that on it's own like in Kafka's case)

Oh man, @orgr I am so sorry about just seeing this! If you want to, by all means feel free.
I actually just merged some code that makes this much easier to implement.
Here's the best place to start:
https://github.com/silverton-io/buz/blob/main/pkg/backend/backendutils/sink.go#L38
In terms of getting things up and running, make bootstrap after a git pull will get a sample config in place and buz spinning.
If you'd also like to get available backends up and running, there's a docker compose located here. After pulling buz-docs you can docker-compose -f devel/docker-compose.yml up to get the destinations spinning.
Again, so sorry for not seeing your comment sooner.


Fix memory growth

Per #33, https://github.com/webmproject/libwebm/blob/3d1f6dd8876ed87df705109edaeed35b96c3d116/mkvmuxer/mkvmuxer.h#L1815 holds a continuously-growing list of clusters.
#33 worked around this by allowing memory growth.
It may be that we don't need the list of clusters when live-streaming for example. Investigate this and see if we can remove the list.

@CitronBaBa I've pushed a change 7021b8f00830dfd7443f2ccd7dd00763e56bad8d which removes the cluster list.
I left a live video encoding running for 3 hours, having reduced initial memory size, and it didn't grow at all.
If you get a chance to give it a try it'd be great to know what you think.


Improve docs and fix copy() type

Make TypeVars public
Import symbols from typing as top-level
Make default values public
Use Self instead of RetryStrategy in copy method signature
Update release notes

Rebased to solve conflicts and enabled auto-merge, needs another approval.


[crash] check/154: ImportError: cannot import name 'urlopen'

This is a python 3 problem that our code-tests did not detect.

here's a description of the proper way of using urllib on python 3:
https://docs.python.org/3/howto/urllib2.html
This crash was not noticed previously because the check that could detect it was disabled:

#1712


Enhance the update-all groovyw utility script further with better logging and resume capability

Essentially three small separate enhancements but maybe not separate issues:

Make groovyw module update-all log what actually gets updated per module - right now there's no actual indication if anything got updated, it would be nice to see a summary with "x new files added, y files updated, z files deleted" or something. Ideally log it to the screen, but if for some reason a log file is better that could work too.

In case of failures either skip a given module and/or allow the script to resume smartly if executed again. For instance don't re-update a module that's already been updated within the last few minutes (there's got to be something in the local git repo that indicates the last fetch or something?)

Respect the .gitignore file when it comes to directories in the modules dir to ignore, like a possible .settings hanging out in there for Eclipse

JGit or whatever it is we're using should have some useful utility to help with some of those :-)
Possible extra just so we have it listed somewhere: support a groovyw module set [x] where [x] is a branch name (so in other words a bulk "Set all my module branches to [x]" operation. Mostly this is probably useful if you're trying to get back to the master branch (so groovyw module set master) - I'm unsure what it should do if you give it a branch name that doesn't exist yet. IntelliJ rarely has tried to bulk-change my branches for all nested Git repos but rarely in a useful fashion.

Here's an example of the output from a routine git pull for a module:
C:\Dev\Terasology\Git\ModuleMegaWorkspace\Terasology\modules\ManualLabor>git pull origin master
From https://github.com/Terasology/ManualLabor
 * branch            master     -> FETCH_HEAD
Updating 68ecbd8..b56c2a2
Fast-forward
 README.md                                       | 7 +++++--
 assets/prefabs/blocks/MetalChest.prefab         | 2 +-
 assets/prefabs/blocks/WoodenChest.prefab        | 2 +-
 assets/prefabs/blocks/WoodenDisplayBlock.prefab | 2 +-
 4 files changed, 8 insertions(+), 5 deletions(-)

While the file-by-file details are going to be too much it would be nice to get the other stuff including git hash, that it is a fast-forward (imho any non-ff operation should halt - too unpredictable), and the summary of changes
A potential added issue: some modules show "dirty" as per the script (and thus JGit I guess) yet clean with git status at least in Windows 10. Specifically I hit that for GooeyDefence and ManualLabor. Probably some odd casing or line ending issue that gets "fixed" in the local workspace but then is detected as a change by JGit yet ignored as a non-change by plain git status

@jdrueckert added a bunch of .gitattributes to modules but not all of them have that yet. This may fix the status issue.


Missing License(s)

I noticed you are missing the license and license headers found in the original project this came from.

Merged


Mention contributor agreements in the contribution section of our docs.

Because, y'know, we require them.

Addressed by #428 and #432.


added comments

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes (if any) #(issue_no)
Replace issue_no with the issue number which is fixed in this PR
Have you read the Contributing Guidelines on Pull Requests?

[ ] Yes
[ ] No

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Documentation Update

Checklist:

[x] My works and is relatively clean.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas

Thanks for merging
On Thu, 8 Oct, 2020, 5:31 am Seth Walker<EMAIL_ADDRESS>wrote:

Merged #19 https://github.com/SethWalkeroo/Quiet-Text/pull/19 into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SethWalkeroo/Quiet-Text/pull/19#event-3852950587, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKYRMRT5X2YXWKQTBAZ5ZCTSJT6OPANCNFSM4SHMUFVQ
.

@all-contributors please add aish0007 for docs


Enable hiding sectors in embed

Overview
Adds a check box to the Embedded Map settings page that allows a user to toggle the display of the sector field on and off.
Connects #2187
Demo

Testing Instructions

Run ./scripts/manage migrate and ./scripts/server
Login as<EMAIL_ADDRESS>and visit the embed tab in the settings. Confirm that the 'Hide sectors' checkbox is present.
Login as<EMAIL_ADDRESS>and visit the embed tab in settings. Confirm that the 'Hide sectors' checkbox is present (c3 has a lower embed permission level than c2).
Give the embedded map a height/width, and confirm that the sector filter is shown on the search page, and the sector field is shown on the facility details page.
Check the box for 'Hide sector data'. Confirm that the sector filter is hidden on the search page, and the sector field is hidden on the facility details page.

Checklist

[x] fixup! commits have been squashed
[ ] CI passes after rebase
[x] CHANGELOG.md updated with summary of features or fixes, following Keep a Changelog guidelines
[x] This PR is targeted at the correct branch (develop vs. ogr/develop)
[ ] If this PR applies to both OAR and OGR a companion PR has been created

Thank you for reviewing!


Training on selected subset of Dask DataFrame rows

In order to do CV iterations, I'd like to load all the data into a Dask DataFrame, select a subset of rows, and then train only on those selected rows. I've written some code that does this and it works when I use a LocalCluster. When I try and use a true distributed cluster, I get an error when constructing the worker_map:
Traceback (most recent call last):
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/dask_xgboost/core.py", line 116, in _train
    worker_map[first(workers)].append(key_to_part_dict[key])
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/toolz/itertoolz.py", line 368, in first
    return next(iter(seq))
StopIteration

I tried to write a test that demonstrates this behavior, but the test passes. This makes me think that distributed.utils_test.gen_cluster uses a LocalCluster. Is there anyway to run this test with a true distributed cluster?
@gen_cluster(client=True, timeout=None)
def test_subset(c, s, a, b):
    # Train in xgboost with selected data
    dtrain = xgb.DMatrix(df[df.x < 8], label=labels[:7])
    bst = xgb.train(param, dtrain)

    # Combine data and labels and select rows together
    newdf = df.copy()
    newdf["labels"] = labels
    ddf = dd.from_pandas(newdf, npartitions=4)
    ddf_trimmed = ddf[ddf.x < 8]

    # Split data and labels back apart
    ddf_train = ddf_trimmed.drop("labels", axis=1)
    ddf_labels = ddf_trimmed["labels"]

    # Train in dask-xgboost with trimmed data (fails with distributed cluster!)
    dbst = yield dxgb._train(c, param, ddf_train, ddf_labels)

    result = bst.predict(dtrain)
    dresult = dbst.predict(dtrain)

    correct = (result > 0.5) == labels[:7]
    dcorrect = (dresult > 0.5) == labels[:7]
    assert dcorrect.sum() == correct.sum()

Still tracking this down. It works when I start workers from the command line on the same machine. It does not work when I use command line workers on two different machines. It gives me the same error on the scheduler as above, but since I'm using the command line workers I can get new error messages from workers that aren't local to the scheduler:
distributed.protocol.pickle - INFO - Failed to deserialize b"\x80\x04\x95\xc9\x03\x00\x00\x00\x00\x00\x00(\x8c\ndask.utils\x94\x8c\x0cmethodcaller\x94\x93\x94\x8c\x05apply\x94\x85\x94R\x94]\x94(\x8c/('getitem-b9a4e72ddad1ca8e3fa063ede97f4f79', 4)\x94\x8c\x17cloudpickle.cloudpickle\x94\x8c\x0e_fill_function\x94\x93\x94(h\x08\x8c\x0f_make_skel_func\x94\x93\x94h\x08\x8c\r_builtin_type\x94\x93\x94\x8c\x08CodeType\x94\x85\x94R\x94(K\x01K\x00K\x01K\x04KSC\x1bt\x00\x00|\x00\x00d\x04\x00d\x00\x00\x85\x02\x00\x19d\x02\x00\x83\x02\x00d\x03\x00\x16S\x94(NK\x03K\x10K\x05J\xfd\xff\xff\xfft\x94\x8c\x03int\x94\x85\x94\x8c\x03sha\x94\x85\x94\x8c\x1edistributed_train_dataframe.py\x94\x8c\x08<lambda>\x94KUC\x00\x94))t\x94R\x94J\xff\xff\xff\xff}\x94\x87\x94R\x94}\x94N}\x94\x8c\x08__main__\x94NtR\x88)e}\x94\x8c\x12pandas.core.series\x94\x8c\x06Series\x94\x93\x94)\x81\x94}\x94(\x8c\x05_data\x94\x8c\x15pandas.core.internals\x94\x8c\x12SingleBlockManager\x94\x93\x94)\x81\x94(]\x94\x8c\x18pandas.core.indexes.base\x94\x8c\n_new_Index\x94\x93\x94\x8c\x19pandas.core.indexes.range\x94\x8c\nRangeIndex\x94\x93\x94}\x94(\x8c\x05start\x94K\x00\x8c\x04name\x94N\x8c\x04stop\x94K\x00\x8c\x04step\x94K\x01u\x86\x94R\x94a]\x94\x8c\x15numpy.core.multiarray\x94\x8c\x0c_reconstruct\x94\x93\x94\x8c\x05numpy\x94\x8c\x07ndarray\x94\x93\x94K\x00\x85\x94C\x01b\x94\x87\x94R\x94(K\x01K\x00\x85\x94\x8c\x05numpy\x94\x8c\x05dtype\x94\x93\x94\x8c\x02i8\x94K\x00K\x01\x87\x94R\x94(K\x03\x8c\x01<\x94NNNJ\xff\xff\xff\xffJ\xff\xff\xff\xffK\x00t\x94b\x89C\x00\x94t\x94ba]\x94h1\x8c\x1bpandas.core.indexes.numeric\x94\x8c\nInt64Index\x94\x93\x94}\x94(h7N\x8c\x04data\x94h?hBK\x00\x85\x94hD\x87\x94R\x94(K\x01K\x00\x85\x94hM\x89hPt\x94bu\x86\x94R\x94a}\x94\x8c\x060.14.1\x94}\x94(\x8c\x06blocks\x94]\x94}\x94(\x8c\x08mgr_locs\x94h?hBK\x00\x85\x94hD\x87\x94R\x94(K\x01K\x00\x85\x94hM\x89hPt\x94b\x8c\x06values\x94hFua\x8c\x04axes\x94h.ust\x94bh7N\x8c\x04_typ\x94\x8c\x06series\x94\x8c\t_metadata\x94]\x94h7aubt\x94."
Traceback (most recent call last):
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/distributed/protocol/pickle.py", line 59, in loads
    return pickle.loads(x)
TypeError: _fill_function() takes 5 positional arguments but 6 were given
distributed.worker - WARNING - Could not deserialize task
Traceback (most recent call last):
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/distributed/worker.py", line 1241, in add_task
    self.tasks[key] = _deserialize(function, args, kwargs, task)
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/distributed/worker.py", line 658, in _deserialize
    args = pickle.loads(args)
  File "/home/proth/.conda/envs/dask/lib/python3.5/site-packages/distributed/protocol/pickle.py", line 59, in loads
    return pickle.loads(x)
TypeError: _fill_function() takes 5 positional arguments but 6 were given

Still working on it, but if this looks familiar to anyone I'd love to know.

Given the error my first guess is a difference in library versions somewhere.  Perhaps _fill_function takes five or six arguments in different versions of the same library.

So there has been some activity in cloud pickle. I'd validate that all your nodes are running the same /latest? Version

Yep. Versions. I did a deep clean on my local conda environment. I must have had something old in there that was different from what was getting provisioned on EC2 nodes. Thanks.


Support loading attribute on Button

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

@sagardspeed2 please link your PRs to issues

@evshi I think I attached with issues, This is new issue may be


Update Chinese language text

Thank you, and sorry for the delay. New release in just a few minutes.

👍🎉🎉


Return the Sum of Two Numbers

Before jumping into Pr first comment for assign.All Problem from Edabit. Link is mandatory to add
Problem statement: Create a function that takes two numbers as arguments and return their sum.
Problem Link: https://edabit.com/challenge/3LpBLgNRyaHMvNb4j

Before submitting a PR please Check some details.Check Edabit for problem task

[ ]  Add label for Problem
[ ]  In file there should be problem statement and link to probelm
example -
[ ] fileName formet should be in camelcase
example- returnTheNextNumber.py

'''
    Probem Task : This program will add two numbers
    Problem Link : https://edabit.com/challenge/SFzHtm63XT6EYNHWY
'''
*/
def main():
    return a + b

This repository is vaild for HacktoberFest2020
Read before making PR - How to contribute on Github
Good Luck,

Hey can I solve this problem, this would be a oneliner

Can I solve it?

Hey ! Can I solve it?

I wanna work on this!


Self test date updated to 15.11.2024 (for push to develop branch)

not merged. Should be part of stabi branch...


Fix usage of wait-for-postgres.sh

The docker-compose example file passed db:5432 as the -h option for psql. However, -h is to specify the hostname, and doesn't
accept a port number.

Thanks, but I see this usage in wait-for-it.sh's docs:
wait-for-it.sh host:port [-s] [-t timeout] [-- command args]


Handle TIMESTAMPTZ in Lua SQL queries

The server does not do the required conversion of the SQL TIMESTAMPTZ data type to a format which can be recognised by Lua. This can be demonstrated with:
local query = [[
SELECT create_time FROM users LIMIT 1
]]
local parameters = {}
local rows = nk.sql_query(query, parameters)
for _, row in ipairs(rows) do
  for k, v in pairs(row) do
    print(k, v)
  end
end

As a workaround it's possible to instruct the database to cast the TIMESTAMPTZ to VARCHAR within the query and access the row key with row["create_time::VARCHAR"].
SELECT create_time::VARCHAR FROM users LIMIT 1

Fixed in 1c61023c8fc27c8c9e2a8fd306b9d1d57ad45744 and will be part of the next release. Database time types are now converted to UTC seconds before being exposed to the Lua runtime.
This was the last database return value type not correctly handled. In the general case unknown types will now convert to Lua nil values - open a new issue for any further types that need special handling.

Thank you @zyro


Example file using a Swing window

Shows that the library works as well as how one would use it with a GUI. Could definitely be cleaned up but ¯\_(ツ)_/¯

I don't want examples to be included inside the library source. If examples are to be added they have to be on a separate source set.

Done and done. Hopefully it looks good now?


Even after a second read, this documentation isn't helping.

So I gave the documentation another chance. PLEASE. How about TFS documentation? One-size-fits all isn't working.

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

ID: 2d588805-0219-7eb1-6a5c-1f1363f41870
Version Independent ID: 515fb392-083b-644b-b824-efb581aa0a91
Content
Content Source
Service: unspecified

Thank you for your feedback. TFS and VSTS share a UI and features, however the release schedule for updates to VSTS is more regular - which causes some disconnect in the documentation until TFS releases catch up. We are working to provide a new documentation experience that clearly shows the differences between VSTS and each version of TFS. You will see this new experience appearing in the coming months.


Document how the domain._factory module works

There is a lot of "magic" here, it really needs documenting and justifying

This module no longer exists :tada:


Missing target attribute

These variables are supposed to have the target attribute:
https://github.com/arjenmarkus/io_utilities/blob/8b3a01f7b793457e54b2d37d6e04deca340736ba/test/test_keyvars.f90#L9-L11
The keyvar(...) type uses pointers internally.

You're absolutely right. I have updated the source and the documentation.


error checking improved closes #78

Coverage remained the same at 100.0% when pulling b9bf8b58a5fc06b0a226ad9dbcebd25907eb6179 on improve-error-checking-#78 into 12ed31388ad82be6849dd0b50e23b7aa367d72d2 on develop.


sdk.openlogin.com erro

Sometimes when I’m trying to login using web3sdk for ios I got the next error. How to fix that?
We used v3.5.1. The error is reproduced only for the first attempt of autorisation.
We used the next code
Task {
let response = try await Web3Auth().login(W3ALoginParams(loginProvider: .GOOGLE)) { result in
switch result {
case .success(let state):
print("success")
case .failure:
print("error")
}
}
}

Fixed in 6.0.0. Pls upgrade


refactor(rust/gui-client): remove Tauri from the tray menu code

Closing this, it's out of date and I don't think it will be needed if we go ahead with GTK