Introduce config parameter for header propagation outside of LRA context

Fixes #201.

@xstefank for your review

@mmusgrov
Option 2: Current situation which has issues for which I created #201
Option 3: This can handle the propagation of the LRA context only when a an LRA context active. Not when there is no @LRA placed. So option 3 is not a valid solution for #201.
Option 1: Then you basically revert the solution of #7 , which is fine for me but I wanted to keep the 'current' functionality by defining a config parameter.

@mmusgrov
Option 2: Current situation which has issues for which I created #201

I am not sure what the specific issue you had since I think I provided a response to each of the issues on #201

Option 3: This can handle the propagation of the LRA context only when a an LRA context active. Not when there is no @lra placed. So option 3 is not a valid solution for #201.

I mean put the propagate attribute on an LRA aware method. So when the context is propagated to a non-LRA aware resource the implementation knows whether or not it should propagate the context on outgoing requests made by this non-LRA aware resource.

Option 1: Then you basically revert the solution of #7 , which is fine for me but I wanted to keep the 'current' functionality by defining a config parameter.

Fine with me also but the request came from another community member and we agreed to change the behaviour.

@mmusgrov The example I gave in 201 is never solved
suppose you have the following calling sequence
A -> B -> C
A : @LRA(REQUIRES_NEW)
B : Nothing
C : @LRA(NEVER)
This fail for the moment and your solution

.header(LRA_HTTP_CONTEXT_HEADER, lraURI)

Does not work in service B.
You can try "" or null as value of lraURI but implementation will add the LRA id started in A because it must have a LRA Context on all outgoing requests (as per spec definition) since it propagates the headers.

What about option 3.

@mmusgrov The example I gave in 201 is never solved
suppose you have the following calling sequence
A -> B -> C
A : @lra(REQUIRES_NEW)
B : Nothing
C : @lra(NEVER)

I don't see anything wrong with this. A starts a new LRA which gets propagated to C (via B). C says there should not be any context so the invocation fails. That is the definition of the NEVER attribute.

But that means that once you have a LRA header active, you have no means to git rid of that. (developers should stay in control!!)
Does it still makes sense when Service A, B and C are deployed on 3 different servers, 3 different implementations and service B isn't even an MicroProfile application but happens to be deployed on a runtime which support MicroProfile?

What about option 3?

I proposed option 3 to address your concerns but if you don't like it then:

But that means that once you have a LRA header active, you have no means to git rid of that. (developers should stay in control!!)

Resource A can remove the header before invoking B.

Does it still makes sense when Service A, B and C are deployed on 3 different servers, 3 different implementations and service B isn't even an MicroProfile application but happens to be deployed on a runtime which support MicroProfile?

Possibly not, and my initial spec proposal was to not propagate across non JAX-RS aware resources. But since the community vote was to propagage across non-JAX-RS aware resources it is the logical behaviour.

I proposed option 3 to address your concerns but if you don't like it

I wanted to keep the option that it automatically propagates (which is not possible with option 3) since you defend the solution of #7 so vividly.

Resource A can remove the header before invoking B.

No it is not possible with the current spec. The implementation MUST propagate the active context on outgoing JAX-RS requests. states the spec and it is unclear if developer can remove the header (developer is allowed to set the header with another LRA id)

community vote was to propagate across non-JAX-RS.

Issue was opened by you and I see no comments from other people .

@rdebusscher @mmusgrov sorry I was down yesterday because of medical problems.
I don't think we should leave this discussion in a state it is right now. I agree with Rudy that this is indeed an issue and we should either remove LRA propagation over non LRA aware resources or merge this PR to allow users to choose to opt in for this behavior. So I believe this PR should be reopened.
One more comment for the option 3 - can we even find out from which method an outgoing JAX-RS call is being made to check for LRA annotation?

Just to add that I think that stopping an unannotated LRA propagating the transaction by default would revert https://github.com/eclipse/microprofile-lra/issues/7
I would disagree with adding system properties into the specification, perhaps there could be a some global default annotation that applications can set in their Java code @LRAConfig(propagateByDefault=true)

@tomjenkinson This PR is introducing MP Config property which is a standard way of providing this kind of configuration for MP specifications (examples can be found for instance in Metrics or REST client).

Ah, OK. If it is standard then fine. Default must be true though or it overrides #7

I proposed option 3 to address your concerns but if you don't like it

I wanted to keep the option that it automatically propagates (which is not possible with option 3) since you defend the solution of #7 so vividly.

