text:
ruff server: Support a custom TOML configuration file

Summary
Closes #10985.
The server now supports a custom TOML configuration file as a client setting. The setting must be an absolute path to a file. If the file is called pyproject.toml, the server will attempt to parse it as a pyproject file - otherwise, it will attempt to parse it as a ruff.toml file, even if the file has a name besides ruff.toml.
If an option is set in both the custom TOML configuration file and in the client settings directly, the latter will be used.
Test Plan

Create a ruff.toml file outside of the workspace you are testing. Set an option that is different from the one in the configuration for your test workspace.
Set the path to the configuration in NeoVim:

require('lspconfig').ruff.setup {
    init_options = {
      settings = {
        configuration = "absolute/path/to/your/configuration"
      }
    }
}

Confirm that the option in the configuration file is used, regardless of what the option is set to in the workspace configuration.
Add the same option, with a different value, to the NeoVim configuration directly. For example:

require('lspconfig').ruff.setup {
    init_options = {
      settings = {
        configuration = "absolute/path/to/your/configuration",
        lint = {
          select = []
        }
      }
    }
}

Confirm that the option set in client settings is used, regardless of the value in either the custom configuration file or in the workspace configuration.

In the absence of a project configuration for ruff, will the LS load the seetings from ~/.config/ruff/ruff.toml like the CLI does ?

It should yes -- not sure if it does yet though @snowsignal?

@GaetanLepage I actually don't think we do this, yet - I've filed an issue to support this.

authors: GaetanLepage charliermarsh snowsignal

repo: astral-sh/ruff


text:
Remove WithItem<"as"> goal

Summary
I found the negation difficult to reason about. That's why I extracted a new WithItemAs rule instead.

Test Plan
cargo test

Current dependencies on/for this PR:

main

PR #6867

PR #6868   👈

This comment was auto-generated by Graphite.

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Print shell-specific activation command in venv

When using the fish shell, the activate script fails with this error
❯ uv --version
uv 0.1.13

❯ uv venv -p 3.11
Using Python 3.11.7 interpreter at: /opt/homebrew/opt/python@3.11/bin/python3.11
Creating virtualenv at: .venv
Activate with: source .venv/bin/activate

❯ source .venv/bin/activate
.venv/bin/activate (line 69): Unsupported use of '='. In fish, please use 'set VIRTUAL_ENV '/Users/myapp/.venv''.
VIRTUAL_ENV='/Users/myapp/.venv'
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
from sourcing file .venv/bin/activate
.: Error while reading file '.venv/bin/activate'

Are there any plans to support fish shell?
Thank you for this great project 🙏🏽

A dedicated activate.fish exists, so you should be able to use source .venv/bin/activate.fish.
It looks like the venv command does not try to guess the current shell used, so it always displays bin/activate on non-Windows systems: https://github.com/astral-sh/uv/blob/14d968ac224c88988c60b6c067f0cafbc3ea4a07/crates/uv/src/commands/venv.rs#L227-L231

Also with git bash on windows uv says: Activate with: .venv\Scripts\activate
but command is wrong. Should be source .venv/Scripts/activate

Hopefully the above would fix that too though not 100% sure.

I can confirm that activate.fish worked 🙌🏽
So yea, it's just a nit to make the experience more intuitive.
Thanks forlks

source: gharchive/issue

authors: charliermarsh daniel-bartley mkniewallner saada

repo: astral-sh/uv


text:
md5 hashes in pip compile *.txt are not supported by pip

Hello there!
Issue:
When compiling dependencies with uv pip compile requirements.in we noticed that uv is putting md5 hashes instead of sha hashes in the resulting requirements.txt. This is a problem as pip only supports sha256, sha384, sha512 hashes.
When does this happen:
This happens only for our private Gemfury pypi index so my suspicion is that Gemfury responds with a md5 hash as default instead of sha.
Could uv check if there is also a sha hash in the index's response or calculate the sha from the package?
Example:
#requirements.txt
our-pkg==3.39.0 \
    --hash=md5:2427c69da75124df182f48e6d8fa7ccb

$ pip install --require-hashes -r requirements.txt

ERROR: Invalid requirement: our-pkg==3.39.0     --hash=md5:2427c69da75124df182f48e6d8fa7ccb
pip: error: Allowed hash algorithms for --hash are sha256, sha384, sha512.

Version: uv 0.2.22 (f5e84bbba 2024-07-07)

We should probably remove MD5 support.

