Writing workflow / timeline

We now have a draft list of 10 issues.  Let's set a goal of writing them up in 2 weeks, e.g. drafts up in the repository by April 23rd.  Any issues that people don't assign themselves to I'll try and write.  There are still a couple unassigned issues.  So if there's an issue you'd like to take on, please assign yourself.  If the issue is already taken, please volunteer to help in the comments.  Most 10 simple rules paper rules tend to bet about 150-300 words and 1 to 2 paragraphs.  Obviously feel free to write more or less than that, it's just a guideline.
Thanks for all your work everyone.
Rough Timeline

April 23rd paragraphs written
April 30th Draft assembled
May 7th comments on assembled draft

I notice that your makfile autogenerates LaTeX and PDF from the Markdown source. This is really neat! Is there any particular reason for having the generated files (.tex, .aux, .out, .dvi, .pdf, .lg, .out) committed to the repository? This confused me at first, and it has the potential for the generated files to get out of sync with the MD text.
Also, I think it would be neat to have a make clean target to remove the generated files. Are you OK with me issuing a PR for that?

@emhart Since I don't have complete ownership on any of the rules, I can take a first pass once all the draft rules have been merged.  And if I am feeling it, I can attempt an intro.

What's the best way to comment on the assembled draft? New issues? comments on existing issues?
[Print it out, write on the paper, scan the paper, email it to everyone?]

The latter of course :laughing: Seriously though.  My first thought is that we should comment in the issue for the particular rule if you have have general comments.  However if you want to make edits to a rule, I'd make the edits, possibly add comments in the MD as HTML comments, and then submit a PR and ping the main author.  That way the author can discuss the changes to the manuscript with the editor.  But if people have other approaches they prefer please bring them up.

I'm about to go offline for a couple of weeks; I think I've made what useful comments I can, so please don't wait for me for the next step. Thanks all!

Thanks Pauline.  We're waiting for one last rule from Tim and then we'll
assemble the entire manuscript into a more coherent paper.
On Mon, May 18, 2015 at 10:13 AM Pauline Barmby<EMAIL_ADDRESS>wrote:

I'm about to go offline for a couple of weeks; I think I've made what
useful comments I can, so please don't wait for me for the next step.
Thanks all!
--
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103137666
.

Just out of curiosity, which rules is this? I think I submitted PR for 1 & 2, was I supposed to do a third one?
On Mon, May 18, 2015 at 10:15:58AM -0700, Edmund Hart wrote:

Thanks Pauline.  We're waiting for one last rule from Tim and then we'll
assemble the entire manuscript into a more coherent paper.
On Mon, May 18, 2015 at 10:13 AM Pauline Barmby<EMAIL_ADDRESS>wrote:

I'm about to go offline for a couple of weeks; I think I've made what
useful comments I can, so please don't wait for me for the next step.
Thanks all!
--
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103137666
.

Reply to this email directly or view it on GitHub:
https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103138936

It's rule 7 on privacy, which Tim Church is writing.  I've spoken with him
and he said he should have something within the next week.
On Mon, May 18, 2015 at 10:23 AM Timothée Poisot<EMAIL_ADDRESS>wrote:

Just out of curiosity, which rules is this? I think I submitted PR for 1 &
2, was I supposed to do a third one?
On Mon, May 18, 2015 at 10:15:58AM -0700, Edmund Hart wrote:

Thanks Pauline. We're waiting for one last rule from Tim and then we'll
assemble the entire manuscript into a more coherent paper.
On Mon, May 18, 2015 at 10:13 AM Pauline Barmby <
<EMAIL_ADDRESS>wrote:

I'm about to go offline for a couple of weeks; I think I've made what
useful comments I can, so please don't wait for me for the next step.
Thanks all!
--
Reply to this email directly or view it on GitHub
<
https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103137666

.

Reply to this email directly or view it on GitHub:

https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103138936
--
Reply to this email directly or view it on GitHub
https://github.com/emhart/10-simple-rules-data-storage/issues/42#issuecomment-103140746
.

Right, so the other Tim. Gotcha.


Add support for SOCKS proxies

Hi there,
Sorry for creating another feature request. I think it would improve the usability and so just adding here. In my experience socks proxies are faster than http proxies so it would be great if you could add support for them as well.
Currently, when I try to use them I get the following message:
javascript.errors.JavaScriptError: ('anonymizeProxy', 'Error: Invalid "proxyUrl" option: only HTTP proxies are currently supported.\n    at Object.anonymizeProxy (/path/venv/lib/python3.10/site-packages/javascript/js/node_modules/proxy-chain/dist/anonymize_proxy.js:28:15)\n    at Bridge.call (/path/venv/lib/python3.10/site-packages/javascript/js/bridge.js:136:42)\n    at Bridge.onMessage (/path/venv/lib/python3.10/site-packages/javascript/js/bridge.js:231:25)\n    at Socket.<anonymous> (/path/venv/lib/python3.10/site-packages/javascript/js/bridge.js:288:18)\n    at Socket.emit (events.js:400:28)\n    at addChunk (internal/streams/readable.js:293:12)\n    at readableAddChunk (internal/streams/readable.js:267:9)\n    at Socket.Readable.push (internal/streams/readable.js:206:10)\n    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)')

We actually use proxy-chain, because proxy-chain does not support socks, so the only option is to go with HTTP proxies. And Thank you very much for starring us, and creating GitHub Issues.
I really means a lot to me.


Hunt hwid unbann guide.

Hey IntelSDM, I heard your HWID got banned, so there's a free spoofer available on unknowncheats right now.
Motherboard spoofer: https://www.unknowncheats.me/forum/valorant/612562-vanguard-spoofer-rev-2-a.html
Hard disk spoofer video(skip to 2.50min): https://www.youtube.com/watch?v=YFxX3QSC--g
Just deinstall hunt with revo uninstaller to get rid of the tracers and no bios flash needed.
I hope you can add more features to the cheat now that you're unbanned.

Just install the game on the new hard drive you created and you're fine. I'm using this method for Hunt and Tarkov, no problems.

I have never been HWID banned in Hunt. Every time I just reformat my drive and reinstall windows and it bypasses the ban every time.


How should packit handle dependencies with overlapping stacks?

Background
Currently some buildpacks (e.g. CPython) have multiple dependencies with the same ID and version but with support for different, overlapping, stacks. In this situation, packit is sometimes picking the dependency with support for the * stack (i.e. wildcard) instead of the dependency with the more specific (matching) stack dependency.
This causes a problem because there is no requirement that the dependencies behave identically (e.g. in CPython, the dependency with * stack support is actually the Python source code and will be compiled dynamically by the buildpack, likely with different flags).
We thought we fixed this specific issue in #402 by ordering the * stack support lower than any other dependency, but we are still seeing packit selecting the wrong dependency in the CPython buildpack.
To generalize a little, the problem statement is:
Should packit support dependencies with overlapping stack support? e.g.:
[[metadata.dependencies]]
id = "some-dep"
version = "1.2.3"
stacks = ["stack_a", "stack_b"]

[[metadata.dependencies]]
id = "some-dep"
version = "1.2.3"
stacks = ["stack_b", "stack_c"]

What should packit do?
Essentially I see two options:

Make packit more robust to this situation. Deprioritize the * stack below specific stacks and (probably) use the order that the dependencies are listed in buildpack.toml as a final ordering once all other filtering/version-ordering/stack-ordering has occurred. The buildpack.toml ordering would act as a tie-breaker in the case where multiple dependencies match the current stack.

Pro: encapsulates this behavior in packit; does not require buildpack authors to handle anything special in their buildpack execution code
Con: It is complex to handle all the edge-cases that could potentially arise.
Con: leveraging the buildpack.toml ordering is not particularly intuitive.

Do not support multiple dependencies matching the provided stack at all. Instead, require buildpack authors to use different dependency IDs and push the decision of dependency-ID selection to the buildpacks. Once buildpacks have chosen a dependency ID, packit can resolve it as before.

Pro: it keeps packit simple
Pro: conceptually easier for buildpack authors to understand which dependency will be selected
Con: buildpack authors must duplicate some of the logic that could be abstracted within packit to choose a dependency before trying to resolve it via packit. It is possible that we will want to add helper methods to packit to facilitate these questions (e.g. "does the buildpack.toml have a dependency that matches this specific stack?") or change the current packit interface (e.g. do not error when there are no dependencies for a given stack)

Just a quick update - it seems that packit is now doing the correct thing. The issue with CPython was a bug in the integration test for the buildpack, not the buildpack itself.
I think that reduces the urgency of this issue to a more academic one, as we currently do not envisage any situation where we have overlapping stacks except the wildcard stack, and that is already handled by #402.

I think that overlapping stacks for dependency versions shouldn't be allowed outside of the * stack, and for the * stack, we should continuing with just deprioritizing it as we have now. I don't see why we should allow for two dependencies with the same version to have overlapping sets of stacks in any other case.

I feel that if you have 2 dependencies listed in the metadata with the same version and overlapping stack support, then it should not matter which version is chosen by packit. If its required to differentiate between these dependencies, then I'd argue you probably aren't talking about the same thing and you should consider option 2.
As for option 1, I am quite wary of us layering on more semantics to the existing stack ID. It is a very weak way to describe compatibility, especially when its allowed to be set to * which means basically nothing is being asserted as to whether this dependency will work.

@ryanmoran yeah, that does seem reasonable.
I think it would also be clearer in the buildpack code to differentiate between multiple different types of dependencies (e.g. pre-compiled vs source).
It seems reasonable for the buildpack to ask packit to resolve each set of dependencies separately - the logic would then look something like:

resolve "pre-compiled" dependencies for the current stack
resolve "source" dependencies for the current stack
If there is a pre-compiled dependency, use it.
If there is not a pre-compiled dependency, and there is a source dependency, use that (possibly emitting a warning that the build will take a while)
If there are no pre-compiled dependencies or source dependencies, fail with error.

I think it would also be clearer in the buildpack code to differentiate between multiple different types of dependencies (e.g. pre-compiled vs source).

This makes sense to me. It also probably simplifies the logic for updating buildpack.toml for pre-compiled dependencies and compile-from-source dependencies separately. @paketo-buildpacks/python-maintainers can you comment on how this is working currently in the cpython buildpack?

https://github.com/orgs/paketo-buildpacks/teams/python-maintainers can you comment on how this is working currently in the cpython buildpack?