My proposal was to set the default to automatically propagate the context:
public @interface LRA {
   boolean propagate() default true;

This approach has the twin benefits of:
#1 it does not invalidate #7
#2 it is more flexible in the sense that the propagation mode can be set on a per LRA basis

Resource A can remove the header before invoking B.

No it is not possible with the current spec. The implementation MUST propagate the active context on outgoing JAX-RS requests. states the spec and it is unclear if developer can remove the header (developer is allowed to set the header with another LRA id)

The spec says the resource is allowed to set the active context on outgoing requests. So clearing it is implicit.

community vote was to propagate across non-JAX-RS.

Issue was opened by you and I see no comments from other people .

I opened it at the request of a community member (see item 2e of the minutes from the June meeting last year).

snip
My proposal was to set the default to automatically propagate the context:
public @interface LRA {
   boolean propagate() default true;

This approach has the triple benefits of:
1 it does not invalidate #7
2 it is more flexible in the sense that the propagation mode can be set on a per LRA basis
3 it satisfies your preference

@rdebusscher I notice that both you and @xstefank prefer the default to be not to propagate the context so the proposed default value for the annotation attribute does not satisfy your preference. If we did choose to go with option 3 then is there a precedent for overriding an annotation default value using a global config property?

I reopened the PR by mistake. Should we continue the discussion on the iss #226 instead?

I think the default must be to propagate through any MP LRA aware service. If you want the default to be off, don't deploy MP LRA libraries. I do think a config option to change the default should be fine though.


Next poll is skipped after a manual sync. Have to wait following poll.

Expected behavior
Let say I have a 15 minutes poll interval. No push. This was with a Gmail account.
K9 polls at 2.20
I manually sync at 2.27
I expect K9 to poll at 2.35
Actual behavior
K9 polls at 2.20
I manually sync at 2.27
(I now make sure I have a new email in my gmail inbox -ie not K9 inbox -, by sending one from a PC)
K9 skips the polling at 2.35 (the K9 inbox is not reflecting this email) and poll at 2.50.
I don't know if the polling is effectively skipped, but for sure the folder which are supposed to be updated via polling are not updated until the next polling scheduled event.
Steps to reproduce
1.as described above
Environment
K-9 Mail version: 5.0.10
Android version:CM13 (6.0.1)
Account type (IMAP, POP3, WebDAV/Exchange):GMAIL IMAP POLL

That's better than my experience. What I'd like to see is manual poll resets the poll timer so the next poll is (current time + base poll time). What I've seen is "Next poll 3 minutes ago". I poll manually and it doesn't reset and then polls two minutes later for no good reason. What I'd like to see: manual poll truly resets timer. Last poll 2:20. Manual poll 2:36 (because it hasn't polled at 2:35 for whatever reason). Next poll: 2:51.
Skipping a poll is too much, but ignoring manual polls is too little. The via media of "Manual poll is last successful poll" should be a reasonable compromise.

The reason it might poll a minute late is because we don't ask for exact 'alarms' from Android because we take the view that it's not worth the battery trade-off. So Android can  and often does trigger the event slightly early or slightly late to match a device wake-up window.
This is probably the root cause of the 'Next poll x minutes ago' issue (which is obviously a bug - i think there's an issue already for it).

We changed the way we sync. This should no longer be an issue in master.


fix(debug): Displaying connection error info

:tada: This PR is included in version 7.1.13 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


ejercicio 5

pulleado!

La velocidad de este grupo... sin precedentes jajajja
El mar., 16 de nov. de 2021 01:36, Carla @.***>
escribió:

pulleado!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/2167-Team1/TeamProject/pull/2#issuecomment-969852007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVEUVHK5DSCA32P5QQRRT23UMHNU7ANCNFSM5IDGNCGQ
.
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.


Avoid thrown/caught exceptions when using HttpClient.openUrl (and related methods) with hostnames

In a recent change (d884d1a76e47e45c5b34b376575b10e236ebeb0a) to fix #50868, there are calls to _InternetAddress.fromString() that will throw (and then catch) ArgumentError whenever the URI contains a hostname and not an IP address.
This is not itself a bug/problem and everything works as expected. However, a lot of users are running with "break on all exceptions" ticked in VS Code and breaking here is causing some confusion. I've explained the issue here although that's not very visible unless you read the entire thread.
I think that issue should probably be closed (because as far as I can tell everything is working as expected), but since fetching URLs using hostnames is very common I thought it was worth seeing if that code could be altered to not rely on throwing/catching for this flow. While I think users shouldn't generally run with "Break on all exceptions" enabled (the default is "Break on uncaught exceptions"), the less "noise" there is when running in that mode, the easier it'll be to track down actual issues caused by unexpected exceptions being thrown and caught.

I am facing the same kind of issue, please seek it out on time.
I have explained my problems in this video 👇👇👇👇👇
https://youtu.be/lRtrcG_Sz8U

A fix is in place. I'll go through the cherrypick process tomorrow.


Detectron2 build/installation query

I am using detectron2 in my env already, so instead of building detectron2 like mentioned in the installation guidelines; I tried to use to pip installed version which was there in my env.

The above steps caused me error where for fast_rcnn_inference() it says instead of 6 arguments 7 are passed.

So, my question:

Is it required to build the detectron2, can't I use the installed package of same cuda configuration?

Is there any changes in maskal/detectron2 than that of detectron2 (as seems to be the case for some functions) and that's why re-building is required, is there any work-around to use the existing detectron2 package instead of rebuild?

@nick0tine Indeed, logic question. There are so many things changed (for example adding dropout layers for the Monte-Carlo dropout) that you've to build it again. Also, the approach is different: standard D2 is trained once, MaskAL is trained iteratively after every sampling and annotation. So I recommend to follow the steps and rebuild the code. Then it should work out of the box

Thanks for the quick explanation


fix: Ensure transactions are managed in a thread safe way and add deb…

…ug logging

Nothing to add, but I get emails about this repo still and every time I think "I hope those guys are doing well and enjoying life!"
Particularly in the holiday season, I hope you all and your families are thriving :)
-Caleb


tweaks to handle more galleries

Make #308 further.
It should handle this now:

What's more
List mode can still be laggy if you swiping across huge groups, it needs a redesign to reach the baseline of a reasonable performance.

LGTM

Besides, recude cacheExtent for GroupList can only help with scroll performance, it will make group toggle performance worse, if your list contains 5000 gallerys, UI will be laggy when you open/close a group.
Currentl grid layout is recommended for such a huge amount of gallerys. GroupList will be refactored because its poor implement later.

Without reducing cacheExtent, list view will stuck nearly forever until a relief when you can switch to grid view.
I think it's a fair tradeoff, where more cacheExtent provides almost no help on performance .


Unable to locate element: {"method":"css selector","selector":".MGdpg > button:nth-child(1)"}

When I run the code after a full set up it consistently states "Message: no such element: Unable to locate element: {"method":"css selector","selector":".MGdpg > button:nth-child(1)"}" Has this issue come up before? If so, is there a simple solve? I am afraid IG may have changed the CSS identifier for the load_more_comments button

the code still works on me. Do you really sure all the comments scroll have no ended up so the load more button won't appear?

I'm having the same problem when clicking "load_more_comment"

I installed everything from the beginning and I have the newest version of chrome

the code still works on me. Are you really sure all the comments scroll have no ended up so the load more button won't appear?

whats your version in chromedrive ?

Sorry for the late response. I just have tried with version 87.0.4280.88 and it works fine. I guess the page you open has not load more button, in another word, all comments have shown in a single load

Ahh my bad, this is might be a connectivity issue, this script will wait for 1.5 seconds roughly, then will try to click the next, you can try to change the time.sleep(1.5) at this line to desired waiting time in second

Hey @AgiMaulana I experience the same problem as @gugahb and @gryff530. While the script starts correctly, it aborts with an error message after the first attempt to load more comments:
Found <selenium.webdriver.remote.webelement.WebElement (session="dedebb2733ffba0efd1fd79dd74ca3a8", element="8e712b55-2377-48c1-aa90-8f51c0f756e4")>
Message: no such element: Unable to locate element: {"method":"css selector","selector":".MGdpg > button:nth-child(1)"}   (Session info: chrome=87.0.4280.88)
I have tried both posts with few comments (less than 20) and with many comments (more than 1000) and i always observe the same behavior.
I also tried Firefox/geckodriver as selenium webdriver for testing purposes. Even changing the value of time.sleep(1.5) did not change the behavior.
Is there any chance that Instagram changed the way comments are loaded?

where have you located guys? if you use VPN let me know the location did you used,  I'll try to check is Instagram has changed the page structure in certain locations.

where have you located guys? if you use VPN let me know the location did you used, I'll try to check is Instagram has changed the page structure in certain locations.

Thanks a lot for your answer! I m based in Germany and have not used a VPN to access Instagram.

I found out that in some locations Instagram redirects the posting page to login page

Hi, guys, I am trying to add a login feature but need volunteer developer to try the feature since I haven't found free VPN service for Linux/Ubuntu, you can check the feature is under development in this branch

Hi, guys, I am trying to add a login feature but need volunteer developer to try the feature since I haven't found free VPN service for Linux/Ubuntu, you can check the feature is under development in this branch

hi all,
i am facing this issue as well, did anyone solve it ?
sometimes it finds the selector .MGdpg but most of time it doesn't find.

One hacky way to work around this is to set the sleep before starting scraping to longer enough (30s) in scraper.py line7 so that you have time to manually login and then the scraping will work fine


Fix isPrimary bug for empty patches

Patches with no valid entries marked 'isPrimary' in ref_table
were returning all ref_table entries.  This fixes that by

Explicitly restricting ref_table to isPrimary
Skipping patches that are empty lists.

The tracts that I needed to regenerate were
4429 4433 4637 4640 4852 5066


Cannot choose display options in an embedded preview

Describe the bug
Clicking "Display Options" (a gear icon) in an embedded preview doesn't do anything. It seems to work ok when rendered as a preview, i.e. a popover appears and lets me change the display options.
I tried to dig into this today but couldn't figure out how DisplayOptions::Editor::Component gets rendered 😢
To Reproduce
Steps to reproduce the behavior:

You need to have more than one display option configured.
Visit any embed URL.
Click on gear icon.

Expected behavior
The same popover from the preview page should render on the embed page.
Screenshots
There's not much to show here.
Version numbers
Please complete the following information:

Lookbook: 2.0.2
ViewComponent: 3.5.0
Rails: 7.0.3
Ruby: 3.2.0

Thanks @camertron! I'll look into this and get it fixed up as soon as I can.

I tried to dig into this today but couldn't figure out how DisplayOptions::Editor::Component gets rendered 😢

Yeah it's all a bit convoluted in the views at the moment 🥺 would love some time to rework things to make it a bit easier for people to dig into! It's actually rendered here in the embed: https://github.com/ViewComponent/lookbook/blob/317fda7a89bcf0f6dd56a254399525c0341e2d38/app/components/lookbook/embed/inspector/component.html.erb#L21 but I think the issue must be something JS related. I'll check it out and let you know when I've got a fix in place.

@camertron I've found the issue and pushed up a fix - will go out in the next release, hopefully later today.

This should be fixed now in v2.1.0 so I'm going to go ahead and close this. If you are still have any problems with it just let me know!

Awesome, thanks very much for looking into this @allmarkedup!


chore: bump asset service version

Description

bumps the asset service version to blacklist KICK and update ATOM custom description
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[x] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #509 - we missed KICK originally
Risk

essentially zero
Testing

search for KICK - no results should be returned
Screenshots (if applicable)
n/a

hurr, yeah, original issue and associated impl was in lib - issue is here https://github.com/shapeshift/lib/issues/509


added supported platform (with version)

Added supported platform with version requirement.
(Otherwise someone might try to run this package on an unsupported build target)
PS: Feel free to change the version to a lower requirement. I just picked the latest.

PPS: and also feel free to add different targets if needed.
(here is the documentation)


Emit TAP count at end of test run

Due to parameterized tests, we don't know in advance how many tests we will run. Fixes #561.
(I'm fairly sure it wasn't correct prior to the introduction of parameterized tests either, due to nested tests, but whatever, it's fixed now.)

Can one of the admins verify this patch? (see README)


Version 1.4 asks for a directory path and does not accept the path to a file

Since version 1.4.0 we are unable to deploy a file. The error message is DeployPath: src/Droid/bin/Release/be.ourid-bitrise-signed.apk: not a directory

Same here—this is blocking some of our pipelines. A workaround is to pin to an earlier version, but it's not ideal.

doesn't work with the 1.4.1 version either (1.3.19 works though)

Hey @rubenhorn !
Thanks for the report, the fix already implemented: #84
The new version of the step will be released soon.


Can't import winrt::windows::data or ::ui

rustc 1.18.0 (03fc9d622 2017-06-06)
cargo 0.19.0 (28d1d60d4 2017-05-16)

My Cargo.toml:
[package]
name = "hello_world"
version = "0.0.1"
authors = [ "Adam Baxter<EMAIL_ADDRESS>]

[dependencies]
winrt = "0.2.1"

[features]
windows-ui = []
windows-data = []

main.rs:
extern crate winrt;
use winrt::*; // import various helper types
use winrt::windows::data::xml::dom::*;
use winrt::windows::ui::notifications::*;

fn main() {
    let rt = RuntimeContext::init();
	println!("Hello, world!");

}

(to be replaced with a toast notification as soon as I can make it work)
PS C:\git\rust\hello> cargo build --verbose
       Fresh winapi v0.2.8
       Fresh winapi-build v0.1.1
       Fresh ole32-sys v0.2.0
       Fresh runtimeobject-sys v0.2.0
       Fresh oleaut32-sys v0.2.0
       Fresh winrt v0.2.1
   Compiling hello_world v0.0.1 (file:///C:/git/rust/hello)
     Running `rustc --crate-name hello_world src\main.rs --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=1d57d6994d17b2e4 -C extra-filename=-1d57d6994d17b2e4 --out-dir C:\git\rust\hello\target\debug\deps -L dependency=C:\git\rust\hello\target\debug\deps
--extern winrt=C:\git\rust\hello\target\debug\deps\libwinrt-9ac1a1eab3936cb9.rlib`
error[E0432]: unresolved import `winrt::windows::data::xml::dom::*`
 --> src\main.rs:3:5
  |
3 | use winrt::windows::data::xml::dom::*;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Could not find `data` in `windows`

error[E0432]: unresolved import `winrt::windows::ui::notifications::*`
 --> src\main.rs:4:5
  |
4 | use winrt::windows::ui::notifications::*;
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Could not find `ui` in `windows`

error: aborting due to 2 previous errors

error: Could not compile `hello_world`.

Caused by:
  process didn't exit successfully: `rustc --crate-name hello_world src\main.rs --crate-type bin --emit=dep-info,link -C debuginfo=2 -C metadata=1d57d6994d17b2e4 -C extra-filename=-1d57d6994d17b2e4 --out-dir C:\git\rust\hello\target\debug\deps -L dependency=C:\git\rust\h
ello\target\debug\deps --extern winrt=C:\git\rust\hello\target\debug\deps\libwinrt-9ac1a1eab3936cb9.rlib` (exit code: 101)
PS C:\git\rust\hello>

This seems to be the same as #38. Is there any way in which we could make this clearer in the documentation?

Sorry for the duplicate issue.
Is there no way to make features depend on each other automagically?
Failing that, perhaps the example should include (at least a fragment of) a Cargo.toml file - perhaps in a comment at the top of the file?

@voltagex I tried to improve the wording of the README in this PR branch: https://github.com/Boddlnagg/winrt-rust/tree/multifile-gen. It now includes a fragment of Cargo.toml. What do you think, is this better?
Surely there is lots of room for improvement still ...

winapi-rs uses a custom build.rs file that turns on features based on the dependency graph. Perhaps a similar file could be used in this case too.
However, their build.rs file is manually written. I don't know if the Windows Metadata files also contain dependency information, and manually writting all the dependencies for this huge API might take quite a while.

@GuildMasterInfinite Interesting! However, in WinRT, the number of features is rather small, and problem with interdependencies are already worked around by cfg'ing out parts of the API (e.g., if a function in Windows.System refers to a data structure defined in Windows.Storage, that function will not be available unless Windows.Storage is also enabled via the windows-storage feature.
I don't see any way to make the handling of features any easier, except maybe:

Enable all features by default and let the user opt out of that. IMHO this leads to unacceptable compile times in the common case (i.e., people will complain).
Have some way of analyzing the source code of the application to collect all the required features of WinRT. I'm not even sure whether this is possible, but I think it would be too much magic with not enough benefit.

By the way, when you're writing a C# application for WinRT, you also have to manually reference all the WinMD files that are directly needed. Since WinMD files map 1:1 to our Cargo features, you have to essentially do the same thing when using this crate.

I consider this issue to be solved.


 statements

I tried to automate SSH key distribution over Napalm with this driver. If I get it right driver uploads the generated configuration to the switch over SCP and then executes copy home://merge_config.txt running-configuration .
The problem I encountered is that when I have this statement in the merge_config.txt file:
itchy# show file home merge_config.txt
username ansible sshkey "ssh-rsa xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx==<EMAIL_ADDRESS>
I can execute the copy and it succeeds but the key is not added into running configuration:
itchy# copy home://merge_config.txt running-configuration
Copy completed
itchy# show running-configuration | grep ansible
username ansible password
$6$rounds=656000$xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx role sysadmin priv-lvl 15
itchy#

Is there any reason for not installing the key over copy file running-configuration? I guess this is a bug in OS10, right?
Is there any workaround to achieve SSH key installation into the config?

Btw. I tried it with this OS10 version:
itchy# show version
Dell EMC Networking OS10 Enterprise
Copyright (c) 1999-2020 by Dell Inc. All Rights Reserved.
OS Version: <IP_ADDRESS>
Build Version: <IP_ADDRESS>.190
Build Time: 2020-06-19T21:48:07+0000
System Type: S5248F-ON
Architecture: x86_64
Up Time: 1 day 11:28:12


Changes the license field to valid SPDX

We believe this is currently causing our dependency reviews to fail like:

@chifflier Would you mind taking a look at this? Thanks!

ping @chifflier

Hi,
Sorry for the long delay.
Merged, thanks!


We need a unit test that overflows the famfs metadata log

Log overflow has not been tested yet...
Mind you the default log size has space for >25000 entries, and the minimum allocation unit is 2MiB (but if you're creating files <=2MiB, you're probably missing the point of famfs).
Still: will add such a test

Unit test coming. Glad I dug into this. An off-by-one error was causing log header corruption when the log filled up. Appears to be fixed now, but running more tests.

Tests and the off-by-one issue are fixed in this commit 9b93c0f

Tests and the off-by-one issue are fixed in this commit 9b93c0f


Excessive runtime memory footprint?

Reading about the runtime memory issues got me very worried about the runtime memory footprint of linkding on a typical Windows 10/11 machine. Can you add some information on memory use in the README?

From what I understand, the more memory is availabe to a Docker container the more it will use, unless you explicitly run the container with a memory limit. One cause is that the Linux system running in the container will cache accessed files in memory, and it will continue doing that if it still has memory available. So the stats that people report will vary, depending on how much memory is available on their host system, and how much they give to the container.
That being said, I run the base image on a Raspberry Pi with 1GB RAM, of which linkding takes up 230 MB. For the plus image, which runs Chromium for creating snapshots of websites, memory usage can easily spike way beyond that. To run that you should give the container 1GB of memory to be on the safe side.
Not sure if I can document any conclusive stats yet, but I will consider doing so in the future.


win11上部署，python依赖一直过不去

402.3 Downloading rpds_py-0.20.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (354 kB)
402.7 Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
403.0 Downloading smmap-5.0.1-py3-none-any.whl (24 kB)
404.1 ERROR: THESE PACKAGES DO NOT MATCH THE HASHES FROM THE REQUIREMENTS FILE. If you have updated the > package versions, please update the hashes. Otherwise, examine the package contents carefully; s   someone may have > tampered with them.
404.1     unknown package:
404.1         Expected sha256 0220fce2a62d71cc5e89617419b6224ddb43f1753b00f68b5c9af8b5f41d38c9
404.1              Got        42617eac5241ff34028fd4bed5d42b76526e1b00533d25374eabc67c4b33fa6f
404.1

failed to solve: process "/bin/sh -c pip install --no-cache-dir -r requirements.txt" did not complete successfully: exit code: 1

about Network ?

试试换一下源


feat: As a user, I want to be able to add multiple plugins on an Ingress

Description
I have an ingress that look like that:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: api
  annotations:
    k8s.apisix.apache.org/plugin-config-name: plugin1,plugin2 #Enable plugin1 and plugin2
spec:
  ingressClassName: apisix
  rules:
    - host: api.mycorp
      http:
        paths:
          - path: /api1
            pathType: Prefix
            backend:
              service:
                name: api1
                port:
                  number: 80

The requirement is to be able to activate multiple plugins on the same ingress using a comma separated list in the plugin-config-name annotation.

This annotation is a reference to the ApisixPluginConfig resource.
Multiple plugins can be configured at the same time in the ApisixPluginConfig resource.
You can refer to this one.
https://github.com/apache/apisix-ingress-controller/blob/5beb519f24b0a8dc534e97285bb442721eeb13a4/test/e2e/suite-annotations/plugin_conifg.go#L31-L46

Seems good to me, thank you @tao12345666333


raidboss: add callout to swap or stay during XFold Blast

Currently, the callout for XFold Blast accumulates and then calls out
the chain of N/S one time near the start of the mechanic.
This works ok, but it can be easy to get lost in the middle and lose
track of whether you need to swap or not.
Detect when the previous XFold Blast hits, and call a swap or stay. Use
a response, so that swaps are called at alert level, while stay is
called at info level. This gives a nice cadence to the indicator and at
least helps me stay aware.
Signed-off-by: Jacob Keller<EMAIL_ADDRESS>

This is another option I've been running for a while, and I prefer. I suspect it may be too spammy for general mainline, but wanted to get opinions.

I somewhat feel that it would be better to explicitly call "north" or "south" each time instead of "swap" or "stay"; if someone starts or ends up (possibly due to mistake or raise) on the wrong side at some point and continues to follow the calls, they could end up swapping or staying on the incorrect side multiple times.

That's true.. but I did like the alert vs info to distinguish between needing to do something or stay put when correct already. Its a nice audible reminder.
I suppose it could be possible to get character position and check what side you're already on?

I suppose it could be possible to get character position and check what side you're already on?

It's possible, but that feels like it might be a bit of overkill for this mech.  I agree that North/South is more optimal than stay/swap here, and perhaps then change the North/South call from an alert to info if it's the same as the prior cleave.  That would satisfy the objective to use an infoText if no movement is required, and there's no need for stay vs. swap or determining character positions?

I suppose it could be possible to get character position and check what side you're already on?

It's possible, but that feels like it might be a bit of overkill for this mech. I agree that North/South is more optimal than stay/swap here, and perhaps then change the North/South call from an alert to info if it's the same as the prior cleave. That would satisfy the objective to use an infoText if no movement is required, and there's no need for stay vs. swap or determining character positions?

Strictly speaking it currently calls out "Swap (S)" or "Swap (N)" and "Stay (S)" or "Stay (N)", but I agree thats a bit harder to read.


What's new for pr 4387

🚀 Pull Request
Description

What's new entry separate to PR to prevent too many conflicts in latest.rst

Consult Iris pull request check list

Checked docs build locally


Added a function that plots log-likelihood scores

this looks great @bayonato89 ! i haven't looked through the code in detail yet, but i did notice that i think we want to place these functions in csep/utils/plots.py. i will take a look through the code in the next couple of days.

Removed the plot_diff_spatial_likelihood function from the poisson_evaluation.py file, and inserted it into the plots.py file.

Codecov Report

Merging #119 (f13a7d3) into master (40c28bb) will increase coverage by 0.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   56.88%   57.46%   +0.58%
==========================================
  Files          19       19
  Lines        3115     3120       +5
  Branches      451      452       +1
==========================================
+ Hits         1772     1793      +21
+ Misses       1237     1217      -20
- Partials      106      110       +4

Impacted Files
Coverage Δ

csep/core/poisson_evaluations.py
45.63% <ø> (ø)

csep/core/forecasts.py
55.93% <0.00%> (+0.84%)
:arrow_up:

csep/core/catalogs.py
60.07% <0.00%> (+2.20%)
:arrow_up:

csep/utils/calc.py
53.57% <0.00%> (+3.57%)
: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 40c28bb...f13a7d3. Read the comment docs.

@bayonato89 i'd like to first add this function to the documentation to show an example of how to make a custom figure using matplotlib. having some kind of a cookbook could be cool and this figure might be a nice start. i can think of a few functions in the current plots.py module that could be better suited as cookbook recipes than included in the distribution. what do you think @bayonato89 @pabloitu @mherrmann3 ?

Yes, documenting how to 'cook' custom plots is a good idea, but doesn't plots.py and @bayonato89's new plotting function already serve as guide by themselves? That is, CSEP users with Python experience will figure it out how to "cook by themselves". The question is how often a regular CSEP user wants to create custom plots - and what type of plots?
For instance, this new plotting function of @bayonato89 shows a data layer on a map, which may be a common use case for which CSEP has already appropriate functions. But entirely new plots are rather difficult to anticipate. In case we want to document the 'cooking' in more detail, it may be sufficient to focus on one or more cases that adapt/extend one of CSEP's elemental plotting functions (e.g., a map) with a new feature (layer). For this purpose, I believe that @bayonato89's example is actually a good candidate to document. (side note: shouldn't this function make use of plot_basemap like plot_spatial_dataset does? In this case, plot_spatial_dataset is also a good candidate for illustrating how to adapt it to a custom layer.)
@wsavran: Did you intend to make this 'cookbook' a subsection of docs.cseptesting.org/tutorials/plot_customizations.html?
In addition, we might also include an enumeration of elemental CSEP plotting functions that have the potential to be extended/modified.

@mherrmann3 I agree plots.py does that as well as the new function that @bayonato89 wrote. The main difference is where the information is found. In the case of plots.py users would have to read the code possibly from GitHub if they didn't install from source.
In the case of the 'cookbook' it would be a new section on the documentation page at the same level (or one below) tutorials. An example URL might read docs.cseptesting.org/cookbook/plot_log_likelihood_scores.html.
A main reason for this is that we could provide a place where users could submit 'recipes' (they don't necessarily have to be plotting functions) that aren't required to work with the pyCSEP plotting wrapper (ie plot_basemap and plot_spatial_dataset) or interface completely with the pyCSEP natives. The expectation would be that a user could copy-paste this function into their script and modify it as needed as opposed to us abstracting away every option that a new user might want (similar to the way plot_catalog or plot_spatial_dataset works. It seems like an efficient way to allow for useful new contributions while keeping the development requirements somewhat low.
Candidate functions to move into the cookbook would be

plot_cumulative_events_versus_time_dev
plot_cumulative_events_versus_time
plot_magnitude_versus_time
plot_ecdf
plot_magnitude_histogram_dev
plot_magnitude_histogram

Ah, now I got you. (I understood to create a place where some pyCSEP functions are described in more detail to help creating new ones).
So it's about a collection of optional functions. Yes, I like this idea! Basically like gist.github.com integrated into our docs. We could also think about shipping them with pyCSEP in a separate module (e.g., 'addons') to facilitate their use.
PS: should we move this discussion to a new issue?

@mherrmann3 yes exactly! its kind of a place to allow for contributions that make sense to share with others but work standalone and dont' need to be integrated into the main package.  i have started a notebooks folder that we might use for this. that way functions can be self documented within the package. im closing this pull request, but opening in an new issue to continue the discussion.


Nodejs deprecations and warnings

user@desktop1:~/vcs/easy-wallet/App$ npm i ../RTNMonero/
npm WARN deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":">=14"} (current: {"node":"10.19.0","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":">=12"} (current: {"node":"10.19.0","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(../RTNMonero/node_modules/jest-haste-map/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN App No description
npm WARN App No repository field.
npm WARN App No license field.

       v18.16.0   (Latest LTS: Hydrogen)
user@desktop1:~/vcs/easy-wallet/App$ nvm i 18.16
Downloading and installing node v18.16.0...
Downloading https://nodejs.org/dist/v18.16.0/node-v18.16.0-linux-x64.tar.xz...
--2023-06-03 12:58:30--  https://nodejs.org/dist/v18.16.0/node-v18.16.0-linux-x64.tar.xz
Распознаётся nodejs.org (nodejs.org)… <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700:10::6814:162e, ...
Подключение к nodejs.org (nodejs.org)|<IP_ADDRESS>|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… 200 OK
Длина: 23734296 (23M) [application/x-xz]
Сохранение в: «/home/user/.nvm/.cache/bin/node-v18.16.0-linux-x64/node-v18.16.0-linux-x64.tar.xz»

/home/user/.nvm/.cache/bin/node-v18.16.0-linux-x64/n 100%[=====================================================================================================================>]  22,63M  9,60MB/s    за 2,4s

2023-06-03 12:58:32 (9,60 MB/s) - «/home/user/.nvm/.cache/bin/node-v18.16.0-linux-x64/node-v18.16.0-linux-x64.tar.xz» сохранён [23734296/23734296]

Computing checksum with sha256sum
Checksums matched!
Now using node v18.16.0 (npm v9.5.1)
Creating default alias: default -> 18.16 (-> v18.16.0)
user@desktop1:~/vcs/easy-wallet/App$ npx react-native@latest init EasyWallet
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated<EMAIL_ADDRESS>support for ECMAScript is superseded by `uglify-js` as of v3.13.0


3.1.0 fix '[Linux] Hide duplicate GPU lines (Only display 1)' isn't working for me

My neofetch output includes:
GPU: Intel 965GM
GPU: Intel 965GM
Neofetch version
~ $ neofetch --version
Neofetch 3.1.0

Screenshot

Config file
#!/usr/bin/env bash
# vim:fdm=marker
#
# Neofetch config file
# https://github.com/dylanaraps/neofetch

# Speed up script by not using unicode
export LC_ALL=C
export LANG=C

# Info Options {{{

# Info
# See this wiki page for more info:
# https://github.com/dylanaraps/neofetch/wiki/Customizing-Info
printinfo () {
    info title
    info underline

    info "OS" distro
    info "Kernel" kernel
    info "Uptime" uptime
    info "Packages" packages
    info "Shell" shell
    info "Resolution" resolution
    info "DE" de
    info "WM" wm
    info "WM Theme" wmtheme
    info "Theme" theme
    info "Icons" icons
    info "Font" font
    info "CPU" cpu
    info "GPU" gpu
    info "Memory" memory

    # info "Disk" disk
    # info "Battery" battery
    # info "Local IP" localip
    # info "Public IP" publicip
    # info "Users" users
    # info "Birthday" birthday
    # info "Song" song

    info linebreak
    info cols
    info linebreak
    info linebreak
}

# Kernel

# Show more kernel info
# --kernel_shorthand on/off
kernel_shorthand="on"

# Distro

# Mac OS X hide/show build version
# --osx_buildversion on/off
osx_buildversion="on"

# Mac OS X hide/show codename
# --osx_codename on/off
osx_codename="on"

# Show 'x86_64' and 'x86' in 'Distro:' output.
# --os_arch on/off
os_arch="on"

# Uptime

# Shorten the output of the uptime function
# --uptime_shorthand tiny, on, off
uptime_shorthand="off"

# Shell

# Show the path to $SHELL
# --shell_path on/off
shell_path="on"

# Show $SHELL's version
# --shell_version on/off
shell_version="off"

# CPU

# CPU speed type
# Only works on Linux with cpufreq.
# --speed_type current, min, max, bios,
# scaling_current, scaling_min, scaling_max
speed_type="max"

# CPU Display
# Set shorthand setting and progress bar setting
# --cpu_display (name, speed, tiny, on, off) (bar, infobar, barinfo, off)
cpu_shorthand="off"
cpu_display="off"

# CPU Cores
# Display CPU cores in output
# --cpu_cores on/off
cpu_cores="on"

# GPU

# Shorten output of the getgpu funcion
# --gpu_shorthand on/off/tiny
gpu_shorthand="on"

# Resolution

# Display refresh rate next to each monitor
# Unsupported on Windows
# --refresh_rate on/off
refresh_rate="off"

# Gtk Theme / Icons

# Shorten output (Hide [GTK2] etc)
# --gtk_shorthand on/off
gtk_shorthand="off"

# Enable/Disable gtk2 theme/icons output
# --gtk2 on/off
gtk2="on"

# Enable/Disable gtk3 theme/icons output
# --gtk3 on/off
gtk3="on"

# Battery

# Which battery to display.
# By default we display all batteries.
# NOTE: Only works on Linux.
# --battery_num all, 0, 1, 2, etc
battery_num="all"

# Whether or not to print each battery on the same line.
# By default each battery gets its own line and title.
# NOTE: Only works on Linux.
# --battery_shorthand on/off
battery_shorthand="off"

# IP Address

# Website to ping for the public IP
# --ip_host url
public_ip_host="http://ident.me"

# Song

# Print the Artist and Title on seperate lines
# --song_shorthand on/off
song_shorthand="off"

# Birthday

# Whether to show a long pretty output
# or a shortened one
# NOTE: Long pretty output doesn't work on OpenBSD or NetBSD.
# --birthday_shorthand on/off
birthday_shorthand="off"

# Whether to show the time in the output
# --birthday_time on/off
birthday_time="on"

# Date format to use when printing birthday
# --birthday_format "format"
birthday_format="+%a %d %b %Y %l:%M %p"

# Color Blocks

# Color block range
# --block_range start end
start=0
end=7

# Toggle color blocks
# --color_blocks on/off
color_blocks="on"

# Color block width
# --color_block_width num
block_width=3

# }}}

# Text Colors {{{

# Text Colors
# Each number represents a different part of
# the text in this order:
# title, @, underline, subtitle, colon, info
# colors=(4 6 1 8 8 6)
# You can also specify:
# fg (foreground color)
colors=(distro)

# }}}

# Text Options {{{

# Toggle line wrapping
# --line_wrap on/off
line_wrap="off"

# Toggle bold text
# --bold on/off
bold="on"

# Enable/Disable Underline
# --underline on/off
underline_enabled="on"

# Underline character
# --underline_char char
underline_char="-"

# Prompt height
# You should only have to change this if your
# prompt is greater than 2 lines high.
# --prompt_height num
prompt_height=1

# }}}

# Progress Bars {{{

# Progress bar character
# --progress_char elapsed_char total_char
progress_char_elapsed="-"
progress_char_total="="

# Progress vorder
# --progress_border on/off
progress_border="on"

# Progress bar length in spaces
# Number of chars long to make the progress bars.
# --progress_length num
progress_length="15"

# Progress bar colors
# When set to distro, uses your distro's logo colors
# Takes: num, "distro"
# --progress_colors col col
progress_color_elapsed="distro"
progress_color_total="distro"

# Customize how the info is displayed.
# bar: Only the progress bar is displayed.
# infobar: The bar is displayed after the info.
# barinfo: The bar is displayed before the info.
# off: Only the info is displayed.
#
# --memory_display bar/infobar/barinfo/off
# --battery_display bar/infobar/barinfo/off
# --disk_display bar/infobar/barinfo/off
memory_display="off"
battery_display="off"
disk_display="off"

# }}}

# Image Options {{{

# Image Source
# --image wall, ascii, /path/to/img, /path/to/dir/, off
image="ascii"

# Thumbnail directory
thumbnail_dir="$HOME/.cache/thumbnails/neofetch"

# W3m-img path
# Some systems have this in another location
w3m_img_path="/usr/lib/w3m/w3mimgdisplay"

# Image position
# Only works with the w3m backend
# --image_position left/right
image_position="left"

# Crop mode
# --crop_mode normal/fit/fill
crop_mode="normal"

# Crop offset
# Only affects normal mode.
# --crop_offset northwest/north/northeast/west/center
#               east/southwest/south/southeast
crop_offset="center"

# Image size
# The image is half the terminal width by default.
# --size auto, 00px, 00%
image_size="auto"

# Right gap between image and text
# --gap num
gap=2

# Image offsets
# --xoffset px
# --yoffset px
yoffset=0
xoffset=0

# }}}

# Ascii Options {{{

# Default ascii image to use
# When this is set to distro it will use your
# distro's logo as the ascii.
# --ascii 'distro', path/to/ascii
ascii="distro"

# Ascii colors
# When this is set to distro it will use your
# ditro's colors to color the ascii.
# NOTE: You can also set this to a range of colors
# which will allow you to custom color distro logos
# --ascii_colors distro
# --ascii_colors 2 4 5 6
ascii_colors=(distro)

# Logo size
# Arch, Crux and Gentoo have a smaller logo
# variant. Changing the value below to small
# will make neofetch use the small logo.
# --ascii_logo_size small, normal
ascii_logo_size="normal"

# }}}

# Scrot Options {{{

# Whether or not to always take a screenshot
# You can manually take a screenshot with "--scrot" or "-s"
scrot="off"

# Screenshot program to launch
# --scrot_cmd
scrot_cmd="scrot -c -d 3"

# Scrot dir
# Where to save the screenshots
# --scrot_dir /path/to/screenshot/folder
scrot_dir="$HOME/Pictures/"

# Scrot filename
# What to name the screenshots
# --scrot_name str
scrot_name="neofetch-$(date +%F-%T).png"

# }}}

# Stdout options {{{

# Separator for stdout mode
# --stdout_separator string
stdout_separator="  "

# }}}

# Config Options {{{

# Enable/Disable config file
# --config off, none
config="on"

# Path to custom config file location
# --config path/to/config
config_file="${XDG_CONFIG_HOME:-${HOME}/.config}/neofetch/config"

}}}
Verbose log
https://pastebin.com/KxVHEKij
My system: Mint 18.1 x64 Cinnamon

Fixed.
Thanks for reporting this!

I am sorry to report this, but I just did a gitclone, and then opened a new terminal and ran neofetch and: the problem is still there; the program reports the same version number as before (namely 3.1.0).

Weird.
Are you 100% sure you're using the git cloned version? Try another git clone and --version, I just pushed a commit to report a different version from 3.1.0.

Something weird is indeed going on:
MMMMMMMMMMMMMMMMMMMMMMMMMmds+.       nicholas@Laptop
MMm----::-://////////////oymNMd+`    ---------------
MMd      /++                -sNMd:   OS: Linux Mint 18.1 Serena x86_64
MMNso/`  dMM    `.::-. .-::.` .hMN:  Kernel: 4.10.0-19-generic
ddddMMh  dMM   :hNMNMNhNMNMNh: `NMm  Uptime: 44 minutes
    NMm  dMM  .NMN/-+MMM+-/NMN` dMM  Packages: 3649
    NMm  dMM  -MMm  `MMM   dMM. dMM  Shell: /bin/bash
    NMm  dMM  -MMm  `MMM   dMM. dMM  Resolution: 1280x800
    NMm  dMM  .mmd  `mmm   yMM. dMM  DE: Cinnamon 3.2.7
    NMm  dMM`  ..`   ...   ydm. dMM  WM: Mutter (Muffin)
    hMM- +MMd/-------...-:sdds  dMM  WM Theme: Cinnamon (SimpleX-Grayscale_NJ)
    -NMm- :hNMNNNmdddddddddy/`  dMM  Theme: Mint-Y [GTK2/3]
     -dMNs-``-::::-------.``    dMM  Icons: Paper [GTK2/3]
      `/dMNmy+/:-------------:/yMMM  Font: Noto Sans UI 11 [GTK2/3]
         ./ydNMMMMMMMMMMMMMMMMMMMMM  CPU: Intel 2 Duo T7500 (2) @ 2.201GHz
            .MMMMMMMMMMMMMMMMMMM     GPU: Intel 965GM
                                     GPU: Intel 965GM
                                     Memory: 3017MiB / 7972MiB

~ $ neofetch --version
Neofetch 3.1.0

Copyright (c) 2016-2017 Dylan Araps

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the 'Software'), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Written by Dylan Araps with help from the following people:

https://github.com/dylanaraps/neofetch/contributors

~ $ sudo apt remove neofetch
[sudo] password for nicholas:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED
  neofetch
0 to upgrade, 0 to newly install, 1 to remove and 1 not to upgrade.
After this operation, 301 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 480029 files and directories currently installed.)
Removing neofetch (3.1.0-1~ubuntu16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
~ $ sudo apt install neofetch
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  cmus feh mpc nitrogen moc
The following NEW packages will be installed
  neofetch
0 to upgrade, 1 to newly install, 0 to remove and 1 not to upgrade.
Need to get 0 B/64.1 kB of archives.
After this operation, 301 kB of additional disk space will be used.
Selecting previously unselected package neofetch.
(Reading database ... 479911 files and directories currently installed.)
Preparing to unpack .../neofetch_3.1.0-1~ubuntu16.04.1_all.deb ...
Unpacking neofetch (3.1.0-1~ubuntu16.04.1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up neofetch (3.1.0-1~ubuntu16.04.1) ...
~ $ neofetch --version
Neofetch 3.1.0

Perhaps I have more than one version installed? I'll investigate

I removed all the files on my system to do with neofetch - save ones in the trash bin, and a copy of neofetch source in my home folder and I got the same results.

Can you send me the output of lspci -mm?

Here it is. But note that neofetch itself - as against my system when
installing or removing it - is still displaying the wrong version
number. Note also that my system does - to other applications, and the
kernel - misreport the number of CPUs (it's a bug - a BIOS one I think);
but I thought this was what you were working around.
~ $ lspci -mm
00:00.0 "Host bridge" "Intel Corporation" "Mobile PM965/GM965/GL960
Memory Controller Hub" -r0c "Dell" "Mobile PM965/GM965/GL960 Memory
Controller Hub"
00:02.0 "VGA compatible controller" "Intel Corporation" "Mobile
GM965/GL960 Integrated Graphics Controller (primary)" -r0c "Dell"
"Mobile GM965/GL960 Integrated Graphics Controller (primary)"
00:02.1 "Display controller" "Intel Corporation" "Mobile GM965/GL960
Integrated Graphics Controller (secondary)" -r0c "Dell" "Mobile
GM965/GL960 Integrated Graphics Controller (secondary)"
00:1a.0 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB
UHCI Controller #4" -r02 "Dell" "82801H (ICH8 Family) USB UHCI Controller"
00:1a.1 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB
UHCI Controller #5" -r02 "Dell" "82801H (ICH8 Family) USB UHCI Controller"
00:1a.7 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB2
EHCI Controller #2" -r02 -p20 "Dell" "82801H (ICH8 Family) USB2 EHCI
Controller"
00:1b.0 "Audio device" "Intel Corporation" "82801H (ICH8 Family) HD
Audio Controller" -r02 "Dell" "82801H (ICH8 Family) HD Audio Controller"
00:1c.0 "PCI bridge" "Intel Corporation" "82801H (ICH8 Family) PCI
Express Port 1" -r02 "" ""
00:1c.1 "PCI bridge" "Intel Corporation" "82801H (ICH8 Family) PCI
Express Port 2" -r02 "" ""
00:1c.3 "PCI bridge" "Intel Corporation" "82801H (ICH8 Family) PCI
Express Port 4" -r02 "" ""
00:1c.5 "PCI bridge" "Intel Corporation" "82801H (ICH8 Family) PCI
Express Port 6" -r02 "" ""
00:1d.0 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB
UHCI Controller #1" -r02 "Dell" "82801H (ICH8 Family) USB UHCI Controller"
00:1d.1 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB
UHCI Controller #2" -r02 "Dell" "82801H (ICH8 Family) USB UHCI Controller"
00:1d.2 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB
UHCI Controller #3" -r02 "Dell" "82801H (ICH8 Family) USB UHCI Controller"
00:1d.7 "USB controller" "Intel Corporation" "82801H (ICH8 Family) USB2
EHCI Controller #1" -r02 -p20 "Dell" "82801H (ICH8 Family) USB2 EHCI
Controller"
00:1e.0 "PCI bridge" "Intel Corporation" "82801 Mobile PCI Bridge" -rf2
-p01 "" ""
00:1f.0 "ISA bridge" "Intel Corporation" "82801HM (ICH8M) LPC Interface
Controller" -r02 "Dell" "82801HM (ICH8M) LPC Interface Controller"
00:1f.1 "IDE interface" "Intel Corporation" "82801HM/HEM (ICH8M/ICH8M-E)
IDE Controller" -r02 -p8a "Dell" "82801HM/HEM (ICH8M/ICH8M-E) IDE
Controller"
00:1f.2 "SATA controller" "Intel Corporation" "82801HM/HEM
(ICH8M/ICH8M-E) SATA Controller [AHCI mode]" -r02 -p01 "Dell"
"82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode]"
00:1f.3 "SMBus" "Intel Corporation" "82801H (ICH8 Family) SMBus
Controller" -r02 "Dell" "82801H (ICH8 Family) SMBus Controller"
09:00.0 "Ethernet controller" "Broadcom Corporation" "NetXtreme BCM5755M
Gigabit Ethernet PCI Express" -r02 "Dell" "NetXtreme BCM5755M Gigabit
Ethernet PCI Express"
0c:00.0 "Network controller" "Intel Corporation" "PRO/Wireless 4965 AG
or AGN [Kedron] Network Connection" -r61 "Intel Corporation"
"PRO/Wireless 4965 AG or AGN"

I've figured out what was happening and I've now fixed it. Please try another git clone.

With the newest version, two GPUs are not reported and the version
number is correct. However, no GPU at all was reported!

I'll revert the change and investigate further.

It would be nice to have this fixed. I've just tried the current git version and . .

Still, it's only a minor bug.

Yup, still working on a cleaner fix. Hence why the issue is still open. I've been insanely busy with university and I'll get started on the open bugs once my break starts.


Find why DispatcherServlet is initialized on first request on JVM and startup on native image

This difference of behavior is a real issue since DispatcherServlet early initialization triggers DispatcherServlet.properties + reflection initialization which requires more configuration on GraalVM native.
This seems to be triggered by a difference of behavior in Tomcat connection pool on native image, not sure why yet.
With this + https://github.com/spring-projects/spring-framework/issues/25209 and related Spring Fu update, we should be able to remove DispatcherServlet substitution.

Hi @sdeleuze
Servlet Initialization
I took a brief look on what boot is doing. Right now, Spring Boot is configuring servlets for lazy initialization.
When I say initialization, I specifically refer to
javax.servlet.Servlet.init(ServletConfig config);

modifying application.properties to include the line
spring.mvc.servlet.load-on-startup=1

will ensure that the DispatcherServlet is loaded and initialized at startup instead of on the first request (first request = default)
When I ran this example, I'm seeing the correct behavior for native-image as well as JVM for both 1 and -1 values
DispatcherServlet.properties
For both JVM and native-image, the DispatcherServlet.properties file is loaded when the class is loaded, during application startup. (not on first request)
On the JVM, DispatcherServlet.properties is loaded SpringApplication.run calls refreshContext
On native-image, DispatcherServlet.properties is loaded SpringApplication.run calls refreshContext
I'm seeing the same behavior for both runtime environments.
java.lang.Exception: FILIP-DispatcherServlet.initStrategies
        at org.springframework.web.servlet.DispatcherServlet.initStrategies(DispatcherServlet.java:505)
        at org.springframework.web.servlet.DispatcherServlet.onRefresh(DispatcherServlet.java:497)
        at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:599)
        at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:530)
        at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:170)
        at javax.servlet.GenericServlet.init(GenericServlet.java:158)
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1134)
        at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:135)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:541)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:139)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343)
        at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:373)
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868)
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1590)
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        at java.lang.Thread.run(Thread.java:748)
        at com.oracle.svm.core.thread.JavaThreads.threadStartRoutine(JavaThreads.java:517)
        at com.oracle.svm.core.posix.thread.PosixJavaThreads.pthreadStartRoutine(PosixJavaThreads.java:192)

