Latex workshop won't make a pdf viewer

Sorry  I didn't notice that thee information didn't add to the post issue.
First, when i build latex file i get this output .

[09:55:36] Initializing LaTeX Workshop.
[09:55:36] Creating LaTeX Workshop http and websocket server.
[09:55:36] LaTeX Workshop initialized.
[09:55:36] Found root file from active editor: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Root file changed from: undefined. Find all dependencies.
[09:55:38] Instatiating new file watcher for c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Parsing c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Cannot find .bib file references
[09:55:38] Server created on <IP_ADDRESS>:55389
[09:55:38] Snippet data loaded.
[09:55:38] LaTeX Workshop version: 6.0.0
[09:56:02] BUILD command invoked.
[09:56:02] Found root file from active editor: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:56:02] Root file remains unchanged from: c:\Users\khalil\Downloads\modele_ensi_pcd.tex.
[09:56:02] Building root file: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:56:02] Build root file c:\Users\khalil\Downloads\modele_ensi_pcd.tex

and when I run the pdf preview on vscode tab or on the browser i get this output .

[10:01:55] VIEW command invoked.

and nothing happen.

We have written the needed data into your clipboard because it was too large to send. Please paste.

@khalilRhouma please share the needed information to help troubleshoot.

Sorry  I didn't notice that thee information didn't add to the post issue.
First, when i build latex file i get this output .

[09:55:36] Initializing LaTeX Workshop.
[09:55:36] Creating LaTeX Workshop http and websocket server.
[09:55:36] LaTeX Workshop initialized.
[09:55:36] Found root file from active editor: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Root file changed from: undefined. Find all dependencies.
[09:55:38] Instatiating new file watcher for c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Parsing c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:55:38] Cannot find .bib file references
[09:55:38] Server created on <IP_ADDRESS>:55389
[09:55:38] Snippet data loaded.
[09:55:38] LaTeX Workshop version: 6.0.0
[09:56:02] BUILD command invoked.
[09:56:02] Found root file from active editor: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:56:02] Root file remains unchanged from: c:\Users\khalil\Downloads\modele_ensi_pcd.tex.
[09:56:02] Building root file: c:\Users\khalil\Downloads\modele_ensi_pcd.tex
[09:56:02] Build root file c:\Users\khalil\Downloads\modele_ensi_pcd.tex
and when I run the pdf preview on vscode tab or on the browser i get this output .

[10:01:55] VIEW command invoked.

and nothing happen.

We have written the needed data into your clipboard because it was too large to send. Please paste.

@khalilRhouma please share the needed information to help troubleshoot.

Yes , Sorry I didn't notice that .

Close as lack of enough information to help troubleshoot. We can reopen whenever we have good reproduce steps.


Question about local copies

I have a google drive account, and I have computers at 2 different locations. Both computers are running OSX.
On computer A, I plan on keeping all the content local, but letting the folders sync UP to the gdrive.
On computer B, there is much less storage and higher download capacity, so I'd rather let it steam most of the stuff down.
How would I setup Plexdrive to encrypt it, but always leave the copy on computer A forever?

You want the setup 2 Plex Media Server on 2 computer?

You can achieve this by adding rclone to the mix. Essentially, rclone does all of the uploading on computer A and a combination of plexdrive and rclone will do the downloading+decrypting for computer B.
Computer A:

Uploads occur via rclone sync
All uploads are local encrypted first

[local_file] -> [rclone crypt] -> [rclone to google drive]
rclone config file example:
[googledrive]
type = drive
client_id =
client_secret =
token = insert_token
[googledrivecrypt]
type = crypt
remote = googledrive:/encrypted_folder
filename_encryption = standard
password = super_long_key
password2 =
Syncing up
rclone sync /home/local/media googledrivecrypt:/
Computer B:

Will use plexdrive to grab the encrypted files on the fly
Will use rclone to decrypt the plexdrive encrypted files on the fly

[google drive encrypted files] -> [plexdrive to fetch] -> [rclone local to decrypt] -> [local_file_decrypted]
rclone config
[google-drive-decrypt]
type = crypt
remote = local:/mnt/plexdrive/encrypted_folder
filename_encryption = standard (or one of the other options)
password = insert-long-encryption-key-here-again
password2 =
Basic mounts
See rclone forums for cleaner upstart mount. See plexdrive wiki for cleaner upstart mount)
plexdrive /mnt/plexdrive
rclone mount google-drive-decrypt:/ /mnt/media
At this point you should clean decrypted files at /mnt/media. The raw downloading of files will be courtesy of plexdrive and the decryption of said files courtesy of rclone

Note that two separate plex servers will be running, each with their own copy of metadata. See plex forums on how to keep show/movie watch progress in sync between servers.

I have a similar setup, but on Computer A, I need to be able not to copy but automatically move the files: [local file] -> [rclone move to Google Drive] -> [delete local file]. This should happen automatically so I don't have to manually execute the commands to sync and delete source. Any thoughts?

Use rclone move for this. Here is an example bash script which ensures one copy is running at a time (I found this on the web somewhere and slightly tweaked it. I take no credit):

#!/bin/bash
if pidof -o %PPID -x "rclone-cron.sh"; then
echo "$(date "+%d.%m.%Y %T") EXIT: rclone-cron.sh already running."
exit 1
fi
echo "Starting rclone-move at $(date "+%d.%m.%Y %T")"
/usr/local/bin/rclone move path/to/local.folder remotepath:/ -v --log-file=/var/log/rclone-sync.log
exit

Just put something like that ^ in a crontab to run it on a schedule

@Brandon168 s answer is very good. In case there is no actual problem here I close this issue.


Option to check every write in TFRecordWriter.

Referencing this post on stackoverflow.
There may be situations when we write huge databases of images into a TFRecord (or at least a few TFRecords). It would be good if there's an option to check every write to prevent such cases of corrupted data happening during training.
@allenlavoie

@jkschin You mentioned you have run twice, so did you use the same TFRecord file or recreate it for each run?
If it's the first case, I guess you are using local disk. It might be just corruption in the IO path, like broken disk, bugs in IO controllers, non-ECC memory and bit rot etc. But this should be rare. Using checksum-ed auto recovery (by either duplication or EC code) file system like GFS, HDFS (or simply RAID) can avoid most of the problems. I think check every write to prevent such cases of corrupted data happening is not the responsibility of tensorflow.
If it's the second case, it may be a bug.

@llhe, I could recreate the error. I used the same TFRecord file 4 times. I decided to recreate the TFRecord. It worked.

@llhe the case of corrupted data is definitely something that happens locally. It's probably a black swan event. I'll close this as it's probably not wise to implement such a thing.

@jkschin @allenlavoie May be adding an option Ignore corrupted record silently in the reader is a reasonable feature request? Looks like many TF users use poor unstable storage but processing big data which data corruption is not that rare.


Apply style in excel.

I am generating the XLSX formate of excel , I want to use same style which I have received from HTML string.
Please suggest Its important for me.

I am closing this issue as a duplicate of:

#12: How to apply styles to excel file?

I am closing this issue as a duplicate of:

#12: How to apply styles to excel file?


Missing timeouts for fti plugin tests

In GitLab by @ksiero on Dec 14, 2020, 12:48

In GitLab by @ksiero on Dec 14, 2020, 12:48
mentioned in commit 7d6828a2a5d3703757933aa753a7f20154b2c90a

In GitLab by @ksiero on Jan 16, 2021, 19:15
mentioned in commit af25d80037c184115a0d55723064ced7c10bc036

In GitLab by @ksiero on Jan 16, 2021, 17:21
mentioned in commit b34c96f7baab65757335f9772c014e96e2855954

In GitLab by @ksiero on Dec 14, 2020, 12:53
mentioned in commit 6d815e9ea8afde8631c146f1be7428044884bbb9

In GitLab by @ksiero on Jan 7, 2021, 14:09
mentioned in commit 2dd074b10395ee7897cb7fd6e70d3d4ca32f7ef5


Noise floor and digital black

Factor out any digital black in the audio data from the calculation of noise floor level.

Not sure about this.  What would cause the Noise_floor_dB in the csv to report a value of "=-inf"  I thought that "=-inf" implied 0 sample value, but after checking a few examples (w/ Audition's Amplitude Statistics) that does not seem to be the case.

In case you've not seen it, here is an example of that reporting:

Try latest ffmpeg version from git, it should have fixed noise floor calculation, no longer uses histogram approach, and was limited to 8192 bins - which caused that very small noise floors would be reported as -inf while in fact they where not 0.

@richardpl Do you know if a new version of FFmpeg will be released soonish?

Not really, there was plan to release 6.1 in July but overall situation and morale is pretty low since "introduction to mailing list/pushing for committing" of avradio/(Software Defined Radio) directly into FFmpeg.

Thank you for the information! This confirms my feelings.


Redshift support time zones in time stamps from Sep, 2016

See: Amazon Redshift introduces new data type to support time zones in time stamps
So,

Redshift can set time zone to session using SET TIMEZONE
And can create table with TIMESTAMP WITH TIME ZONE fields

Is there a migration path to convert an existing database?

Maybe No.
I migrated manually.

Yo @shimizukawa -- can we proceed merging this one? It is highly demanded feature. Thank you. :)

Actually I have no spare time but I'll take a look ASAP.

Hey @Surgo, can you please update the README file at the "Type mapping" section to match the underlying Redshift type? Thanks!

@emyller Thank you for your comment. updated :)

From now, I check this PR.

I'll merge this PR after resolve conflict. @Surgo can you please rebase?

@shimizukawa rebased :)

Thanks, I'll merge soon!
On Sun, Aug 27, 2017 at 7:21 PM Kosei Kitahara<EMAIL_ADDRESS>wrote:

