Use bootstrap to lay widgets out

... to improve responsiveness, avoid scrollbars, and possibly facilitate further content structuring.
Currently vm detail is based on dl/dd/dt tags.

using flex in redesign, closing


Error invalid request BLR at offset 132 function POS is not defined module name or entrypoint could not be found

I used OS Linux.
Version Firebase file fdb 2.5. Database uses UDF
My code:
#![allow(unused_variables, unused_mut, unreachable_code, unused_imports)]
use std::path::Path;
use rsfbclient::{prelude::*, FbError};

#[allow(clippy::unnecessary_wraps)]
fn main() -> Result<(), FbError> {

    println!("exists test.fdb: {}", Path::new("/test/rust_firebird/test.fdb").exists());
    println!("exists libfbclient.so: {}", Path::new("/opt/firebird/lib/libfbclient.so").exists());

    #[cfg(not(feature = "pure_rust"))] // No support for embedded with pure rust driver
    {

        let mut conn = rsfbclient::builder_native()
            .with_dyn_load("/opt/firebird/lib/libfbclient.so")
            .with_remote()
            .db_name("/plinor/rust_firebird/test.fdb")
            .user("SYSDBA")
            .pass("masterkey")
            .connect()?;

        let rows = conn.query_iter("SELECT * FROM FZL", ())?;

            println!("-------------");
            println!("Table name");
            println!("-------------");
            for row in rows {
                let (r_name,): (String,) = row?;

                println!("{:^10}", r_name);
            }
    }
    Ok(())
}

I have return error
exists test.fdb: true
exists libfbclient.so: true
Error: Sql { msg: "invalid request BLR at offset 132\nfunction POS is not defined\nmodule name or entrypoint could not be found", code: -104 }
[1]    4102 segmentation fault  cargo run

EDIT COMMENT:
Used Python 3.11 on Linux, i readed fdb file Firebird 2.5
con = fdb.connect(
    database=database_selex,
    user=user_selex,
    password=password_selex,
    charset="UTF8",
    sql_dialect=3,   # sql_dialect (int): SQL Dialect for connection (1, 2 or 3).
    no_db_triggers=True,  # no_db_triggers (int): No database triggers flag (FB 2.1).
)
cur = con.cursor()

How setup rsfbclient connect to fdb with sql_dialect and no_db_triggers ?

I have return error

Please, provide the DDL for your FZL table

How setup rsfbclient connect to fdb with sql_dialect and no_db_triggers ?

no_db_triggers is not supported yet.
sql_dialect just call the dialect() method on connection builder. More infos:
 .db_name("/plinor/rust_firebird/test.fdb")
            .user("SYSDBA")
            .pass("masterkey")
            .dialect(Dialect::D1)
            .connect()?;

        let mut conn = rsfbclient::builder_pure_rust()
            .host("localhost")
            .db_name("/plinor/rust_firebird/test.fdb")
            .user("SYSDBA")
            .pass("masterkey")
            .dialect(Dialect::D1)
            .charset(charset::UTF_8)
            .transaction(TransactionConfiguration {
                lock_resolution: TrLockResolution::NoWait,
                ..TransactionConfiguration::default()
            })
            .connect()?;

Error
exists libfbclient.so: true
Error: Sql { msg: "invalid request BLR at offset 132\nfunction POS is not defined\nmodule name or entrypoint could not be found", code: -1 }```

I found the constant rsfbclient_core::ibase::isc_dpb_no_db_triggers, but I don't know how to change it and apply it to the query

Your invalid request BLR at offset 132\nfunction POS is it caused by database triggers? Or are you just trying to change this flag for another reason?
I'm investigating how provide this flag on the connection builder

I found the constant rsfbclient_core::ibase::isc_dpb_no_db_triggers, but I don't know how to change it and apply it to the query

Now you can disable the db trigger, try my last commit:
[dependencies]
rsfbclient = { git = "https://github.com/fernandobatels/rsfbclient.git", branch = "feature-151" }

   let mut conn = rsfbclient::builder_pure_rust()
            .host("localhost")
            .db_name("/plinor/rust_firebird/test.fdb")
            .no_db_trigger()
            .....
            .connect()?;

I found the constant rsfbclient_core::ibase::isc_dpb_no_db_triggers, but I don't know how to change it and apply it to the query

Now you can disable the db trigger, try my last commit:
[dependencies]
rsfbclient = { git = "https://github.com/fernandobatels/rsfbclient.git", branch = "feature-151" }

   let mut conn = rsfbclient::builder_pure_rust()
            .host("localhost")
            .db_name("/plinor/rust_firebird/test.fdb")
            .no_db_trigger()
            .....
            .connect()?;

"Cargo.toml"
rsfbclient = { git = "https://github.com/fernandobatels/rsfbclient", branch = "feature-151"}
n main() -> Result<(), FbError> {
    let file_fdb: &str = "test.fdb";
    println!("exists test.fdb: {}", Path::new(&file_fdb).exists());

    let mut conn = rsfbclient::builder_pure_rust()
        .host("localhost")
        .db_name("test.fdb")
        .user("SYSDBA")
        .pass("masterkey")
        .dialect(Dialect::D1)
        .no_db_trigger()
        .connect()?;

    let rows = conn.query_iter("SELECT * FROM FZL", ())?;

    println!("-------------");
    println!("Table name");
    println!("-------------");

    for row in rows {
        let (r_name,): (String,) = row?;

        println!("{:^10}", r_name);
    }
    Ok(())

Error:
error[E0425]: cannot find function `builder_pure_rust` in crate `rsfbclient`
  --> main.rs:15:36
   |
15 |         let mut conn = rsfbclient::builder_pure_rust()
   |                                    ^^^^^^^^^^^^^^^^^ not found in `rsfbclient`

I found the constant rsfbclient_core::ibase::isc_dpb_no_db_triggers, but I don't know how to change it and apply it to the query

Your invalid request BLR at offset 132\nfunction POS is it caused by database triggers? Or are you just trying to change this flag for another reason?
I'm investigating how provide this flag on the connection builder

Yes, I want to connect without triggers. Because if do not disable triggers, there will be a connection error. The same thing happened when trying to connect to Python using the fdb library

Error:
error[E0425]: cannot find function `builder_pure_rust` in crate `rsfbclient`
  --> main.rs:15:36
   |
15 |         let mut conn = rsfbclient::builder_pure_rust()
   |                                    ^^^^^^^^^^^^^^^^^ not found in `rsfbclient`

My bad. Try enabling the pure_rust feature
[dependencies]
rsfbclient = { git = "https://github.com/fernandobatels/rsfbclient.git", branch = "feature-151", features=["pure_rust"] }

Error:
error[E0425]: cannot find function `builder_pure_rust` in crate `rsfbclient`
  --> main.rs:15:36
   |
15 |         let mut conn = rsfbclient::builder_pure_rust()
   |                                    ^^^^^^^^^^^^^^^^^ not found in `rsfbclient`

My bad. Try enabling the pure_rust feature
[dependencies]
rsfbclient = { git = "https://github.com/fernandobatels/rsfbclient.git", branch = "feature-151", features=["pure_rust"] }

Yes, it works!
Thanks

Are you still facing BLR offset problems when select?

If it is possible to use triggers? I can send you an example database file

The new flag only disable the database level triggers. Table triggers will still be working.

Are you still facing BLR offset problems when select?

There are no more problems with reading the data.

New version released with this new resource: 0.24.0


[BUG] Remove recommend_seen

Description
recommend_seen parameter was modified but the Hyperdrive notebooks were not updated to this change.

This has been addressed by #840


Update readme to address jdk7+

Seems that hystrix is not supported on jdk6 anymore, so maybe this change will help new users...
Feel free to ignore if not :)

AFAIK, setting SOURCE/TARGET compatibility to Java 1.6 in build.gradle should be working to generate JDK6 bytecode.  We can't compile with JDK6 though, because The Nebula plugins only support JDK7+:

What went wrong:
java.lang.UnsupportedClassVersionError: nebula/plugin/netflixossproject/NetflixOssProjectPlugin : Unsupported major.minor version 51.0
nebula/plugin/netflixossproject/NetflixOssProjectPlugin : Unsupported major.minor version 51.0

hmm, ok


Added Name

Hello @gauravsharma97  The contributors.md file has been deprecated in recent PRs, you however can add your name here https://github.com/HacktoberfestinAba/HacktoberfestinAba.github.io/blob/master/CONTRIBUTING.md
You can git pull the repo to sync the updates and send in a new PR/ Re-Open this PR


[3.0] Remove deprecated code

This issue tracks the things that need to be deprecated. I'd like to have an issue for each one of these. Also, moving forward, when we deprecate an API, we need to immediately make an issue and assign it to the milestone when we are going to completely remove it.
Here's the list, please edit and add anything I'm missing.

[x] context.location, context.history
[x] default hashHistory
[x] old histories that don't use useRouterHistory
[x] mixins
[x] Link props (query, params, etc)
[x] getComponents first argument
[x] useRoute (the warning says to use createTransitionManager but I don't think that's right, seems like they should use useRouterHistorybut I don't know the history of that warning, transitionManager seems like implementation, not API)
[ ] isActive(pathname, query, indexOnly) in createTransitionManager and ``replaceState(state, pathname, query)inrunTransitionHooks`
[ ] Multiple leave hooks

