Wrong SparkSession initialization in Testing method 'withQbeastContextSparkAndTmpDir'

What went wrong?
When running a single test that uses withQbeastContextSparkAndTmpDir, as there is no active SparkSession it fails. For example, in this test:
https://github.com/Qbeast-io/qbeast-spark/blob/35c9f5698ee7ce01e1eaf467013805dfad63d7da/src/test/scala/io/qbeast/spark/utils/QbeastDataSourceIntegrationTest.scala#L13-L15
The method withQbeastContextSparkAndTmpDir is called and will fail, due to QbeastContext needing an active SparkSession, which is not active at this point yet:
https://github.com/Qbeast-io/qbeast-spark/blob/35c9f5698ee7ce01e1eaf467013805dfad63d7da/src/test/scala/io/qbeast/spark/QbeastIntegrationTestSpec.scala#L144-L145
As you can see, withQbeastContext tries to get the SparkSession:
https://github.com/Qbeast-io/qbeast-spark/blob/35c9f5698ee7ce01e1eaf467013805dfad63d7da/src/test/scala/io/qbeast/spark/QbeastIntegrationTestSpec.scala#L126-L128
How to reproduce?

Code that triggered the bug, or steps to reproduce:
Run the mentioned test, for example, the one mentioned from QbeastDataSourceIntegrationTest.scala.

 Are you launching the app on a remote K8s cluster? Or are you just running the tests in a local computer?
I'm running the tests in my local computer.

Stack trace:

No active or default Spark session found
java.lang.IllegalStateException: No active or default Spark session found
	at org.apache.spark.sql.SparkSession$.$anonfun$active$2(SparkSession.scala:1065)
	at scala.Option.getOrElse(Option.scala:189)
	at org.apache.spark.sql.SparkSession$.$anonfun$active$1(SparkSession.scala:1065)
	at scala.Option.getOrElse(Option.scala:189)
	at org.apache.spark.sql.SparkSession$.active(SparkSession.scala:1064)
	at io.qbeast.spark.QbeastIntegrationTestSpec.withQbeastContext$default$2(QbeastIntegrationTestSpec.scala:128)
	at io.qbeast.spark.QbeastIntegrationTestSpec.withQbeastContext$default$2$(QbeastIntegrationTestSpec.scala:128)
	at io.qbeast.spark.utils.QbeastDataSourceIntegrationTest.withQbeastContext$default$2(QbeastDataSourceIntegrationTest.scala:11)
	at io.qbeast.spark.QbeastIntegrationTestSpec.withQbeastContextSparkAndTmpDir(QbeastIntegrationTestSpec.scala:145)
	at io.qbeast.spark.QbeastIntegrationTestSpec.withQbeastContextSparkAndTmpDir$(QbeastIntegrationTestSpec.scala:144)
	at io.qbeast.spark.utils.QbeastDataSourceIntegrationTest.withQbeastContextSparkAndTmpDir(QbeastDataSourceIntegrationTest.scala:11)
	at io.qbeast.spark.utils.QbeastDataSourceIntegrationTest.$anonfun$new$1(QbeastDataSourceIntegrationTest.scala:15)
	at org.scalatest.OutcomeOf.outcomeOf(OutcomeOf.scala:85)
...

I suggest just going withSparkAndTmpDir, without involving any QbeastContext initialization in the spec.
In case we are trying new configurations, we can do so with the SparkSession.config(...)

I suggest just going withSparkAndTmpDir, without involving any QbeastContext initialization in the spec.
In case we are trying new configurations, we can do so with the SparkSession.config(...)

Then, when do we need withQbeastContext() in the tests? As I understand from your comment, we only need it if we change some of the SparkConf, but we can do it with the SparkSession.config(...), right?
I quickly fixed it in the branch I was working (PR #62, commit 81f7b4) by changing the order of the methods, but I don't really know when we need the QbeastContext.

Closing because is already fixed in main since commit c4a6a64a6acd3ee18b3d38ba30e5609fd7f5b7b7


BlobBaseClient.StartCopyFromUriAsync document: Text overflowing edge of browser, can't scroll over

The summary statement at the top of the page goes of the page and I am unable to scroll horizontally.

Resizing the window does not fix the issue
I am using Microsoft Edge browser Version 88.0.705.74

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

ID: efd0e00b-df56-46f2-be22-3949805f85d3
Version Independent ID: e106e179-f3d8-30ad-14ea-2bbc06772f17
Content: BlobBaseClient.StartCopyFromUriAsync(Uri, BlobCopyFromUriOptions, CancellationToken) Method (Azure.Storage.Blobs.Specialized) - Azure for .NET Developers
Content Source: xml/Azure.Storage.Blobs.Specialized/BlobBaseClient.xml
Service: azure
GitHub Login: @CamSoper
Microsoft Alias: casoper

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@danieljurek:  This looks like it may be a tooling issue.   The summary section from the doc comments isn't wrapping and the <see cref="" /> expansion is way wrong.   The comment source looks like:
/// <summary>
/// The <see cref="StartCopyFromUri(Uri, BlobCopyFromUriOptions, CancellationToken)"/>
/// operation begins an asynchronous copy of the data from the <paramref name="source"/> to this blob.
/// You can check the <see cref="BlobProperties.CopyStatus"/>
/// returned from the <see cref="GetProperties"/> to determine if the
/// copy has completed.
///
/// For more information, see
/// <see href="https://docs.microsoft.com/en-us/rest/api/storageservices/copy-blob">
/// Copy Blob</see>.
/// </summary>

Do you mind offering your thoughts?

Yeah, this appears to be a problem specific to the docs.ms.com processing of the refdocs.  It appears to be fully qualifying the types which creates the wrapping problem.  If we can fix the types from being fully qualified, there won't be a line wrapping problem.
For comparison, here is a link to the github.io docs for the same function and it doesn't fully qualify the types.

Link to internal work item: https://dev.azure.com/ceapex/Engineering/_workitems/edit/389299?src=WorkItemMention&src-action=artifact_link

Internal tracking item is closed.  Closing...


fix: completely remove update_source_code

What is the problem that this fixes or functionality that this introduces? Does it fix any open issues?
In https://github.com/OpenDevin/OpenDevin/pull/3259 we removed update_source_code, but forgot to do the same in other places (e.g., evals) 😓

Give a summary of what the PR does, explaining any non-trivial design decisions
This PR remove those

Other references

@li-boxuan You probably need to pull down SWE-Bench's instance images to run it: we move to use instance-level images, because it will allow us to run on the full SWE-Bench easily..
https://github.com/OpenDevin/OpenDevin/tree/main/evaluation/swe_bench#opendevin-swe-bench-instance-level-docker-support


Add legends for analyses

I have some Analyses on a plot, such as a linear fit and a smoother, in different colors. I would like it to create a legend that shows what the lines mean.
let N = 1000
(
    data(DataFrame(a=rand(N), b=rand(N)))
    * mapping(:a, :b)
    * (
        visual(Scatter, markersize=2)
        + AlgebraOfGraphics.linear() * visual(color=:teal)
        + AlgebraOfGraphics.smooth(span=0.1) * visual(color=:pink)
    )
)|> draw(resolution=(800,600))
end

Any update on this?


Module bases test cases updated (EN-1778)

┆Issue is synchronized with this Jira Task by Unito

This is a really poor issue description.

extremely poor !?!?
i could have never understood it by reading it

Sorry for the inconvenience, both title and description are updated now.


Add esm module support

Fixes Issue #23
Proposed Changes

Add option to bundler.js script to generate an esm module output file
Update original umd output file name to beedle.umd.js to distinguish between the different module types. Ideally, this file would be removed in the future and the main entry point updated to be the newly added bundler.js esm file.

A brief summary of what the changes do
The changes proposed here improve the library by providing a module entry point into the package for tools like @pikapkg/web that generate and provide browser ready ES6 modules based on this entry point. It also means there will now be an unpkg browser ready esm option, while still providing the umd version for users consuming the package via unpkg with Nodejs.
Once enough Nodejs support is available for ES6 modules (see node documentation for further reading around this) then the bundler.js script and the package entry points can be updated to include only the beedle.js esm file.
It's a forward looking approach while not affecting users that still need to consume the package with Nodejs in it's current state of support for ES6 modules.

I also noticed that the first test is currently failing. Dispatch returns true if action was found. It's returning undefined but expects true. I haven't looked into what the problem is and didn't touch it as it's not connected with the changes in this PR.
I thought I'd point it out though, but I'm happy to looking into it if you'd like.

Oh good spot! I just looked at the latest build and you're absolutely right. Travis is very misleading on the build passing.
If you wouldn't mind looking (it's very kind of you to offer, thank you), that would be great. Shall we do that in a separate PR?
The rest of this PR looks great, thank you.

Yeah that's no problem at all. I can look into it. I'll do that and set up another PR for it to keep it separate from the updates in this PR.
Do you want me to setup an issue for the failing test first? Or directly create a PR for it?
Happy either way, just let me know how you want to do it and I'll get that sorted.

Yeh just do a PR for it. I'll merge this one. Thanks again, @shinobi5. I really appreciate your help.


Update cancel method

Summary
related to #1019
Details and comments
Fixes #

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 4 (75.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.007%) to 73.99%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_runtime/runtime_job.py
3
4
75.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.007%

Covered Lines:
2455

Relevant Lines:
3318

💛  - Coveralls

Closing for now, will reopen when this problem arrises again or we have a better solution


Security Concerns Due to Unmaintained Dependencies

Description
The "wamp-parser-rs" repository relies on the "websocket" crate, which in turn depends on an outdated and unmaintained version (v0.10) of the "hyper" crate. As of now, "hyper" has moved on to v1.0.0-rc.4, and the "websocket" crate remains on an old version.
Additionally, it's worth noting that the "websocket-rs" project, which provides the "websocket" crate, is also unmaintained, adding to the security concerns.
Impact
Using outdated and unmaintained dependencies poses significant security risks. Such dependencies may have unresolved vulnerabilities or lack essential updates and patches to address security issues.
Proposed Solution
Switch to an Alternative WebSocket Implementation: A preferred and effective solution is to migrate to a different WebSocket implementation, such as tokio-tungstenite. Tokio-tungstenite is an actively maintained WebSocket library designed to seamlessly integrate with the Tokio asynchronous runtime. By transitioning to this well-maintained library, you can ensure the long-term security and maintainability of the project while minimizing the effort required to address dependency-related issues.
Advantages of this Solution:

Utilizing a WebSocket library that is actively maintained.
Compatibility with modern Rust async/await patterns and Tokio.
Reduced long-term maintenance overhead.

Considerations:

Carefully plan the migration to ensure that existing code using the "websocket" crate is updated to use "tokio-tungstenite" as smoothly as possible.
Update project documentation and dependencies to reflect the switch to "tokio-tungstenite."