@fhanik I agree with the behavior you describe, but what I was not able to find is how to have the same behavior on JVM and native image with Boot defaults (lazy servlet loading).
On native image, it seems we have an eager loading of the servlet by default (to be confirmed). Is it what you observe as well?

After more tests it indeed seems consistent so I close this issue.


docs: remove non existing utility classes from documentation

Description
Jira ticket: https://dialpad.atlassian.net/browse/DLT-1368
Affects the utility classes docs that where using apps/dialtone-documentation/docs/_data/spacing.json to obtain the values, these are: margin, padding, auto-spacing and gap.
margin and padding have the same values, but gap and auto-spacing have other ones.
Check that the shown values are the same as the generated ones in dialtone.css
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

spacing.json

I honestly didn't check, I only checked for the ones that used spacing.json. Let me see if a can find a method to review that

We are merging this as is for now since checking every utility class is a big effort. We might get more reports in the future, and maybe we can think of a better way to generate the docs.


Update models.py to support more functionalities

Some future functionalities require a change in models.py for support. We want to add a field to the tournament model to represent the number of winners and modify the tournament model to provide support to the tournament bracket functionality. Also, we plan to add support for the admin interface to handle models.

In this #209 pull request, we have made some changes to
allow developers to access the tournament models through the admin interface (admin.py).
add a num_winner field to the tournament model to keep track of the number of winners for a tournament.
make the matches and players fields of the tournament model optional during the creation and edition of a tournament such that users can join and withdraw from a tournament by themselves instead of from direct assignment. Also, matches are made optional because they should be created through the bracket assignment mechanism in issue.

