Can't scrape any url from The Washington Post (even with demo)

Kindly, The Washington Post site can't be scrapped; not the root domain, nor any of its links like this article,
I'm already trying on the demo, where it is giving me:

Ooops!!! MetaInspector couldn't scrape this page and complained about:
execution expired

That seems like the site is rejecting the connection, because it detects your request as an automated one. You may try setting a different User-Agent string, but it's probably based on your IP.
Can you check making the request from another server? For example, the demo is hosted on Heroku, but if you check from your laptop maybe you'll get in. In this case it's not a MetaInspector error, it's just that the Washington Post doesn't like your IP.

Well, I've tried from 3 different places:

The demo
My local machine (Egypt)
My production environment (GCP US East region)

where all produced the same issue

I've just tried from my home IP in Argentina and it worked well:
[1] pry(main)> p = MetaInspector.new('https://www.washingtonpost.com/graphics/2020/world/national-security/cia-crypto-encryption-machines-espionage/');nil
=> nil
[2] pry(main)> p.response.status
=> 200
[3] pry(main)> p.title
=> "How the CIA used Crypto AG encryption devices to spy on countries for decades - Washington Post"
[4] pry(main)> p.description
=> "U.S. and German intelligence agencies partnered on a scheme to dupe dozens of nations into buying rigged encryption systems — taking their money and stealing their secrets."
[5] pry(main)> p.images.best
=> "https://www.washingtonpost.com/resizer/5i6h3byfAbADvdFUAn-5RMklGQ4=/1200x630/filters:focal(2231x1260:4531x2559):quality(100)/arc-anglerfish-washpost-prod-washpost/public/JBWJ3HR4RQI6VL7CBEHLG63AWE.jpg"
[6] pry(main)> p.meta_tags
=> {"name"=>
  {"viewport"=>["width=device-width,initial-scale=1,user-scalable=yes,minimum-scale=1,maximum-scale=1"],
   "twitter:title"=>["The CIA secretly bought a company that sold encryption devices across the world. Then its spies sat back and listened."],
   "description"=>
    ["U.S. and German intelligence agencies partnered on a scheme to dupe dozens of nations into buying rigged encryption systems — taking their money and stealing their secrets."],
   "twitter:description"=>
    ["U.S. and German intelligence agencies partnered on a scheme to dupe dozens of nations into buying rigged encryption systems — taking their money and stealing their secrets."],
   "keywords"=>
    ["Crypto AG,CIA,NSA,BND,Cold War,West Germany,encryption machines,German spy agency,Boris Hagelin,William Friedman,Iran hostage crisis,Falklands War,Berlin disco bombing,ZDF,Thesaurus,Rubicon,code-breaking machines,CIA secret history,CIA document,Snowden,Surveillance Huawei,Kaspersky"],
   "twitter:url"=>["https://www.washingtonpost.com/graphics/2020/world/national-security/cia-crypto-encryption-machines-espionage/"],
   "twitter:image"=>
    ["https://www.washingtonpost.com/resizer/5i6h3byfAbADvdFUAn-5RMklGQ4=/1200x630/filters:focal(2231x1260:4531x2559):quality(100)/arc-anglerfish-washpost-prod-washpost/public/JBWJ3HR4RQI6VL7CBEHLG63AWE.jpg"],
   "twitter:site"=>["@postgraphics"],
   "twitter:card"=>["summary_large_image"]},
 "http-equiv"=>{},
 "property"=>
  {"og:title"=>["The CIA secretly bought a company that sold encryption devices across the world. Then its spies sat back and listened."],
   "og:description"=>
    ["U.S. and German intelligence agencies partnered on a scheme to dupe dozens of nations into buying rigged encryption systems — taking their money and stealing their secrets."],
   "og:url"=>["https://www.washingtonpost.com/graphics/2020/world/national-security/cia-crypto-encryption-machines-espionage/"],
   "og:image"=>
    ["https://www.washingtonpost.com/resizer/5i6h3byfAbADvdFUAn-5RMklGQ4=/1200x630/filters:focal(2231x1260:4531x2559):quality(100)/arc-anglerfish-washpost-prod-washpost/public/JBWJ3HR4RQI6VL7CBEHLG63AWE.jpg"],
   "og:type"=>["article"],
   "article:publisher"=>["https://www.facebook.com/washingtonpost"],
   "article:author"=>["https://www.facebook.com/washpostvisuals"],
   "fb:app_id"=>["41245586762"],
   "og:site_name"=>["Washington Post"],
   "fb:admins"=>["1244584375", "4403963", "2724956", "500835072", "1513210492"]},
 "charset"=>["utf-8"]}
[7] pry(main)>

Thanks for your quick response, and hope you the best with the work you are doing here.

Try using a proxy. That did the trick for us. We're currently using NordVPN (US server) and you can pass the proxy info to the faraday_options as the following
page = MetaInspector.new(url, faraday_options: { proxy: "https://#{URI.escape(ENV['PROXY_USER'], '@')}:#{ENV['PROXY_PASSWORD']}@#{ENV['PROXY_ADDRESS']}:80" })


Introducing a high-level FS abstraction

Hi! This originated in a personal learning project and I'd like to know what others think about it. Would be cool if we can bring this upstream. It's about creating a high level FS abstraction over the existing FS protocol. It aims to be as close to top-level functions provided by std::fs as possible.
Motivation
Usually, UEFI-application hackers want to do something like this:

read configuration file from /foo/bar/config
write to /for/bar/log.txt
read /foo/bar/kernel.elf

Code example / API demonstration
    let mut fs = FileSystem::new(
        "boot",
        system_table.boot_services().get_image_file_system(handle).unwrap()
    );

    fs.write("foobar.bin", [1,2,3]).unwrap();
    fs.read("bar").unwrap_err();
    fs.copy("foobar.bin", "bar").unwrap();
    fs.read("bar").unwrap();
    fs.rename("bar", "barfoo").unwrap();
    assert_eq!(fs.read("barfoo").unwrap().as_slice(), &[1, 2, 3]);

    log::info!("fs integration test worked!");

From the module description (initial version; a few changes in the meantime):
//! A high-level file system API for UEFI applications. It supports you to conveniently perform the
//! following important operations:
//! - read file to bytes
//! - write bytes to file
//! - create files
//! - iterate directories and walk the file system tree
//!
//! Unlike UNIX-based file systems, there is no virtual file system. Thus, users perform actions on
//! dedicated volumes: For example, the boot volume, such as a CD-rom, USB-stick, or a storage
//! device. There are no symlinks or hard-links. Just plain paths, directories, and regular files.
//! The way to access a volume is to open a [FileSystem].
//!
//! All paths are absolute and follow the FAT-like file system conventions for paths. Thus, there
//! is no current working directory and path components like "." and ".." are not supported. In
//! other words, the current working directory is always "/", i.e., the root, of the opened volume.
//! This may change in the future but is currently sufficient.
//!
//! There are no `File` and `Path` abstractions that get publicly exported. Paths are provided as
//! `&str` and validated internally. There are no `File` objects that are exposed to users.
//!
//! The difference to using the [SimpleFileSystemProtocol] directly is that the abstractions in this
//! module take care of automatic release of resources and support you by returning data owned on
//! the heap (such as file info). There is no synchronization as it is untypically that users
//! bootstrap Application Processors (AP) during the UEFI stage, i.e., before hand-off to a kernel.

Open Questions

[x] Do we want this at all in uefi-rs?
[x] Integration tests (I have integration tests in my private project so I know it is working)
[x] how to integrate it into the existing code base
[x] verify: apparently there is already a "get boxed file info"-implementation. But I do not know if it respects the dynamically sized C16-string length

Steps to Undraft

[ ] polish documentation a little
[ ] fix integration test

I haven't had a chance to look at the details of this yet, but I'm definitely on board with the idea of a high-level FS API! The motivation you described sounds very reasonable to me. I'll give some more detailed feedback once I get some time to peruse :)

Quick notice: I'm currently on vacation and probably won't work on the PRs until the last week of August

@nicholasbishop @GabrielMajeri I finally had time working on this. It is still not ready to merge but much closer now. I add it as a new workspace member uefi-fs. Let me know what you think.
API examples from the new integration test:
     let mut fs = FileSystem::new(sfs);

    fs.create_dir("test_file_system_abs").unwrap();

    // slash is transparently transformed to backslash
    fs.write("test_file_system_abs/foo", "hello").unwrap();
    // absolute or relative paths are supported; ./ is ignored
    fs.copy("\\test_file_system_abs/foo", "\\test_file_system_abs/./bar").unwrap();
    let read = fs.read("\\test_file_system_abs\\bar").unwrap();
    let read = String::from_utf8(read).unwrap();

    fs.rename("test_file_system_abs\\bar", "test_file_system_abs\\barfoo").unwrap();

    let entries = fs.read_dir("test_file_system_abs").unwrap()
        .map(|e| e.unwrap().file_name().to_string())
        .collect::<Vec<_>>();
    assert_eq!(&[".", "..", "foo", "barfoo"], entries.as_slice());

Looks nice!
A few thoughts and questions:

Will a PathBuf API be provided as well? Wouldn't necessarily need to be in the initial PR.
I think maybe instead of a new crate, we could put this as a module in the main uefi crate, e.g. uefi::fs. My reasoning is basically that unless the new code runs against one of a few specific cases I'll list below, it's easier on the end user to keep it in the main crate. This is relevant to those other tickets about features vs crates as well, and I intend to write up some more thoughts eventually. But briefly, the reasons I can think of to put it in a separate crate are:

If the new code increases the compile-time of the crate significantly then putting it in a separate crate makes sense. I don't think that's an issue here; compilation-time increases are often related to pulling in more dependencies, but the only new dep here is derive_more, which pulls in quote/syn/proc_macro2, all of which we already depend on because of uefi-macros. And the new code is not so large that it should meaningfully affect compilation times.
If the new code needs to be separated by a feature flag. Putting it in a separate crate can be a reasonable alternative to crate features, but in this case I think we can either gate the whole thing behind alloc, or maybe do it more fine-grained and just gate particular functions and types behind alloc. But it's not like, depending on new unstable features or anything.
If the new code would negatively affect the API of the uefi crate. I don't think there's any issue with that here, it could all be neatly contained in uefi::fs.

Just a suggestion for examples and tests with paths containing backslashes, you can use r"a\b\c" as a slightly cleaner alternative to "a\\b\\c".

Will a PathBuf API be provided as well? Wouldn't necessarily need to be in the initial PR.

So far, the API a user sees is just a &str. Internally, it is transformed to a normalized CString16. I do not have a Path/PathBuf implementation yet (that is meant to be public). I think in the long term, each method should consume fn foo<P: Into<&cstr16>(&self, path: P) or so, but I'm not sure about the interface. I think, it is most important that &str is accepted as path.