This solution prioritizes adopting a well-maintained WebSocket library to enhance the project's security and sustainability while avoiding the complexities of forking and maintaining an outdated crate.
For more context, please refer to the comment on the original issue highlighting the concerns related to the old dependency and the unmaintained status of the "websocket" crate.

Websocket libraries can be entirely removed from this repo. Websocket functionality is being moved to the other library. Websocket library was available for message conversion from JSON String to Websocket message.

websocket crate and a few other crates were removed completely from the repo. We will not be using tungnstenite in this library, in favor of ezsockets in the Client side library (found https://github.com/ibotva/wamp-client-rs.


Adding P2D or P3D to setup seems to help.
void setup() {
size(1200, 750);  // Size should be the first statement
if (frame != null) {
surface.setResizable(true);
}

void setup() {
size(1200, 750, P3D);  // Size should be the first statement
if (frame != null) {
surface.setResizable(true);
}

I will check that, thank you

Found that rendering problem not exist on gnome flasback (metacity).
I posted next observation but that dissapered.. or i did something wrong.
Using P2D or P3D cause some character problems, using "Delete" not deleting numbers, it add ( ' )-character instead. Using numpad Del works ok (Num lock on). Some NEWT / AWT problem?
I used Finnish keyboard and processing 3.5.4.

Ok in that case i will leave it as is
Input is done through controlp5 library - http://www.sojamo.de/libraries/controlP5/ which is notoriously buggy in this regard. Unfortunately nobody seems to want to invest time to fix it and there is really no other alternative in Processing so it is as it is.


Add support for /v2/events stream

The PR allows to use event stream from Marathon REST API added in v0.9.0

Hmm. This is kinda new and different. Can you add an itest for it?
Also setup.py probably needs to change.

Thank you. Long term, if you need this feature to continue to work as marathon evolves, it needs to have a section in the actual itest code that actually tries to read the events and maybe asserts that there is like, something?
But this technically isn't a blocker to merging.

Hi,
I've added actual itest code. I take some time to make it working on mac, but it works now.

Ok, the last thing to do is to bring it up to pep8 compliance. Check out the flake8 issues in an example travis run: https://travis-ci.org/thefactory/marathon-python/jobs/123588467
Or run tox -e pep8

Tests are failing on marathon waiting timeout.

It looks like the feature isn't really supported till 0.11.0 due to https://github.com/mesosphere/marathon/issues/1926
so I updated tests to run starting from 0.11.0 and above

This looks great to me. Thank you very much for iterating through the tests and pep8 and all the things. Thanks!


Revert edition diff code

We need to revert edition_diff on Action and all code related to creating the diff.
https://trello.com/c/MnNWuuIj/1016-revert-the-diff-work-temporarily

I think there might be something that has broke in the world of end to end (yay)


Make Bolt Python more customizable from global middleware

This pull request applies the following changes to make Bolt Python more customizable from global middleware.

Extract the core part of listener execution from App
Enable kwargs_injection to merge all fields in context into args

In the short term, this is beneficial for Steps from Apps support.
Category (place an x in each of the [ ])

[x] slack_bolt.App and/or its core components
[x] slack_bolt.async_app.AsyncApp and/or its core components
[ ] Adapters in slack_bolt.adapter
[ ] Document pages under /docs
[ ] Others

Requirements (place an x in each [ ])
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've run ./scripts/install_all_and_run_tests.sh after making the changes.

Codecov Report

Merging #103 into main will decrease coverage by 0.08%.
The diff coverage is 82.67%.

@@            Coverage Diff             @@
##             main     #103      +/-   ##
==========================================
- Coverage   90.14%   90.05%   -0.09%
==========================================
  Files         133      135       +2
  Lines        3775     3832      +57
==========================================
+ Hits         3403     3451      +48
- Misses        372      381       +9

Impacted Files
Coverage Δ

slack_bolt/listener_matcher/builtins.py
86.52% <25.00%> (-2.67%)
:arrow_down:

slack_bolt/util/payload_utils.py
98.46% <50.00%> (-1.54%)
:arrow_down:

slack_bolt/app/async_app.py
95.39% <80.00%> (+3.56%)
:arrow_up:

...eware/ignoring_self_events/ignoring_self_events.py
78.26% <80.00%> (ø)

slack_bolt/listener/asyncio_runner.py
82.69% <82.69%> (ø)

slack_bolt/app/app.py
84.79% <83.33%> (+0.05%)
:arrow_up:

slack_bolt/listener/thread_runner.py
86.79% <86.79%> (ø)

slack_bolt/kwargs_injection/async_utils.py
86.95% <100.00%> (+1.95%)
:arrow_up:

slack_bolt/kwargs_injection/utils.py
86.95% <100.00%> (+1.95%)
:arrow_up:

...ignoring_self_events/async_ignoring_self_events.py
83.33% <100.00%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


Filter not functioning

Description
No response
Screenshots
https://github.com/pooranjoyb/popShop/assets/96072228/d1a7a05c-9829-4f1c-9405-d09a9593cc41
Any additional information?
No response
What browser are you seeing the problem on?
No response

Congratulations, @UtkarshBirla28! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work!We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines

hello @pooranjoyb I would like to work on this issue

Go ahead :) @masterboy376

@pooranjoyb Assign it to me please

@pooranjoyb Assign it to me please

Next on the line @UtkarshBirla28


New prow cluster name

/test all

/test all

/lgtm

Force merging, to make the prow configuration working.


Adding missing hubble-stats netlify config

Summary of changes

Adding the missing Netlify config file for the hubble-stats app.

I'm going to merge this PR without waiting for a review, as it simply adds a Netlify config file. We require this to mend the CI for all PRs related to the hubble-stats app. It's a necessary step to ensure everything runs smoothly.


add endpoint flag for beta test

Description of changes:

Add missing endpoint flag to fix beta prow job failures.
Fix regression test error- Useeksctl to scale nodegroup. The test cluster creates unmanaged nodegroups and aws eks does not know about unmanaged nodegroups.

An error occurred (ResourceNotFoundException) when calling the DescribeNodegroup operation: No node group found for name: None.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Could you also manually trigger Manual Integration test workflow against this PR and verify if it works

Could you also manually trigger Manual Integration test workflow against this PR and verify if it works

The integration test did run against the latest changes in this PR.. verified that it has succeeded.

lgtm


Add Ruby 3.0 and 3.1 to the CI matrix

This adds Ruby 3.0 and Ruby 3.1 to the CI matrix.
To get everything green I split out the linting into a separate GitHub Action.  The specified version of Rubocop is not compatible with Ruby 3.1.
Everything runs green on my fork.

Awesome, thanks a lot!


Add keyboard shortcuts in React

Fixes #2246

@frjo Have used ~ctrl~+u and ~ctrl~+d as shortcuts for thumbs up & down respectively. Please let me know if you need any changes


Nixos - ollama - NVIDIA GeForce RTX 3060 Cuda not working

Describe the bug
Bought this GPU specifically because it was listed at the top of the recommended hardware on ollama Tried to enable ollama as well the overall nvidia support, but nothing seems to be picking up the device.
Here is my config: https://github.com/asosnovsky/nixos-setup/blob/main/hosts/hl-bigbox1.nix
Here is my device info
Gigabyte Technology Co., Ltd. B550 GAMING X V2
│
├─AMD Ryzen 5 3600 6-Core Processor:
│ │   Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ │   Current version:    0x08701030
│ │   Vendor:             Advanced Micro Devices, Inc.
│ │   GUIDs:              b54f3c89-8a41-5b9f-9a5c-0367c19a9451 ← CPUID\PRO_0&FAM_17&MOD_71
│ │                       d951a23c-a920-50ac-ad89-0660aa0be95c ← CPUID\PRO_0&FAM_17&MOD_71&STP_0
│ │   Device Flags:       • Internal device
│ │
├─GA106 [GeForce RTX 3060 Lite Hash Rate]:
│     Device ID:          08740947f5235290dc47990eb8e3468dad7fe6b8
│     Current version:    a1
│     Vendor:             NVIDIA Corporation (PCI:0x10DE, PCI:0x1022)
│     GUIDs:              2954a00b-f08f-56ad-81f7-7e22bedfdfc7 ← PCI\VEN_10DE&DEV_2504
│                         533f2b03-1243-530c-a168-9706751fc035 ← PCI\VEN_10DE&DEV_2504&SUBSYS_1462397D
│                         2d530482-50db-5cbc-97f7-6ae02507276d ← PCI\VEN_1022&DEV_1483
│                         0b05f0c1-7f0b-59e0-adb4-0e58b9b6e7e3 ← PCI\VEN_1022&DEV_1483&SUBSYS_10221453
│     Device Flags:       • Internal device
│                         • Cryptographic hash verification is available
│
├─TPM:
│     Device ID:          c6a80ac3a22083423992a3cb15018989f37834d6
│     Summary:            TPM 2.0 Device
│     Current version:    <IP_ADDRESS>
│     Vendor:             Advanced Micro Devices, Inc. (TPM:AMD)
│     GUIDs:              9305de1c-1e12-5665-81c4-37f8e51219b8 ← TPM\VEN_AMD&DEV_0001
│                         78a291ae-b499-5b0f-8f1d-74e1fefd0b1c ← TPM\VEN_AMD&MOD_AMD
│                         65a3fced-b423-563f-8098-bf5c329fc063 ← TPM\VEN_AMD&DEV_0001&VER_2.0
│                         5e704f0d-83cb-5364-8384-f46d725a23b8 ← TPM\VEN_AMD&MOD_AMD&VER_2.0
│     Device Flags:       • Internal device
│                         • System requires external power source
│                         • Needs a reboot after installation
│                         • Device can recover flash failures
│                         • Full disk encryption secrets may be invalidated when updating
│                         • Signed Payload
│
└─WD BLACK SN770 250GB:
      Device ID:          71b677ca0f1bc2c5b804fa1d59e52064ce589293
      Summary:            NVM Express solid state drive
      Current version:    731030WD
      Vendor:             Sandisk Corp (NVME:0x15B7)
      Serial Number:      22196Y802128
      GUIDs:              1524d43d-ed91-5130-8cb6-8b8478508bae ← NVME\VEN_15B7&DEV_5017
                          87cfda90-ce08-52c3-9bb5-0e0718b7e57e ← NVME\VEN_15B7&DEV_5017&SUBSYS_15B75017
                          36698e2e-ae33-573d-a6c0-798393b361ef ← WD_BLACK SN770 250GB
      Device Flags:       • Internal device
                          • Updatable
                          • System requires external power source
                          • Needs a reboot after installation
                          • Device is usable for the duration of the update

Here is my nix info
Steps To Reproduce
  services.ollama = {
    enable = true;
    acceleration = "cuda";
    listenAddress = "<IP_ADDRESS>:11434";
    environmentVariables = {
      OLLAMA_LLM_LIBRARY = "cuda";
    };
  };

Screenshots
Ollama serve logs from systemctl
time=2024-07-13T16:44:09.180-04:00 level=INFO source=routes.go:1054 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.38)"
time=2024-07-13T16:44:09.180-04:00 level=INFO source=payload.go:30 msg="extracting embedded files" dir=/run/user/1000/ollama2290230408/runners
time=2024-07-13T16:44:13.920-04:00 level=INFO source=payload.go:44 msg="Dynamic LLM libraries [cpu cpu_avx cpu_avx2 cuda_v12]"
time=2024-07-13T16:44:13.963-04:00 level=INFO source=types.go:71 msg="inference compute" id=0 library=cpu compute="" driver=0.0 name="" total="31.3 GiB" available="5.9 GiB"

and while running ollama run llama3:8b
root@hl-bigbox1:/home/ari/nixos-setup/ > ollama ps
NAME            ID              SIZE    PROCESSOR       UNTIL
llama3:8b       365c0bd3c000    4.9 GB  100% CPU        4 minutes from now

Metadata

system: "x86_64-linux"
host os: Linux 6.9.6, NixOS, 24.05 (Uakari), 24.05.20240624.fc07dc3
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.18.2
nixpkgs: /nix/store/r5clili0iqprbn4dnngkywsgxm51a5cw-source

Jul 14 01:50:26 Nix ollama[1087239]: time=2024-07-14T01:50:26.372+03:00 level=INFO source=payload.go:44 msg="Dynamic LLM libraries [cpu cpu_avx cpu_avx2 cuda_v12]"
Jul 14 01:50:26 Nix ollama[1087239]: time=2024-07-14T01:50:26.473+03:00 level=INFO source=types.go:98 msg="inference compute" id=GPU-0a730a3d-f915-32f2-19e0-bef38f6809b4 library=cuda compute=8.6 driver=12.5 name="NVIDIA GeForce RTX 3090" total="23.8 GiB" available="22.3 GiB"

Try change settings to something like that:

    environmentVariables = {
      OLLAMA_LLM_LIBRARY = "cuda";
      LD_LIBRARY_PATH = "run/opengl-driver/lib";
    };

@VeilSilence are you on unstable or nixos-24?

Unstable.
В Вс, июля 14, 2024 в 02:09, Ari Sosnovsky @.***(mailto:В Вс, июля 14, 2024 в 02:09, Ari Sosnovsky < написал(а):

@.***(https://github.com/VeilSilence) are you on unstable or nixos-24?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@VeilSilence just switched my configs to use unstable still the same.. :(
mind sharing your configs?

Maybe you should try setting services.xserver.videoDrivers = ["nvidia"];? It seems to influence services.xserver.drivers, which could potentially be read by other nixos modules even if you don't use xserver.
Have you tried a minimal ollama config with just the following? Maybe host or one of the env vars is actually interfering?
services.ollama = {
  enable = true;
  acceleration = "cuda";
};

Also, if you just want to use unstable ollama I would recommend the following with a base of stable nixos-24.05, where unstable is imported from a separate nixpkgs-unstable flake input:
services.ollama = {
  enable = true;
  acceleration = "cuda";
  package = unstable.ollama;
};

Also, are you aware that your enableNetowrking option is misspelled with the wo swapped to ow? As is homeMangerVersion, with the nag dropping the a to ng.

@abysssol thank you for catching those (embarassing)
I figured the issue... I never removed the old gpu I had on this (just removed the power from it). Looks like properly taking it out fixed my issues.

@asosnovsky
@abysssol
I have a RTX 3060 aswell and Ollama isn't using my GPU but it is being detected!
My config:
    ollama = {
      enable = true;
      acceleration = "cuda";
      environmentVariables = {
        OLLAMA_LLM_LIBRARY = "cuda";
        LD_LIBRARY_PATH = "run/opengl-driver/lib";
      };
    };

I am getting the same 100% CPU log from Ollama as at the top of this issue,
Journalctl logs:
Jul 10 09:43:05 nixos ollama[1989]: time=2024-07-10T09:43:05.270+10:00 level=INFO source=routes.go:1111 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.47)"
Jul 10 09:43:05 nixos ollama[1989]: time=2024-07-10T09:43:05.271+10:00 level=INFO source=payload.go:30 msg="extracting embedded files" dir=/tmp/ollama3450513807/runners
Jul 10 09:43:09 nixos ollama[1989]: time=2024-07-10T09:43:09.081+10:00 level=INFO source=payload.go:44 msg="Dynamic LLM libraries [cuda_v12 cpu cpu_avx cpu_avx2]"
Jul 10 09:43:09 nixos ollama[1989]: time=2024-07-10T09:43:09.148+10:00 level=INFO source=types.go:98 msg="inference compute" id=GPU-6814f4a1-a623-257e-fdcf-1da7dbff1e59 library=cuda compute=8.6 driver=12.2 name="NVIDIA GeForce RTX 3060" total="11.8 GiB" available="11.6 GiB"

@asosnovsky
@abysssol
I have a RTX 3060 aswell and Ollama isn't using my GPU but it is being detected!
I don't have any other GPU's and the iGPU of my CPU (Intel i5-12600) is disabled in the BIOS.
My config:

    ollama = {

      enable = true;

      acceleration = "cuda";

      environmentVariables = {

        OLLAMA_LLM_LIBRARY = "cuda";

        LD_LIBRARY_PATH = "run/opengl-driver/lib";

      };

    };

I am getting the same 100% CPU log from Ollama as at the top of this issue,
Journalctl logs:

Jul 10 09:43:05 nixos ollama[1989]: time=2024-07-10T09:43:05.270+10:00 level=INFO source=routes.go:1111 msg="Listening on <IP_ADDRESS>:11434 (version 0.1.47)"

Jul 10 09:43:05 nixos ollama[1989]: time=2024-07-10T09:43:05.271+10:00 level=INFO source=payload.go:30 msg="extracting embedded files" dir=/tmp/ollama3450513807/runners

Jul 10 09:43:09 nixos ollama[1989]: time=2024-07-10T09:43:09.081+10:00 level=INFO source=payload.go:44 msg="Dynamic LLM libraries [cuda_v12 cpu cpu_avx cpu_avx2]"

Jul 10 09:43:09 nixos ollama[1989]: time=2024-07-10T09:43:09.148+10:00 level=INFO source=types.go:98 msg="inference compute" id=GPU-6814f4a1-a623-257e-fdcf-1da7dbff1e59 library=cuda compute=8.6 driver=12.2 name="NVIDIA GeForce RTX 3060" total="11.8 GiB" available="11.6 GiB"

Honestly after I did another nix flake update about a week ago, this stopped working for me again. I think because ollama is still niche, it could be that the developer working on this has not had the proper time to support it well. I manage to get this working properly by doing a pass through with nvidia to docker (which is more widely used and supported) and then spinning up ollama with an official docker image.
See my container config https://github.com/asosnovsky/nixos-setup/blob/753f21b3fe95b5d0259c37a5186900fd19bfa5c1/hosts/hl-bigbox1.nix#L18
And docket nvidia pass through https://github.com/asosnovsky/nixos-setup/blob/753f21b3fe95b5d0259c37a5186900fd19bfa5c1/hosts/hl-bigbox1.nix#L6

Thanks @asosnovsky
I'll give that docker container setup a try!

Thanks @asosnovsky
I'll give that docker container setup a try!
Edit:
Works perfectly thank you, I just had to reinstall my models with docker exec ollama ollama pull my-model

You can install the ollama cli via pkgs.ollama and set the OLLAMA_HOST env to point at the container. That way you can manage it with the standard cli tool (or any gui)


[ptp4u] use leapsectz lib to determine leapsecond

Summary
Option to use leapsectz lib

Test Plan
$ /usr/local/bin/ptp4u -workers 200 -timestamptype hardware -loglevel error -leapsectz

Codecov Report

Merging #89 (0506050) into main (7f3444f) will increase coverage by 0.00%.
The diff coverage is 52.63%.

@@           Coverage Diff           @@
##             main      #89   +/-   ##
=======================================
  Coverage   56.27%   56.28%
=======================================
  Files          63       63
  Lines        4759     4776   +17
=======================================
+ Hits         2678     2688   +10
- Misses       1759     1764    +5
- Partials      322      324    +2

Impacted Files
Coverage Δ

ptp/ptp4u/server/server.go
31.01% <0.00%> (-0.44%)
:arrow_down:

ptp/ptp4u/server/config.go
70.83% <66.66%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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


The code in some.C files is all grey

Issue Type
Bug
Description
The code in the ST Hal library .C file is all grey
VS Code Info
VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 10.0.16299

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

Memory (System)
7.70GB (3.54GB free)

Process Argv
C:\APP\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Extensions (12)

Extension
Author (truncated)
Version

code-gnu-global
aus
0.2.2

aio-compiler
azt
1.0.2

GBKtoUTF8
buk
0.0.2

npm-intellisense
chr
1.3.0

vscode-markdownlint
Dav
0.13.0

vscode-npm-script
eg2
0.3.3

prettier-vscode
esb
1.1.3

CppSnippets
har
0.0.13

vscode-cdecl
kae
1.0.0

vscode-clang
mit
0.2.2

cpptools
ms-
0.15.0

team
ms-
1.122.0

(6 theme extensions excluded)

Reproduces only with extensions

Closing this as out of date. It seems to have magically popped into our issues.
If you are still effected by this, please open a new issue


EF Core 2.2 DbContext Properties "missing"

I could not find a topic like that in here, if there is, sorry for that.
Here we go, On prev version like EF 6.0 we had the possibility to set a default column type
like:   //General Custom Context Properties
builder.Properties()
.Configure(p => p.HasColumnType("nvarchar"));
and this would be applied for all fields of type string, where I can't find a similar way for Ef core
same for those options here:
modelBuilder.Conventions.Remove();
modelBuilder.Conventions.Remove();
modelBuilder.Conventions.Remove();
modelBuilder.Conventions.Remove();
for now on what is the recommendation to try to get the same behavior in EF core 2/3.0?

@douglassimaodev Basically, you can iterate over the model at the end of OnModelCreating and bulk set facets like this. There are some examples in #6787.


Add Lars router

Hello! Will be great if you can add https://github.com/go-playground/lars to the next round. Thanks!

Tests are already implemented and the results will be included in the next round. You can run the benchmark on your own if desired.


[Docs] Fix barplot

What does this PR do?
This PR replaces the previous plot of toxicity example with a nice TRL-themed barplot
cc @lvwerra

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[AERIE-1715]  Typescript evaluation in scheduler-server

Tickets addressed: AERIE-1715
Review: By commit
Merge strategy: Merge (no squash)

Description
This PR adds Nashorn as a dependency to scheduler-server, and adds a SchedulerDSLCompilationService. Note that here I'm using the word "Compilation" to mean "Compilation of Typescript to Javascript, followed by execution of Javascript to produce JSON, followed by parsing of JSON".
The flow is as follows:

Typescript program is provided as a string
The program string is prepended with a preface, and followed by an epilogue
This combined string is saved to a temporary file
tsc (the typescript compiler) is run on this temporary file, producing another temporary file
The newly generated file is read in as a string
This string is executed in Nashorn
The epilogue contains a "JSON.stringify()" of the result, so we get back a serialized JSON string
This string is run through a JSON parser that we define, the same way we define all of our JSON parsers.

I tried and failed to get a standalone tsc js file that successfully runs under Nashorn. Rather than let that be a blocker, I've gone ahead and installed the typescript compiler in the scheduler-server docker container.
Currently, it is assumed that the scheduling goal defines a goal() function that returns a particular type. This is in part because I could not figure out how to get modules to work.
Verification
I added some unit tests as I went, feel free to check those out and execute them.

Note to run the tests, you'll need to have tsc on your path. I did this by running npm install --global typescript
I toyed with using gradle-node-plugin to install typescript for testing purposes, but again, I didn't want to spend all day figuring that out. Any suggestions are welcome!

Documentation

I'm not aware of any documentation that this would directly affect - perhaps it will deserve mention in our general scheduling EDSL documentation when we get around to writing that.
Future work
The goal of this PR was to establish the workflow. Next steps are to expand the EDSL definition, provide an actual library, and write a parser that corresponds to that library.

If we need node for the typescript compiler, why not just run the whole thing in node and remove the additional Nashorn dependency?

If we need node for the typescript compiler, why not just run the whole typescript to ast in node and remove the additional Nashorn dependency?

That's a good point - I'll prototype that option and see how we feel about maintaining this functionality in typescript :+1: (one advantage is it will be very similar to command expansion that way)

Additionally, we should try to find a way that leaves the typescript compiler running so we don't have to release everything each compilation

That's certainly on the table as we consider performance optimizations. In the first cut I think I'd rather just start it up from scratch every time for simplicity's sake.
Regardless of which approach we settle on for this initial version, my main goal with this PR is to "connect the dots" across our end-to-end workflow. To that end, what I think is most important for us to iron out over the next week or two is the details of the SchedulingGoalDSLCompilationService, which right now is just this method:
https://github.com/NASA-AMMOS/aerie/blob/dde5bf8ada5a4ce279a68612ba0331b0744cb3f0/scheduler-server/src/main/java/gov/nasa/jpl/aerie/scheduler/server/services/SchedulingGoalDSLCompilationService.java#L24
The GoalDefinition in particular will need to expand to encompass a usable subset of the AST definition, and the schedulingJsonP parser will need to be updated accordingly. We'll also eventually need to make activity type information available somehow.

I’ll take a look/poke at the PR and might do a branch off it to propose some changes addressing some of this.
On Feb 25, 2022, at 08:25, Matt Dailis @.***> wrote:

If we need node for the typescript compiler, why not just run the whole typescript to ast in node and remove the additional Nashorn dependency?
That's a good point - I'll prototype that option and see how we feel about maintaining this functionality in typescript 👍 (one advantage is it will be very similar to command expansion that way)
Additionally, we should try to find a way that leaves the typescript compiler running so we don't have to release everything each compilation
That's certainly on the table as we consider performance optimizations. In the first cut I think I'd rather just start it up from scratch every time for simplicity's sake.
Regardless of which approach we settle on for this initial version, my main goal with this PR is to "connect the dots" across our end-to-end workflow. To that end, what I think is most important for us to iron out over the next week or two is the details of the SchedulingGoalDSLCompilationService, which right now is just this method:
https://github.com/NASA-AMMOS/aerie/blob/dde5bf8ada5a4ce279a68612ba0331b0744cb3f0/scheduler-server/src/main/java/gov/nasa/jpl/aerie/scheduler/server/services/SchedulingGoalDSLCompilationService.java#L24https://urldefense.us/v3/__https://github.com/NASA-AMMOS/aerie/blob/dde5bf8ada5a4ce279a68612ba0331b0744cb3f0/scheduler-server/src/main/java/gov/nasa/jpl/aerie/scheduler/server/services/SchedulingGoalDSLCompilationService.java*L24__;Iw!!PvBDto6Hs4WbVuu7!ftIDug_fpywCsv3jLiQssG7A4prE2iYCd_OEScmAqQP78KGvN0sCji4S8KI7WICbDRW6cp3_aS-h$
The GoalDefinition in particular will need to expand to encompass a usable subset of the AST definition, and the schedulingJsonP parser will need to be updated accordingly. We'll also eventually need to make activity type information available somehow.
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/NASA-AMMOS/aerie/pull/63*issuecomment-1051000052__;Iw!!PvBDto6Hs4WbVuu7!ftIDug_fpywCsv3jLiQssG7A4prE2iYCd_OEScmAqQP78KGvN0sCji4S8KI7WICbDRW6cj0w8Sf0$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/ADFK2Q55NS4JS75QTL6L5O3U46UPRANCNFSM5PI55LXQ__;!!PvBDto6Hs4WbVuu7!ftIDug_fpywCsv3jLiQssG7A4prE2iYCd_OEScmAqQP78KGvN0sCji4S8KI7WICbDRW6cqMfYAF1$.
You are receiving this because you commented.Message ID: @.***>

I’ll take a look/poke at the PR and might do a branch off it to propose some changes addressing some of this

Sounds good :+1: In my last couple commits, I took a step in that direction by adding a node script that just calls the compiler (twice, because I couldn't figure out how to output error messages from transpileSource). Feel free to start with that, if you find that's a reasonable starting point.

Yeah. Do the tests you’ve written cover the calling of the node stuff? If so, I might also play with setting it up as a multiple-call service where we just spit the scheduling script into stdin and snag the ast from stdout to cover the performance initially.
Sent from my iPhone
On Feb 25, 2022, at 12:06, Matt Dailis @.***> wrote:

I’ll take a look/poke at the PR and might do a branch off it to propose some changes addressing some of this
Sounds good 👍 In my last couple commits, I took a step in that direction by adding a node script that just calls the compiler (twice, because I couldn't figure out how to output error messages from transpileSource). Feel free to start with that, if you find that's a reasonable starting point.
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https://github.com/NASA-AMMOS/aerie/pull/63*issuecomment-1051188241__;Iw!!PvBDto6Hs4WbVuu7!cKbxHywlOZ9XzmYJ7-GgiD6VfQskrPWeiRyFtz5VeVr1scatFz3BTxILOcjkbSqSIwTSAiGpWwyq$, or unsubscribehttps://urldefense.us/v3/__https://github.com/notifications/unsubscribe-auth/ADFK2QYAE52XSGUULSVRE5TU47OLBANCNFSM5PI55LXQ__;!!PvBDto6Hs4WbVuu7!cKbxHywlOZ9XzmYJ7-GgiD6VfQskrPWeiRyFtz5VeVr1scatFz3BTxILOcjkbSqSIwTSAi0r236R$.
You are receiving this because you commented.Message ID: @.***>

Yeah. Do the tests you’ve written cover the calling of the node stuff? If so, I might also play with setting it up as a multiple-call service where we just spit the scheduling script into stdin and snag the ast from stdout to cover the performance initially.

Yup - I slotted the node call into the same place I called tsc from before:
https://github.com/NASA-AMMOS/aerie/blob/b19a8505e48030f811835770db23540d4eed4baf/scheduler-server/src/main/java/gov/nasa/jpl/aerie/scheduler/server/services/TypescriptExecutionService.java#L70-L73
So main.ts expects to be called like this:
node main.js INFILE.ts --outfile OUTFILE.js

At the moment it's still running the javascript in nashorn. main.ts is just a thin wrapper around ts.transpileModule.
The tests will use your local node install, if it's on the PATH. If it's not on the PATH, gradle will install its own node executable in scheduler-server/.gradle/nodejs/node-v14.15.4-darwin-x64/bin/node.
Realizing as I write this that I should probably force gradle to grab node 16 instead.


Replace "Sign up" button for "Subscribe"

Describe the bug
We subscribe to a newsletter not Sign up
Expected behavior
More professional approach
Screenshots
Location: Footer

Have you read the Code of Conduct?
yes,
Kindly assign this issue to me.

This isn't a bug and its as per the expectation.


fix: Prevent "Connection closed" errors when deleting the session for @wdio/cucumber-framework

Proposed Changes
This fixes #115.
Validation
Since we don't have Cucumber set up in this repo I used seanpoulter/wdio-vscode-cucumber-example:
$ cd .../wdio-vscode-service
$ npm link
$ npm run build

$ cd .../wdio-vscode-cucumber-example
$ npm link wdio-vscode-service

$ npm run test

> test
> wdio run ./test/wdio.conf.ts

Execution of 1 workers started at 2024-02-27T01:45:04.115Z

Skipping download, bundle for ChromeDriver v27.2.3 already exists
Found existing install in .../.wdio-vscode-service/vscode-linux-arm64-1.86.2. Skipping download
[0-0] RUNNING in chrome - file:///test/features/webview.feature
[0-0] PASSED in chrome - file:///test/features/webview.feature

 "spec" Reporter:
------------------------------------------------------------------
[chrome 118.0.5993.159 linux #0-0] Running: chrome (v118.0.5993.159) on linux
[chrome 118.0.5993.159 linux #0-0] Session ID: 90871adafb5727ca052e30dc884ec9e9
[chrome 118.0.5993.159 linux #0-0]
[chrome 118.0.5993.159 linux #0-0] » /test/features/webview.feature
[chrome 118.0.5993.159 linux #0-0] Hello World
[chrome 118.0.5993.159 linux #0-0] As an extension developer
[chrome 118.0.5993.159 linux #0-0] I want to test if a Webview is displayed
[chrome 118.0.5993.159 linux #0-0]
[chrome 118.0.5993.159 linux #0-0] Webview Shows "Hello World!"
[chrome 118.0.5993.159 linux #0-0]    ✓ When I open the Webview
[chrome 118.0.5993.159 linux #0-0]    ✓ Then I expect that "Hello World!" is displayed
[chrome 118.0.5993.159 linux #0-0]
[chrome 118.0.5993.159 linux #0-0] 2 passing (3.2s)

Spec Files:      1 passed, 1 total (100% completed) in 00:00:10

:tada:

I am a bit confused as to why Cucumber behaves differently here.

Me too. There wasn't anything obvious comparing the run method for the Mocha and Cucumber frameworks. As a hunch, it seems like Mocha is either not making request after the test case, or it's hiding the rejected promise.


cannot find package "github.com/gernest/utron/app"

I use win 10 x64, and get error
cannot find package "github.com/gernest/utron/app" in any of:
C:\Go\src\github.com\gernest\utron\app (from $GOROOT)
C:\Users\HieuLuong\go\src\github.com\gernest\utron\app (from $GOPATH)

@lchhieu  try to reinstall utron like this
 go get -v -u github.com/gernest/utron/...
I don't know why you are seeing such an error but that command should help!

Just a reminder sample applications can be found here https://github.com/utronframework

@gernest i had try again and success

Cool! I'm closing this issue then. You can reopen if it still persists.


packages.elm-lang is down

Just an FYI. But it seems like a runtime error has taken down the package view of packages.elm-lang.
Port Error:

    Regarding the port named 'context' with type:

        Page.Package.Context

    You just sent the value:

        {"user":"elm-lang","project":"core","version":"3.0.0","allVersions":["3.0.0","2.1.0","2.0.1","2.0.0","1.1.1","1.1.0","1.0.0"],"moduleName":null}

    but it cannot be converted to the necessary type.
    Runtime error when sending values through a port.
    Expecting an object with fields `user`, `name`, `version`, `versionList` but was given
    {"user":"elm-lang","project":"core","version":"3.0.0","allVersions":["3.0.0","2.1.0","2.0.1","2.0.0","1.1.1","1.1.0","1.0.0"],"moduleName":null}

Open the developer console for more details.

It's a caching issue, it should be fixed if you do a hard refresh. Please reopen if that's not the issue!

It is indeed fixed now, love the new look!
Also I have a trick to overcome cashing issues you may like. In the html build step, you can put a uuid fingerprint on the .js and .css files. That way changes to those files don't yield caching issues for browsers, because the browser sees all updates as an entirely new file. So...
<script src="/artifacts/Page-Package-cb2d7259-33c4-4ba4-93bd-a083e5274612.js"></script>

or even
<script src="/artifacts/Page-Package.js?_=cb2d7259-33c4-4ba4-93bd-a083e5274612"></script>

Thanks, glad you like it!
I know, but I'm not sure how to add this into snap in a nice way. It's one of the things that I'd like to do better, but I can't actually focus on it too much ever :/


Show liveness in 'node list' command

I have a cluster of 4 nodes, 2 in EU and 2 in US.
I recently suffered a split brain.
When I ran jobs with --target=all only the 2 nodes in the EU were sent work.
bacalhau node list showed all 4 nodes.
It would be useful when investigating this situation, to determine when a particular node last contacted the requester.
If dead nodes are expected to stay in the node list, it would also be good if they were somehow shown as dead/unresponsive.

We now have connected and disconnected states
https://github.com/bacalhau-project/bacalhau/pull/3709


Create new Mobility section and redirect existing docs into it

Closes #180.

Confirmed, the "Edit this page" links in our renamed files are broken. :(
Sample 404s
https://precog.mapzen.com/mapzen/mapzen-docs-generator/rhonda-new-mobility/documentation/mobility/optimized/api-reference/
-->
https://github.com/valhalla/valhalla-docs/tree/master/optimized/api-reference.md
--> correct location (optimized_route)
https://github.com/valhalla/valhalla-docs/blob/master/optimized_route/api-reference.md
https://precog.mapzen.com/mapzen/mapzen-docs-generator/rhonda-new-mobility/documentation/mobility/turn-by-turn/api-reference/
-->
https://github.com/valhalla/valhalla-docs/tree/master/turn-by-turn/api-reference.md
--> correct location (no turn-by-turn)
https://github.com/valhalla/valhalla-docs/tree/master/api-reference.md

Cheap and easy fix: link to the top of the documentation section on Github and let people figure out what to edit.
Harder fix: track the files we are renaming and ensure the links go to the right places.

I think I’ve fixed this. The only new twist is that mz:renames now must use filenames instead of directory names, so that the renaming can be found in the template.

Hooray, looks good so far...will do some testing.

New thing...@kkowalsky found that images are broken links. The only topic with images is documentation/mobility/turn-by-turn/add-routing-to-a-map/, but I'd assume it'd be a problem with any of them.
Broken link example:
documentation/mobility/turn-by-turn/images/browser-controls.png
I'm not yet sure where the images actually live...still looking.

Remaining items are content-related and will be done in the valhalla-docs repository.


Cocaine::ExitStatusError?

This is what I'm getting when trying this library
Cocaine::ExitStatusError: Command '/Users/usercore/.rvm/gems/ruby-2.2.2/bin/youtube-dl --no-color --output 'some_file.mp4' "https://www.youtube.com/watch?v=gvdf5n-zI14"' returned 1. Expected 0

Turns out it was a conflict with a previous gem I had installed called youtube_dl. Lol

Yeahh.... If youtube-dl.rb (this gem) finds a youtube-dl in the system $PATH then it assumes that's the youtube-dl executable to use. Thanks for bringing my attention to the gem conflict though!

Thanks for your work on the gem!


Feature: Query and paste from the clipboard

While most terminal emulates don't support reading from the clipboard, there is growing support for this feature – the next release of iTerm (3.5) will allow for querying the clipboard.
It'd be nice to support pasting for those who use a terminal emulator that supports querying the clipboard via OSC 52!

I will definitely look into it :) I don't have time this week and the next but after I should be able to work on this.

Hey @ojroques, thanks for working on this! I don't want to bring bad news but it's unlikely going to work. The Foot terminal on Linux supports OSC-52 for copying/pasting. I tried this patch and it didn't work for me. It actually makes sense because according to OSC-52, the terminal returns base64-encoded clipboard content surrounded by OSC-52 escape codes, and it's up to the caller to unescape and decode the data.
You can check how it's supposed to work in this script there → https://github.com/rumpelsepp/oscclip/blob/master/oscclip/init.py. I tried the script and it worked well for me.
Now I wonder, is this even possible to work with /dev/tty from Lua API? Can the file descriptor for that device be changed to be non-blocking? :thinking:

Thanks for the info! I'll check how it can be implemented in the plugin when I have time. Probably not anytime soon though.

Sadly, I'm fairly certain that pasting can't be implemented as a simple plugin.
Standard Lua has no facilities for non-blocking file I/O and changing the terminal mode, so this would require binding to a C library or patching neovim for these parts.

JFYI, native OSC-52 support has been landed to NeoVim master branch. :partying_face:
https://github.com/neovim/neovim/pull/25872

That's great news! I updated the README with a disclaimer.


When the Keyboard is dismissed, the TextField content is cleared

The question title is very self explanatory, after the user type in the textfield and dismiss the keyboard, the content of the TextField is cleared.
I tried do transform the screen in a Stateful widget, but the problem persists.
Bellow is my code, the log that appears when the keyboard is dismissed and the Flutter Doctor.
The error itself

My Code
[Stateful backclass default ommited]
class _EditNoteScreenState extends State<EditNoteScreen>{

  _EditNoteScreenState(String day, String title, String note){
    this.day = day;
    this.title = title;
    this.note = note;
  }

  String day, title, note;

  @override
  Widget build(BuildContext context) {
    var noteController = TextEditingController();
    var titleController = TextEditingController();
    titleController.text = ( title == " ") ? null : title;
    noteController.text = (note == " ") ? null : note;

    var noteNode = FocusNode();
    var titleNode = FocusNode();

    _saveNote() {
      DBProvider.db.addNote(day, titleController.text, noteController.text);
      print("DAY " + day);
      Navigator.pop(context);
    }

    return Scaffold(
        body:SingleChildScrollView(
              child: Padding(
                padding: const EdgeInsets.only(top:20.0, left:8.0),
                child: Column(
                  children: <Widget>[
                    Container(
                      margin: const EdgeInsets.only(top: 18, left: 18, right: 18),
                      child: TextField(
                        controller: titleController,
                        focusNode: titleNode,
                        autofocus: true,
                        onEditingComplete: () {
                          FocusScope.of(context).requestFocus(noteNode);
                        },
                        style: TextStyle(fontWeight: FontWeight.bold, fontSize: 22),
                        decoration: InputDecoration(border: InputBorder.none, hintText: "Título"),
                      ),
                    ),
                    Container(
                      margin: new EdgeInsets.only(left: 18, right: 8),
                      child: TextField(
                        controller: noteController,
                        focusNode: noteNode,
                        maxLines: 10,
                        style: TextStyle(fontSize: 18),
                        decoration: InputDecoration(border: InputBorder.none, hintText: "Corpo da nota"),
                      ),
                    ),
                    Padding(
                      padding: const EdgeInsets.only(right: 16.0, top: 8),
                      child: Row(
                        mainAxisAlignment: MainAxisAlignment.end,
                        children: <Widget>[
                          Flexible(
                            child: RaisedButton.icon(
                              color: primary_yellow,
                              onPressed: () {
                                _saveNote();
                              },
                              label: Text("Registrar Nota"),
                              icon: Icon(
                                Icons.edit,
                                color: pretty_black,
                              ),
                              shape: new RoundedRectangleBorder(
                                  borderRadius: new BorderRadius.circular(30)),
                            ),
                          ),
                        ],
                      ),
                    )
                  ],
                ),
              ),
            ));
  }
}

Logs
[+7694 ms] W/IInputConnectionWrapper( 3164): getTextBeforeCursor on inactive InputConnection
[   +1 ms] W/IInputConnectionWrapper( 3164): getSelectedText on inactive InputConnection
[   +1 ms] W/IInputConnectionWrapper( 3164): getTextAfterCursor on inactive InputConnection

[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [versÃ£o 10.0.17763.529], locale pt-BR)
    • Flutter version 1.2.1 at C:\res\flutter
    • Framework revision 8661d8aecd (3 months ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\muril\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.4)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 35.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[√] Connected device (1 available)
    • Moto G 5S •<PHONE_NUMBER> • android-arm • Android 8.1.0 (API 27)

• No issues found!

Put your TextEditingController() and FocusNode() outside the build(...) function.
This is an issue with your code and not Flutter.

When you dismiss the keyboard, build(...) gets rebuilt. Thus your controllers too. Therefore you have to put it outside your build(...) functions. A state widget does not maintain the variables in the build(...) function, only variables outside it!

When you dismiss the keyboard, build(...) gets rebuilt. Thus your controllers too and your text gets removed. Therefore you have to put it outside your build(...) functions. A State widget does not maintain the variables in the build(...) function, only variables outside


Long running docker instance has many CLOSE_WAIT and can't idetify protocol fds

Description

Steps to reproduce the issue:

Deploy many containers
When some process are in some unkillable states
Kill these containers

Describe the results you received:
Request timed out, and docker cannot release its net socket fd.
docker  8925 root  337u  sock                0,8      0t0   47494363 can't identify protocol
docker  8925 root  338u  sock                0,8      0t0   47478892 can't identify protocol
docker  8925 root  339u  sock                0,8      0t0   47465307 can't identify protocol
docker  8925 root  340u  sock                0,8      0t0   47494388 can't identify protocol
docker  8925 root  341u  sock                0,8      0t0   47450385 can't identify protocol
docker  8925 root  342u  sock                0,8      0t0   47490649 can't identify protocol
docker  8925 root  343u  sock                0,8      0t0   47487617 can't identify protocol
docker  8925 root  344u  sock                0,8      0t0   47465420 can't identify protocol
...
docker  8925 root *027u  IPv6           57864376      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:56546 (CLOSE_WAIT)
docker  8925 root *028u  IPv6           57859473      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:51419 (CLOSE_WAIT)
docker  8925 root *029u  IPv6           57867780      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:51420 (CLOSE_WAIT)
docker  8925 root *030u  IPv6           57874562      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:56126 (CLOSE_WAIT)
docker  8925 root *031u  IPv6           57865892      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:56127 (CLOSE_WAIT)
docker  8925 root *032u  IPv6           57864402      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:10664 (CLOSE_WAIT)
docker  8925 root *033u  IPv6           57864403      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:10663 (CLOSE_WAIT)
docker  8925 root *034u  IPv6           57874659      0t0        TCP <IP_ADDRESS>:4444-><IP_ADDRESS>:35490 (CLOSE_WAIT)
...

Describe the results you expected:
Request timed out, docker can release its net socket fd.
Additional information you deem important (e.g. issue happens only occasionally):
Some user processes are in brackets in ps, e.g.:
# ps -opid,command --pid 506188
    PID COMMAND
 506188 [sh]

Output of docker version:
# docker version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.4
 Git commit:   20f81dd-unsupported
 Built:        Mon Apr 25 00:23:10 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.4
 Git commit:   20f81dd-unsupported
 Built:        Mon Apr 25 00:23:10 2016
 OS/Arch:      linux/amd64

Output of docker info:
# docker info
Containers: 20
 Running: 20
 Paused: 0
 Stopped: 0
Images: 70
Server Version: 1.10.3
Storage Driver: aufs
 Root Dir: /disk1/docker/lib/aufs
 Backing Filesystem: extfs
 Dirs: 537
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: host null
Kernel Version: 4.2.0-27-generic
Operating System: Ubuntu 14.04.5 LTS
OSType: linux
Architecture: x86_64
CPUs: 48
Total Memory: 251.8 GiB
Name: nqgpu4
ID: CYIF:THAJ:LDC2:3O6Z:WK4Z:IO7Q:FCN2:PSZE:JVMC:2E2T:GZ2O:UVUO
WARNING: No swap limit support

Additional environment details (AWS, VirtualBox, physical, etc.):
physical

Docker 1.10 is quite old now, and no longer maintained; also, your seem to be running a custom build of an unofficial package (20f81dd-unsupported); if you have a system to test on, could you try if you're still able to reproduce this on the current release?

Also, what kind of processes are running in your container? There was a bug in aufs that caused some JAVA processes to get stuck; that issue is resolved in newer kernel versions, see https://github.com/docker/docker/issues/18180#issuecomment-193708192

@thaJeztah
Yes, these stuck processes are JAVA programs. If there is no workaround, we plan to upgrade docker & linux kernel.
Which linux lts version you suggest in production?

You probably don't have to upgrade ubuntu, just the kernel. But if you're planning on updating, Ubuntu 16.04 is more up to date, and has support for seccomp-filtering, so more secure. Ubuntu 16.04 uses systemd (instead of upstart) by default, so you may have to get used to that.

Let me close this issue for now, but let us know how it went


Possible to require semi colon only when needed?

For example,
This code is fine and doesn't need semi colons:
const p = props
const v = 'foo'

But this code may be error-prone:
const p = props
(window as any).test = "test"

because it is the same as
const p = props(window as any).test = "test"

which tries to call props as a function.
Can we make semi colons only required when cases like that are detected, otherwise never require a semicolon? So we would write code like this:
const foo = 'foo' // no semicolon
const p = props; // semicolon required

(window as any).test = "test" // no semicolon

This would also teach people why semis are needed or not needed, rather than just tell them "always use semi colons".
Maybe I can achieve exactly this in a different way using other rules, like requiring function call parens on the same line as the function identifier? Any other cases that can be covered by rules, to achieve the same overall effect of requiring semis only in those special cases?

Looks like tslint-eslint-rules has a rule that does exactly this.

@trusktr So you basically want something like eslint's no-unexpected-multiline?

Hey guys, yeah something like those would be great!
On Apr 10, 2017 11:09 PM, "Klaus Meinhardt"<EMAIL_ADDRESS>wrote:

@trusktr https://github.com/trusktr So you basically want something
like eslint's no-unexpected-multiline
http://eslint.org/docs/rules/no-unexpected-multiline?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/palantir/tslint/issues/2542#issuecomment-293160328,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASKzqxhrMrhkMlwbzfzU9RkfE4uBuswks5ruxkbgaJpZM4M5asZ
.

Apparently there's already "semicolon": [true, "never"] in tslint itself and no-unexpected-multiline is included in tslint-eslint-rules, so you can just combine those two and it'll do exactly what you want.

Cool, it works!


PogoPlayer RPC Error 51

Anyone else getting an error when trying to run pogoplayer please see here:
https://github.com/MRokas/PogoPlayer/issues/6
https://github.com/cyraxx/pogobuf/issues/85

could you paste the output?

when pogo.js runs to accept TOS, for each account I receive this message (formatting is my own, but the content of the message is the same:
Failed to initialize client...
ERROR: {
  [Error: operation timed out after 5061 ms, 5 tries with error: Fetching RPC endpoint failed, received status code 51]
  failure: [Error: Fetching RPC endpoint failed, received status code 51],
  code: 'ETIMEDOUT'
}

`

PR for a fix is ready for review on the pogobuf repo, once that's merged and a release created I think you can just do npm update ... speaking of which, should the install.bat script include an npm update command to handle this situation (for those users who can't figure out how to do a simple command)
see:
https://github.com/cyraxx/pogobuf/pull/86

will be kept in mind on the install script, the windows one is still considered experimental.

This is an issue with the submodule and dependancies. Once that gets fixed on the other repos, it'll automatically get fixed here since we're including them as a submodule and not just a copy. closing

I agree with the decision pyr0 EXCEPT that most people don't search the issues before submitting. I put it here as a FYI to preempt any other folks from submitting "OMG WTF Y U NO WORK"

pogobuf is updated.
npm update


vscode: "Extensions have been modified on disk. Please reload the window."

Describe the bug
Very often, when opening Visual Studio Code (Codium in my case), or when opening a new folder, if you have with many extensions, the message in the title may appear.
I have no idea what exactly causes this to happen. With the many extensions I use, this message appears more than half of the time.
I managed to make the message spawn with only two extensions, but it isn't consistent at all (I managed to do it twice):
Steps To Reproduce
Steps to reproduce the behavior:

Install vscode with the extensions below (it can also be installed with nix-shell);
Open code (codium in my case). Maybe also load a folder;
You may see the notification: "Extensions have been modified on disk. Please reload the window.".

Expected behavior
The notification shouldn't appear.
Additional context
Here are the logs.
The notification message is in the logs, so it can be searched, then look the context around.
With many extensions: vslog.txt
environment.systemPackages = with pkgs; [
  (vscode-with-extensions.override {
    vscode = vscodium;
    vscodeExtensions = with vscode-extensions; [
      streetsidesoftware.code-spell-checker
      serayuzgur.crates
      mhutchie.git-graph
      eamodio.gitlens
      arrterian.nix-env-selector
      jnoortheen.nix-ide
      rust-lang.rust-analyzer
      llvm-vs-code-extensions.vscode-clangd
      github.vscode-pull-request-github
      vadimcn.vscode-lldb
    ] ++ pkgs.vscode-utils.extensionsFromVscodeMarketplace [
      {
        name = "clang-tidy";
        publisher = "notskm";
        version = "0.5.1";
        sha256 = "sha256-neAvG8bk8yzpbuSzvVVi8Z3lCr29FBncXx3Sv/KChHw=";
      }
      {
        name = "code-spell-checker-italian";
        publisher = "streetsidesoftware";
        version = "0.1.12";
        sha256 = "sha256-4DcFOowP3yALpYuCPN004TktTMgUE1cnq4R81/LxM3I=";
      }
    ];
  })
]

With few extensions: vsminlog.txt
environment.systemPackages = with pkgs; [
  (vscode-with-extensions.override {
    vscode = vscodium;
    vscodeExtensions = with vscode-extensions; [
      jnoortheen.nix-ide
      llvm-vs-code-extensions.vscode-clangd
    ];
  })
]

Notify maintainers
@Synthetica9 @turion @bobby285271
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.18.9-zen1, NixOS, 22.11 (Raccoon), 22.11pre390234.2770cc0b1e8`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos"`
 - channels(user): `""`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Fixed upstream: https://github.com/microsoft/vscode/issues/151370.

Sorry, saw another issue about that in the repo that was closed, making me think it was a NixOS issue.
(This one)

I still experience the issue on VSCodium 1.69.1.
Clearing the cache also didn't fix it.

The fix I mentioned is still only released to Insiders, I'll keep this open until we have the release version that contains this fix packaged.


[tool_crash] FileSystemException: Cannot open file, OS Error: The system cannot find the file specified., errno = 2

Command
flutter doctor

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot open file, OS Error: The system cannot find the file specified.
, errno = 2
#0      _File.throwIfError (dart:io/file_impl.dart:675:7)
#1      _File.openSync (dart:io/file_impl.dart:490:5)
#2      _File.writeAsBytesSync (dart:io/file_impl.dart:644:31)
#3      _File.writeAsStringSync (dart:io/file_impl.dart:668:5)
#4      ForwardingFile.writeAsStringSync (package:file/src/forwarding/forwarding_file.dart:150:16)
#5      ErrorHandlingFile.writeAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:266:22)
#6      _runSync (package:flutter_tools/src/base/error_handling_io.dart:587:14)
#7      ErrorHandlingFile.writeAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:265:5)
#8      Cache.setStampFor (package:flutter_tools/src/cache.dart:675:35)
#9      VersionCheckStamp.store (package:flutter_tools/src/version.dart:802:30)
#10     FlutterVersion._getLatestAvailableFlutterDate (package:flutter_tools/src/version.dart:338:31)
<asynchronous suspension>
#11     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart:285:47)
<asynchronous suspension>
#12     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:322:11)
<asynchronous suspension>
#13     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
<asynchronous suspension>
#15     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
<asynchronous suspension>
#16     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
<asynchronous suspension>
#17     main (package:flutter_tools/executable.dart:90:3)

[!] Flutter (Channel stable, 3.19.5, on Microsoft Windows [Version 10.0.22631.3374], locale en-ID)
    • Flutter version 3.19.5 on channel stable at C:\Users\vinse\Documents\flutter
    ! The flutter binary is not on your path. Consider adding C:\Users\vinse\Documents\flutter\bin to your path.
    ! The dart binary is not on your path. Consider adding C:\Users\vinse\Documents\flutter\bin to your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (16 hours ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\vinse\AppData\Local\Android\sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[✗] Visual Studio - develop Windows apps
    ✗ Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[✓] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[✓] VS Code (version 1.87.2)
    • VS Code at C:\Users\vinse\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.84.0

[✓] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.22631.3374]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 123.0.6312.60
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 122.0.2365.92

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 3 categories.

Flutter Application Metadata
No pubspec in working directory.

Closing this as a duplicate of https://github.com/flutter/flutter/issues/76479


Terminal task title lost when task is finished

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:
Version: 1.87.1 (system setup)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:36.258Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045
OS Version: Versión 22H2 (compilación de SO 19045.3086)

Steps to Reproduce:

Launch a task in the integrated terminal
The terminal title picks the task name correctly (based on terminal.integrated.tabs.title)
When the task finishes, the terminal gets renamed to "Task" losing the title task

This was not happenning in previous versions, broke recently

The terminal title gets renamed correclty after changing terminal.integrated.tabs.title and back:

Best regards!

this is working as designed as ${task} resolves to Task when the terminal belongs to a task. you can fix this by resetting the value of terminal.integrated.tabs.title to the default value.

Hello! thanks for the answer, and the provided solution.
It seemed to work, but Im afraid it does not cover all cases? But at least I think we narrowed down the bug.
I have a complex (pretty sure deterministic) python script with static code that touches stdout/stdcerr (also potentially spawns subprocesses). As you can see in the following pic, most times it does not keep the task name even with the default value for terminal.integrated.tabs.title ${process}:

But if I touch terminal.integrated.tabs.title value then it seems to be forced to reload  it and therefore correclty assings the title. You can see this in action in the gif from the original post, the task name is corrected for all values used after touching the setting.

My guess: This seems like there is some kind of race condition where the title is renamed sometimes as the task loses ownership due to subprocesses being spawned. At the end the task is always the owner, hence touching the setting and forcing the title to be reloaded always assigns a correct name.
Note: This was not happening before like in Januay, but could be certaintly due to my script being updated.
My suggested fix: This is weird and hard to reproduce, but seems like it could be certaintly fixed for any case if said reload of the terminal title is simply triggered always an additional time after task completion.

I tried reproducing it with the following simple tasks but no luck (which appear on top in the pic)
{
    "label": "_test echo",
    "command": "echo simple echo"
},
{
    "label": "_test echo py",
    "command": "python -c \"print('python echo')\""
},
{   // uses an external file (just with a print call)
    "label": "_test echo py script",
    "command": "python D:/diego.mateos/REPOS/__user/python/echo.py"
},
{
    "label": "_test echo py sub",
    "command": "python -c \"import subprocess; subprocess.Popen('echo python echo subprocess', shell=True)\""
},

Btw, ${task} works as I expect for these simpler tasks too: the task name is displayed in all cases even after completion.


Prevent ownership transfers in higher frequency

Due to an API rate limit, channel names cannot be changed more often than twice in 10 minutes. This means that voice channels that are transferred more often than that, cause the bot to "hang" in that async function until the rate limit allows the action which is then executed after the delay.
To prevent this from happening, a transfer should only be possible every 10 minutes. Note that fixing this issue should include putting some thought in handling the "automated" transfer after the owner left where the result cannot just be a "You cannot use this command right now".
Instead of using in-memory state, a new field in the database called last_transfer (or similar) should be used to store the timestamp of last update which is used to prevent or buffer further calls to VoiceChannel#setName.

Closing this as this has occured only a single time after deliberate attempts to break something in the bot and hasn't happened ever since. Without active attempts to do this, users usually all leave within the ~5 minute period after or the conversation goes on for longer than 5 minutes with the new room owner.

Currently the bot just buffers the output until the rate limit allows renaming the channel which makes things look like the bot is dead; that can certainly be improved.

This will be taken care of in the next release containing the revamped /voice commands


Bugs nic

Remove dependency for ChangeLog to fix issue with tests and settings.

Changes Unknown when pulling 36be45f9fafe9a75fff849f4a7edce0318ed9629 on bugs_nic into ** on v2**.


CI for Node

App
✕ Contains the compiled JavaScript (8 ms)
       ✕ Starts the game with a random player (1 ms)
turn
  ✓ Inserts an 'X' into the top center (1 ms)
  ✓ Inserts an 'X' into the top left
nextPlayer
  ✕ Sets the current player to be whoever it is not (1 ms)


[CS2103T-T12-2] tCheck

tCheck helps bubble tea store managers manage their stores' inventory, employee contact numbers, and other information. It is optimized for CLI users to update and retrieve the information more efficiently.

Codecov Report

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

@@            Coverage Diff            @@
##             master      #44   +/-   ##
=========================================
  Coverage     72.31%   72.31%
  Complexity      400      400
=========================================
  Files            70       70
  Lines          1228     1228
  Branches        124      124
=========================================
  Hits            888      888
  Misses          308      308
  Partials         32       32

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6389d85). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #44   +/-   ##
=========================================
  Coverage          ?   72.48%
  Complexity        ?      400
=========================================
  Files             ?       70
  Lines             ?     1225
  Branches          ?      124
=========================================
  Hits              ?      888
  Misses            ?      305
  Partials          ?       32

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <ø> (ø)
0.00 <0.00> (?)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <ø> (ø)
0.00 <0.00> (?)

Continue to review full report at Codecov.

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


added support for javascript incompatible devices

Devices that don' support javascript will have a notification link telling them to enable javascript inorder to use the preference tool.The notification is also a link that points to steps on how to enable javascript on their devices

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your<EMAIL_ADDRESS>seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

There are several cons related to the  tag. You can read about them here.  If you're going to fall back to no-Javascript, there is a much better way than a  tag. Simply do this in the HEAD of your document:
<script type="text/javascript">     document.getElementsByTagName('html')[0].className += ' Q_js'; // better than noscript </script>
With this technique, you can easily refer to the Q_js class in your CSS to hide things. With the  tag, the best you can hope for is to include an additional CSS file to override previous CSS. This becomes important when some elements with static content are supposed to be hidden right away (not flicker) until Javascript can make them more dynamic.
Reference: https://stackoverflow.com/questions/2170484/shouldnt-we-use-noscript-element
P.S. Please sign the CLA too.


chore(main): release 1.2.0

:robot: I have created a release beep boop
1.2.0 (2023-09-28)
Features

add NodejsFunction construct and create common alarm infra (#23) (8db3112)

Bug Fixes

update dependencies to latest versions with security fixes (#21) (ec24592)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cuckoointernet/aws-constructs/releases/tag/v1.2.0 :sunflower:


opaque type

Opaque type that holds the model

It is not opaque type.

This one is solved, thanks @4onen!


Failed to read input from stdin

Describe the bug
When I try to convert any input image, cjxl failed to read input from stdin with the error: Reading image data failed.
To Reproduce
cjxl - - < in.jpg > out.jxl
cat in.jpg | cjxl - - > out.jxl
Expected behavior
cjxl should read in the input from stdin and output into the stdout.
Environment

OS: Tested on both Windows 11 Home 22621.2283 and Linux
CPU type: x86_64
cjxl/djxl version string: JPEG XL encoder v0.8.2 954b4607 [AVX2,SSE4,SSSE3,SSE2]

Thanks for pointing out this issue! Seems like this is working on unix based systems, but still does not work on Windows. As a workaround until we have fixed it using WSL might help.

309b637 fixes this.

please re-open if the problem is reproducible at current head


Problem with short operations + underscores

Given:
  parser = Trollop::Parser.new do
    opt :silent, %q{Causes the script to not ask any questions, instead all questions turn into email + abort; used by cron}, :short => 's'
    opt :region, %q{Causes the script only work on the listed region}, :short => 'r', :type => String
    opt :noinst, %q{Causes the script to skip the checking of all instances}, :short => 'i'
  end

Running it with -i gives us:
  {:silent=>false,
   :region=>nil,
   :noinst=>true,
   :help=>false,
   :noinst_given=>true}

However, given:
  parser = Trollop::Parser.new do
    opt :silent, %q{Causes the script to not ask any questions, instead all questions turn into email + abort; used by cron}, :short => 's'
    opt :region, %q{Causes the script only work on the listed region}, :short => 'r', :type => String
    opt :no_instances, %q{Causes the script to skip the checking of all instances}, :short => 'i'
  end

which is what I had originally, running it with -i gives:
  {:silent=>false,
   :region=>nil,
   :no_instances=>false,
   :help=>false,
   :no_instances_given=>true}

which strikes me as wrong.

There is special logic for flags starting with 'no' to account for
supporting negation of normal flags.   I think you can specify a default to
get your desired affect.  Another option is to code for the positive and
set a default.
See this blog post for more detail.
http://masanjin.net/blog/trollop-2.0-released
Does that help explain it?
On Jan 26, 2015 9:48 PM, "rlpowell"<EMAIL_ADDRESS>wrote:

Given:
parser = Trollop::Parser.new do
opt :silent, %q{Causes the script to not ask any questions, instead all questions turn into email + abort; used by cron}, :short => 's'
opt :region, %q{Causes the script only work on the listed region}, :short => 'r', :type => String
opt :noinst, %q{Causes the script to skip the checking of all instances}, :short => 'i'
end
Running it with -i gives us:
{:silent=>false,
:region=>nil,
:noinst=>true,
:help=>false,
:noinst_given=>true}
However, given:
parser = Trollop::Parser.new do
opt :silent, %q{Causes the script to not ask any questions, instead all questions turn into email + abort; used by cron}, :short => 's'
opt :region, %q{Causes the script only work on the listed region}, :short => 'r', :type => String
opt :no_instances, %q{Causes the script to skip the checking of all instances}, :short => 'i'
end
which is what I had originally, running it with -i gives:
{:silent=>false,
:region=>nil,
:no_instances=>false,
:help=>false,
:no_instances_given=>true}
which strikes me as wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/ManageIQ/trollop/issues/37.

That does, although now the bug is "this doesn't seem to be mentioned in the documentation anywhere" :)
I'm looking at http://www.rubydoc.info/gems/trollop/2.1.1 and http://www.rubydoc.info/gems/trollop/2.1.1/Trollop/Parser

@ripowell thanks for bringing this up. Any suggestions for the docs?


Support for nodejs backend

Frameworks

[ ] express
[ ] fastify
[ ] next
[ ] nest

JS and TS with bpilerplates


Error when data are filled with zeros

In case where the data array are filled with all zeros, Expected Number error will occurred:
Error: <path> attribute d: Expected number, "M4 NaN L 4 NaN L 29…"
Base on looking at the source, the Y coord of each datapoint is determined by the max values of datapoints.  If data arrays are all 0, then you will run into a divide by zero scenario resulting in the above error.
  // The maximum value. This is used to calculate the Y coord of
  // each sparkline datapoint.
  const max = Math.max(...values);

i think this is causing the issue not sure though i havent used it
  if (typeof(entries[0]) === "number") {     entries = entries.map(entry => {       return {value: entry};     });   }

Have reproduced the error. Can someone recommend a fork that has the patch?


fix(popover): remove unnecesary effect-refs asignments + more

fix: precedeassertInInjectionContext with isDevMode
chore: add alignOffset change scenario to the stories

Enhances #97

@pimenovoleg something in addition to https://github.com/pawel-twardziak/radix-ng-primitives/commit/8cdcfa66f357b30b33ab323241f13148ac57ab90 :)

Upsss sorry, just updated the branch with main :) and re-requested for your approval unnecessarily :P


Enable the device server push events manually

Problem Description
At the moment the generated device server requires that polling be set for attribute(s) so that the client(s) can be able to subscribe to the attribute events. Depending on how many attributes the device might have, this might also degrade the performance of the server.
One proposed solution to this would be to have the device server push events to clients, which is more efficient than polling.
Two possible solutions (there can be more) are proposed:
Solution 1. Specify the flag(s) as part of the attribute configuration
In this scenario we add a property/properties in each attribute configuration to flag whether we want the device server to push either change/archive event for each individual attribute. The nice thing about this approach is that we can set it up for a specific attribute.
The proper place for this would be to use the SimDD.json configuration file to add this extra properties. This means we might also have to update the parser, but it shouldn't be difficult, and then when initialising the device, we would get these properties from the model and configure it accordingly.
Code snippet: tango_sim_generator.py
def initialize_dynamic_attributes(self):
    model_sim_quants = self.model.sim_quantities
    attribute_list = set([attr for attr in model_sim_quants.keys()])
    for attribute_name in attribute_list:
        meta_data = model_sim_quants[attribute_name].meta
        # Dynamically add all attributes except those with DevEnum data type,
        # and SPECTRUM data format since they are added statically to the device
        # class prior to start-up. Also exclude attributes with a data format
        # 'IMAGE' as we currently do not handle them.
        if not self._is_attribute_addable_dynamically(meta_data):
            if model_sim_quantities[attribute_name].meta['push_change_event']:
                self.set_change_event(attribute_name, True, True)

            if model_sim_quantities[attribute_name].meta['push_archive_event']:
                self.set_change_event(attribute_name, True, True)

             continue
        ....

        self._add_dynamic_attribute(attr, rw_type)
        MODULE_LOGGER.debug("Added dynamic {} attribute".format(attribute_name))

        if model_sim_quantities[attribute_name].meta['push_change_event']:
            self.set_change_event(attribute_name, True, True)

        if model_sim_quantities[attribute_name].meta['push_archive_event']:
            self.set_change_event(attribute_name, True, True)

Solution 2. Pass the flags as command line arguments
In this scenario, we pass a flag(s) in the terminal to signal whether to manually push events or not. With this approach, there won't be an easier way to specify as to for which attribute we want the event to be pushed for. We will have to just push for all attributes.
Code snippet: bash
$ tango-simlib-generator --sim-data-file <xmi/fgo/json>\
                         --dserver-name <server-name>\
                         --directory <output filepath>\
                         --push-change-events <True/False>\
                         --push-archive-events <True/False>

Code snippet: tango_sim_generator.py

....

def generate_device_server(
    server_name,
    sim_data_files,
    directory="",
    push_change_events=False,
    push_archive_events=False
):
....
    lines = [
        ....
        "    TangoDeviceServers = get_tango_device_server("
        "        models,"
        "        sim_data_files,"
        "        push_change_events={},".format(push_change_events)
        "        push_archive_events={}".format(push_archive_events)
        "     )"
....

def get_tango_device_server(
    models,
    sim_data_files,
    push_change_events=False,
    push_archive_events=False
):
....

def initialize_dynamic_attributes(self):
    model_sim_quants = self.model.sim_quantities
    attribute_list = set([attr for attr in model_sim_quants.keys()])
    for attribute_name in attribute_list:
        meta_data = model_sim_quants[attribute_name].meta
        # Dynamically add all attributes except those with DevEnum data type,
        # and SPECTRUM data format since they are added statically to the device
        # class prior to start-up. Also exclude attributes with a data format
        # 'IMAGE' as we currently do not handle them.
        if not self._is_attribute_addable_dynamically(meta_data):
            if push_archive_events:
                self.set_archive_event(attribute_name, True, True)

            if push_change_events:
                self.set_change_event(attribute_name, True, True)

             continue
        ....

        self._add_dynamic_attribute(attr, rw_type)
        MODULE_LOGGER.debug("Added dynamic {} attribute".format(attribute_name))

        if push_archive_events:
            self.set_archive_event(attribute_name, True, True)

        if push_archive_event:
            self.set_change_event(attribute_name, True, True)

@ajoubertza , @samueltwum1 please let me know what you think of this? Any suggestions are also welcome.

I like option 1, as the behaviour is more clearly document in the configuration file, and it gives the user more options.  A few suggestions:

I agree that the default behaviour is not to push change or archive events.
For devices that have many attributes it will be tedious to add the config for each one to simDD.json, so I suggest a global option as the start of the file that allows us to enable the feature(s) for all attributes.  Then users could optionally disable it for some attributes, if they like.  Alternatively, the user could disable at the global level, and then only turn it on for a few attributes.  It depends on use case.
It would also be useful to override the last parameter to set_archive_event and set_change_event.  To use rel/abs filtering rules or not.


Generate first repeating OBR segment from FHIR bundle

User Story:
As a receiver, I want the internal FHIR bundle to be converted to an HL7 v2 message, so I ReportStream can prepare the message to be sent.
Description/Use Case
We have a FHIR to HL7 v2 library to convert our internal FHIR bundles to HL7.  We need to configure the library, so that the data in the FHIR bundle is converted to HL7 in a lossless way.
Risks/Impacts/Considerations

The FHIR to HL7 library is unable to convert some data for some unforeseen reason.
The HL7 to FHIR conversion was not lossless and we are missing data.

Dev Notes:

Reference the RS HL7 v2 to FHIR dictionary (the spreadsheets) generated for the HL7 to FHIR conversion to determine the proper FHIR to HL7 conversion.

Acceptance Criteria

The full ELR HL7 ORC segment data is converted from FHIR resources and added to an HL7 message.
The generated HL7 segment matches the sample HCA input HL7 segment (used during the HL7->FHIR conversion) excluding any exceptions noted in the mapping dictionary.
Document any exceptions or issues with the conversion process.

Effort for the first segment or all repeating segments is the same, so closing in favor of just doing all repeating segments of this type.

Effort for the first segment or all repeating segments is the same, so closing in favor of just doing all repeating segments of this type.


Don't remove other IP's from provisioning interface

If the podIP is set to be on the provisioning network (it's not clear
to me how kubelet picks which IP to be for a pod that's using host networking), then when it gets
removed by the static IP manager and replaced with the <IP_ADDRESS>
record, podIP is still set to the old invalid IP and heath checks start
failing and the cluster breaks.
From previous scouring of various bug reports, it looks like we were
using 192.168.111.x baremetal network for the podIP before, so maybe
something changed here. With this fix, e.g. running this before building
a cluster:
export IRONIC_STATIC_IP_MANAGER_LOCAL_IMAGE=https://github.com/stbenjam/static-ip-manager-image.git

We can get a successful install.

Not sure what the right solution is, but this does get the cluster to come up.
/cc @cybertron
/cc @celebdor

I'm unclear why the podIP would ever be on the provisioning network?
That's supposed to be the external/controlplane interface to the pod and the provisioning nic is dedicated to the provisioning network, which is completely unrelated to the pod networking.
So I assume something changed here which set this incorrectly?

We did discover the underlying cause, and there's fixes in progress: https://github.com/openshift/installer/issues/2646#issuecomment-552983562
The changes to CRI-O have to make into RHCOS, and then into the installer, so it'll take some time for all that to flow through. The CRI-O team has reacted super fast to this but it's still a week or more away for the whole process to complete :-\
We'll need some solution in the iterim, @hardys was looking at a less invasive change to network manager via dev-scripts, so hopefully we can take that instead of this.

/hold

/close


Working installation

In a virtual environment with python 3.9, have to modify requirements.txt
importlib_metadata
mapomatic==0.6
mthree==0.24
pylatexenc
qiskit==0.46.3
qiskit-aer
qiskit-terra>=0.21
it will install
qiskit-0.46.3     (the last one before qiskit 1.0)
qiskit-aer-0.14.2
qiskit-terra-0.46.3
and
from linear_solvers import NumPyLinearSolver, HHL
works without errors (after moult effort).

confirm working


runtime: should there be a minimum heap size to trigger GC?

The really tiny GCs (of less than 1 MB) are very sensitive to constant overheads in the
GC.
The usual 2x policy doesn't work great if the program has a consistent live data set of
100 kB.
There are tons of GCs and the constants dominate.

Should we set a minimum heap size for GC like 1 MB, so that even if the previous GC
ended with 100 kB of live data, we still wait until 1 MB (not 200 kB) before the next
one?

813e97b introduced a heap minimum of 4MB and later b6e178e updated this so the heap minimum is 4MB * (GOGC/100).


update regression function and script: adding linear/quad drift

Added linear and quadratic drift.
Haven't add smoothing function yet, will do that soon.
Just want to upload the things I have for now.

Ok I will update the test functions

Now, I have no idea how to merge the conflict...

0.0 commit the files in your current branch first,
then pull the changes, you will probably get merge conflicts message, then
You have to manually go through the each merge conflict file and follow the answer to
http://stackoverflow.com/questions/24103490/need-help-to-understand-merge-conflict-example
then re-commit and push

lmk tomorrow if you cannot get it to work, then I will just copy and paste your code and update it

OK, fixed merge conflicts. :D

ok good, someone else can give this a check?

Not all the input/output is updated to include the drifts but doesn't really matter, it looks good, thanks for the work you guys


Add anchor style for address in footer section

Issue Description
I see that the color of email address (linked text) has different color than others and is underlined as well in every page that contains footer section. So, I wanna add address class and set its styles there to change the color and remove the underlined effect. It'll make change to existing and every new page created that contains footer section as well.
For now, it's on home and trending page.

If you find this issue valid, please assign to me.
Are you a Hacktoberfest'21 contributor

[X] Yes, I'am Hacktoberfest'21 contributor

also please add the link to Best Sellers and Trending pages to the footer in order same as Navbar.

I already add address class and link for trending and best sellers on the footer as well. Please check my pull request #62
Thank you

I've fixed the conflicts and create new pull request #66 because I've removed previous branch. Please check the new one. Thank you.