Issue Score: Excellent
Comments:
Good job! Same comments as the PR - minor but important change.


Feature request: slower PWM

Hi, thank you for this great firmware.
I'd like to bllink a load (i.e. a LED) at 0.5Hz, 1Hz or 2Hz. Could you please add this feature to the PWM options?
Thank you... and I owe you a cofee!

Hi,
Thank you for a coffee :)!
Sorry, but PWM cannot work at this frequency.
I think you can use a "Pulse generator" option for your task.

Hi, the pulse generator could do, but I do not see a way to stop it counting. Would it be possible to have an on/off cluster for that?
Thank you

Added in the latest version. But the minimum frequency is 4 Hz.

Ok, so it's still a PWM configuration. There is no way to start/stop the pulse generator from an output cluster, right?
Thank you.

Any PWM endpoint also supports the ON/OFF commands.


Clarification on Assign Built in User-Assigned Managed Identity to Virtual Machines is optional on Enable Azure Automation Change Tracking using AMA at scale

Documentation mentions for enabling at scale to use Azure Policy Initiative with one of the Policy Definitions Assign Built in User-Assigned Managed identity to virtual machines.
Link to documentation: https://learn.microsoft.com/en-us/azure/automation/change-tracking/enable-vms-monitoring-agent?tabs=singlevm%2Cvm#enable-change-tracking-at-scale-using-azure-monitoring-agent

