matrix-synapse: 1.9.1 -> 1.11.1

Motivation for this change
This updates matrix-synapse to 1.11.1.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test matrix-synapse postgresql

I fixed pythonPackages.signedjson https://github.com/NixOS/nixpkgs/pull/80449, not sure if you just want to pull the changes into this pr or not

Anyone got an idea how this can be backported to 19.09 or any following release for that matter as we would add some changes to the postgresql module which might not be desired.

I'm actually using this on 19.09 already (my matrix HS is still running 19.09 on a custom branch based on release-19.09 with this change cherry-picked on top) and the database still works fine (you get a warning at the beginning though), so it should be fine (considering the fact that 19.09 will only live for a few months at most).

(however, I do think it totally makes sense to backport to 20.03, because even though we're technically past cut-off time, we haven't said it's stabilized yet, and the risk of breakage in the following 9 months is quite high, given we're speaking of synapse)

(however, I do think it totally makes sense to backport to 20.03, because even though we're technically past cut-off time, we haven't said it's stabilized yet, and the risk of breakage in the following 9 months is quite high, given we're speaking of synapse)

Just for the record: we backported every release of matrix-synapse to stable in the past (at least since I'm taking care of the package) as many releases either contained important bugfixes or were needed due to some infrastructure changes at matrix.org that would break a self-hosted synapse otherwise.

Just updated matrix-synapse to the latest upstream version (1.11.0).

Let me try to summarize the issue here and propose some solutions:
matrix-synapse 1.10 requires LC_CTYPE and LC_COLLATE to be set to C when using a postgresql database for persistence (which basically means that postgresql should ignore any locale-preferences: https://www.postgresql.org/docs/12/locale.html). This only affects new databases, existing databases will remain usable, but matrix-synapse will start with a warning.
I'm also pretty sure that the majority of setups isn't affected by this since the database was configured properly in 19.09 and older. Since b2d67c08d03679ba1b9a928ac5610ad940846e7f the matrix-synapse module uses the ensure* options that don't configure the database properly (this change is only on nixos-unstable).
My original solution added the lc_{ctype,collate} options to the ensureDatabases option in the postgresql-module. As @grahamc noted this has the downside that we break declarativity here: the options won't be taken into account if the database already exists, so if we want to "ensure" a database to exist, but it already exists, the database won't be configured properly. I'd also like to mention that I'm pretty much against automated migration since Nix isn't designed to handle application's state at the moment and there's a lot of stuff that can go wrong (e.g. when using nixops deploy --allow-reboot).
I can currently think of the following solutions:

drop database management entirely and do the setup in the test. This will only affect new setups as existing setups already have an existing database. This is already done for nextcloud, codimd, slurm and a few more (my preferred solution atm).

Use initialScript in the module (this is probably a bad idea since the database won't be configured if matrix-synapse is deployed to a machine with an already existing postgresql since initialScript will only be used at the very first startup of postgresql).

Leave it as it is. This has the downside that new matrix-synapse setups will probably have trouble upgrading since the database-creation will be done again since /var/lib/matrix-synapse/db-created doesn't exist.

I think the best solution is to remove the database configuration entirely for now.
@mguentner @fpletz @fadenb @aanderse @grahamc @kampka  thoughts on this?

Maybe the declarativity can be helped with naming? Like using create_time_lc_collate instead of lc_collate or something similar that signifies that it only affects new databases.

Leave it as it is. This has the downside that new matrix-synapse setups will probably have trouble upgrading since the database-creation will be done again since /var/lib/matrix-synapse/db-created doesn't exist.

Instead of checking the existence of that flag file, we could check the existence of the role and database directly and initialise those only if they don't, in some idempotent transaction executed in the preStart phase as @aanderse suggested.  This should be compatible with all the previous automatic initialisation methods used in this module in the past.

I just discussed the issue with @fpletz today. We decided that the best solution for now is to remove the database handling entirely (as it's implemented in several other modules). The change will be documented and users can copy configurations from the VM test or the docs for a database setup.
New users will have to take care of their database on their own, users with existing setups won't have any issues as the database is configured already.
If you deploy an existing configuration to a new machine, the missing database-setup will be detected by an assertion which instructs the user to either configure the database manually or to provide a database on a foreign host.
The change is currently work in progress :)

Just had a short chat with @aanderse this afternoon about this where we both agreed that it's the best solution for now to drop the database configuration since Nix lacks proper safety measures for application-state handling.
Additionally, if we add an idempotent setup later, it shouldn't be too complicated to add this to the matrix-synapse module IMHO.
@GrahamcOfBorg test matrix-synapse
@grahamc after several discussions I decided that it's best for now to drop the database configuration for now. I should also mention that I fully agree with your concerns after thinking a little bit more about this :)
@fpletz and I think that we should merge (and backport) this soon though since this fixes an actual security issue of matrix-synapse.

Please don't merge it yet. @florianjacob made some good suggestions about how we should document this and I'd like to add this (already started working on it) first :)

@GrahamcOfBorg test matrix-synapse

Just pushed a change which fixes a minor typo in the docs. As soon as the eval is finished, I'll merge this now. The latest changes from Sunday were documentation-related (and reviewed by @mguentner), the actual update has been discussed pretty much now and should be mergable.
Also, I'm running matrix-synapse 1.11.1 on NixOS 19.09 for a while now without any issues, the change should be fairly safe to use (and to backport).
Thanks a lot for everyone involved here!

Thanks for all your work on this @Ma27 :tada:

Backported to stable:

20.03: 7f8e302fb6513d1d5b59f22a9948a5610ca75296, ba6271a49c6079e0223ee9a166d6a65b0de05445, 23139ff62fb08f7bf7b3a4efc30e6e798d9f7e26
19.09: a9d474652f740fbdbf4c0e29158e26508d17a01a, dce33f1a2d491489ad044259c7d06d8870a205fb

Thanks for everyone involved, especially @Ma27

Could you please have a look at this PR https://github.com/NixOS/nixpkgs/pull/339195 ?  I need some help since I haven't write a unit test for postgresql (especially in nixpkgs) before


Current NPM repo does not have Jimp.loadFont and Jimp.prototype.print in jimp.d.ts

The current repository in NPM seems to miss the print method, as well as the static loadFont method, even though it is the same version as the GitHub repo, and checking the file on this repo, it does have those to typings. Maybe the NPM repo isn't updated properly ?
Using the master branch of the GitHub repo as a dependency in my package.json file does the trick.
I used version ^0.2.28 in my dependencies.

Yes, i get the error info :
UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined

closing in favor of #484


Deep drill unable to be operated

Describe the bug
IMPORTANT: Please first search existing bugs to ensure you are not creating a duplicate bug report.  (Didnt see anything that sounded similar)
Neither Colonists nor non-colonist workers can access the deep drill. I can not order them to focus on working at the deep drill as right-clicking on the deep drill shows no jobs available (reflected in log file, UI exception)
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Error Log
Link to contents of Player.log or Error.log (Please use something like gist or pastebin. DO NOT PASTE HERE)
https://pastebin.com/qjKKMMnG
Mod List
Paste contents of ModList used when bug occurred.
https://gist.github.com/9273f9f05e6750e7935678a6a5a4751c
Screenshots
If applicable, add screenshots to help explain your problem.

Please see:

Q&A

Mod Compatibility

Known Issues

The Community Modpack

This Mod Order Guide

Address the problems in your mod list before asking for help or submitting errors & bug reports!

You can submit a bug report here

If your submitted issue gets closed and the bug is still happening you can re open the issue.


Keep App Center alive

I am lost for words over the news that App Center is being retired. Many users rely heavily on App Center for the building, testing and distribution of their apps.
This is a feature request to reconsider a decision that will affect thousands of users who rely heavily on App Center.

It is sad, but it seems MS' heart is elsewhere now. There haven't been many meaningful updates in a long time.
Big thanks to the AppCenter team for all the work they put in! Analytics & Diagnostics have been very helpful to me and it is a shame to see it go.

The retirement post for context - https://learn.microsoft.com/en-us/appcenter/retirement

I am very appreciative of all the hard work the App Center team has put in, but decisions like these make it hard  for developers to ever trust and invest in any new solutions Microsoft put out.

That is very unfortunate. Had someone at Microsoft Xamarin/MAUI in mind? They only mention iOS & Android in the retiremant information.
The Microsoft Partner Center seems not to be updated in years and looks very abandoned.
Is .net MAUI dead already?

I guess since the Xamarin rebranding chaos to .net and the many shutdowns in microsoft solutions there are many reasons for my clients to disbelieve microsoft. Its a constant snowball of shutting down services and platforms issues.

Guys, I‘m sharing your toughts 100%. AppCenter is/was a very valuable tool and our team was also very surprised to hear the news of its retirement. Does anyone know the reason behind this decision?
No matter what happens, .NET has a huge and very capable developer community. I‘m pretty sure soon we will see new solutions to replace AppCenter in the near future, trust me.

Doubt it. They have been shutting down services for a few years now. The
migration from xamarin to .net is rather disruptive and so on. Our project
has been affected by these for over 5 years now and its hard to sell
microsoft to my clients anymore.
Appcenter has been completely stale for over 2 years now. Even the build
versions have had serious delays to keep up. It honestly feels like there
is literally 1-2 guys doing all the job
El vie, 15 mar 2024, 19:06, Thomas Galliker @.***>
escribió:

Guys, I‘m sharing your toughts 100%. AppCenter is/was a very valuable tool
and our team was also very surprised to hear the news of its retirement.
Does anyone know the reason behind this decision?
No matter what happens, .NET has a huge and very capable developer
community. I‘m pretty sure soon we will see new solutions to replace
AppCenter in the near future, trust me.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/appcenter/issues/2622#issuecomment-2000284850,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZXKR6RPTBX7ZMZDWF6KXLYYNBEPAVCNFSM6AAAAABEXA3M4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBQGI4DIOBVGA
.
You are receiving this because you commented.Message ID:
@.***>

@jfversluis Gerald, could you help us in understanding Microsoft decisions all around Xamarin and Maui? Our clients starting to avoid Ms technologies because of uncertainity of supporting services. Many people here have many questions today aboud App Center.

Hi!
Can anyone share his thoughts on how to use Google Play or App Store Connect for testing internal dev-builds without occasionally promotiing it to the production?
We do mobile games and our dev-builds contain code not intended for production like cheats, developer UIs etc.
Usually we used App Center for distributing these "dangerous" builds to internal testers.
How are we assumed to do that then?

I implemented own server for apk distribution.
It is not complicated thing.
Also implementes ABIs selection for apk, so files are smaller.
In app you must implement requesting package installer thats all.

@brzezinol

I implemented own server for apk distribution.

That is cool!!
Can you share more details??
Is it some open source tool??

@RahulSDeshpande
there is no opensource solution, I wrote simple mvc app for distributing files for customers, apps, and releases.
In this case there are apk files.
In Android app you need to implement process of:

request update info
download file from your apk server
invoke package installer after file is downloaded.
all of this things are available in web.

I could help you in some details if you have problems.


Update dev guide from _opensearch-sdk-1 to _opensearch-sdk-java-1 in example curl command

Signed-off-by: Craig Perkins<EMAIL_ADDRESS>Description
The example curl command in the developer guide still uses the legacy _opensearch-sdk-1 route from before this repo was renamed to opensearch-sdk-java. The example extensions.yml file uses opensearch-sdk-java-1 so the curl should match.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #391 (7463fd2) into main (9882630) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##               main     #391   +/-   ##
=========================================
  Coverage     69.35%   69.35%
  Complexity      126      126
=========================================
  Files            27       27
  Lines           558      558
  Branches         15       15
=========================================
  Hits            387      387
  Misses          162      162
  Partials          9        9

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I recall a conversation where /.../_hi/hello was a little too book-of-mormon-ish ;). I would be in favor of hw or example-1

I would be in favor of hw or example-1

Or custom-id.  Whatever it is needs to communicate that the user has the choice.
Again, we can merge this and decide on something later.


Extensions not working on iPhone Tableau Mobile app

Hi,
I am testing extensions for a customer of us on the Mobile app.
I am using a iPhone XS with IOS 13.3.1.
Chrome for IOS: Working
Safari for IOS: Not working by default
Tableau Mobile App: Not working
I changed some of my settings of Safari under the 'private and security' tab. I have disabled 'Do not Track' and 'block all cookies' and extensions are working on Safari for IOS now.
However I was assuming these same settings would apply to the Tableau Mobile app with the built in browser. But this is not the case. No extensions are working on the mobile app.
This has a very big impact for this large Tableau user.
Do you have any tips on getting extensions to work on Mobile?
Does this require a change in the Mobile App?

Merlijn:
Are these sandboxed extensions you are testing, or just any extension?
Thanks,
John

To be specific: Any extension developed by AppsforTableau.
Sandboxed aren't working because the customer want on-premise extensions only.

Okay, thanks. We will investigate.

Hi Merlijn:
It appears that the AppsforTableau web server doesn't play well with the latest versions of Safari.
Safari 13.1 on MacOS Catalina cannot run your extensions. I see the following errors both on Catalina, and on iOS 13.3.1:
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) (bootstrap.min.css, line 0)
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) (commons.js, line 0)
[Error] Failed to load resource: the server responded with a status of 403 (Forbidden) (index.js, line 0)
Meanwhile, socket.io.js loads fine.
 I'm wondering if there is something in the request header when it comes from an iframe that your server doesn't like.