After we cut our next minor release (https://github.com/reactjs/react-router/milestones/next-2.3.0), we'll create a 3.0 branch to start working on this stuff, that way we can still make bug fix releases on 2.3 from master. To keep our promise to not make major releases more often than every 3 months, we can release 3.0 on May 9-ish.

Set up a 2.x branch that we can put stuff on after 3.0 is out. I don't think we need ones for 2.0.x, 2.1.x, 2.2.x, etc.
In order to avoid the hassles and confused issues while we waited on 2.0, we should keep master as 2.x until we're either at or near a 3.0.0 release. It's more annoying for us as developers, but it's also annoying having to close tons of issues because of confusion over docs and code changes.

The next major release should go on a rolling next branch (like the one we have). That way you don't have to remember to keep updating .travis.yml (or the Circle equivalent, because Circle is sort of just a lot better) with the branch config.
In practice it's not that confusing to users (since only people close enough to the code to actually follow the repo will see it), and it's less book-keeping for us.
If we're really ambitious, we could just set up the deprecation removals on that branch right now, and cut pre-releases on an ongoing basis.

Working on that at the moment. Updated the next branch too.

Re: The getComponents deprecation. That was introduced in 2.2. You guys are closer to this issue than I am, but I remember Ryan (or someone else) saying anything un-deprecated that works in 2.0 will work in 3.0 with warnings. Are we attempting to maintain that here? Honestly, I don't care. I just want to know if it should go into the PR or not.
(P.S. Yes, @taion, CircleCI is many times better than Travis. I've got to talk Dan into using it for Redux. The speedups over there would be quite notable.)

OK, they're all in #3340.

Found some more. Added to the OP. But it's bedtime, so if someone else wants to get them, go nuts!

@timdorr The rule of thumb is that stuff that people use a lot should stay deprecated for longer. The location arg to getComponent is almost never used, so we don't need to keep it around.

BTW, lets go with merging between next and master rather than rebasing. It makes for a slightly messier git history, but it'll be easier to tell what's going on.

@timdorr The rule of thumb

Probably need to document this somewhere.
Rule is it goes away in the next release, unless we decide it's too close to the next release and we want to give people more time.
Sound right @taion ?

That makes sense to me.


No such table: messages (Edit: Support for WhatsApp databases with "message" table)

When running the script I get following error message
Gathering contacts...(97)
Traceback (most recent call last):
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\Scripts\wtsexporter.exe\__main__.py", line 7, in <module>
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 147, in main
    messages(db, data)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\extract.py", line 88, in messages
    c.execute("""SELECT count() FROM messages""")
sqlite3.OperationalError: no such table: messages

My database doesn't contain the table messages, I only have one called message which contains the data but the schema of the table looks different from what it's supposed to look like.

What could be the issue here?

I'm using Android.
WhatsApp versions that have been used are  <IP_ADDRESS> and <IP_ADDRESS> (Beta)
<IP_ADDRESS> was running on an emulator so that I could pull the /com.whatsapp/ directory.
On the <IP_ADDRESS> version I used the previously pulled key to decrypt the db.

Is both versions and environments result in same database schema?

Yes, they both resulted in the same database schema

Interesting. I will try to reproduce it with <IP_ADDRESS> on emulator.

I installed WhatsApp on the emulator on the 9th of this month and then imported my chat history using the chat backup in WhatsApp.
On my actual phone, WhatsApp has been installed like 6 months ago.

I have check some similar project and suspect that "message" table is a legacy table for storing messages. On your phone, is the WhatsApp conversation restored from old backup after installation?

I restored the WhatsApp conversations from Google Drive (doing weekly backups).
Never deleted my WhatsApp chat history though so the messages go all the way back to 2013

As far as I observed, it is possible that "message" was used in the early years of WhatsApp. Could you check if new installation without backup will result the same situation?

I'll give it a try later and report back.

Sorry, it took a little bit longer until I had time to try it out.
Setup a new emulator, installed WhatsApp and didn't import my backup.
The table messages exists now.
So I'm guessing my backup is just too old for it to work then? :(

Sorry, it took a little bit longer until I had time to try it out.

No problem!

So I'm guessing my backup is just too old for it to work then? :(

I think so.
I would like to add support for older version. However, I don't have such database, hence, I am not able to do it. If you have time and you want the script to work with your database, you can take a look inside the database and fine tune the script.
Anyway, I will keep my eyes on the opportunity for supporting old databases. Thanks for your report!

Hey everyone! I just stumbled upon the same issue with WhatsApp version <IP_ADDRESS> on Android on two different devices using two different phone numbers without restoring any backup.
I'll try to reinstall WhatsApp and try it again, but it seems like the database scheme is changing. The new messages table has the following schema:
CREATE TABLE message (
  _id INTEGER PRIMARY KEY AUTOINCREMENT,
  chat_row_id INTEGER NOT NULL, from_me INTEGER NOT NULL,
  key_id TEXT NOT NULL, sender_jid_row_id INTEGER,
  status INTEGER, broadcast INTEGER,
  recipient_count INTEGER, participant_hash TEXT,
  origination_flags INTEGER, origin INTEGER,
  timestamp INTEGER, received_timestamp INTEGER,
  receipt_server_timestamp INTEGER,
  message_type INTEGER, text_data TEXT,
  starred INTEGER, lookup_tables INTEGER,
  message_add_on_flags INTEGER, sort_id INTEGER NOT NULL DEFAULT 0
);

I'll try to reinstall WhatsApp and try it again, but it seems like the database scheme is changing. The new messages table has the following schema:

I can produce the same result.
@Takepy As I can reproduce your situation now, I will work on supporting "message" table.

WhatsApp using "message" table spread different types of message to many other tables. Good chance for me to rewrite the project :)

@Takepy were you able to find a way around this issue? Looks like I'm in the same boat, unfortunately and my whatsapp database is using the "legacy" format as well. I've got messages dating back all the way to 2014.

@karanrajpal14 I came across the same issues as well, got a new phone and couldnt export the messages. Did you have any luck getting it to work?
I've started on a c# project to extract the messages which is working to extract and dump to text, just working on the html part now

Has anyone made some progress here - it now seems as if it has to do with new versions of whatsapp? Or does it only affect people with a very long message history? I am very ready to back everything up and try moving to a full puppeteered whatsapp with mautrix-whatsapp, but things seem to still be shifting way too much.
@KnugiHK any way we can help?

Has anyone made some progress here - it now seems as if it has to do with new versions of whatsapp? Or does it only affect people with a very long message history? I am very ready to back everything up and try moving to a full puppeteered whatsapp with mautrix-whatsapp, but things seem to still be shifting way too much.
@KnugiHK any way we can help?

The hardest part of this project is to understand the structure of the WhatsApp database. Any clues on the structure and pull requests are welcome.

I played with it a bit yesterday and replaced the main query in extract.py with this:
SELECT message.sender_jid_row_id as key_remote_jid,
                        message._id,
                        message.from_me as key_from_me,
                        message.timestamp,
                        message.text_data as data,
                        message.status,
                        message_future.version as edit_version,
                        message_thumbnail.thumbnail as thumb_image,
                        message_media.file_path as remote_resource,
                        message_media.mime_type as media_wa_type,
                        message_location.latitude,
                        message_location.longitude,
                        message_quoted.key_id as quoted,
                        message.key_id,
                        message_quoted.text_data as quoted_data,
                        message_media.media_caption
                 FROM message
                    LEFT JOIN message_quoted
                        ON message_quoted.message_row_id = message._id
                    LEFT JOIN message_location
                        ON message_location.message_row_id = message._id
                    LEFT JOIN message_media
                        ON message_media.message_row_id = message._id
                    LEFT JOIN message_thumbnail
                        ON message_thumbnail.message_row_id = message._id
                    LEFT JOIN message_future
                        ON message_future.message_row_id = message._id
                    WHERE key_remote_jid <> '-1';

That brings me past the missing messages db, but will clash in extract.py:240 trying to match the remote id to something in the big data dictionary. So, I assume me trying to replace key_remote_jid with sender_jid_row_id might go into the right direction, but might need some more joints to actually turn things into a phone number.
There are also a messages_view and a chats_view now that seem to match some more tables with each other. Did anybody else figure some dependencies based on their connections out?

I played with it a bit yesterday and replaced the main query in extract.py with this:
SELECT message.sender_jid_row_id as key_remote_jid,
                        message._id,
                        message.from_me as key_from_me,
                        message.timestamp,
                        message.text_data as data,
                        message.status,
                        message_future.version as edit_version,
                        message_thumbnail.thumbnail as thumb_image,
                        message_media.file_path as remote_resource,
                        message_media.mime_type as media_wa_type,
                        message_location.latitude,
                        message_location.longitude,
                        message_quoted.key_id as quoted,
                        message.key_id,
                        message_quoted.text_data as quoted_data,
                        message_media.media_caption
                 FROM message
                    LEFT JOIN message_quoted
                        ON message_quoted.message_row_id = message._id
                    LEFT JOIN message_location
                        ON message_location.message_row_id = message._id
                    LEFT JOIN message_media
                        ON message_media.message_row_id = message._id
                    LEFT JOIN message_thumbnail
                        ON message_thumbnail.message_row_id = message._id
                    LEFT JOIN message_future
                        ON message_future.message_row_id = message._id
                    WHERE key_remote_jid <> '-1';

That brings me past the missing messages table, but will clash in extract.py:240 trying to match the remote id to something in the big data dictionary. So, I assume me trying to replace key_remote_jid with sender_jid_row_id might go into the right direction, but might need some more joints to actually turn things into a phone number.
There are also a messages_view and a chats_view now that seem to match some more tables with each other. Did anybody else figure some dependencies based on their connections out?

I will have a look at the clash later.

I am curious about how WhatsApp decides which table to store messages 🤨. Is "message" a legacy table? Or "messages" is the legacy one?

"messages" is the legacy one, please read https://thebinaryhick.blog/2022/06/09/new-msgstore-who-dis-a-look-at-an-updated-whatsapp-on-android/

I played with it a bit yesterday and replaced the main query in extract.py with this:
SELECT message.sender_jid_row_id as key_remote_jid,
                        message._id,
                        message.from_me as key_from_me,
                        message.timestamp,
                        message.text_data as data,
                        message.status,
                        message_future.version as edit_version,
                        message_thumbnail.thumbnail as thumb_image,
                        message_media.file_path as remote_resource,
                        message_media.mime_type as media_wa_type,
                        message_location.latitude,
                        message_location.longitude,
                        message_quoted.key_id as quoted,
                        message.key_id,
                        message_quoted.text_data as quoted_data,
                        message_media.media_caption
                 FROM message
                    LEFT JOIN message_quoted
                        ON message_quoted.message_row_id = message._id
                    LEFT JOIN message_location
                        ON message_location.message_row_id = message._id
                    LEFT JOIN message_media
                        ON message_media.message_row_id = message._id
                    LEFT JOIN message_thumbnail
                        ON message_thumbnail.message_row_id = message._id
                    LEFT JOIN message_future
                        ON message_future.message_row_id = message._id
                    WHERE key_remote_jid <> '-1';

That brings me past the missing messages table, but will clash in extract.py:240 trying to match the remote id to something in the big data dictionary. So, I assume me trying to replace key_remote_jid with sender_jid_row_id might go into the right direction, but might need some more joints to actually turn things into a phone number.
There are also a messages_view and a chats_view now that seem to match some more tables with each other. Did anybody else figure some dependencies based on their connections out?

key_remote_jid same with raw_string from table jid

Are there any updates on this?

Not yet. Hopefully there will be updates on Dec.

Are there any updates on ?

Found a solution but i am not sure every aspect of project is working properly.
First https://github.com/andreas-mausch/whatsapp-viewer/issues/151#issuecomment-1229244368
I applied this solution this solition modified old msgstore.db.
After that  i still recieved errorS. So with SQLlite i add new tables to overcome error: no such table: ...
After adding couple tables, code is working now.  And able to output a result.
But as i said i cannot confirm that every aspect of project is working properly.

Hi everyone,
I am working on porting the code to the WhatsApp database with new schema. The main part is completed and there are some bugs need to be fixed.

I created a new branch called "testing" which support "message" table directly from wtsexporter command. Feel free to give it a try but please expect bugs from the branch. Bug reports are welcome and should be reported in this issue.

First of all, thank you for working on this.
I just downloaded the branch and gave it a try.
Unfortunately it didn't work for me.
╰─ wtsexporter -a
Gathering contacts...(97)
Traceback (most recent call last):
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\Scripts\wtsexporter.exe\__main__.py", line 7, in <module>
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 174, in main
    messages(db, data)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\extract.py", line 195, in messages
    c.execute("""SELECT count() FROM messages""")
sqlite3.OperationalError: no such table: messages

I made sure to uninstall the old version I had with pip uninstall whatsapp-chat-exporter and then installed the new one.
Is there anything I'm missing?

First of all, thank you for working on this. I just downloaded the branch and gave it a try. Unfortunately it didn't work for me.
╰─ wtsexporter -a
Gathering contacts...(97)
Traceback (most recent call last):
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\Scripts\wtsexporter.exe\__main__.py", line 7, in <module>
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 174, in main
    messages(db, data)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\extract.py", line 195, in messages
    c.execute("""SELECT count() FROM messages""")
sqlite3.OperationalError: no such table: messages

I made sure to uninstall the old version I had with pip uninstall whatsapp-chat-exporter and then installed the new one. Is there anything I'm missing?

Can you verify that the __main__.py file import extract_new from Whatsapp_Chat_Exporter import extract_new as extract instead of extract from Whatsapp_Chat_Exporter import extract, extract_iphone

__main__.py did not include from Whatsapp_Chat_Exporter import extract_new as extract.
Replaced the files in \site-packages\Whatsapp_Chat_Exporter manually with the ones from the branch now and ran the script again.
Now being faced with this
╰─ wtsexporter -a
Gathering contacts...(97)
Traceback (most recent call last):
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\Scripts\wtsexporter.exe\__main__.py", line 7, in <module>
  File "C:\Users\GLa******OS\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\__main__.py", line 184, in main
    messages(db, data)
  File "C:\Users\******\AppData\Local\Programs\Python\Python310\lib\site-packages\Whatsapp_Chat_Exporter\extract_new.py", line 206, in messages
    c.execute("""SELECT jid.raw_string as key_remote_jid,
sqlite3.OperationalError: no such column: message_media.media_caption

It should be fixed in the latest commit: https://github.com/KnugiHK/Whatsapp-Chat-Exporter/commit/d3892a4e4f4f0b533107f871a23de22153cc879a.

The new branch worked on my side -- thanks a lot !
Although all medias are missing from the htmls (i tried both with and without the -e flag).
Thanks a lot for your work, your tool is great.

The new branch worked on my side -- thanks a lot ! Although all medias are missing from the htmls (i tried both with and without the -e flag). Thanks a lot for your work, your tool is great.

Hello, @cbzittoun , I had the same problem with the media. Try to pass the parent directory of "Media" instead of the address to "Media" itself.
I still have three issues, though:

All exported conversations start with "This message is not supported".
The flag "-s" seems not to be working.
I've realized that it would also be helpful for me to split the result into multiple HTML files 🙈.

I think I was pointing to no Media folder actually.
I was expecting the script to copy the files, not move them (although safer, it would be slower).
https://github.com/KnugiHK/Whatsapp-Chat-Exporter/blob/580eaddb24ee359433593776f1b6643e01d91979/Whatsapp_Chat_Exporter/extract.py#L531
Maybe is it worth an explicit warning that input files have been moved around?

@cbzittoun

The new branch worked on my side -- thanks a lot ! Although all medias are missing from the htmls (i tried both with and without the -e flag). Thanks a lot for your work, your tool is great.

Actually, embedding media to the HTML file (-e option) is removed and was presented in the very early version. It is planned to have embedding again. Media should be located under WhatsApp folder (i.e., WhatsApp/Media). If your current working directory has the folder named WhatsApp, it will automatically move that folder. If you want to specify another directory, use -m.

I think I was pointing to no Media folder actually, as I was running the cmd for the 2nd time. I was expecting the script to copy the files, not move them (although slower, it would be safer).
https://github.com/KnugiHK/Whatsapp-Chat-Exporter/blob/580eaddb24ee359433593776f1b6643e01d91979/Whatsapp_Chat_Exporter/extract.py#L531
Maybe it is worth an explicit warning that input files are being moved around?

We move the discussion of this to https://github.com/KnugiHK/Whatsapp-Chat-Exporter/issues/25.

@velecto1

I still have three issues, though:
* All exported conversations start with "This message is not supported".
* The flag "-s" seems not to be working.
* I've realized that it would also be helpful for me to split the result into multiple HTML files see_no_evil.

Can you confirm if the first two issues happen only in the message_table branch? If they happen in the main branch, please open another issue for that.

Hi, sorry for the delay; I didn't have the old backup available immediately.

Nope, the "This message is not supported" thing does not display in the resulting HTML when converting an old database. The chat is actually complete, so maybe it is the "message" saying: "Messages and calls are end-to-end encrypted..."

The 'main' branch doesn't have the '-s' flag available at all.

Hi, sorry for the delay; I didn't have the old backup available immediately.
1. Nope, the "This message is not supported" thing does not display in the resulting HTML when converting an old database. The chat is actually complete, so maybe it is the "message" saying: "Messages and calls are end-to-end encrypted..."

2. The 'main' branch doesn't have the '-s' flag available at all.

I will look into it.
Oh, yes. -s is not released yet.

@velecto1

I still have three issues, though:
* All exported conversations start with "This message is not supported".
* The flag "-s" seems not to be working.
* I've realized that it would also be helpful for me to split the result into multiple HTML files see_no_evil.

Can you confirm if the first two issues happen only in the message_table branch? If they happen in the main branch, please open another issue for that.

Hello there u can contact me I can help u out !

@velecto1

I still have three issues, though:
* All exported conversations start with "This message is not supported".
* The flag "-s" seems not to be working.
* I've realized that it would also be helpful for me to split the result into multiple HTML files see_no_evil.

Can you confirm if the first two issues happen only in the message_table branch? If they happen in the main branch, please open another issue for that.

Hello there u can contact me I can help u out but in private !

Feel free to poke me around in the Matrix network: https://matrix.to/#/!KtGjfSytJvzxewsXVd:matrix.org

I've had the same problem. I was able to extract a Whatsapp DB from Android using the extractor tool and noticed it only has the 'message' table. Will give the test branch a try and see how it goes.

I've had the same problem. I was able to extract a Whatsapp DB from Android using the extractor tool and noticed it only has the 'message' table. Will give the test branch a try and see how it goes.

This issue will likely happen to more and more people in the future as WhatsApp updates more people's database schema.

I just used the code from the message_table branch and was able to successfully export my Whatsapp database. I really appreciate your effort for this useful tool. The only thing I noticed in the resulting files is, that in group chats the name of the group is shown instead of the name of the person writing the message.

I just used the code from the message_table branch and was able to successfully export my Whatsapp database. I really appreciate your effort for this useful tool. The only thing I noticed in the resulting files is, that in group chats the name of the group is shown instead of the name of the person writing the message.

Thanks for reporting that, I can reproduce the problem.

I updated to the latest version of the message_table branch and can confirm that the error is gone, thank you for that. In the meantime I had another issue: When opening the files in Safari on Mac the encoding is not detected properly and emojis and german umlauts are not displayed correctly.
By adding <meta charset="UTF-8"> to the head section of one of the files, I was able to fix that. Could you please automatically add this tag.

Hi, sorry for the delay; I didn't have the old backup available immediately.
1. Nope, the "This message is not supported" thing does not display in the resulting HTML when converting an old database. The chat is actually complete, so maybe it is the "message" saying: "Messages and calls are end-to-end encrypted..."

2. The 'main' branch doesn't have the '-s' flag available at all.

Metadata is also treated as message in the database, but since it is not the main focus when it comes to exporting chats, metadata may shows as "not supported" unless handled like changes of group name. Therefore, I will consider it not a bug if the chat is complete.
I will start preparing for the release when more tests are being performed.

hello, I have the "sqlite3.OperationalError: no such table: messages" error too.
But I am messing with the Whatsapp databases firstly around since today.
My used Whatsapp-Chat-Exporter version is: Minor Release 2023/01/31 0.85
and in this version it should be fixed right?

I checked out the message_table branch and used it to extract my newer 'message' DB successfully. All conversations including group conversations were converted to HTML. Many thanks @KnugiHK !

I had to cherry-pick the fix for https://github.com/KnugiHK/Whatsapp-Chat-Exporter/issues/32 and then it worked perfectly. Thank you for making this tool!
➜  Whatsapp-Chat-Exporter git:(message_table)$ git cherry-pick 2ba5571
➜  Whatsapp-Chat-Exporter git:(message_table)$ pip install '.[android_backup]'

Hello everyone! We are finally moving to the last step before releasing this update.
I merged the logic for processing old and new schema in extract.py in commit fb88124. As it is not a commit specifically for message table, it will not be merge into the message_table branch and the branch will not be updated from now on. And changes will be committed to dev branch as usual.
Feel free to give it a try, especially for those who have databases with both message and messages tables, to see if there is any compatibility issue.

Hey there! Not sure if it's related, but I was having the same issue related to this thread, downloaded both the commit and the dev branch versions and now I'm getting a different error:
Traceback (most recent call last):
  File "/home/user/.local/bin/wtsexporter", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/user/.local/lib/python3.11/site-packages/Whatsapp_Chat_Exporter/__main__.py", line 229, in main
    messages(db, data)
  File "/home/user/.local/lib/python3.11/site-packages/Whatsapp_Chat_Exporter/extract.py", line 249, in messages
    data[content["key_remote_jid"]].add_message(content["_id"], Message(
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'add_message'

Again, not sure if it's related, but what should I do in this case, please?

What's the command you issued?

Hiya there @KnugiHK, I ran wtsexporter -a. I have msgstore.db, wa.db and the WhatsApp folder (containing the Backups, Databases and Media folders) in the directory I tried to run the command.

@umjediqualquer I did a quick fix on it (b371587) in the dev branch. Would you please see if the fix works?

@umjediqualquer I did a quick fix on it (b371587) in the dev branch. Would you please check if the fix works?

Managed to make some progress, getting a different error message now:
Gathering messages...(694764/694764)
Gathering media...(43618/43618)
Traceback (most recent call last):
  File "/home/user/.local/bin/wtsexporter", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/home/user/.local/lib/python3.11/site-packages/Whatsapp_Chat_Exporter/__main__.py", line 231, in main
    vcard(db, data)
  File "/home/user/.local/lib/python3.11/site-packages/Whatsapp_Chat_Exporter/extract.py", line 491, in vcard
    file_name = "".join(x for x in media_name if x.isalnum())
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not iterable```

Do you know if your msgstore.db use message or messages table?

Do you know if your msgstore.db use message or messages table?

I'm assuming it's message because when running the release version, I get the sqlite3.OperationalError: no such table: messages error, but I can open this with a db viewer to double check.

Attempt on fixing it is pushed (06a1d34). See if that works (the error may disappear but it is not a good fix IMO).

Is there a way to extract only the chat without the media?

There is no way to extract chat only. Maybe it is a good option to add.

It's weekend and I don't to keep bothering you with this haha

That's fine. The bug has to be fixed anyway. And I only reply when I am available.
As for the bug, I committed another attempt to fix it. This time I modified my database to test the problem myself and it works for me. Also, maybe the file name should rely on the information inside the vcards instead of the message data (the current implementation).

@KnugiHK it worked! Seems to have generated everything correctly and didn't throw any errors :D
Thank you very much for your help, especially on a weekend! May I buy you a cup of coffee (or tea, it that's your cup, heh) as a token of gratitude?

Glad that works for you too! And thanks for your report! The point for not releasing this update yet is to let everyone test it and spot problems.
Also, I appreciate your offer to buy me a cup of coffee or tea, but it's not necessary. If you'd like to show your support, consider staring this repo instead. That meant a lot to me😆. Thanks again.

Hi, I cloned the "message_table" branch and run the tool with this command:
python3 main.py -a --db ./msgstore.db
The messages are recovered correctly but i noticed that two identical "WhatsApp" folders are created.
One outside and one inside the "result" folder.
This might be a bug.
The two folders structure are:
./WhatsApp/
./WhatsApp/vCards/
./result/
./result/messages.html
./result/WhatsApp/
./result/WhatsApp/vCards/

Did "Copying media directory..." printed in your console? I guess your problem is related to #25.
Also, "message_table" branch is no longer maintained. Try dev branch instead.

The output treats deleted message as not supported message in the new schema. It is fixed in c7a01bb.

WhatsApp using "message" table spread different types of message to many other tables. Good chance for me to rewrite the project :)

Kindly do it, I am also getting same error : sqlite3.OperationalError: no such table: messages
In my case Messages are stored in "message" table.

WhatsApp using "message" table spread different types of message to many other tables. Good chance for me to rewrite the project :)

Kindly do it, I am also getting same error : sqlite3.OperationalError: no such table: messages In my case Messages are stored in "message" table.

The support of the message table is completed and will be released soon.


[Modification Request] Change tag text color (in browser overlay)

Environment

Operating System: MacOS Mojave 10.14.4
Node Version: 10.15.1
NPM Version: 6.9.0
webpack Version: 4.30.0
${package} Version: 2.24.4

Expected Behavior / Situation
errors and warning tag should be clearly readable.
Actual Behavior / Situation
errors and warning tag text are barely readable because of the contrat between the background color and the text color.
The text color is by default white, which is too light to contrast with the background color of the tag.
Modification Proposal
Add a tagColor entry in overlayStyles object and give it a default value of #000000.

I’d happily take a PR for this 👍

Just created PR #360 to fix this.
I end up by simply improved the style of client overlay because adding an option wasn't compatible with the actual overlayStyles object, which is only for the parent div style, not the tag.
Anyway now tags are easily readable and the UX will be better.
Hope you can merge that soon! 😄

@glenjamin thank you so much, it was a fast PR 😄
Could let us now when you publish it on npm?
Cheers


Notebooks with names that differ only in special characters are merged (MD export)

Export of the following folders

end in the folowing file/folder structure

Open Bug report https://github.com/laurent22/joplin/issues/9436

Thank you for opening the upstream issue!


Gopro8 Black Not Waking up.

mac mini M1
connect gopro with USB cable.
this is my code.
from goprocam import GoProCamera, constants
gopro = GoProCamera.GoPro(ip_address="<IP_ADDRESS>")

gopro = GoProCamera.GoPro(ip_address="<IP_ADDRESS>")
Waking up...

but not waking up..

@davidkahle
what is the connection string used to connect to the gopro when connected via USB cable not wifi?
is it the ip <IP_ADDRESS> or the UIID which is found in /dev/ ?
any Help ?


Define "nodraw" commands that don't expect shaders

Hi guys,
So far it feels like the thinking is that if we want a command that doesn't draw anything, then that command has to issue a callback that calls the other draw commands, like this:
setupCamera( () =>{
    drawBunny();
  })

Which is fine, although I'm not sure it's really documented, but my main point is that as your application grows in size you can see how this can get unwieldy really quickly, just with a few more features:
  setupCamera( () =>{

    setupScene( () =>{

      createSky( () => {
        drawBunny();
      })
    })

  })

yes, that would be a fancy bunny.
I'm aware this could be by design though, because even if this is cumbersome, I agree that it does centralise everything that happens during one frame in one place.
If this is the case, I guess maybe the docs should be a bit clearer on that point.
Otherwise it would be good to be able to define these "no draw" commands with a flag or something rather than nesting them.

@alvinsight I may be misinterpreting, but I think the nesting might be necessary. If you type:
commandThatSetsFramebufferA(() => {
  commandThatSetsFramebufferB(() => {
    draw1();
  })
  draw2();
})

Then you'd expect that draw1 would write to framebufferB while draw2 would write to framebufferA. So if a command sets a property, isn't the nesting required to ensure it properly unsets it? Does the nesting cause logical/data flow problems or is it more a matter of keeping the code structure nice? If the latter, then it might be more a matter of code organization and separating out functions to reduce the indentation if not the actual nesting.
Let me know if I'm misinterpreting though!

@rreusser You're right, sorry I just realised my comment might have been misleading, I just updated it.
What I think would be to be able to call a command that doesn't draw anything on its own like:
setUpCameraAndTimeUniforms();
commandThatSetsFramebufferA(() => {
  commandThatSetsFramebufferB(() => {
    draw1();
  })
  draw2();
});

Just to reduce the amount of nesting, as at the moment the above would break.

regl commands conceptually do three things when called:

set the state specified
either draw or call the provided function
restore the state

So if you didn't draw anything and you didn't nest a function, the command would simply set and then restore the state, which would be a waste. For the command do have any effect you'd need to remove step 3, but 'sticky' states like that would conflict with regl's effort to make things stateless. Otherwise you'd maybe want a command that sets state that's undone by the parent command, but currently the only way to do that is to make the data part of the parent command.
To be honest, the nesting bothered me too for a bit, but I found that with maybe one level of indirection by breaking up into functions, it hasn't really been a problem. (at least much less of a problem than dealing with state!)

I believe this issue goes against the design principles of regl. Thanks for the comments @alvinsight but I'm going to go ahead and close this as not actionable.

Hey @gregtatum no problem! I've found my way around setting context variables and other stuff that were not really brought forward in the examples, so I think this was mostly due to my lack of understanding of what regl really is for :)

Great, glad you worked it out!


When the Topic Area is chosen, topics in draft are not visible

Function of the workaround for making topics/categories "unpublished," I realize. Just entering as it's something to get resolved when we're ready to

Lost track of commit, but this is fixed.


PR for code review - Page structure and API calls

For this PR, a list of shows is presented on the website, while showing likes and comments that each show has
Features

List of top rated shows on page
Show's like counter
Show's comment counter
Show's comments popup

Done by
@wickathou @danielmatama
NOTE
There was a conflict when merging a branch which resulted on a mistaken merge of a feature branch into the dev branch
Live view

Status: Invalid 🔴
Hi @wickathou, @danielmatama 🙋♀,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that does not follow the proper GitHub flow for submitting final Capstone projects.

Kindly merge this Pull Request and create a new Pull Request merging the dev branch to the main branch. This is how you should always submit your Capstone Projects.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers 🥂  and Happy coding!!! 👯
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me @KDlamini  in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Support coverage calculated from PIT mutation tests

Closes #70

Coverage decreased (-1.6%) to 94.969% when pulling 990414ce16cba90f7d1578359bfc4f8b57e69116 on thejohnfreeman:master into d6d954324ad279c5a368e8e2a72fe9a6c27152df on kt3k:master.

After pushing this latest fix, the build passed with oraclejdk8 and failed with oraclejdk7. I believe that failure is spurious, caused by some transient internet connectivity problem. I believe that if you restart the build, which I cannot do, then it will pass.
The fall in coverage is due to following the pattern for the JacocoSourceReportFactoryTest where only the static method is tested, but not the instance method that finds the source directories.

Thanks for the constribution!
All looks good to me. I agree that the test failure in travis (oraclejdk7) is irrelevant of this PR. (I found similar issue.)
I'll publish this version in a few days.

Coverage decreased (-1.6%) to 94.969% when pulling 990414ce16cba90f7d1578359bfc4f8b57e69116 on thejohnfreeman:master into d6d954324ad279c5a368e8e2a72fe9a6c27152df on kt3k:master.

Published as v2.8.0!


Build fails on Windows

Building this project fails on Windows. Any plans to add support for Windows?

@jethrogb i got the following error
error: failed to run custom build command for `mbedtls-sys-auto v2.26.1`

Caused by:
  process didn't exit successfully: `C:\Users\Skill\Programs\Sources\Rust\websocket_test\target\debug\build\mbedtls-sys-auto-ba83572cec9b6e94\build-script-build` (exit code: 101)
  --- stderr
  error: unknown argument: '-nologo', err: true
  error: unsupported use of internal gcc -Z option '-Z7', err: true
  warning: unknown warning option '-W4' [-Wunknown-warning-option], err: false
  thread 'main' panicked at 'bindgen error: ()', C:\Users\Skill\.cargo\registry\src\github.com-1ecc6299db9ec823\mbedtls-sys-auto-2.26.1\build\bindgen.rs:140:14

Done by #235
Now 0.9.3 or master rust-mbedtls is able to be compiled with target x86_64-pc-windows-msvc on stable

Thanks for the update.


NavigationMeshInstance bake broken?  I tried downloading the navigation mesh demo. Then I baked the demo node and the NavigationMeshInstance doesn't work, the path dissappear.
https://i.imgur.com/GtNxziE.gifv
https://i.imgur.com/919YnTj.gifv
Those errors are thrown:
Errors

Damn, nvm, i see now you can create a NavMesh directly in the mesh menu at top bar. Sorry for post.
Closed.


Provide an example on how to use libtrixi

Should we somewhere add an example CMakeLists.txt which compiles the fortran_hello_world as a standalone cmake project? Or maybe just add the cmake code to README.md?
For reference:
#
# Fortran Hello Trixi
#

# Specify minimum cmake version
cmake_minimum_required ( VERSION 3.0 )

# Specify project info
project ( fortran_hello_world VERSION 0.1.0 DESCRIPTION "Example for using libtrixi Fortran" )

# Enable Fortran
enable_language(Fortran)

# Find libtrixi
find_library ( TRIXI_LIBRARY trixi REQUIRED)

# Find libtrixi.mod
find_path ( TRIXI_MOD_DIR libtrixi.mod PATH_SUFFIXES lib REQUIRED)

# Find MPI
find_package( MPI REQUIRED )

# Find Julia
list ( APPEND CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}" )
find_package( Julia REQUIRED )

# Define the executable
add_executable(${PROJECT_NAME} fortran_hello_world.f90)

# Add libraries for linking
target_link_libraries(${PROJECT_NAME} PRIVATE ${MPI_Fortran_LIBRARIES} ${TRIXI_LIBRARY} ${JULIA_LIBRARY})

# Add include directories
target_include_directories(${PROJECT_NAME} PRIVATE ${MPI_Fortran_INCLUDE_DIRS} ${TRIXI_MOD_DIR})

Requires CMAKE_PREFIX_PATH=<libtrixi_install_directory> when running cmake.
Originally posted by @bgeihe in https://github.com/trixi-framework/libtrixi/issues/1#issuecomment-1591086591

Personally, I would not put it in the README - too much clutter. Instead, I would maybe just put the standalone CMakeLists.txt inside the examples/ folder and then add a section to the README such as "Building the examples", which explains how to build the examples after having built the library itself.

Also, IMHO we should always have a C (and/or C++) based example, that mimics the Fortran example. C/C++ are just far better understood by the majority of users (I believe), and it might help for debugging when we want to rule out some issues and don't know if it is due to some weird Fortran <--> C conversion or something else.


Invalid LICENSE-MIT file

The file LICENSE-MIT is at present invalid, because it refers to a contained copyright notice that was removed in this commit: https://github.com/rust-lang/cargo/commit/d82153017d599e89d6d2aeeeb4ca0022ea6f8382
It is a condition of the license that "The above copyright notice (…) shall be included in all copies or substantial portions of the Software.", but there exists no "above copyright notice" to include. As such, it is impossible to be in compliance with this license.

Another take on avoiding misattribution is what maplit does: https://github.com/bluss/maplit/blob/master/LICENSE-MIT
The license file states Copyright (c) 2015 without attribution.
I have no idea of the legal bearings of any of this, I just want to be in compliance :)

cc @joshtriplett

@maghoff This really isn't an issue, and no one will interpret it as such. "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." is normally interpreted to mean "reproduce the entire copyright/license block exactly as you receive it". If there isn't a notice, then that's fine; you just have to reproduce the entire license block. Better that than to change the text to not exactly match the MIT license. And better that than to have an inaccurate notice; "The Rust Project Developers" is not a legal entity.
Also note that all works are automatically copyrighted without any need for a notice, and a legally valid copyright notice has a very specific form, which does require an author name. Including a half-formed copyright notice does not have any particular meaning.

Thanks for getting back to me @joshtriplett 🙂
Let me start out by saying that whatever you decide is fine by me, I am by no means an authority here. I'll take this opportunity to explain my viewpoint and then you can decide whether or not you consider it to have any merit.

This really isn't an issue, and no one will interpret it as such.

What do you mean? No lawyer will interpret it as an issue? Or did you mean to call me nobody? 😉 Because here we are.

"The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software." is normally interpreted to mean "reproduce the entire copyright/license block exactly as you receive it".

I take issue with this interpretation, especially in a reality where package managers such as Cargo (but also, for example, npm) make it so easy to drag in hundreds of (transitive) dependencies.
I am currently working on getting my relatively modest project Sausagewiki into compliance with the licenses of all its direct and indirect dependencies. For my ~32 declared crate dependencies I now count 117 crate dependencies in total.
I find it user hostile, and against the spirit of the respective licenses, to simply concatenate 117 license files (or ~200, considering all the dual licensing?) and call it compliance.
That's my basis for reacting in this case; I want to be able to show the user the relevant copyright notices while also showing only one copy of each relevant license.

Another interpretation of cargo's LICENSE-MIT could be that, considering that there is no "above copyright notice", including no copyright notice would trivially be compliance. For now, I am going to go with this interpretation.

I still find the LICENSE-MIT file suspect, but you have given this thought, and I do not consider myself an authority on legal matters. As such, I will now close this issue. But thanks for explaining a little bit 🙂

@maghoff

What do you mean? No lawyer will interpret it as an issue? Or did you mean to call me nobody? 😉 Because here we are.

My apologies, I did not intend to come across that way, and that implication didn't even occur to me. Let me phrase it another way.
Based on the extensive history of license analysis I've seen, in Linux distributions that care scrupulously about licenses and license compliance, in companies that care scrupulously about licenses and license compliance, and in legal review discussions of various types, I've never seen the interpretation suggested that omitting the copyright notice from the MIT license would lead to such a problem. Rather, the prevailing interpretation the few (non-zero) times the subject has ever come up was...

Another interpretation of cargo's LICENSE-MIT could be that, considering that there is no "above copyright notice", including no copyright notice would trivially be compliance. For now, I am going to go with this interpretation.

...exactly this interpretation.
Also:

I find it user hostile, and against the spirit of the respective licenses, to simply concatenate 117 license files (or ~200, considering all the dual licensing?) and call it compliance.

I appreciate your diligence in that. I personally think it's acceptable to aggregate all the licenses directly in a file few people will ever actually read, and to separately summarize the list of licenses that apply in a very brief fashion that just names the licenses (e.g. "incorporates works variously under MIT, MIT/Apache-2.0 dual-license, 3-clause BSD, LGPLv2.1 or later, and GPLv2 or later; for full details see LICENSES-THIRD-PARTY.txt"), for user convenience in knowing what terms apply.

Thank you @joshtriplett ! I appreciate this detailed follow-up immensely, as I am not surrounded by people knowledgeable in this topic.

@joshtriplett I know this issue has been closed already for years, but I didn't want to open an exact one again.

Including a half-formed copyright notice does not have any particular meaning.

At least in the U.S., a singular copyright notice can work for collective works. See, e.g., 17 U.S.C. § 404. This article might give more information on that matter. It seems like consensus is that "copyright © <year> the <project-name> developers" is a valid copyright notice.
That said, I'm not a lawyer, and none of this is legal advice.


Improve Image Fit for Platform "Permanent Land Site"

Issue

When looking for platform "Permanent Land Site" in CASEI https://impact.earthdata.nasa.gov/casei/explore/platforms, the tag "STATIONARY" is showing below.
Desired
Tag "STATIONARY" should not show if an image uploaded to the thumbnail

Update 10 update:

Work is done but we are still having issues with deployment so that need needs to be address to see the fix here.


[MCHECKSTYLE-325] Provided multi-module IT with verification. Provide…

Provided multi-module IT with verification.
Provided documentation highlighting plugin handling of resources in multi-module reactors.

Fixes #MCHECKSTYLE-287
Fixes #MCHECHSTYLE-294

Are have you created one PR for two issues? Can we handle separately, issue by issue? I am willing to merge after review.

Hello there,
Handle them separately is fine; I was simply lazy enough to continue developing in the same repo.
I realized that the same root cause has been the origin of several JIRA issues.
// vänlig hälsning,
// [sw: "best regards"],
//
// Lennart Jörelid

10 juli 2016 kl. 19:52 skrev Michael Osipov<EMAIL_ADDRESS>Are have you created one PR for two issues? Can we handle separately, issue by issue? I am willing to merge after review.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Great, I will wait for new PRs from you.


Direct link to a talent tree not working

Hi,
first of all thank you for your great tool.
I try to implement your talent tree in a website. It's working fine besides one bigger issue.
If you want to open the url of a talent tree where you've already set the skill points you will get a 404 error. On your site it's working as expected.
Example:
If you open https://projects.yoro.dev/df-talents/druid/7hox-1ekg/balance/ on your site it's working fine, but not on others,
Could you give a tip, how did you managed the right loading of the url including the query string?

Hi, thanks for the kind words.
In order for this to work you need to redirect all "subpage" requests to index.html in the calculator's base directory. I'm doing this by configuring .htaccess file.
It should look something like this
RewriteCond %{REQUEST_URI} !(.html|.js|.css)
RewriteCond %{REQUEST_URI} !^(.*).(jpg|jpeg|png|gif|txt|ico)
RewriteCond %{REQUEST_URI} !(.eot|.ttf|.woff)
RewriteRule ^(.*) ./index.html [NC,L]

But this method may not apply to your hosting provider.

Thank you! Works perfectly.


How to trigger SCIPsolveConcurrent?

SCIP provides concurrent solving https://www.scipopt.org/doc-5.0.1/html/CONCSCIP.php. How would i go about triggering it?

First thing would be to compile SCIP with the suitable options.
Second would be to modify slightly the optimize! function to call SCIPsolveConcurrent instead of SCIPsolve here:
function MOI.optimize!(o::Optimizer)
    set_start_values(o)
    if o.objective_sense == MOI.FEASIBILITY_SENSE
        MOI.set(o, MOI.ObjectiveFunction{SAF}(), SAF([], 0.0))
    end
    @SCIP_CALL SCIPsolve(o)
    return nothing
end

PS: up to date documentation page is here:
https://www.scipopt.org/doc-8.0.1/html/CONCSCIP.php

I'll close this one for https://github.com/scipopt/SCIP.jl/issues/242 which is similar.


Add a new icon - globe-checked for claimed website

Add a new icon for claimed website.

Warnings

:warning:

:file_folder: Bundlesize - Bundle size increase detected, please review

Filename
Size Diff
Gzip Diff
Prev Size
Current Size
Prev Gzip
Current Gzip

gestalt.js
:small_red_triangle: 0.4%
:small_red_triangle: 0.8%
268.09 KB
269.2 KB
59.57 KB
60.05 KB

gestalt.es.js
:small_red_triangle: 0.4%
:small_red_triangle: 0.8%
265.46 KB
266.57 KB
59.19 KB
59.68 KB

  Generated by :no_entry_sign: dangerJS

Codecov Report

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

@@           Coverage Diff           @@
##           master     #264   +/-   ##
=======================================
  Coverage   70.24%   70.24%
=======================================
  Files          46       46
  Lines         820      820
  Branches      189      189
=======================================
  Hits          576      576
  Misses        172      172
  Partials       72       72

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a3b08fa...412bc5e. Read the comment docs.

@BigTiannn Thank you!


lambda properties should identify the self parameter as an instance of their containing class

Environment data

Language Server version: 2021.4.3
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): 3.8.5 (tags/v3.8.5:580fbb0, Jul 20 2020, 15:57:54) [MSC v.1924 64 bit (AMD64)]
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: off

Expected behaviour
In a member property initialized with property(lambda self: "foo"), the self parameter should be identified as an instance of the containing class.
Same goes for lambda-initialized methods.
Actual behaviour
The self parameter is untyped (Any).
Code Snippet / Additional information
Consider the following code:
class Test(object):
	property_from_lambda = property(lambda self: self)
	method_from_lambda = lambda self: self
	def classic_method(self): return self

test = Test()
print(test.property_from_lambda)
print(test.method_from_lambda())
print(test.classic_method())

Both property_from_lambda and method_from_lambda are legal instance-bound members, as the test prints prove.
However, in both cases the self parameter is not recognized as an instance of Test:

By comparison, in a "normal" method the self parameter is correctly identified as an instance of Test:

In the tooltip/autocomplete menu, method_from_lambda is identified as a variable; this is more debatable, but IMO it would be more relevant to identify it as a method (tooltip, icon, syntax highlighting etc):

By comparison, this is classic_method:

Please refer to my response in #1230.


Compilation error

Hi,
I'm trying to build and run the project, but I've got the following error :
[ERROR] No plugin found for prefix 'quarkus' in the current project and in the plugin groups
I could not find any help on the subject, would you have any hint ?
Thx

@Christopher-Chianelli Can you please take a look?

@KobNael From which directory are you building the project? With which command are you building the project?

Reproduced:
Build from the root directory and run "mvn quarkus:dev".
@KobNael "mvn quarkus:dev" needs to be run in one of the use-cases subdirectories.
For example: cd use-cases/school-timetabling; mvn quarkus:dev

@KobNael Where did you see the information that led you to believe to run "mvn quarkus:dev" from the root directory? We'd like to improve that docs/readme/guide.

thank you, that did the trick.
It's my bad, I read the readme too fast.
It's clearly written though :  cd optaplanner-quickstarts/use-cases/maintenance-scheduling   ...

Thanks!


domd: set XDG_RUNTIME_DIR for systemd-based weston start

/etc/default/weston is a default place for environment
variables. Put XDG_RUNTIME_DIR into it, since displbe
and display-manager services already referencing that
configuration.
Signed-off-by: Andrii Chepurnyi<EMAIL_ADDRESS>

Acked-by: Volodymyr Babchuk<EMAIL_ADDRESS>

added ack


Eslint and editorsconfig changes.

hi, I'll take a look at pull request, later this day

so, I agree with 99% of the changes, the only thing I would like to discuss more, is the position of the { (open curly brace) I still find it much easier to read code when curly brace is on next line, since it always enforce a new line, so function header is always visible.
what do you think ? @bafxyz and @websoftwares

Why merged ? :-(

Yea why?:(


Differences between sketch and web: misaligned flex boxes

I'm rendering rows that all have equal width cells using flex: 1. The problem is on the web, if the cell has content, the width is not the same as the cells in other rows and it becomes misaligned. Full code to reproduce is here:
import React from 'react';
import { Text, View } from 'react-primitives';

function Row({ children }) {
  return (
    <View style={{ flexDirection: 'row', height: 50 }}>
      <View style={{ borderWidth: 1, borderColor: '#f0f0f0', flex: 1 }} />
      <View style={{ borderWidth: 1, borderColor: '#f0f0f0', flex: 1 }}>
        {children}
      </View>
      <View style={{ borderWidth: 1, borderColor: '#f0f0f0', flex: 1 }} />
      <View style={{ borderWidth: 1, borderColor: '#f0f0f0', flex: 1 }} />
    </View>
  );
}

function Document() {
  return (
    <View style={{ width: 500 }}>
      <Row>hello</Row>
      <Row />
      <Row />
      <Row />
      <Row />
    </View>
  );
}

export default Document;

If you render this in sketch it looks like this, which is correct:

However, rendering on the web shows this:

It's clearly a difference in how flex is treated, but I'd like to know why and if there's any way react-primitives can make it more consistent.

Just a shot in the dark here, but it looks like a padding / margin issue. Have you tried setting padding and margin to 0 on the text element

@andrewgrewell No difference, but I don't think it's a padding issue. It's a flex behavior that I don't understand. As far as I know the sketch layout is how it should look since the content does not overflow.

Ugh if I set flex-basis: 0 it seems to line up. Now to figure out where to fix this.

I noticed in the web implementation of View there is this comment :
// TODO(lmr):
// we should probably ensure that children is not a string, and enforce that those types of
// children be rendered in a `<Text>` component

So maybe try wrapping 'hello' in a Text

Yeah I realized that forget Text, but these are all red herrings.
If I explicitly set flexBasis: 0 it works. I think this is a bug in react-sketchapp's implementation of flex so I'll file there.

https://github.com/airbnb/react-sketchapp/issues/98

This was a bug in react-native-web: https://github.com/necolas/react-native-web/commit/88ddeca0c6b8ad8f2f690e07cd4ede7f9a31d1e2


Add Prometheus Exports to Mongodb Replicaset

What this PR does / why we need it:

Adds option for prometheus compatible metric exports in all pods under the Mongodb-replicaset chart
Fixes some broken TLS chart functionality and allows the metrics exporter to use TLS options

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
First PR into kubernetes/charts 😁

Just signed the CLA with my github! 😄
Also I added dockerfiles for the container but not necessary to the functionality. If it's not wanted, I can drop those files which would reduce the size if this PR.

/assign @foxish

/ok-to-test

Thanks for the feedback! I bumped the version to 3.5 and fixed the conflicts.

/lgtm

@prydonius @ssalaues I'm inclined to revert this PR.

Always adds annotation for Prometheus. You don't need them if you use prometheus-operator.
The Makefile has stuff specific to Google Container Registry in it but the image is on Dockerhub. Why?
Doesn't follow best practices for specifying images.
Most importantly: Uses the admin user for the exporter instea of a user with the clusterMonitor role. This is bad practice and a security risk. We should not have such practices in the chart.

@unguiculus sure, I think we should go ahead and revert this. Once reverted, @ssalaues can re-create a PR to apply the changes and we can try to solve some of the issues you mentioned.

@unguiculus I'll make the requested changes and re create the PR. Thanks!

@ssalaues Thanks. I'll be happy to assist. You can find my on Kubernetes Slack.


[Question]Why is faraday_middleware a development dependency?

Although require faraday_middleware is required according to usage document, why is its dependency is development_dependency? I'm wondering why faraday_middleware is not a runtime dependency.

This is because faraday_middleware is not required.
Please execute the following code:
https://gist.github.com/winebarrel/9c72a245e0469c3011e3809f831de3ef
The sample code uses faraday_middleware because I think that faraday_middleware is often used with faraday_middleware-aws-sigv4.

The sample code uses faraday_middleware because I think that faraday_middleware is often used with faraday_middleware-aws-sigv4.

Now, I get it. Thanks 👍


feat: create table primary keys

ref: https://github.com/truflation/marketplace/issues/34

Log: I will add additional test cases to ensure the function doesn't rerun if the key is present.
Also, will ensure that this functionality doesn't break the pipeline logic.

Log: I will add additional test cases to ensure the function doesn't rerun if the key is present.
Also, will ensure that this functionality doesn't break the pipeline logic.

@georgeciubotaru is this PR good to go now?

@Jarryd-pretorius Yes, requested review from @joequant

@georgeciubotaru Can you test this patch locally?
checkout truflation/truflation-transformers and
pip install .
run the script run-mktables.sh and run-mkdashboard.sh see if anything blows up
Also checkout truflation-ingestors
pip install .
run.sh
See if all works.

Also for something this big, I'd like to target deploying into production over this weekend.

Also since this is a huge database change. I'd like to target pushing to production over the weekend.  Normally this would be Friday evening or Saturday morning Asia time so that if something breaks people don't notice as much.  Also we are going to need to do a full database backup before we deploy.
We've rarely had to make a big database schema change, so this is a big deal.

Log: I will check the scripts
ETA: 1h

Log: During mktables.sh on truflation-transformers, there are 3 errors, Looks like 3 tables are processed but they don't exist
com_numbeo_uk_owned_dwellings
uk_gov_cpih_passenger_transport_by_road
uk_gov_cpih_telephone_and_telefax_equipment___services

They don't break the script running but FYI

Log: getting error on adding Primary key
Query 1 ERROR: BLOB/TEXT column 'table' used in key specification without a key length
Problem:
There are table with columns as text that doesn't have length specification, a solution can be to define something like this
column_name(length) in the primary key declaration, but the issue is with the table column which is a reserved word.
cc @Jarryd-pretorius, @joequant

Log: Testing my solution with using id column as the primary key, with autogenerated uuid

@Jarryd-pretorius, @joequant
Using my option with id column worked during the script checks on both truflation-transformers and truflation-ingestors. (The only thing it takes  much time to run)
The version using all fields as PK is not viable and there are a lot of issues with it (after trying with all  tables)

issue with text fields because of missing length
issue with reserved column names
issue with double type columns

@Jarryd-pretorius, @joequant
Using my option with id column worked during the script checks on both truflation-transformers and truflation-ingestors. (The only thing it takes much time to run)
The version using all fields as PK is not viable and there are a lot of issues with it (after trying with all tables)

issue with text fields because of missing length
issue with reserved column names
issue with double type columns

@georgeciubotaru what is remaining here?

@markholdex Remains the review and merge.

@joequant please re-review.
cc: @Jarryd-pretorius

Log: I will take 1 more hour to double-check the transformers repo if it doesn't fail after the new changes from main

@georgeciubotaru ping Jarryd and Joseph when ready for review. Thx!

@Jarryd-pretorius, @joequant PR is ready for review.
Tested in both apps and without issues

log: pinged @joequant in Telegram

Hi.  This is a very high risk disruptive change that could break the database, and I don't want to check it in without a lot of testing.
I was planning on getting it in last weekend, but the hedge index got in the way.
@georgeciubotaru Can you log into api-test and apply this patch to the tree there?

then on api-test.  run the script run.sh on in truflation-ingestors
then in transformers,. run the scripts run-mktables.sh, run-mkindex.sh, run-mkdashboard.sh

If it runs on api-test for the rest of the week, then I can push it into production this weekend.

Log: will work on that, after finishing with Deadlift

Log: having an issue with running docker workflows in the ingestors repo, still investigating.
@joequant is also, checking.

Log: Was able to publish docker images on both repos, the work is resumed

@georgeciubotaru any updates here?

@markholdex Postponed the deployment because focusing on deployment of the Deadlift index


Entering dungeon landed on downstairs

Procedure
(1) Exit from dungeon
(2) Enter dungeon again
Expected
(3) The party lands on the upstairs (on the 1st floor)
Actual
(3) Somehow the party is on downstairs

party.resumed flag was not cleared after resuming.  The fix will be in the next push.


Add dark mode to Gradle User Manual

Details
This is a Documentation change ONLY.
Context
Many users have requested the support of dark mode for our manual.
Reviewers:

@bot-gradle test BD

BTW: The Kotlin DSL uses a grey/white version of the Gradle logo: https://docs.gradle.org/current/kotlin-dsl/index.html, IMHO the blue Gradle logo is too dark.

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

@bot-gradle clean

@bot-gradle test BD

I've triggered the following builds for you. Click here to see all build failures.

BuildDistributions build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Set up renovate to auto-merge on minor and patch releases

I'm very comfortable with the test coverage for this library, so let's
set up Renovate to auto-merge on minor and patch releases (not major
ones) to reduce the maintenance burden.
Signed-off-by: Juan Antonio Osorio<EMAIL_ADDRESS>

Codecov Report

Merging #117 (e82d501) into main (1c03bc2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #117   +/-   ##
=======================================
  Coverage   97.04%   97.04%
=======================================
  Files          10       10
  Lines         338      338
=======================================
  Hits          328      328
  Misses          7        7
  Partials        3        3

Flag
Coverage Δ

unittests
97.04% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Upgrade gRPC packages across solution to 2.24.0 (=1.24.0)

Upgrade Grpc.Core and Grpc.Tools across solution to 2.24.0. This is equivalent to gRPC version 1.24.0; the major version bump was caused by a breaking changed needed to support .NET Core 3.0.

Actually need to roll this back to 1.22.1. This should fix @LoekL's issue, but there's a problem with using the 2.x.x release caused by a bug in the Platform SDK. Added details to this ticket.


Add library completion for Python modules

This is built against https://github.com/jupyter-xeus/robotframework-interpreter/pull/10, we should wait for a robotframework-interpreter release.

Replaced by https://github.com/jupyter-xeus/xeus-robot/pull/40


Mec15 gpio glitch

Potential fix for #61343
I basically followed https://github.com/zephyrproject-rtos/zephyr/commit/79ee5a876fce82e4bd22f865032567ba2cab9327 and it seems to solve it for MEC15 as well.
Also added a test.
Note: included patches from https://github.com/zephyrproject-rtos/zephyr/pull/61139, otherwise GPIO interrupts don't work for MEC15.

@albertofloyd  can you please review.

Any other comments?

Looks good to us.

@albertofloyd can you help to approve?


Upgrade to Solidity 0.5.13

For some reason this has caused an issue with referencing the built contracts...
@statechannels/nitro-protocol:   5:41  error  Unable to resolve path to module '../../../../build/contracts/SingleAssetPayments.json'  import/no-unresolved

@kerzhner Turned out I had missed a change from 0.5.11 to 0.5.13 and I just didn't notice.


chore: improve home view screen memory consumption

[future-friday]
Description
This PR updates the default rendering values in the home view rails in order to improve the performance and memory consumption.
By default, initialNumToRender is 10 and windowSize is 21. That's fine for vertical lists where more content is visible. In the case of our horizontal lists, we barely show 2 items, and we don't need to render the 10th at initial render.

Before
After

What comes next?

Maybe we can move the constants to a more shared folder and use them in other areas of the app
We can probably be even more aggressive with some rails like shows, fairs and collections which are heavy and be less strict with artwork rails.

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

improve home view screen memory consumption - mounir

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (improve home view screen memory consumption - mounir)

  Generated by :no_entry_sign: dangerJS against c37b56afd0077714f1e9bd07ecc88df2215b924c

Very nice, thanks.
Out of curiosity, this profiling is done in XCode? A quick KS or show-and-tell on that would be great!


Higher resolution charts

Hi
Setting higher devicePixelRatios does not seem to have any effect for any value over 2. Are there any ways around this?
Thanks in advance :)

Hey @Detan-L, unfortunately not at this time.  devicePixelRatio is capped at 2.0, for retina devices.

Setting the format to svg (setFormat) should give you an improved resolution.


Run multiple time the hook

Hello there,
I hope the project is not as abandoned as it looks like.
I have a project with multiple subproject (two in this case) and I want to run composer install inside this two directories. Is there a way to do so ? I can't find a solution for now. I can run composer install in one of the two directory but not in the second. Event if I create another custom task wich reset composer_ variables then invoke composer:run, :install (I think the implementation is good, see below)
Thanks.
Here is a representation of my architecture:
my_root_project
|__ symfony_projecet_1 # I want to run composer install here
|   |__ composer.lock
|   |__ composer.json
|__ symfony_project_2 # I want to run composer install here too
    |__ composer.lock
    |__ composer.json

Implementation of my custom_task:
namespace :portal do

  task :composer do
    on roles fetch(:composer_roles) do
      # Before this set, composer_working_dir is defined like this in the global configuration:
      # set :composer_working_dir, -> { File.join(fetch(:release_path), 'server') }
      set :composer_working_dir, -> { File.join(fetch(:release_path), 'portal') }
      within fetch(:composer_target_path, release_path) do
        invoke 'composer:run', :install, fetch(:composer_install_flags)
      end
    end
  end
end

Thank you for your response.
It's not possible to split the project into multiple parts as these parts are dependent.
I switched to deployer as it is written in PHP, I am more confortable to explore and understand the code. The behavior is the same as capistrano-composer but I can rewrite the hooks and run composer as many time as I want.
If someone find this issue, I think we can do the same with capistrano but as I am not a ruby developer, I can't provide any example or track to do the same.


Startup race condition - sagas injected after dispatched actions don't fire

Description
Suppose a child component of a parent container dispatches an action from the parent container (with useEffect or useLayoutEffect), the action is dispatched before the saga watchers (and even the parent reducer) have started and is thus missed.
If this isn't a bug, what are the best strategies to accomplish something like this. Adding a delay in the use hook seems wrong.
Steps to reproduce
See example
Expected behavior
I would expect the parent's reducers/sagas to be injected by the time the child dispatches the action. In this case, the state should have the new username.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions

React-Boilerplate: dev (master too)
Node/NPM: 6.13.6
Browser: brave/chrome

I have this problem too.

Duplicate of #2845

I had the same problem

https://github.com/react-boilerplate/react-boilerplate/blob/d19099afeff64ecfb09133c06c1cb18c0d40887e/app/utils/injectSaga.js#L51-L58
React.useEffect in injectSaga.js is running after childrens UseEffects. This is a normal flow with react's useEffect. Ex : https://codesandbox.io/s/patient-dream-rsltf
A possible workaround would be to set a state on parent didMount then pass it trough childrens props Ex : https://codesandbox.io/s/priceless-currying-tsdwb

That's a lot of code to handle this situation. Just feels like we've lost something with the useInjectSaga().

FWIW, I encountered this on my project, and we solved it by just attaching the sagas that are called within a useEffect during the configuration of the store.
In a sagaMiddleware.js file,
/**
 * Creates the saga middleware and attaches a function, `afterMount`, that will
 * start any sagas that should not be injected dynamically with `useInjectSaga`
 *
 * @param {Object} sagaMiddlewareOptions Options to pass to the middleware
 * @returns {Object} The saga middleware
 */
export default function createSagaMiddlewareWrapper(
  sagaMiddlewareOptions = {},
) {
  const sagaMiddleware = createSagaMiddleware(sagaMiddlewareOptions);

  // Attach a function to call after mounting the middleware on the store
  sagaMiddleware.afterMount = function afterMount() {
    this.run(languageProviderSaga);
  };

  return sagaMiddleware;
}

and then in configureStore.js,
  ...
  // Extensions
  sagaMiddleware.afterMount();
  store.runSaga = sagaMiddleware.run;
  store.injectedReducers = {}; // Reducer registry
  store.injectedSagas = {}; // Saga registry

Doesn't solve the race condition, using useInjectSaga would be more ideal, but it was an easy enough fix for the short term.

The more I think about it, a better solution is probably to just use the injectSaga HOC, instead of the hook.

Thinking about it even further, the useInjectSaga has a different behavior then the HOC.
While useInjectSaga uses the useEffect hook, which is similar to componentDidMount, the injectSaga HOC uses the constructor. This is what causing the unexpected behavior from children nodes that are using useEffect or componentDidMount.


http://localhost:8086/api/v2/query?org={org} method not allowed

Describe the bug
I am using the queryService.query() to make a query and it is returning a 400 (Bad Request) with the following
{
"code": "method not allowed",
"message": "allow: OPTIONS, POST"
}

To Reproduce
Steps to reproduce the behavior:

Run an influxdb database InfluxDB v2.7.10 (git: f302d9730c) build_date: 2024-08-16T20:19:28Z
Perform a query

 var client = InfluxDBClient(
        url: 'http://localhost:8086',
        token: '<token>',
        org: 'ORG',
        bucket: 'BUCKET',
        client: RemoveUserAgentClient(),
        debug: true);

var queryService = client.getQueryService();
var records = await queryService.queryRaw(''' ... ''');

Expected behavior
Expect a string of records in records
Specifications:

Client Version: influxdb_client: ^2.10.0
InfluxDB Version: InfluxDB v2.7.10 (git: f302d9730c) build_date: 2024-08-16T20:19:28Z
Platform: GCP instance Linux 6.1.0-23-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux

Additional context
I had to strip the user agent info because chrome was erroring out with unsafe header errors if I did not do that. the code for that is
class RemoveUserAgentClient extends http.BaseClient {
  final http.Client _inner = http.Client();

  RemoveUserAgentClient();

  @override
  Future<http.StreamedResponse> send(http.BaseRequest request) {
    request.headers
        .removeWhere((key, value) => key.toLowerCase() == 'user-agent');
    return _inner.send(request);
  }
}

Hi @shaktee,
Thank you for engaging with our client. Just to clarify, are you currently using the client within a web environment?
Is this something you would be willing to help with? All PR is welcome and we will be happy to review your submission.
Best Regards.


HOPS-185 do not reserve GPU containers on CPU machines

Make sure there is no duplicate PR for this issue

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added and passed (for bug fixes / features)
[x] HOPS JIRA issue has been opened for this PR
[x] All commits have been squashed down to a single commit
[x] The commit message has the following format: [HOPS-XXX] message

Post a link to the associated JIRA issue

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Other information:

Jenkins test this please.

Can one of the admins verify this patch?

Jenkins test this please.

Jenkins test this please.


Updating a mail node

Hello,
this probably is a silly question but im trying to update de value of the mail address nodes. Currently i'm doing it by setting the value of the corresponding node, the thing is what I'm writing is a literal, using this
  for await (const emailId of me["vcard:hasEmail"]) {     let email = await data[emailId}].vcard$value.set<EMAIL_ADDRESS>   ); }
This previously shown is not the exact code I'm using but you get what im trying to do, just access the correct node and change its value.
I'm not sure what is the exact type of<EMAIL_ADDRESS>node so what I'm obtaining is something like :id1588664791865 n:value<EMAIL_ADDRESS>and not the expected between <> value. How would be the appropriate way to do it? Thank you in advance

You'll want a NamedNode there, so set(namedNode('mailto:mail@email.com')).

Thank you so much, I recently started using this library so I don't know how it exactly works, guess I need practice.

And documentation… we'll work on that 🙂


Fix package dependencies

The recent rash of packages being unpublished from npm has caused npm install to fail due to reliance on these no-longer-available dependencies.
This PR replaces the broken dependencies with new packages (or more recent packages) so that this package can continue to be installed.
It's worth noting that all the api rest tests seem to be broken, but (to the best of my knowledge) this seems to be a problem with the tests (or the api end point) and not with the code itself.

thanks! this looks great!
i was so busy on the npm side of things i didnt check which of my own modules were impacted.

You're very welcome.  Thanks for making and maintaining these tools/libraries for Pinoccio!


Problem with web_promo

The command promo download only web_promo_small not web_promo
And i can't run targetedoffers command
// Targetedoffers
https://i.imgur.com/gmslZno.png
// Promo
https://i.imgur.com/JYdwaav.png
https://i.imgur.com/JAKoNgA.png
I use windows 10

hey
so the web_promo folder is empty because in the external_variables only small images exist. so there are no large web_promo images only small ones. i should remove the web_promo and only keep web_promo_small instead.
for the targetedoffers im not sure maybe i broke something with the update i made yesterday. can you please try again with an older version like 1.11.2 and see if it still doesnt work?

Always the same concern for targetedoffers

okay weird. i need to test it myself and fix it if its broken but im currently very busy with work so please be patient.
and thanks for the issue report!

Okay i found the problem with the targetedoffers command. Well it isn't really a problem. You are using the Habbo.fr external_variables and there are not targetedoffers defined. So the command is working as intended but it just couldn't find anything. You can however download the targedetoffers from the Habbo.com domain. Just change the domain to com in your config.
Im closing this issue now. Feel free to create a new one if you have questions or anything. Thanks again for your issue report!


Default lighting

Add directional light and ambient light for default lighting of the
scene.

Looks good. :+1:
Let's look for a way to hide the frustum visualization next.


Bluetooth: Host: allow llpm connection interval

Allow nordic connection interval of 1ms to 7ms when connecting.

replaced by https://github.com/nrfconnect/sdk-zephyr/pull/1246


service update - validate and allow only fields that can be updated.

Currently the update simply overrides the complete OCL of an already registered service.
We need to define attributes that can be updated and simply reject if the update is changing even basic things in the OCL.
Eg., version, name cannot be updated. This will break other things.

Discuss what properties can be updated.
Add validation to the update method.

@WangLiNaruto thank you for pro-actively picking up this issue. Much appreciated.


info.rkt: fix license definition

A single "license-id" should not be wrapped in a list.

For reference see:

https://docs.racket-lang.org/pkg/metadata.html
https://github.com/Metaxal/quickscript-test/commit/d6aa7d1a0145901184c47e4439683dd4eb118b71

Signed-off-by: Maciej Barć<EMAIL_ADDRESS>

Thanks Maciej, for taking the time to look over my project! I also used the wrong SPDX short-form license identifier, so I'll also fix that once I merge.
Cheers from Virginia, USA
Jacob


Disallow block comments before markers

Correctly parsing headings, lists, enums, and terms can be difficult for both humans and computers, if a comment is placed in front.
An example that is difficult to parse for humans would be:
- foo
  - bar
    /* comment
*/- baz

See #762 for more examples.
However, this change is primarily motivated by the difficulty in parsing such expressions using tree-sitter.
Producing useful and consistent syntax trees is quite difficult due to limitations of the tool.
I don't think this change will cause much breakage.
Comments before markers seem niche and not very useful to me.

I don't think that this is a good idea. In. my opinion, it is sometimes very useful to select a block of text and comment it when working on a project.
If you disallow this, it'll become way more painful to quickly see how a typst document outputs when removing a specific part.

I commented on #762. I agree that things are a bit wonky, but I'm not sure whether this is the solution or whether a better solution would be to ignore comments for indent purposes (as if each character and the comment markers were whitespace). That would make some of the examples clearer to parse for humans imo. Would it help with tree-sitter?

Writing a response to @laurmaedje's comment gave me an idea on how to correctly parse markers.
That means, after many hours of trying to make it work, I was able to write a functioning parser that allows for block comments in front of headings.
Without any major drawbacks!

As it is right now, I know of two bugs with the implementation. One of them likely existed earlier already. Neither should be hard to fix.

I commented on #762. I agree that things are a bit wonky, but I'm not sure whether this is the solution or whether a better solution would be to ignore comments for indent purposes (as if each character and the comment markers were whitespace). That would make some of the examples clearer to parse for humans imo. Would it help with tree-sitter?

Yes, I would suppport that change. It would make the syntax easier for humans to reason about and doesn't seem difficult to parse.

Alright, then let's do that change.


Fix typo in config.go

This fixes a typo in the config.go file:
CilliumEndpoint -> CiliumEndpoint
Signed-off-by: Maartje Eyskens<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[x] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Thanks for contributing!

Fix a typo in pkg/option/config.go

(is there a way to say no release note is needed?)

/test


Fix the trades of Luna not loading bug

The name old Luna has been changed to LUNC.
Old holder of Luna had been given LUNA.
We need to handle this issue as the exchange we used

This is a new account and middle office. No longer need to deal with the luna issue!


SectionList not properly typed

Description
SectionList's props does not infer the type from the data prop. Similar to #4469 but for SectionList.
CodeSandbox/Snack link
/
Steps to reproduce
No response
NativeBase Version
3.3.4
Platform

[X] Android
[ ] CRA
[ ] Expo
[X] iOS
[ ] Next

Other Platform
No response
Additional Information
No response

@codakkk Thanks for reporting! We're looking into this.

This issue has been fixed in version 3.3.6.


I think i have solved your problem for writing GUI apps for Windows

I have just read your blog post:
https://tulach.cc/writing-gui-apps-for-windows-is-painful/
We have figured out a way to use clang directly. Here is an example:
https://github.com/trcrsired/winrt-toys/blob/main/0003.hellogeo/main.cpp

https://github.com/[trcrsired/windows-msvc-sysroot](https://github.com/trcrsired/windows-msvc-sysroot)