Hi there! This issue has been open for a while, and I can second that it's likely mostly for private repositories.
md5 support was added here. It seems we might need to revert that PR (I know it's not really the source of the problem) or provide a set of hash algorithms that are acceptable as an option with some reasonable default. FWIW pip doesn't allow md5 in their secure installs which was the source of the original issue.
Would suggest using sha256, sha384, sha512 as 'acceptable' values as they seem to be the allowed values for pip, which as I understand it is still meant to remain compatible with uv.
In the meantime, for those that are having this issue can use regular pip-compile on problem packages temporarily, but it means keeping uv.lock up to date which is at best a hack.

We should probably remove MD5 support.

Removing may be a bit harsh although there are very valid arguments to do so.
Making md5 support "opt-in" when generating a requirements.txt file would be sufficient.
I just tried integrating uv into our toolchain (we maintain about 100 Python projects) and a lot of CI jobs still use pip install [...] and using uv to generate the file made all those jobs fail because of the md5 hashes.
The support added in #1547 is still valid. But generating md5 hashes in requirements files... not so much :)

authors: angerrp bcmyguest charliermarsh exhuma


text:
Stream zip archive when fetching non-range-request metadata

Summary
If a registry doesn't support range requests, then today, we download the entire wheel to disk and then read the metadata from the downloaded archive. This PR instead modifies the registry client to stream the zipfile and stop as soon as it's seen the metadata, which should be more efficient.
Closes https://github.com/astral-sh/uv/issues/1596.
Test Plan
Made this the only path for downloading metadata; verified that the test suite passed.

Something like 10-20% faster:
puffin on  charlie/async-meta:main [$!⇡] is 📦 v0.1.6 via 🐍 v3.12.1 (.venv) via 🦀 v1.75.0
❯ python -m scripts.bench \
        --uv-path ./target/release/main \
        --uv-path ./target/release/uv \
        ./scripts/requirements/dtlssocket.in --benchmark resolve-cold --min-runs 50
Benchmark 1: ./target/release/main (resolve-cold)
  Time (mean ± σ):     896.5 ms ±  79.0 ms    [User: 404.9 ms, System: 202.6 ms]
  Range (min … max):   726.3 ms … 1075.0 ms    50 runs

Benchmark 2: ./target/release/uv (resolve-cold)
  Time (mean ± σ):     802.7 ms ±  58.6 ms    [User: 420.7 ms, System: 179.8 ms]
  Range (min … max):   722.5 ms … 953.8 ms    50 runs

Summary
  './target/release/uv (resolve-cold)' ran
    1.12 ± 0.13 times faster than './target/release/main (resolve-cold)'
puffin on  charlie/async-meta:main [$!⇡] is 📦 v0.1.6 via 🐍 v3.12.1 (.venv) via 🦀 v1.75.0 took 1m34s
❯ python -m scripts.bench \
        --uv-path ./target/release/main \
        --uv-path ./target/release/uv \
        ./scripts/requirements/black.in --benchmark resolve-cold --min-runs 50
Benchmark 1: ./target/release/main (resolve-cold)
  Time (mean ± σ):     380.8 ms ±  83.5 ms    [User: 102.9 ms, System: 39.9 ms]
  Range (min … max):   281.8 ms … 550.7 ms    50 runs

Benchmark 2: ./target/release/uv (resolve-cold)
  Time (mean ± σ):     325.3 ms ±  44.7 ms    [User: 113.8 ms, System: 26.9 ms]
  Range (min … max):   269.4 ms … 411.9 ms    50 runs

Summary
  './target/release/uv (resolve-cold)' ran
    1.17 ± 0.30 times faster than './target/release/main (resolve-cold)'


text:
Fix running make docker-run when there is a new version

Previoulsy, we never deleted wheels. The consequence is that the include directory would contain multiple versions of the Ray provider package, which would raise an exception when trying to run make docker-run.
Example of error:

0.608 The conflict is caused by:
0.608     The user requested astro-provider-ray 0.2.1 (from /usr/local/airflow/include/astro_provider_ray-0.2.1-py3-none-any.whl)
0.608     The user requested astro-provider-ray 0.3.0a7 (from /usr/local/airflow/include/astro_provider_ray-0.3.0a7-py3-none-any.whl)
0.608
0.608 To fix this you could try to:
0.608 1. loosen the range of package versions you've specified
0.608 2. remove package versions to allow pip to attempt to solve the dependency conflict
0.608
0.825
0.825 [notice] A new release of pip is available: 24.2 -> 24.3.1
0.825 [notice] To update, run: pip install --upgrade pip
0.826 ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
------
Dockerfile:25
--------------------
  23 |     USER astro
  24 |
  25 | >>> RUN pip install /usr/local/airflow/include/*.whl
  26 |
--------------------
ERROR: failed to solve: process "/bin/bash -o pipefail -e -u -x -c pip install /usr/local/airflow/include/*.whl" did not complete successfully: exit code: 1

View build details: docker-desktop://dashboard/build/desktop-linux/desktop-linux/17i8mx9qdqmd7fb72fe3uxjxc
Error: command 'docker build -t dev_c226a1/airflow:latest failed: failed to execute cmd: exit status 1
make: *** [docker-run] Error 1
```

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.22%. Comparing base (be298c8) to head (2a3dfcf).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   98.22%   98.22%
=======================================
  Files           5        5
  Lines         564      564
=======================================
  Hits          554      554
  Misses         10       10

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

authors: codecov-commenter tatiana

repo: astronomer/astro-provider-ray


text:
As an Astronomer Customer... guide

Let's try to make a guide with all onboarding information in one place to make the initial email less intimidating and drive traffic back to our site.
Let's try to get this up ASAP - tons of new cloud deals prospects coming in :)

Just pushed up this guide: https://astronomer.io/guides/astro-customer-onboarding/
Will continue iterating with @vparekh94 @petedejoy but closing this out for now.

repo: astronomerio/airflow-guides


text:
Remapped escape not working

I use linux and have remapped my escape key to caps lock with setxkbmap -option caps:escape. It works everywhere in my OS as well as in vscode when I want to close the menu for example.
However, it does not exit insert or visual mode with this plugin for some reason. I have checked with showkey program that when I press escape or caps lock they output identical codes. Any ideas what could be causing this?
EDIT: Wanted to add that this is also the case with no other plugins installed and all default vscode settings. Oh, and normal escape key works just fine.

Try to set in vscode settings:
"keyboard.dispatch": "keyCode"
See https://github.com/microsoft/vscode/issues/23991 for the background:

That fixed it! Should have assumed it's vscode issue.
Anyway, thanks for quick reply and your work on this extension. It's making me try vscode again after a long hiatus.

You're welcome!

authors: asvetliakov erlais

repo: asvetliakov/vscode-neovim


text:
hotkey('fn', 'f10') isn't working

I use fn + f10 to turn on/off my webcam, but the hotkey doesn't works. Am I missing something?
from pyautogui import hotkey
hotkey('fn', 'f10')

Please check your keybinding
It's working fine in my machine

authors: Shubhamsm leo-smi

repo: asweigart/pyautogui

license_source: bigquery


text:
Support for deriving OneofObject and Union +  OneofObject and Interface simultaneously

Description of the feature
Since the @oneOf directive only applies to input now (also see #915), it would be nice if other forms of output polymorphism could be supported using the same enum we use for OneofObject. This could be achieved by allowing to simultaneously derive OneofObject and Union or OneofObject and Interface.
This seems to be possible by (re)using #[graphql(input_name = "...")] (see the example below). Right now, derivation at the same time is not possible because of a runtime error:

thread 'main' panicked at 'Register Ab as Union, but it is already registered as InputObject

When using OneofObject and Interface simultaneously we get a compile time error:

error: Unknown field: field

Code example
OneofObject and Union
use async_graphql::*;

#[derive(SimpleObject, InputObject)]
#[graphql(input_name = "AInput")]
struct A {
    a: String,
}

#[derive(SimpleObject, InputObject)]
#[graphql(input_name = "BInput")]
struct B {
    b: String,
}

#[derive(Union, OneofObject)]
#[graphql(name = "AB")]
#[graphql(input_name = "ABInput")]
enum AB {
    A(A),
    B(B),
}

directive @oneOf on INPUT_OBJECT

type A {
    a: String!
}
input AInput {
    a: String!
}

type B {
    b: String!
}
input BInput {
    b: String!
}

union AB = A | B
input ABInput @oneOf {
    a: AInput
    b: BInput
}

OneofObject and Interface
use async_graphql::*;

#[derive(SimpleObject, InputObject)]
#[graphql(input_name = "AInput")]
struct A {
    name: String,
    a: String
}

#[derive(SimpleObject, InputObject)]
#[graphql(input_name = "BInput")]
struct B {
    name: String,
    b: String
}

#[derive(Interface, OneofObject)]
#[graphql(name = "AB")]
#[graphql(input_name = "ABInput")]
#[graphql(field(name = "name", type = "String"))]
enum AB {
    A(A),
    B(B),
}

directive @oneOf on INPUT_OBJECT

type A implements AB {
    name: String!
    a: String!
}
input AInput {
    name: String!
    a: String!
}

type B implements AB {
    name: String!
    b: String!
}
input BInput {
    name: String!
    b: String!
}

interface AB {
    name: String!
}
input ABInput @oneOf {
    a: AInput
    b: BInput
}

Using multiple procedural macros at the same time and avoiding conflicts is often cumbersome and requires a lot of compatibility work. 😂

Partially solved in #1116

repo: async-graphql/async-graphql


text:
Dynamic Document Title for GraphiQL v2 and GraphQL Playground

Closes #1098

Thanks!😄

@sunli829 could you add the hacktoberfest label to the repository, or add the hacktoberfest-accepted label to this PR so this counts as a valid contribution? That would be awesome :)


text:
Throw on invalid watcher identifier

Addresses #58. Adds InvalidWatcherExeption that should be thrown if enable, disable, cancel, reference, or unreference is attempted with an invalid watcher identifier.

I'd explicitly specify invalid or cancelled. This eliminates every ambiguity.
Cancelling may or may not invalidate the watcher internally immediately.

Do we maybe want to explicitly add (on Driver interface) that disable() never invalidates a watcher?

I agree, I'll add that as well.

Cancelling may or may not invalidate the watcher internally immediately.

I'd say it should do that immediately.

@kelunik yes, should. But that's an implementation detail we have no control of.

It's something we can define. Then we have the control.

It may eventually depend on the loop implementation. I.e. uv internally only releases it on the next tick. (to avoid freed memory access; see also uv_close() on libuv docs))

authors: bwoebi kelunik trowski

repo: async-interop/event-loop

license: mit


text:
ci: fix update-spec workflow

As in title: treat injected value from action context as string.

@derberg Could you check again? I had to update the github-scripts action to v4 version, because that version only read the local scripts from repo.

repo: asyncapi/spec


text:
redirect output log

Hi!
Is it possibile to redirect the output of actor logging to stderr or to a file?
Something like log.SetOutput(iow).
The problem: using a tui (i.e.: https://github.com/jroimartin/gocui) I cannot redirect or capture the output of the actor log.
EDIT: forgot to mention that I'd prefer a solution using the library instead of redirect the output to another file descriptor (i.e. ./run >& log.txt)

I need this too.

you can make a pr for it.
https://github.com/AsynkronIT/protoactor-go/blob/dev/log/string_encoder.go#L23

I also need this,Logs cannot be integrated into my business.
I suggest that can set  a logger ,this logger has "debug,info,error..." interface

Is there any movement on this? Why not use something like https://github.com/uber-go/zap? That would fall in line with the Build on existing technologies.

authors: coverthesea cupen hulucc notdodo tyronegroves

repo: asynkron/protoactor-go


text:
contents of the buffer

hello. As I see, the pio0 for each 32-bit sampled data fills the buffer by two values: the size of the sampled data and the sampled 32-bit data itself. then you add the end time of sampling that data as the third element. thus for each 32 data sampling, the buffer is filled by 3 elements in a row. but sometimes pio0 pushes out another element as a fourth value which is 0xFFFFFFFF.
so, what is this value and what does it mean? is it a flag for the end of the frame?

The size of the data from the PIO is indicated as 0xffffffff-actual size (it counts down from 0xffffffff) and the data is limited to 31 bits. So, highest bit can be used to distinguish size (end of packet) from the data bits.
The only time PIO0 can push 0xffffffff is when the actual size is 0, and that only happens in the case of a line reset (D+=low, D-=low), which appears as a valid start of packet marker, but then does not have synchronization field.
But 0xffffffff is never pushed as an additional data, it is always pushed as a length part.

So for each data sample, g.buffer is filled only with 3 elements: size,
time, data itself.
در تاریخ یکشنبه ۸ سپتامبر ۲۰۲۴، ۱۸:۵۳ Alex Taradov <
@.***> نوشت:

The size of the data from the PIO is indicated as 0xffffffff-actual size
(it counts down from 0xffffffff) and the data is limited to 31 bits. So,
highest bit can be used to distinguish size (end of packet) from the data
bits.
The only time PIO0 can push 0xffffffff is when the actual size is 0, and
that only happens in the case of a line reset (D+=low, D-=low), which
appears as a valid start of packet marker, but then does not have
synchronization field.
But 0xffffffff is never pushed as an additional data, it is always pushed
as a length part.
—
Reply to this email directly, view it on GitHub
https://github.com/ataradov/usb-sniffer-lite/issues/19#issuecomment-2336725079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2VUWY7YRITJFSGWIIOND5LZVRTYLAVCNFSM6AAAAABN3AZVACVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMZWG4ZDKMBXHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Correct. You get data + size from the PIO itself and the time is added in the loop after the last element is read from the PIO.

repo: ataradov/usb-sniffer-lite


text:
🛑 Wedding HTTPS is down

In a10be1f, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in b16c06b.

repo: atatkin/milos-uptime


text:
🛑 Wedding HTTPS is down

In 51f236d, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in a744124.


text:
🛑 Wedding HTTPS is down

In 534fbe0, Wedding HTTPS ($WEDDINGHTTPS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wedding HTTPS is back up in 40f9c12.


text:
Slow sending an email to multiple recipients

I'm trying to implement #108 on a basic level by modifying the Send API controller, by looping through an array of recipients. Even though I am not really known with Ruby I managed to code something that seems to work (minus some bugs).
I noticed though that it takes a lot more time if you send an email to multiple recipients. Sending the same email to 1 recipient takes roughly 0.4 seconds, 3 recipients varied between 2.7 and 3.6 seconds and when sending to 7 recipients it nearly took 7 seconds. (On other runs it varied between 4 and 10 seconds)
(I tried this both with my modified API controller and with the default/original controller)
If I'm not mistaken, all the emails are first queued aren't they? So it's not like it's actually sending the emails in those 7 seconds. What could be causing this latency? Or are these figures normal?

Where are you timing this? It could well be the receiving server taking some time to process your message. The best place to look will be in the worker.log log file which will show you everything that happens when a message is sent from the queue.
By default, postal runs a single worker process that is single-threaded. You can run multiple workers to improve throughput if you have lots of messages waiting to be processed in the queue. You can update the workers.quantity option in the configuration file.

This is the time reported back by Postal ("status" => "success", "time" => 5.87 for example), using the HTTP API.
I'm not talking about the actual delivery of the emails, I mean the time it takes to complete the HTTP API call.

Oh I see! If you've modified the code, I'm afraid I really can't help you with that.

It also occurs with the original code. If I send the same email with multiple recipients in the "to" array, it has the same performance.

Which method? send/raw or send/message?

From send/message:
{
  "status": "success",
  "time": 0.14,
  "flags": {},
  "data": {
    "message_id": "f7924582-466d-4b19-b51b-a8ec34f25690@rp.postal.example.com",
    "messages": {
      "test@pat.infra.atech.io": {
        "id": 11,
        "token": "Zbwr96NDnwQA"
      },
      "test2@pat.infra.atech.io": {
        "id": 12,
        "token": "agC9jXKKZOnx"
      },
      "test3@pat.infra.atech.io": {
        "id": 13,
        "token": "Zx6gKs28FBoo"
      },
      "test4@pat.infra.atech.io": {
        "id": 14,
        "token": "pteO3cEa85zr"
      },
      "test5@pat.infra.atech.io": {
        "id": 15,
        "token": "aSutiv3KbAcy"
      },
      "test6@pat.infra.atech.io": {
        "id": 16,
        "token": "igs2puZZqYCp"
      },
      "test7@pat.infra.atech.io": {
        "id": 17,
        "token": "NmSwV9x8sS8F"
      },
      "test8@pat.infra.atech.io": {
        "id": 18,
        "token": "dmSie6EZCpEk"
      },
      "test9@pat.infra.atech.io": {
        "id": 19,
        "token": "AMyxqrLX55mi"
      }
    }
  }
}

I'm using send/message. Does Postal queue the emails injected via the HTTP API, or does it try to deliver them immediately? The latter would explain it.

All messages are queued. They are stored straight in the database and a message will be sent to RabbitMQ to trigger the sending. There is no processing done in the foreground on those messages.
If you have speed issues there it is likely down to database, disk or RabbitMQ performance rather than anything in the software.

authors: adamcooke alexroosenstein

repo: atech/postal


text:
how to send emails as part of a thread vs new thread?

hi all, i'm using postal through my work and we want to make sure that when we send certain emails, that they get delivered as "replies" in a thread vs brand new emails.
doing some testing, i see that if the subject lines match... then the email will fall into a reply and will collapse under the main email (this is gmail/inbox). i will be doing some testing on yahoo/oulook after submitting this issue.
i do see that when sending an email, i get a messageId in the response data.  can I use this message id to force a reply to a thread?
or is it possible that every email client treats emails differently?
thanks for any help!!!!

is it as simple as just making the subject "Re: ${oldSubject}"

or is it possible that every email client treats emails differently?

Thats exactly it.
This isn't really a Postal issue, no one can guarantee that emails received will be threaded.


text:
Duplicate knob created at top-left corner of container on Android 4.3 after changing knob value

This only happens on Android 4.3 (I tried it on Android 4.1 and it worked fine). As soon as you try to change the knob from its initial value, it creates a duplicate knob. I have no idea how to get rid of it.
Additionally, it doesn't update the input value on release. The val stays the same.

Hi,
same issue here, are there any updates, workarounds or fixes available?
Thanks.

authors: garrett-gottlieb michaelkoehne

repo: aterrien/jQuery-Knob


text:
Dynamically adding JQuery Knob

Does anyone know how to configure dynamically added jQuery Knobs? I have several knobs in a bootstrap Collapse element, whose content html is dynamically loaded from a file when activated.
The problem is, my knob configuration happens on page load, as I also have knobs outside collapses on the main page; this means that the knobs inside the collapse simply load as input boxes as they are not configured.
Can't figure out a way round this, so any help would be appreciated!

You can call $('your element').knob(...) after your elements are rendered instead of on documentready. Then if you want to change value, call $('your element').val(newValue).trigger('change');

Thanks @zxfrank, this worked great, should have figured this out from the demo!

Actually... I failed to notice that though the knobs are now configured as knobs (whereas before they were simply rendered as an input box), the change callback does not get called when the knob is moved.
My knob (as part of a larger chunk of html with some other elements) is dynamically loaded as below:
    $.get("Content/Steps/steps_B.html", function( content ) {
      document.getElementById("seq_row_B_"+row).innerHTML = content;
      $('.knob-dyn').knob();
    });

and my knob() function (which works for all non-dynamically loaded knobs) is as below:
$(".knob").knob({
'change' : function (value) {
if(manTrigger === 0)
handleKnobEvent(this, value);
},
'release' : function (value) {
if(manTrigger == 1)
manTrigger = 0;
}
});//knob
Any thoughts would be greatly appreciated
Tia

authors: cSmout zxfrank


text:
hugo main build incorrect path for css

incorrect path in public/index.html
line 19

and after deployment, my github page look like this

after I fix the path, everything is ok

Hey, Thanks for opening the issue. Can you share your config file.

https://github.com/supercaizehua/blog-resources/tree/master/supercaizehua

Just add a trailing /   to your baseURL
https://github.com/supercaizehua/blog-resources/blob/d3bd36db7929acb8558afb6cf314c4f429bb0496/supercaizehua/config.toml#L1

problem solved

authors: athul supercaizehua

repo: athul/archie


text:
Not validating minItem for enum

I have the following schema definition
        "user": {
            "title": "User",
            "type": "object",
            "additionalProperties": false,
            "properties": {
                "pNumber": {
                    "type": "string",
                    "minLength": 3,
                    "maxLength": 30
                },
                "org": {
                    "type": "string",
                    "minLength": 3,
                    "maxLength": 30
                },
                "enabled": {
                    "type": "boolean"
                },
                "userRoles": {
                    "type": "array",
                    "uniqueItems": true,
                    "minItems": 1,
                    "maxItems": 7,
                    "items": {
                        "type": "string",
                        "enum": [
                         "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                        ]
                    }
                }
            },
            "required": [
                "pNumber",
                "org"
            ],
            "example": {
                "pNumber": "Excepteur amet dolore elit au",
                "org": "anim ad",
                "enabled": true,
                "useRoles": [
                          "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                ]
            }
        },
        "users": {
            "title": "Users",
            "type": "array",
            "items": {
                "$ref": "#/definitions/user"
            },
            "example": [
                {
                    "pNumber": "proiden",
                    "org": "nisi"
                },
                {
                    "pNumber": "dolor qui",
                    "org": "cupidatat",
                    "userRoles": [
                        "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                    ],
                    "enabled": false
                },
                {
                    "pNumber": "occaecat in dolore ad",
                    "org": "ex cons",
                    "enabled": true,
                    "userRoles": [
                            "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                    ]
                },
                {
                    "pNumber": "tempor sed deserun",
                    "org": "labore Excepteur eiusmod qui e",
                    "userRoles": [
                         "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                    ]
                },
                {
                    "pNumber": "id v",
                    "org": "dolor q",
                    "userRoles": [
                         "admin",
                        "orgadmin",
                        "superadmin",
                        "publisher",
                        "consumer"
                    ]
                }
            ]
        }
    }

userRoles in an enum with minItems=1. The following should not validate as no values are present in userRoles.
{
"pNumber": generated_pNumber.toString(),
"org": "ese",
"enabled": true,
"userRoles": [
]
}
However this passes validation which is not correct behaviour

We do not currently validate against the minItems or maxItems of an array.  I'll look at how we can add that.

Hi @brodyd , can you please push this for 2.x as well?

3.0.4 is completely compatible with 2.x so you could update it.

I will test this today with 3.0.4.

Swagger 2.0 is working with all my test cases for version 3.0.4

Excellent!  I'll update the readme so it is clearer

authors: brodyd gauravve


text:
Attachment enhancements

Tweaked a bunch of styles.
Added SoundCloud.
Added inline YouTube videos.
Made the Twitter attachments more complete.

/cc @atmos

authors: atmos fabianperez

repo: atmos/electrogram


text:
🛑 AtmoVantage Appointment Booking is down

In 626b567, AtmoVantage Appointment Booking (https://booking.atmovantage.com/#/customer/schedule) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AtmoVantage Appointment Booking is back up in ed0befa.

repo: atmovantage/atmostatus


text:
Added metadata data in documents mock

In order to test code which use metadata, it's necessary to add metadata map to documents mockup

Thank you for the PR and for going as far as updating the changelog @zariweyo! Would you mind adding a unit test to test the code, and also demonstrate how one would use your feature?

Thank you for the PR and for going as far as updating the changelog @zariweyo! Would you mind adding a unit test to test the code, and also demonstrate how one would use your feature?

As you suggested, I add a test to check metadata.

Thank you @zariweyo, I will release it at the same time as #145, some time this weekend.


text:
Console Crash

When pushing 1000 items to localStorage atom-shell crashes

I tried to push items with following code but it works fine:
for (var i = 0; i < 10000; ++i)
  localStorage[i] = i;

Which platform are you using?

It appears it was actually due to an overload of console.log messages. atom-shell will crash if you do for (var i = 0; i < 10000; ++i)
console.log(i);

I can not reproduce on Windows and OS X, which platform and what is version of atom-shell are you using?

Sorry for the later reply. I ran into the error on Mac OS X Yosemite and the latest release version of atom-shell.

Can you paste the crash report here? You should be able to find it in Console.app.

I'm closing this unless there is more information.

In case this is still relevant, it crashes for me as well. The following code makes it crash. Funny enough, for me it crashes as soon as I do 1790 or more loops.
https://gist.github.com/aperc/a8649a406e54115abbf9
electron version is 0.28.3
OS X Yosemite 10.10.3

Additional info, only happens if run through the electron drag & drop GUI. Running the app through the console works fine.

authors: aperc marcus433 zcbenz

repo: atom/atom-shell


text:
Uncaught Error: Replacing non-existent child when trying to split panes

Possibly related to https://github.com/atom/atom/issues/14616

view > panes > split right

None of the splits work, neither from the view-menu nor keyboard shortcuts.
Atom: 1.19.6 x64
Electron: 1.6.9
OS: Mac OS X 10.12.5
Thrown From: Atom Core
Stack Trace
Uncaught Error: Replacing non-existent child
At /Applications/Atom.app/Contents/Resources/app/src/pane-container.js:145

Error: Replacing non-existent child
    at PaneContainer.replaceChild (/Applications/Atom.app/Contents/Resources/app/src/pane-container.js:145:47)
    at Pane.module.exports.Pane.split (/Applications/Atom.app/Contents/Resources/app/src/pane.js:984:27)
    at Pane.module.exports.Pane.splitRight (/Applications/Atom.app/Contents/Resources/app/src/pane.js:964:25)
    at HTMLElement.pane:split-right-and-copy-active-item (/Applications/Atom.app/Contents/Resources/app/src/register-default-commands.js:269:38)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:265:35)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:3:65)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:166:25)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchApplicationMenuCommand (/Applications/Atom.app/Contents/Resources/app/src/atom-environment.js:1338:34)
    at EventEmitter.outerCallback (/Applications/Atom.app/Contents/Resources/app/src/application-delegate.js:334:31)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:194:7)

Commands
     -0:43.5.0 project-manager:list-projects (atom-pane.pane.active)
     -0:41.5.0 core:move-down (input.hidden-input)
     -0:41.1.0 core:confirm (input.hidden-input)
  2x -0:41 tree-view:show (atom-workspace.workspace.scrollbars-visible-when-scrolling.theme-one-dark-syntax.theme-one-dark-ui)
     -0:24.2.0 editor:fold-at-indent-level-1 (input.hidden-input)
     -0:13.2.0 pane:split-right-and-copy-active-item (input.hidden-input)

Non-Core Packages
advanced-open-file 0.16.6
atom-beautify 0.30.5
atom-html-preview 0.2.2
atomic-emacs 0.12.1
bug-report 0.7.1
busy-signal 1.4.3
color-picker 2.2.5
counter 0.3.5
emmet 2.4.3
file-icons 2.1.11
file-watcher 1.2.6
git-time-machine 1.5.9
goto-definition 1.3.4
intentions 1.1.5
language-cython 0.3.0
language-latex 1.1.1
language-restructuredtext 1.1.0
latex 0.46.0
linter 2.2.0
linter-chktex 1.3.1
linter-flake8 2.2.1
linter-markdown 5.2.0
linter-ui-default 1.6.8
MagicPython 1.0.12
markdown-scroll-sync 2.1.2
markdown-writer 2.7.2
merge-conflicts 1.4.5
minimap 4.29.6
minimap-cursorline 0.2.0
pdf-view 0.59.0
pretty-json 1.6.4
project-manager 3.3.5
python-indent 1.1.0
rst-preview-pandoc 0.1.12
Sublime-Style-Column-Selection 1.7.4
symbols-tree-view 0.14.0

Thanks for the report!  Can you reproduce in safe mode (atom --safe)?  Also, are your steps to reproduce the same as https://github.com/atom/atom/issues/14616#issuecomment-325599119?  I.e. do you have to start an empty window, add a project, open a file, then split?  Or is any attempt at splitting generating an error for you?
After making sure to save any unsaved work, does clearing saved state clear things up for you?
http://flight-manual.atom.io/hacking-atom/sections/debugging/#clearing-saved-state

Hmm.  I haven't been able to reproduce the problem which first occurred after a (hard) reboot.  Normal restarts since then also haven't reproduced the problem.  It's probably safe to assume that something got corrupted at the time, but there isn't a general issue.  Sorry I didn't confirm before posting, but I'll close this for now --- and update if the issue returns!

Well, with me the error seems to persist even after a hard reboot.
It works well when i start Atom with the safe flag though.
Will try to narrow down a possible plugin incompatibility

... Open Atom
... Try to split Editor

Atom: 1.19.7 x64
Electron: 1.6.11
OS: linux 4.12.12-1-ARCH
Thrown From: Atom Core
Stack Trace
Uncaught Error: Replacing non-existent child
At /usr/lib/atom/src/pane-container.js:141

Error: Replacing non-existent child
    at PaneContainer.replaceChild (/usr/lib/atom/src/pane-container.js:141:41)
    at Pane.module.exports.Pane.split (/usr/lib/atom/src/pane.js:982:21)
    at Pane.module.exports.Pane.splitRight (/usr/lib/atom/src/pane.js:962:19)
    at HTMLElement.pane:split-right-and-copy-active-item (/usr/lib/atom/src/register-default-commands.js:267:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/lib/atom/src/command-registry.js:265:29)
    at /usr/lib/atom/src/command-registry.js:3:59
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/lib/atom/node_modules/atom-keymap/lib/keymap-manager.js:606:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/lib/atom/node_modules/atom-keymap/lib/keymap-manager.js:397:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/usr/lib/atom/src/window-event-handler.js:100:36)
    at HTMLDocument.<anonymous> (/usr/lib/atom/src/window-event-handler.js:3:59)

Commands
     -0:40.9.0 application:reopen-project (input.hidden-input)
     -0:35.3.0 intentions:highlight (input.hidden-input)
     -0:35.1.0 pane:split-right-and-copy-active-item (input.hidden-input)

Non-Core Packages
atom-beautify 0.30.5
autocomplete-fortran 0.9.5
autocomplete-python 1.10.2
autocomplete-R 0.6.0
busy-signal 1.4.3
color-picker 2.2.5
ctrl-dir-scroll 0.2.5
git-plus 7.9.3
highlight-selected 0.13.1
intentions 1.1.5
intentions-colorpicker 1.0.1
kite 0.41.0
language-latex 1.1.1
language-markdown 0.25.1
language-matlab 0.2.1
latex 0.46.0
latextools 0.8.5
linter 2.2.0
linter-docker 0.2.1
linter-matlab 1.1.0
linter-pylint 2.1.0
linter-sass-lint 1.7.6
linter-scss-lint 3.1.1
linter-spell 0.15.0
linter-spell-latex 0.10.0
linter-ui-default 1.6.8
markdown-writer 2.7.2
minimap 4.29.6
minimap-cursorline 0.2.0
minimap-find-and-replace 4.5.2
minimap-git-diff 4.3.1
minimap-highlight-selected 4.6.1
minimap-linter 2.0.2
script 3.15.0
sync-settings 0.8.3

it's the minimap-cursorline package. don't know why, but disabling
the package solves the error. It is already reported here: Issue 3 ... or rather here

Ahhh, awesome thanks for dropping that note @julian-carpenter :+1:

[Enter steps to reproduce:]

Open
Try to split

Atom: 1.21.1 x64
Electron: 1.6.15
OS: Mac OS X 10.13
Thrown From: Atom Core
Stack Trace
Uncaught Error: Replacing non-existent child
At /Applications/Atom.app/Contents/Resources/app/src/pane-container.js:145

Error: Replacing non-existent child
    at PaneContainer.replaceChild (/Applications/Atom.app/Contents/Resources/app/src/pane-container.js:145:47)
    at Pane.module.exports.Pane.split (/Applications/Atom.app/Contents/Resources/app/src/pane.js:998:27)
    at Pane.module.exports.Pane.splitRight (/Applications/Atom.app/Contents/Resources/app/src/pane.js:978:25)
    at Object.<anonymous> (/Applications/Atom.app/Contents/Resources/app/node_modules/tabs/lib/layout.js:50:33)
    at Object.end (/Applications/Atom.app/Contents/Resources/app/node_modules/tabs/lib/layout.js:56:16)
    at HTMLLIElement.TabView.element.ondragend (/Applications/Atom.app/Contents/Resources/app/node_modules/tabs/lib/tab-view.js:62:29)

Commands
     -0:59.5.0 intentions:highlight (input.hidden-input)
     -0:55.6.0 application:add-project-folder (input.hidden-input)
  2x -0:44.9.0 fuzzy-finder:toggle-file-finder (atom-pane.pane.active)
     -0:11.7.0 core:confirm (input.hidden-input)

Non-Core Packages
atom-beautify 0.30.5
atom-jest-snippets 1.1.1
atom-jinja2 0.6.0
atom-material-syntax-dark 1.0.0
atom-monokai 0.10.9
browser-plus 0.0.98
busy-signal 1.4.3
change-case 0.6.5
codemods 0.0.4
color-picker 2.2.5
dash-ui 0.4.3
docblockr 0.11.0
editorconfig 2.2.2
flow-ide 1.8.1
git-blame 1.3.1
git-plus 7.10.0
highlight-selected 0.13.1
hyperclick 0.1.5
intentions 1.1.5
javascript-snippets 1.2.1
language-babel 2.75.1
language-hugo 0.3.1
language-ini 1.19.0
language-markdown 0.25.1
language-swift 0.5.0
lcov-info 0.12.0
linter 2.2.0
linter-eslint 8.3.2
linter-flake8 2.2.1
linter-flow 5.6.1
linter-ui-default 1.6.10
loved-syntax 1.0.2
monokai-seti 0.9.0
node-debugger 1.10.1
pigments 0.40.2
prettier-atom 0.40.0
react-snippets 1.0.0
sort-lines 0.18.0
spacegray-atom-dark-syntax 1.3.2
sublime-block-comment 0.5.1

I'm having this issue regularly (v. 1.23.3).

@Recmo if you can reproduce in safe mode (atom --safe) and after clearing saved state 1 (make sure to save any unsaved work first), go ahead and open a new issue with the issue template filled out and we'll take a look.

authors: Recmo difelice julian-carpenter lzkelley rsese

repo: atom/atom


text:
Restore Previous Windows On Start is not working Atom 1.41.0 macOS

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
With the Core Setting "Restore Previous Windows On Start" set to "yes" or "always", when I click on the Atom Dock icon or run atom in the terminal my previous project is not restored. An empty editor opens.  Interestingly, the previous project that I want to be opened automatically is shown as the most recent entry under File > Reopen Project
Steps to Reproduce

Make sure the Core Setting "Restore Previous Windows On Start" is set to "yes" or "always"
Open a folder from File > Open OR Open a project from File > Reopen Project
Close the Atom window.  Optionally (does not make a difference) also quit Atom. (on macOS, so the application does not automatically quit when the window is closed.)
Click on the Atom icon in the Dock OR run atom from the terminal.

Expected behavior:
The previous window will be restored on start.
Actual behavior:
An empty window is opened.
Reproduces how often:
100%
Versions
$ atom --version
Atom    : 1.41.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0
$ apm --version
apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.41.0
python 2.7.16
git 2.20.1
macOS Mojave Version 10.14.6
Additional Information
I found some similar, closed tickets for older versions of Atom. None of the suggestions in them helped.  I can reproduce this in safe mode.  I have checked permissions for various files and folders.  I ran mv ./Library/Application\ Support/Atom/IndexedDB ./Library/Application\ Support/Atom/IndexedDB.backup to get a new IndexedDB.  There are no error or any other messages in the developer console in the new blank window that opens.
I just noticed that while I have a project open, I get this:
$ cat ~/.atom/storage/application.json
{"version":"1","windows":[{"projectRoots":["/path/to/my/project"]}]}

as soon as I close the window, I get this:
$ cat ~/.atom/storage/application.json
{"version":"1","windows":[]}

It seems like this is what Atom needs to re-open the project.  Why would it delete it?

I have the exact same problem with macOS Catalina bêta 10.15 (19A573a)

Same problem here, on macOS Catalina 10.15.3. The problem also happens when running Atom in portable mode.

Same issue with macOS Catalina 10.15.4 and Atom 1.46.0.
(I've also unchecked "Open Empty Editor Start"

I've had the same experience. I've wasted and hour so will go off and find another editor. I did find that Atom uses IndexedDB and that there should be a directory /Library/Application Support/Atom/ to hold the db, but in spite of permission changes and reinstall, nothing ever appears in this directory.
Greg Ambrose

Any fixes for this so far @atom?

Yep :(
Atom    : 1.57.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1

Now it works all of a sudden. I didn't change any of Atom's settings, so it probably had something to do with my Arch install. atom --version's output is still the same.

Guy, same issue here
Ubuntu 20.04.2 LTS

Same issue
Atom    : 1.58.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1
macOS: 11.6

same here:
Atom    : 1.58.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1
macOS: 12.0.1

Same issue

Same
Atom    : 1.58.0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1
macOS:	11.6

Same
Ubuntu 22.04LTS
Atom 1.60.0

https://github.blog/2022-06-08-sunsetting-atom/
Not gonna get fixed it seems :( RIP atom

Is it still not fixed? Because it looks like it is not. Version 1.60.0. Linux Mint.

authors: ArkoMO93 CyborgPatrick akaskj brucelourenco formula1 glibg10b golottie-jens gregatreliance jherskow pierre-andre-long sagargulati samo-sato solongtony vlady88


text:
Uncaught Error: The module '/Applications/Atom.app/Contents/Resources/app.asar.unpacked/node_modu...

[Enter steps to reproduce:]

...
...

Atom: 1.46.0 x64
Electron: 4.2.7
OS: Unknown macOS version
Thrown From: Atom Core
Stack Trace
Uncaught Error: The module '/Applications/Atom.app/Contents/Resources/app.asar.unpacked/node_modules/oniguruma/build/Release/onig_scanner.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 70. This version of Node.js requires
NODE_MODULE_VERSION 69. Please try re-compiling or re-installing
the module (for instance, using npm rebuild or npm install).
At /Applications/Atom.app/Contents/Resources/app/static/<embedded>:11

Error: The module '/Applications/Atom.app/Contents/Resources/app.asar.unpacked/node_modules/oniguruma/build/Release/onig_scanner.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 70. This version of Node.js requires
NODE_MODULE_VERSION 69. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
    at Function.Module._load (internal/modules/cjs/loader.js:533:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:146745)
    at /app.asar/node_modules/oniguruma/src/oniguruma.js:3:21)
    at /app.asar/node_modules/oniguruma/src/oniguruma.js:116:3)
    at Module.get_Module._compile (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:147429)
    at Object.value [as .js] (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:150977)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
    at Function.Module._load (internal/modules/cjs/loader.js:533:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at customRequire (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:1:695134)
    at get_OnigRegExp (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:560449)
    at TreeSitterLanguageMode.regexForPattern (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:560508)
    at TreeSitterLanguageMode.decreaseIndentRegexForScopeDescriptor (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:559999)
    at TreeSitterLanguageMode.suggestedIndentForEditedBufferRow (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:551098)
    at TextEditor.autoDecreaseIndentForBufferRow (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:58863)
    at Selection.insertText (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:539496)
    at s.mutateSelectedText.n (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:15695)
    at getSelectionsOrderedByBufferPosition.map (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16220)
    at Array.map (<anonymous>)
    at transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:16209)
    at TextBuffer.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:492516)
    at TextEditor.transact (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:24215)

Commands
     -1:36 tree-view:duplicate (span.name.icon.icon-file-text)
     -1:07.0 core:paste (input.hidden-input)

Non-Core Packages

This just happened to me, immediately when I upgraded my TypeScript.
Just a quick restart of Atom helped me to overcome this.
I believe, restarting is opening up with all the newly updated version.
Maybe an auto-refresh can be performed when there is a version change.

@GSThina Thank you for letting us know that the issue has been resolved. I encourage you to open an issue describing the auto-refresh feature you are suggesting in the comment. For now I will close this and mark it as resolved.

I got the same issue but with nslog package. Seems like the right explanation why in happens is here: #19646
As I understand it right, atom ships with it's own nodejs distribution and running script/bootstrap will install packages using that own npm version, so that version mismatch happens when atom binary was compiled using nodejs version different from that one, that is in current sources.

authors: GSThina andrewpavlenko eli-stewart sadick254


text:
[1.48.0] Don't work multi-cursor

Multi-cursor don't work in editor, although this param is on in settings:

I've turned it on and off a 100 times, but it didn't have any effect.
I looked at what is happening in atom keymap, and keybinding resolver.
In keymap i didn't find mention about ctrl-click. In keybinding resolver, also.
What i can do with this?

duplicate of #20803 should be fixed in #20804

Yes, doesn't work on version 1.48.0 (fresh installed, no package).
I back to 1.47.0
OS: Windows 10

authors: duboloms putude zanna-37


text:
Atom crashes at startup - MacOS 11.0,  "Big Sur”,  Apple Silicon

Prerequisites

[ X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom crashes on startup on the Apple ARM DTK  (Developer Transition Kit, ARM64), MacOS 11
Labels: Mac-BigSur
Labels: Mac-Arm64
Steps to Reproduce

Crashes at startup

Expected behavior:
Open Atom Editor
Actual behavior:
Crashes
Reproduces how often:
Every time.
Versions
I tried on all three different builds (Atom stable, beta and nightly) downloaded on 7/15/20
Stable Version
Atom    : 1.49.0
Electron: 5.0.13
Chrome  : 73.0.3683.121
Node    : 12.0.0
OS
MacOS 11.0,  "Big Sur”,  Apple Silicon, ARM64
Labels: Mac-BigSur
Labels: Mac-Arm64
Additional Information
Seems similar to issue with other Electron based applications.
Link to similar issue
https://bugs.chromium.org/p/chromium/issues/detail?id=1098899
The issue here is that Chromium hardcodes macOS page size to 4 KB, whereas on Apple silicon devices it's actually 16 KB. We managed to fix it in our fork of Electron by changing code that uses hardcoded page size: https://github.com/Unity-Technologies/electron/commit/79a9fa9f4619393b78a44a69f92b32070f473e83
*** when running in safe mode - from Stable Build
/Applications/Atom.app/Contents/MacOS/Atom --safe
<--- Last few GCs --->
<--- JS stacktrace --->
Fatal process OOM in insufficient memory to create an Isolate
20764
*** crash report from - Nightly Build
Process:               Atom Nightly Helper [5461]
Path:                  /Applications/Atom Nightly.app/Contents/Frameworks/Atom Nightly Helper.app/Contents/MacOS/Atom Nightly Helper
Identifier:            Atom Nightly Helper
Version:               0
Code Type:             X86-64 (Translated)
Parent Process:        Atom Nightly [5442]
Responsible:           Atom Nightly [5442]
User ID:               502
Date/Time:             2020-07-15 21:50:58.307 -0700
OS Version:            Mac OS X 10.16 (20A5299w)
Report Version:        12
Anonymous UUID:        046B23A9-EBF5-1015-D3CD-5146E2CA0F1E
Sleep/Wake UUID:       41F34368-CD91-48AC-8AEF-80C8680A17FE
Time Awake Since Boot: 170000 seconds
Time Since Wake:       49000 seconds
System Integrity Protection: enabled
Crashed Thread:        0  CrRendererMain  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Termination Signal:    Illegal instruction: 4
Termination Reason:    Namespace SIGNAL, Code 0x4
Terminating Process:   exc handler [5461]
Thread 0 Crashed:: CrRendererMain  Dispatch queue: com.apple.main-thread
0   com.github.Electron.framework 	0x00000001107f1cd2 0x10c7e1000 + 67177682
1   com.github.Electron.framework 	0x000000010da326f0 0x10c7e1000 + 19207920
2   com.github.Electron.framework 	0x000000010da32650 0x10c7e1000 + 19207760
3   com.github.Electron.framework 	0x000000010dab7a3b 0x10c7e1000 + 19753531

For reference, electron seem to be aware of this: https://github.com/electron/electron/issues/24319

It looks like Electron now has an official upgrade path for Apple Silicon https://www.electronjs.org/blog/apple-silicon

authors: DeeDeeG ThatGuySam pearcy


text:
Atom suddenly not launching anymore

Windows 8.1
So I built it just yesterday, and after initial hiccups it built successfully and launched fine. Ran it a few times, used it for a few code files to play around, and then also installed one or two packages (javascript-related code completion etc).
Now, out of nowhere, it won't launch an editor window anymore. It opens partially in the task bar:

But no actual window opens, no matter how often I click on the partial snippet in the task bar, or alt-tab to it.
And if I try to run it from command line, I get this error:

[11128:0607/235050:ERROR:crash_reporter_win.cc(69)] Cannot initialize out-of-process crash handler"

I suppose I'll have to re-build it, which will probably fix this. I just wanted to log the issue.
Update: I have just rebuilt it from scratch. Still the same issue.
I suppose that points at something outside of Atom being wrong.

Is there an upstream (on electron repo) issue for it? Because my own application runs into the same error

authors: MTRNord batjko


text:
PackageState doesn't change when ProjectPath is changed programitcally

console.log(atom.packages.packageStates) //<-- have a look at it
atom.project.setPaths(['/var/www']) // <-- change it to any other project
console.log(atom.packages.packageStates) //<-- same

The property atom.packages.packageStates isn't part of Atom's public API; it's for internal use only. Can you explain why you're using it? There might be a different way to achieve what you're going for.

I am using it in a package which re-opens the last opened project.
I wanted to use atom.packages.packageStates to get the serialized data I have for that project. Opened files for example.
Because I need Opened Files for the Project that I set myself, not the default one, the state I get on activation is useless.

You shouldn't use atom.packages.packageStates for this. It has nothing to do with the project paths. There's no reason for it to change when calling project.setPaths.

authors: maxbrunsfeld steelbrain


text:
crash: closing modified file consistently crashes atom

Whenever I change a file opened in atom and then try to close it without saving it, atom crashes. This has been going on for months, so I suspect it has to do with my system and its gtk lib: I am using Debian unstable, libgtk2.0-0 amd64 2.24.25-3
I am always pulling and building from the latest atom git repo.
Here is the log:
/usr/local/bin/atom: line 98:  8718 Segmentation fault      nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[8718:0305/112908:ERROR:browser_main_loop.cc(164)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on.
MESA-LOADER: could not create udev device for fd 13
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[8747:0305/112908:INFO:renderer_main.cc(211)] Renderer process started
App load time: 217ms

[8718:0305/112927:INFO:CONSOLE(175)] "Upgraded the following syntax theme selectors in `.atom/packages/monokai-extended/index.less` for shadow DOM compatibility:

`.editor, .editor .gutter` => `:host, :host .gutter`
`.editor.is-focused .cursor` => `:host(.is-focused) .cursor`
`.editor.is-focused .selection .region` => `:host(.is-focused) .selection .region`
`.editor.is-focused .line-number.cursor-line-no-selection, .editor.is-focused .line.cursor-line` => `:host(.is-focused) .line-number.cursor-line-no-selection, :host(.is-focused) .line.cursor-line`
`.editor .gutter .line-number.git-line-added, .editor .gutter .line-number.git-line-modified, .editor .gutter .line-number.git-line-removed` => `:host .gutter .line-number.git-line-added, :host .gutter .line-number.git-line-modified, :host .gutter .line-number.git-line-removed`

See the upgrade guide for information on removing this warning.", source: /usr/local/share/atom/resources/app/src/styles-element.js (175)
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gdk: Offscreen windows not supported with native-windows gdk
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gdk: IA__gdk_window_set_user_data: assertion 'GDK_IS_WINDOW (window)' failed
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gtk: IA__gtk_style_attach: assertion 'window != NULL' failed
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gtk: IA__gtk_style_set_background: assertion 'GTK_IS_STYLE (style)' failed
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] GLib-GObject: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gtk: IA__gtk_style_attach: assertion 'window != NULL' failed
[8718:0305/112932:ERROR:browser_main_loop.cc(210)] Gtk: _gtk_style_peek_property_value: assertion 'GTK_IS_STYLE (style)' failed
Crash dump id: 3b8d71ca-c401-4229-9a00-e206b7664cd8

If you need any other information, please let me know.

one more thing: starting atom in safe mode won't help--either when closing the changed file with Ctrl-W or when quitting atom, I will still get a segmentation fault.

Wow! I finally found the key: unset GDK_NATIVE_WINDOWS and it will work! Eclipse needed that many years ago and I still had it set.

I get this issue on Windows when I swap branches in git and then close a file that no longer exists.
The correct message appears as follows.
'' has changes, do you want to save them?
Your changes will be lost if you close this item without saving.
Options are ,  and <don't save>
If I choose <don't save> then all open Atom windows crash! It is not consistent, I cannot reliably reproduce it.

authors: ggstuart michael-brade