Let us know what you find.
Thanks,
John

Hi John,
Thank you for investigating!
Are you debugging mobile or are you trying to load the extension in your browser directly?
We are doing checks on our machine on the location of the request.
In your experience, should all extensions work on mobile?

I was running directly in the browser on both an iPad, and iOS Simulator. I then ran on Safari on MacOS, and found the same behavior there.
I also tried (but did not debug) in Tableau Mobile. I have another extension that I tried in all three places.
We have some minor reported bugs on Tableau Mobile, but in general, yes, extensions should work on mobile.

I have fixed it, thank you for your investigation :)

Great news. Thanks for the update.


feat: persist size of right chat

Is your feature request related to a problem? Please describe.
It would be nice to persist the size of right chat so when I close my window and come back I still have the same size of chat that I had.
Describe the solution you'd like
When I reload page my right chat has the same size.
Additional context
We can use localStorage to persist the size.

sgtm!

@AdamSchinzel just merged this in #59, you can close this whenever convenient!


Remove uuid from svcat get output

When using svcat, the uuid loses its importance because svcat understands how to work with the external names. I propose that we not display uuid in the svcat get command output. When someone wants to know the uuid, fore example so that they can use it in a kubectl command, they can look it up with svcat describe.
In it's place, I'd like to make the broker more visible (see https://github.com/kubernetes-incubator/service-catalog/issues/1749). I'm showing the final output that I'd like even though these are two separate issues (this one is just for not displaying uuid)_. 😀
$ svcat get classes
            NAME                      BROKER                         DESCRIPTION
+--------------------------+---------------------------+--------------------------------------+
  azure-rediscache            osba                        Azure Redis Cache
                                                          (Experimental)
  redis                       Minibroker                  In-cluster installation of Redis

$ svcat get plans
        NAME                  CLASS                      BROKER                   DESCRIPTION
+------------------+--------------------------+----------------------+----------------------------------------+
  basic              azure-rediscache           osba                    Basic Tier, 250MB Cache
  redis-5-7          redis                      Minibroker              In-cluster installation of Redis 5.7

I think there is still some value in being able to query based on UUID, I hope that aspect was not removed. Maybe the uuid column can be optionally shown?

Nothing has been implemented yet, this is just a suggestion. It wasn't my intention of removing the --uuid flag supporting uuid queries. I just want remove it from the default columns displayed in the get output table.

Closed by #1977


Miri errors on the timer_wheel module. (Miri v0.1.0 8b2459c1 2024-04-09)

Miri started to report errors on the test for the moka::common::timer_wheel module.
https://github.com/moka-rs/moka/actions/runs/8629705772/job/23654526179
$ cargo +nightly miri -V
miri 0.1.0 (8b2459c1 2024-04-09)

The errors change when Stacked Borrows is used, or Tree Borrows is used.
Miri's Stacked Borrow
$ cargo +nightly miri test timer_wheel --features 'sync, future'

running 2 tests
test common::timer_wheel::tests::test_advance ... error: Undefined Behavior: trying to retag from <704136> for SharedReadOnly permission at alloc237477[0x0], but that tag does not exist in the borrow stack for this location
   --> /Users/tatsuya/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/ptr/non_null.rs:402:18
    |
402 |         unsafe { &*self.as_ptr().cast_const() }
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                  |
    |                  trying to retag from <704136> for SharedReadOnly permission at alloc237477[0x0], but that tag does not exist in the borrow stack for this location
    |                  this error occurs as part of retag at alloc237477[0x0..0x28]
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
    = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
help: <704136> was created by a Unique retag at offsets [0x0..0x28]
   --> src/common/deque.rs:172:37
    |
172 |             let node = NonNull::new(Box::into_raw(node)).expect("Got a null ptr");
    |                                     ^^^^^^^^^^^^^^^^^^^
help: <704136> was later invalidated at offsets [0x0..0x28] by a SharedReadOnly retag
   --> src/common/timer_wheel.rs:517:55
    |
517 | ...                   let entry_info = unsafe { node_p.as_ref() }.element.entry_info();
    |                                                 ^^^^^^^^^^^^^^^
    = note: BACKTRACE (of the first span) on thread `common::timer_wheel::tests::test_advance`:
    = note: inside `std::ptr::NonNull::<common::deque::DeqNode<common::timer_wheel::TimerNode<u32>>>::as_ref::<'_>` at /Users/tatsuya/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/ptr/non_null.rs:402:18: 402:46
note: inside closure
   --> src/common/deque.rs:162:48
    |
162 |         self.tail.as_ref().map(|node| unsafe { node.as_ref() })
    |                                                ^^^^^^^^^^^^^
    = note: inside `std::option::Option::<&std::ptr::NonNull<common::deque::DeqNode<common::timer_wheel::TimerNode<u32>>>>::map::<&common::deque::DeqNode<common::timer_wheel::TimerNode<u32>>, {closure@src/common/deque.rs:162:32: 162:38}>` at /Users/tatsuya/.rustup/toolchains/nightly-aarch64-apple-darwin/lib/rustlib/src/rust/library/core/src/option.rs:1072:29: 1072:33
note: inside `common::deque::Deque::<common::timer_wheel::TimerNode<u32>>::peek_back`
   --> src/common/deque.rs:162:9
    |
162 |         self.tail.as_ref().map(|node| unsafe { node.as_ref() })
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
note: inside `common::timer_wheel::TimerWheel::<u32>::reset_timer_node_positions`
   --> src/common/timer_wheel.rs:335:16
    |
335 |         while !deque.peek_back().unwrap().element.is_sentinel() {
    |                ^^^^^^^^^^^^^^^^^
note: inside `<common::timer_wheel::TimerEventsIter<'_, u32> as std::iter::Iterator>::next`
   --> src/common/timer_wheel.rs:492:17
    |
492 | /                 self.timer_wheel
493 | |                     .reset_timer_node_positions(self.level, i as usize);
    | |_______________________________________________________________________^
note: inside `common::timer_wheel::tests::test_advance`
   --> src/common/timer_wheel.rs:751:32
    |
751 |         assert_eq!(expired_key(expired_entries.next()), 1);
    |                                ^^^^^^^^^^^^^^^^^^^^^^
note: inside closure
   --> src/common/timer_wheel.rs:647:22
    |
646 |     #[test]
    |     ------- in this procedural macro expansion
647 |     fn test_advance() {
    |                      ^
    = note: this error originates in the attribute macro `test` (in Nightly builds, run with -Z macro-backtrace for more info)

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to 1 previous error

error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/Users/tatsuya/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/cargo-miri runner /Users/tatsuya/Documents/git-repos-ssd/moka-rs/worktrees/fix-ci/moka-012-2/target/miri/aarch64-apple-darwin/debug/deps/moka-445381416204669a timer_wheel` (exit status: 1)
note: test exited abnormally; to see the full output pass --nocapture to the harness.

Miri's Tree Borrow
$ MIRIFLAGS="-Zmiri-tree-borrows" cargo +nightly miri test timer_wheel --features 'sync, future'

running 2 tests
test common::timer_wheel::tests::test_advance ... error: Undefined Behavior: write access through <679865> at alloc237007[0x20] is forbidden
   --> src/common/deque.rs:208:13
    |
208 |             (*next.as_ptr()).prev = node.prev;
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ write access through <679865> at alloc237007[0x20] is forbidden
    |
    = help: this indicates a potential bug in the program: it performed an invalid operation, but the Tree Borrows rules it violated are still experimental
    = help: the accessed tag <679865> is a child of the conflicting tag <679827>
    = help: the conflicting tag <679827> has state Frozen which forbids this child write access
help: the accessed tag <679865> was created here
   --> src/common/deque.rs:172:37
    |
172 |             let node = NonNull::new(Box::into_raw(node)).expect("Got a null ptr");
    |                                     ^^^^^^^^^^^^^^^^^^^
help: the conflicting tag <679827> was created here, in the initial state Reserved
   --> src/common/timer_wheel.rs:245:37
    |
245 |                 let node = unsafe { Box::from_raw(node.as_ptr()) };
    |                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: the conflicting tag <679827> later transitioned to Active due to a child write access at offsets [0x20..0x28]
   --> src/common/deque.rs:171:13
    |
171 |             node.prev = self.tail;
    |             ^^^^^^^^^^^^^^^^^^^^^
    = help: this transition corresponds to the first write to a 2-phase borrowed mutable reference
help: the conflicting tag <679827> later transitioned to Frozen due to a reborrow (acting as a foreign read access) at offsets [0x0..0x28]
   --> src/common/timer_wheel.rs:517:55
    |
517 | ...                   let entry_info = unsafe { node_p.as_ref() }.element.entry_info();
    |                                                 ^^^^^^^^^^^^^^^
    = help: this transition corresponds to a loss of write permissions
    = note: BACKTRACE (of the first span) on thread `common::timer_wheel::tests::test_advance`:
    = note: inside `common::deque::Deque::<common::timer_wheel::TimerNode<u32>>::move_to_back` at src/common/deque.rs:208:13: 208:46
note: inside `common::deque::Deque::<common::timer_wheel::TimerNode<u32>>::move_front_to_back`
   --> src/common/deque.rs:225:22
    |
225 |             unsafe { self.move_to_back(node) };
    |                      ^^^^^^^^^^^^^^^^^^^^^^^
note: inside `common::timer_wheel::TimerWheel::<u32>::reset_timer_node_positions`
   --> src/common/timer_wheel.rs:336:13
    |
336 |             deque.move_front_to_back();
    |             ^^^^^^^^^^^^^^^^^^^^^^^^^^
note: inside `<common::timer_wheel::TimerEventsIter<'_, u32> as std::iter::Iterator>::next`
   --> src/common/timer_wheel.rs:492:17
    |
492 | /                 self.timer_wheel
493 | |                     .reset_timer_node_positions(self.level, i as usize);
    | |_______________________________________________________________________^
note: inside `common::timer_wheel::tests::test_advance`
   --> src/common/timer_wheel.rs:751:32
    |
751 |         assert_eq!(expired_key(expired_entries.next()), 1);
    |                                ^^^^^^^^^^^^^^^^^^^^^^
note: inside closure
   --> src/common/timer_wheel.rs:647:22
    |
646 |     #[test]
    |     ------- in this procedural macro expansion
647 |     fn test_advance() {
    |                      ^
    = note: this error originates in the attribute macro `test` (in Nightly builds, run with -Z macro-backtrace for more info)

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to 1 previous error

error: test failed, to rerun pass `--lib`

Caused by:
  process didn't exit successfully: `/Users/tatsuya/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/cargo-miri runner /Users/tatsuya/Documents/git-repos-ssd/moka-rs/worktrees/fix-ci/moka-012-2/target/miri/aarch64-apple-darwin/debug/deps/moka-445381416204669a timer_wheel` (exit status: 1)
note: test exited abnormally; to see the full output pass --nocapture to the harness.

The error should be fixed by #416.
The code that was causing the error (Stacked Borrows/Tree Borrows violation) was enabled only when testing (#[cfg(test)]), so the release and debug builds had no issue.


my changes

added a link that provided good examples of column databases and how they are stored inside the database

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Reason: We do not accept PRs which only add links when there are already valid reference links for the article.
Thank you and happy coding.


RAM Backup is modifying Archive

When I use the RAM backup feature, it seems to also back up Archive memory, which is frustrating as I have lost considerable progress when resetting my calculator because Cesium will overwrite programs with the last backed up version, when the program was never in RAM, neither when I backed up or when I reset.

No, this is the OS - it rebuilds the symbol table from flash and discovers whatever was archived.


Can't assign self as reviewer of other user's PRs

Gitea version (or commit ref): v1.13.0-rc1
Git version: n/a
Operating system: Ubuntu

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[x] Yes (URLs inline)
[ ] No

Description
There seem to be multiple bugs with permissions around assigning reviewers:

As an administrator assigned to a repository, I cannot edit reviewers for a pull request and e.g., assign myself, even though it isn't my PR.

As user1, create user1/testing1

As user1, add cipherboy-user2 as an administrator to the repo:

As user1, open a pull request.

As cipherboy-user2, try to assign myself to review the pull request. However, I don't have permission to even edit reviewers -- shouldn't administrator collaborators have this access:

As an owner (cipherboy-user2 and user1) in an organization which has repos, I (cipherboy-user2) can edit PR's reviewers (yay! -- on individual repos I can't) but I can't assign myself as a reviewer on another user's PR. I can only assign other people (user3) as reviewers.

Using user1 above, opens a PR in an organization with multiple owners.

Using cipherboy-user2 above, tries to assign cipherboy-user2 as a reviewer.  -> cipherboy-user2 doesn't show up in the list. Can only assign other users (say, user3).

However, user1 can assign other reviewers (such as cipherboy-user2) just fine.

Note: I believe both 1 and 2 to be the same issue just in different permission models (user's repo vs org's repos). Its just that my single user repo had only two people added, whereas the org had three people. If another user is added to the repo, cipherboy-user2 can assign cipherboy-user3 to review user1's PR.
Screenshots
Provided above, inline.

but I can't assign myself as a reviewer on another user's PR. I can only assign other people (user3) as reviewers.

Assigning reviewer sends notification and requests review from specified user; doing it for yourself is illogical in my opinion, if you wish to leave review just leave it and you'll be added as reviewer automatically.

@CirnoT -- I disagree. It is really helpful when maintaining projects. GitHub shows all of your active review requests here: https://github.com/pulls/review-requested -- when triaging incoming PRs/... you can assign yourself as a reviewer so you can come back to them later.
One of the projects I've contributed to, the maintainer ultimately merging the PR was the final assignee, whereas reviewers were requested using the reviewers request field.

I just wanted to create this issue myself. I would like to use this feature to mark for myself and for other users that I am planning on reviewing this PR at a later time in my project.
I do not think there could be any harm from allowing this.

Hmm, I think it's ok to allow a self review request. Just skipping notification is enough. but sadly gitea does not have filter option about review and review-request in search pull request list like gh.so I wonder whether it is useful.

I think this issue can be closed as you can request yourselve on other pulls ...


Link /etc/profile to /etc/zprofile with zsh is installed

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

Ugh, I hate when that happens!


Dependabot/nuget/nunit 4.0.1

tests run but

test explorer does not execute/show atm...

deleting bin and obj folders helped ...

-> Not really an issue -> branch is okay


Remove 'quit' attribute

It's set in a few places but it's never read by anything, and removing
it can simplify the API significantly.
This work was sponsored by Sourcegraph.

Thanks


Added French structure-filters.md & structure-widgets.md and improved structure-views.md [skip ci]

Q
A

Is bugfix?
yes/no

New feature?
yes/no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

Thank you!

Thank you for merging my work.
Could you please answer a question I have:
"When looking at this page https://github.com/yiisoft/yii2/tree/master/docs/guide-fr , I can see that some titles of second level have a TBD mark in front of them. Moreover the title is not translated even if the corresponding file is. What does this TDB stand for?"

To be done.

Could you be more accurate ? Does this mean that the file is not fully achieved and doesn't deserve translation at the time being?

It means original has some significant parts to improve. Currently these are:

One section in tabular input called "Combining Update, Create and Delete on one page".
APIDoc extension documentation.
Core widgets.


How long does training take and how many GPUs do you use?

Thankyou for your work!!
I have a question : does using diffusion as a backbone require a long training time? Looking forward to your reply, Thanks!!!

Hi! We use LoRA for training, which costs much lower than training the whole U-Net. However, due to the large scale of dataset, it will take about 3 days on 8 4090 GPUs if training from the scratch. We highly recommend you to finetune from our released models.


hap over wan

Hello,
I connect the HAP in LAN mode without problem, buy if I go out my home, I loss my wifi connection and don´t work.
Is it possible use it by WAN?, what is the port for foward?
thank you

For remote connection you need an Apple TV as HomeKit hub!

Actually it is possible w/o AppleTV or an iPad. You need a VPN connection to your home LAN, then run a DNS proxy that bridges the HAP mDNS info to your VPN subnet.


Non-existent modules on the Internet

When running nosetests as outlined by issue #5, the following modules do not seem to exist.  They are likely internal modules that should either be removed or bundled with Treadmill:
webauthd
proiddb
plugins.fs
The following is the trail of errors illustrating which tests are picking these up:
ERROR: Tests optional container features.
Traceback (most recent call last):
File "/home/tome/treadmill/tests/appmgr/manifest_test.py", line 266, in test__add_features
treadmill.appmgr.manifest._add_features(manifest)
File "/home/tome/treadmill/lib/python/treadmill/appmgr/manifest.py", line 188, in _add_features
raise Exception('Unsupported feature: ' + feature)
Exception: Unsupported feature: webauthd
-------------------- >> begin captured logging << --------------------
treadmill.appmgr.manifest: ERROR: Unable to load feature: webauthd
Traceback (most recent call last):
File "/home/tome/treadmill/lib/python/treadmill/appmgr/manifest.py", line 183, in _add_features
'treadmill.appmgr.features.' + feature
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
ImportError: No module named webauthd
--------------------- >> end captured logging << ---------------------
======================================================================
ERROR: Test the normalization of manifests.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1297, in patched
arg = patching.enter()
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1353, in enter
self.target = self.getter()
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1523, in
getter = lambda: _importer(target)
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1210, in _importer
thing = _dot_lookup(thing, comp, import_path)
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1199, in _dot_lookup
import(import_path)
ImportError: No module named proiddb
======================================================================
ERROR: Test AppMgr environment initialization.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched
return func(*args, **keywargs)
File "/home/tome/treadmill/tests/appmgr_test.py", line 67, in test_initialize
app_init.initialize(self.app_env)
File "/home/tome/treadmill/lib/python/treadmill/appmgr/initialize.py", line 16, in initialize
nodeinit.initialize(tm_env)
File "/home/tome/treadmill/lib/python/treadmill/osmodules/linux/nodeinit.py", line 20, in initialize
fs.init_plugins(tm_env.root)
File "/home/tome/treadmill/lib/python/treadmill/fs.py", line 253, in init_plugins
for mod in _iter_plugins():
File "/home/tome/treadmill/lib/python/treadmill/fs.py", line 235, in _iter_plugins
fsplugins = importlib.import_module('treadmill.plugins.fs')
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
ImportError: No module named plugins.fs

apiproxy module is also missing:
======================================================================
ERROR: Failure: ImportError (cannot import name apiproxy)
Traceback (most recent call last):
File "/home/centos/treadmill/.tox/py27/lib/python2.7/site-packages/nose/loader.py", line 418, in loadTestsFromName
addr.filename, addr.module)
File "/home/centos/treadmill/.tox/py27/lib/python2.7/site-packages/nose/importer.py", line 47, in importFromPath
return self.importFromDir(dir_path, fqname)
File "/home/centos/treadmill/.tox/py27/lib/python2.7/site-packages/nose/importer.py", line 94, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
File "/home/centos/treadmill/tests/sproc/apiproxy_test.py", line 11, in
from treadmill.sproc import apiproxy
ImportError: cannot import name apiproxy


Missing Configuration Parameters for Zooz Zen20

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
I received the below configuration parameters from Zooz tech support after inquiring about what I initially believed to be missing functionality. As it turns out, the ability to track Amps and Voltage via the Zen20 is turned off by default. In order to enable this functionality, the parameters listed below need to be configured.
In my case, I leveraged the Custom Configuration feature of ZwaveJS2Mqtt to test and enact these configuration changes. Figured I'd share the information Zooz provided me so that it can be included in the main config for this device.

Electrical Current (A) Report Frequency
Parameter 35: The number entered as value corresponds to the number of seconds. So if 30 is entered, the Strip will report electrical current values (Amperes) every 30 seconds.
Values: 0 – electrical current reports disabled (default); 30 – 2678400.
Size: 4 byte dec
Voltage Report (V) Frequency
Parameter 36: The number entered as value corresponds to the number of seconds. So if 30 is entered, the Strip will report Voltage values (Volts) every 30 seconds.
Values: 0 – voltage reports disabled (default); 30 – 2678400.
Size: 4 byte dec

Device information
Manufacturer: Zooz
Model name: Zen20
Github Page: https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x015d/zen20.json
How are you using node-zwave-js?

[ ] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[X] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch:
zwavejs2mqtt branch:
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Don't know, this is a new device
If yes, where did it work?
No response
Attach Driver Logfile
2022-07-14 14:39:57.076 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 32.6 => 34.9
2022-07-14 14:39:57.173 INFO ZWAVE: Node 65: value updated: 50-0-value-66049 32.6 => 34.9
2022-07-14 14:39:57.765 INFO ZWAVE: Calling api sendCommand with args: [
{ nodeId: 65, commandClass: 112 },
'set',
[ 35, 30, 4, [length]: 3 ],
[length]: 3
]
2022-07-14 14:40:03.077 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 34.9 => 27.3
2022-07-14 14:40:03.106 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:03.170 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:03.272 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:03.338 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:03.385 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:03.479 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:04.672 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:04.787 INFO ZWAVE: Node 36: value updated: 50-0-value-66049 0 => 0
2022-07-14 14:40:04.901 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:04.961 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3
2022-07-14 14:40:05.030 INFO ZWAVE: Node 65: value updated: 50-2-value-66049 27.3 => 27.3

To add to this, Zooz support has provided me with a full list of configuration parameters for the Zen20. It appears that ZwaveJS is missing parameters 28-36.
https://www.support.getzooz.com/kb/article/1024-zen20-power-strip-advanced-settings/

Not quite comfortable doing a PR to this yet, but if anyone wants it, here's the updated JSON file (as a uploadable TXT file)
zen20.json.txt
.


Off by one error in division

Nim:

Wolfram Alpha:

Python:

Nim v0.13.0
Bigints downloaded earlier today, so also up to date
The calculation is 40!/(20!*20!)

Next time please don't put the code in an image.
import bigints

var x = initBigInt("815915283247897734345611269596115894272000000000")
var y = initBigInt("5919012181389927685417441689600000000")

echo(x div y)

Interesting bug though.
@def- Any ideas?

This part of the division gets called and probably causes the off-by-one, but I'm not sure yet where the mistake is: https://github.com/def-/nim-bigints/blob/master/src/bigints.nim#L609-L616

Discovered a problem with this as well:
import bigints

var x = initBigInt("815915283247897734345611269596115894272000000000")
var y = initBigInt("20000000000")

echo x div y

It's returning<PHONE_NUMBER>2394886701185424564904152901 instead of<PHONE_NUMBER>2394886717280563479805794713. A difference of<PHONE_NUMBER>4901641812.
As this code goes through the branch you mentioned there may be an issue with, I thought it could be the same problem.


Is it possible to proxy request HTTP headers?

Hello!
Is it possible to proxy request HTTP headers? For instance, it would be great if I could send basic authentication header to test front-end with a real REST API. Adding login and password to URL in plain text does not work.
Thanks for any information.
Kind regards,
Vladimir

Hi Vladimir.. yes, i would like this feature - if it is currently not working i'd like to fix it. Could you send me a link to a gist or some code i can use to reproduce this issue? With a failing test case it would be easier for me to diagnose and repair.

Hi Lloyd,
I've just realized that it is not a big issue. All the headers that sent with a request to a local-web-server instance are proxied to the remote resource. I have installed a Chrome extension to modify request headers and now I can add Authorization header on the fly. However, I think that it would be really nice to implement an extra configuration for "rewrite" section, so besides "from" and "to" properties one could also specify a list of HTTP headers to be sent to the remote resource.
Sorry for wasting your time. Local-web-server is a great tool! :+1:
Kind regards,
Vladimir

I think that it would be really nice to implement an extra configuration for "rewrite" section, so besides "from" and "to" properties one could also specify a list of HTTP headers to be sent to the remote resource.

that's a good idea, I will add that at some point.
Thanks, let me know if you have any more issues.

due to corporate proxy authentication, would be really great

yes, this feature is next on the list once v2 is done.. re-opening.

In local-web-server v2 (work in progress), all headers from the initial request are included in the proxy request.
So, let's say you have this config:
{
  "rewrite": [
    {
      "from": "/users/*",
      "to": "http://example-api.com/users/$1"
    }
  ],
}

If your local server receives this request:
GET /users/ HTTP/1.1
Host: <IP_ADDRESS>:8000
Connection: keep-alive
User-Agent: Mozilla/5.0
Content-Type: application/json
Accept: application/json
X-Requested-With: XMLHttpRequest
Referer: http://<IP_ADDRESS>:8000/
Accept-Encoding: gzip, deflate, sdch, br
Accept-Language: en-US,en;q=0.8
Cookie: JSESSIONID=OSyd08J4xYKryHhHHCzh1OPJ

Then the proxy request sent to the remote server will look like this:
GET /users/ HTTP/1.1
Host: example-api.com     # <-- The only difference in the proxy request.
Connection: keep-alive
User-Agent: Mozilla/5.0
Content-Type: application/json
Accept: application/json
X-Requested-With: XMLHttpRequest
Referer: http://<IP_ADDRESS>:8000/
Accept-Encoding: gzip, deflate, sdch, br
Accept-Language: en-US,en;q=0.8
Cookie: JSESSIONID=OSyd08J4xYKryHhHHCzh1OPJ

Notice that only the Host header is changed (to make it seem to the remote server that it received a valid, direct request). Therefore, all headers included in the initial request are included in the proxy request. If you want additional headers to be sent to the remote server, then add them to the initial request.
Does this behaviour satisfy your use cases? @raDiesle  @djsuprin

You can test the behaviour described above in v2 which is in progress and available for preview.

fixed and released in v2.0.0


ConfigureKioskResetAfterIdleTimeout - MultiApp

Will ConfigureKioskResetAfterIdleTimeout be supported in MultiApp deployment anytime? I successfully set the setting but it does nothing in a multiple configuration. I have public kiosks and would like the Edge session to reset after a given time.

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

ID: f840fa14-a379-d297-c3f7-ada05ec299d6
Version Independent ID: 81396f7b-7506-43cd-fd9a-4066719a6eb2
Content: Deploy Microsoft Edge kiosk mode
Content Source: browsers/edge/microsoft-edge-kiosk-mode-deploy.md
Product: edge
Technology: microsoft-edge
GitHub Login: @eavena
Microsoft Alias: eravena

@officedocsbot assign @e0i

Hello, @Niglb  thank you for providing feedback.
The issues section of this repository is intended for product documentation issues only.
Please consider opening a product support ticket by the following link below for your problem so that it gets resolved quickly.
Windows 10 Support
Thank you.


Implement iterators for the accessor class

This PR implements an iterator class for accessors as required in Section <IP_ADDRESS>. of the SYCL 2020 spec.
The implementation of the iterator is relatively simple, but arguably not optimal w.r.t. performance: the iterator stores a linear id that is relative to the accessor's offset. When the iterator is dereferenced, a sycl::id is computed that is again relative to the offset and this id is then transformed back to a linear id taking the offset into account using the accessor's operator[](sycl::id) (with the changes made in #992).

Can you resolve conflicts? (and maybe merge in develop to get GPU CI :) )


idea: remove yAxis.nicing ( ? )

solves #183 and #184, plus it's not really needed since axes are "nicer" by default than they used to be.

Fixed by 00e7b23665f38122f66de77f0c87ac2f33f631a1

verified in 0.9.108


Web & App Links - Not working

Describe the bug
Option to open a task in app or on web - neither option works on iOS.
To Reproduce
Steps to reproduce the behavior:

Long press a task
A menu will appear offer either open in app or in web

Expected behavior
Once tapping the menu, the link should open - however neither option does anything.
Mobile:

Plugin Version 1.11.1
Obsidian Version 1.4.6

Additional context
Add any other context about the problem here.

Closing as a dupe of #158


Cannot train model

While I am am trying to run the differential expression test using the tutorial found https://docs.scvi-tools.org/en/stable/tutorials/notebooks/scrna/scVI_DE_worm.html the model cannot be trained.

model = scvi.model.SCVI(
adata, gene_likelihood="nb"
)  # We use Negative Binomial count likelihoods, following Boyeau et al., 2023.
model.train(
check_val_every_n_epoch=1,
max_epochs=400,
early_stopping=True,
early_stopping_patience=20,
early_stopping_monitor="elbo_validation",
)
INFO: GPU available: False, used: False
INFO:lightning.pytorch.utilities.rank_zero:GPU available: False, used: False
GPU available: False, used: False
INFO: TPU available: False, using: 0 TPU cores
INFO:lightning.pytorch.utilities.rank_zero:TPU available: False, using: 0 TPU cores
TPU available: False, using: 0 TPU cores
INFO: IPU available: False, using: 0 IPUs
INFO:lightning.pytorch.utilities.rank_zero:IPU available: False, using: 0 IPUs
IPU available: False, using: 0 IPUs
INFO: HPU available: False, using: 0 HPUs
INFO:lightning.pytorch.utilities.rank_zero:HPU available: False, using: 0 HPUs
HPU available: False, using: 0 HPUs
/usr/local/lib/python3.10/dist-packages/lightning/pytorch/loops/fit_loop.py:281: PossibleUserWarning: The number of training batches (5) is smaller than the logging interval Trainer(log_every_n_steps=10). Set a lower value for log_every_n_steps if you want to see logs for the training epoch.
rank_zero_warn(
Epoch 1/400:   0%|          | 0/400 [00:00<?, ?it/s]
RuntimeError                              Traceback (most recent call last)
 in <cell line: 1>()
----> 1 model.train(
2     check_val_every_n_epoch=1,
3     max_epochs=400,
4     early_stopping=True,
5     early_stopping_patience=20,
44 frames
/usr/local/lib/python3.10/dist-packages/torch/nn/modules/linear.py in forward(self, input)
112
113     def forward(self, input: Tensor) -> Tensor:
--> 114         return F.linear(input, self.weight, self.bias)
115
116     def extra_repr(self) -> str:
RuntimeError: mat1 and mat2 must have the same dtype
Versions:

INFO: Global seed set to 0
INFO:lightning.fabric.utilities.seed:Global seed set to 0
Global seed set to 0
Last run with scvi-tools version: 1.0.4

I've never seen this particular error. Are you using the dataset from the tutorial or your own data? Also, are you on Linux or Mac?

Hello, thanks for your reply. I am using Windows and working on Google Colab. However, I found the cause of the error, which seems to be due to inconsistency between SCVI and PyTorch. I had installed the latest edition of PyTorch, while version 2.1.0 was needed. Downgrading to 2.1.0 solved the issue!

Great, glad you were able to resolve the issue! I'll be closing this thread.


feat(app): support user field service reports submission

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


Use "docker daemon"

docker -d is deprecated and has to be replaced with docker daemon

LGTM

LGTM, thansk


Refactor context to extract dependencies calculation to a separate mod

This makes unit dependency graph construction eager and moves it to a separate file.
Hopefully, this makes Context slightly easier to understand :)

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 1b63fcf has been approved by alexcrichton

:hourglass: Testing commit 1b63fcf74e4049669ebf4073886086335905afd7 with merge 607f954e0675c703cb952e77984b1cc5afeb3bbc...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 607f954e0675c703cb952e77984b1cc5afeb3bbc to master...


Handle bfrt Info for new type

Fix regression failure "Error when generating BF-RT info for 'Digest' .*: packed type is too complex"

Looks fine.
The comments in "p4types.proto" says
// New types introduced with the "type" keyword
message P4NewTypeSpec {
....

Is this error being issued for some type declared with "type"?

Yes,
i.e.
type PortIdUint_t         PortId_t;


Auto reconnect if lavalink server restart

Summary

I still have a little trouble with pull requests, sorry.

its good man an reconnect its not like this

ill work to it later

its good man and reconnect its not like this  ill work to it later

ok, weird it works for me


Getting an empty list output from process_results function

Instructions

The more information/context you provide, the better we (the instructors and class) can collectively assist you.

Please fill out all of the relevant sections below. Incomplete questions will not be addressed by the instruction team.

Questions asked without showing an attempt to answer individually will also not be addressed.

It is bad etiquette to ask things such as "I don't know how to do this, can you tell me how?" or "I can't get this code to work, what is wrong?" if you do not provide the context and/or screenshots necessary to
help.

Question (continued)
Describe the context or additional details that may be necessary to resolve this question.
I tried to generate the list of tuples but I am getting an empty list.
# Paste your code in this code block (if needed)
results = []
pos = [0]

def process_results(genome_positions = None):
    for pileup in genome_positions:
        if pileup['normal']['depth'] and pileup['tumor']['depth']:
            if pileup['normal']['concensus'][0] != pileup['tumor']['concensus'][0]:
                if pileup['tumor']['concenus'][1]/pileup['tumor']['depth'] > 0.5:
                    results.append((pos,pileup['tumor']['concensus'][0], pileup['normal']['concensus'][0],pileup['tumor']['concenus'][1]/pileup['tumor']['depth']))
        pos += 1
    return results

What do you have?
Use this space to describe what resources/functions/code you have that you feel may be relevant to answering this question.
I think it might be how I am appending the list to the results =[]
Additionally, if this is a coding question, describe what input this problem section of code requires. By "input", we mean what type of data it is.
# Paste your code in this code block (if needed)

What do you need?
Use this space to describe what resources/functions/code/data you believe is required to determine if this question has been solved.
Can anyone help troubleshoot this code?
Additionally, if this is a coding question, describe what output this problem section of code requires. By "output", we mean what type of data it is.
# Paste your code in this code block (if needed)

What have you done?
Use this space to describe what approaches you have done in your attempts to solve this question yourself. This is the *most important part of your question.
If this is just a general question
Describe what your hypothesis of what the answer is here
If this is a coding question
We require you to post your code, error messages, and output of your code here.
User-written code
# Paste your code here

Observed error messages
# Paste the observed error messages here
I don't get an error message. Just an empty list.

Observed output of code (other than error messages)
# Paste the output of your coding attempts here

Checklist
Replace the space in between the brackets with an X

[ ] Identified what you already have available to address this question
[ ] Identified what you need to reach an acceptable answer
[ ] Shown what you have done up to this point

[ ] A hypothesis if this is a general question
[ ] Your code, error messages, and output if this is a coding question

@mashiat13 could you try printing something after each if statement? That way you might be able to find out if those conditions are being met:
results = []
pos = [0]

def process_results(genome_positions = None):
    for pileup in genome_positions:
        if pileup['normal']['depth'] and pileup['tumor']['depth']:
            print("Met condition 1:", pileup, "\n")
            if pileup['normal']['concensus'][0] != pileup['tumor']['concensus'][0]:
                print("Met condition 2:", pileup, "\n")
                if pileup['tumor']['concenus'][1]/pileup['tumor']['depth'] > 0.5:
                    print("Met condition 3:", pileup, "\n")
                    results.append((pos,pileup['tumor']['concensus'][0], pileup['normal']['concensus'][0],pileup['tumor']['concenus'][1]/pileup['tumor']['depth']))
        pos += 1
    return results

Note: the danger here is overflowing your console with print statements. Maybe just run it for the first n results like this:
for pileup in genome_positions[:n]:

You may have an empty list if you are using the smaller datasets. Try changing the threshold to 0.25 instead of 0.5.
Small note too, your pos is not inside the function...and neither are your results = [].
Furthermore, pos=[0] is probably better as pos=0
Example:

Also, another student was having an issue here, but the problem was because of one of the other functions. Can I see how you send me an email  with your process_read function?
Also, can you edit your initial post to remove the code for process_results and just create an example instead. We don't want to give away your hard-earned answers.

I also found that your spelling of 'concensus' was inconsistent in this example ('concenus' and 'concensus') where the homework suggests to use 'consensus'.
When I moved results = [] & pos=0 inside the function and corrected those spellings using a known good genome_positions ("known good" does not mean the same data you are using) and applied your process_results function to it, it worked as expected:


Error when extending access token

Hi,
I'm trying to use this package, and I need to get a long lived access token. However, when I call $token->extend(), I get an error:
Exception 'Facebook\FacebookSDKException' with message 'You must provide or set a default application secret.'
It seems that in AccessToken.php, in the extend method, this array is not correctly filled.
$params = [
'client_id' => Connection::$app_id,
'client_secret' => Connection::$app_secret,
'grant_type' => 'fb_exchange_token',
'fb_exchange_token' => $this->access_token,
];
When I dump $params there, 'client_id' and 'client_secret' are null, which seems to be the reason for the error.
How can I fix this?
Thanks!

How are you obtaining the access token? Can you provide the snippet of code that's causing the error?
Are you able to see the config if you do:
dd(\Config::get('laravel-facebook-sdk::app_id'), \Config::get('laravel-facebook-sdk::app_secret'));

Thanks for the fast response!
If I use that code, it returns the values I entered in the config file (as expected).
I get the token just like in your example code and then store it in a session.
try{
     $token = Facebook::getTokenFromRedirect($redirect_uri);
     if (!$token) {
		return Redirect::to('/')->with('error', 'Unable to obtain access token.');
	}
}
catch (SammyK\FacebookQueryBuilder\FacebookQueryBuilderException $e) {
      return Redirect::back()->with('error', $e->getPrevious()->getMessage());
}
Session::put('FacebookAccessToken', $token);

Then on another route, I get it from the session and try to extend it.
$token = Session::get('FacebookAccessToken');
if (! $token->isLongLived()) {
        $token = $token->extend();
 }

and it throws the error.
However, It tried it like this:
$token = Session::get('FacebookAccessToken');
Facebook::setAccessToken($token);
if (! $token->isLongLived()) {
        $token = $token->extend();
}

And it doesn't throw the error. But
Facebook::setAccessToken($token);
if (! $token->isLongLived()) {
        $token = $token->extend();
}
dd($token->isLongLived());

still dumps "false", so it seems it's not getting a long lived token either.

I usually extend my access tokens right after I get a short-lived access token. Try extend()ing the token before storing into a session. Then store the newly-generated long-lived access token in the session. And since the access token is returned as a PHP object, you might want to cast it to a string before saving it to a session.
Session::put('FacebookAccessToken', (string) $token);

Also, due to limitations of v4.0 of the SDK, the isLongLived() feature will always return false unless you grab the token info with getInfo() or get a long-lived token with extend() beforehand:
$tokenInfo = $token->getInfo();

// This should work now...
if ( ! $token->isLongLived()) {
    $token = $token->extend();
}

Let me know if any of that helps! :)


Add model configuration property for log name

Makes log name configuration easer and more in line with other model configuration options in this package.

Very nice, thanks! Could you also send a PR to our docs repo with an example of the new functionality?

@freekmurze Sure. Will do it later this week.


chore: streaming module

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Summary

Ping flink service resources
Run flink when app streming enable
Stop flink when all app streming disable
Check transformer type for streaming

Implementation highlights
(describe how the merge request does for feature changes, share the RFC link if it has)
Test checklist

[ ] add new test cases
[ ] all code changes are covered by unit tests
[ ] end-to-end tests

[ ] deploy web console with CloudFront + S3 + API gateway
[ ] deploy web console within VPC
[ ] deploy ingestion server

[ ] with MSK sink
[ ] with KDS sink
[ ] with S3 sink

[ ] deploy data processing
[ ] deploy data modeling

[ ] new Redshift Serverless
[ ] provisioned Redshift
[ ] Athena

[ ] deploy with reporting
[ ] streaming ingestion

[ ] with Redshift Serverless
[ ] with provisioned Redshift

Is it a breaking change

[ ] add parameters without default value in stack
[ ] introduce new service permission in stack
[ ] introduce new top level stack module

Miscellaneous

[ ] introduce new symbol link source file(s) to be shared among infra code, web console frontend, and web console backend

SonarQube Quality Gate Result

Result: :white_check_mark: OK
Triggered by @tyyzqmf on pull_request

Metric
Status
Value
Error Threshold

Reliability rating
:white_check_mark: OK
1
> 1

Security rating
:white_check_mark: OK
1
> 1

Sqale rating
:white_check_mark: OK
1
> 1

Coverage
:white_check_mark: OK
83.70
< 80

Duplicated lines density
:white_check_mark: OK
5.10
> 30

Blocker violations
:white_check_mark: OK
0
> 0

Bugs
:white_check_mark: OK
0
> 0

Code smells
:white_check_mark: OK
9
> 40

Critical violations
:white_check_mark: OK
0
> 0

Major violations
:white_check_mark: OK
0
> 0

Vulnerabilities
:white_check_mark: OK
0
> 0

View on SonarQube
updated: 6/27/2024, 10:05:26 (UTC+0)

SonarQube Code Analytics
Quality Gate passed

Additional information
The following metrics might not affect the Quality Gate status but improving them will improve your project code quality.
Issues
 0 Bugs
 0 Vulnerabilities
 0 Code Smells
Coverage and Duplications
No data Coverage
No data Duplication


Better tracking display on smaller screens

The tracking display is squished to the side on smaller screens. Maybe have a way to toggle the view to fill the entire screen?
Reproduction Steps

Screen Size: 1366x768
GUI Scale: 3

Will be released in 0.3.3


Unknown kernel command line parameters with CNI and Linux 6.1 Kernel

The Firecracker team recently added a Linux Kernel 6.1 configuration for guest VMs.
When switching to this, and using CNI for networking and IP allocation, the IP address is injected into KernelArgs part of the firecracker.Config struct.
The problem appears to be that one or more of the previously valid configuration items or approaches for setting IPs is no longer valid in the 6.1 Kernel.
[    0.000000] Kernel command line: i8042.noaux i8042.nomux init=/sbin/init root=/dev/vda random.trust_cpu=on console=ttyS0 reboot=k pci=off ip=<IP_ADDRESS>::<IP_ADDRESS>:<IP_ADDRESS>:::off::: i8042.dumbkbd panic=1 acpi=off i8042.nopnp root=/dev/vda rw earlycon=uart,mmio,0x40003000
[    0.000000] Unknown kernel command line parameters "pci=off ip=<IP_ADDRESS>::<IP_ADDRESS>:<IP_ADDRESS>:::off::: acpi=off", will be passed to user space.

The result is that networking is not enabled or working as it was in a 5.11 Kernel with the same use of this Go SDK and the same CNI configuration.
@richardcase also ran into an identical issue whilst trying to write a new tool with this SDK and CNI.
CNI is important for simple IP management and proper namespacing of networks etc.

As @alexellis mentions, i ran into this using:

The recommended 6.1 kernel config
Using the sample CNI config from the SDK

For the time being i have used the 5.10 kernel config instead.

It seems like pci= ip= and acpi= are all valid within the Kernel documentation for 6.1: https://www.kernel.org/doc/html/v6.1/admin-guide/kernel-parameters.html
Perhaps there's an issue with the format of the string injected by CNI? I.e. ip=<IP_ADDRESS>::<IP_ADDRESS>:<IP_ADDRESS>:::off:::

It's been a couple of weeks now, so I wanted to tag a maintainer/contributor for suggestions/input.
@fangn2 what would be your thoughts?
@kzys are you at Fly now? I don't think Fly uses this Go SDK, but have you tried a 6.1 Kernel, have you had any similar issues?

This seems to be because CONFIG_IP_PNP is disabled in the 6.1 config: https://github.com/firecracker-microvm/firecracker/blob/60c3b14a998eb1db56403df34853fcdece6efc24/resources/guest_configs/microvm-kernel-ci-x86_64-6.1.config#L893 (see also this Slack thread).
The weird thing is it is also disabled in the 5.10 one: https://github.com/firecracker-microvm/firecracker/blob/60c3b14a998eb1db56403df34853fcdece6efc24/resources/guest_configs/microvm-kernel-ci-x86_64-5.10.config#L893, so I'm not sure how that would work, but 6.1 not (both with Firecracker default configs).

From looking at git blame, and our configs saved from last year, I can see that CONFIG_IP_PNP was actually on until 2 months ago when @pb8o submitted a PR called "trim configurations"
https://github.com/firecracker-microvm/firecracker/commit/1c07d2dac3953915d41b0d6a7a8555d92cbc831d
Disabled some options that we don't seem to need for our integration
tests. There's still options we can disable, but this already brings
down the kernel size from

Perhaps the integration tests in this repo were skipped, or do not exercise CNI and verify that it works?
It also turns off important features for getting containers to work within Firecracker like CONFIG_NF_NAT
A larger issue is the huge heavy lift that exists for all Firecracker users who want to use containers/K8s within their microVMs, we have so many options to add in to every different Kernel version to make it usable.

Hi! Thanks for reporting this issue. In the Firecracker team, we weren't aware that these kernels are used anywhere else besides Firecracker's CI and I went ahead with removing everything that looked superfluous.
We will look into this issue, but keep in mind that these guest kernel config are not recommended, but are rather just provided as examples.

Hey @pb8o do you have a recommended guest config?
Probably one that would work for a prod environment

@utibeabasi6 We don't currently have a recommended guest config. You can use the ones in the repo as a starting point and add anything you need. I will add back that option as that seems like something that is useful for our CI too.

Thank you for the response @pb8o - if you've added this and can link the commit or PR, I'll get this closed?

I haven't added it back yet. Is CONFIG_IP_PNP=y the only option needed or do we also need CONFIG_IP_PNP_DHCP=y?

Hi, the changes got merged in firecracker-microvm/firecracker#4503, and we recently created all the artifacts, so the new kernels should be effective now. I think this can be resolved. Thanks!

Thanks for the message @pb8o I'll close this now.

On a related note, do you have a rough timeline for when the latest LTS Kernel may be available with a tested guest config?

We roughly wait for when a new kernel is released in Amazon Linux, and then we add support some time after. We don't have an established timeline at the moment.


Add Multi-dof joint state in storage and retrieval services

Good point about resuing RobotState.
For now, I will keep this new RobotJointState msg and refactor when we need to pass the attached collision objects information.


Set GTK dark theme if dark theme is enabled

Should fix #3541, ~but I have yet to test.~

[x] Load setting on player window
[ ] Load for settings window
[ ] Live update

I can confirm this works when the window opens. However it does not set it live, i.e. you have to close and re-open the window for it to apply.

all windows should now follow the correct titlebar theme. some pics can be seen here: https://github.com/cassidyjames/Google-Play-Music-Desktop-Player-UNOFFICIAL-/pull/1#issuecomment-506009311
As for reloading browserWindow, does anyone have a good reference to a project that auto-reloads the browserWindow when titlebars are changed/modified? I think vscode does something like this, so I'll go see how they handle it.


Verifying module checksum mismatch

Build error
verifying<EMAIL_ADDRESS>checksum mismatch
	downloaded: h1:BccOYZCzSpyL9JXv6M8W6n9KpAfRrCEAF9n/mFma0/E=
	go.sum:     h1:zSNyS/MqXTfRDNRBBNCApsOu2oUnTEj2uymCaqYSNx8=

If go clean -modcache is executed, then the build error disappears, however the same error would happen under building the main repo matrixone, and vice versa

Reproduced this issue in clean docker container build environment while running github action.
Please refer to https://github.com/matrixorigin/matrixcube/runs/3369272847?check_suite_focus=true
Thanks,
Matthew


fix: capitalizing Detekt report name

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


C# 7.x: Default literals

This PR implements the V7 proposal discussed in Issue #67.

converting to draft: C# 7 feature

closing and reopening to trigger actions.


[Bug] ReferenceError: exports is not defined in ES module scope

Describe the bug
After pulling the new version i am not able to run it anymore
Logs
⚡ root@app  ~/js/twitch-drops   master ±  node -v
v16.14.2
⚡ root@app  ~/js/twitch-drops   master ±  npm run start

<EMAIL_ADDRESS>start
node dist/index.js

file:///root/js/twitch-drops/dist/index.js:14
Object.defineProperty(exports, "__esModule", { value: true });
^
ReferenceError: exports is not defined in ES module scope
This file is being treated as an ES module because it has a '.js' file extension and '/root/js/twitch-drops/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.
at file:///root/js/twitch-drops/dist/index.js:14:23
at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
at async loadESM (node:internal/process/esm_loader:88:5)
at async handleMainPromise (node:internal/modules/run_main:61:12)

My fault, i forgot to re-run npm run start


added timeout on Device#createBond

Adds a timeout on createBond as discussed on #567

Looks good. Thank you!

@all-contributors please add @micheleypf for code


Add dsnet to WireGuard Setup Tools

dsnet is a simple command to manage a centralised wireguard VPN. Think wg-quick but quicker.
PR suggested on hacker news:
https://news.ycombinator.com/item?id=23299023
Thanks!

thanks!

No problem. Also, thanks for creating and maintaining this documentation; it really helped me when I was new to wireguard.


Need home page link

When searching through older scikit-bio docs, there is no way to go back to latest docs without manually changing the url. Shouldn't a home page link exist?
Also, consider some sort of "user notification" making it clear that you are actually reading older documents. I've had a few "oh crap, I'm looking at old docs" moments.

👍, these are both great suggestions! Any takers?


[Feature] Stack order

Hello!,
It would be nice if there were a way to select the order of accessing data from the buffer.
At present, the buffer is treated solely as a queue. However, some people might value the newest messages more than the oldest messages - while still wanting to transact all messages, for historical logging purposes. In this example, treating the data conditionally as a stack would be beneficial.
I'm looking forward to examining this idea further if you see its value.
Thank you,
Rantouan Achmet

some people might value the newest messages more than the oldest

I have difficulty seeing that it makes much difference.  Once the network is back up one would expect the queue to be flushed in a few seconds anyway.

Also consider this situation.  Suppose the network is down and 50 messages become queued.  Then the network recovers and the first 25 are flushed.  Then suppose a new message comes in.  This would be added to the queue, but since messages are being flushed newest first it would be the next message sent, followed by the other 25.  The result would be that the messages were jumbled up.


Improving fix for IDENTITY-3264

Reviewed. Can merge.

Can you create a Carbon Jira for this please?..

https://wso2.org/jira/browse/CARBON-15434

Hi @johannnallathamby,
This PR is being held until we release 4.4.2. This is to avoid any possible merge conflicts. PR will be merged once we merge the release-4.4.2 branch to 4.4.x.

This PR is merged to release-4.4.2 with https://github.com/wso2/carbon-kernel/commit/1e89ce98e1357a4ddd5b42ac32fb566869670ce5
This will be merged to 4.4.x branch once 4.4.2 is released. Hence closing this PR.


wrangle HolyokeUrbanRenewal data and update documentation

There's considerable work needed to get the data package HolyokeUrbanRenewal spreadsheet data into shape (and documented).
This issue will be closed when easy things are done, a comprehensive list of remaining variables that need attention is created, and roxygen2::roxygenize() is run and version number in DESCRIPTION incremented.

Here's the output of glimpse() to give a rough sense of what's needed:
dplyr::glimpse(HolyokeUrbanRenewal::HolyokeUrbanRenewal)
#> Rows: 126
#> Columns: 32
#> $ file_name                              <chr> "block_02_parcel_01_info", "blo…
#> $ block                                  <dbl> 2, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3…
#> $ parcel                                 <chr> "1.0", "5.0", "1.0", "2.0", "3.…
#> $ property_location                      <chr> "Union & Prospect Streets", "We…
#> $ owner                                  <chr> "Whiting Oil Corp.", "Whiting O…
#> $ owner_address                          <chr> "1 Fountain Street, Holyoke, Ma…
#> $ data_acquired                          <chr> NA, NA, NA, "24651.0", "19854.0…
#> $ grantor                                <chr> NA, NA, NA, "Thomas & Alice Gig…
#> $ deed_reference_book                    <chr> NA, NA, NA, "3267.0", "2309.0",…
#> $ deed_reference_page                    <chr> NA, NA, NA, "489.0", "116.0", "…
#> $ tax_year                               <dbl> NA, NA, NA, 1969, 1969, 1969, 1…
#> $ tax_amount                             <chr> NA, NA, NA, "354.9", "373.1", "…
#> $ tax_remarks                            <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ assessed_value                         <chr> NA, NA, NA, "Wood Block - $2,40…
#> $ stamps                                 <chr> NA, NA, NA, "None", "8.25", "22…
#> $ remarks                                <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ building_description                   <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ type                                   <chr> "Garage & oil tanks", "Coal bun…
#> $ current_use                            <chr> "Fuel Oil & truck storage plant…
#> $ highest_and_best_use                   <chr> "Same", "Business", "Residentia…
#> $ zoning                                 <chr> "Business A", "Business A", "Bu…
#> $ appraisal_date                         <dttm> 1970-04-07, 1970-03-09, 1970-0…
#> $ approach_used                          <chr> "cost, market", "cost", "market…
#> $ value_estimate_total                   <dbl> 28000, 13500, 12000, NA, NA, NA…
#> $ value_estimate_before_taking           <dbl> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ value_estimate_after_taking            <dbl> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ damages                                <dbl> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ land_data                              <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ financial_information                  <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ site_descriptions                      <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ interpretations_of_site_maps_and_plans <chr> NA, NA, NA, NA, NA, NA, NA, NA,…
#> $ building_data                          <chr> NA, NA, NA, NA, NA, NA, NA, NA,…

Created on 2024-02-26 with reprex v2.1.0

@Casey308 and @jpapagelis24 at some point this evening can you please tag your commits here and share an update on what you have been doing (and what is planned)?
I'm assuming that this will involve edits to https://github.com/STAT325-S24/HolyokeUrbanRenewal/blob/main/data-raw/DATASET.R
Thanks in advance, Nick

In particular, I would encourage you to start to stub out issues for each of the remaining variables which need to be wrangled: we can tackle them via a divide and conquer approach. (All you two need to do is to outline the variable, what challenges there are, and share some thoughts (or not) about possible ways to address them.

@Casey308 and @jpapagelis24 can you please share an update where this issue stands? I'm hoping that you can make some progress on some of the data wrangling and also create a set of new issues for variables that will not be straightforward to wrangle.

See some minor tweaks here: can you please pull and let me know if you see any issues?
https://github.com/STAT325-S24/HolyokeUrbanRenewal/commit/76da836cdcf8f74b0de032b4d714a429aebf5fb3

@nicholasjhorton Fixed some of the formatting issues you commented with block and parcel. Still working on some of the other variables : d74bff034028ab51eeb94e59f4deb50d1835e041

Thanks for your work on https://github.com/STAT325-S24/HolyokeUrbanRenewal/commit/d74bff034028ab51eeb94e59f4deb50d1835e041: I added some comments to that commit. Can you please review and let me know if you have any questions?

I went ahead and updated the dataset to create the string block and parcel ids: see https://github.com/STAT325-S24/HolyokeUrbanRenewal/commit/66515412e672c37d9488c8335589e37b46160e69
My hope is that this issue can be replaced by any remaining data wrangling issues (as well as a new issue to update the documentation for the HolyokeUrbanRenewal dataset).

Created new issues that specify the individual tasks left to handle


 I am transferring amount through this IPN code but I am not understood how to get transaction id and payment status update on my site.
Please help me.

Does this class still work?


transaction test should use same RocksDB configuration as in production

Now we use a local RocksDB for transaction test, but this RocksDB's configuration is not the same as we use in production, E.g., it doesn't include prefix seek in the Write CF.
This is maybe a risk, we should use the same configuration. Of course, we can use small cache size in the test.

fix in #2572


Create troubleshooting section

pinging @nunix here - my understanding was to create a 'toplevel' troubleshooting section with 'restore' (or 'booting') as subsections. 🤔

pinging @nunix here - my understanding was to create a 'toplevel' troubleshooting section with 'restore' (or 'booting') as subsections. 🤔

@kkaempf indeed, and I adjusted the sidebar.js to have such hierarchy.

@kkaempf indeed, and I adjusted the sidebar.js to have such hierarchy.

Ok. Shouldn't the file be renamed from troubleshooting-restore.md to troubleshooting.md then ?

As the file is in a "hierarchy", I would indeed rename the file but to "what" it troubleshoots (i.e. restore-elemental-node.md).
And the file name is more to know what it is, as the title on the sidebar is set manually on the file headers.

@kkaempf indeed, and I adjusted the sidebar.js to have such hierarchy.

Ok. Shouldn't the file be renamed from troubleshooting-restore.md to troubleshooting.md then ?

As the file is in a "hierarchy", I would indeed rename the file but to "what" it troubleshoots (i.e. restore-elemental-node.md). And the file name is more to know what it is, as the title on the sidebar is set manually on the file headers.

I think that filename is precise and it is explaining what is inside, but it is up to you I can rename to anything what you want.

I think that filename is precise and it is explaining what is inside, but it is up to you I can rename to anything what you want.

@mjura all good then, as in the long run we'll have more files in the section, it's more to avoid "conflicting" filenames.


When upgrading wrapper use scripts and JAR from target Gradle version

Expected Behavior
When executing gradle wrapper --gradle-version, the gradlew scripts and wrapper.jar should be taken from the version of Gradle given as the parameter (i.e. the target version).
Current Behavior
Currently the scripts and the wrapper.jar is updated, but to the version of Gradle used to execute the wrapper task, not the target version.
Context
Currently if the user wants to upgrade to the latest wrapper scripts and JAR, they need to run ./gradlew wrapper after the wrapper version has been upgraded. This is not convenient. What's worse, most people don't know about this, and thus they use the wrapper scripts and JAR from a previous version of Gradle, which is mostly harmless, but it still violates the rule of least astonishment.

Could this be a good candidate to modularize and pull the latest wrapper generation module if connected to the internet? If not, then we can use the current version in the distribution. This would enable for every version going forward to benefit with the latest code generation code. The downside is it would be more work to implement at this stage.

@eriwen How much work it is? Can we fit it into 3.3 to reduce the impact of 3.2.1 wrapper bug?

@pioterj I suspect not so much work that we can't get it in for 3.3. We will prioritize it highly in our sprint planning Monday.

Actually is that issue really a solution to avoid impact of 3.2.1 wrapper bug? What if a user just upgrade gradle version manually in wrapper.properties?

I think we should deprecate editing the wrapper properties directly, and move towards the user always using the wrapper generation logic directly or indirectly, so that we can do whatever upgrades, validation and optimisations make sense for the delta from old version to new version. And so we can move the responsibility for determining which Gradle runtime version to use, and where to get it from, and which parts are required, out of a properties file and into build logic.

Sounds good in the long term, @adammurdoch.
What do we do for 3.3 though? Can we for instance give a meaningful error message for users running into GRADLE-3582 or GRADLE-3583 asking them to regenerate the wrapper files by detecting that they were generated by 3.2?

Given our current priorities and timeline, I'm de-prioritizing this for now.

I can extend this, that not just the wrapper.jar should be updated withing the gradle wrapper --gradle-version=? update run but also the gradlew and gradlew.bat files
I often see (and trapped into myself) committing the wrapper/gradle-wrappe.properties (and perhaps the task wrapper(type: Wrapper){ gradleVersion = '?'} definition but missed to update the other 2-3 artifacts

In Gradle 4.7, this issue is still present. I have to call the update task twice every time a new Gradle version is released.

I've not been able to spot a nice solution to this with the current packaging - they all seem to necessitate weird nested/multiple executions if you want gradle-wrapper.jar and gradlew, gradlew.bat scripts to be from the new/next Gradle runtime version.  This because the distribution download logic lives in the wrapper runtime, whereas the Wrapper task lives in the build itself, which is already running (possibly for the last time for this project) with the older Gradle runtime.
Unless:

a) The matching, or latest, or separately-versioned gradle-wrapper.jar were available for separate download, OR
b) Wrapper task itself forces a (next) runtime install as if a do-nothing build were run as part of the task, post properties-file update.  Significant behaviour change. Also hard to pull the wrapper jar from the dist since it's not yet on the classpath.  OR
c) The wrapper itself becomes aware of the wrapper task (not ideal?) and partitions it into two executions, one which triggers the properties-file update, the second which will force a download/install and take the JAR and make the scripts from that.  Or it could detect changes to the wrapper config during the build and do same.  Messy.

Curious what the current thinking is, or whether this is headed for a can't-fix under that current wrapper architecture.

Particularly while #12273 has not been addressed, I think this should remain open. Unless you know to run wrapper twice, it's a bit too easy at the moment to end up with scripts from an older version of Gradle.

I was about to file an issue that the wrapper task needs to be run twice after updating its configuration, but it appears that might be the same as this issue. Let me know otherwise if I should file this as a separate issue:
Steps to Reproduce

Update the Wrapper task configuration to a newer version of Gradle:

tasks {
    named<Wrapper>("wrapper") {
        gradleVersion = "7.5.1" // Was "7.5"
        distributionType = ALL
    }
}

Run gradlew wrapper.

Expected Behavior
The './gradle/wrapper/gradle-wrapper.properties', './gradle/wrapper/gradle-wrapper.jar', './gradlew', and './gradlew.bat' files are all updated (as applicable) for the new version.
Current Behavior
Only the './gradle/wrapper/gradle-wrapper.properties' is updated with a new distributionUrl value for the new version. The wrapper task must be invoked a second time for the './gradle/wrapper/gradle-wrapper.jar', './gradlew', and './gradlew.bat' files to be updated (if applicable). This can lead to extra commits/PRs when these files are shared via version control, as the updater may not be aware of the need to run the task twice.
If this is not trivial to fix, perhaps logging a warning that the task needs to be run a second time would be helpful in the interim (though maybe it's nontrivial to identify the initial invocation after a gradleVersion configuration change).

I cannot believe this ticket is STILL open after more than 7 years from it being reported? Guys this is one of the most fundamental part of Gradle. Furthermore, it's listed on the Upgrade page:

People (including me) would expect this to work. I must always go after my colleges and verify if the wrapper upgrade was successful or not. So much wasted time!
Is there any ETA for this?

What about re-launching gradle wrapper inside of the wrapper task?
To prevent recursion, only re-launch the gradle wrapper when the current Gradle version doesn't match the requested Gradle version.
// build.gradle.kts
import org.gradle.kotlin.dsl.support.serviceOf

tasks.wrapper {
  val exec = serviceOf<ExecOperations>()
  val projectDir = projectDir

  val cmd = if ("windows" in System.getProperty("os.name").lowercase(Locale.ROOT)) {
    listOf("cmd", "/c", "gradlew.bat") // TODO test Windows
  } else {
    listOf("sh", "./gradlew")
  }

  doLast {
    if (gradleVersion != GradleVersion.current().version) {
      exec.exec {
        commandLine(buildList {
          addAll(cmd)
          add("wrapper")
        })
        workingDir = projectDir
      }
    }
  }
}


Updating RDM Download URL

Updated RDM Free Download URL for label's .sh file.

Found that original URL was working as expected.


docs: Add example showing how multiple Root IngressRoute objects

The original IngressRoute design spec had support for an Aliases field. We've since removed that and this example shows how to accomplish the same functionality with multiple root IngressRoutes.
It demonstrates how to have bar.com, as well as www.bar.com,  have the same delegate route which enables multiple FQDN's to be processed equally.
Updates #644
Signed-off-by: Steve Sloka<EMAIL_ADDRESS>

@stevesloka can you please rebase this? Thanks!


404 accessing Storage adapter microservice link

Type of issue

[x] Bug
[ ] New feature
[ ] Enhancement

Description
Storage adapter microservice used to store the simulation details - the link to this is broken in initial readme.md - repository no longer in github?
https://github.com/Azure/pcs-storage-adapter-dotnet/blob/master/README.md
...
Steps to reproduce

[First step]
[Second step]
[and so on...]

Expected behavior
...
Current behavior <!-- The actual behavior observed --
...
Known workarounds
...
Possible solution
...
Context and Environment

Operating System: ...
GitHub branch: ...
.NET Runtime: ...

Code to reproduce the bug
using Xunit;

public class MyTest
{
    [Fact]
    public void TestToReproduceIssue()
    {
        // Arrange
        ...

        // Act
        ...

        // Assert
        ...
    }
}

Oops, we accidentally marked that repository as private. This has since been fixed. Thanks for letting us know about this and sorry for the trouble. Please let us know if you're still hitting this.


Means to specify the name of the attached file via header Content-Disposition

Some AS2 software processes headers like Content-Disposition: attachment; filename=sample.txt and allows to process this filename.
All the changes are HTTP compliant. New parameter attachedFileName is optional.
Tested against publicly accessible infrastructure of Mendelson Software. They have a site to check the properties of the sent AS2 message - headers, payload, errors, if present. The site: https://testas2.mendelson-e-c.com:8444/webas2/ login guest password guest
Added/updated several unit-tests as well - positive and negative.
Backward compatibility is preserved, I believe. If you don't specify the property attachedFileName, then no header is sent.

Severe conflict and build failure in the module, which I haven't changed. Will open another request and link it to this one.