Yeah, it's not ideal. the Cpython buildpack resolves all dependencies with ID: python for the current stack, and determines if it is a source package based on whether the URI and sourceURI are equal (code here). It works, and it's a sufficient discriminator for now but I think it would be better to be more explicit about which dependencies are source vs pre-compiled.
I opened this issue to address this for the various python buildpacks.

I think we can close this with the explicit (if slightly weasly) statement that packit's behavior is undefined for dependencies with overlapping stacks as described in the problem statement above.
If something changes and we feel the need to define the behavior, then hopefully we will have some additional context on whether we should support it or fail-fast.


Consider references when applying postfix completions

Sometimes my RA debugging workflow breaks because .dbg is applied to the variable that is used later in the code.
It's safer to consider the refences to avoid this for completions that may trigger the move.

bors r+


leverage AWS Cloud Control API

ListResource and DeleteResource from https://aws.amazon.com/blogs/aws/announcing-aws-cloud-control-api/ seem like an easier way to increase type coverage

Thanks for the suggestion! For what it's worth, we recently did an experiment with cloud-control that is documented here: https://github.com/gruntwork-io/cloud-nuke/issues/337
I'm going to close this ticket out for consolidation purposes, but will leave the linked issue up so we can continue to track the progress of cloud control.


Error: Invalid argument setting custom baud rate of 2400

I tried to run your code on a Raspberry Pi, connected to a PIP4048 inverter, on /dev/hidraw0 but got the following error:

root@grafpi:/solar-sis/solar-sis/example/PIP4084# node project.js
[2018-07-11 18:06:05] http localhost Listening on port: 3001
[2018-07-11 18:06:05] ERR! serial:/dev/hidraw0 Error: Error: Invalid argument setting custom baud rate of 2400
[2018-07-11 18:06:05] ERR! serial:/dev/hidraw0     at Error (native)
[2018-07-11 18:06:05] ERR! serial:/dev/hidraw0  { Error: Error: Invalid argument setting custom baud rate of 2400
[2018-07-11 18:06:05] ERR! serial:/dev/hidraw0     at Error (native)
[2018-07-11 18:06:05] ERR! serial:/dev/hidraw0   stack: 'Error: Error: Invalid argument setting custom baud rate of 2400\n    at Error (native)' }
root@grafpi:/solar-sis/solar-sis/example/PIP4084# dmesg | grep hidraw
[    0.796647] hidraw: raw HID events driver (C) Jiri Kosina
[    2.259217] hid-generic 0003:0665:5161.0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.3/input0

here's the history of commands I used:

320 mkdir /solar-sis
321 cd /solar-sis
321  sudo git clone https://github.com/opengd/solar-sis.git
322  cd solar-sis/example/PIP4084
323  ll
324  more package.json
325  more project.js
326  ll
327  more calls.json
328  ll
329  more calls.json
330  ll
331  more project.js
332  kk
333  ll
334  more session.json
335  sudo npm install --unsafe-perm
336  node project.js

Hi,
Do you know what could cause this?

Can someone please tell me what causes this error?

Above issue generally comes from a to new version of serial installed. We are working on an upgraded version but untill then you need to downgrade.

Thank you. What serial are you referring to? nodejs serialport? How do I dowgrade it? I have googled, but couldn't find a suitable answer.

sudo npm install<EMAIL_ADDRESS>--unsafe-perm this verison worked for me and be sure that you stop solar-pip in webmin before you update or you will get an error

I keep getting this message when installing older solar-sis or older serialport version. Am i doing something wrong?
node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v57-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v57 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v57-linux-arm.tar.gz

you are using serial port newer than 4.0.7...first of all are you using daromers imagr or did you install serial port on your own and what versiin of raspberry pi do you have....do you use stretch version of raspbian?

Use the older serial port driver instead. This version of solar-sis have had issues with the latest. Please retest

I have the same issue (on Dietpi , stretch). Downgraded node to lts/carbon, tried various serialport versions between 3.1.2 and latest. What specific version should it work with or any other solutions? (https://github.com/nrm21/skymax-demo works on /dev/hidraw0, but I'd rather use this project).

Found it, I had to update it in node_modules/solar-sis itself.
/solar-sis/example/5048GK/node_modules/solar-sis# npm i<EMAIL_ADDRESS>

I'm trying to get solar-sis working on a RPi 3 B+. I'm unable to downgrade to<EMAIL_ADDRESS>Getting messages that it's deprecated, unavailable, EOL, etc. Is there a source and a manual method to install 1.0.4?

gyp ERR! cwd /home/pi/solar-sis/example/PIP4084/node_modules/serialport
gyp ERR! node -v v10.19.0
gyp ERR! node-gyp -v v5.0.7
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1

Yeah I tried it now on another rpi, can't get it running anymore either...

I'm struggling to install<EMAIL_ADDRESS>on a R4, looks like download is no longer available:
pi@raspberrypi:~/solar-sis/example/PIP4084/node_modules/solar-sis $ npm i<EMAIL_ADDRESS>npm WARN npm npm does not support Node.js v10.24.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
npm WARN npm You can find the latest version at https://nodejs.org/

><EMAIL_ADDRESS>install /home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport
> node-pre-gyp install --fallback-to-build

node-pre-gyp info it worked if it ends with ok
node-pre-gyp verb cli [ '/usr/bin/node',
node-pre-gyp verb cli   '/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/node_modules/.bin/node-pre-gyp',
node-pre-gyp verb cli   'install',
node-pre-gyp verb cli   '--fallback-to-build' ]
node-pre-gyp info using<EMAIL_ADDRESS>node-pre-gyp info using<EMAIL_ADDRESS>| linux | arm
node-pre-gyp verb command install []
node-pre-gyp info check checked for "/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build/Release/serialport.node" (not found)
node-pre-gyp http GET https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
node-pre-gyp http 404 https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http 404 status code downloading tarball https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
node-pre-gyp verb command build [ 'rebuild' ]
node-pre-gyp ERR! Tried to download(undefined): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v64 ABI) (falling back to source compile with node-gyp)
node-pre-gyp http Connection closed while downloading tarball file
node-pre-gyp verb command build [ 'rebuild' ]

I when i use "npm i<EMAIL_ADDRESS>i got this error . any 1 know why ?

pi@raspberrypi:~/solar-sis/example/PIP4084/node_modules/solar-sis $ sudo npm i<EMAIL_ADDRESS>npm ERR! code 1
npm ERR! path /home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install --fallback-to-build
npm ERR! make: Entering directory '/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build'
npm ERR!   CXX(target) Release/obj.target/serialport/src/serialport.o
npm ERR! make: Entering directory '/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build'
npm ERR!   CXX(target) Release/obj.target/serialport/src/serialport.o
npm ERR! make: Leaving directory '/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build'
npm ERR! Failed to execute '/usr/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_path=/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build/Release' (1)
npm ERR! make: Leaving directory '/home/pi/solar-sis/example/PIP4084/node_modules/solar-sis/node_modules/serialport/build'
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>| linux | arm

There is a solution somewhere online to install that ver of serial, the newer Vers don’t work I believe

I think I managed to yarn that ver if I recall but it’s been some time


Gaps in markdown rendering in notebooks

System information:

CPUs
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1896)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.84GB (14.06GB free)

Process Argv

Screen Reader
no

VM
0%

Azure Data Studio Version:
Version: 1.11.0 (user setup)
Commit: 460c739a8d90bdbbde39e01abfb8ecdc278ea787
Date: 2019-09-06T18:08:50.974Z
VS Code 1.37.0
Electron: 4.2.9
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.16299

Steps to Reproduce:

Using this markdown (view raw to see the source)

Code block (3 backticks)

SELECT 42 AS TheAnswer

Inline Code with backticks

Tables
Are
Cool

col 1 is
left-aligned
$1600

col 2 is
centered
$12

col 3 is
right-aligned
$1

apt-get install dockerce

Get-ChildItem

in Preview Markdown, I see:

but in a notebook, the same markdown renders as:

Note that the block code has lost the language-specific color highlighting, the inline code is an (IMHO, ugly) red and the table has lost the right and center alignments, borders, etc.

Looked briefly into this and this has to do with the highlight method in markedOptions.
CSS is included for highlight.js but not the library itself in core, so we need to figure out if we should include that or not by default.
Otherwise, we'll need to figure out how to mesh vscode's syntax highlighting in editors with this css.


Make 1.1.0 release

1.1.0 release

https://github.com/raspberrypi/pico-sdk/releases/tag/1.0.1 was released on 1st Feb - why is this showing commits from 23rd Jan?

https://github.com/raspberrypi/pico-sdk/releases/tag/1.0.1 was released on 1st Feb - why is this showing commits from 23rd Jan?

because they weren't merged until after

Is this superseded by #234 ? :confused:


different read/write mbps

Scenario:
on baremetal:
16 cores
16 threads running
rw ~ 40~mbps
On Docker container on the same baremetal server:
restricted to 2 cores:
2 threads running
rw ~150 mbps
Why such different output behavior?

Also similar behaviour when increasing the core count of the docker to 16 cores

That is very interesting behavior — completely unexpected.
My first question is this: what's the underlying OS (the baremetal OS)? If it's Unix (macOS, Linux, *BSD), the output of uname -a would be helpful.
Also, since I see 16 cores I assume some type of Intel Xeon, or perhaps Ryzen? If Linux, cat /proc/cpuinfo, but you only need to attach the output of the first core. I'm trying to determine exactly what type of chip you're running.
And congratulations — you're the first person other than me using the code.

It's a Xeon processor with 16 cores. Will have the output to the command soon. It's running Ubuntu 16.04.

Thanks, this looks like https://ark.intel.com/products/92986/Intel-Xeon-Processor-E5-2620-v4-20M-Cache-2_10-GHz
I'm going to run similar tests on a similar vintage Xeon D I have to see if I can replicate the behavior.
Thanks for the charts by the way — it demonstrates that the difference in throughput is consistent (i.e. there's not some other process running that's "stealing" the IO).
I must admit I'm a little baffled — the test doesn't use much CPU at all, it's all I/O — so even if there was another process for contending for CPU cycles, it shouldn't make much of a difference. Also the synchronization shouldn't be a big deal, either — it only synchronizes after writing 64 kiB. so even if there was a little lag it should be fine, but maybe I'll focus on the synchronization. Stay tuned.