@shimizukawa https://github.com/shimizukawa rebased :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shimizukawa/django-redshift-backend/pull/23#issuecomment-325189694,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJQR1W6I8v1_iJxtvJOSu6orC6-ANFcks5scUMrgaJpZM4OcU_H
.

@Surgo please check this updated README if you have a chance ;)
https://github.com/shimizukawa/django-redshift-backend/commit/47d92feb586c1c19a346b18e6666f9ca7c4efd1e#diff-88b99bb28683bd5b7e3a204826ead112

@shimizukawa thank you for your support!


can't run my Web appliation

void main() => runApp(MyApp());
class MyApp extends StatelessWidget {
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return MaterialApp(
title: 'Flutter Demo',
theme: ThemeData(
primarySwatch: Colors.blue,
),
home: MyHomePage(),
);
}
}
class MyHomePage extends StatelessWidget{
@override
Widget build(BuildContext context){
return Scaffold(
body: Container(
decoration: BoxDecoration(
gradient: LinearGradient(
begin: Alignment.centerLeft,
end: Alignment.centerRight,
colors: [Color.fromRGBO(195, 0, 0, 1.0),Color.fromRGBO(155, 125, 125, 1.0)]
)
),
child: Column(
children: [
NavBar()
],
),
),
);
}
}
class NavBar extends StatelessWidget{
@override
Widget build(BuildContext context){
return LayoutBuilder(
builder: (context,constraints){
if(constraints.maxWidth>800){
return DesktopNavbar();
} else {
return MobileNavbar();
}
}
);
}
}
class DesktopNavbar extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Container(
child: Row(
children: [
Text('COCULT',style:TextStyle(fontWeight:FontWeight.bold,color:Colors.white,fontSize:30)),
Row(
children: [
Text('Home',style:TextStyle(fontSize: 22,color: Colors.yellow)),
Text('About',style:TextStyle(fontSize: 22,color: Colors.yellow)),
Text('Contact Us',style:TextStyle(fontSize: 22,color: Colors.yellow))
],
)
],
),
);
}
}
class MobileNavbar extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Container(
);
}
}
-------------------When I Tried To Run This Code I Get The Following Message------------------
C:\Users\PC -01\code\webpoject2>flutter run -d chrome
Launching lib\main.dart on Chrome in debug mode...
Error compiling dartdevc module:webpoject2|lib/main.ddc.js
packages/webpoject2/main.dart:43:14: Error: The method 'NavBar' isn't defined for the class 'MyHomePage'.

'MyHomePage' is from 'package:webpoject2/main.dart' ('packages/webpoject2/main.dart').
Try correcting the name to the name of an existing method, or defining a method named 'NavBar'.
NavBar()
^^^^^^

AssetNotFoundException: webpoject2|lib/main.ddc.js
Failed after 7.2s
Building application for the web...                                33.1s
Failed to build application for the Web.
PLEASE HELP

If i try your code, it works just fine, your have a  flutter doctor? Seems like there is an import missing or so, do you have the code in several files and copied it together for github, or is this code in one file you are trying to run?

Actually this code has separated file. When i i run this code in one file,it works fine.but i wanted it separately.when i'm doing that the above error message will be shown.

This is an issue with your code.  Your question would be better asked on a forum like StackOverflow - this issue tracker is for Flutter bugs and feature requests.


Reverted (for now) to CMOR CMIP6 Tables Branch 010010

010010 was what we had before #962

Thanks @valeriupredoi, testing now...

Still not working...
ERROR:esmvaltool._main:Program terminated abnormally, see stack trace below for more information
Traceback (most recent call last):
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_main.py", line 228, in run
    conf = main(args)
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_main.py", line 122, in main
    cfg = read_config_user_file(config_file, recipe_name)
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_config.py", line 89, in read_config_user_file
    read_cmor_tables(CFG)
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 49, in read_cmor_tables
    table_path, default=default,
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 84, in __init__
    self._load_table(json_file)
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 115, in _load_table
    self._assign_dimensions(var, generic_levels)
  File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 125, in _assign_dimensions
    coord = self.coords[dimension]
KeyError: 'olevel'

Remove your build/dist/ESMValTool.egg dirs and reinstall, there is a bugger
CMOR_ohc custom var that has olevel as coord (remember my issue from Monday)
Dr Valeriu Predoi.

ERROR:esmvaltool._main:Program terminated abnormally, see stack trace below for more information
Traceback (most recent call last):
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_main.py", line 228, in run
conf = main(args)
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_main.py", line 122, in main
cfg = read_config_user_file(config_file, recipe_name)
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/_config.py", line 89, in read_config_user_file
read_cmor_tables(CFG)
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 49, in read_cmor_tables
table_path, default=default,
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 84, in init
self._load_table(json_file)
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 115, in _load_table
self._assign_dimensions(var, generic_levels)
File "/mnt/lustre01/pf/b/b309057/ESMValTool/public/esmvaltool/cmor/table.py", line 125, in _assign_dimensions
coord = self.coords[dimension]
KeyError: 'olevel'
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ESMValGroup/ESMValTool/pull/987#issuecomment-475150824,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbpCo_OUt9QSb-sKw6ZFZNYVS3IWpnPKks5vY0ftgaJpZM4b_2yb
.

OK that's not an issue from leftover custom tables, it is a real one, hang tight, I am looking at it :ambulance:

OK good thing I am a git guru (:grin: ), I reverted to the exact CMIP6 CMOR 01.10.10 that we had before the update to v30. Note that the version we had was (and is now) dirty ie https://github.com/ESMValGroup/ESMValTool/pull/987/commits/514ed30181b1433d03ea71c0eebe61bca1a050e9 differs from the one on PCMDI (not sure if these were changes we made or they made at any point; all I know is that is the diff between their 01.00.10 and our 01.00.10). At any rate, things work now :tada:

Testing again...

and here is the commit I used #7a74275da9b503f83435d18f7ae523ab2be366b4

Thank @valeriupredoi, it works now!

Once this is merged, please update the CMOR6 Tables in #985 and let's do the update in that PR (after extensive testing).
And #937 should be reopened.

Once this is merged, please update the CMOR6 Tables in #985 and let's do the update in that PR (after extensive testing).
And #937 should be reopened.

merge this into version2_development, then I'll do a merge of that into #985

And #937 should be reopened.

can you do that pls?


feat: make session token optional for local development

Overview
This change removes the requirement to set a session token when developing the dashboard locally, allowing usage of non-emphemeral AWS credentials.
Legal
This project is available under the Apache 2.0 License.

Looks good and nice update!

Thank you, @dpportet!


Annotation body choice items can also be of type TextualBody

Currently the choice type only allows an item array of resource_t type but needs to support TextualBody items. See https://iiif.io/api/cookbook/recipe/0346-multilingual-annotation-body/manifest.json

fix 1.1.4


Rust: Naming convention for fields is incorrect [Patch]

As per Rust RFC430
FIELD_NAMING_CONVENTION should be snake case
From f0e1a04cb88bd7ffcb66b80ddad15f8d6851cb15 Mon Sep 17 00:00:00 2001
From: Adam Leyshon<EMAIL_ADDRESS>Date: Thu, 15 Jul 2021 18:15:01 +0100
Subject: [PATCH] Fix Rust casing

---
 crates/target_rust/src/lib.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/crates/target_rust/src/lib.rs b/crates/target_rust/src/lib.rs