Ask:

Customers can choose to assign User-Assigned Managed Identity or System-Assigned Managed Identity (default) for AMA. No identity is required for Change Tracking extension.
Perhaps it helps to clarify mentioning this in documentation.

Thanks.

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

ID: b493df17-cc47-7e08-243a-81529db45092
Version Independent ID: 655d96db-77dd-df0a-54be-77487158cdfe
Content: Enable Azure Automation Change Tracking for single machine and multiple machines from the portal.
Content Source: articles/automation/change-tracking/enable-vms-monitoring-agent.md
Service: automation
Sub-service: change-inventory-management
GitHub Login: @SnehaSudhirG
Microsoft Alias: sudhirsneha

@nickylian1
Thanks for your feedback! We will investigate and update as appropriate.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


The format of the input data

Can you offer the 'data.csv' used to train this model, as I want to know the format of the input data. Thank you!

Please see section on Dataset Description in paper. You can use subset of MIMIC-III. But as mentioned in the notebook pre-processing is required according to the use case.


Can't get markup "includes" working as expected (from kss-node)

I was hoping to be able to use direct html / hbs includes (as described within kss-node) as part of a gulp build but cant figure out how / it doesn't seem to work!
Example:
/buttons/_button.scss
// markup: button.html

/buttons/button.html
<button class="myButton">foo</button>