@yogeshVU  How much RAM? I'm guessing >= 32 GiB: 150 MB/s * 450 s = 67,000 MB =~ 64GiB data set size == 32 GiB RAM

with respect to the CPU graph, the graph is only for the docker percentage. So initial half is when the docker is not running and the second half when the tests are actually carried out inside the docker container.

Its having 32Gb
MemTotal:       32717372 kB
MemFree:        28445732 kB
MemAvailable:   31698292 kB

More server info:
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                16
On-line CPU(s) list:   0-15
Thread(s) per core:    1
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
Stepping:              1
CPU MHz:               1200.091
CPU max MHz:           3000.0000
CPU min MHz:           1200.0000
BogoMIPS:              4195.34
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0,2,4,6,8,10,12,14
NUMA node1 CPU(s):     1,3,5,7,9,11,13,15

I've been having difficulty recreating the slowdown you're seeing — although I see a drop-off in write performance when I use the full 16-threads, it's modest (1607 MB/s → 1282 MB/s), and I suspect it has more to do with the disk not being "warmed-up" (a follow-on run with 16 threads has an entirely reasonable 1563 MB/s).
Which leads me to ask the following: What is the type of disk you're testing? If you have a make and model, that's great, but if you only know, "it's a magnetic disk", that's good, too (I suspect it's magnetic because the throughput is too low for SSD).
I'm wondering if the mechanism I use — 16 threads spawns 16 different files being written simultaneously — is causing the disk head to thrash.
cunnie@artful:~/go/src/github.com/cunnie/gobonniego$ sudo go run gobonniego/gobonniego.go -v
2018/04/15 14:47:55 gobonniego starting. version: 1.0.9, runs: 1, seconds: 0, threads: 16, disk space to use (MiB): 7886
2018/04/15 14:47:55 Number of CPU cores: 16
2018/04/15 14:47:55 Total system RAM (MiB): 3943
2018/04/15 14:47:55 Bonnie working directory: /tmp/gobonniegoParent697368994
2018/04/15 14:48:01 Written (MiB): 7886
2018/04/15 14:48:01 Written (MB): 8269.070336
2018/04/15 14:48:01 Duration (seconds): 6.448985
Sequential Write MB/s: 1282.23
2018/04/15 14:48:07 Read (MiB): 7886
2018/04/15 14:48:07 Read (MB): 8269.070336
2018/04/15 14:48:07 Duration (seconds): 4.736989
Sequential Read MB/s: 1745.64
2018/04/15 14:48:23 operations 447000
2018/04/15 14:48:23 Duration (seconds): 15.005925
IOPS: 29788
cunnie@artful:~/go/src/github.com/cunnie/gobonniego$ sudo go run gobonniego/gobonniego.go -v -threads 8
2018/04/15 14:48:39 gobonniego starting. version: 1.0.9, runs: 1, seconds: 0, threads: 8, disk space to use (MiB): 7886
2018/04/15 14:48:39 Number of CPU cores: 16
2018/04/15 14:48:39 Total system RAM (MiB): 3943
2018/04/15 14:48:39 Bonnie working directory: /tmp/gobonniegoParent275247700
2018/04/15 14:48:44 Written (MiB): 7886
2018/04/15 14:48:44 Written (MB): 8269.070336
2018/04/15 14:48:44 Duration (seconds): 5.144056
Sequential Write MB/s: 1607.50
2018/04/15 14:48:50 Read (MiB): 7886
2018/04/15 14:48:50 Read (MB): 8269.070336
2018/04/15 14:48:50 Duration (seconds): 4.600640
Sequential Read MB/s: 1797.37
2018/04/15 14:49:05 operations 376895
2018/04/15 14:49:05 Duration (seconds): 15.004793
IOPS: 25118
cunnie@artful:~/go/src/github.com/cunnie/gobonniego$ sudo go run gobonniego/gobonniego.go -v -threads 4
2018/04/15 14:49:12 gobonniego starting. version: 1.0.9, runs: 1, seconds: 0, threads: 4, disk space to use (MiB): 7886
2018/04/15 14:49:12 Number of CPU cores: 16
2018/04/15 14:49:12 Total system RAM (MiB): 3943
2018/04/15 14:49:12 Bonnie working directory: /tmp/gobonniegoParent370520812
2018/04/15 14:49:17 Written (MiB): 7886
2018/04/15 14:49:17 Written (MB): 8269.070336
2018/04/15 14:49:17 Duration (seconds): 5.585691
Sequential Write MB/s: 1480.40
2018/04/15 14:49:24 Read (MiB): 7886
2018/04/15 14:49:24 Read (MB): 8269.070336
2018/04/15 14:49:24 Duration (seconds): 6.098622
Sequential Read MB/s: 1355.89
2018/04/15 14:49:40 operations 240497
2018/04/15 14:49:40 Duration (seconds): 15.000620
IOPS: 16032
cunnie@artful:~/go/src/github.com/cunnie/gobonniego$ sudo go run gobonniego/gobonniego.go -v -threads 2
2018/04/15 14:49:47 gobonniego starting. version: 1.0.9, runs: 1, seconds: 0, threads: 2, disk space to use (MiB): 7886
2018/04/15 14:49:47 Number of CPU cores: 16
2018/04/15 14:49:47 Total system RAM (MiB): 3943
2018/04/15 14:49:47 Bonnie working directory: /tmp/gobonniegoParent561904331
2018/04/15 14:49:57 Written (MiB): 7886
2018/04/15 14:49:57 Written (MB): 8269.070336
2018/04/15 14:49:57 Duration (seconds): 9.062680
Sequential Write MB/s: 912.43
2018/04/15 14:50:06 Read (MiB): 7886
2018/04/15 14:50:06 Read (MB): 8269.070336
2018/04/15 14:50:06 Duration (seconds): 9.144387
Sequential Read MB/s: 904.28
2018/04/15 14:50:21 operations 136038
2018/04/15 14:50:21 Duration (seconds): 15.000632
IOPS: 9069
cunnie@artful:~/go/src/github.com/cunnie/gobonniego$

Yes, you are correct. It does not have SSD drives.
Interesting results, wrt write throughput from the above experiments.
The IOPS shows linear scaling with the increasing thread count. But the write throughput is less for the 16 threads than that of the 8 threads.
Also, could you try running the same inside a docker container? and see if you are getting any changes to the write mbps. You could try with the minimal docker image based on alpine container to start, and repeat the above tests.
Thanks again.

I'm closing because it's been years.
Final notes: I suspect the baremetal-16-threads slowdown has more to do with threads than with Docker (i.e. a two-thread baremetal would be as performant as Docker container with 2 threads), but this is speculation.


Callback on array length change in editor

Hello !
Thank you for your work! That is really awesome !
I would like to know if there is a way to have an "OnChanged"  when length of an array instead of the item modification  (or a List) is modified ?
Edit : Actually I'm searching, and my real question is : Am I doing it well
Maybe I can extend ListDrawer and call a delegate in right function ? And add it to the TypeDrawerMapper ? Is it a good way ?
Thanks in advance !

You can use 'OnChanged' (See OnChangedExample.cs) - I tried it, it gave me notification when an array count changed, but not a list. So I did some modifications to make it work. See https://github.com/vexe/VFW/commit/4fedb85d33f4cd7a77a8710d56fb49b86d3c27b7 and https://github.com/vexe/VFW/commit/55a4b0ade5c23aa0f6c7f32583ba3e9979d4aea9
This should now work:

    [OnChanged("OnListChanged")]
    public List testList;
[OnChanged("OnArrayChanged")]
public GameObject[] testArray;

void OnListChanged(List<GameObject> list)
{
    Log(list.Count);
}

void OnArrayChanged(GameObject[] array)
{
    Log(array.Length);
}


Request: allow flexibility when editing

Issue
Occasionally I will get a bad edit and a new round of edits like:
<<<<<<< SEARCH

^^^ Bad/missing filename. The filename must be alone on the line before the opening fence

But in most cases there's only a single place where the search matches across all files in context. It would be great if those cases could be handled anyway (maybe with a confirmation from the user).
It feels like a waste of time to go back to the LLM if the match is unique in the project anyway.
Version and model info
Aider v0.50.1
Model: deepseek/deepseek-coder with ♾ diff edit format
Git repo: .git with 5 files
Repo-map: using 1024 tokens

Thanks for trying aider and filing this issue.
Aider is already extremely flexible about parsing replies from the LLMs. But yes, this is a possible enhancement that I've considered.


[Vulnerability] Cross site scripting (XSS) and Open Redirect on the login page

Description
The login page is vulnerable to open redirect and XSS attacks. An attacker can craft a seemingly valid URL and then trick the admin into clicking, after the admin authenticates the payload will run, which will :

Redirect the browser to any URL the attacker chooses. This can lead to phishing and credential theft.
Run javascript code inside the admin's browser. This can lead to unauthorized actions being performed, including but not limited to:
a. Create a new webui user with admin privileges, which can be used to takeover the entire application.
b. Create new clients, exfiltrate existing client config and send to attacker. This can lead to exposure of private network/servers, enabling further exploitation.

Cause
The function redirectNext in login.html does not check the value of 'next' parameters before redirecting:
    function redirectNext() {
        const urlParams = new URLSearchParams(window.location.search);
        const nextURL = urlParams.get('next');
        if (nextURL) {
            window.location.href = nextURL;
        } else {
            window.location.href = '/{{.basePath}}';
        }
    }

Steps to reproduce

Open redirect
Login URL: https://example.com:5000/login?next=/

Change the 'next' parameter to any url:
https://example.com:5000/login?next=https://malicious.domain
After logging in the user will be redirected to the malicious domain.

Cross site scripting:
Change the 'next' parameter to:

javascript:alert(1)

Screenshot

The fix
Check if the 'next' param is just a singular slash (/) or starts with a slash and a character. This will prevent payloads like these:
javascript:alert(1)
https://google.com
//google.com

Thanks @catmandx for reporting and fixing the issue. Merging it.


Update formatters.rst

https://github.com/TeamHG-Memex/eli5/pull/363 by @guyrosin

Thanks @guyrosin !

Thanks @guyrosin !


FIX: Multiply Defined Symbols