index b6215ce..4890e64 100644
--- a/crates/target_rust/src/lib.rs
+++ b/crates/target_rust/src/lib.rs
@@ -19,7 +19,7 @@ lazy_static! {
     static ref FIELD_NAMING_CONVENTION: Box<dyn inflect::Inflector + Send + Sync> =
         Box::new(inflect::KeywordAvoidingInflector::new(
             KEYWORDS.clone(),
-            inflect::TailInflector::new(inflect::Case::camel_case())
+            inflect::TailInflector::new(inflect::Case::snake_case())
         ));
     static ref ENUM_MEMBER_NAMING_CONVENTION: Box<dyn inflect::Inflector + Send + Sync> =
         Box::new(inflect::KeywordAvoidingInflector::new(
--
2.30.2.windows.1

Thanks for this. I agree this should be addressed, and that it seems your suggested patch (and amending the tests) is all that's necessary to fix the issue. Do you want to open a PR that does this?


no result or error in response

In my GTLService File.. The 1145 Line is
GTL_DEBUG_ASSERT(errorJSON != nil, @"no result or error in response:\n%@",
jsonWrapper);
I have the same Problem
*** Assertion failure in -GTLService parseObjectFromDataOfFetcher:,
/xxx/xxxx/Documents/git-repos/dev-objectivec/xxx/ios-app/Pods/iOS-GTLYouTube/Obj
ects/GTLService.m:1145
https://github.com/brynbellomy/iOS-GTLYouTube/issues/4

Without the request/response, it is sorta hard to guess what might be happening.  Try turning on logging (https://github.com/google/google-api-objectivec-client/wiki#logging-http-server-traffic) to get more details.

The issue you reference seems to be a fork of 3 year old code, can you get logs with something more current?


css prop always converted to className prop?

I was updating a project today to use the css prop and found myself adding it to 3rd-party components without thinking expecting it to work. But of course as they don't know know what to do with the css prop, things failed. Since almost all open-source react components handle className — perhaps that's what the css prop should be turned into?

yes, now that classnames work I should use that for the css prop. will do!

awesome! This should pretty much make Glamor Just Work™ across the React ecosystem :D

Well... I do purposely avoid non dom tags because I thougt I'd end up clashing with custom components' 'css' prop if it accepted any. Maybe that's not an issue?

I'd guess a component having a css prop is really rare. All theming options I've seen are className or inline styles based.
Oh but also what I'm suggesting (if this wasn't clear already) is if the tag is non-dom, then you convert the css prop to a className prop and pass that into the component instead.
So <Custom css={{ margin: 10 }} /> becomes <Custom className="hashed-classname" />
You could detect I guess if the prop value passed in isn't an object or an array and just pass it through untouched...
But regardless, I think it's fine throwing your weight around a bit. Glamor is legit and the css prop is a very sensible name for this sort of thing and I can't remember seeing anyone use it before. Also it'd make Glamor even more legit amazing because there's a lot of components that only let you style them with css (via setting a class or using there's) and this would let us have our inline styles cake and eat it too.

It'd also be a lot less confusing to explain Glamor to newbies as it stands right now, you'd have to say something like "you can use Glamor here but not there" which wouldn't quite make sense.

What if instead of using the css prop you just use just spread the existing glamor functions (style, merge, etc) on the component and instead of looking for that css prop, the custom createElement function instead looks for the data-css, data-glamor-theme, or glamor generated classNames and performs the necessary merging into a new className?

that's a bit too much 'magic' for me, I'm afraid. That said, there's some work happening in making a helper to do similar https://github.com/threepointone/glamor/pull/91

Fair enough. Just curious, which part pushes it past too much? I realize after looking back that what I suggested is trying to solve more than just the problem at hand - i.e. the possibility of conflicting prop names. I do think it's a bit optimistic to think that it won't be an issue in the future - a custom component wanting to use css as a prop name isn't unreasonable. You could still use a function instead of a prop (e.g. <Button {...css(stuff)} />) that applies whatever unlikely prop name you want under the hood to be used by createElement.
#91 was what I was thinking of with my earlier suggestion.

This is live in 2.17.16, give it a spin and tell me how it feels and whether you like it?

It's working great! Used the css prop on a number of 3rd party components and the className got passed through just fine! Inline styles nirvana :-D
Thanks!!!


Implement splashscreen

To get some inspiration: https://github.com/nextcloud/android/pull/2448/files :)

close in favour of https://gitlab.com/derSchabi/OCBookmarks/issues/19


default shell not launching

Thanks for the great package.
A blank screen appears instead of prompt. I could see a cursor blinking at the maximum. Please help.

Same with me

Unable to start terminal process. Win32 error code: 267 Error: Unable to start terminal process. Win32 error code: 267
at Error (native)
at Server. (C:\Users\SDS.atom\packages\platformio-ide-terminal\node_modules\pty.js\lib\pty_win.js:67:9)
at emitOne (events.js:77:13)
at Server.emit (events.js:169:7)
at Pipe.onconnection (net.js:1430:8)

Upgrade nan to the latest version.
Solution: https://github.com/tensor5/arch-atom/issues/12#issuecomment-223909881


Q: Will using the "core" target change chroot default from X to Wayland?

I did some poking around to see what core did, and I saw it depends on host-wayland.
I may be crazily stupid, but will it change the chroot default from X to Wayland?

@SaikoHaven,
Short answer: No
Longer answer:
I'm not sure 'depends on' is the right term, core does install both host-dbus & host-wayland in the chroot-bin folder but host-wayland is not necessarily employed.
Both brightness and croutonpowerd along with freon do require and employ host-dbus.
Also, both the xorg & xiwi xmethods require the core target so if you install any desktop you'll be getting and using core.
If you're interested in running the wayland server check out the below links:

Wayland Notes
Running Wayland compositors using ChromeOS's Wayland server?

Hope this helps,
-DennisLfromGA

core is needed for e17 as far as I know.

Closing. Please re-open if this issue is still a concern.


Support admin code override disable_for_time field

Adds support for the disable_for_time field for the admin override feature

Relies on a cloudflare-go PR

acceptance tests look good
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareTeamsAccounts_" -count 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareTeamsAccounts_ConfigurationBasic
--- PASS: TestAccCloudflareTeamsAccounts_ConfigurationBasic (6.89s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	7.916s

@ajholland are you able to look at fixing the access application changes in v0.102.0 that are breaking CI here?


doc: fix the messed up markdown of 06-lark-connector

Kindly refer to the standard title format used in other PRs.

Do I need to create an issue for it?

@LinuxSuRen A corresponding issue for a PR will be good~


Update LOCALIZATION_CONTRIBUTORS

Summary
Details and comments

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

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

Thank you for your interest in contributing to Qiskit translations. Please go ahead and follow steps 4, 5 and 6 in the Contributing to Qiskit documentation.

Hi @imvieira, Please go ahead and follow steps 4, 5 and 6 in the Contributing to Qiskit documentation section.
This PR will be closed if we don't receive joining request in CrowdIn.


aya: Raise the warning when RMILIT_MEMLOCK is not RLIM_INFINITY

Kernels before 5.11 don't use cgroup accounting, so they might reach the
RLIMIT_MEMLOCK when creating maps. After this change, we raise a warning
recommending to raise the RLIMIT_MEMLOCK.

Imho it would be nice to have a helper to query for this condition so you can do this in your code
if (check_rlimit())
  setrlimit()


Installation error when installing Trident plug-in in Private registry environment

[Problem]

Occurred Installation error when installing Trident plug-in in Private registry environment.
The environment being installed by the customer is a Private environment that is not Internet-enabled.
So, we suggested an offline installation way as below.
The Private registry of the trident installation video is an un-authentication basis, but the customer's Private registry is a Authentication base.

[Providing guides]
•             follow below youtube link offline install trident，after pulling two docker image (netapp/trident:18.10.0, quay.io/coreos/etcd:v3.2.19) to local repository then install with below command.
•             e) # ./tridentctl install -n trident --trident-image tacorepo:5000/netapp/trident:18.10.0 --etcd-image tacorepo:5000/quay.io/coreos/etcd:v3.2.19 -d
•             https://www.youtube.com/watch?v=_T3_JntptKA
[Customer Action#1]
•             follow below install guide while generate error。
o             https://netapp.io/2018/12/19/installing-trident-from-a-private-registry/
•             follow above URL link but failed during generate POD。
•             1) after run install command  - stuck in Waiting for Trident installer pod to start. then generate error
•             [root@k8s-master trident-installer]# ./tridentctl install -n trident --trident-image sds.redii.net/jamessc-cho/trident:18.10.0 --etcd-image sds.redii.net/jamessc-cho/etcd:v3.3.9
INFO Created namespace.                            namespace=trident
INFO Created installer service account.            serviceaccount=trident-installer
INFO Created installer cluster role.               clusterrole=trident-installer
INFO Created installer cluster role binding.       clusterrolebinding=trident-installer
INFO Created installer configmap.                  configmap=trident-installer
INFO Created installer pod.                        pod=trident-installer
INFO Waiting for Trident installer pod to start.
ERRO Trident installer pod was not started after 180.00 seconds. Pod status is Pending. Use 'kubectl describe pod trident-installer -n trident' for more information.
INFO Deleted installer cluster role binding.
INFO Deleted installer cluster role.
INFO Deleted installer service account.
FATA Install failed; pod not yet started (Pending).  Resolve the issue; use 'tridentctl uninstall' to clean up; and try again.
•
•             2) Pod state is ImagePullBackOff
[root@k8s-master ~]# kubectl get pod -n trident -owide
NAME                READY   STATUS             RESTARTS   AGE   IP           NODE          NOMINATED NODE
trident-installer   0/1     ImagePullBackOff   0          10m   <IP_ADDRESS>   k8s-worker1
•             3) when check POD event can found error “no basic auth credentials”
•             [root@k8s-master ~]# kubectl describe pod trident-installer -n trident
•             (.... skip ....)
•             Events:
Type     Reason     Age                   From                  Message

Normal   Scheduled  10m                   default-scheduler     Successfully assigned trident/trident-installer to k8s-worker1
Normal   Pulling    8m43s (x4 over 10m)   kubelet, k8s-worker1  pulling image "sds.redii.net/jamessc-cho/trident:18.10.0"
Warning  Failed     8m43s (x4 over 10m)   kubelet, k8s-worker1  Failed to pull image "sds.redii.net/jamessc-cho/trident:18.10.0": rpc error: code = Unknown desc = Error response from daemon: Gethttps://sds.redii.net/v2/jamessc-cho/trident/manifests/18.10.0: no basic auth credentials
Warning  Failed     8m43s (x4 over 10m)   kubelet, k8s-worker1  Error: ErrImagePull
Normal   BackOff    8m19s (x6 over 10m)   kubelet, k8s-worker1  Back-off pulling image "sds.redii.net/jamessc-cho/trident:18.10.0"
Warning  Failed     4m59s (x20 over 10m)  kubelet, k8s-worker1  Error: ImagePullBackOff
[Customer Action #2]
•             Attached YAML file that is used by customer during installation (The YAML file is to pull the image to create the POD in customer’s Private Registry environment)
•             follow below link install trident with YAML file, URL “4. Install Trident – Customized Installation”
o             https://netapp-trident.readthedocs.io/en/stable-v19.01/kubernetes/troubleshooting.html#troubleshooting
Step1: --generate-custom-yaml option generate yaml file then below yaml file will generate.
•             [root@k8s-master ~]# ll /tmp/trident-installer/setup/
합계 28
-rwxrwxrwx 1 1001 1001  206 10월 23 06:01 backend.json
-rwxrwxrwx 1 root root  728  2월 20 02:59 trident-clusterrole.yaml
-rwxrwxrwx 1 root root  255  2월 20 02:59 trident-clusterrolebinding.yaml
-rwxrwxrwx 1 root root 1926  2월 20 04:23 trident-deployment.yaml
-rwxrwxrwx 1 root root   61  2월 20 02:59 trident-namespace.yaml
-rwxrwxrwx 1 root root  297  2월 20 02:59 trident-pvc.yaml
-rwxrwxrwx 1 root root   66  2월 20 02:59 trident-serviceaccount.yaml
•             Step2: change trident-deployment.yaml file  which match private registry (attach yaml file)
•             what
trident-deployment.zip
have changed
imagePullSecrets:
- name: redii
image: sds.redii.net/jamessc-cho/trident:18.10.0
image: sds.redii.net/jamessc-cho/etcd:v3.3.9

hi  expert
same body help check above trident install issue?
thanks
frank

If the private registry requires login to pull then the customer will need to either login before running install (if the login is persistent) or they will need to manually pull the images to their local docker cache prior to running trident install

@adkerr
Thank you for your reply. The following is my customer's feedback for your comment.
Pre-login is a possible way in a docker. In k8s, login authentication information is managed as "imagePulseSecret" and dynamically transmits this information to the docker when running the pod, so even if it is docker login, it ignores it.
And when install with trident CLI, imagePulpolicy value has been "Always". So even if push the image in advance in LOCAL, always check the remote registry, so authentication errors will also occur.
My customer thinks this issue as below.
First of all, all of the above issues were the problems when filled out a specific image address with the CLI parameter as follows.
#> ./tridentl install -n trident --trident-image xxx --etcd-image xxxx
If I can run with custom yaml, I can modify all the problematic parts and reflect them, so it will be solved if you guide the correct way to run with custom yaml.
Thanks
Hendrick

This document goes into the customized installation options available:
https://netapp-trident.readthedocs.io/en/stable-v19.01/kubernetes/deploying.html#customized-installation
Use tridentctl's --generate-custom-yaml option to create the YAML files.  Edit them, then use tridentctl's  --use-custom-yaml option to install a customized version of Trident.
$ ./tridentctl install -n trident --generate-custom-yaml
INFO Wrote installation YAML files.                setupPath=/tmp/trident-installer/setup
$ vi /tmp/trident-installer/setup/trident-deployment.yaml
$ ./tridentctl install -n trident --use-custom-yaml

Occured error as below.

Create to generate-custom-yaml
root@master:/root/trident-installer$ ./tridentctl install -n trident --generate-custom-yaml
INFO Wrote installation YAML files.                setupPath=/root/trident-installer/setup

change to "private image" in custom-yaml
root@master:/root/trident-installer$ cat /root/trident-installer/setup/trident-deployment.yaml | grep image:
image: sds.redii.net/sdspaas/trident:19.01.0
image: sds.redii.net/sdspaas/etcd:v3.3.10

install with custom-yaml (failed)
root@master:/root/trident-installer$ ./tridentctl install -n trident --use-custom-yaml
INFO Created namespace.                            path=/root/trident-installer/setup/trident-namespace.yaml
INFO Created installer service account.            serviceaccount=trident-installer
INFO Waiting for object to be created.             objectName=clusterRole
INFO Created installer cluster role.               clusterrole=trident-installer
INFO Waiting for object to be created.             objectName=clusterRoleBinding
INFO Created installer cluster role binding.       clusterrolebinding=trident-installer
INFO Created installer configmap.                  configmap=trident-installer
INFO Waiting for object to be created.             objectName=installerPod
INFO Created installer pod.                        pod=trident-installer
INFO Waiting for Trident installer pod to start.
ERRO Trident installer pod was not started after 180.00 seconds. Pod status is Pending. Use 'kubectl describe pod trident-installer -n trident' for more information.

Inquiry Trident Pod (did not change as "private image")
root@master:/root/trident-installer$ kubectl get po -n trident
NAME                READY   STATUS         RESTARTS   AGE
trident-installer   0/1     ErrImagePull   0          2m10s
root@master:/root/trident-installer$ kubectl get po -n trident trident-installer -oyaml | grep image:
image: netapp/trident:19.01.0

image: netapp/trident:19.01.0
root@master:/root/trident-installer$ kubectl describe po trident-installer -n trident
Events:
Type     Reason     Age    From               Message

Normal   Scheduled  3m56s  default-scheduler  Successfully assigned trident/trident-installer to node2
Normal   Pulling    3m55s  kubelet, node2     pulling image "netapp/trident:19.01.0"
Warning  Failed     3m40s  kubelet, node2     Failed to pull image "netapp/trident:19.01.0": rpc error: code = Unknown desc = Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Warning  Failed     3m40s  kubelet, node2     Error: ErrImagePull

@iamhyuk Changing the image in trident-deployment.yaml doesn't change the image for the containerized installer and that's the problem you're hitting. However, using  ./tridentl install -n trident --trident-image xxx --etcd-image xxxx changes both Trident deployment image and the containerized installer image.
@clintonk, is there a way to customize the containerized installer without changing the source code?

Trident's custom installation method (--generate-custom-yaml and --use-custom-yaml) should work in this case.  All of the custom YAML files are passed into the containerized installer in a configmap.  But passing the image names to the installer should work equally well.

@clintonk The problem is changing the image in trident-deployment.yaml has no impact on the image used by the containerized installer itself unless --trident-image is used: https://github.com/NetApp/trident/blob/459b11dc2598c39ce7b08d4e122151a46d124a11/cli/cmd/install.go#L1649.
It seems you have to customize the yamls AND specify the command line option.

@kangarlou Good point, you're correct about that.  Trident and its installer use the very same image, but one must invoke the installer with --trident-image which serves both purposes.

@clintonk They would like to use the "--use-custom-yaml" to pass on the ImagePullSecret. So do you think if they use the customized yaml file and the "--trident-image" command line , the install should go through successfully?

@jacobjohnanda I don't see why not.

@jacobjohnanda I don't see why not.

NAME                READY   STATUS   RESTARTS   AGE
trident-installer   0/1     Error    0          7s
Error: unknown flag: --trident-image
This is in a cluster that cannot access the internet, and needs to pull images from a priv repo that requires login.  The command I used to get this error is ./tridentctl install -n trident --use-custom-yaml --trident-image /pub/netapp/trident:19.01.0 --etcd-image /pub/netapp/etcd:v3.3.12
Normally, the repo requires an imagepullsecret. But, they dont seem to work with the "installer".  I get the error "repository does not exist or may require 'docker login'"
I've tried having a yaml file in the setup dir with the username/pw as base64 and I have created the secret in the namespace and added it to the serviceaccount yaml in the setup dir. Neither of these work.
Before that, I tried caching the images on each of my workers and some other tagging trickery, but the "installer" kept trying to reach out to docker.io
Specifying the tridnet and etcd images seems like its the right work around for all of this. Can you elaborate on what unknown flag: --trident-image means, and how to get around?

I am just guessing "netapp/trident:19.01.0" format is causing the build to be pulled from docker.io. Could try the format :/trident:19.01.0 .

Sorry, I had removed the domain names for the purpose of posting here. I am using the full url.  I was able to get this installed this after doing a couple things. First was going back to 18.10. I modified the 19.01 image so that I could exec in there and see what the hang was.  I looks like the tridentctl binary does not have the flags that the 18.10 binary had.  Specifically, 19.01 is missing --trident-image and --etcd-image.
Next is security stuff related to my cluster. I noticed the installer and the actual trident container have their own labels. So, I needed a selector for each in my network policies.  Then I had to put the images in a non-password protected area of my repo.

I did give a try and I was able to install using the --trident-image with Trident 19.01 installer.


Created Seperate Blog Page

Related Issue
#463
Description
Created separate blog page.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

The page looks good. Bring the heading AgroBlogs to the centre and remove that add blogs.Also as a separate page is made for blogs so remove the blog section from the main page that is after the about section resource library should come.

For now i have reverted back your PR.

Once this PR is merged add your own blogs under the other issue which you raised. You will get level tags for both the issues separately.

And please add a video each time you a raise a PR with changes as this avoids the reverting back of PR.


Docs: clarify the source of the issuer extensions

Description
Fulcio's oid-info.md documentation includes docs for two extensions that reference the underlying identity's "issuer":

<IP_ADDRESS>.4.1.57264.1.1 | Issuer
This contains the iss claim from the OIDC Identity Token that was presented at the time the code signing certificate was requested to be created. This claim is the URI of the OIDC Identity Provider that digitally signed the identity token. For example: https://oidc-issuer.com.

and:

<IP_ADDRESS>.4.1.57264.1.8 | Issuer (V2)
This contains the iss claim from the OIDC Identity Token that was presented at the time the code signing certificate was requested to be created. This claim is the URI of the OIDC Identity Provider that digitally signed the identity token. For example: https://oidc-issuer.com.

The difference between this extension and <IP_ADDRESS>.4.1.57264.1.1 is that the extension value is formatted to the RFC 5280 specification as a DER-encoded string.

When using a "directly" issued OIDC token, this documentation is correct: the iss claim is what appears in each extension.
However, when using a "federated" IdP like Sigstore's own Dex instances, the iss claim does not appear in these extensions: instead, the value of federated_claims.connector_id appears, which is the value of the underlying IdP's iss claim.
This is arguably an implementation detail, but IMO an important one: clients who obtain an identity token than represents them have a reasonable expectation around being able to inspect that identity token and confirm its claims, and accuracy w/r/t how that token is interpreted will help clients make better use of the Sigstore ecosystem.
CC @jku as well, since his use case is affected by this 🙂
See https://github.com/sigstore/sigstore-python/pull/635#discussion_r1183968532.

CC @haydentherapper @znewman01

A simple change could be changing "iss claim" to "OpenID Connect provider" or something similar. The use of federated claims is an implementation detail in my opinion. A user who does need to inspect the token would need to understand Dex though, so it's an open question if a client MUST understand this. I'd lean towards no, unless we say that verification of the token before use is a hard requirement.

That works for me in terms of clarifying the origin, but I wonder where it leaves uses who want to understand the provenance steps between "identity token that represents them" and "certificate bound to their identity" (which I believe is @jku's use case).
I don't think verifying the token before use should be a hard requirement, but I do think there's a valid "sanity checking" use case, which is one we've seen crop up with the Python release managers: they've signed for official Python releases with the wrong identity or issuer a few times now, and we have no way to tell them that or fail before it happens because of the opacity of the identity tokens themselves.

I don't think a client can know everything, and should depend on a user knowing they're using a federated identity provider and specify where to look for the issuer (maybe have 'iss' be the default)

I might be misunderstanding, but doesn't this produce the same ambiguity? End users might not be super technical (or might be technical, but not familiar with OIDC and federation), so "your Google identity" versus "your Google identity, federated through Sigstore's Dex instance" might be difficult to express to them (especially when they're going "through" Sigstore no matter what).
Similarly, without guidance about which federated issuer actually lives at https://oauth2.sigstore.dev/auth, I'm not sure the clients can provide useful information here on their own: it'd be incorrect (currently) to assume that that issuer will remain Dex, right?

In terms of Fulcio, particularly the public instance, I don't think we should expose the difference between federated and non-federated identity - There is trust in Dex, albeit it's still auditable due to certificate transparency. Though it's worth considering if a private instance would want to make a different decision and distinguish between the two. I'd argue no because of transparency and probably because the private provider is run within the same trust domain as the private Fulcio instance.
As for the client, my comment was more about that there are many mappings between claims to certificate extensions. Do we want a client to have that mapping? For example, if you want to verify CI claims are present in an extension, you need to know the mapping between claim per CI platform and extension. Though it's a well defined mapping, so there's no technical reason why you couldn't.
Correct, I don't think a client should always assume Dex. My comment was that it's not known which fields will contain the issuer, so you need to rely on the user to specify them. Or you could simply assume it's either 'iss' or when 'iss'= https://oauth2.sigstore.dev/auth, then it's the federated claim.

so just to be sure: "client" here refers to a sigstore client library/CLI? And user refers to a human user or an application using the sigstore client library?

Correct. The user is the entity that will know which claims are relevant for verification. So more accurately, the user is the verification policy.

I shouldn't have to understand dex or federated_claims or connector_ids, I should be able to verify that signer identity that will be used in the signing certificate is ABC with issuer XYZ.

I agree that a user shouldn't have to know anything about Dex. If not the user, then the client must. This comes back to a conversation we've had for Cosign, separating the public good instance workflow from private workflows. I think it's fine if the client by default handles the case of using the Sigstore Dex instance, knowing that the issuer comes from a different field.

I agree that a user shouldn't have to know anything about Dex. If not the user, then the client must. This comes back to a conversation we've had for Cosign, separating the public good instance workflow from private workflows. I think it's fine if the client by default handles the case of using the Sigstore Dex instance, knowing that the issuer comes from a different field.

I think that resolves the issue on the sigstore-python side as well! Thanks @haydentherapper!
I'll also open a PR for the Fulcio docs with the change suggested in https://github.com/sigstore/fulcio/issues/1145#issuecomment-1533691566 in a bit.

#1158 includes the doc changes: I've removed the language implying that iss is always the issuer extension value, and replaced it with a more narrow claim about non-federated tokens.


ScanPolarity to wizard and to raw data overview as quick control

Done from my side.
One more thing for another PR would be how to tell people that chromatogram building on both polarities does not work

Done from my side. One more thing for another PR would be how to tell people that chromatogram building on both polarities does not work

We can validate the parameters before triggering the task and show a message box if polarity "ANY" was chosen for polarity switching data. The message should also point the user to polarity scan filter option

Not sure its usually multiple tasks running in parallel - so we would need to have a mechanism to only show one dialog.
Also I would say the dialog should not block the processing but just show up.
I will create a new issue for this.
#1846

All done


Update navbar-22.html

Here is the component I have built.
Here is a screenshot of that.

Just need to change the button on the right use a secondary icon button form the buttons component for that. @nik132-eng

Great work @nik132-eng
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow these steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/)
Go to the profile section from the top right-hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.
That’s it. Follow the leaderboard!
And don’t forget to share your achievement with your friends.


Silent error if children isn't an array.

Hi, awesome package.  Thanks!
Hey, I ran into a sticky error that might cause others issues.  I had children: {...}, but the children weren't getting to the client.  children: [{...}] worked.
Cheers!
Mike

We should probably just run prepareOptions on options.children as well as options

Added a check on all options fields


Update io_uring-udp.c

bug #814
https://github.com/axboe/liburing/issues/814

git request-pull output:
<!-- START REPLACE ME -->

Generate your PR shortlog and diffstat with these commands:
   git remote add axboe-tree https://github.com/axboe/liburing
   git fetch axboe-tree
   git request-pull axboe-tree/master your_fork_URL your_branch_name

Then replace this with the output of `git request-pull` command.

<!-- END REPLACE ME -->

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

Fix looks good (with cosmetic adjustment suggested), but your commit message should be better. First of all, the first line should be a title for the commit. "Update foo.c" doesn't mean anything, what is being changed here? And then the body should have an explanation of why the change is necessary. Finally, a Signed-off-by line is required with your identity (name) and email as well.
See the other commits in the repo for an example of what a commit message should look like. Here's one from Pavel:
https://git.kernel.dk/cgit/liburing/commit/?id=f1af5ff51a3320a8971c611368c693c1dec560c5

Don't add a new commit to fix your previous unmerged commit. Just fold
it in, then force-push. It's fine to force push to your branch.
Also, as previously has been told, use a Signed-off-by with a real name
and email.

I'll send a patch.


Add missing USE_GEMM3M macro into CMake

Adding USE_GEMM3M macro into CMake kernel targets, so that the *gemm3m functions and parameters can be included into the gotoblas structure. Fixes #4500

Oh right, thanks. That's almost as bad as way back when the CMAKE build did not know about USE_TRMM


Incorrect transformer mask size

Describe the bug
PyTorch multi_head_attention code enforces that data size and mask size matches.
https://github.com/pytorch/pytorch/blob/df4e3d9d08f3d5d5439c3626be4bf29659488cdf/torch/nn/functional.py#L5442-L5444
However, speechbrain code generates masks according to the longest wav_len, which can be shorter than the batch size with padding, resulting in the exception given in the codeblock above.
https://github.com/speechbrain/speechbrain/blob/f6e297e65e266b5b1b8dbbfbf9d60520db9cfd88/speechbrain/lobes/models/transformer/TransformerASR.py#L146
Solution:
The function length_to_mask accepts an optional argument max_len, this could be used. Should I open a PR?
https://github.com/speechbrain/speechbrain/blob/f6e297e65e266b5b1b8dbbfbf9d60520db9cfd88/speechbrain/dataio/dataio.py#L758-L772
Expected behaviour
The mask should have been generated according to what PyTorch anticipates. Instead, an exception is thrown.
To Reproduce
No response
Environment Details
speechbrain==0.5.16  (checking the develop branch this still seem to be an issue)
pytorch==2.1.1

Relevant Log Output
No response
Additional Context
No response

Hello @egaznep, thanks for opening this issue!
Could you please have a look @TParcollet? Thanks :)

Hello @egaznep I am not sure to understand the issue here. Could you provide a code snippet showing explicitly the error? The function length_to_mask() is expected to provide masks containing padding i.e. real size of the input tensor, and this for each sequence. Could you detail a bit more what you are trying to achieve?

Here is a minimal working (or in this case crashing) example:
import torch
import torch.nn as nn
from speechbrain.lobes.models.transformer.TransformerASR import TransformerASR
import random

# Instantiate the TransformerASR model
model = TransformerASR(
    tgt_vocab=720,
    input_size=80,
    d_model=512,
    nhead=1,
    num_encoder_layers=1,
    num_decoder_layers=1,
)

# Generate some dummy input with different lengths
input_lengths = torch.tensor([l for l in range(10,101,10)])
input_data = [torch.randn(length,80) for length in input_lengths]
input_targets = [torch.randint(low=0, high=720, size=(length.item(),)) for length in input_lengths]
# Pad the input sequences to have the same length
input_data = nn.utils.rnn.pad_sequence(input_data, batch_first=True)
input_targets = nn.utils.rnn.pad_sequence(input_targets, batch_first=True)
input_lengths = input_lengths/100.0

print(input_data.shape, input_targets.shape, input_lengths.shape)

output = model.forward(input_data, input_targets, wav_len=input_lengths) # works
output = model.forward(input_data[:-1], input_targets[:-1], wav_len=input_lengths[:-1]) # fails

First call to the model.forward in line 29 has the following wav_lens: 10, 20, ..., 100, thus all are padded to 100. The mask computation will not fail because it can infer the proper mask size.
Second call to the model.forward in line 30, however, has the following wav_lens: 10, 20, ..., 90, even though all are padded to 100 because that is the longest in the entire dataset. The mask computation will fail because mask generator does not check how long the padded sequences are, but simply the largest wav_lens are.

Hello thanks. SpeechBrain padding is relative to the batch, not the dataset. The max len of wav_lens is the max len of the batch.

I had this error while training a model using DistributedDataParallel on 2 GPUs. Could it be that initial data sampler does the padding relative to the complete batch size, but then during distribution to individual GPUs the error I am facing occurs?

@Gastron correct me if I am wrong, but as far as I know, DDP sampler is per-process, hence the padding should be relative to that batch. @egaznep any chance that you could give us an example where this happens?

Hello @egaznep, any news on your side please ?


⚠ Bofrost.at has degraded performance

In 0ec6197, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1107 ms

Resolved: Bofrost.at performance has improved in cc46d3a.


python-rewrite: use black for code formatting

Currently it isn't clear what formatting should be used in the Python files. Since the CLI is now being rewritten to Python could help developers to know how the code should be formatted and format it automatically on pre-commit.

Needs a rebase

Needs a rebase

Done :+1:


Changes required for dotnet 6 upgrade

This PR is required for dotnet 6.0 upgrade for vs code to work properly.
This will be tested through and merged.
This can go after CLI PR https://github.com/Azure/Bridge-To-Kubernetes/pull/48 merged and released to production.

Can we update the change log file as well? We should add note there that going back to previous version will need manual action from user.


Missing Sanity Check for malloc() in catch.hpp

Missing Sanity Check for malloc() in catch.hpp
There appears to be a missing sanity check for malloc in directory
'src/catch', file 'catch.hpp' as the code segment below shows:
inline size_t registerTestMethods() {
    size_t noTestMethods = 0;
    int noClasses = objc_getClassList( CATCH_NULL, 0 );

    Class* classes = (CATCH_UNSAFE_UNRETAINED Class *)malloc( sizeof(Class) * noClasses);
    objc_getClassList( classes, noClasses );

What kind of a "sanity check"? All multiplications/length seem to be correct.
Well, using malloc() is a questionable matter in and of itself.

@nabijaczleweli malloc returning NULL.

Though this really should be classes = new Class[noClasses]...

This should be a smart pointer :v

@dogbert2 - you are technically correct (which is the best kind of correct). However I don't think it's a big deal here. This is called immediately on entering main() - and there's nothing you can do to recover from it. If you're out of memory for this call then the changes of something like iostreams working is pretty low too.
@kirbyfan64 and @nabijaczleweli bear in mind this is Objective-C code (well, technically it's C code in an Objective-C context, reflecting over Objective-C code). That memory handling needs to interact with ARC (Automatic Reference Counting) - and also stick around for the lifetime of the program since instances of the Class object are kept around. I'm sure it could be cleaned up but it's tricky stuff that's been "just working" for years now without any need to touch it.

I agree with Phil here, if things went wrong so soon, then there is nothing to do, except maybe explicitly exit.


Allow to opt-out of automatic msys2_mingw_dependency installation

Hi @jcupitt ,
as discussed in #331 (see comments), we have the need of more fine-grained control on the libvips library version to be used.
When you install the ruby-vips gem on Windows, it would automatically (and unconditionally) install the latest available libvips dependency to your msys2 ruby devkit environment (see here in ruby-vips.gemspec).
There is the %RUBY_DLL_PATH% environment variable which you can point to an external libvips installation (e.g. obtained from libvips/build-win64-mxe releases), but this only works when there is no libvips installation present in the msys2 ruby devkit environment.
So in order to make use of %RUBY_DLL_PATH% to get control of the libvips version being installed, you need to make sure that there is no parallel libvips installation in the msys2 ruby devkit environment. But here's the catch: every time you re-install or update the ruby-vips gem, you will get an msys2 libvips installation as a side effect, breaking the use of the external libvips version in %RUBY_DLL_PATH%.
One solution to this could be to provide a possibility to opt-out of the installation of "msys2_mingw_dependencies" in the gemspec (e.g. via an env var like SKIP_MSYS2_MINGW_DEPENDENCIES=1 or so).
What do you think? Does that sound feasible / sensible? Do you have other suggestions on how to enable better control over the libvips library version?
Cheers,
Torben

Hi again,
Yes, this is a tricky one.
Another possibility would be to add some code to ruby-vips here:
https://github.com/libvips/ruby-vips/blob/master/lib/vips.rb#L13-L34
It could check for an env var called VIPSHOME and prepend that to the library name, perhaps:
def library_name(name, abi_number)
  lib = ''

  if ENV.has_key? 'VIPSHOME'
    lib += "#{ENV['VIPSHOME']}/lib/"
  end

  if FFI::Platform.windows?
    lib += "lib#{name}-#{abi_number}.dll"
  elsif FFI::Platform.mac?
    lib += "#{name}.#{abi_number}"
  else
    lib += "#{name}.so.#{abi_number}"
  end

  lib
end

Though some platforms use lib64 or lib/x86_64-linux-gnu/ which is annoying.

That sounds even better! 👍🏻

because having a dedicated VIPSHOME env var makes it a first-class feature of "ruby-vips" (vs RUBY_DLL_PATH which is a feature of RubyInstaller which is quirky and not under our control, and also works for Windows only)
because that would then work cross-platform (i.e. can be used on Linux, Windows, MacOS in the same way), does it?

If I get (or rather guess) it right on how ffi works, by explicitly loading the libraries from VIPSHOME via ffi_lib if present, there is no chance this might interfere with an additionally installed libvips in msys2 / mingw, right?

I'm honestly not sure :( We'd need to do some testing. Perhaps opening libvips-42.dll in c:\libvips-8.12.4\bin would load dependencies like libopenslide.dll from the mingw area by mistake? That could cause horrible crashes.
Thinking about it some more, really the best thing would be to fix the pacman package. Maybe open a bug report here?
https://github.com/msys2/MINGW-packages/issues?q=is%3Aissue+is%3Aopen+libvips

It seems that RubyInstaller honors the --ignore-dependencies option of gem:
https://github.com/oneclick/rubyinstaller2/blob/ee44ad03f22cedfccb368f33dc9081daa84d0d81/resources/files/operating_system.rb#L8
So, to avoid installing libvips from MSYS2, you can just do:
$ gem install ruby-vips ffi --ignore-dependencies

FWIW, I tried to debug that crash with GDB using the mingw-w64-ucrt-x86_64-gdb package, but without debug symbols it's difficult to debug that further.

Hi @jcupitt , thanks for the link to the MINGW-packages repo, I didn't know where to report this 👍🏻  but yes, fixing the pacman package would help for #331 (the crash), but not for #332 (how to control libvips version) though...
For sure, I can support with testing the VIPSHOME approach sketched above, also checking if it accidentally picks up libraries from the wrong location or not. Is the snippet from above all there is to it, or are there more places that would need to be adapted? (e.g. does ruby-vips exclusively use the libraries, or does it expect the correct vips.exe on the PATH or so?). If you want, I can also create a PR for that to start with.
@kleisauke yes, thanks for the hint regarding --ignore-dependencies. I found that too while trying to trick around it, but usually we freeze + install our gem dependencies via bundler, and there this approach won't work :-/

Yes, that's the only thing you'd need to change (I think!). But messing with paths and library resolution is extremely fragile and we're likely to trigger a lot of difficult to debug crashes.
I was thinking about this again -- I now think your original idea was right and we should have an env var like  RUBYVIPS_EXTERNAL_LIBVIPS to turn off msys2_mingw_dependencies.
Perhaps (untested):
    "msys2_mingw_dependencies" => ENV.key?("RUBYVIPS_EXTERNAL_LIBVIPS") ? "" : "libvips"

So to use an external libvips you'd need to set RUBYVIPS_EXTERNAL_LIBVIPS to stop installation of the msys one, and set RUBY_DLL_PATH to include your external libvips bin area.
Any thoughts?

I came across this interesting article from a few years ago:
https://bibwild.wordpress.com/2015/09/09/optional-gem-dependencies/
Which (I think) advocates removing optional dependencies and checking at runtime instead, perhaps with a helpful message.
@jrochkind sorry to ping you, but I wonder if you have any insights on this issue?

You can ping me anytime @jcupitt, I love vips and appreciate and am impressed your work!  (Although I am a rubyist and use vips, I don't currently use ruby-vips -- my code calls out to a shell calling command line vips currently!)
There is no way to "opt out" of something in a ruby gemspec at runtime -- any conditional logic in the gemspec will be applied at gem build time, not at individual installation runtime. So definitely don't try that -- either something is in a gemspec or is not, there's no way to make it conditional.
I don't develop or run ruby on Windows though, so don't totally understand the windows-specific issues.  Looking at the current ruby-vips gemspec... I see in gem metadata, the key/value "msys2_mingw_dependencies" => "libvips" -- I have never seen this before, from the discussion here it sounds like you can express windows OS-level dependencies in gem metadata, that are actually enforced at gem install time?  I am not familiar with this feature at all!  So it's hard for me to judge the pros/cons of different ways of doing things.
With ordinary ruby gemspec depdencies -- which this is not -- there are definitely pro's and con's of making an optional dependency only checked at runtime. Mainly the downside is that you are no making available ordinary ruby dependency features to do things like automatically install all dependencies at installation time, or compute the latest version(s) of all dependencies that are mutually satisfactory to each other.  But if including the dependency in the ordinary way causes problems for some users -- whose usage isn't going to require the dependency at all, but where having it causes them problems (generally either long installation time/sizes, or conflicts with their desired dependency tree) -- it's kind of the only option.
If you do have an "optional dependency" which is only enforced at runtime -- I think it's important for the runtime checking to be very robust and the error message very clear, including (when it comes to rubygems) expressing and reporting the range of versions of the optional dependency that would be acceptable. (Rails' own runtime optional checking is not as good as it could be here when it comes to reporting).
That's my thinking on ordinary ruby gemspec dependencies. But this msys2_mingw_dependency is not that -- it's a windows feature I didn't even realize existed!  (In non-Windows OSs, ruby gems generally have no formal way to express non-ruby-gem OS-level dependencies at all, as far as I know!).  So I'm not totally sure how it applies here.

Hi! Thanks for the feedback.
It sounds like the best thing is to remove msys2_mingw_dependencies (as you guessed, it's way for windows ruby users to install gems with binary components, which otherwise can be extremely difficult) and display the best error message we can instead.
Presumably a try / catch around the first ffi import, maybe here:
https://github.com/libvips/ruby-vips/blob/master/lib/vips.rb#L45
Does anyone fancy taking a stab at a prototype PR?

Although I am a rubyist and use vips, I don't currently use ruby-vips -- my code calls out to a shell calling command line vips currently!

Oh, interesting. Do you use rails? Does ActiveRecord not fit your use case well?

Oh, interesting. Do you use rails? Does ActiveRecord not fit your use case well?

I do use rails. I think maybe you're asking about "ActiveStorage"?  It's true I don't use ActiveStorage, I do my own file handling and transformation with shrine.  I could still use the image_processing gem that ActiveStorage uses (which is actually by janko, the same author as shrine) -- but I don't. Partially because some of this code pre-dates ActiveStorage/ImageProcessing, partially because file handling is central to my app and I just want complete control, including of things that may or may not be available via ImageProcessing.
I definitely could still use ruby-vips but... I just don't? I just felt more comfortable not relying on anything but the command line, and not having to worry about any possible concurrency or ruby memory bugs.

which otherwise can be extremely difficult

I now worry your proposal would make things "extremely difficult" for the common case, for the benefit of making something more convenient that's an edge case.
But I don't use ruby on Windows, I don't fully understand the case here (as far as I know, on non-windows there isn't even a facility to formally express non-ruby dependencies like this!), so I'll stay out of any further discussion!

Ah! I had an idea!
How about removing the mingw dependency from ruby-vips, and making a tiny new gem called ruby-vips-windows (or maybe ruby-vips-mingw? something like that?) which depends on ruby-vips, and which has the mingw dependency.
Now windows users who want the mingw binary can put ruby-vips-mingw in their gemspec, and everyone else can use plain ruby-vips.
I suppose the downside is that the ruby-vips-mingw version numbers will need to exactly match the ruby-vips ones so people can still pin etc. Can we have two gems in one repo and generate the second programmatically?

Hmmm yes that's true.
I was imagining downstream projects would continue to just have just ruby-vips as a dependency, and then at the final step anyone deploying on windows would add ruby-vips-mingw to their gemspec. But that's not really any better than asking people to use pacman to install libvips if they are running on windows.
I'm now thinking this is unfixable. You can't safely mix the official libvips binaries with a mingw install (DLLs could crash into each other). If you want to use ruby-vips on windows with the libvips binaries, you really need to manage the whole binary stack yourself.
Let's just fix the pacman libvips. It needs fixing anyway, and that'll resolve most of these immediate issues.

I meant to add:

I don't have spare time to fix the pacman libvips myself, I should have said, sorry. I'd be very happy to help if I can, of course.

@jrochkind, you asked about this whole mingw thing.
My understanding is that it's rather like anaconda in the python world. Ruby (and python) gems with binary components (like ruby-vips, which needs ruby-ffi as well as a libvips binary) work by including C (usually) source code and building on the target platform as part of the install process. However, Windows is designed around binary distribution and, out of the box, is missing many of the necessary build tools.
Anaconda and rubyinstaller (the leading ruby package for windows) work around this by including an entire *nix-style environment and custom package manager as part of the base install and building (or downloading) all binary packages in that. They have a complete stack, all the way down to just above libc.
The msys2_mingw_dependencies that's causing the pain here makes bundler on windows install the libvips binary using the msys2 package manager (pacman). This is not the libvips binary we make, it's one built by the people who run msys2. It's an older version built with different flags and with different dependencies.
We can't safely drop our binary in there. Really we need something that's built against the other libraries in pacman, and that means fixing the pacman libvips is probably the only realistic solution.
Anaconda has the same problem: they have their own package manager and their own libvips binary and you can't mix them up.

Interesting, thanks for the background.
In other OS, with some gems you responsible for installing your own C or other binary components, usually with a package manager. The most you will get from the gem is a nice warning message telling you you need to install it if it isn't present (and more often a cryptic warning message).  Or in some cases on other OSs with ruby, the gem will install the a binary library itself at install time (the message you see at gem install time when this happens is  Building native extensions.  This could take a while...).
So rubygems on Windows, though, unique to rubygems on Windows, has a mechanism to trigger automatic install of binary dependencies from an external package manager. By listing something in the gemspec metadata -- which I can't think of anything else in metadata that has an actual automatic effect on gem install or run, all the rest of them are either just description, or in some cases possibly have an effect on rubygems.org hosting at release-time.
I'm not sure what aspect of Windows makes this more desirable such that they've rigged up this windows-ony feature -- maybe that it's harder to supply your own binary library with the gem on Windows, as is sometimes done on other OSs?  Or it's just harder to install binary libraries yourself on Windows in general, in a linkable way?
Some other gems use OS-provided binaries instead; if the latest standard package-manager-supplied binary library on another OS had problems with it, that would probably cause problems in that non-Windows situation too.  They rely on the the package-manager-supplied binary library building -- or if it doesn't they have the option of supplying/compiling the binary library themselves at gem install time, which is an option not present or less feasible on Windows.

... I made a PR to update the libvips version: https://github.com/msys2/MINGW-packages/pull/11078
It seems to build OK, but I've not tested to see if it fixes the bug you were seeing, I wasn't sure how to make a ucrt package.

I think my current thinking is that we can't safely mix binaries between the libvips win builds we make and the win builds made by the msys team. Many of the DLLs will clash and it's very likely to cause mysterious crashes. I'm often wrong though, so if I'm mixed up there, please do correct me!
This means there's no safe way for people who use rubyinstaller to patch in a different libvips binary themselves. They must go via pacman and the msys toolchain. It's not actually that hard: you just make some edits to the PKGBUILD file and rerun it to make a new .pkg which you can drop in with pacman.
So I think that's probably the solution. You can stick with the libvips that ruby gives you automatically, or if you're determined, you can make your own package.
Hopefully the updated libvips will fix the original crash too, though I've not been able to test it yet.


Question: how to manage alembic autogenerate in multi-module project structure

Hi,
Thank you for your great work!
Something is unclear for me according to "FastAPI Best Practices" and this repo.
If this repository would have the same multi-module structure (src/auth/models.py, src/posts/models.py), the alembic will not see these models during the autogenerate, because we need import Base and all models we want to track somewhere in one place.
How do you handle this?
Is the alembic/env.py the best place to do these imports?
For example:
from src.models import Base  # noqa
from src.auth.models import User # noqa
from src.posts.models import Post # noqa

target_metadata = Base.metadata

I think explicit imports in env.py is not a bad idea, because we can control which models alembic will be tracking.
But what is the best practice?

Hi,
I think with SQLAlchemy ORM and a common base model, alembic is able to see the common metadata for all models that inherit from that class, so that's not a problem (at least when I was working with ORM a long time ago).
For the SQLAlchemy Core and db table definitions, I do a controversial, yet simple trick - put all Table schemas in one file - src.database - that way alembic is able to see changes. Then, each package's service just imports the table schema and works with it (you can see examples in the src.auth.service).
Putting all the table schemas in one file sounds smelly, but it worked for us and we didn't even notice it while having a medium-sized codebase with several dozens of tables (50-60 Table objects). DB tables didn't change frequently, but the services around them did.
Importing all the models in env.py sounds smart, but having an obligation to do it every time you add a new table feels like a burden to me.

Hey,
I did this script (in alembic/env.py), altough it's hacky it may help you.
for root, dirs, files in os.walk("src"):
    for file in files:
        if file == "models.py":
            path = os.path.join(root, file).replace(os.sep, ".")[:-3]
            module = __import__(path)


Frontend bugfix & Documentation update

Changed

Resolved an issue with the selection of parts toggle.
Fixed wrong urls in documentation

LGTM, you also extended the documentation. 👍


Facing "data.tls_certificate.this[0].certificates is empty list of object" in terraform plan command

╷
│ Error: Invalid index
│
│   on .terraform/modules/eks/main.tf line 211, in resource "aws_iam_openid_connect_provider" "oidc_provider":
│  211:   thumbprint_list = concat([data.tls_certificate.this[0].certificates[0].sha1_fingerprint], var.custom_oidc_thumbprints)
│     ├────────────────
│     │ data.tls_certificate.this[0].certificates is empty list of object
│
│ The given key does not identify an element in this collection value: the collection has no elements.
Above error is coming again and again. Previous day it was working but today it is continuously throwing above error.
Please reply if anyone has faced above error or knowing solution.
Thanks,
Jayesh

I am facing the same issue.

Same for me, a solution has been posted here: https://github.com/terraform-aws-modules/terraform-aws-eks/issues/2170#issuecomment-1191922960

temp fix https://github.com/terraform-aws-modules/terraform-aws-eks/issues/2170#issuecomment-1191922960

Thank you all of you guys,
Now it has been resolved from #2170.

This issue has been resolved in version 18.26.6 :tada:


AWS S3 TransferUtility for Unity

Currently (as of release v<IP_ADDRESS>), S3.TransferUtility is not yet supported in the Unity SDK. Is there any official plan to support this in Unity any time soon?
Here's one of the biggest benefit using TransferUtility:

When uploading large files by specifying file paths instead of a stream, TransferUtility uses multiple threads to upload multiple parts of a single upload at once. When dealing with large content sizes and high bandwidth, this can increase throughput significantly.

Which is definitely a handy feature to have for many file intensive use cases.

Unfortunately we don't have any immediate plans to support it.


Rootless Docker: Style edits and minor updates

Made some minor style edits to the Rootless Docker topic.
Related to https://github.com/docker/docker.github.io/pull/10965

Thanks!

thanks! wording looks good; left some suggestions (mostly related to wrapping, and one markdown issue)

Yea, I'm not why the 80 chars didnt persist. I've committed your suggestions. PTAL.


Convert HTML to Bokeh Buttons

Bokeh should manage the diagrams drawer button
Convert from vanilla HTML to using Bokeh widgets to control drawers.
Check list
Handy reminders of things to do ahead of merge

[ ] Bump version number to reflect change, edit forest/__init__.py
(Use semantic version x.y.z where x is major, y is feature, z is patch)

@twsearle the conversion from html tags to bokeh widgets paves the way for server-side logic to remove elements


whitelist_blacklist_tests.cpp:10:10: fatal error: 'deferred_test/deferred_test.wast.hpp' file not found

There is an issue when building docker image, the detail information as below, could EOS support fix this issue? seems like the unit test cause the fatal error.
[1329/1345] Building CXX object unittests/CMakeFiles/unit_test.dir/whitelist_blacklist_tests.cpp.o
FAILED: unittests/CMakeFiles/unit_test.dir/whitelist_blacklist_tests.cpp.o
/usr/bin/clang++   -Icontracts -I/eos/contracts -Iunittests/contracts -I/eos/unittests/contracts -I/eos/libraries/testing/include -Iunittests/tests/contracts -I/eos/unittests/wasm_tests -Iunittests/include -I/eos/libraries/chain/include -Ilibraries/chain/include -I/eos/libraries/chain/../wasm-jit/Include -I/eos/libraries/chain/../../externals/binaryen/src -I/eos/libraries/utilities/include -I/eos/libraries/utilities/../wasm-jit/Include -I/eos/libraries/fc/include -I/usr/local/include -I/usr/include/openssl/include -I/eos/libraries/fc/vendor/websocketpp -I/eos/libraries/chainbase/include -I/eos/libraries/wasm-jit/Source/Runtime/../../../chain/include -I/eos/libraries/softfloat/source/include -I/eos/libraries/softfloat/source/8086-SSE -I/eos/libraries/softfloat/build/Linux-x86_64-GCC -I/eos/libraries/builtins -I/eos/libraries/builtins../softfloat/source/include -Ilibraries/testing/include -I/eos/libraries/testing/../wasm-jit/Include -I/eos/libraries/abi_generator/include -I/usr/lib/llvm-4.0/include -Wall -Wno-invalid-partial-specialization -fcolor-diagnostics -O3 -DNDEBUG   -std=gnu++14 -MD -MT unittests/CMakeFiles/unit_test.dir/whitelist_blacklist_tests.cpp.o -MF unittests/CMakeFiles/unit_test.dir/whitelist_blacklist_tests.cpp.o.d -o unittests/CMakeFiles/unit_test.dir/whitelist_blacklist_tests.cpp.o -c /eos/unittests/whitelist_blacklist_tests.cpp
/eos/unittests/whitelist_blacklist_tests.cpp:10:10: fatal error: 'deferred_test/deferred_test.wast.hpp' file not found
#include <deferred_test/deferred_test.wast.hpp>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
[1330/1345] Building CXX object unittests/CMakeFiles/unit_test.dir/tic_tac_toe_tests.cpp.o
[1331/1345] Building CXX object unittests/CMakeFiles/unit_test.dir/wasm_tests.cpp.o
ninja: build stopped: subcommand failed.
The command '/bin/sh -c git clone -b $branch https://github.com/EOSIO/eos.git --recursive     && cd eos && echo "$branch:$(git rev-parse HEAD)" > /etc/eosio-version     && cmake -H. -B"/tmp/build" -GNinja -DCMAKE_BUILD_TYPE=Release -DWASM_ROOT=/opt/wasm -DCMAKE_CXX_COMPILER=clang++        -DCMAKE_C_COMPILER=clang -DCMAKE_INSTALL_PREFIX=/tmp/build  -DSecp256k1_ROOT_DIR=/usr/local -DBUILD_MONGO_DB_PLUGIN=true -DCORE_SYMBOL_NAME=$symbol     && cmake --build /tmp/build --target install && rm /tmp/build/bin/eosiocpp' returned a non-zero code: 1

This error is occurred on Dawn-4.0, Dawn-4.2, Eos-1.0.1 even EOS-1.0.2 as well, all versions are tried, still with the same issue.

After checked the source code, there is no file "deferred_test.wast.hpp" under the folder unittests/contracts/deferred_test/, but the whitelist_blacklist_tests.cpp include the head file, cause this issue, hopping EOS team to update the unit test module ASAP.

I had the same issue building on Ubuntu 18.04 LTS

I have same issue during my 1st build on Ubunti 16.04 LTS Virtual Machine....

Resolved by #3992.


Problems with multiple ips in pool

Hi there,
These days we are trying to warm up our ip's, sending a % ratio of our platform emails through postal.

We had configured 3 pools (P.A, P.B, P.C) with 1 ip in each one (P.A -> IP.A, P.B -> IP.B, P.C -> IP.C).
We had configured 3 mail servers with a default pool for each one (MS.A -> P.A, MS.B -> P.B, MS.C -> P.C). No IP pools rules anywhere.

The fact is that yesterday I realised that (as we are only sending through Mail Server C (due to our needs)) we have been only warming up 1 IP (IP.C). So I added the two other IPs to the Pool C too. (P.C -> IP.C & IP.B & IP.A). (The hostnames of each IP remain the same too for PTR convenience).
Today I realised that all of our emails that have been trying to be sent throgh IP.A and IP.B are in queue without any "sending action" from postal server.
Once we have removed the IP.A and IP.B from pool C, all the emails have been starting to send again... (I did a postal restart in the middle of this process).
As you can see here all of the queued messages are from this ip's (4 and 5).
Any idea? I will tray to investigate a bit further.
thanks in advance

When a message is queued with a IP it is added to a different queue on RabbitMQ. Specifically it will be outgoing-ID where the ID is the ID of the IP address.
The worker will only listen for messages on the queues where it has the IP configured though so if you have IPs configured in Postal but they aren't actually configured on any servers, the messages will never be able to processed.
It is designed in this way to ensure that the system works in a clustered installation where IPs can be moved between hosts on failures because only the server with the IP is able to send messages from it.

I have recently documented IP pools and have made sure to mention this on those docs: https://github.com/atech/postal/wiki/Configuring-IP-Pools

Clarification: when I say Mail Server, Im refering to a "software" mail server configured in Postal. The "mail servers" you can add per organization.
What do yo mean when you say "It's important to make sure that the IP addresses you add in the web interface are actually configured on your Postal servers" ? Are you refering to configure it as real IPs on the machine? In such a case, yes I have the 3 IPs properly configured in my machine.
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:50:56:01:28:dc brd ff:ff:ff:ff:ff:ff
    inet x.x.x.1/16 brd x.x.255.255 scope global enp0s3
    inet x.x.x.2/16 brd x.x.255.255 scope global enp0s3
    inet x.x.x.3/16 brd x.x.255.255 scope global enp0s3
    inet6 fe80::250:56ff:fe01:28dc/64 scope link

In deed we can actually send emails from the 3 pools (with and IP in eachone) assigned to each mail server. The problem is when I add the first 2 IPS also to the 3rd pool. The emails processed through theses ips wont be sent.

So that is maybe the problem! ^_^, thanks adam

Can you please elaborate this point.
"It's important to make sure that the IP addresses you add in the web interface are actually configured on your Postal servers" ? Are you refering to configure it as real IPs on the machine?"
Kindly add more details where to add those IP's in machine, also which file and how.
Thanks

You'll need some experience managing a Linux server in order to add IPs to your network interfaces. I suggest posting over on something like ServerFault if you need help with this.


Updated customProxy & Readme to run hac-infra plugin standalone

This PR updates the customProxy in the dev webpack config to point to the local kcp proxy. With this change we can test hac-infra without needing to start up hac-core locally each time.

Code looks good - and in theory, it should work, but I'm getting the following errors in the browser's console.  Wondering if this is due to the debugging the hac-core team is doing.

Thanks for testing, @kdoberst. Yes, this error does seem to be related to issue the HAC Core team has been investigating. I believe a fix was merged ~2 hours ago. cc: @florkbr
Also, looks like hac-infra got temporarily disabled as part of that troubleshooting effort and is yet to be re-enabled.
We'll need to hold off on testing this PR until that revert is merged and deployed.

Verified this worked
/approved
/lgtm

/approve


Adjust plugin.zsh file to run on zsh 5.1 in mSYS2.

A sole filename caused "command not found" errors while loading with zplug or oh-no-zsh on zsh 5.1.1 inside mSYS2 (Windows).
Sourcing the main file seems to work fine.

Can you fix the missing brackets like you did in z-sy-h, squash to one commit, and re-submit the PR to v0.3.x branch instead of master.
Thanks!


Slashing: on-chain evaluation of misbehavior reports from the BFT and statement table subsystems

...and automatically generate transactions with any witnessed misbehavior.
Should be simple enough:

Each misbehavior report must be accompanied by some security bond.
Each report contains a validator who misbehaved, the block hash they were building on when they misbehaved, and the proof of misbehavior
A report is valid iff the validator was a validator at the given block hash and the misbehavior given is true.

BFT misbehavior reports could be managed at the substrate level.
Parachain Statement Table misbehavior can only be managed in the polkadot runtime -- and will often require proofs of group membership at a block in recent history. We will need to make sure that all duty rosters within some range of history are computable.

@rphmeier i can help out on this regarding runtime logic and slashing, but will need help on logic for determining if "the misbehavior given is true"

What does that mean?
On Tue, Feb 16, 2021, 4:24 PM Robert Habermeier<EMAIL_ADDRESS>wrote:

Closed #81 https://github.com/paritytech/substrate/issues/81.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/paritytech/substrate/issues/81#event-4338527689, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSJH44CFGPAR5PBAU5RPE3S7LWBNANCNFSM4ESBBMOQ
.


Add allowInsecurePredicate to fix CI

Currently CI fails due to insecure packages https://hercules-ci.com/github/SomeoneSerge/nixpkgs-cuda-ci/jobs/10602

It seems other files need to be changed. See #18