I can get the html field copied as part of the build but sc5 never renders the html fragment in button.html
Am I missing something?

Apologies. I understand that the convention for providing the markup as a file is:
//markup:
//button.html


Media section added above FAQ with Press releases and in the news

As per discussion in slack #general with @pesa<EMAIL_ADDRESS>- he was saying that media has a tougher time writing about Bitcoin Cash due to quotes going direct to websites such as bitsonline or bitcoin.com - which they can't use. He recommended any quotes from Development team to articles be included in a press release to allow more writers to re-use the same quotes without getting in trouble.
We discussed adding a Press Release section. @peso also offered to write Press Releases for Bitcoin Cash, he just needs a full days notice. But if we have any public updates from development team it might be good to place press releases online as well as highlight stories on Bitcoin Cash.
This section isn't perfect as it will struggle with > 15-20 Press Releases or Articles, but it buys time.
If someone can find 5-10 articles to link to for "In the news" and if we can dig up or write 3 press releases re: bitcoin cash it should be safe to go up.

I think this looks really good. We just need to populate it with good content before we add it!

@zquestz the problem is , who is going to maintain this?

@fyookball that is a great question. I would hope that if we added this with relevant recent content that the community could propose updates here on github. I also would be willing to propose updates and put up PRs here. That being said, it is a decent amount of work to keep it up to date, and this content might be more appropriate for a blog in the future.