Fix multiply defined symbols linker error that occurs when IMeasurement or OMeasurement is used in two different translation units as the present method definition in the two header files violates the One Definition Rule.
Pull request type
Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
As method implementations for IMeasurement and OMeasurement are contained in the header file, multiply defined symbols errors will be thrown by the linker if the classes are used in two different translation units.
Issue Number: N/A
What is the new behavior?
Using the inline keyword, this error is fixed.
Does this introduce a breaking change?

[ ] Yes
[x] No

Other information
Alternative solutions would be implementing the method in the header definition directly or move them to cpp files instead.

@KerstinKeller: As I see it, this should not harm any API (but probably the ABI?), so it should be safe to merge to master. Can you confirm this?


Add better testing to module code

Currently, testing is conducted manually and across all modules using the account-init.sh script in https://github.com/RootPrivileges/terragrunt-aws . This is brittle and slow, taking a long time to run and failing in weird ways.
Adding robust testing, as Yevgeniy Brikman describes in https://www.infoq.com/presentations/automated-testing-terraform-docker-packer/, will make it easier to detect errors without needing to run the whole script. Additionally, this can be integrated with Gitlab Actions to run the tests manually on commits.
While implementing testing, also add other static analysis as referred to in the video (i.e. terraform validate, tflint, conftest) into the CI/CD pipeline as best practise.

https://www.terraform.io/docs/commands/fmt.html


The downloads path for release 0.6.0 snap does not match toolchain-installer.sh expectations

It seems all the previous releases had 'v' in front of the actual version number, and toolchain-installer.sh relies on it.
For some reason the release 0.6.0 is not found at the 'v0.6.0' path but it's '0.6.0', this breaks the toolchain-installer.

OK fixed.
Chose to adapt the toolchain installer for consistency.
https://github.com/openXC7/toolchain-installer/commit/d6365f9a4607aa3452697f71eae39fb638070e1b

Thanks for reporting this!


Error In Handling Delete Message

When a message Is deleted in From Channel (Chat A)
The Bot does not the delete that msg in To Channel (Chat B)
Edit Function is working Fine But Delete function doesn't
Please See And fix it as soon as Possible
Waiting for Positive Reply
Thank You

try to locate your config.py file and change
delete_sync: bool = False
to
delete_sync: bool = True

Bro I followed Your Instruction properly but it didn't work
please help me with different solution

Your config file should look like this
https://nekobin.com/jadicayufe
Replace xxx and yyy with your chats IDs.


Add support for creating shared domains

Currently, cf-mgmt can only create private domains (and then share them with named orgs). It would be awesome if we could specify shared domains too.
(Our workaround for this was to add a shared_domains array to cf-mgmt.yml and use the CF CLI to create them.)

There be dragons here.
Before you use shared domains, be really, really sure you want them. In PCF 1.10 you could only have one org doing path-based routing on a shared domain. Once one org had a path-based route mapped, no other orgs could do any path-based routing.
This may no longer be an issue in PCF 2.0 but I strongly suggest you do your research before using shared domains.
Alternatively, create private domains and share them between orgs.

Hi,
As PCF 2.0 support shared domains now, is possible to support shared domain creation now?
Thanks.

Released 1.0.12 (https://github.com/pivotalservices/cf-mgmt/releases/tag/v1.0.12)


Proposal: add .editorconfig to enforce style on non-source files

After some discussion on a separate PR regarding the EOL at the end of the swagger.yml file, it would probably be a better use of time to automate style enforcement for YAML and other non-source files.
As far as I'm aware, EditorConfig is as close to a standard tool as we'll get there. Many editors support it already, and many other editors support EditorConfig through a plugin.
For that particular case of the trailing newline, it looks like the config would be as simple as:
[*.yaml]
insert_final_newline: true

There are standalone implementations that we could use as a CI step to enforce the rules outside of an editor.

This is a great idea. Without giving this much thought, it would be helpful to use an implementation that is easily brewd or apt-getd.

I did stumble across https://github.com/editorconfig-checker/editorconfig-checker, which is written in Go, but which was not listed in the standalone implementations part of EditorConfig's wiki. If we do this proposal, and if that project is a good fit, we can add it to the other tooling dependencies of influxdb, since installing Go binaries is a solved problem for us.


Integrate form fyxer

Worth getting some early eyes on this.
This adds a normalize form fields option for PDF forms. It also adds a dialog that allows you to manually rename fields to make spot corrections, and we're using an embedded PDF so someone can more easily locate fields on the PDF.
The UX could be a lot better--e.g., there's no way to view the labels of checkbox fields since they are too small. The best UX would not be very easy to achieve in Docassemble. But this should still be very helpful.

I forgot to check beautifulsoup4 as a dependency for the draggable table module. Could you add it before you merge this PR? Thanks!

I'll put that in a separate PR


(#817) Add missing redirects

Description Of Changes

Change firewall rules redirect

Motivation and Context
Ensure the redirects for all docs removed work properly.
Testing

[X] I have previewed these changes using the Docker Container or another method before submitting this pull request.

Change Types Made

[X] Minor documentation fix (typos etc.).
~[ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).~
~[ ] New documentation page added.~
~[ ] The change I have made should have a video added, and I have raised an issue for this.~

~Issue #~

Change Checklist

~[ ] Requires a change to menu structure (top or left hand side)~
~[ ] Menu structure has been updated~

Related Issue
#817

@ryanrichter94 thanks for getting this fixed up!


Colour theme is being displaying too light

Issue Type: Bug
I'm using a custom colour theme that I wrote myself to customise the editor's colours and when loaded the background colour (and perhaps others) is incorrectly displayed. It seems too light.
Here is my colour theme:
https://github.com/nomad-software/vscode/tree/master/freya-theme
In that colour theme the background colour is defined as:
"editor.background": "#2A2A2A",

But when screenshotted and measured in GIMP it's #2E2E2E.
In other editors such as Vim it displays correctly.

We set the RGB to the DOM or styleheet and that's how the Chromium engine(part of Electron) renders it.

Well, something's going wrong somewhere because it's not correctly displaying the color.

Color rendering is a complex topic. The Chromium engine renders the colors based on your monitor's color profile monitor. I don't know what VIM does.
To make sure this is not caused by VSCode, I opened the following html-page in Chrome and verified that there are no color rendering differences. I did it on Ubuntu 18.04.3 LTS.
<html>
    <body style="background-color: #2A2A2A"></body>
</html>

If you are convinced that it's wrong what Chrome does, please file an issue against Chromium.

Chromium isn't the issue as that renders fine as you have demonstrated.
Change your vscode background to:
"editor.background": "#2A2A2A",

then screenshot it, then measure it.
vscode (and only vscode) doesn't display as #2A2A2A. Every other application or editor displays it fine.

I've just tested it again and screenshotted a load of applications, including the webpage you posted above. All display properly as #2A2A2A apart from vscode.

Ok, I've just update to the latest version of vscode and it's fixed! It looks like something has been changed in the newer version. Nevermind, alls good now.


Fix issue with YAML requiring deep construct

When not using deep construct, some mutable types may not be populated e.g. model lists. This change forces deep construct when creating components.

Codecov Report

Merging #230 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #230   +/-   ##
=======================================
  Coverage   92.32%   92.32%
=======================================
  Files         122      122
  Lines        4598     4599    +1
  Branches      682      682
=======================================
+ Hits         4245     4246    +1
  Misses        251      251
  Partials      102      102

Impacted Files
Coverage Δ

stonesoup/serialise.py
97.34% <100.00%> (+0.02%)
: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 cdd4052...c7c6ece. Read the comment docs.


LightGBM import error related to dll

Please search your question on previous issues, stackoverflow or other search engines before you open a new one.
Seems to be a similar issue to "LightGBM import error #499" and "[GPU] LightGBM import error again! nvidia OpenCL.dll not found #566." However, re-installing nvidia driver or re-cloning the latest build does not solve the problem.
For bugs and unexpected issues, please provide following information, so that we could reproduce on our system.
Environment info
Operating System: Windows 7
CPU: Intel i5-3750k
GPU: GeForce GTX 1070
C++/Python/R version:  Anaconda 4.3.21, Python 3.6.1
Error Message:
Please note that "print(lib_path)" is added at line 26 per #499 and #566.
['D:\Anaconda3\lib\site-packages\lightgbm-0.2-py3.6.egg\lightgbm\lib_lightgbm.dll']
OSError                                   Traceback (most recent call last)
 in ()
43 plt.style.use('seaborn-whitegrid')
44
---> 45 import lightgbm as lgb
D:\Anaconda3\lib\site-packages\lightgbm-0.2-py3.6.egg\lightgbm_init_.py in ()
7 from future import absolute_import
8
----> 9 from .basic import Booster, Dataset
10 from .callback import (early_stopping, print_evaluation, record_evaluation,
11                        reset_parameter)
D:\Anaconda3\lib\site-packages\lightgbm-0.2-py3.6.egg\lightgbm\basic.py in ()
30
31
---> 32 _LIB = _load_lib()
33
34
D:\Anaconda3\lib\site-packages\lightgbm-0.2-py3.6.egg\lightgbm\basic.py in _load_lib()
25         return None
26     print(lib_path)
---> 27     lib = ctypes.cdll.LoadLibrary(lib_path[0])
28     lib.LGBM_GetLastError.restype = ctypes.c_char_p
29     return lib
D:\Anaconda3\lib\ctypes_init_.py in LoadLibrary(self, name)
424
425     def LoadLibrary(self, name):
--> 426         return self._dlltype(name)
427
428 cdll = LibraryLoader(CDLL)
D:\Anaconda3\lib\ctypes_init_.py in init(self, name, mode, handle, use_errno, use_last_error)
346
347         if handle is None:
--> 348             self._handle = _dlopen(self._name, mode)
349         else:
350             self._handle = handle
OSError: [WinError 127] The specified procedure could not be found
Reproducible examples
Steps to reproduce

Also, I can run the testing in CLI without any issues.
/github_repos/LightGBM/examples/binary_classification
"../../lightgbm.exe" config=train.conf data=binary.train valid=binary.test objective=binary device=gpu

@frostmanfrost
if you can run it by cli, the possible reason is your python version is 32-bit.
Can you try to build without GPU, and try the install python-package ? The problem is in gpu side if this can work.

Thank you, guolinke.  Finally figured out the problem:  the dll chain broke at libstdc++-6.dll, which is in .../mingw64/bin.  Though the location was added to PATH, basic.py still could not load it.  Copying the dll to c:/windows/system32 solved the problem.


[k8s-extension] Fix bugs while removing azure-mgmt-relay SDK

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

k8s-extension

Follow the release process from AzureArcForKubernetes, we don't need it anymore.


show "paused" status of mistal workflow correctly in st2 command

mistal workflow is in "paused" state, while st3 execution command still shows workflow in  "running" state.
note: workflow is in paused state if includes  "pause-before: true" in a task.
reference:  http://docs.openstack.org/developer/mistral/dsl/dsl_v2.html#workflows

Has been lots of overhaul of pause/resume behavior. Don't think this applies any more.


java.lang.NullPointerException

Bug

Exception java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.Activity.runOnUiThread(java.lang.Runnable)' on a null object reference
at com.brentvatne.exoplayer.ReactExoplayerView$7$1.run (ReactExoplayerView.java:560)
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:644)
at java.lang.Thread.run (Thread.java:1012)
Platform
Which player are you experiencing the problem on:

Android

Environment info

Library version: 6.0.0-alpha.11
Device:  [Android 12 (SDK 31)]

Cloud you provide more informations ?

I think I know this issue. It should happen when you  start the app and directly stop it...
The action is null in the reactContext ...

I think I know this issue. It should happen when you start the app and directly stop it... The action is null in the reactContext ...

Yes @freeboub  you are right ..

Cloud you provide more informations ? Thank
this is random behaviour error  sometime it throwing this kind of error

I just double check, I think the crash has been fixed in last beta version.
Can you double check please ?
I cannot reproduce the crash on my side

@toorandroidmaster Can you confirm the issue is resolved in v6 beta3 ?


Netatmo binary sensor

Description:
This PR create a new platform which provides binary sensor based on event seen by the Netatmo camera
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#964
Example entry for configuration.yaml (if applicable):
binary_sensor:
   platform: netatmo
   home: home_name
   cameras:
     - camera_name1
     - camera_name2
   monitored_conditions:
     - Someone known
     - Someone unknown
     - Motion

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

You can use two aproches in order to use discovery:

automatic capability: check whether the discovered device has any capability reported
Or
manual capability detection: test them youself in the code to see if u have a camera, wheather or anything other capability

The last one could be done in the netdisco ant it would emit in your case only two entities discovered and then in HA two different components would listen for them and render them in the frontend

@rofrantz I used the second approach but it was not perfect as the Netatmo API will return all the devices that you own, but if you have one camera in one home and an another one in another home you might don't want to display both in you home-assistant interface.
My idea was to use the discovery if no specific camera has been setup in the configuration.yaml (then it will use the default camera), but if a camera is setup then discovery is ignored.

Still sounds like a custom setup meaning that u have 2 cameras in 2 different locations in the same HA instance; why dont u hide one of two entities if thats the issue or add a default camera flag.
Although as I read this again indeed its a custom setup with a delicate solution which would only complica the HA logic, so yeah we better drop it :)