I think maybe instead of a new crate, we could put this as a module in the main uefi crate, e.g. uefi::fs. My reasoning is basically that unless the new code runs against one of a few specific cases I'll list below, it's easier on the end user to keep it in the main crate. This is relevant to those other tickets about features vs crates as well, and I intend to write up some more thoughts eventually. But briefly, the reasons I can think of to put it in a separate crate are:

If the new code increases the compile-time of the crate significantly then putting it in a separate crate makes sense. I don't think that's an issue here; compilation-time increases are often related to pulling in more dependencies, but the only new dep here is derive_more, which pulls in quote/syn/proc_macro2, all of which we already depend on because of uefi-macros. And the new code is not so large that it should meaningfully affect compilation times.
If the new code needs to be separated by a feature flag. Putting it in a separate crate can be a reasonable alternative to crate features, but in this case I think we can either gate the whole thing behind alloc, or maybe do it more fine-grained and just gate particular functions and types behind alloc. But it's not like, depending on new unstable features or anything.
If the new code would negatively affect the API of the uefi crate. I don't think there's any issue with that here, it could all be neatly contained in uefi::fs.

I thought about it, and it doesn't massively increase compilation times nor requires it a feature flag. It will be just part of the normal API.

Just a suggestion for examples and tests with paths containing backslashes, you can use r"a\b\c" as a slightly cleaner alternative to "a\\b\\c".

Ah, I didn't know that, thanks.

Ping @nicholasbishop ? :)

I'm in favor of merging this once the tests are passing and the one todo!() is fixed. We can handle cleanups/additional tests in follow up PRs.

I'm in favor of merging this once the tests are passing and the one todo!() is fixed. We can handle cleanups/additional tests in follow up PRs.

I've created a tracking issue: #747


Feature: Add Slider for "Expand Mask" Iteration Count

Brief
This PR adds a simple slider below the Expand Mask button which allows the user to specify the number of iterations to use for the mask expansion operation.
Motivation for Change
Often times, dilating the mask region a single time is not enough to really impact the result in inpainting/cleaning. I often found myself having to spam the Expand Mask button which was slow since every time you press the button you have to wait for the image to reload before you can press again. This PR aims to make everyone's life a bit easier by just allowing them to set the number of iterations (dilation steps) for the Expand Mask operation.
Additional Changes

Increased the limit to the number of iterations within inpaint_anything.py::expand_mask(). Previously, the range was set to values of 1-5 however this seemed needlessly small so I upped the limit to 100 to reflect the max value of the slider.

Tests

[x] Tested various values for the iteration count slider.
[x] Compared manually expanding mask 1 at a time for 15 iterations and expanding mask using an iteration count of 15. Both gave same result.

Thanks for your contribution. I believe this is a valuable feature, as it fits well within the available space in the UI. I'll merge this pull request.


isoseq groupdedup for variant analysis

I want to do variant calling on .bam files from Hifi data, using deepvariant. When I put .bam files that have followed the isoseq workflow to the refine step (.corrected.bam) deepvariant works, but the .bam made by groupdedup seems to remove the quality scores and wont run through deepvariant. Is groupdedup only used for isoform detection?

Yes

Hi! I have the same problem. I am wondering if you managed to restore the quality scores for running DeepVariant? Thanks in advance!

The tool output was not meant to be piped into DeepVariant.


Fix all but one Python 3 test

saver_test is still broken.

Can one of the admins verify this patch?

This PR contains a lot edits in the same spots as https://github.com/tensorflow/tensorflow/pull/1034 We can look and decide which PR to merge.

It's much better to open the file correctly as binary or not than to decode manually, so this PR seems better.

@girving I agree that this PR is better with one exception: In scatter_ops_test.py, use
from six.moves import xrange
so that we can get both 2-3 compatibility and the performance of xrange.

I'm closing https://github.com/tensorflow/tensorflow/pull/1034 in favor of this one.

The performance difference is negligible for small loops and this is just a test, so I went for simplicity.

Jenkins, test this please.

merged.


Submit button disabled when no validations are included

If you do not include validations, and there is no Ember-Validations included, the submit button will be disabled

Closing in favor of #229


Return duplicate rules

given input: ['ll', 'l', 'u'] to $DupRules->duprule
then
expected return
['l', 'u'], [['ll', 'l']]: first ref is for uniq rules, second one is for duplicate rules.
actuall
only uniq rules are returened.

closed in #16


Works on localhost but not deployed

Thank you so much for this amazing project.
Is there a special configuration to ensure it works on the server? It's deployed on the .now.sh.
This is my current configuration
cookie: {
path: "/",
maxAge: 60602414*1000
}
Thanks.

Are you using the default MemoryStore? It does not work in serverless environment. Try using stores like redis-connect or mongo-connect should do.

Oh, I didn't know it doesn't work in a serverless environment. Thanks for the suggestion, I'll check it out.

Thank you for pointing it out though. I will update the docs with this info. Let me know if it works

Any advice on how to do this in a serverless environment? Are there stores that do work in a serverless environment, since I assume redis/mongo require a server?

Can confirm, have just tried deploying to vercel by using ioredis. Works perfectly :)

@lonelydatum Close since it should be solved using an external session store. Also make sure that maxAge is in second (you do not want that *1000)


Error when compiling, possible typo?

I am coming across this issue recently when building for web:
Target dart2js failed: Exception: ../../programs/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_form_builder-4.0.0-pre.4/lib/src/fields/form_builder_searchable_dropdown.dart:181:17:
Error: No named parameter with the name 'autoValidate'.
                autoValidate: autoFocusSearchBox,
                ^^^^^^^^^^^^