Unless there is a dedicated resource, this will inevitably fall into either a deprecated state or mismanagement.
BitcoinCash.org is (I believe) supposed to be an informational website about the protocol and ecosystem.  It is not the appropriate entity to be feeding info bytes to the media.
Therefore, I am against this.

@fyookball that is a very reasonable concern. There are pros and cons for sure. That being said, it would have been great to have a way to link to the difficulty adjustment proposals and other technical progress being made for Bitcoin Cash.
Perhaps it should be on another site. If someone wants to own a great Bitcoin Cash news site, perhaps there is a way to add them as a resource in the FAQ, or link to that resource rather than having the content directly on bitcoincash.org.

Completely understandable about concerns re managing content. Just throwing some ideas around, but what if we just jack in an RSS feed from say bitcoin.com's Bitcoin Cash tag:
https://news.bitcoin.com/tag/bitcoin-cash/rss
That could supply regular content, or we could include additional sources from Coingeek:
https://coingeek.com/tag/bitcoin-cash/feed/
We could easily do that by just parsing the XML with Jquery. Doesn't give us any ability to moderate, but even if we just pull in from bitcoin cash friendly news sources and just display the latest 5-10 posts, then that leaves the Press Releases as the only thing we need to worry about in terms of manual entry.
Thoughts?

@maplesyrupsucker I think this is a reasonable suggestion. Lets put together a list of potential news sources. Anyone else have feedback on this?

Since this PR is out of date I am going to close this. We can revisit adding news when we get done with other sections. =)


Adapter support for GPTNeoX

I have implemented adapter for GPTNeoX following the instructions in the documentation. It passed all tests but during the training of the language adapter, it trained the prediction head too. Do you by chance have an idea why this is happening? Do a PR?

Hey @ajesujoba, this sounds great, would be awesome to have GPTNeoX support integrated into the library, so feel free to do a PR!
Regarding your question on language adapter training, could you add some more context on what you observed and which behavior you expected (ideally with some code snippet). Thank you!

Thanks for providing the additional context (and of course thanks for opening the PR!).
After looking into it a bit deeper, the cause for this behavior seems to be that GPT-NeoX does not tie the weights of the input and output projection layers. By default, adapter-transformers will only freeze the weights of the base model, excluding the weights of any prediction head (as you usually want to fine-tune that with the adapter). Thus, for LM heads, freezing the output projection layer relies on the fact that most models supported so far share these weights with the input projection (which is part of the base model, therefore frozen).
To ensure the expected behavior also for GPT-NeoX, we'd probably need to freeze the output projection manually somewhere in the code. Maybe adding it to the freeze_model() method in the model mixin via self.get_output_embeddings() would work.

Hi @calpt, thanks for your feedback. I thought as much, I also noticed that they did not tie the weights of the input and output projection layers.
Yes, I agree that freezing the prediction head somewhere else such as within freeze_model() would be the best option. I guess this would be done at your end right?

You can directly integrate a fix for this into your PR with the model integration if you like. Otherwise, I could also add it independently.

Checking again it appears it is not plausible to have it fixed within freeze_model(). self within model_mixin.py is the base_model without any prediction head (because the embeddings are not tied). I may be wrong. So I guess a possible place to fix this would be within  training.py. If it is fine with you, you can add it independently so that I don't break a lot of things


Update .ghal.rules.json for v3

I ported the existing ruleset. I need to merge before I can deploy the tool update.
The new tool does not support the old v1 and v2 schemas anymore.

can someone ping me on teams please. I would like to merge all 3 repos using the tool at the same time.


Added emoji-link-tile-format

Q
A

Bug fix?
no

New sample?
yes

Related issues?

What's in this Pull Request?
Added emoji-link-tile-format.

Very cool to see a sample that combines groupProps with the Gallery view! Thanks @tecchan1107!


automated tests

Tests be ran when a pull request is created.   if tests fail, then the pull request cannot be approved.
Branch protection rules will also need to be implemented for this purpose.

https://github.com/almostengr/show-pulse-fpp/commit/54f73d6dffcb43d6efe7541302106978da67e51f


Review of C++ Sample READMEs

For each readme in the DirectProgramming/C++ folder, I reviewed and updated to include consistent instructions for:

Using VS Code
sourcing or running setvars
troubleshooting with the diagnostics utility

Partially Fixes Issue#
https://jira.devtools.intel.com/browse/DOC-9252
External Dependencies
None
Type of change
Please delete options that are not relevant. Add a 'X' to the one that is applicable.

[x ] Documentation

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

[ ] Command Line
[ ] oneapi-cli
[ ] Visual Studio
[ ] Eclipse IDE
[x ] VSCode
[ ] When compiling the compliler flag "-Wall -Wformat-security -Werror=format-security" was used

@ishaghosh27 Please review.

I don't see an option to review this. i think @tomlenth is still the official reviewer.


No images are displayed for the feed articles or only for some feeds.

Steps to Reproduce
For most of the feeds, no images are displayed for the articles. In ReadYou-RSS, however, the images for the feeds are loaded correctly. It is possible that this is not a bug, but just not yet developed far enough. YouTube feeds in particular do not load / display an image preview in the article overview.
Expected behavior
Display of article images for feeds. If the article does not contain an image at all, then of course not.
Screenshots or screen recording
No response
Device, Operating system, and app version
Google Pixel 8. Android 15. GrapheneOS. Capy Reader 2024.12.1086 in combination with FreshRSS.

thanks @OrkoGrayskull - do you have an example feed you can share? I'll use that to compare.

Of couse. Here are some examples:
Working (picture preview):

https://www.spiegel.de/netzwelt/index.rss
https://netzpolitik.org/feed/

Not working (picture preview):

https://www.youtube.com/feeds/videos.xml?channel_id=UC-muQylmRx61Mt6U1oDSEVA
https://www.heise.de/thema/Datenschutz.xml
https://www.youtube.com/feeds/videos.xml?channel_id=UCmygqPg6xajBuGIDnPiXr0g
https://dygma.com/blogs/product-development.atom
https://www.heise.de/security/rss/news.rdf

I really like the Capy Reader. Is there a way to submit a request for new functions?