This PR also fix an issue with voluptuous  that will be introduce by https://github.com/home-assistant/home-assistant/pull/3287 in release 0.29 https://github.com/home-assistant/home-assistant/pull/3486

🐬


Rewrote and extended the log parser.

This is a proposed improvement for #159. I think it is still not catching all warnings, but significantly more. A further improvement is a better determination for lastFile in the log.
The downside is that the parser now does two passes of the log instead of one.

I did not touch the whole arara part. Putting an arara log directly through the parser works.
However, when calling arara through atom-latex the build log only shows

arara --log  [file]
[arara ascii art]
Running PDFLaTeX... SUCCESS

Are you sure that this is a problem with the parser? If so: can you tell me how to get this to work so I can debug it?

Ah, you need to ask arara to log to the stdio - so  arara %DOC -v

I am seriously confused right now. For me this works with arara and latexmk.
The parser even finds the newly implemented hyperref warnings (this is a slight change of your MWE):
\documentclass{article}
\usepackage[utf8]{inputenc}
\usepackage{graphicx}
\usepackage{hyperref}

\begin{document}
\title{Minimal document for maximum testing.}
\maketitle

Section \ref{sec:SecA} is defined, but Section \ref{sec:secC} is still WIP.
\section{Section A: $F$igures}
\label{sec:SecA}
\begin{figure}[h]
\centering
 \includegraphics[width=.5\textwidth]{example-image-a}
 \caption{Standart Reification}
 \label{fig:ExampleA}
\end{figure}

\section{Section B: Todo}
\label{sec:SecB}

\end{document}

I obtain

I suspect this is a problem with my identification of tex files vs. Host OS. Could you provide me the full log for your MWE on your machine?

aha! The plot thickens! I am on Win10, here is the raw log

Yep, that fixed it!
Do you feel any other tests are needed or is it ready to merge?