../../programs/flutter/.pub-cache/hosted/pub.dartlang.org/dropdown_search-0.4.5/lib/dropdown_search.dart:144:3:
Info: Found this candidate, but the arguments don't match.
  DropdownSearch({
  ^^^^^^^^^^^^^^
Error: Compilation failed.

This is the line, it gets the same value as the one above? Is it supposed to be like this? @danvick
https://github.com/danvick/flutter_form_builder/blob/b101c7c07529015c4ef1a544accae3f0ce992516/lib/src/fields/form_builder_searchable_dropdown.dart#L181

Noted. Thanks for the keen eye @nstrelow

Thanks for the quick fix @danvick
This still fails sadly:
Target dart2js failed: Exception: ../../../AppData/Local/Pub/Cache/git/flutter_form_builder-313581cb78e63cd5334f75e05f7418bfb03783ce/lib/src/fields/form_builder_searchable_dropdown.dart:181:17:
Error: No named parameter with the name 'autoValidate'.
                autoValidate: autovalidateMode == AutovalidateMode.always,
                ^^^^^^^^^^^^
../../../AppData/Local/Pub/Cache/hosted/pub.dartlang.org/dropdown_search-0.4.5/lib/dropdown_search.dart:144:3:
Info: Found this candidate, but the arguments don't match.
  DropdownSearch({
  ^^^^^^^^^^^^^^
Error: Compilation failed.

The DropdownSearch package seems to also have replaced autoValidate by autoValidateMode.
Will make a PR.

In general, autovalidate has been deprecated in favor of autovalidateMode.  Start changing your code now.


Android Basics: Shared ViewModel

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-shared-viewmodel?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-3-pathway-4%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-shared-viewmodel#7
In which task and step of the codelab can this issue be found?
Task 8 Step 4
Describe the problem
When testing the app, the same day pickup charge is being applied on the "Choose Flavor" screen. This is due to resetOrder() being called in the init block setting the _date value to dateOptions[0] which is always today. The code needs to either exclude _date in resetOrder() and check the first radio button automatically only when going into the "Choose Pickup Date" screen or the updatePrice() will need to be updated with a flag to differentiate whether setQuantity() or setDate() called updatePrice().
For example if setDate() calls updatePrice() and passes in a flag value of TRUE then that flag can be added to the IF condition to apply the same day pickup charge.
Steps to reproduce?

Run the App from the solution code in Task 10
Click any of the buttons on the Cupcake screen
You will see the subtotal automatically applies the $3 fee for same day pickup before a date was selected.

Versions
_Android Studio version: Android Studio Arctic Fox | 2020.3.1 Patch 3
_API version of the emulator: 30
Additional information
Include screenshots if they would be useful in clarifying the problem.

Same issue here

@DFilkins919


Dropping awesome font characters?

I've only recently started playing around with i3 and polybar. Haven't done much except copy pasted on guy's config. Was pretty happy with it but I kind of want to add icons to workspaces.
`###################################
#    Polybar Configuration File   #
###################################

; Define Color Variables - Mine still need a little work,
; but are based on base16-default-dark/testing
[colors]
background = #1b1818
background-alt = #369
foreground = #ffffff
foreground-alt = #ca4949
primary = #ffffff
secondary = #ffffff
alert = #ca4949
focused-bg = #369
focused-fg = #2b1818

###################################
#         Define Left Bar         #
###################################

; You can set up multiple bars for multiple monitors,
; if you are setting up polybar on a laptop you only need
; to set up one. You can also name it anything, eg: 'bar/foo'
; You just need to coordinate it in the launch.sh file

[bar/left]
font-3 = "Font Awesome 4 Free:size=10;3"
font-4 = "Font Awesome 4 Free:style=Solid:size=8;1"
font-5 = "Font Awesome 4 Brands:size=8;1"
fc-match FontAwesome:pixelsize=14
FontAwesome.otf: "FontAwesome" "Regular"
; Set bar/left to my left monitor
;monitor = ${env:MONITOR:eDP-1-1}
; Set the width, height of bar/left
width = 100%
height = 25
strip-wsnumbers = true
; Potentially curve the bar
radius = 0
; This controls the behavior of the center module... I think...
fixed-center = true
; Set the bar colors
background = ${colors.background}
foreground = ${colors.foreground}

; This has to do with the behavior of floating windows
; going above/below the bar, I think. This works for me.
override-redirect = false
wm-restack = i3

; Haven't seen these offsets make a difference
;offset-x = 8
;offset-y = 8

; Here are some pretty self-explanatory customization options:

line-size = 2
;line-color = #fff

border-size = 0
border-color = #ffffff

padding-left = 0
padding-right = 3

module-margin-left = 1
module-margin-right = 2

font-0 = fixed:pixelsize=8;1
font-1 = unifont:fontformat=truetype:size=8:antialias=false;0
font-2 = inconsolata:pixelsize=8;1

; This is where you put the modules where you want them. Then you
; customize the modules below in the modules section.

modules-left = i3
modules-center = date

tray-position = right
tray-padding = 0
;tray-transparent = false
;tray-background = #369
;wm-restack = bspwm
;wm-restack = i3

;override-redirect = true

;scroll-up = bspwm-desknext
;scroll-down = bspwm-deskprev

scroll-up = i3wm-wsnext
scroll-down = i3wm-wsprev

cursor-click = pointer
;cursor-scroll = ns-resize

###################################
#         Define Modules         #
###################################

; These modules are the content of the bar. ;I've removed a bunch, so check out
; the example configuration file if you want something less minimal.

[module/xwindow]
type = internal/xwindow
label = %title:0:30:...%

; This i3 module is what sets the workspaces. For some reason, I can get foreground
; and border to change, but not bg, really. All my weird tweaking and padding DID get
; me exactly what I wanted, even though this isn't really clean or perfect.

[module/i3]
type = internal/i3
format = <label-state> <label-mode>
wrapping-scroll = false
ws-icon-1 = 1;
ws-icon-2 = 2;
ws-icon-3 = 3;
label-focused =%index% %icon%
label-unfocused = %index%  %icon%
label-urgent = %index%  %icon%
label-visible = %index% : %icon%
; Only show workspaces on the same output as the bar
pin-workspaces = true

label-mode-padding = 2

; focused = Active workspace on focused monitor
;label-focused = %index%
label-focused-underline = #ffffff
label-focused-background = #369
label-focused-padding = 4
index-sort = true
; unfocused = Inactive workspace on any monitor
;label-unfocused = %index%
label-unfocused-padding = 4
label-active-font = 3

; visible = Active workspace on unfocused monitor
;label-visible = %index%
;label-visible-padding = 4

; urgent = Workspace with urgency hint set
;label-urgent = %index%
label-urgent-padding = 4

[module/eth]
type = internal/network
interface = wlp7s0
interval = 3.0

;format-connected-prefix = " "
format-connected-prefix-foreground = ${colors.foreground}
label-connected = %local_ip%

format-disconnected =
;format-connected-underline = ${colors.foreground}
;format-disconnected = <label-disconnected>
;format-disconnected-underline = ${self.format-connected-underline}
;label-disconnected = %ifname% disconnected
;label-disconnected-foreground = ${colors.foreground-alt}

; I tweaked the date module a good bit to get the date/clock how I wanted
; you can do a lot to tweak this. It's pretty cool.

[module/date]
type = internal/date
interval = 5

date = "%h %d %Y "
date-alt = "%Y-%m-%d"

time = %H:%M
time-alt = %H:%M:%S

;format-prefix = 
format-prefix-foreground = ${colors.foreground-alt}
format-underline = ${colors.foreground}

label = %date% %time%

; By default, Polybar gives you this crazy volume bar. I didn't like it.
; I just wanted a 'Vol: 90%' indicator, so I removed a bunch of stuff from
; here.

[module/volume]
type = internal/volume

format-volume = <label-volume>
label-volume = Vol %percentage%%
label-volume-foreground = ${root.foreground}
;label-volume-underline = ${root.foreground}

;format-muted-prefix = " "
format-muted-foreground = ${colors.alert}
label-muted = Vol Muted
label-muted-underline = ${colors.alert}

[settings]
screenchange-reload = true
compositing-background = xor
compositing-foreground = source
;compositing-background = screen
;compositing-border = over

[global/wm]
margin-top = 5
margin-bottom = 5

; vim:ft=dosini
`

I've installed awesome font from the Solus software centre:
fc-list| grep awesome                              ✔  648  15:58:33
/usr/share/fonts/truetype/fontawesome/fa-regular-400.ttf: Font Awesome 5 Free:style=Regular
/usr/share/fonts/truetype/fontawesome/fa-brands-400.ttf: Font Awesome 5 Brands:style=Regular
/usr/share/fonts/truetype/fontawesome-4/fontawesome-4.ttf: FontAwesome:style=Regular
/usr/share/fonts/truetype/fontawesome/fa-solid-900.ttf: Font Awesome 5 Free:style=Solid
/usr/share/fonts/opentype/fontawesome-4/FontAwesome.otf: FontAwesome:style=Regular

I've scoured this site, changed pixelsize to just size, changed up a bunch of things but nothing worked. Any ideas? I've copied the glyphs from fontawesome website.
Maybe I should add that there is no warning messages. It just doesn't show up and when I add the same glyph somewhere else this pops up:

Please read the Font wiki page, everything you need to troubleshoot should be there.
I see you have specified Font Awesome 4 ... in your config instead of Font Awesome 5.


Gg surge Add Fluidigm C1 to SmartSeq2

Purpose

No issue is linked to this PR.

Changes
Adding support for Fluidigm C1 platform scRNA-seq experiments to SmartSeq2 pipeline
Review Instructions

No instructions.

@kbergin @kishorikonwar did we get SmartSeq working with Fluidigm data?

This must have been merged in in another PR, because we do have this support.


Something broken on Caroline (skylake)

Describe the bug
Some audio devices, namely speakers and one other I'm not sure what is used for, seem to be inaccessible and create a weird situation in which it is not even created a dummy output and every software trying for audio simply crashes.
I don't know if this issue is relatively new because I only just updated from a working configuration from several months ago, since some big changes in in the driver broke my config and I just reverted to a previous linux version for the time being since I had no time to debug that and I needed audio. Still have very little time but I think this might need to be addressed before too much time passes.
Boardname
Caroline (skylake)
Logs
Multiple things hang when trying to access some sound cards, including pipewire, external software requiring sound access and alsa tools used by your script to get logs. Trying to make the script to work properly, given the hangs and segfaults and my lack of familiarity with audio devices inner workings, proved to be a waste of time. I can provide specific logs if needed.
I'm on archlinux and I downgraded alsa-ucm-conf to 1.2.12 prior to debugging to prevent new syntax issues and avoid possible errors in new ucm configurations, since I read about it in #185.
Also, the driver module snd_soc_avs throws a bad error at loading time, I'll include the kernel call trace though probably useless:
[   22.447051] #PF: supervisor read access in kernel mode
[   22.447055] #PF: error_code(0x0000) - not-present page
[   22.447058] PGD 0 P4D 0
[   22.447062] Oops: Oops: 0000 [#1] PREEMPT SMP PTI
[   22.447067] CPU: 1 UID: 1000 PID: 951 Comm: wireplumber Tainted: G         C         6.12.1-arch1-1 #1 33f4a68ee85c59cb5d6edb747af0349869779b24
[   22.447074] Tainted: [C]=CRAP
[   22.447077] Hardware name: Google Caroline/Caroline, BIOS SeppiaTech 02/20/2018
[   22.447081] RIP: 0010:avs_dai_fe_hw_params+0x1f/0x100 [snd_soc_avs]
[   22.447111] Code: 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 55 49 89 f1 41 54 55 53 48 63 47 3c 48 8d 04 40 4c 8b 6c c2 30 <49> 8b 75 08 48 85 f6 74 0f 31 ed 5b 89 e8 5d 41 5c 41 5d c3 cc cc
[   22.447115] RSP: 0018:ffffb41e0f4e3890 EFLAGS: 00010286
[   22.447119] RAX:<PHONE_NUMBER>000003 RBX: ffff970d8ccb1028 RCX:<PHONE_NUMBER>000000
[   22.447122] RDX: ffff970d8ccb1028 RSI: ffffb41e0f4e38f0 RDI: ffff970d8449d000
[   22.447125] RBP: ffff970d8449d000 R08: ffff970d8449d228 R09: ffffb41e0f4e38f0
[   22.447128] R10:<PHONE_NUMBER>000000 R11: ffff970da798afb8 R12: ffff970da744b828
[   22.447130] R13:<PHONE_NUMBER>000000 R14:<PHONE_NUMBER>000000 R15: ffff970db0321800
[   22.447133] FS:<PHONE_NUMBER>a91400(0000) GS:ffff970dfbc80000(0000) knlGS:0000000000000000
[   22.447137] CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
[   22.447140] CR2:<PHONE_NUMBER>000008 CR3: 000000012ea80002 CR4:<PHONE_NUMBER>3726f0
[   22.447143] Call Trace:
[   22.447147]  <TASK>
[   22.447150]  ? __die_body.cold+0x19/0x27
[   22.447157]  ? page_fault_oops+0x15a/0x2d0
[   22.447166]  ? exc_page_fault+0x81/0x190
[   22.447172]  ? asm_exc_page_fault+0x26/0x30
[   22.447181]  ? avs_dai_fe_hw_params+0x1f/0x100 [snd_soc_avs 6a3d03215b20085d7cf889e3cd6a64426f6dfd08]
[   22.447200]  snd_soc_dai_hw_params+0x39/0x80 [snd_soc_core 2ed91f7b7ecc741332d7b8494a2e0d5b0c029be8]
[   22.447258]  __soc_pcm_hw_params+0x547/0x680 [snd_soc_core 2ed91f7b7ecc741332d7b8494a2e0d5b0c029be8]
[   22.447306]  dpcm_fe_dai_hw_params+0xde/0x2a0 [snd_soc_core 2ed91f7b7ecc741332d7b8494a2e0d5b0c029be8]
[   22.447340]  snd_pcm_hw_params+0x2e1/0x6f0 [snd_pcm 9b700b3a2034e224048acc8b817daa4ae522e7f5]
[   22.447360]  snd_pcm_common_ioctl+0xaf1/0x13a0 [snd_pcm 9b700b3a2034e224048acc8b817daa4ae522e7f5]
[   22.447374]  ? __seccomp_filter+0x303/0x520
[   22.447383]  snd_pcm_ioctl+0x2b/0x40 [snd_pcm 9b700b3a2034e224048acc8b817daa4ae522e7f5]
[   22.447402]  __x64_sys_ioctl+0x91/0xd0
[   22.447411]  do_syscall_64+0x82/0x190
[   22.447422]  ? syscall_exit_to_user_mode+0x37/0x1c0
[   22.447431]  ? do_syscall_64+0x8e/0x190
[   22.447437]  ? __seccomp_filter+0x303/0x520
[   22.447447]  ? syscall_exit_to_user_mode+0x37/0x1c0
[   22.447453]  ? do_syscall_64+0x8e/0x190
[   22.447457]  ? do_syscall_64+0x8e/0x190
[   22.447463]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[   22.447468] RIP: 0033:0x734726ecbced
[   22.447498] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
[   22.447502] RSP: 002b:00007fff740d4370 EFLAGS: 00000246 ORIG_RAX:<PHONE_NUMBER>000010
[   22.447507] RAX: ffffffffffffffda RBX: 00007fff740d44e0 RCX:<PHONE_NUMBER>ecbced
[   22.447510] RDX: 00007fff740d44e0 RSI: 00000000c2604111 RDI:<PHONE_NUMBER>00001a
[   22.447512] RBP: 00007fff740d43c0 R08:<PHONE_NUMBER>000000 R09:<PHONE_NUMBER>000000
[   22.447515] R10:<PHONE_NUMBER>000004 R11:<PHONE_NUMBER>000246 R12: 00006244b5ad9910
[   22.447518] R13: 00006244b5add540 R14: 00007fff740d4af0 R15: 00007fff740d44e0
[   22.447526]  </TASK>
[   22.447529] Modules linked in: xt_hl ip6t_rt ip6table_filter ip6table_nat ip6_tables xt_TCPMSS iptable_mangle xt_comment xt_addrtype xt_tcpudp xt_conntrack xt_LOG nf_log_syslog xt_limit iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c cros_ec_sensors cros_ec_sensors_core industrialio_triggered_buffer kfifo_buf industrialio snd_soc_avs_hdaudio intel_pmc_core_pltdrv snd_soc_dmic snd_soc_avs_nau8825 snd_soc_avs_ssm4567 snd_soc_avs_dmic snd_soc_avs_probe intel_pmc_core intel_vsec leds_cros_ec pmt_telemetry led_class_multicolor pmt_class cros_ec_sysfs joydev cros_usbpd_charger cros_charge_control cros_ec_sensorhub gpio_cros_ec intel_tcc_cooling mousedev cros_ec_chardev cros_ec_hwmon cros_ec_debugfs cros_usbpd_logger iwlmvm iTCO_wdt intel_pmc_bxt x86_pkg_temp_thermal iTCO_vendor_support hid_generic snd_hda_codec_hdmi intel_powerclamp mac80211 snd_soc_avs 8250_dw snd_soc_hda_codec coretemp snd_hda_ext_core intel_rapl_msr libarc4 snd_hda_intel ptp pps_core cros_ec_dev kvm_intel btusb
[   22.447646]  memconsole_coreboot btrtl snd_intel_dspcfg cbmem framebuffer_coreboot memconsole btintel chromeos_laptop snd_intel_sdw_acpi iwlwifi btbcm kvm snd_hda_codec processor_thermal_device_pci_legacy btmtk ipu3_imgu(C) i2c_i801 processor_thermal_device snd_soc_nau8825 uvcvideo atmel_mxt_ts spi_nor nls_iso8859_1 snd_soc_ssm4567 processor_thermal_wt_hint rapl snd_hda_core intel_cstate vfat i2c_smbus fat intel_uncore mtd pcspkr uvc bluetooth cfg80211 snd_soc_core i2c_mux snd_hwdep videobuf2_dma_sg videobuf2_vmalloc processor_thermal_rfim snd_compress videobuf2_memops processor_thermal_rapl rfkill videobuf2_v4l2 ac97_bus intel_rapl_common intel_lpss_pci intel_xhci_usb_role_switch snd_pcm_dmaengine videobuf2_common processor_thermal_wt_req intel_lpss snd_pcm processor_thermal_power_floor idma64 roles intel_pch_thermal processor_thermal_mbox videodev snd_timer intel_soc_dts_iosf int3403_thermal i2c_hid_acpi snd mc soundcore int340x_thermal_zone i2c_hid cros_ec_lpcs cros_usbpd_notify cros_ec coreboot_table
[   22.447772]  int3400_thermal pinctrl_sunrisepoint acpi_thermal_rel mac_hid zram 842_decompress 842_compress lz4hc_compress lz4_compress sg crypto_user loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 dm_crypt mmc_block rpmb_core cbc encrypted_keys trusted asn1_encoder tee dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 sha256_ssse3 serio_raw sha1_ssse3 atkbd aesni_intel libps2 vivaldi_fmap gf128mul sdhci_pci crypto_simd cqhci cryptd sdhci spi_intel_pci mmc_core spi_intel gpio_keys i8042 serio i915 i2c_algo_bit drm_buddy video wmi ttm intel_gtt drm_display_helper cec
[   22.447873] CR2:<PHONE_NUMBER>000008
[   22.447878] ---[ end trace<PHONE_NUMBER>000000 ]---
[   22.447882] RIP: 0010:avs_dai_fe_hw_params+0x1f/0x100 [snd_soc_avs]
[   22.447914] Code: 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 55 49 89 f1 41 54 55 53 48 63 47 3c 48 8d 04 40 4c 8b 6c c2 30 <49> 8b 75 08 48 85 f6 74 0f 31 ed 5b 89 e8 5d 41 5c 41 5d c3 cc cc
[   22.447919] RSP: 0018:ffffb41e0f4e3890 EFLAGS: 00010286
[   22.447925] RAX:<PHONE_NUMBER>000003 RBX: ffff970d8ccb1028 RCX:<PHONE_NUMBER>000000
[   22.447928] RDX: ffff970d8ccb1028 RSI: ffffb41e0f4e38f0 RDI: ffff970d8449d000
[   22.447932] RBP: ffff970d8449d000 R08: ffff970d8449d228 R09: ffffb41e0f4e38f0
[   22.447936] R10:<PHONE_NUMBER>000000 R11: ffff970da798afb8 R12: ffff970da744b828
[   22.447940] R13:<PHONE_NUMBER>000000 R14:<PHONE_NUMBER>000000 R15: ffff970db0321800
[   22.447944] FS:<PHONE_NUMBER>a91400(0000) GS:ffff970dfbc80000(0000) knlGS:0000000000000000
[   22.447949] CS:  0010 DS: 0000 ES: 0000 CR0:<PHONE_NUMBER>050033
[   22.447953] CR2:<PHONE_NUMBER>000008 CR3: 000000012ea80002 CR4:<PHONE_NUMBER>3726f0
[   22.447957] note: wireplumber[951] exited with irqs disabled

These might also be indicative of the problem:
[   13.594579] avs_nau8825 avs_nau8825.2: ASoC: Parent card not yet available, widget card binding deferred
[   13.609260] Bluetooth: hci0: Intel BT fw patch 0x43 completed & activated
[   13.613635] input: avs_nau8825 Headset Jack as /devices/platform/avs_nau8825.2/sound/card1/input17
[   13.622600] avs_ssm4567 avs_ssm4567.1: ASoC: Parent card not yet available, widget card binding deferred
[   13.653980] iwlwifi 0000:01:00.0 wlp1s0: renamed from wlan0
[   13.659202] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 0 0
[   13.659213] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 0
[   13.659217] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 1 1
[   13.659221] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 1
[   13.659224] snd_hda_codec_hdmi hdaudioB0D2: creating for HDMI 2 2
[   13.659228] snd_hda_codec_hdmi hdaudioB0D2: skipping capture dai for HDMI 2
[   13.660102] avs_hdaudio avs_hdaudio.2: ASoC: Parent card not yet available, widget card binding deferred
[   13.660234] avs_hdaudio avs_hdaudio.2: avs_card_late_probe: mapping HDMI converter 1 to PCM 1 (00000000c3d737ff)
[   13.660241] avs_hdaudio avs_hdaudio.2: avs_card_late_probe: mapping HDMI converter 2 to PCM 2 (00000000f7c3085c)
[   13.660246] avs_hdaudio avs_hdaudio.2: avs_card_late_probe: mapping HDMI converter 3 to PCM 3 (00000000d979681d)
[   13.669987] input: hdaudioB0D2 HDMI/DP,pcm=1 as /devices/platform/avs_hdaudio.2/sound/card3/input18
[   13.680540] input: hdaudioB0D2 HDMI/DP,pcm=2 as /devices/platform/avs_hdaudio.2/sound/card3/input19
[   13.680880] input: hdaudioB0D2 HDMI/DP,pcm=3 as /devices/platform/avs_hdaudio.2/sound/card3/input20
[   13.686661] avs_dmic avs_dmic: ASoC: Parent card not yet available, widget card binding deferred

ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:2 use case configuration -2
  0: hw:1
    Google-Caroline-1.0
  1: hw:3
    Google-Caroline-1.0
  2: hw:4
    Google-Caroline-1.0

 0 [avsprobemb     ]: avs_probe_mb - avs_probe_mb
                      Google-Caroline-1.0
 1 [avsnau8825     ]: avs_nau8825 - avs_nau8825
                      Google-Caroline-1.0
 2 [avsssm4567     ]: avs_ssm4567 - avs_ssm4567
                      Google-Caroline-1.0
 3 [hdaudioB0D2    ]: hdaudioB0D2 - hdaudioB0D2
                      Google-Caroline-1.0
 4 [avsdmic        ]: avs_dmic - avs_dmic
                      Google-Caroline-1.0

card 1: avsnau8825 [avs_nau8825], device 1: Headset (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: avsssm4567 [avs_ssm4567], device 1: Built-in Speakers (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: hdaudioB0D2 [hdaudioB0D2], device 1: HDMI1 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: hdaudioB0D2 [hdaudioB0D2], device 2: HDMI2 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 3: hdaudioB0D2 [hdaudioB0D2], device 3: HDMI3 (*) []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

FWIW I have the same issue on an Asus C302:
Hardware name: Google Cave/Cave, BIOS MrChromebox-2405.0 06/15/2024
Running Arch, all working yesterday, I ran a "yay -Syu" and now sound is broken with similar symptoms (and dmesg) as above. Rerunning scripts didn't change anything.
Please let me know if there is any more info, logs or troubleshooting I can provide to help.

@djfergus that's skylake as well. Do you happen to know which linux version you upgraded from yesterday? Could you try to revert back just the kernel to that last working version?
Note that you should downgrade alsa-ucm-conf anyway to 1.2.12 since 1.2.13 needs new syntax for ucm confs and won't work otherwise even on previously working kernels.
I checked various kernel versions and all present issues from 6.9 onward. The last version on which audio works is 6.8. From there on seems to get progressively worse, up to 6.12 which is completely broken, so it seems that after this even more important changes were made.
Anyway even on 6.8 there are some issues since not all cards are detected but at least speakers do work:
ALSA lib main.c:1554:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
  0: hw:1
    Google-Caroline-1.0
  1: hw:2
    Google-Caroline-1.0
  2: hw:3
    Google-Caroline-1.0
  3: hw:4
    Google-Caroline-1.0

But at least this seems mostly a missing firmware issue
[   23.162696] snd_soc_avs 0000:00:1f.3: no DMIC ep_blob found
[   23.162702] snd_soc_avs 0000:00:1f.3: module-type create failed: -2
[   23.162705] snd_soc_avs 0000:00:1f.3: error creating module -2
[   23.162759] snd_soc_avs 0000:00:1f.3: create path failed: -2
[   23.162762] snd_soc_avs 0000:00:1f.3: ASoC: error at snd_soc_dai_hw_params on DMIC Pin: -2
[   23.162768]  DMIC: ASoC: error at __soc_pcm_hw_params on DMIC: -2
[   23.162771]  Digital Microphone: ASoC: error at dpcm_fe_dai_hw_params on Digital Microphone: -2

I took the time to remove all ucm modifications, configurations for linux audio modules, userspace software configurations for alsa, pipewire and wireplumber and firmware additions on my system that accumulated during the years to start from scratch.
I manually reinstalled ucm2 configurations provided in this repo with updated syntax version 7, modules options and wireplumber conf provided in this repository, all according to the setup-audio script. No need to install any firmware on archlinux since all the needed ones for my board are already packaged in linux-firmware.
The mic that wasn't working lately now works. There was probably some configuration that got messed up during upgrades.
So, using linux 6.8.9 speakers and mic work like used to previously and I confirm that updated configurations provided here do in fact work (syntax 7 actually seems to be mostly ignored by alsa since it even worked before updating it) on Skylake Caroline (with system provided and packaged firmware blobs that match the ones provided here).
Everything falls apart when I try to upgrade the kernel as I described in the previous comments.
On linux 6.9.x and 6.10.x I get the dummy output with various errors and on 6.12.x I got the broken module errors from the previous comments and the system actually hangs when trying to use audio.
I reverted this change and rebuilt linux 6.9.1 and I confirm I got audio working again there.
I didn't try to revert even further changes in subsequent versions of linux.
So, as far as I can tell, the issue seems to be in the kernel driver, that from 6.9 got progressively broken, at least on skylake boards.
I don't know if this is due to misconfigurations of kernel modules or userspace tools, or if it needs to be addressed in the updated driver.


Leaf Nodes in BST Doc

Fixes #296

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Documentation for Leaf Nodes in BST
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#296

@siddharth25pandey , @HarshCasper  kindly review the PR


By typing in .../edit/... into a deck url- one can edit someone else's submitted deck - Urgent

By typing in .../edit/... into a deck url- one can edit someone else's submitted deck

looks terrible, and it is, but it's not as bad as it seems - you can't save deck changes or delete the deck if you're not the owner of it.


Dependency failure for Building Hygieia Publisher Plugin 1.3-SNAPSHOT

Off of a fresh clone of Hygieia, we're seeing problems building the jenkins plugin. Here's our stack trace after mvn clean package:
> mvn clean package
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jenkins-ci.plugins:hygieia-publisher:hpi:1.3-SNAPSHOT
[WARNING] 'parent.relativePath' of POM org.jenkins-ci.plugins:hygieia-publisher:1.3-SNAPSHOT (/Users/ujc428/Hygieia/hygieia-jenkins-plugin/pom.xml) points at com.capitalone.dashboard:Hygieia instead of org.jenkins-ci.plugins:plugin, please verify your project structure @ line 15, column 13
[WARNING] 'build.plugins.plugin.version' for org.jacoco:jacoco-maven-plugin is missing. @ line 166, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Hygieia Publisher Plugin 1.3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
....
[INFO] Final Memory: 24M/439M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project hygieia-publisher: Could not resolve dependencies for project org.jenkins-ci.plugins:hygieia-publisher:hpi:1.3-SNAPSHOT: Could not find artifact com.-removed-.dashboard:core:jar:2.0.2-SNAPSHOT in anonymous (https://nexus.kdc.-removed-.com/nexus/content/groups/CLM) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Clone Hygieia root. mvn clean install and then build the plugin. We have not released core 2.0.2 yet. We will most probably move this plugin to jenkins plugin repo.

Received this error after running mvn clean install in core:
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.2-SNA
PSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-
parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/maven2):
 Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] fai
led: Connection timed out: connect and 'parent.relativePath' points at wrong loc
al POM @ com.capitalone.dashboard:Hygieia:2.0.2-SNAPSHOT, C:\Users\Gur648\Hygiei
a\pom.xml, line 10, column 10
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.capitalone.dashboard:core:[unknown-version] (C:\Users\
Gur648\Hygieia\core\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.2
-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-star
ter-parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/mave
n2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>]
 failed: Connection timed out: connect and 'parent.relativePath' points at wrong
 local POM @ com.capitalone.dashboard:Hygieia:2.0.2-SNAPSHOT, C:\Users\Gur648\Hy
gieia\pom.xml, line 10, column 10 -> [Help 2]

Got a previously created HPI file for the jenkins plugin I needed to set up from @tabladrum

Hi I am still getting the error after re-cloning Hygieia -> mvn clean install and building hygieia jenkins plugin.
mvn clean install from /hygieia-jenkins-plugin folder
[INFO] Scanning for projects...
[WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:1.106 is missing, no dependency information available
[WARNING] Failed to build parent project for org.jenkins-ci.plugins:hygieia-publisher:hpi:1.4-SNAPSHOT
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jenkins-ci.plugins:hygieia-publisher:hpi:1.4-SNAPSHOT
[WARNING] 'parent.relativePath' of POM org.jenkins-ci.plugins:hygieia-publisher:1.4-SNAPSHOT (/home/svc-hygieia/node/mtvgserver001_sdt-ecomp-portal/workspace/Hygieia/hygieia-jenkins-plugin/pom.xml) points at com.capitalone.dashboard:Hygieia instead of org.jenkins-ci.plugins:plugin, please verify your project structure @ line 15, column 13
[WARNING] 'build.plugins.plugin.version' for org.jacoco:jacoco-maven-plugin is missing. @ line 185, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Hygieia Publisher Plugin 1.4-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom
Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.pom (5 KB at 15.1 KB/sec)
Downloading: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar
Downloaded: http://repo.jenkins-ci.org/public/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar (23 KB at 114.6 KB/sec)
Downloading: http://repo.jenkins-ci.org/public/org/jenkins-ci/main/jenkins-war/1.567/jenkins-war-1.567-war-for-test.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 02:10 min
[INFO] Finished at: 2016-09-12T17:37:26+00:00
[INFO] Final Memory: 24M/378M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project hygieia-publisher: Could not resolve dependencies for project org.jenkins-ci.plugins:hygieia-publisher:hpi:1.4-SNAPSHOT: Could not transfer artifact org.jenkins-ci.main:jenkins-war:jar:war-for-test:1.567 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): GET request of: org/jenkins-ci/main/jenkins-war/1.567/jenkins-war-1.567-war-for-test.jar from repo.jenkins-ci.org failed: Premature end of Content-Length delimited message body (expected: 68151300; received: 23435919 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Just cloned Hygieia master in STS. Receiving this error after mvn compile:
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/1.2.5.RELEASE/spring-boot-starter-parent-1.2.5.RELEASE.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: Connection timed out: connect and 'parent.relativePath' points at wrong local POM @ line 14, column 11
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT (C:\Workspace\Hygieia\Hygieia_Master\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: Connection timed out: connect and 'parent.relativePath' points at wrong local POM @ line 14, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Please help. I see that the above issue is similar to this but not finding solution for this on this page.

Cloned Hygieia master on my local machine and when I try to do mvn clean install I get the following error:
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/1.2.5.RELEASE/spring-boot-starter-p                                  arent-1.2.5.RELEASE.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT: Could not transfer artifact org.springframework.bo                                  ot:spring-boot-starter-parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Failed to transfer file: https://                                  repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/1.2.5.RELEASE/spring-boot-starter-parent-1.2.5.RELEASE.p                                  om. Return code is: 400 , ReasonPhrase:Bad Request. and 'parent.relativePath' points at wrong local POM @ line 14, column 11
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT (C:\Anshul_Saxena\Work\Experiments\Hygieia\Hygieia\pom.xml) has 1 e                                  rror
[ERROR]     Non-resolvable parent POM for com.capitalone.dashboard:Hygieia:2.0.4-SNAPSHOT: Could not transfer artifact org.springframewor                                  k.boot:spring-boot-starter-parent:pom:1.2.5.RELEASE from/to central (https://repo.maven.apache.org/maven2): Failed to transfer file: http                                  s://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/1.2.5.RELEASE/spring-boot-starter-parent-1.2.5.RELEA                                  SE.pom. Return code is: 400 , ReasonPhrase:Bad Request. and 'parent.relativePath' points at wrong local POM @ line 14, column 11 -> [Help                                   2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Does anyone know the cause of this? Tried researching for the solution but unable to find anything that says anything about this error.
Any help is highly appreciated.


Update README to include zstd workaround for windows.

This PR contains the following changes:

Move Cache segment restore timeout section to Know practices and workarounds
Add yaml formatting for actions code blocks
Add zstd workaround for windows and zstd requirement for self-hosted windows runners.

This doesn't fix it. Even in your own test, this doesn't fix it
https://github.com/pdotl/sample-cache-demo/runs/7959974880?check_suite_focus=true
The Cache Python virtualinv step on Ubuntu took 2 seconds, and on Windows it took 11 seconds.
That is more then 5 times slower on windows, even with a tiny cache.

Hi @wrexbe, I agree. This workaround is being used by customers vs using gzip which is even slower. We are simply documenting the same. We are looking into improving windows performance for cache by looking at several alternatives.


Add Azer from Dawn of Flames AP

This is my first pull request to a repo... So I am keeping this small just so I can get a feel of the process.
I have followed the contributing doc link.
Also, I tested the actor once it was done cooking and everything seemed in order.
I plan to go through and add the DoF items/NPCs if this works out.
Let me know if you see anything odd!

Looks good, merging.


Porting other models

Can we port the model of human key points? I want to analyze the behavior of the human body.

pls explain what you mean by "port the model of human key points"?

Feel free to reopen if there's follow up questions.


Minor content fixes in the Migrating from File-Based Routing section

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)

Description

a little typo (from and to to to):

missing a highlight for changes in the Migrating from File-Based Routing section:

before Content Collections (the tutorial version):

after introducing Content Collections:

my fix (highlighting the new url format):

This looks great, @ilkou! Thank you for taking the time to contribute, and welcome to Team Docs!  🥳


Fix billing metrics tests (datapoints found error) and disable checking removed prometheus rule

Sometimes, when we run a metrics query in OpenShift Monitoring, we get "no datapoints found" as a result. If we wait a few minutes and run the same query we get the result.
This PR adds retries to the "Run Query" keyword to avoid having this issue and also makes the Test Suite Teardown more reliable
This PR also fixes test ODS-510 after the rule SLOs - JupyterHub DB was removed in build 1.1.1-41

Running here right now: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/163/

Finally it seem to work well now:
https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/170/console
==============================================================================
Tests.Monitor And Manage.Metrics
==============================================================================
Tests.Monitor And Manage.Metrics.Metrics
==============================================================================
Test Existence of Prometheus Alerting Rules                           Testing Builds
Testing DeadManSnitch
Testing RHODS-PVC-Usage
Testing SLOs-haproxy_backend_http_responses_total
Testing SLOs-probe_success
| PASS |
------------------------------------------------------------------------------
Test Existence of Prometheus Recording Rules                          Testing Availability Metrics
Testing SLOs - JupyterHub
Testing SLOs - ODH Dashboard
Testing SLOs - RHODS Operator
Testing SLOs - Traefik Proxy
Testing Usage Metrics
| PASS |
------------------------------------------------------------------------------
Tests.Monitor And Manage.Metrics.Metrics                              | PASS |
2 tests, 2 passed, 0 failed
==============================================================================
Tests.Monitor And Manage.Metrics.Billing Metrics
==============================================================================
Verify OpenShift Monitoring results are correct when running undef... | PASS |
------------------------------------------------------------------------------
Test Billing Metric (notebook cpu usage) on OpenShift Monitoring      | PASS |
------------------------------------------------------------------------------
Tests.Monitor And Manage.Metrics.Billing Metrics                      | PASS |
2 tests, 2 passed, 0 failed
==============================================================================
Tests.Monitor And Manage.Metrics                                      | PASS |
4 tests, 4 passed, 0 failed
==============================================================================
Tests.Monitor And Manage                                              | PASS |
4 tests, 4 passed, 0 failed

New PR test with including new cluster creation:
https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/173/

Testing again in new cluster: https://opendatascience-jenkins-csb-rhods.apps.ocp4.prod.psi.redhat.com/job/rhods-ci-pr-test/176


Call user-defined functions on kernel entry and exit.

This change allows users to define functions that can called on kernel entry and exit. See onKernelEntry and onKernelExit in utils/utiltest/test_dictionary.cu for an example.
Modified instlibs/utils/sassi_lazyallocator.hpp and the example (instlibs/utils/utiltest/test_dictionary.cu).

Hi Siva, this pull request looks good.  Let me just make sure it doesn't break regression tests.  I like how you're passing the CUPTI callback data to the handler.  At some point I should probably do something similar for the init and reset functions.


[Bug] Export application does not export JS Collections

When exporting an application which has JS objects, the JS collections are not included but the JS actions are, making the imported application incomplete.

Fised in #7892


allow setting run mode via env, add helpers to determine it

bonus: error out if backend-only and frontend-only is set at the same time
needed here: https://github.com/reflex-dev/reflex-chakra/pull/22

needs coordination with https://github.com/reflex-dev/reflex/pull/4192


Finalizing hello world heat equation blog post

@curfman, @rinkug, and @bernhold this is ready for final review and publication

I have two comments, otherwise I like the article. First, the title confused me as I don't understand what it means. I would think a simple "Hello CSE World!" might be clearer. Second, after I read the code repository section, I starting looking for a link to the repository. Then I re-read the section about the temporary code snippets and realized that is what you have at the moment. Is that not going to be the repository? Maybe you could be a bit clearer about what you have now and what your plans are for the future?

Was trying to be cute with the title. You'd have to be a Rene Zellweger fan to catch the reference. Its from the movie Jerry Maguire where she says "You had me at hello." 😃. I don't need to be that cute though. On the other hand, so much of our content is a little on the dry side.
Regarding confusion over repository plans and what is available now. I will try a re-wording.

Sorry to be a spoilsport. :-/ I like Rene, but I haven't seen that movie.

Thanks, we'll move ahead with copy edits and image treatment.


Correction for raw affiliation Montpellier SupAgro, UMR AGAP, Montpellier, cedex 5 - France

Correction needed for raw affiliation Montpellier SupAgro, UMR AGAP, Montpellier, cedex 5 - France
raw_affiliation_name: Montpellier SupAgro, UMR AGAP, Montpellier, cedex 5 - France
new_rors: 03rnk6m14;02w4exq36
previous_rors: 03rnk6m14
works_examples: W2004758577
contact: 0c11223a34029a9a960f3be43264d853:3e21cb8c63bc0480e54e80bf550015588c7e @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


STL Loader doesn't provide error feedback when parsing invalid data

Using Babylon.js 2.5
I accidentally tried to load a binary STL file (not realizing that wasn't supported).
The STL loader should detect this and throw an error for the developer (even if it's just a general 'STL format not recognized, ensure it's ASCII formatted.').
Similarly, other invalid parsings (like bad nan normals) should throw errors as well.

Actually, looks like there's no mechanism for the loaders to do anything besides return false right now and signal general failure: https://github.com/BabylonJS/Babylon.js/blob/master/src/Loading/babylon.sceneLoader.ts#L176

Talked to David, he mentioned loaders should return false and use Tools.error to provide more details.


Suggested changes to text of JOSS paper

Raising issue as part of JOSS review https://github.com/openjournals/joss-reviews/issues/5021
Some suggested changes to the text of the JOSS paper:
However the estimation of models'parameters →
However the estimation of models' parameters
(missing space between models' and parameters)
A common strategy to explore parameter space is to sample through a Markov Chain Monte Carlo (MCMC). →
A common strategy to explore a model's parameter space is to approximately sample the posterior distribution on the parameters with a Markov Chain Monte Carlo (MCMC) method.
(Markov chain Monte Carlo is a descriptor of a class of algorithms and wouldn't usually be used as an object grammatically; MCMC methods sample from a distribution so helpful to specify what distribution this is)
Yet even MCMC methods can struggle to faithfully represent the parameter space when only relying on local updates. →
Yet even MCMC methods can struggle to faithfully represent the posterior distribution on the parameter space when only relying on local updates.
(the Markov chain samples generated by an MCMC method represent a distribution on the parameter space, typically a posterior distribution in a Bayesian inference context, not the parameter space itself)
FlowMC is a Python library for accelerated Markov Chain Monte Carlo (MCMC) →
FlowMC is a Python library implementing accelerated MCMC [methods/algorithms]
(no need to repeat acronym definition and again better to use MCMC as a qualifier)
At its core, FlowMC uses a local sampler and a learnable global sampler in tandem to efficiently sample posterior distributions →
At its core, FlowMC combines Metropolis-Hastings based Markov kernels proposing local moves and global moves (using a learned approximation to the target distribution) to efficiently sample posterior distributions with non-trivial geometry
(to me local and global sampler are too vague and in particular global sampler is a bit misleading as the moves proposed using the normalizing flow model are still accepted or rejected within a Metropolis acceptance step meaning the moves are still 'local' when the proposals are rejected)
While multiple chains of the local sampler generate samples over the region of interest in the target parameter space, the package uses these samples to train a normalizing flow model, then use it to propose global jumps across the parameter space. →
While multiple chains using Markov kernels with local moves generate approximate samples from the target posterior distribution on the parameter space, the package uses these samples to train a normalizing flow model approximating the target distribution, and uses this approximation to propose global jumps across the parameter space within a Metropolis independence sampler.
MALA → Metropolis adjusted Langevin algorithm (MALA)
GPUs → graphics processing units (GPUs)
TPUs → tensor processing units (TPUs)
SIMD → single instruction multiple data (SIMD)
(all abbreviations should be defined on first usage)
As soon as the dimension of  exceeds 3 or 4, it is necessary to resort to a robust sampling strategy such as a MCMC
I would not be so specific here as actually I would say MCMC methods are not necessarily the best choice for target distributions on spaces with dimension 5 with quadrature methods, rejection sampling and importance sampling methods all being potentially viable in these sort of dimensionalities. I would say something more vague like In high dimensions or For parameters spaces with more than a few dimensions would be better.
Jax → JAX (capitalisation should be consistent throughout)
GPU and TPU supports → GPU and TPU support
The entire algorithm belongs to the class of adaptive MCMCs → The entire algorithm belongs to the class of adaptive MCMC methods
the chains previous steps → the chains' previous steps
Use of Accelerator → Use of Accelerators
leverage Just-In-Time → leverage JIT (abbreviation has been previously defined so should be used for subsequent usages)
the log-posterior function → a function to evaluate the logarithm of the (unnormalized) density of the posterior distribution of interest

Comments on the paper as part of JOSS review https://github.com/openjournals/joss-reviews/issues/5021, to supplement the (excellent) review above. NOTE these comments with regards to commit; d2414382fd74d51ed6d8ad9b9c28dd67e0592865, on kazewong/flowMC/40-joss-paper, which is currently the latest version of the paper.
General typo comments (in addition to the above review):

[ ] Title: Normalizing flow should not have a hyphen.
[ ] Capitalisation: unless, it is the first word of a sentence, or is someones name, e.g. Markov or Bayesian, do not capitalise. For example,  Just-In-Time to just-in-time , or Markov Chain Monte Carlo to Markov chain Monte Carlo , or Rational-Quadratic Splines to rational quadratic splines (there is no hyphen here), … etc.
[ ] As mentioned by the other reviewer. All acronyms need to be defined on first usage, but do not need to be repeated again. Another one not given above is HMC as Hamiltonian Monte Carlo .
[ ] You are using NF, short for, normalising flow. This is fine, but I would recommend defining this upon the first instance of normalizing flow appears (which is the summary section) and using NF thereon.
[ ] None of your math equations are correctly punctuated.
[ ] Remove unnecessary adjectives from the manuscript. These make sentences challenging to read, e.g. more and more , increasingly , very , etc.

From the other reviewer’ feedback in the above, I would recommend you hyphenate Metropolis-adjusted Langevin algorithm (MALA) , and do not capitalise “chain” in Markov chain Monte Carlo.
For more typos please see my PR #80. Note this PR does not address all the above (or the below), it only contains some of what I have noticed.
Structure (mostly ignoring typos here)
Summary
“Across scientific fields, more and more flexible models are required to understand increasingly complex physical processes.”

[ ] Baseless claim. Need examples with citations if you wish to use this in the paper.

“However the estimation of models’parameters becomes more challenging as the dimension of the parameter space grows.”

[ ] Motivate why we need high dimensional probabilistic models to model physical processes in the first place? Why does inference become challenging in higher dimensions?

“estimation of models’parameters”? This is myopic for a Bayesian approach? I would talk about the challenges of inferring the posterior distribution, rather than parameter estimation (which is only one facet of Bayesian inference).

[ ] Perhaps mention intractability of the posterior and would motivate why we are using approximate inference to begin with?

typo: models’parameters
“Yet even MCMC methods can struggle to faithfully represent the parameter space when only relying on local updates.”

[ ] What MCMC methods? Perhaps you mean conventional MCMC methods? Please say so.
[ ] Why / in what sense do they struggle? Perhaps you mean they are inefficient / take longer time to converge in higher dimensions. Can you please reference literature that highlights this issue.
[ ] As identified by the first reviewer, parameter space is another typo.

“The flowMCsampler can handle non-trivial geometry, such as multimodal distributions and distributions with local correlations.”

[ ] typo: flowMCsampler

“It is built on top of the machine learning libraries JAX and Flax.”

[ ] Both JAX and Flax need citations.

“While multiple chains of the local sampler generate samples over the region of interest in the target parameter space, the package uses these samples to train a normalizing flow model, then use it to propose global jumps across the parameter space.”

[ ]  “the package” I would be specific with flowMC

“The key features of flowMC are summarized in the following list:”

[ ] Personally, not a fan of seeing bullet lists in a paper. This could be rewritten more cohesively.

I would try and aim for two concise paragraphs at the most in this section. Though you do state some features of normalising flow enhanced MCMC, I would tell the story in a differently to make the comparison clearer to why you would use this over conventional MCMC. I would first be specific with the misgivings  of conventional MCMC, i.e., inefficient in high dimensions, state the issues with multimodal and locally correlated distributions, and then after that introduce the normalising flow approach “on the other hand” …. Perhaps mention the target audience, to draw reader in.
Statement of need
Already mentioned. But it is important you punctuate all maths.
Gradient-based sampler
“The computational cost of obtaining a gradient in this way is often of the same order as evaluating the target function itself, making gradient-based samplers favorable with respect to the efficiency/accuracy trade-off.”

[ ] This is a baseless claim. Moreover, it is irrelevant if this is generally true for most automatic differentiation software. What is of relevance here: can you guarantee this true specifically for your JAX implementation, and or for JAX in general? If yes, do justify, if not then remove. This otherwise serves as an unfounded performance claim, and I advise you remove this.

Learned transition kernels with normalizing flow
”Posterior distribution of many real-world problems have non-trivial geometry such as multi-modality and local correlations, which could drastically slow down the convergence of the sampler only based on gradient information.”

[ ] Baseless claim. Please cite relevant literature.

[ ] Typo: “Variant of this idea have been...” to “Variants of this idea have been...”

[ ] “and references therein”. If these are important, please cite, if not remove.

[ ] Sequential Monte Carlo to sequential Monte Carlo

[ ] Use of Accelerator to Use of accelerator
 ”Modern accelerators such as GPUs and TPUs are designed to execute dense computation in parallel. Due to the sequential nature of MCMC, a common approach in leveraging accelerators is to run multiple chains in parallel, then combine their results to obtain the posterior distribution. However, a large portion of the computation time comes from the burn-in phase for which chain-parallelization provides no speed up.”

[ ] Don’t see how this is relevant. I would remove this, to just have just this:

flowMC is built on top of JAX, so that it supports the use of GPU and TPU accelerators by default. Users can write codes in the same way as they would do on a CPU, and the library will automatically detect the available accelerators and use them at run time. Furthermore, the library leverage Just-In-Time compilations to further improve the performance of the sampler.

[ ] Note there are a few typos in the above paragraph as identified in my PR #80.

Simplicity and extensibility - Make it clear this concerns the target audience.
“While we provide a high-level API for most of the users, the code is also designed to be
extensible.”

[ ] Who are “most of the users”? Practitioners?
[ ] Designed to be “extensible”.  Great, but for whom? Researchers?
[ ] Make it clear who the target audience is.

Overall
This is shaping up nicely. You give key functionality that your library has to offer and identify the advantages of a JAX codebase. Just need to fix those typos, and support some the claims made. Look forward to reading the revised version. :)

Thanks a lot @Daniel-Dodd and @matt-graham for the valuable feedback and the spotted typos.
I iterated on your suggestions in commit:
#1827618
@Daniel-Dodd we are leaning towards keeping the key features itemized as we feel it makes it easy for readers to parse them.

Nice work, @marylou-gabrie! Paper looks good to me - the story is nice and clear. Happy with the itemized list. :)
Just noticed a couple of things on 84c7fdf. Think, @matt-graham, left a few comments on your commit changes, but I'll give mine here. I believe that some of your references aren't appearing on the compiled pdf, perhaps due to missing an @ symbol? Also, I spotted a few remaining typos:
Intro
Paragraph 1:

[ ] prohitive -> prohibitive

Paragraph 2:

[ ] While multiple chains are ran using local-update Markov kernels to .... -> While multiple chains are run using local-update Markov kernels to ...

Itemised list:

[ ] Use of accelerators such as graphics processing unites (GPUs) and tensor processing unites (TPUs) are natively supported. The code also supports the use of multiple accelerators with SIMD parallelism. -> Use of accelerators such as graphics processing units (GPUs) and tensor processing units (TPUs) are natively supported. The code also supports the use of multiple accelerators with SIMD parallelism.
[ ] By default, just-in-time (JIT) compilations are used to further acclerate the sampling process. -> By default, just-in-time (JIT) compilations are used to further accelerate the sampling process.

Statement of need:

[ ] The mathematical detail of the method are explained in [@Gabrie2021a]. -> The mathematical details of the method are explained in [@Gabrie2021a].

[ ] While we provide a high-level API suitable for most practitionners, the code is also designed to be extensible. -> While we provide a high-level API suitable for most practitioners, the code is also designed to be extensible.

Thank you very much for all your feedback. I believe all your remarks have been taken into accounts.

@marylou-gabrie nice one, really pleased with the end result, it reads well! Good job. :)


Callout width larger than total screen width, breaks on smaller screens

Problem: The width of the .callout element is larger than the width of the screen, causing a resize and a white bar to appear on the right (visible in the header/footer of the page).
Root cause: Line 5 of _components.scss - the max width is unset.
Potential Solutions:

Change line 5 to max-width: calc(100vw + 1rem); - fixing the white bar on the right, but now having rounded corners visible only on the right side.
Change lines 4 and 6 to width: calc(100% + 2rem); and margin: 2rem -1rem 2rem -1rem; accordingly, essentially making the callout fit the size of the screen. *This may require additional changes to the padding, depending on the desired look.

Thanks for reporting! Should be fixed in the latest version.


Significance of Python version for resolved dependencies

Hi!
pip-compile resolves dependencies for a particular Python version, and it is important because projects can define dependencies like this:
importlib-metadata >=4.3; python_version < '3.10'

To represent this, it includes a comment, which at least makes it clear, but nothing is done with it as far as I know:
# This file is autogenerated by pip-compile with Python 3.11

and in that file for the above example importlib-metadata isn't even mentioned anywhere! So it will just not work if someone tries to use this lock file with Python 3.9.
As such, I think this plugin could be improved as follows, especially because Hatch gives it direct information about the intended Python version:

Include the Python version into the header (currently it is stripped)

Perhaps warn users when an environment is invoked that the lock file might be intended for a different Python version than is currently used?

Anything else? Like managing separate lock files in case there is a matrix with multiple Python versions?

Oh, I like this idea. Here's what I'm thinking for an error message and updated header - open to any feedback though
####################################################################################
# 🔒 hatch-pip-compile 🔒
# Generated with Python 3.9.4
#
# - hatch
#
####################################################################################

Python version mismatch detected
    Lock File: requirements.txt
    Lock Version: 3.9.4
    Hatch Environment (default): 3.11.4
Dependencies will be attempted to be synced, but may fail
Lock file will not be updated - delete the lock file to regenerate

This message only applies when an existing lock file is detected. Only Python major and minor versions are considered when comparing.

Good stuff!
My suggestion:
-Generated with Python 3.9.4
+Generated with Python 3.9

Motivation: This will cause a diff way too often and doesn't help - patch version never affects anything.

-Dependencies will be attempted to be synced, but may fail
+Dependencies will still be installed, but they may be incorrect for this Python version

Motivation: for the particular example I showed, the dependencies will actually install fine, just that at run time it will fail to import because it's missing. I think this will be the much more typical scenario, though failure to sync might also be a possible outcome, I'm not sure.

Additionally:
While we are here, could I ask to avoid the lock emoji 🥺
It'll be the only character always bringing the file out of ASCII range - and who knows which tool may somehow not like that.

Ah and I forgot to add-- maybe adding too many big warnings is not the most pragmatic solution. If one contributor updates their Python but another one doesn't, and can't do so easily, the warning can be too annoying. And maybe the lock files will work across versions in most cases anyway so people will just be angry at the warning 😕
Anyway - maybe the warning should be really short and/or dismissable somehow

Closing this as #9 was merged via #11. Let me know if you have any other concerns and we can re-open


Have build system generate fancy <meta> metadata goodness for Twitter, Facebook cards

https://github.com/luiguild/gulp-fancy-meta/blob/master/index.js

relevant tweet: https://twitter.com/cvanw/status/974068622468423680


fix: adapter-netlify redirect for /_data.json

Fixes #8999
Included a if statement to catch root route
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[x] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

thank you!


Cordova doesn't link to correct files

The translation files doesn't seem to get through when doing a cordova build. Have you tried this?

:+1: Going with the one language rename to en for now.

Any updates or timeline on this? What is the issue, any pointers for looking into a PR?

+1

Support for Cordova when internet connection is available added in v1.4.0.
https://github.com/TAPevents/tap-i18n#using-tap-i18n-in-cordova-apps
Thanks to @slickdev for funding it.

Hey @theosp, i am currently working on a cordova project and i think its critical to have i18n on mobile devices without requiring internet connection. As the language files are bundled by meteor to the application it should be possible to load them completely without internet connection.  I would try to create a PR for this if you would take the time to describe your current solution and the problem, this would save me a lot of time.
Best,
Ahmed

Hi Ahmed,
Work in this direction is currently in progress for v1.6 , will post it the
release candidate as it'll be ready so you can help with testing.
-Daniel
On Fri, Jun 26, 2015 at 9:44 PM, Ahmed Hassan<EMAIL_ADDRESS>wrote:

Hey @theosp https://github.com/theosp, i am currently working on a
cordova project and i think its critical to have i18n on mobile devices
without requiring internet connection. As the language files are bundled by
meteor to the application it should be possible to load them completely
without internet connection. I would try to create a PR for this if you
would take the time to describe your current solution and the problem, this
would save me a lot of time.
Best,
Ahmed
—
Reply to this email directly or view it on GitHub
https://github.com/TAPevents/tap-i18n/issues/25#issuecomment-115695327.

Hi, I am now using v1.7 and I have the same issue when trying to run my app on an iOS device: "Couldn't load language 'fr' JSON: error"
On desktop it works fine. Do you have any idea?

I have a similar problem with Meteor 1.2.1 and tap-i18n 1.7.0. Translations are not loaded on Android nor on iOS, but the app itself is working. Translations are working on my desktop development environment.
When testing on Android, I get this error message:
(android:http://meteor.local/:0) XMLHttpRequest cannot load http://<IP_ADDRESS>:3000/i18n/de.json. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://meteor.local' is therefore not allowed access.

Any idea how to resolve this issue?

@arjank @arathipanya. Did you find a solution for this?

@miri-am Unfortunately no... At last I just created a simple cordova project linked to my server, where my Meteor app is hosted.

@miri-am not really. It seems to work when I remove the app from the phone and then re-build / re-install it, so it could be a caching issue.

@arjank using meteor 1.2.1, I realized if you test locally don't use the mobile-server option it confuses the loading imho. And yes deleting the app or deleting all app data helps often.
Also I changed my cdn_path in project-tab.18n to the url on production server with this https://www.productionserver.com/i18n since my app did not even continued to load.  It could not connect to the right cdn_path. it was looking on a completely wrong server. an ip which is still a miracle to me.


Subsequent xinit calls fail with inability to move logs.

name: xenial
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/xenial...
crouton: version 1-20171122220410~master:99877eaf
release: xenial
architecture: amd64
xmethod: xorg
targets: xorg,keyboard,extension,core,x11
host: version 9901.77.0 (Official Build) stable-channel edgar
kernel: Linux localhost 3.18.0-16037-gf59ef0b48a68 #1 SMP PREEMPT Mon Nov 13 16:36:01 PST 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /mnt/stateful_partition/crouton/chroots/xenial...
Please describe your issue:
Log file for Xorg cannot be moved by xinit
If known, describe the steps to reproduce the issue:
While in the chroot, I do xinit. It comes up fine.
I close it and do xinit again, I get:
Cannot move old log file "/tmp/Xorg.crouton.2.log" to "/tmp/Xorg.crouton.2.log.old"
I remove the log and repeat and the same thing happens, works once than the error.
I

It seems you're having problems with permissions on the tmp files.
Try giving the user you want to log in to ownership of the tmp files so crouton can move around the log files:
chown 1000 /tmp/Xorg.crouton*


Show number of changed lines on pull request's page

Feature Description
Good day!
(Strange but haven't found a feature request like this.)
Propose to show number of changed (added, removed) lines on pull request's page.
Thanks!
Screenshots

Did you mean

? It has been implemented. You need to change to File Changed tab

You need to change to

The idea is to let me don't:

on pull request's page.

Closing in favour of #25326, will be implemented by #25387


[RFC] Need to be able to compile only rustpython's virtual machine to wasm

Summary
RustPython in the web can be one of it's best use cases
The python community have been pushing to have python run in the browser.
Many such implementations have been brython, skulpt, Batavia etc.
Likened with batavia's approach to run python bytecode  in the browser, I have been wondering if rustpytgon can ship only it's virtual machine to do similar task
Detailed Explanation
Rustpython's  wasm module currently is about 4.5mb. thus size is too big to be inculcated in most projects.
However I believe if we could remove the parser, lexer and other compiler related stuff and compile only the virtual machine, the size will drastically reduce.
This approach will also require that apps get compiled on their maybe machines before the bytecode is shipped.
Drawbacks, Rationale, and Alternative
Rationale:
It will take a long time for RustPython to get to compete with cpython natively(where cpython works well already) but the web is one place where competition is less. If this works, we can have web apps fully written in python(little to no javascript)
Be able to run already existing software on the web.
This can also lead to the revolution of building front end livraries. Like implementing python alternatives to react, angular, Vue etc.
Currently, the beeware team have been working hard to have the Toga(beewae's gui library) working in browsers but are limited by the size of Batavia.
I may certain everyone loved Anvil.works for their idea of creating web apps completely in python.
Possible Drawback:
Since apps will need to be compiled before shipped and most people use cpython, rustpython's vm must be able to run cpython generated bytecode
This may not even be an issue but I raise this because I'm unaware of the bytecode implementation.

This is a really nice idea; we've experimented with excluding the parser and compiler for native executables of rustpython, but not yet for wasm. We don't currently run CPython bytecode; we have our own bytecode format and I think it would be less effort to have people install the rustpython compiler as part of whatever toolchain this would be than it would be to convert CPython's bytecode to RustPython's. Also, I could see bundling 2 different versions of rustpython into the rustpython_wasm npm package; one with the compiler (import "rustpython_wasm") and one with only the vm (import "rustpython_wasm/vm-only").

Well I think the proposed fix with regards to cpython bytecode (thus having to install RustPython for the toolchain) is great and won't be difficult implementing.
If excluding the parser is capable of generating smaller wasm file probably just kilobytes, then if the size is still too large, a little tree shaking can be done especially on parts of the standard library that won't be needed on the web.

I would love to ask if it will be a simple task to compile only the vm to webassembly as I am unsure of how it depends on the other modules. And if possible, suggestive steps to make that work ?

Yep, you just have to disable the default features (which right now is rustpython-parser and rustpython-compiler), and then the VM won't depend on the parser and compiler crates:
[features]
parser-compiler = [
    "rustpython-parser", "rustpython-compiler",
    "rustpython-vm/rustpython-parser", "rustpython-vm/rustpython-compiler"
]
default = ["parser-compiler"]

[dependencies]
rustpython-parser = { path = "../../parser", optional = true }
rustpython-compiler = { path = "../../compiler", optional = true }
rustpython-vm = { path = "../../vm", default-features = false }

Then, just add #[cfg(feature = "parser-compiler")] attributes to everything in the rustpython-wasm crate that uses rustpython_compiler or rustpython_parser (which should be a lot, because right now we only support passing code as strings), and add new APIs that can accept Vec<u8>s and use rustpython_bytecode::bytecode::CodeObject::from_bytes to deserialize them.

You can test if it works by commenting out the default = [...] line and compiling the demo (npm run dist). Also, I really don't think it's very feasible to try to convert CPython->RustPython bytecode; they're different enough that it would be difficult/inefficient to do so, and it really does not bring much benefit (in my view). Also, it would have to be done at runtime, which would just add to the startup time of the python wasm app.

Thank you very much. I will try the solution out. I have my hopes high already. Off to work!

I am also interested in getting python to work in the browser... but the use cases that I know of are related to academia, publishing scientific papers and reproducible research especially in economics.
The load time is not as huge of a hurdle or at least I can manage the user's expectation and some some smart loading of resources.
I'll look the merge request from 10 days ago. I've seen your demo and looked at another repo https://github.com/RustPython/demo where there is a .wasm file and re-used that. Is there an "optimal" way or just a minimal source code to load python in browser? Should we add those to examples?


New version search bookmarks differently

Issue continues from #9.
If I search for ”react” both an old and a new version (0.1.1) have same results. I want to narrow down results and specifying search query with another word  (“react redux”). Old version shows a result that has both “react” and “redux” in a bookmark, but a new version, I suppose, shows results that have “react” or “redux” in a bookmark.
Old version results (results are different):

New version results (results are the same, but maybe it contains more search results):

Please download new version from https://github.com/mdreizin/chrome-bookmarks-alfred-workflow/releases/tag/v0.1.2
New version will be added automatically when travis finishes build https://travis-ci.org/mdreizin/chrome-bookmarks-alfred-workflow/builds/141552162

Thank you for quick response and changes!
It's almost done :)
I have these links:
Building React Applications with Idiomatic Redux - Course by @dan_abramov @eggheadio
https://egghead.io/series/building-react-applications-with-idiomatic-redux

React and Redux Single Page Applications Resources — Medium
<EMAIL_ADDRESS>
Leveling Up with React: Redux | CSS-Tricks
https://css-tricks.com/learning-react-redux/

How to Build a Todo App Using React, Redux, and Immutable.js
https://www.sitepoint.com/how-to-build-a-todo-app-using-react-redux-and-immutable-js/

mxstbr/react-boilerplate: Quick setup for performance orientated, offline-first React.js applications featuring Redux, hot-reloading, PostCSS, react-router, ServiceWorker, AppCache, FontFaceObserver and Mocha.
https://github.com/mxstbr/react-boilerplate

When I'm searching react redux last link is not in results, but all other links are. But when I'm searching for react Redux all links in results including last one. Even react edux shows last link :)
Previous workflow show all five links for both react redux and react Redux.

@hudochenkov I have just fixed this issue. Please wait for 0.1.4.

Wow you're quick! Thank you! I use your workflow very often, thank you for saving my time :)


When I build by rollup, I got the bellow error.

DON'T merge. The PR that I only want to watch this diff.
⚠   The 'this' keyword is equivalent to 'undefined' at the top level of an ES module, and has been rewritten
https://github.com/rollup/rollup/wiki/Troubleshooting#this-is-undefined
node_modules/whatwg-fetch/fetch.js (460:40)
458:   }
459:   self.fetch.polyfill = true
460: })(typeof self !== 'undefined' ? self : this);
^

Sorry, I mistook.


Patrons included in "most up to date sheet"

It seems like pygrambank cldf is excluding the Patron column when generating "Grambank_most_updated_sheet". That seems unfortunate.

Sorry, not the CLDF command I think. Whichever is rendering "Grambank_most_updated_sheet"

Ok, needs to be added here https://github.com/grambank/pygrambank/blob/606b3da1bf63a007edeb4f3fde16d0b33052b733/src/pygrambank/commands/new.py#L29-L39

Great!


Determine where historical benchmarking data should live

As part of https://github.com/coiled/coiled-runtime/issues/148, we'll need to store historical benchmark results somewhere. We should determine where those results should live. For example:

In this repository
In a dedicated coiled-runtime-benchmarks (or some other name) repository
In S3
...

Related to https://github.com/coiled/coiled-runtime/issues/186

A quick update on my thinking here:
In #208 we are keeping historical data (as well as cluster dumps and probably performance reports) as a sqlite file in S3. This is an easy decision to reverse if we want to try to do something else, since it's a fairly straightforward tabular dataset written using sqlalchemy, all of which is pretty swappable.
We had a couple of discussions around keeping the benchmarks checked into the repo. This may work, and we can revisit this, but I think we want to avoid that for the time being in order to keep flexibility while we explore different models of running CI. This avoids having to work through merge conflicts with concurrent builds, having benchmark updates trigger their own CI runs, etc (none of those are insurmountable, but are not necessary right now, IMO).


Cloud DNS polling on change status? (change is almost like an LRO)

In Cloud DNS, when I create a change on a zone, I get back a Change -- which should have been a long-running operation, but isn't. This means that I can't easily attach a handler to "should the status of this change, run this callback".
Can we treat a dns#Change resource the same way as a long-running operation? And allow hooking up callbacks to those with some polling something?

Pending DNS library support

@danoscarmike we do have support for DNS in the library via @google-cloud/dns.

This issue was moved to googleapis/nodejs-dns#10


Query Filter "Not In ...."

Hi Oro Team,
When filtering with a Select list "My Field"

We would expect that all values that are not set or have no defaults to be included. Otherwise, there is no way to create a segment with entities that does not have a value set.

Current behavior
The  current SQL query is generated from the above filter.


Update Calendar.vue to fix alignment

The Calendar component's CSS adds additional padding which results in Saturday and Sunday not being aligned with the rest of the days.
This appears to fix: https://github.com/radix-vue/shadcn-vue/issues/343

Thanks for your PR, great 👍

Strange, those changes you removed used to prevent some other issues, which now cause problems 🤔
Will review tomorrow. Thanks

Noticed vc-weekdays default style using grid but in our style, we applied flex to it
Just added justify-items-center to vc-weekdays and cleared other paddings