great, I'll take a look at these and keep this thread up-to-date.
About new functionality, you can post feature requests here: https://github.com/jocmp/capyreader/discussions/new?category=feature-requests. I don't implement every feature request for various reasons (time, simplicity, reach, etc.) but I do read and consider them all!


build: circleci git config being updated too early

Due to the fact that we try to run git config --global before CircleCI set up the global Git configuration, the publish task is still broken. This should fix it.

The bazel_build_test job should be fixed with #13949.


Asset ComputePlan: various improvements

do not redefined _FutureMixin.attach(), already implemented in parent
class
_FutureMixin: raise a proper error if the asset has not been attached when using the session
ComputePlan.list_<tuple>: use session set from the _FutureMixin.attach class method:
ComputePlan.list_<tuple>: add assert to ensure the list methods are working as expected
test_compute_plan: small fix regarding typo in state attributes

Thanks!


Adversarial Transformation Networks (ATN)

Adversarial Transformation Networks: Learning to Generate Adversarial Examples

I'll take this up

I can take this up if no one else it up for it.

yeah @gchhablani you can take it up


Screen goes blue after switching workspace in Linux

Description
Hello!
I'm running manjaro linux with proprietary amd drivers and i3 windows manager. Sometimes, when i switch from atom to another workspace(browser for example) and switch back to workspace with atom, atom goes blue like that:

Sometimes atom become to look like normal, someties only closing editor and reopening it again helps
Steps to Reproduce

Open atom
Change workspace
Change workspace again
Sometimes atom screen goes blue

Versions
atom - 6.5.0
apm - 1.14.1
catalyst - 2016.09-1
compton - 0.1_beta 2.5.3
i3 - i3-gaps 4.12.1-1

Does this happen only with Atom or other applications that are based on Electron / Node?

Versions
atom - 6.5.0

Also there is no version 6.5.0 of Atom, 1.12.2 is the latest stable release.
You can replace this with the output from the atom --version command.

Yes, it goes in every electron app. Here is screenshot of electron with exactly same trouble

But in vivaldi(which has the same chromium engine) everything works fine and there are no blue screen
My versions of atom and electron are
Atom    : 1.11.2
Electron: 1.4.6
Chrome  : 53.0.2785.143
Node    : 6.5.0

Electron: 1.4.6

You are running an unsupported Atom distribution.  Please uninstall it and reinstall from https://atom.io.  In addition, since this appears to be an Electron-related issue, please create an issue on electron/electron instead.


Resource/Media Folder in navx

Hello,
I do not know if my issue is a request or a question.
Is there a way, in a navx package, to store images/files and access these resources by AL?
For instance, I would like provisioning the Media table with new images used by my extension.
I know I can do that by storing my data in a base64 string in AL but this is not very classy :)

See #245


Support default export of a component with hooks

Now genType exports a component like any other function. It would be useful to make it a "default" export.

Could we broaden this issue to be about aligning genType with how Bucklescript supports default exports? Given a reason module like:
[@genType]
let default = 1;

Bucklescript 5.0.2 generates:
var $$default = 1;

export {
  $$default ,
  $$default as default,
}

Taking flow as an example<EMAIL_ADDRESS>creates a file that looks like:
import * as DefaultExportBS from './DefaultExport.bs';
// line below is a syntax error
export const default: number = DefaultExportBS.default;

There would have to be some special behaviour for bs.js files with default exports. One suggestion would be to generate a file that looks like:
import * as DefaultExportBS from './DefaultExport.bs';

const $$default: number = DefaultExportBS.default;
export default $$default;

Anyhow, I wanted to say thanks to everyone involved in this project and I am super enthusiastic about it's potential 👏

@petegleeson that sounds great -- no magic, just support the bucklescript convention.
See: https://github.com/cristianoc/genType/commit/166ef6fb3db30224898fa932687a853934da509c with a couple of examples.

Sounds good, just not sure how such a component will be used both from ReasonML JSX and javascript JSX. https://github.com/cristianoc/genType/commit/166ef6fb3db30224898fa932687a853934da509c#r33202551
If I understand it correctly, <Component/> in Reason calls make. But now it is called default to become the "default" export in javascript.

OK, looks good!  ✅

In https://github.com/cristianoc/genType/pull/180.


refactor(cursors): Use data-uris for cursors

I've switched us from using file-loader to url-loader. This will automatically convert local URL
imports to data URIs, which means the framework no longer needs to load them from a remote URL.
fix #207

I found the cause of build error 🔍👀
But I can't push it to GitHub 😭
I'll push it when I get home. 🏠
# update package-lock.json
$ npm update globby --depth 5

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Move docs to readme inside specific packages

npm can display the docs more easily
user only needs to reference what they're interested in

the bulk is done, can add subheadings another time if needed


Warning: Invalid hook call. Hooks can only be called inside of the body of a function component

What is the problem?
I try to build the package myself and get the following errors:
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component
and
Uncaught TypeError: Cannot read properties of null (reading 'useEffect')
cam you help my?
What is the current behavior?

Please provide the steps to reproduce and create a CodeSandbox.

What is the expected behavior?

Your environment:
Toolset (e.g. webpack, vite, vue-cli...):
Version (@viselect/<insert package>):
Browser:
OS:

I found a solution:
Here


Help! How do I code sack?

Please take a look at my code here:
<ingred type="sack">....</ingred>

Does this look right to you?

(Example closed issue)


feat: Licensing Service Plan Reference Formats

Supply the Licensing Service Plan Reference table as different formats - CSV / JSON.
This is in lieu of waiting for MS to update Graph API to include the Portal 'friendly' names as requested here: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/37398988-add-a-friendly-name-attribute-when-getting-msol-li
https://github.com/MicrosoftDocs/azure-docs/issues/49024

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

Hi @daveba - As business approver for Azure Active Directory, could you review this pull request?
cc @SyntaxC4
Thanks.


example : zero shot closing

Ghost article is added to the README.md, example is closed!
@AyushExel

resolve conflicts


⚠ 366.ru has degraded performance

In 8360a19, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 1998 ms

Resolved: 366.ru performance has improved in e056454.


Add ability to force a hub to send the payload

When msg.payload.forceSend is set the hub will not determine if the state of the node changed, forcing a send regardless of it.
This is useful when the actual state of the device changes without knowledge of the hub.

Hello, @hashworks.
Thanks for your contribution. I want to sheet some light on state change limitation. It was intentionally created to prevent infinite loops if hub output is used as input.
I was thinking to revise the list of input options to:
No
Process
Process and output
Process and output on state change
Would it be helpful for your cases?

Since I've no inputs that could fire twice (or create infinite loops), yes. If one needs both input options one could always create two hubs.

Ok, I will add it in v0.1.10

How is useful to have 2 hubs? Does not has sense to drag 2 hubs on flow? Thanks

How is useful to have 2 hubs? Does not has sense to drag 2 hubs on flow? Thanks

This is only useful if you need different input settings for specific nodes. Then you need one hub with Process and output and one hub with Process and output on state change.


[C++] Fix message id is always the default value in send callback

Motivation
After commit of #4817, the send callback's 2nd argument became MessageId, but the MessageId in callback is always the default value (-1, -1, -1, -1). We need the message id in send callback if messages were sent successfully.
The problem is that the correct message id has been retrieved in ProducerImpl::ackReceived but not passed to the user provided callback. Because after messages were sent to BatchMessageContainer, the wrapper of user provided callback used the MessageId of user constructed Message as the 2nd argument, which is always (-1, -1, -1, -1).
Modifications

Remove useless field messageId of BatchMessageContainer::MessageContainer. Then add const MessageId& argument to batchMessageCallBack instead.
Add tests for message id in send callback. Specially, for a batched message, each internal message's batch index was verified.

Verifying this change

[ ] Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:
Run BasicEndToEndTest.testSendCallback and BatchMessageTest.testSendCallback.

/pulsarbot run cpp-tests

/pulsarbot run unit-tests

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks


Format the code

Looks like the code is in dire need of a good rustfmt pass.

This was done in #279.


Fixed #32946 -- Changed internal usage of dynamic Q() objects construction to use non-kwargs initialization.

Ticket is 32946.
Changes a bunch of internal usages of Q() to prefer Q(('a', 1)) instead of Q(a=1) for consistency (eg: internally split_exclude already does the same thing) and for performance of dynamic generation of them (eg: for creating a long list of x = 1 OR y = 2 OR z = 3 without many intermediate Q objects being combined)
I've avoided (hopefully) touching internal usages that might be considered semi-user-facing, such as ModelBackend.with_perm, the migration 0011_update_proxy_permissions.py, When(...), descriptor filter when it's a dict, limit_choices_to when it's a dict ... etc.
For those where it could be changed (eg: ModelBackend.with_perm) I'll happily do so if requested.
Along the way I've removed the add_filter method. It can come back if desired, but it had been simplified over the years to the point of being a needless wrapper IMHO. YMMV.
Ran 14892 tests in 508.389s
OK (skipped=1193, expected failures=4)

@kezabelle Thanks :+1: I split commits and added small release notes.


Include & reverse include functionality for queries

Add resources that reference the selected or resources that are referenced by the selected resource to the query functionality
Extract the included resources into separate properties in the response

query.include("Resources", reverse=False)