Ok, there is some seriously evil magic going on here, that I do not understand.
As I suspected, the problem was input file name recognition. I searched for
(./
which is how input files begin in unix latex logs. However, the raw logs you showed me for win, there is no dot and slash (see line 12 in arara and line 8 in latexmk, where it is just
(minimal.tex
). However, this is why is it completely elusive to me the current parser works. Your screencaps proved that it correctly recognizes minimal.tex as the source of the warning. However the RegEx /^.*?\(\.\/(.*?\.\w+)/ simply does not match the line (minimal.tex, so there is something more going on.
That being said, it is kinda difficult to identify input files when allowing full generality. For example, overfull box warnings have
(9.43824pt too wide
which might go through as a file name, since it matches (.*?\.\w+).
I have commited a solution which works as long as the file endings of input files contain no digits. I currently have no better idea how to solve this problem.

However, this is why is it completely elusive to me the current parser works. Your screencaps proved that it correctly recognizes minimal.tex as the source of the warning. However the RegEx /^.?(./(.?.\w+)/ simply does not match the line (minimal.tex, so there is something more going on.

The file level warnings are captured by this parsing the warnings directly, that are generated by passing in the -file-line-error flag to the engine.
if result
        items.push
          type: 'error',
          text: if result[3] and result[3] != 'LaTeX' then \
                """#{result[3]}: #{result[4]}""" else result[4],
          file: if result[1] then \
            path.resolve(path.dirname(@latex.mainFile), result[1]) else \
            @latex.mainFile
          line: if result[2] then parseInt result[2], 10 else undefined

Hence for an error in \include{incldues/macros} the log results in:
<EMAIL_ADDRESS>(incldues/macros.tex

incldues/macros.tex:17: LaTeX Error: Missing \begin{document}.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H <return>  for immediate help
)

But maybe an idea is to match the preceding lines for filename.aux? I must say though, I am not really well versed in latex log stuff!

But maybe an idea is to match the preceding lines for filename.aux?
That is actually the best idea to solve this, I think. This increases the complexity of the parser, however, for all intends and purposes this should be fine. I did a few checks and it did not really affect compile time. I guess this might be noticeable for really huge projects, but then this is most likely dominated by LaTeX's build time anyways.

I am happy with this now and I think it it compatible to all platforms now, as well.

@sbdfh will check it on windows in a few, might I ask what platform you've tested it on?
Btw - I was looking at how others do this and found latex-log-parser-sharelatex didn't go through it completely though.

I'm on Linux using the current texlive installation.
The latex-log-parser-sharelatex parser is actually quite similar. At some point it might have been the basis for atom-latex?
Quick inspection tells me, they are also parsing one line at a time, and trying to detect multiline warnings. Which is a decent alternative. However, this seems to sometimes lead warnings attributed to the wrong source file? I might check that out if I have some additional spare time.

This won't solve the problem I initially started to fix. The current parser does not pick up warnings of packages that include linebreaks. These linebreaks are unaffected by max_print_lines because these are in the warning message.


OpenAPI construction

Related Issue(s):

Description:

Use standard FastAPI OpenAPI builder and inject metadata through env settings
Remove stac_api.api.app:StacAPi.customize_openapi method as it unnecessarily wraps the FastApi.openapi call.

PR Checklist:

[X] Code is formatted and linted (run pre-commit run --all-files)
[X] Tests pass (run make test)
[ ] Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
[X] Changes are added to the CHANGELOG.

@c-wygoda Whats the reason for this change?

We want to be able to specify more of the OpenApi metadata fields and in the process I found the customize_openapi method to be a rather redundant wrapper around the OpenApi functionality, if the FastAPI params are used directly in the attribute definition of the app.

This would also tackle #454 if I'm not mistaken.

I found the customize_openapi method to be a rather redundant wrapper around the OpenApi functionality,

I agree, this code is leftover from years ago when customization of OpenAPI was less flexible.  Now customize_openapi isn't hurting more than it helps (ref #454).

We want to be able to specify more of the OpenApi metadata fields

There is precedence to define openapi related things in ApiSettings so I think this is a good approach 👍
Note to self that at some point in the future we should deprecate StacApi.title, api_Version, and description (obviously a breaking change).

Thanks. I'm happy to help as I'm responsible for an instance, so hopefully can contribute more. Direct feedback welcome as I slowly learn the ropes of this project...

@c-wygoda The changes LGTM but I do want to play with this a little more to understand the difference between setting servers to self.app.servers compared to pulling from the environment within the context of #454 and #489

How can I help to move forward? More test coverage?

@geospatial-jeff ping

@jonhealy1 I think we should use this instead of #639 (we would need to update the landing page)

I'm not 💯 what we should do.
This kinda breaking change so definitely something we should keep for 3.0, but at the same time #639 does almost the same thing without breaking anything.
Both PR fixes stuff but do not represent the best solution to the issue:

499: fixes the OpenAPI but does not forward title, description,... to the landing page
639: add info to both the OpenAPI and landing page but doesn't use the Config class and add some code duplication

IMO we should wait after 2.5 to be released and see if we can refactor a bit to accommodate both changes
cc @jonhealy1

This PR should add some documentation how to set the env variables...

in #639 we implemented part of the proposed solution, Let's wait after 2.5 release to finish this PR


settings_overlay: Change privacy icon to a lock

Fixes #19737

Testing plan:
Manual testing.
GIFs or screenshots:

Merged, after a small tweak to the commit message to explain the motivation, thanks @jonathanktran!

Johny boy
On Tue, 14 Sep 2021, 18:13 Tim Abbott, @.***> wrote:

Merged, after a small tweak to the commit message to explain the
motivation, thanks @jonathanktran https://github.com/jonathanktran!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/19749#issuecomment-919351015, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADRP6AO7MLROIP6SUICJOH3UB57FLANCNFSM5D7GMPQA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


turn on debug logging in KBFS on mobile

remove old comments

As @strib suggests, it wasn't a KBFS bug, but a gobind bug.  Not tested....

ok, tried it with this commit cbb5153

Merging despite CI failures, which I believe are unrelated.


Log WebServer's context path consistently (track)

This issue tracks issue 36149 of spring-boot.

Change is needed in the following files:

spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/embedded/jetty/JettyWebServer.java
spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/embedded/netty/NettyWebServer.java
spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/embedded/tomcat/TomcatWebServer.java
spring-boot-project/spring-boot/src/main/java/org/springframework/boot/web/embedded/undertow/UndertowWebServer.java

Associated test files are:

spring-boot-tests/spring-boot-smoke-tests/spring-boot-smoke-test-jetty/src/main/java/smoketest/jetty/SampleJettyApplication.java
There is no spring-boot-smoke-test-netty?
spring-boot-tests/spring-boot-smoke-tests/spring-boot-smoke-test-tomcat/src/main/java/smoketest/tomcat/SampleTomcatApplication.java
spring-boot-tests/spring-boot-smoke-tests/spring-boot-smoke-test-undertow/src/main/java/smoketest/undertow/SampleUndertowApplication.java

org/apache/catalina/core/StandardContext.java, setPath does not allow converets "/" to "". Forr TomcatWebServer this means that we have to handle the output in-place.

		return Arrays.stream(this.tomcat.getHost().findChildren())
			.filter(TomcatEmbeddedContext.class::isInstance)
			.map(TomcatEmbeddedContext.class::cast)
			.map(context -> {
				final String path = context.getPath();
				if (path.isEmpty()) {
					return "/";
				}
				return path;
			})
			.collect(Collectors.joining(" "));
	}

While looking for tests or server implementations to see the results of my changes, I've found that there s no spring-boot-smoke-test-netty, whereas there is a smoke tests for all other embedded servers (jetty, tomcat, undertow). Am I missing something or did I found another issue?

For Undertow, if we want to add a context path, we need to add a path handler: https://github.com/quarkusio/quarkus/commit/f6acf8b091e95da03faca4c689b59c1a340ffb30

netty string is Netty started on port 8080, we should add context path.


Add sample + sample integration test for auth library's most common consumers

Add an integration test for some of google-auth-library's most important downstream consumers:

nodejs-googleapis-common.
nodejs-common.
gax.

Open question
If we do intend to take a breaking change, how can we do so without ignoring these broken integration tests (🐔  or 🥚  problem).

[Internal]
The root issue for this request will be resolved via the resolution of: go/nodejs-mono-repo
Closing this for now.


Create Articles “best-ant-control-for-gold-coast-homeowners-keep-ants-out-this-summer”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
5a32c7702528c87ec7d9443f45792d2f55a04a10

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/66f67697346ae50008a1a6fe


Way to limit parsing to currently open CSS file?

Is there a way to limit the parsing so it only looks at the currently open file?

VSCode already supports local file CSS Variable parsing.

But, I feel you want the features provided by this extension available to Open File Scope.
Let me check if this can be done easily or might take some time.

Anyhow, I feel this feature should be behind a Config toggle since most users want multiple files to be parsed by default.

Exactly, only parse/show variables for the file I am working on.
I am only learning HTML/CSS/JS and doing mini projects atm, but I use one large dir path of the projects and open the top level in VScode so I can quickly look at other code I've done. (Rather than using multiple windows)
And yeah, definitely behind a config toggle. I'm sure my use case is rarer
TopLevel
  index.html
  style.css
  --FrontendMentor
    --newbie
        --proj1
            index.html
            style.css
        --proj2
            index.html
            style.css
        --proj3
            index.html
            style.css
   --junior
        --proj1
            index.html
            style.css

Will surely look into it. Thanks!

I like the idea, it could be also having all of them on the same list, but somehow indicate they are on the current file or are from an external file. Maybe the blue dashes from the popup list having a different color for it, perhaps...

Hi Folks
This can be achieved using Multi Root workspaces as demonstrated in this example folder, since v1.5.0.
Do keep in mind that VSCode has its own IntelliSense enabled when it comes down to the same CSS file. Thus, you will see duplicate variables in the dropdown list when a variable needs to be accessed.
Every feature from this extension will work as is for a single file. 🎉
If you keep a single file in different root folders, then this can mimic what you are requesting, which is parsing the currently open file.

Found that you can disable VSCode's inbuilt CSS variable IntelliSense: https://github.com/willofindie/vscode-cssvar/issues/28#issuecomment-1081555892

Thank you for multi-root support, that works great.

Found that you can disable VSCode's inbuilt CSS variable IntelliSense: #28 (comment)

Sort of, that used to work. Now it disables all variables autocompletes EXCEPT the color variables you provide. I had a few months of not using VS Code so I'm not sure when it broke. I'm currently using VSCode version 1.71.2 and latest version of the extension published 15/09/2022.
Example with showVariables set to false, it only shows the color variables from your extension

Example with showVariables set to true, it shows variables from VS Code and your extension (top --fs-sell from your extension, one below from VS Code)

Don't know why it partially works setting showVariables to false, showing just the color variables, but not the rest provided by your extension. Unsure if this is a VSCode bug, or an extension bug.

There's a conflict with this setting since VSCode v1.70 I guess. I have kept a list of conflicts with VSCode here: https://github.com/willofindie/vscode-cssvar/issues/66
Another user also faced this same issue: https://github.com/willofindie/vscode-cssvar/issues/63#issuecomment-1236347800. The only resolution right now is to disable it, but I couldn't find any way (yet) to remove the duplicates in the same file since v1.70.
I will keep you posted if I find any fix.

There's a conflict with this setting since VSCode v1.70 I guess. I have kept a list of conflicts with VSCode here: #66

Ahh good to know, dang.

Another user also faced this same issue: #63 (comment). The only resolution right now is to disable it, but I couldn't find any way (yet) to remove the duplicates in the same file since v1.70.

Gotcha, will do that. At least VSCode's own suggestions consistently come second

I will keep you posted if I find any fix.

Cheers 💜

I tried to disable with the code added in settings.json, but nothing happened. In the suggestion list I still keep seeing variables from everywhere, not only from the current file.
"editor.suggest.showVariables": false,


fix:  gitlab vars

Fix error message when Gitlab env variables are empty to meet
the changed Gitlab variables as in constants.
Issue ticket number and link
Type of change

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm

/lgtm


ES-07|Mock model progress - Own Data Segmentation Approach Done

Problem
Work Item:
Solution Proposal
Manual Tests
No-Regression
:warning: Work In Progress
Progression
:warning: Work In Progress

Hey, there are some folders in the PR that I'm not sure why you're creating. Could you please provide a description in the PR? Thanks.


firejail --appimage tries to execute /bin/bash

Describe the bug
firejail --appimage tries to execute /bin/bash
Steps To Reproduce

Enable firejail
Run firejail --appimage

Expected behavior
The app image runs under firejail
Additional context
Error: dumpable process
Remove read permission on fseccomp executable
Error: dumpable process
Remove read permission on fsec-optimize executable
exec: Failed to execute process '/run/firejail/appimage/AppRun': The file specified the interpreter '/bin/bash', which is not an executable command.
Error: cannot run the sandbox

Notify maintainers
@7c6f434c
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.18, NixOS, 24.05 (Uakari), 24.05pre590113.1536926ef562`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

On another app it seems that it picks the wrong environment?
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/default.profile
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/default.local
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/globals.local
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/disable-common.inc
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/disable-common.local
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/disable-programs.inc
Reading profile /nix/store/1nljmpphdbv0w7gbj4c5ipqbm5g9b6nb-firejail-0.9.72/etc/firejail/disable-programs.local

** Note: you can use --noprofile to disable default.profile **

Parent pid 292046, child pid 292047
Error: dumpable process
Remove read permission on fseccomp executable

** Warning: dropping all Linux capabilities and setting NO_NEW_PRIVS prctl **

Mounting appimage type 2
Error: dumpable process
Remove read permission on fseccomp executable
Error: dumpable process
Remove read permission on fseccomp executable
Child process initialized in 120.51 ms
Could not start dynamically linked executable: /run/firejail/appimage/AppRun.wrapped
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see:
https://nix.dev/permalink/stub-ld

Parent is shutting down, bye...
AppImage detached


Start OPA CLI instructions

It's probably pretty rough right now. But I wanted to start some instructions of the CLI.

Hah you beat me to it. https://github.com/FairwindsOps/insights-docs/pull/25
I think we should just ditch the API instructions. I also added a CLI section


Views Controlled Vocabularies TG call May 27 at 15:00 UTC

The Views Controlled Vocabularies Task Group will have an online meeting at 15:00 UTC on Wednesday, May 27. That corresponds to 11:00 AM Eastern (US) Daylight Time (New York), 10:00 AM Central (US) Daylight Time(Chicago), 8:00 AM Mountain (US) standard time (Phoenix), and 5:00 PM Central European summer time (Stockholm).
We will continue the discussion about John Oswald's database and how to move forward on development of the controlled vocabularies. Meeting details to follow.

Steve Baskauf is inviting you to a scheduled Zoom meeting.
Topic: Views Controlled Vocabularies Task Group
Time: May 27, 2020 15:00 UTC
Join Zoom Meeting
https://vanderbilt.zoom.us/j/94952922793
Find your local number for dial-in: https://vanderbilt.zoom.us/u/abDfpgViRr
Google Calendar link: https://vanderbilt.zoom.us/meeting/tJAkcuuhrDktE9fmVXM3S7KiFKuUX2-5v6BE/calendar/google/add
Outlook Calendar (.ics) link: https://vanderbilt.zoom.us/meeting/tJAkcuuhrDktE9fmVXM3S7KiFKuUX2-5v6BE/ics

This is a reminder that the Views Controlled Vocabularies task group is meeting at 15:00 UTC on Wednesday, May 27. For connection details and local times, see https://github.com/tdwg/ac/issues/163

The notes from this meeting are posted here


FOSS Kickstart substitute?

This sounds like an interesting project but I'm not 100% sure on what it does.
Is it fair to say this is an open source, clean-room reimplementation of the Amigas kickstart rom? If thats what is has grown into, why do you not say this in the README? Maybe thats intentional for legal reasons?
If thats what HelloAmi is, more or less, what features does it lack that genuine kickstart roms have, if any? I'd like to see this info added to the README.
Thanks

Is it fair to say this is an open source, clean-room reimplementation of the Amigas kickstart rom?

It is not a re-implementation of the Kickstart/AmigaOS, and never will be.
You might be looking for the https://en.wikipedia.org/wiki/AROS_Research_Operating_System
In this project I tried to get used to the AmigaOS and wanted to create a floppy disk that boots into the graphical user interface. But the 1.x Kickstart ROMs do not include the icon.library - so I did a clean implementation of this library to close this little gap. With this library you can boot into the 1.x Workbench that is included in the Kickstart ROM - but note that you boot into a very basic system and most of the tools that make up the AmigaOS are missing. So this environment is very limited, but it might be useful to initially setup a system or to start some tools.


installation

3614 verbose unlock done using /Users/home/.npm/_locks/staging-3a08f0df5026584d.lock for /usr/local/lib/node_modules/.staging 3615 timing stage:rollbackFailedOptional Completed in 142ms 3616 timing stage:runTopLevelLifecycles Completed in 6836ms 3617 verbose stack Error<EMAIL_ADDRESS>postinstall: alfy-init3617 verbose stack Exit status 1 3617 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16) 3617 verbose stack     at EventEmitter.emit (events.js:182:13) 3617 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 3617 verbose stack     at ChildProcess.emit (events.js:182:13) 3617 verbose stack     at maybeClose (internal/child_process.js:961:16) 3617 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:250:5) 3618 verbose pkgid<EMAIL_ADDRESS>3619 verbose cwd /Users/home/ 3620 verbose Darwin 16.7.0 3621 verbose argv "/usr/local/Cellar/node/10.9.0/bin/node" "/usr/local/bin/npm" "install" "--global" "alfred-bitbucket" 3622 verbose node v10.9.0 3623 verbose npm  v6.2.0 3624 error code ELIFECYCLE 3625 error errno 1 3626 error<EMAIL_ADDRESS>postinstall:alfy-init 3626 error Exit status 1 3627 error Failed at the<EMAIL_ADDRESS>postinstall script. 3627 error This is probably not a problem with npm. There is likely additional logging output above.
uname -a  Darwin Kernel Version 16.7.0: Tue Jan 30 11:27:06 PST 2018; root:xnu 3789.73.11~1/RELEASE_X86_64 x86_64
npm --version 6.2.0

I retried with sudo and
`><EMAIL_ADDRESS>install /usr/local/lib/node_modules/alfred-bitbucket

node scripts/install.js

events.js:167
throw er; // Unhandled 'error' event
^
Error: EACCES: permission denied, open 'info.plist'
Emitted 'error' event at:
at WriteStream.onerror (_stream_readable.js:690:12)
at WriteStream.emit (events.js:182:13)
at lazyFs.open (internal/fs/streams.js:273:12)
at FSReqWrap.oncomplete (fs.js:139:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node scripts/install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/home/.npm/_logs/2018-08-23T06_27_27_102Z-debug.log`

I'm closing this, everything should be fine using either an LTS or 14 version of node. Reopen if you still have issues


Errors thrown from context creator functions are not handled properly.

My scenario is exactly like this one. I have a context creation function which throws exception when jwt verification fails. This issue has been fixed in apollo-server and my code worked fine when I was using it. When I migrated to graphql-yoga, I started getting this error in case of invalid token:
Invalid options provided to ApolloServer: {"params":{"token":"eyJhbG...abbreviated"},"code":"AUTH_INVALID_AUTHORIZATION_TOKEN"}

Going through the past issues in graphql-yoga repo, there are other open issues similar to this. Any workarounds?
Thanks

I have moved onto Apollo Server 2.0. I wanted to use yoga, but this and some other issues are a bottleneck for me. Feel free to close it.

I have moved onto Apollo Server 2.0. I wanted to use yoga, but this and some other issues are a bottleneck for me. Feel free to close it.

Can you elaborate? What other issues?


magick command to make icons does not exist on Ubuntu 20.04 - but I have ImageMagick installed

The "magick" command does not exist, however the "convert" command (used by imagemagick to convert images) exist.
ImageMagick can be easily installed on Ubuntu by simply sudo apt install imagemagick

Look what quark setup tries to do:

Now you could say "ah this can be solved by just creating an alias in your bashrc like alias magick='convert' right?
No, even if I restart the application, does not work either. Seems like a bug, probably easy to correct.

I solved (I think the problem manually) by changing quark/package.js file and changing the "magick" command to "convert"
Maybe you could do a variable with a check before if convert command exists and "magick" not, and use convert
However... It seems there is another problem:

I am trying, as you see, to generate an app for win64 and linux, and it shows this "winx64 FAILURE, no .dat file" and no Windows file (even the .exe) was generated.

Actually imagemagik is only used to create the icon for Windows executables. Both Linux and Mac do not have support for icons within the executable.

Of course, but in Ubuntu the Quark and the whole software won't work if this change is not made... The executable will never be generated, this is why this is a bug.

I guess we can just ignore the whole imagemagik code when not on Windows. @terremoth Maybe you can create a PR?

I think I can do better if I have time: make an "if convert command exists and imagick command does not, use convert command instead", and it will work, but the second problem will remain to create winx64 dat file.

It would be good to create windows application directly from linux/ubuntus too, so it would need to correctly generate dat file and exe file

Yes you're right.

I can solve the first problem, but the second one I don't think I can figure out myself


Request for adding animate diff LoRa from shatterAnimatediff_v10

Here: https://huggingface.co/ArtGAN/Controlnet/blob/94b10ac2bab3f128115c26585059dcbe439ca592/shatterAnimatediff_v10.safetensors
Thanks.

Added here:
https://github.com/fofr/cog-comfyui/commit/ab387fd4929b82d255ba5f19d9cc11d638389155


Boost Version Update

Can you update the boost version? It is currently using 1.76.0, which does not recognize Visual Studio 2022 and caused error when installing.
Found with vswhere C:\Program Files\Microsoft Visual Studio\2022\Community

###
### "Unknown toolset: vcunk"
###
### You can specify the toolset as the argument, i.e.:
###     .\build.bat msvc
###
### Toolsets supported by this script are: borland, como, gcc,
###     gcc-nocygwin, intel-win32, mingw,
###     vc12, vc14, vc141, vc142
###
### If you have Visual Studio 2017 installed you will need to either update
### the Visual Studio 2017 installer or run from VS 2017 Command Prompt
### as we where unable to detect your toolset installation.
###

Failed to build Boost.Build engine.

mingw32-make[2]: *** [CMakeFiles\external_boost.dir\build.make:91: boost/src/external_boost-stamp/external_boost-configure] Error 1
mingw32-make[1]: *** [CMakeFiles\Makefile2:120: CMakeFiles/external_boost.dir/all] Error 2
mingw32-make: *** [makefile:135: all] Error 2

Yes, I installed the latest version boost, and ran cmake .. -DCMAKE_PREFIX_PATH=C:\Softwares\boost_1_78_0 and then make in the build directory. But it still installs the old version boost for me. Is the command wrong? I am very new to installing frameworks.


Explore extension in Development is no longer showing the icon in the activity bar, requires a CTRL SHIFT-F5  before it then appears

VS Code Version: 1.54.1
OS Version: WIndows 10

I am working on an Explorer Extension. For many months, I have been able to click F5 and start in debug mode and the extension's icon appears in the activity bar and all is well.  I can make a code change then press CHTRL-SHIFT-F5 and restart the debug session. again all has been fine.
Now, when I first start VSCode, the bar at the bottom of the screen is blue. If I click F5, the bar turns orange and a new window opens but the Explorer Icon is not being displayed in the Actitvity Bar - yet, I can hover over where it should be and  it displays the hover over text.  I have to do a CTRL-SHIFT-F5 and restart the debug session and then the icon does appear.
The same happens if I run without debugging. The icon is not present in the Activity bar till I do a CTRL-SHIFT-F5 to restart.
This has started to only occur in the past 4 - 5 days. It has been fine for months previously.

This appears to be a duplicate of the already opened https://github.com/microsoft/vscode/issues/118338


CPU and memory limits are not reconciled back when they are removed manually

How to categorize this issue?

/area auto-scaling
/area control-plane
/kind bug
What happened:
We used an OPA policy to remove CPU and memory limits on Deployments in a Shoot namespace on a Seed. This worked as expected, limits got removed on e.g. the kube-apiserver Deployment, the Deployment got rolled and all Pods and Containers got updated as expected.
Afterwards, we tried to bring the limits back by ensuring the OPA policy isn't applied anymore (we removed the marker labels on the Shoot namespace) and reconciled the Shoot. Limits were brought back in the kube-apiserver Deployment, but not on all containers – the kube-apiserver container did not get any limits assigned.
What you expected to happen:
The kube-apiserver also gets limits reconciled, similar to the other containers in the Deployment.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
This seems to happen because we're using HVPA to manage the kube-apiserver container, which leads to resources being managed by HVPA only during Deployment reconciliation

I have given this some thought many times already and I came up with the following rule of thumb about what objects webhooks should mutate for which use cases:
I would generally recommend to do all pod-specific/runtime-related mutations on pods themselves instead of mutating higher-level controllers, e.g.:

resource requests/limits
scheduling constraints
injecting sidecars

Only workload-related mutations should be applied to higher-level controllers, e.g.:

manipulating command-line flags
adding additional application config

This has the advantage, that when you change webhooks to apply different runtime-related settings (or stop applying them) it will take effect on the next pod creation. This minimizes unnecessary disturbance by rollouts and doesn't need to wait for the next update to the higher-level controller (e.g. by gardenlet).
If runtime-related settings differ between multiple pods, it's generally not an issue. However, following the above pattern ensures that workload-related settings are consistently applied across replicas.


Add endpoints for stable-coin support

/payloadCreation/freeze
/payloadCreation/unfreeze
/dataRetrieval/frozenBalance
/dataRetrieval/frozenBalance
/dataRetrieval/frozenBalanceForId

:tada: This PR is included in version 1.0.0 :tada:
Your semantic-release bot :package::rocket:


Unable to remove project tmp dir

Hello, I tried dapp 1.0.0 alpha and run into problem that dapp was unable to remove project tmp directory, latest output is:
npm WARN company No repository field.
npm WARN company No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 999 packages from 630 contributors and audited 13066 packages in 94.629s
found 0 vulnerabilities

# Building image dimgstage-nodejs-backend-auth:44d4ad5a0836837889d58fb2485914b45f794b987ae4107195bcaa21c042e89a for dimg/nodejs-backend-auth stage/setup
# Using cached image dimgstage-nodejs-backend-auth:28347249896a7fe21822d2a203e2e052d8ab5703bead7c6098e9591119a40b6a for dimg/nodejs-backend/auth/ stage/from
# Building image dimgstage-nodejs-backend-auth:2f24c247f6d2ba3ddcbe7286effe941d27502caa8fc8fb5ec53ae697dc647f1a for dimg/nodejs-backend/auth/ stage/after_setup_artifact
WARNING: unable to remove project tmp dir /tmp/dapp-502848276: remove /tmp/dapp-502848276/dimg/nodejs-backend/auth/artifact/nodejs-backend-auth/4e99338780ae02474e1e8480a2de401a0d56d307e0aab3c40320eb9cc90fe670/nodemon-debug.json: permission denied

inside of docker containers we run everything by root user, we run dapp by special user (gitlab-runner), and as result that directory files of /tmp/dapp-/ are owned by root:root which leads to problem with permissions
I took a look at code
https://github.com/flant/dapp/blob/master/pkg/build/stage/base.go#L86
https://github.com/flant/dapp/blob/master/pkg/build/stage/base.go#L178
and as far as I understand the tmp_dir is mounted into container.
Is there any possible workaround agains this issue? I'm not really willing to run gitlab ci by root user and it also would be weird to have user gitlab-runner inside of docker containers just to fix the issue with removing directories.

https://github.com/flant/dapp/releases/tag/v1.0.0-alpha.2


NavigationMenuContent not appearing under the NavigationMenuItem

I have tried multiple times even reusing the exact example show in the (docs)[https://ui.shadcn.com/docs/components/navigation-menu] and still nothing I even went as far as starting a new project with
pnpm create next-app -e https://github.com/shadcn/next-template

I also tried manually installing everything
you get the point. please any other ideas

@crazycodestar I had this same issue. It looks like in the navigation-menu.tsx file that is created under the components/ui folder has a left-0 attribute for the className of NavigationMenuViewport. I removed that, and now they're centered under the trigger text. Let me know if you're still having the issue or if it worked. Below is line 82 and below of the file with the updated className:
`const NavigationMenuViewport = React.forwardRef<
React.ElementRef,
React.ComponentPropsWithoutRef

(({ className, ...props }, ref) => (

))
NavigationMenuViewport.displayName =
  NavigationMenuPrimitive.Viewport.displayName
const NavigationMenuIndicator = React.forwardRef<
React.ElementRef,
React.ComponentPropsWithoutRef

(({ className, ...props }, ref) => (
<NavigationMenuPrimitive.Indicator
ref={ref}
className={cn(
"top-full z-[1] flex h-1.5 items-end justify-center overflow-hidden data-[state=visible]:animate-in data-[state=hidden]:animate-out data-[state=hidden]:fade-out data-[state=visible]:fade-in",
className
)}
{...props}

</NavigationMenuPrimitive.Indicator>
))
NavigationMenuIndicator.displayName =
NavigationMenuPrimitive.Indicator.displayName
export {
navigationMenuTriggerStyle,
NavigationMenu,
NavigationMenuList,
NavigationMenuItem,
NavigationMenuContent,
NavigationMenuTrigger,
NavigationMenuLink,
NavigationMenuIndicator,
NavigationMenuViewport,
}`

I also realized another thing. I tried increasing the number of dropdown menu's in the navbar. That's when I realized that the dropdowns aren't coming under each dropdown button. Rather it's coming down at the center of the entire dropdownMenuList

Yeah, you're right. I'll try to mess with it more later but hopefully someone that does front-end more regularly than me has a solution to share as well.

I'm having the same issue, anyone found a way to fix it?

After playing with it more, I realized what is actually so great about it - it's the modularity of the components themselves. How I ended up using it was wrapping my menu in a nav tag with some flex attributes, and then the NavigationMenu and NavigationMenuItems themselves in a div that uses a grid. For example, this is how my return in my Navbar.tsx file is structured:

                        ....content.....

Now please take the above Tailwind styling with a grain of salt because I'm no frontend guy by any means and that's just what worked for me, but it's the ability to use the tags in your own header/div styling that makes them so powerful. Hope this helps and let me know if you have any clarifying questions.

Came across this myself recently, made a minimal reproduction repository in case it helps anyone trying for a fix - https://github.com/AdiRishi/shadcn-navbar-bug-demo
Quick video to demo the issue

Also running into it

This might not be the right way to do it, but it works for me.  If I wrap each <DropdownMenuItem> that had a dropdown with it's own <NavigationMenu> it seems to force the dropdown to appear under the trigger.
See the pull request: https://github.com/AdiRishi/shadcn-navbar-bug-demo/pull/1/files
function DropdownMenuItem({ itemText }: { itemText: string }) {
  return (
    <NavigationMenu>  {/* Added */}
      <NavigationMenuItem>
        <NavigationMenuTrigger>{itemText}</NavigationMenuTrigger>
        <NavigationMenuContent>

            {DROPDOWN_ITEM_DATA.map((component) => (
              <ListItem
                key={`${itemText}${component.title}`}
                title={component.title}
                href={component.href}
              >
                {component.description}
              </ListItem>
            ))}

        </NavigationMenuContent>
      </NavigationMenuItem>
    </NavigationMenu>  {/* Added */}
  );
}

@crazycodestar I had this same issue. It looks like in the navigation-menu.tsx file that is created under the components/ui folder has a left-0 attribute for the className of NavigationMenuViewport. I removed that, and now they're centered under the trigger text. Let me know if you're still having the issue or if it worked. Below is line 86 with the updated className:

This worked for me

This might not be the right way to do it, but it works for me. If I wrap each <DropdownMenuItem> that had a dropdown with it's own <NavigationMenu> it seems to force the dropdown to appear under the trigger.
See the pull request: https://github.com/AdiRishi/shadcn-navbar-bug-demo/pull/1/files
function DropdownMenuItem({ itemText }: { itemText: string }) {
  return (
    <NavigationMenu>  {/* Added */}
      <NavigationMenuItem>
        <NavigationMenuTrigger>{itemText}</NavigationMenuTrigger>
        <NavigationMenuContent>

            {DROPDOWN_ITEM_DATA.map((component) => (
              <ListItem
                key={`${itemText}${component.title}`}
                title={component.title}
                href={component.href}
              >
                {component.description}
              </ListItem>
            ))}

        </NavigationMenuContent>
      </NavigationMenuItem>
    </NavigationMenu>  {/* Added */}
  );
}

This solves the positioning relative to the trigger, but breaks the slide effect because you are no longer sharing the same viewport... I this component is best suited for when you have dropdowns all next to eachother so you can share the same viewport. Nice.

Issue persists. Even after removing left-0 from the NavigationMenuViewport className, if you have multiple dropdown triggers each dropdown menu appears at the same place.

This might not be the right way to do it, but it works for me. If I wrap each <DropdownMenuItem> that had a dropdown with it's own <NavigationMenu> it seems to force the dropdown to appear under the trigger.
See the pull request: https://github.com/AdiRishi/shadcn-navbar-bug-demo/pull/1/files
function DropdownMenuItem({ itemText }: { itemText: string }) {
  return (
    <NavigationMenu>  {/* Added */}
      <NavigationMenuItem>
        <NavigationMenuTrigger>{itemText}</NavigationMenuTrigger>
        <NavigationMenuContent>

            {DROPDOWN_ITEM_DATA.map((component) => (
              <ListItem
                key={`${itemText}${component.title}`}
                title={component.title}
                href={component.href}
              >
                {component.description}
              </ListItem>
            ))}

        </NavigationMenuContent>
      </NavigationMenuItem>
    </NavigationMenu>  {/* Added */}
  );
}

This worked for me.

Managed to get the content position to stick under the corresponding trigger element.
If anyone needs it, I made a gist over here.

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

Definitely closed by accident. Jeez, auto-close bots are the worst.

@shadcn In a fresh project this is still an issue, with all defaults in next 15. :)
Can we reopen this?


switch the Light on but not switch it off :(

Hello,
yesterday i installed Hoobs on the Raspberry.All Shellys were also found but Shelly 1.0 which are set up to switch the Lights do not work correctly.I can switch the Light on but not switch it off via the App.
Everything works perfectly in the Shelly App
Shelly 2.5 in Shutter Mode work without problems.
is there a solution to this problem?
all Shellys are set up on the current update.

Are you sure you are right here?
I think you're more likely to find a solution here: https://support.hoobs.org/


errors on bash event loop

run greeter.sh at https://pglet.io/docs/tutorials/bash/ I got below duplicated multiple line errors:
pglet.sh: line 217: .events: No such file or directory

What OS are you running it on?

ubuntu 20.04

Ah, I see. The problem is in line pglet_page "index". In Pglet 0.4.5 the service mode was made default where "index" page name is reserved. Change it to just pglet_page, so random name is used for page name:
. pglet.sh

pglet_page

pglet_send "clean"
txt_name=`pglet_send "add textbox label='Your name' description='Please provide your full name'"`
btn_hello=`pglet_send "add button primary text='Say hello'"`

while true
do
    pglet_wait_event
    if [[ "$PGLET_EVENT_TARGET" == $btn_hello && "$PGLET_EVENT_NAME" == "click" ]]; then
        name=`pglet_send "get $txt_name value"`
        pglet_send "clean page"
        pglet_send "add text value='Hello, $name!'"
        pglet_send "add text value='Close browser window to exit the program...'"
        break
    fi
done

Good catch. Thanks for trying Pglet!

@laoshaw it's been kind of surprising (and pleasant) to see a sudden spike in Pglet usage, so may I ask where did you know about Pglet and what kind of app are you working on and what language? We are still trying to better understand Pglet use cases and need to plan an upcoming release for any new/breaking changes.

https://messaged.com/tldr/newsletter is where I learned it. I actually was trying to see what pglet really does but was paused due to the mentioned bug. Anything making UI easy will find its audience I think.

Oh, great, thank you!


Fix typographical error(s)

@hellsan631, I've corrected a typographical error in the documentation of the LogosDistort project. Specifically, I've changed consistant to consistent. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

me am bad spell