Support connect database from db handler.

e.g.
use async_mysql::DBClient

impl From<DBClient> for sea_orm::DatabaseConnection {}

Hey @ltoddy, is there any special reason for you to use mysql_async instead of sqlx?

No.
Sometimes, the database used by developer is a cloud database.
For example, mysql.
The database client actually connects to the proxy, not the database itself .
In other words, connecting to the database is through service discovery not IP address.
Therefore, cloud service providers provide SDKs for service discovery, and SDK return the db handler.

其实意思就是，使用云服务商提供的数据库，是通过服务发现的方式来连接数据库的，用户是不知道数据库真是的ip地址的。
使用云服务商提供的sdk，只能得到一个db handler，比如他们基于async_mysql库自己做了一个库，支持上了服务发现的方式去连接。
这样子，就无法使用sea-orm了。
所以，如果sea-orm支持了通过一个数据库连接，来得到sea-orm的DBConnection对象，这样子就可以使用sea-orm来连接云数据库了。

Take Planetscale as an example, you have no fixed ip address access to the cloud db. But you can connect to it with a connection string<EMAIL_ADDRESS>

Your example uses the MySQL connection protocol header . But In my life, dsn like: "sd@<service_name>/<db_name>".

I guess you have to specify the db protocol at the front, db_protocal://sd@<service_name>/<db_name>

Not in front.
The process of parsing the protocol is:

service discovery read the DSN which like sd@<service_name>/<db_name>
client send request to service discovery center by <service_name> to get database proxy ip address
client establish connection with database proxy.
client send sql to db proxy, and then proxy send sql to db to execute it.

Seems you can perform the first two steps without sea-orm?

service discovery read the DSN which like sd@<service_name>/<db_name>
client send request to service discovery center by <service_name> to get database proxy ip address

After you get the concrete IP then you can initialize the connection with sea-orm. e.g. protocol://username:password@host/database

client establish connection with database proxy.
client send sql to db proxy, and then proxy send sql to db to execute it.

Please correct me if I'm wrong


GFPGAN with the Android

I've been trying to find documentation on building GFPGAN with the Android system but haven't been able to find any. Do you have any advice on this? Thank you.

I haven't tried it also but I know that there is a version of the upscaler implemented in TFLite. I don't think it is as good as this but maybe you can try it.

Thank you! Do you have any reference links? I would really appreciate it

Of course. You can try the links below.

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/g3doc/examples/super_resolution/overview.ipynb

https://github.com/tumuyan/ESRGAN-Android-TFLite-Demo


Default journal format

Tui-journal stores files by default as txt files. It would be nice to have an option to configure this to enable other formats like markdown--especially given the goal for a RESTful API. Having the ability to control note format could make for more powerful fuzzy searching and thus more powerful note taking/finding abilities.

Thanks for the suggestion.
Actually the app saves the data by default as a local SQLite database and it has another json backend. The content of the journal is saved as plain text since there are no other possibility currently to render it as markdown.
Another point is that the markdown format is actually a plain text that is rendered in a special way by web-browser and other GUI software and having that data in that format will not provide any advantages in the fuzzy searching (Hopefully this suggestion isn't some kind of AI hallucinations).

Thanks for the reply, not an AI hallucination here, just a person trying to learn more :) I understand the point that the markdown format is essentially just a construct that sits on top of plain text and the clear assumption of tui-journal is that all text is plaintext. You are correct that using the markdown format wouldn't improve fuzzy finding capabilities, I suppose that was just a link I formed in my mind because I usually fuzzy find based off the headers of a document, but the find by content option is format agnostic.
The assumption that all text is plaintext may be true for tui-journal's rendering purposes, but it is not an assumption that holds once a document leaves the confines of the database. Thanks to the elegant mechanism for exporting it is possible to take journal entries beyond the database for other uses as well, but renaming every file being exported as the same .md filetype is a chore that should be automated.
There are useful reasons for this feature that extend far past searching: A default file format used with importing and exporting would allow for syncing notes across machines and applications something would greatly extend the functionality associated with tui-journal. A plugin for batch importing/exporting could transform a shared repo used with other note taking applications like Obsidian into a home for tui-journal as well, allowing it to shine as a blazingly fast tui note application.
I would be happy to help with development if you would consider supporting the feature and need community support.

Thanks for the suggestion... I want to make sure that you are know all the current export and import functionality because maybe you can achieve you goal with much simpler way...
Currently we support to kinds of export:

The first one is just to export one journal content and you can assign the extension as you want, since it's just the plain text of the journal content.
The other one, which is more elegant to sync your journal between many apps and databases is the export in multi-select mode, which let you select many journals at once and export all the journal information like its date, tags and priority. This export has json format which is the most common language to serialize data which make it very easy to write another script that parse the data very easily (since json is support in all languages) and then it can forms the data in any format. This approach is much powerful since it gives the users an easy way to read the data so they can form as they want with a very simple script. ( Like you can sort the journal to different directories based on their tags so you can order them easily in obsidian)

Do you think we need to improve on that mechanism or it's enough for your use-case?


python310Packages.pymavlink: 2.4.31 -> 2.4.33

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pymavlink is: "Python MAVLink interface and utilities"
meta.homepage for python310Packages.pymavlink is: "https://github.com/ArduPilot/pymavlink"
meta.changelog for python310Packages.pymavlink is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.33 with grep in /nix/store/lybyhxq38qnp72v6g794nnq2iayvkzcd-python3.10-pymavlink-2.4.33
found 2.4.33 in filename of file in /nix/store/lybyhxq38qnp72v6g794nnq2iayvkzcd-python3.10-pymavlink-2.4.33

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
mavproxy
python310Packages.pymavlink
python39Packages.pymavlink

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lybyhxq38qnp72v6g794nnq2iayvkzcd-python3.10-pymavlink-2.4.33 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pymavlink https://github.com/r-ryantm/nixpkgs/archive/9b148ee43bd67cbc53512521b7fe9da6584ab909.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lybyhxq38qnp72v6g794nnq2iayvkzcd-python3.10-pymavlink-2.4.33
ls -la /nix/store/lybyhxq38qnp72v6g794nnq2iayvkzcd-python3.10-pymavlink-2.4.33/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

mavproxy
python310Packages.pymavlink
python39Packages.pymavlink

Maintainer pings
cc @lopsided98 for testing.

#186868


Fix for input when window is minimized

Fixes the issue of the program crashing if you minimize the window while it is still in startup.
The issue was due to failure of device acquisition being considered an error even though it is a valid state for the device.

Well done.


The campfire caused the game to crash

latest.log
The game log shows that there is a problem with the campfire

你能提供更多信息吗？你是自己点了篝火还是在世界上找到的？你有没有改变任何配置？你对篝火做过什么（放食物，用铲子把它灭掉等）？当你用它做某事时它会崩溃还是只是随机的？

#Enable/disable infinite life time for indirectly placed campfires (e.g. worldgen, other mods mechanics).
worldgenCampfiresInfinite = false
I modified this, in the game I have not synthesized the campfire, just walking around the game crashed


what if a search returns with no code but with emoji  &keyword?

example:
emoji_search("github")
emoji_search("octocat")

There are answers, but the code column is empty.

I think this is down to a mismatch in the search (based on the github emoji set) and the Twitter emoji set (which doesn't include the github-centric emojis, which are not part of the UNICODE standard afaik).
These emojis cannot be plotted with emoGG as there is no image to pull from the Twitter emoji CDN.
I'll try to fix this in a future release! Thanks for letting me know 😸


Move BEAST2 analysis code to beastier GitHub

As the developer of beautier, a package to create BEAST2 input files, it is natural to refer to a package called beastier, a package to parse BEAST2 output files.
As I am writing an article about beautier now, it is the time to act.
There are many reasons to make the move:

My code follows all quality stands, where 84% of all RBeast code does not even test the code
RBeast has a heavy dependency on rJava, that I do not need

I will move the code, and link to RBeast wherever appropriate,

RBeast code will not break, it will call beastier code instead.

This issue was moved to richelbilderbeek/beastier#1

Nope, Issue is not solved yet.


Add JSON view for layers

Two changes:

Adds the ability to return the configuration as a dictionary instead of as a YAML string from get_mapproxy
Adds a JSON view for layers.

Coverage decreased (-0.2%) to 99.469% when pulling a1308085bb5bdc8850d3c138a6dd96e190a772bb on theduckylittle:master into 72b9e4293173199e8995fbb58600c08675a27d93 on boundlessgeo:master.

Coverage decreased (-0.2%) to 99.469% when pulling a1308085bb5bdc8850d3c138a6dd96e190a772bb on theduckylittle:master into 72b9e4293173199e8995fbb58600c08675a27d93 on boundlessgeo:master.


Implementation of non-linear power spectrum

We only have an EH linear power spectrum currently, and should implement some non-linear corrections.
I have placed in jax_cosmo/nonlinear.py some code inherited from comicpy for smith et al. 2003 non-linear corrections. But I haven't turned it into proper working code yet.
We should:

[ ] Implement a standard mechanism for non-linear corrections in jax_cosmo/power.py
[ ] Add specific utilities for a given correction in jax_cosmo/nonlinear.py

For the mildly non-linear matter Pk, one can apply some of the integrals of perturbation theory / EFToLSS, but rewriting them into JAX. Recent codes, like FASTPT or pyBird do this very efficiently and they don't even use jit or any parallelization. It's mostly FFTLog integrals.
For deeply non-linear Pk, the best would be to have a quick emulator and write those coefficients also within JAX.

I'm pretty sure I can get halofit in easily. But I've been looking at FAST-PT..... it's pure python code as far as I can tell....


A test issue to be closed soon

Testing with this issue.

test

test

test

Closing this issue

Test!

testt

test open

Close it now

ffff


Add toml version of themes

The themes have been migrated using:
for file in themes/*.yaml; do alacritty migrate -c "$file"; done

Tested the "seashells" and the "nord" themes, everything seems to be working well.
I've also migrated the schemes.yaml file, but maybe that wasn't necessary ?

#34.


[4.0] Items and their IMPORT files are making duplicates in file browser

Godot version
4.0 Alpha 1
System information
Windows 10
Issue description

Importing models (FBX, OBJ or DAE – doesn't matter) started to cause duplicated entries in the editor (mostly the file browser). It makes impossible to delete them properly up to a full crash of Godot 4 editor or it will brake all scenes, where they've been used.
Then importing other files caused the same issue.
Steps to reproduce
I was just trying to import the house model to setup shadows properly.
Nothing too special about it.
Minimal reproduction project
Godot 4 Import Bug.zip

The project I've added is just a house walls OBJ, textures from the screenshot are not uploaded, but you can try to add any texture and see, if the issue will be reproduced. If not, I can add a smaller textures version.

This looks very similar to the duplication-on-import bug that #55373 is fixing, see #53871 for a bit of discussion on this. Might be worth a shot to see if that PR fixes all of these.

I haven't seen this bug for a while now.

Can anybody still reproduce this issue?

No response for over a year, and the related issues https://github.com/godotengine/godot/issues/53871, https://github.com/godotengine/godot/issues/54774, and https://github.com/godotengine/godot/issues/57225 are fixed, by PR #73214, so closing this issue and assuming it is fixed as well.


OSX library not found for -lQt5Gui

trying to build a very simple app on OSX.  Qt5 installed via homebrew.  Looks to be some kind of confusion as cpp_to_rust should probably be passing the -framework flag on OSX instead of trying to link explicitly to individual Qt libraries?
  = note: "cc" "-m64" "-L" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride0.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride1.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride10.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride11.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride12.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride2.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride3.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride4.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride5.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride6.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride7.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride8.rust-cgu.o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.ride9.rust-cgu.o" "-o" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43" "src/ride/ride/target/debug/deps/ride-6203a9cc1ea02c43.crate.allocator.rust-cgu.o" "-Wl,-dead_strip" "-nodefaultlibs" "-L" "src/ride/ride/target/debug/deps" "-L" "src/ride/ride/target/debug/build/fontsan-e421d55911bffb66/out/lib" "-L" "src/ride/ride/target/debug/build/miniz-sys-b8bddff7cf4c1223/out" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "src/ride/ride/target/debug/build/qt_gui-44210001ee586765/out/c_lib_install/lib" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "src/ride/ride/target/debug/build/qt_core-bdc98b4a9bc5fbeb/out/c_lib_install/lib" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "/opt/homebrew/Cellar/qt/5.10.0/lib" "-L" "src/ride/ride/target/debug/build/qt_widgets-a60d7919ed1ae7c5/out/c_lib_install/lib" "-L" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib" "src/ride/ride/target/debug/deps/libqt_gui-4e9e544b23b5ab2c.rlib" "src/ride/ride/target/debug/deps/libqt_core-f84aad4d021306b1.rlib" "src/ride/ride/target/debug/deps/liblibc-fa97112e9ce8b6b2.rlib" "src/ride/ride/target/debug/deps/libcpp_utils-aa984d6d79c0ad7d.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libstd-a5573c28baa2d270.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libpanic_unwind-0e1dd264eb0295ca.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/liballoc_jemalloc-40e38640b113cbe4.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libunwind-4d7cc397a07cb119.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/liballoc_system-3555cc0ff631180a.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/liblibc-d3676d01f6a9d053.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/liballoc-0285aed88b3edf43.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libstd_unicode-8a7521ee3925d10e.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/librand-7270a913c138d53b.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libcore-24fa1060c4e0b7b1.rlib" "/opt/homebrew/Cellar/rust/1.22.1/lib/rustlib/x86_64-apple-darwin/lib/libcompiler_builtins-eeb63a38b1651c16.rlib" "-l" "Qt5Gui" "-l" "Qt5Core" "-l" "stdc++" "-l" "Qt5Core" "-l" "stdc++" "-l" "System" "-l" "resolv" "-l" "pthread" "-l" "c" "-l" "m"
  = note: ld: library not found for -lQt5Gui
          clang: error: linker command failed with exit code 1 (use -v to see invocation)

Also there's no Qt5Gui library.  There's the QtGui framework which has he QtGui library...


chore(deps): update common-dev-assets digest to 4861832

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
9ff9b04 -> f812701

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Renovate Bot.

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


Right monitor incorrectly adjusts zones to accommodate taskbar along left (vertical) side of left monitor

Microsoft PowerToys version
0.31.2
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Dual monitors I will name LEFT and RIGHT.  RIGHT is the main display which presents the taskbar.

Create zones in LEFT that bump against the far right edge of LEFT.
Move taskbar to the left vertical edge of RIGHT.
Move an application to the zones that were directed to make use of the right edge of LEFT.
The picture below illustrates the bad behavior.  The zones are set so the left window should touch the taskbar.  The red circle highlights the incorrect adjustment FancyZones imposes.

Notes:

Zones on RIGHT monitor are adjusted for the real location of the taskbar correctly.  The bug seems to be incorrect adjustments performed in addition to the correct adjustments.
The bad adjustment goes away when the taskbar is moved away from the edge RIGHT and LEFT share.  That is, it the bad adjustment is gone when the taskbar is on the bottom, top or right edges of the RIGHT monitor.
When I edit zones while the taskbar location in invoking the bad behavior, the editor shows the zones take the space I intend.  "The space I intend" == "space that does not incorrectly adjust for the taskbar".

✔ Expected Behavior
The app will fill the full zone allocated, including the space along the right edge of LEFT monitor.
❌ Actual Behavior
The app fills a space similar to the zone created, but the far right edge of the zone is reduced by the same width of the taskbar--as if the zone were being adjusted for the taskbar in the wrong place.
Other Software
No response

It seems you're using an outdated version of PowerToys. Please update to the latest release v0.47 and check if the issue persists.

version 0.47.0 resolves the issue.  Good eye & thanks.


feat(uploads,server): Implement File entity

Details
Thir PR introduces File entity.
Changes

[x] Create File entity to store following information:

[x] It extends Record entity;
[x] Has key property to store file id assigned by tus;

Checklist

[x] I have self-reviewed my changes before asking for a review from maintainers
[x] I have added changesets (optional)
[x] I have brought tests (if necessary)

This PR is merged from command line, because of GitHub issues.


Fetch specific columns through a join table

I have three tables: User (PK: user_id), Bet (PK: bet_id) and Joiner (PK: joiner_id).
Now, when a bet is created, there is a user that creates a bet, and there are many users that join.
As a result, there is Many to Many relationship from Bet to User, that is why I have created the Joiners table. Except for its PK, this table has also a FK, bet_id, and another FK, user_id. So, for each bet, there can be many joiners with different or same user_id.
What I want to do, is fetch all bets, along with the id and username columns of the bet creator and the joiners. My first attempt was this, but it doesn't work very well:
var Bet = Bookshelf.Model.extend({
    tableName: 'bet',
    idAttribute: 'bet_id',
	user: function() {
	return this.belongsTo(User, 'bet_creator');
    },
	joiner: function() {
		return this.hasMany(User, 'user_id').through(Joiner, 'user_id', 'bet_id');
	}
});

var Joiner = Bookshelf.Model.extend({
    tableName: 'joiner',
    idAttribute: 'joiner_id',
    bet: function() {
        return this.hasMany(Bet, 'bet_id');
    }
});

AND
model.Bets.forge()
		.query({where: {match: requestObject.matchid}})
		.fetch(
  {withRelated: ['user', 'joiner']},
			{debug:true}
		).then(function(collection) {
			return res.json(collection.toJSON());
		});

Update: I can now fetch correctly the joiners.
I changed this bit:
joiner: function() {
        return this.hasMany(User, 'user_id').through(Joiner, 'user_id', 'bet_id');
    }

to
joiner: function() {
        return this.belongsToMany(User, 'user_id').through(Joiner, 'bet_id', 'user_id');
    }

But how can I fetch only the user_id and the username for the users and joiners?

Hi @dksakkos.
In your examples you're doing something a bit strange - calling a relationship by the "pivot table", rather than the models it returns. Do you want to return Joiners or Users from joiner()? Here's an attempt at answering:
For a many-to-many you just put belongsToMany on each side of the relationship. I've actually not used belongsToMany with through before, but the second argument is meant to be the table, not the foreign key.
Should be something like this I believe:
var Bet = Bookshelf.Model.extend({
    tableName: 'bet',
    idAttribute: 'bet_id',
    creator: function() {
      return this.belongsTo(User, 'bet_creator');
    },
    joinedUsers: function() {
      return this.belongsToMany(User, 'joiner', 'user_id');
    }
});

Hi @rhys-vdw, I appreciate the reply.
Actually I want to return the Users, so I can fetch the usernames. I can only fetch this through the join table, that is why I use the through command (http://bookshelfjs.org/#Model-through).
I tried your solution but it doesn't seem to work. Right now I'm happy with the fix I implemented, since it works.
However, the problem that remains is how can I only fetch the user_id and the username, and discard the useless columns.

I can only fetch this through the join table, that is why I use the through command.

belongsToMany also uses a pivot table. If you don't need data from the joiner table you shouldn't require a Joiner model at all.

However, the problem that remains is how can I only fetch the user_id and the username, and discard the useless columns.

Try this:
model.Bets.forge()
  .query({where: {match: requestObject.matchid}})
  .fetchAll({
    withRelated: [
      {user: function(qb) { qb.columns('user_id', 'username'); }},
      'joiner'
    ],
    debug:true
  })
  .then(function(collection) {
    return res.json(collection.toJSON());
  });

I get an error on fetchAll(): undefined is not a function.
I believe it's because collections don't have fetchAll, but fetch().
If I use the latter, along with the following relation in my model
var Bet = Bookshelf.Model.extend({
    tableName: 'bet',
    idAttribute: 'bet_id',
	joiner: function() {
		return this.hasMany(Joiner, 'bet_id');
	}
});

and run your code, I get no output.

I believe it's because collections don't have fetchAll, but fetch().

Sorry, updated code. Just copy pasted and didn't realize there was a collection hidden in there.

I get no output.

There should be a debug trace from the query.

There is no output at all, and I really don't know why. As you said, there should at least be an error printed out.
Also, for some reason fetchAll() doesn't work with the Bet model either. I have to use the Bets collection and fetch() method in order to avoid the "undefined is not a function" TypeError.
But even so, no output whatsoever.

Add a .catch, it might be throwing before the debug trace.

For some reason it fails to recognize catch as a function. If I use otherwise instead, I get a
[TypeError: undefined is not a function]

on this line:
 {user: function(qb) { qb.columns('user_id', 'username'); }}

It's not possible for .catch to not be recognized as a function. Can you provide the whole sample code where that is happening?

Sure thing.
leagueModel.Bets().forge()
  .query({where: {match: requestObject.matchid}})
  .fetch({
    withRelated: [
      {user: function(qb) { qb.columns('user_id', 'username'); }},
      'joiner'
    ],
    debug:true
  })
  .then(function(collection) {
   console.log(JSON.stringify(collection.toJSON()));
  })
  .catch(function(err) {
	  console.error(err);
  });

This one fires a
TypeError: undefined is not a function

on the first line of code.
If I change it to this
new leagueModel.Bets()

it fires the same error on the line where the catch function is.

The problem with that is that you're calling the model constructor leagueModel.Bets() and then calling .forge() on the result of that. That doesn't work. You either use the model constructor to create a new instance like:
new leagueModel.Bets().query().fetch(/* ... */)

or you use forge to build a new instance:
leagueModel.Bets.forge().query().fetch(/* ... */)

Both at the same time doesn't do anything good as you found out.

Fair enough. But I still end up with an error on the catch function.

Um. Well, that doesn't seem likely/possible. But evidently it's happening.
fetch() should return a Promise, and then() should return that same promise reference for chaining.

OK. Once again, this is the code I'm using
leagueModel.Bets.forge()
  .query({where: {match: requestObject.matchid}})
  .fetch({
    withRelated: [
	{user: function(qb) { qb.columns('user_id', 'username'); }},
      'joiner'
    ],
    debug:true
  })
  .then(function(collection) {
   console.log(JSON.stringify(collection.toJSON()));
  })
  .otherwise(function(err) {
      console.error(err);
  });
}

and this is my schema
var Bet = Bookshelf.Model.extend({
    tableName: 'bet',
    idAttribute: 'bet_id',
	user: function() {
	return this.belongsTo(User, 'user_sender');
    },
	joiner: function() {
		return this.belongsToMany(User, 'user_id').through(Joiner, 'bet_id', 'user_id');
}
});

var Joiner = Bookshelf.Model.extend({
    tableName: 'joiner',
    idAttribute: 'joiner_id',
    bet: function() {
        return this.belongsTo(Bet, 'bet_id');
    },
	user: function() {
		return this.belongsTo(User, 'user_id');
	}
});

There should be an error somewhere.
The error I get is a [TypeError: object is not a function].

Aaaaah found it. Line
{user: function(qb) { qb.columns('user_id', 'username'); }}

changed to
{user: function(qb) { qb.column('user_id', 'username'); }},

It's column, not columns!
2 days of work for one character. I love my job.


EditorSettings: Move interface/ properties to interface/editor

Fixes inconsistent behaviour where clicking on "Interface"
in the Editor Settings wouldn't collapse the category as is the
case for all the other categories.
I thought there was an issue about this, but I can't find it...

#11601?

#11601?

I don't think this is the exactly the same.
Oh I didn't get what's this PR does at the first time: It adds a new category in the Interface menu called Editor, so that it works like other categories (no "root" properties, but extend/collapse instead when clicking).
The changes LGTM :)

@Hinsbart editor is a good name for all thos preiperties!
But maybe we couod still move some of them to other sections?

@toger5 sure!
I haven't read the discussion in #11601 when I made this, so my solution was to just dump them all into a new category. Feel free to further move them around.


CI: disable visual testing for forks

Describe the bug
While  #1786 disabled visual testing for this repository, it left the workflow enabled for forks.
To Reproduce
Steps to reproduce the behavior:

Fork this repository
Make a change
See error

Expected behavior
If a workflow is disabled for the main repository, it shouldn't be enabled for forks.
Error
Error: TypeError: Cannot read property 'replace' of undefined
    at /home/runner/work/_actions/chromaui/action/v1/action/main.js:2:1611930
    at /home/runner/work/_actions/chromaui/action/v1/action/main.js:2:1610851
    at Object.next (/home/runner/work/_actions/chromaui/action/v1/action/main.js:2:1610956)
    at o (/home/runner/work/_actions/chromaui/action/v1/action/main.js:2:1609670)
Error: Cannot read property 'replace' of undefined

Desktop (please complete the following information):

OS: Linux

Additional context
Add any other context about the problem here.

I'll send a PR

@lesliecdubs this has a PR...


Docker compose for self-hosted server

I noticed a docker-compose.yml and example .env file is missing in the repo even though server code is there and it can be set using environment. I would suggest adding it to the repo and docs to make setup easier.
Something along these lines does work. Then just point to the server using HISHTORY_SERVER variable.

networks:
  hishtory:
    driver: bridge

services:
  postgres:
    image: postgres
    restart: unless-stopped
    networks:
      - hishtory
    environment:
      POSTGRES_PASSWORD: ${POSTGRESQL_PASSWORD}
      POSTGRES_DB: hishtory
      PGDATA: /var/lib/postgresql/data/pgdata
    volumes:
      - ./postgres-data:/var/lib/postgresql/data

  hishtory:
    image: hishtory
    depends_on:
      - postgres
    networks:
      - hishtory
    build:
      context: ./
      dockerfile: ./backend/server/Dockerfile
    restart: unless-stopped
    environment:
      POSTGRESQL_PASSWORD: ${POSTGRESQL_PASSWORD}
      VERSION: ${VERSION}
    #labels:
    #  traefik.docker.network: traefik
    #  traefik.enable: true
    #  traefik.http.routers.hishtory.rule: Host(`hishtory.${DOMAIN}`)
    #  traefik.http.routers.hishtory.entrypoints: secure
    #  traefik.http.routers.hishtory.middlewares: security@file, compression@file
    #  traefik.http.services.hishtory.loadbalancer.server.port: 8080
    ports:
      - 8080:8080

See the "Self-Hosting" section in the readme for preliminary information on this. I do like the idea of having a docker-compose file, but I want to test that manually before adding it to the repo.


Using kuroshiro with module bundler

Hi hexeng !
Thank you very much for this awesome tool!! I love it!
I added some information to the readme about using kuroshiro with a module bundler like webpack.

Coverage remained the same at 92.228% when pulling 78bf96973da9892fd5ebbf28e26ac6ad20c049c3 on mornir:patch-1 into b0907319e36d38deeb10b3e309bc740d354db9b1 on hexenq:master.

Nice work! Thanks.


Cannot build 5.5.0 or higher

Describe the bug
Cannot build version 5.5.0. It fails with an error that I do not know how to interpret (I'm not node developer).
To Reproduce
Steps to reproduce the behavior:

Download source code
Build
See error

Environment (please complete the following information):

Lens Version: 5.5.0
OS: Arch Linux
Installation method (e.g. snap or AppImage in Linux): n/a

Logs:
Build log (the failure part)
$ env NODE_ENV=production concurrently yarn:compile:*
[compile:*main] $ yarn run webpack --config webpack/main.ts
[compile:*renderer] $ yarn run webpack --config webpack/renderer.ts
[compile:*extension-types] $ yarn run webpack --config webpack/extensions.ts
[compile:*main] $ /build/lens/src/lens-5.5.0/node_modules/.bin/webpack --config webpack/main.ts
[compile:*renderer] $ /build/lens/src/lens-5.5.0/node_modules/.bin/webpack --config webpack/renderer.ts
[compile:*extension-types] $ /build/lens/src/lens-5.5.0/node_modules/.bin/webpack --config webpack/extensions.ts
[compile:*renderer] WEBPACK:renderer {
[compile:*renderer]   assetsFolderName: 'assets',
[compile:*renderer]   isDevelopment: false,
[compile:*renderer]   rendererDir: '/build/lens/src/lens-5.5.0/src/renderer',
[compile:*renderer]   buildDir: '/build/lens/src/lens-5.5.0/static/build',
[compile:*renderer]   appName: 'OpenLens',
[compile:*renderer]   htmlTemplate: '/build/lens/src/lens-5.5.0/src/renderer/template.html',
[compile:*renderer]   publicPath: '/build/'
[compile:*renderer] }
[compile:*main] WEBPACK:main {
[compile:*main]   isDevelopment: false,
[compile:*main]   mainDir: '/build/lens/src/lens-5.5.0/src/main',
[compile:*main]   buildDir: '/build/lens/src/lens-5.5.0/static/build'
[compile:*main] }
[compile:*main] asset main.js 417 KiB [emitted] [minimized] (name: main) 1 related asset
[compile:*main] orphan modules 419 KiB [orphan] 224 modules
[compile:*main] runtime modules 937 bytes 4 modules
[compile:*main] modules by path ../ 983 KiB
[compile:*main]   modules by path ../src/common/ 457 KiB 223 modules
[compile:*main]   modules by path ../src/main/ 403 KiB 90 modules
[compile:*main]   modules by path ../src/extensions/ 80.8 KiB 23 modules
[compile:*main]   modules by path ../src/renderer/ 30.2 KiB 5 modules
[compile:*main]   modules by path ../src/migrations/ 1.09 KiB 2 modules
[compile:*main]   + 1 module
[compile:*main] modules by path external "lodash/ 168 bytes
[compile:*main]   external "lodash/orderBy" 42 bytes [built] [code generated]
[compile:*main]   external "lodash/isEqual" 42 bytes [built] [code generated]
[compile:*main]   external "lodash/fp" 42 bytes [built] [code generated]
[compile:*main]   external "lodash/get" 42 bytes [built] [code generated]
[compile:*main] + 35 modules
[compile:*main] lens-app-main (webpack 5.72.0) compiled successfully in 85520 ms
[compile:*main] yarn run compile:main exited with code 0
[compile:*renderer] assets by path chunks/*.js 4.82 MiB
[compile:*renderer]   assets by chunk 4.05 MiB (id hint: vendors) 14 assets
[compile:*renderer]   + 71 assets
[compile:*renderer] assets by path assets/ 1.74 MiB 27 assets
[compile:*renderer] assets by path *.js 26.3 MiB
[compile:*renderer]   asset OpenLens.js 25.2 MiB [emitted] (name: OpenLens) 1 related asset
[compile:*renderer]   + 2 assets
[compile:*renderer] assets by path *.css 231 KiB
[compile:*renderer]   asset OpenLens.css 207 KiB [emitted] (name: OpenLens)
[compile:*renderer]   asset 888.css 13.9 KiB [emitted]
[compile:*renderer]   asset 8185.css 10.3 KiB [emitted]
[compile:*renderer] assets by path *.node 206 KiB
[compile:*renderer]   asset 757dd2dc5031e2651296c33d39faa131.node 115 KiB [emitted] (auxiliary id hint: vendors)
[compile:*renderer]   asset 935e5cd0f470d7d3b7db3968a941c7bd.node 90.5 KiB [emitted] (auxiliary id hint: vendors)
[compile:*renderer] asset OpenLens.html 363 bytes [emitted]
[compile:*renderer] Entrypoint OpenLens 25.4 MiB (28.8 MiB) = OpenLens.css 207 KiB OpenLens.js 25.2 MiB 1 auxiliary asset
[compile:*renderer] orphan modules 9.49 MiB (javascript) 1.74 MiB (asset) 257 KiB (runtime) [orphan] 3542 modules
[compile:*renderer] runtime modules 9.95 KiB 15 modules
[compile:*renderer] modules by path ./ 28.5 MiB (javascript) 229 KiB (css/mini-extract)
[compile:*renderer]   modules by path ./node_modules/ 25.1 MiB (javascript) 78.3 KiB (css/mini-extract)
[compile:*renderer]     javascript modules 24.7 MiB 2555 modules
[compile:*renderer]     css modules 78.3 KiB 69 modules
[compile:*renderer]     json modules 463 KiB 30 modules
[compile:*renderer]   modules by path ./src/ 3.4 MiB (javascript) 151 KiB (css/mini-extract)
[compile:*renderer]     javascript modules 3.33 MiB 757 modules
[compile:*renderer]     css modules 151 KiB 212 modules
[compile:*renderer]     asset modules 72.2 KiB 22 modules
[compile:*renderer]     ./src/renderer/components/monaco-editor/monaco-themes/clouds-midnight.json 1.83 KiB [built] [code generated]
[compile:*renderer]   ./package.json 10.7 KiB [built] [code generated]
[compile:*renderer] + 26 modules
[compile:*renderer]
[compile:*renderer] WARNING in ./node_modules/chokidar/lib/fsevents-handler.js 9:13-32
[compile:*renderer] Module not found: Error: Can't resolve 'fsevents' in '/build/lens/src/lens-5.5.0/node_modules/chokidar/lib'
[compile:*renderer]  @ ./node_modules/chokidar/index.js 15:24-57
[compile:*renderer]  @ ./src/extensions/extension-discovery/extension-discovery.ts 14:0-33 209:8-13
[compile:*renderer]  @ ./src/extensions/extension-discovery/extension-discovery.injectable.ts 6:0-59 17:29-47
[compile:*renderer]  @ ./src/renderer/bootstrap.tsx 27:0-108 92:41-69
[compile:*renderer]
[compile:*renderer] 1 warning has detailed information that is not shown.
[compile:*renderer] Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
[compile:*renderer]
[compile:*renderer] lens-app-renderer (webpack 5.72.0) compiled with 1 warning in 129049 ms
[compile:*renderer] yarn run compile:renderer exited with code 0
[compile:*extension-types] WARNING in ./node_modules/chokidar/lib/fsevents-handler.js 9:13-32
[compile:*extension-types] Module not found: Error: Can't resolve 'fsevents' in '/build/lens/src/lens-5.5.0/node_modules/chokidar/lib'
[compile:*extension-types]
[compile:*extension-types] webpack compiled with 1 warning
[compile:*extension-types] yarn run compile:extension-types exited with code 0
  • electron-builder  version=23.0.3 os=5.17.9-arch1-1
  • loaded configuration  file=package.json ("build" field)
  • rebuilding native dependencies<EMAIL_ADDRESS>platform=linux arch=x64
  • rebuilding native dependency  name=node-pty version=0.10.1
  ⨯ cannot execute  cause=exit status 1
                    out=$ node scripts/install.js
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

                    errorOut=/bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    /bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    /bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    gyp info it worked if it ends with ok
    gyp info using<EMAIL_ADDRESS>    gyp info using<EMAIL_ADDRESS>| linux | x64
    gyp info find Python using Python version 3.10.4 found at "/usr/bin/python3"
    gyp http GET https://atom.io/download/electron/v14.2.4/node-v14.2.4-headers.tar.gz
    gyp http 200 https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v14.2.4/node-v14.2.4-headers.tar.gz
    gyp http GET https://atom.io/download/electron/v14.2.4/SHASUMS256.txt
    gyp http 200 https://gh-contractor-zcbenz.s3.amazonaws.com/atom-shell/dist/v14.2.4/SHASUMS256.txt
    gyp info spawn /usr/bin/python3
    gyp info spawn args [
    gyp info spawn args   '/usr/lib/node_modules/node-gyp/gyp/gyp_main.py',
    gyp info spawn args   'binding.gyp',
    gyp info spawn args   '-f',
    gyp info spawn args   'make',
    gyp info spawn args   '-I',
    gyp info spawn args   '/build/lens/src/lens-5.5.0/node_modules/node-pty/build/config.gypi',
    gyp info spawn args   '-I',
    gyp info spawn args   '/usr/lib/node_modules/node-gyp/addon.gypi',
    gyp info spawn args   '-I',
    gyp info spawn args   '/build/.electron-gyp/14.2.4/include/node/common.gypi',
    gyp info spawn args   '-Dlibrary=shared_library',
    gyp info spawn args   '-Dvisibility=default',
    gyp info spawn args   '-Dnode_root_dir=/build/.electron-gyp/14.2.4',
    gyp info spawn args   '-Dnode_gyp_dir=/usr/lib/node_modules/node-gyp',
    gyp info spawn args   '-Dnode_lib_file=/build/.electron-gyp/14.2.4/<(target_arch)/node.lib',
    gyp info spawn args   '-Dmodule_root_dir=/build/lens/src/lens-5.5.0/node_modules/node-pty',
    gyp info spawn args   '-Dnode_engine=v8',
    gyp info spawn args   '--depth=.',
    gyp info spawn args   '--no-parallel',
    gyp info spawn args   '--generator-output',
    gyp info spawn args   'build',
    gyp info spawn args   '-Goutput_dir=.'
    gyp info spawn args ]
    /bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    /bin/sh: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8)
    gyp: Call to 'node -e "require('nan')"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
    gyp ERR! configure error
    gyp ERR! stack Error: `gyp` failed with exit code: 1
    gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/node-gyp/lib/configure.js:261:16)
    gyp ERR! stack     at ChildProcess.emit (events.js:400:28)
    gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:285:12)
    gyp ERR! System Linux 5.17.9-arch1-1
    gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
    gyp ERR! cwd /build/lens/src/lens-5.5.0/node_modules/node-pty
    gyp ERR! node -v v14.19.3
    gyp ERR! node-gyp -v v9.0.0
    gyp ERR! not ok
    error Command failed with exit code 1.

                    command=/usr/bin/node /usr/lib/node_modules/yarn/bin/yarn.js run install
                    workingDir=/build/lens/src/lens-5.5.0/node_modules/node-pty
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Additional context
This is important to update the AUR Arch Linux package.

Same error with 5.1.1

@ogarcia based on the logs it seems that node-gyp (or python3) is not working correctly. Could you check that nodejs/node-gyp dev/build environment works?

After doing a lot of checks, what I see is that the error occurs when using a clean chroot to build the package (in Arch Linux we use extra-x86_64-build). If the build is done directly the system does not fail. I don't understand this error, because the content inside and outside the chroot is exactly the same.
In any case this problem is unique to Arch Linux, so I close this issue. Sorry for the inconvenience.

Finally the mistery is solved. The chroot configures locales to en_US-UTF-8 so you need change it to C whith export LANG=C LC_ALL='' before run make.


BitBucket Pull Request Path Filters Timeline?

Hey folks,
Is there a timeline for the support of path filters for code coming from BitBucket? It is supported for CI builds so it sounds simple enough?
Or is it a limitation from what information BitBucket exposes?
Path filters for PR triggers are not yet supported for Bitbucket Cloud repos.
Taken from - https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?tabs=yaml&view=azure-devops#pr-triggers

It is no longer there?
I can see it on this cached version
https://webcache.googleusercontent.com/search?q=cache:YruvtsXR5qgJ:https://docs.microsoft.com/bg-bg/azure/devops/pipelines/build/triggers%3Fview%3Dtfs-2018+&cd=2&hl=en&ct=clnk&gl=nz
I will experiment and confirm tomorrow :)

This is now working, paths only declared in the yml file, no manual override in AZDO, and PR builds are kicked off

And it is no longer working... my CI path triggers are all working okay but PR ones have relapsed since I closed this 2 weeks ago

This appears to be a bug we are investigating.  Tracked here: https://developercommunity.visualstudio.com/content/problem/653939/azure-pipelines-bitbucket-path-triggers-not-workin.html

For the record, this was a bug that has been fixed.


ntfy: pin older emoji

Description of changes
emoji 2.0.0 introduces breaking changes, so pin an older version.
Further to 3920fde6f06
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

@peterhoeg I noticed a PR that fixes the issue, and I figured using the patch is probably lighter than another version of emoji: https://github.com/NixOS/nixpkgs/pull/185088

In principle, we should wait for upstream to at least comment on the proposed fix (ideally it should be merged) before we choose to go in that direction but as the fix is a one-liner, it's definitely manageable.


[Asgardeo to Choreo Hub] Add functionality to fetch a message-batch in the initial consolidator state-sync phase

Description:

$subject

With websubhub 2.0 implementation [1] this feature is no longer required.
[1] - https://github.com/ballerina-platform/ballerina-standard-library/issues/4263


Add link to videos in readme..

I love to see the code, but the most important thing is the videos, so it would be interesting if you refer to them here. :wink:

@matiasdelellis - want to make a PR for it?

Cooll.. Thank you so much for everything. 😃 🎉


Explain "ec"

This abbreviation is often used on Mastodon. People might be confused what it means.

Good suggestion! I've added a couple common abbreviations.


The code in the main.cpp file generated using CMake: Quick start is C code

Brief Issue Summary
More info:
This issue has been reproduced since CMake Tools:v1.18.41
Repro Steps:

Create a new folder named 'Test' and open it with vscode.
Run command: “CMake:configure”
Enter a name for new project :'Helloworld'
Select 'C++'
Select 'Executable'
Select "CPack"and click OK.
Open main.cpp file

Expected result:

Actual result:

CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response

I verified the issue on latest pre-release: v1.19.20 (pre-release) and it was fixed.
ENV：
CMake Tools: v1.19.21 (pre-release)
vscode: 1.19.1 (user setup)
C/C++:v1.21.1(pre-release)

We verified the issue on CMake tools: v1.19.45 and it has been fixed.
ENV：
CMake Tools:v1.19.45
vscode: 1.92.2
Actual result:


PR for issue #34, use salt api for minion key accept

@shortdudey123 Sound reasonable. I will give it one more try.

@vkhatri hows it going on your end with the feedback? anything i can do on my end?

@shortdudey123 will submit a revised PR over the weekend.

Sounds good

@shortdudey123 Got all the changes in place, just finishing up specs.

Sounds good :)

Travis is failing because of an issue with yaml configuration file reported in issue #45 .
https://travis-ci.org/shortdudey123/chef-salt/jobs/210111392#L488
   +---
    +external_auth:
    +  pam:
    +    saltapi: !ruby/array:Chef::Node::ImmutableArray
    +      internal:
    +      - "@wheel"
    +      ivars:
    +        :@__path__: []
    +        :@__root__:
    +        :@__node__:
    +        :@__precedence__:

It would be great if you could merge this PR.

The new changes look fine in a quick skim over of them.  I will review them in more detail this week.
I added a comment to address the travis failure


feat: add auto-close tabs

I used this to close tabs and send them to Omni...so I wanted this to automatically do it.

Hey @geoffwork-22, thanks for the submission.
This seems like a personal preference, so it would be great if it was a setting that the user could turn on or off.


Support for handling private keys as byte[]

Since strings are immutable in java, the best practice for handling sensitive data is to use a more primitive data format, such as char[] and byte[] instead of the String format. Otherwise it is possible to retrieve the sensitive data by forcing a heap dump of the running application.
Methods in KeyPairService should support this, something as simple as following in KeyPairService.java:
  String sign(UnsignedByteArray message, byte[] privateKey);

And of course need to make sure the byte[] is handled all the way and is not converted to String in the call path at any point.

Looking more closely at this issue, we're unlikely to fix this in v2.x because we're targeting v3 for a revamped signature architecture. Maybe let's sync verbally to get your feedback on that design (and/or take a look at this branch if you're interested, in particular at the TransaactionSigner interface).
Note also that there's a different proposed interface that is meant for HSMs and delegated key-access -- see DelegatedTransactionSigner  (i.e., unless you're on an android phone, it's preferable to not use TransactionSigners because keys are in-memory in the JVM, as you point out).

FYI, I started a Discussion around this stuff here: https://github.com/XRPLF/xrpl4j/discussions/293. Let's move this over there (or re-open this if you want to advocate for trying to get this into v2).


Add a --no-skeleton extension

The skeleton.py file is nice but there should be a flag to avoid the creation of this file.

This was done in 53ad4ec8c92a0479d1b5afda9e76da736dc2c2d2


AOT compilation disabled! when bundling meteor app for production

I am getting a similar message to #1922 saying that AOT is disabled when I am trying to package up my meteor app for production. I do not use the angular CLI and it is not installed (installing this globally seems to make no difference).
@angular/compiler-cli is a dev dependecy whereas  @angular/compiler is a dependency in my package.json (which is the same as the example app).
Here is part of the log when bundling the app:
meteor npm install --production >/dev/null

NODE_OPTIONS=--max_old_space_size=4096 ROOT_URL=http://localhost:/ MAIL_URL=smtp://localhost:25 PORT=8400 AOT=1 meteor build --debug .dockerimage/ --directory --architecture os.linux.x86_64 --mobile-settings ./server/settings/dev.testing.json

WARNING: The output directory is under your source tree.
         Your generated files may get interpreted as source code!
         Consider building into a different directory instead
         meteor build ../output

@angular/compiler and @angular/compiler-cli must be installed for AOT compilation!
AOT compilation disabled!
Ignore this if you are using AngularJS 1.X

I've tried several times to get something installed that the compiler is happy with but AOT will not enable. I have forced @angular/compiler-cli to install after the install --production command. I have listed the installed npm's from within the deploy script and both of the mentioned npms are actually installed but the error message persists.
The actual error message is swallowed up in plugin/register.ts so it doesn't really tell you what the problem is. I debugged this by adding a console.error line to write out the error and it was complaining that typescript was not installed. Typescript is a dev dependency in my app (as well as installed globally)
Can you please update the error message to indicate that typescript is a requirement for AOT as well. It would also be useful if the actual error was printed to the console to assist in debugging any future issues.

@angular/compiler and @angular/compiler-cli must be installed for AOT compilation!
those two packages should be installed globally in the machine running the build

npm install -g @angular/compiler @angular/compiler-cli

@pmcochrane typescript is peer dependency of angular's compiler cli. You're right, we need to share error message as well.
@onhate No, they should not be installed globally in the machine.

How running with AOT in windows 10?
> AOT=1 ROLLUP=1 meteor --production

'AOT' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ start:prod: `AOT=1 ROLLUP=1 meteor --production`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ start:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

@aulrahman Just run meteor --production
And if you'd like to use env variables, you have to learn how to use env variables on Windows. They're different from Linux;
https://superuser.com/questions/79612/setting-and-getting-windows-environment-variables-from-the-command-prompt


Use starship prompt in header

Please describe the problem you're trying to solve
I'd like to have my starship prompt in the header instead of the default "~".
I've already experimented in lua with the header, because I found this tip.
As soon as I try to render it, the header just disappears entirely, am I doing something wrong?
In lf I configured the prompt like this:
cmd on-cd &{{
    export STARSHIP_SHELL=
    fmt="$(starship prompt)"
    lf -remote "send $id set promptfmt \"$fmt\""
}}

I'm sure something similar is possible in lua.
Thanks in advance!
Would you be willing to contribute this feature?

[X] Yes, I'll give it a shot

Describe the solution you'd like
Have the prompt of starship prompt appear in the header.
Maybe possible as a plugin or in init.lua.
Additional context
No response

After running starship prompt, I get this output:
❯ starship prompt

%{%}yazi%{%} on %{%} %{%}%{%}pr-c195b66a%{%} via %{%}🦀 %{%}%{%}v1.78.0-nightly%{%}%{%} %{%}
%{%}❯%{%} %

I'm not sure how to parse it, is there any documentation about it?

Not really, I had the same issue in lf. My workaround was to set the env var
STARSHIP_SHELL= to nothing for the calling shell in lf. I think then the prompt just gets printed as ascii.

You can achieve it by overriding Header:cwd() method.
The following code requires the latest main branch atm, since it uses a new ui.Line.parse() API to parse ANSI sequences into Yazi UI components.
https://github.com/sxyazi/yazi/assets/17523360/69b596b6-ab3d-4507-a02d-9c0cb7a90971
Sync version
Save these lines as ~/.config/yazi/plugins/starship.yazi/init.lua:
return {
  setup = function(st)
    Header.cwd = function()
      local cwd = cx.active.current.cwd
      if st.cwd ~= cwd then
        st.cwd, st.output = cwd, io.popen("STARSHIP_SHELL= starship prompt"):read("*a"):gsub("^%s+", "")
      end
      return ui.Line.parse(st.output)
    end
  end,
}

Then include it in your ~/.config/yazi/init.lua:
require("starship"):setup()

Async version (Recommend)
When in a very large Git repository, starship might slow down, thus blocking the Yazi UI thread rendering. However, this async version always executes starship asynchronously, avoiding any blocking on Yazi.
Save these lines as ~/.config/yazi/plugins/starship.yazi/init.lua:
local save = ya.sync(function(st, cwd, output)
  if cx.active.current.cwd == Url(cwd) then
    st.output = output
    ya.render()
  end
end)

return {
  setup = function(st)
    Header.cwd = function()
      local cwd = cx.active.current.cwd
      if st.cwd ~= cwd then
        st.cwd = cwd
        ya.manager_emit("plugin", { st._name, args = ya.quote(tostring(cwd)) })
      end

      return ui.Line.parse(st.output or "")
    end
  end,

  entry = function(_, args)
    local output = Command("starship"):arg("prompt"):cwd(args[1]):env("STARSHIP_SHELL", ""):output()
    if output then
      save(args[1], output.stdout:gsub("^%s+", ""))
    end
  end,
}

Then include it in your ~/.config/yazi/init.lua:
require("starship"):setup()

Works as expected with main, thanks a lot!
The async version is highly recommended, even on some mid-sized git repos there is a noticeable lag from starship.
Your last comment would probably fit very well into the tips section of your documentation, so that other users can find it easier :)


Add Maine Turnpike shield

I used a little stylized "TP" in place of the text part.

Pics from the web:
https://commons.wikimedia.org/wiki/File:Maine_Turnpike_sign.svg

You're off by half a pixel at 1x, causing the top bar of the T to be blurry:

You're off by half a pixel at 1x, causing the top bar of the T to be blurry

@jleedev Thanks, fixed.

Aligned:


[CARBONDATA-649] fix for update with rand

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[CARBONDATA-<Jira issue #>] Description of pull request

[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).

[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.

[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

[ ] Testing done
 Please provide details on
 - Whether new unit test cases have been added or why no new tests are required?
 - What manual testing you have done?
 - Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

retest this please


fix: increase the timeout value from 10 mins to 20 mins

Description
Increase the timeout value from 10 mins to 20 mins of the status-report test suite, so it waits longer for the PLR to start in case the system is under heavy load.
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e

/hold

The main motivation to double the timeout value is that I assumed the given test suite was failing due to the heavy load on the system. But that's not true, the test was failing because the spray proxy server was down (refer: RHTAPBUGS-1049). So, I'd rather not update the timeout value.
Hence, closing this PR. Thanks all for the reviews!


Make template lint use node glob to ensure consistent lint results across OS

[x] This PR follows the Contribution Guide
[x] Changelog updated
[ ] Upgrade guide entry added

Description / Motivation

This PR updates the npm lint command to use the node glob pattern (instead of the OS glob) for scaffolded projects. This makes linting results more consistent across different OS (e.g. windows development machine vs linux build server).
See https://stackoverflow.com/questions/54165756/eslint-glob-is-not-considering-all-directories-recursively
This node glob was introduced silently in the JSS development scripts (see https://github.com/Sitecore/jss/commit/786913d15aaccb2d38fb090d09062063e544f227), but it never made its way to the scaffolding templates.
Testing Details

[ ] Unit Test Added
[x] Manual Test/Other (Please elaborate)

I experienced this with an lint issue in my (customized) packages\create-sitecore-jss\src\templates\nextjs-sxa\src\Layout.tsx  file. The lint error was detected on Windows (**/*.tsx matches direct children), but not on Ubuntu linux (**/*.tsx does NOT match direct children).
After forcing to node glob pattern, the lint issue was detected on both Windows AND (Ubuntu) linux.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@Elyseum thanks for the PR and sorry for the delay with feedback. Do you think you'll be able to expand this over to vue sample too, for consistency? We can then merge it into jss proper.

I messed up my branch in the process, so I started over in https://github.com/Sitecore/jss/pull/1988. Sorry for that.


Policy "Turn on script scanning" missing

Hello,
I downloaded the latest security baseline for Windows Server 2022. In the Group Policy Report for the MSFT Defender Antivirus Server 2022, there is a parameter "Turn on script scanning" (supported from Server 2012/Win8) in the Real-time Protection section which is missing from the latest WindowsDefender.admx version. This parameter is added in Security Baseline for server 2022 but was not for Security Baseline for Server 2019.
So, this parameter must still exist for servers ? There is something to update in the latest ADMX ?
You don't mention this parameter in this documentation page.
Thank you in advance for your reply.
Kind regards,
Téva

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

ID: 67ba09a9-8323-a87f-83e7-61590de89e36
Version Independent ID: 41962064-f36a-f283-55d4-721c4c457cac
Content: Configure Microsoft Defender Antivirus with Group Policy
Content Source: microsoft-365/security/defender-endpoint/use-group-policy-microsoft-defender-antivirus.md
Product: m365-security
Technology: mde
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@denisebmsft Please help us in resolving this issue. Thanks

@yogkumgit I have reached out to the product team. Will post an update here soon.

Thank you @vTa47 for raising this issue. And thank you @yogkumgit for your help. I have updated the content, and the revisions will be live later today. Updates include a link to script scanning information (https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-defender) and the latest Group Policy Reference Spreadsheets. (Win 10: https://www.microsoft.com/download/details.aspx?id=101451; Win 11: https://www.microsoft.com/download/details.aspx?id=103506)


Intermittent error: ConnectNamedPipe failed: Windows error 232

I use winpty in a Node application with https://github.com/daviwil/node-pty-prebuilt. A customer is reporting intermittent errors:
[56365.101 node.exe,p19464,t5808]: libwinpty error: code=5 msg='ConnectNamedPipe failed: Windows error 232'

Any ideas what could cause this or how I can find out why it is happening? I have not seen it in any of our test environments and no other customer has reported this. The customer says that the problem is intermittent, and retrying the operation usually works. He is using Windows 10 Enterprise.
I am using node-pty-prebuild v0.7.3, which uses winpty 0.4.3. Logs from winpty-debugserver.exe are attached: winpty2.log.

I don't know why that would happen.

I have had another report of this problem from a different customer. I believe that it is caused by McAfee Endpoint Security interfering with the startup of the winpty agent. Both clients have this antivirus software installed, and disabling McAfee resolves the issue.
I have reproduced the same error with Avast antivirus. When libwinpty launches the agent, Avast scans winpty-agent.exe for threats (see screenshot). It then appears to kill the agent and relauch it (with a different pid). This is all hidden from libwinpty - CreateProcessW returns the pid of the second agent once the scan has finished. The problem is that the first agent already connected to and disconnected from the control pipe, so when libwinpty calls ConnectNamedPipe it returns ERROR_NO_DATA, which is the documented behaviour when the client has already disconnected from the pipe.
It seems like Avast and McAfee have similar approaches to threat detection, and both involve running the agent twice, probably in some kind of sandbox for the first run. One way to handle this could be for libwinpty to accept multiple client connections and loop until one of them is proven to be OK, similar to this: https://docs.microsoft.com/en-us/windows/desktop/ipc/multithreaded-pipe-server. libwinpty would also have to call ConnectNamedPipe before spawning the agent, rather than afterwards as it does today.
Do you think this is a reasonable change to make? Or do you have any other ideas about how libwinpty could be modified to handle this situation? I am happy to implement any suggestions and submit a pull request.
There are several other reports of this error, so I think it is worth fixing. These antivirus tools are only going to get more common and more intrusive.

https://github.com/JunoLab/atom-julia-client/issues/443
https://github.com/zeit/hyper/issues/2832

Thanks for debugging this.
In winpty2.log, when the first pipe connection fails (to winpty-control-19464-4-...), I don't see a previous connection attempt to the pipe. Maybe when the agent runs inside the antivirus sandbox, it's not able to report trace() messages?

... One way to handle this could be for libwinpty to accept multiple client connections and loop until one of them is proven to be OK, similar to this: https://docs.microsoft.com/en-us/windows/desktop/ipc/multithreaded-pipe-server. libwinpty would also have to call ConnectNamedPipe before spawning the agent, rather than afterwards as it does today.
Do you think this is a reasonable change to make?

I suppose something like that has to be done?
Would libwinpty need a worker thread to service connection attempts? The pipe is using overlapped I/O already, so with one control-pipe instance, it's fairly easy to start the ConnectPipe operation before spawning the agent, then finish the attempt after CreateProcess returns, but if I understand correctly, something in libwinpty would need to start another ConnectPipe operation between the antivirus killing the first agent instance and starting the second instance.
Would it be sufficient if libwinpty created 2 or more instances of the control pipe up front, then used the first good instance after the CreateProcess call? As long as there's an instance ready, I think(?) the agent would be able to successfully connect.
I suspect the antivirus software would allow whitelisting the winpty-agent.exe process, but users either don't know they need to do that or lack admin privileges.

I don't see a previous connection attempt to the pipe. Maybe when the agent runs inside the antivirus sandbox, it's not able to report trace() messages?

Yeah, I am assuming that McAfee blocks the trace messages somehow. I hope to verify this on the customer's machine soon. When running with Avast you can see both connections. See the attached winpty-avast.log.

Would it be sufficient if libwinpty created 2 or more instances of the control pipe up front, then used the first good instance after the CreateProcess call?

No idea. Presumably creating a multi-client pipe server is a normal thing to do so there must be a way of doing it such that the server doesn't miss any connections. I will look into it and see if I can get something working, using a worker thread if necessary.

I can reproduce the issue with Avast, and I have a change that works around it: https://github.com/rprichard/winpty/tree/antivirus.
Are you able to reproduce the problem with McAfee, and can you check whether my antivirus branch fixes it?

That's great, thanks so much for implementing this. I will ask our customer if they can test the patch with McAfee.

@rprichard Sorry for the delay, the customer took a while to respond, but they have confirmed that your change resolves the problem. Will you incorporate it into a winpty release at some point?

Yeah, at some point I'll merge the fix and put out a new release.

Any update on a new release? Thx

Any update on a new release? Thx

I recently started getting a the same error Error creating winpty: ConnectNamedPipe failed: Windows error 232 when I run node in a Windows 10 in BaSH, node v12.13.0.  I do not use — nor have I ever — McAfee, I use Malwarebytes.  I've used it for years and haven't had issues nor is there anything in Malwarebytes' logs that indicate any interference with winpty nor node.  Ideas?


refactor(levm): opcodes PUSHn

The implementation could be refactored to something simpler. The N can be a parameter of the generic function for example. Figure out if something more can be done simpler.

Closed in #1398


Replace pass-by-reference with mutability, clean up

For issue #321
This edit only affects the Avoid Side Effects (part 2) section.
It replaces the discussion of pass by reference with an explanation in terms of mutability.
By avoiding the confusing terminology and possible links to the implementation details of
different JS engines the explanation can be kept at an abstraction level that's great for
beginners and experts alike. I also cleaned up some grammar, typos, etc.

Very well written, thank you!


rsop: init at 0.3.9

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

src fetcher gives a 502

$ nix-build -A rsop.src
/nix/store/aq6fhvg1qx14w63345j89mc5mcb8jx4p-source

Seems to work fine now. Maybe there was a codeberg outage?

@ofborg eval

@Lassulus merge


Downloading a package fails with "404 Not Found" after a previous attempt to publish the package with an existing version fails

Describe the bug
Downloading a package fails with "404 Not Found" after a previous attempt to publish the package with an existing version fails.
To Reproduce
Steps to reproduce the behavior:

Create a new package, @my-co/my-package
Modify package @my-co/my-packageecho bump>>readme.md
yarn version

Publish package @my-co/my-packagenpm pack
npm publish

In another project, my-consumer, consume package @my-co/my-packageyarn add @my-co/my-package
yarn build

Modify original package, @my-co/my-package, but do not bump its versionecho bump>>readme.md

Publish same versioned package, @my-co/my-packagenpm pack
npm publish

This will correctly fail with an EPUBLISHCONFLICT error
Clear yarn cache and attempt to reconsume the package in my-consumer yarn cache clean
 yarn

Here the download fails with the following error$ yarn
yarn install v1.7.0
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred<EMAIL_ADDRESS>Request failed \"404 Not Found\"".

When inspecting differences changes in<EMAIL_ADDRESS>it appears the _rev property is changed even when the package should fail to be uploaded.
Rebooting the web server does not resolve the issue. The package at the version where the overwrite failed remains permanently unavailable.
Expected behavior
The package should remain available for download even when a previous attempt to overwrite it with the same version fails.
Configuration File (cat ~/.config/verdaccio/config.yaml)
storage: ./storage
auth:
  activedirectory:
    url: "ldap://ad.myco.local"
    baseDN: 'dc=myco,dc=local'
    domainSuffix: 'myco.local'
packages:
  '@*/*':
    access: $all
    publish: $authenticated
  '**':
    access: $all
    publish: $authenticated
logs:
  - {type: stdout, format: pretty, level: http}
url_prefix: https://npmjs.myco.com

I've repeated twice your steps but I cannot reproduce. In my case some slight differences

url_prefix: https://npmjs.myco.com I don't use proxy
yarn 1.9.2

_rev will change all the time, I guess if nothing changes, this field should remains the same.
Aside of that, I haven't found anything odd, I did not get any 404. So. I'd suggest try again, with latest and next and I'll wait your feedback.


vim.org's plugin update service is down

When uploading new script in vim.org, an error is encountered:
XXXX is empty, are you sure you specified the correct path?

But the file is not empty.

Now, it becomes like this:
POST has been used more than 500 times within 5 hours. Assuming bot attack. Retry again later. If you continue having trouble write to the mailinglist.

Now, it becomes like this:
POST has been used more than 500 times within 5 hours. Assuming bot attack. Retry again later. If you continue having trouble write to the mailinglist.

This indicates that something is trying to send a lot of requests to the website.  As mentioned in the error, please try again after five hours.

This indicates that something is trying to send a lot of requests to the website.  As mentioned in the error, please try again after five hours.

I found that one IP address was sending lots of requests.  I have blocked it, now it should work again.

I found that one IP address was sending lots of requests.  I have blocked it, now it should work again.

the first error happen again:
XXXX is empty, are you sure you specified the correct path?

the first error happen again:
XXXX is empty, are you sure you specified the correct path?


fix(google): mobile ui fixes

🔧 What does this fix? 🔧
fixes a bunch of bugs i found on mobile, including unthemed search suggestions, text and borders, i was able to test it by using chrome's devtools
closes #365
🗒 Checklist 🗒

[X] I have read and followed Catppuccin's contributing guidelines.
[X] I have updated the version appropriately in the ==UserStyle== header of the catppuccin.user.css file.

Thanks a lot for doing this!!! 🩷
I never got the time to deal with it.

@GitMuslim your welcome :)

for grammar purposes, it's you're, which means you are


docs: fix https://github.com/skeletonlabs/skeleton/issues/2245

Linked Issue
Closes #2245
Description
{description}
Changsets
Instructions: Changesets automate our changelog. If you modify files in /packages, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[x] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[x] Ensure Svelte and Typescript linting is current - run pnpm ci:check
[x] Ensure Prettier linting is current - run pnpm format
[x] All test cases are passing - run pnpm test
[ ] Includes a changeset (if relevant; see above)

Thanks @maehr I'm planning to run through an review new PRs over the next day or two. This seems like a useful fix though!

Thanks @maehr I'm planning to run through an review new PRs over the next day or two. This seems like a useful fix though!

You are welcome. Renaming the branch closed the PR. There is a new one https://github.com/skeletonlabs/skeleton/pull/2248
Best
moritz


Wrong version string dll on Nuget

The build date is correct, but the version text is not <IP_ADDRESS>.
Thanks.
Nuget: https://www.nuget.org/packages/DokanNet/<IP_ADDRESS>

Hi @jhlee8804 ,
Yes you are right. Thanks for the report.
This has already been fixed in a commit https://github.com/dokan-dev/dokan-dotnet/commit/6d967bede09e793d81e77df0e2f7ad7a48c1407c


Conform code to contemporary terminology

The glossary in #3076 gives terms for communicating about constructs in Coda.
The code should use the same terminology.

There wasn't interest in this idea.


Build failure: python3Packages.faiss (on Darwin)

Steps To Reproduce

On Darwin...
build python312Packages.faiss
Observe:

make: *** [Makefile:208: swigfaiss] Error 2
error: builder for '/nix/store/mbr9lq6ppqzws7q2qv6s70fhrhrzjl3z-faiss-1.8.0.drv' failed with exit code 2;
       last 10 log lines:
       >         return SWIG_NewPointerObj(data, SWIGTYPE_p_unsigned_long, 0);
       >                                         ^
       > /tmp/nix-build-faiss-1.8.0.drv-0/source/build/faiss/python/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx:5095:41: error: use of undeclared identifier 'SWIGTYPE_p_long'
       >         return SWIG_NewPointerObj(data, SWIGTYPE_p_long, 0);
       >                                         ^
       > 2 errors generated.
       > make[3]: *** [faiss/python/CMakeFiles/swigfaiss.dir/build.make:76: faiss/python/CMakeFiles/swigfaiss.dir/CMakeFiles/swigfaiss.dir/swigfaissPYTHON_wrap.cxx.o] Error 1
       > make[2]: *** [CMakeFiles/Makefile2:269: faiss/python/CMakeFiles/swigfaiss.dir/all] Error 2
       > make[1]: *** [CMakeFiles/Makefile2:276: faiss/python/CMakeFiles/swigfaiss.dir/rule] Error 2
       > make: *** [Makefile:208: swigfaiss] Error 2
       For full logs, run 'nix log /nix/store/mbr9lq6ppqzws7q2qv6s70fhrhrzjl3z-faiss-1.8.0.drv'.
error: 1 dependencies of derivation '/nix/store/wnjfqxjfakg3m3ymdf9bf661zm3rzxq2-python3.12-faiss-1.8.0.drv' failed to build

This is a known issue when swig generates Darwin code: https://github.com/swig/swig/issues/2864
Faiss accepted a patch for the next release: https://github.com/facebookresearch/faiss/commit/bd22c936e108d4551648435764b126aef40b4530
Notify maintainers
@SomeoneSerge
cc: @natsukium
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"aarch64-darwin"`
 - host os: `Darwin 23.6.0, macOS 14.6.1`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Add a :+1: reaction to issues you find important.

Unfortunately, cherry-picking the patch didn't work. I'll close this for now as I don't see a way to patch around it; I'll see if I can lobby for an interim faiss release.

So the issue is still present? Then we should keep this open?

Yes, it's still present so let's keep this open.
I've asked the faiss team if they could cut a release to include Darwin. We'll see what they say.
Otherwise, I'll keep looking into potential patches.

See https://github.com/facebookresearch/faiss/issues/3846

@SomeoneSerge they are producing a new release next week!

Closed by #341418

Closed by #341418


volatile GPU-util is pretty low

Hi, I run the command "nvidia-smi" and I found the "volatile GPU-util" is around 20%. Do you think it has not fulfilled my GPU potential?
The GPU memory-usage seems to be good. It shows 7865MiB /  7951MiB.
Also, "volatile GPU-util" is not always 20%, it can be 20% for one second and drop to 0% in the next second, and then go back to 20% again. I mean the figure seems to be 0%-20%-0%-20%... I can hear my GPU fan run fast-slowly-fast-slowly...

In GTX 1080Ti, the "volatile GPU-util" is 0%~80%.
If you model already fixed, you can delete the validate code in training to reduce the 0% "volatile GPU-util" circumstance.

I set the params['pred_image_on_tensorboard'] to be false. I think the validation should be stopped.


concurrency anamoly for pipeline drivers

Handle multiple requests for pipeline driver when not needed due to concurrency jobs.

This change is

/deploy dev

/deploy dev

/deploy dev

/deploy dev

/deploy dev

/deploy dev

/deploy dev

/deploy dev


Type issue in directions

Describe your problem and - if possible - how to reproduce it
penguin class should declar the --penguin-skin variable and assign it to gray.
penguin class should declar the --penguin-skin variable and assign it to white.
penguin class should declar the --penguin-skin variable and assign it to orange.
On all three statements, "declar" should read "declare"
Also notice the "--penguin-skin" variable does not change to reflect "--penguin-belly" or "--penguin-beak"
Add a Link to the page with the problem
https://learn.freecodecamp.org/responsive-web-design/basic-css/use-css-variables-to-change-several-elements-at-once
Tell us about your browser and operating system

Browser Name:
Browser Version:
Operating System:

If possible, add a screenshot here

Also notice the "--penguin-skin" variable does not change to reflect "--penguin-belly" or "--penguin-beak"

I'm pretty sure that's intentional, but the variable name is not precise. I would suggest renaming the "--penguin-skin" variable to "--penguin-back" or "--penguin-dorsal-skin" or "--penguin-dorsal-feather", something along the lines. Although I don't think it's necessary.(penguins have feather btw)

Really? The var name in the style section reads:
/* change code below /
--penguin-skin: black;
--penguin-belly: gray;
--penguin-beak: yellow;
/ change code above */
But in the instructions it has all --penguin-skin. The instructions are usually fairly precise on what var should be changed to which assignment.
Did not know that about penguins and feathers (but it makes sense if we are thinking they are birds)

I think it should read:
penguin class should declare --penguin-skin variable and assign it to gray.
penguin class should declare --penguin-belly variable and assign it to white.
penguin class should declare --penguin-beak variable and assign it to orange.

Hi @KoniKodes. I decided to check the link you sent above and this is a screenshot of what I see. I am not sure where you are getting this issue.

@KoniKodes you are right I misunderstood the problem, however, I think this issue has been fixed, for me it's correctly displayed. Is it still an issue on your part?

Wonderful! It's been fixed.
Thank you so much!

In this lesson, I don't know if I don't understand or there is an error. I just can't pass through!!

The error continues when I add the "background"

This seems to be a problem both in Chrome and Firefox. Now on my page, the background stays the original pink color and does not change to #c6faf1 - and the message says to do what we are supposed to do.

Perhaps the instructions aren't clear. You are supposed to Change the value of --penguin-belly to white in the penguin class.
like this...
  .penguin {
    /* add code below */
    --penguin-belly: white;
    /* add code above */

Since the original issue here has been fixed, I am going to close this. Feel free to create a new issue if either of you think the instructions need to be reworded. Thanks!

doesn't work @moT01 your solution doesn't work, even after i change background: var(--penguin-belly, pink); to background: var(--penguin-belly, white);

I'm running into an issue where the correct answer is not allowing me to complete the segment.
Code:

@avery-windham
If I do what the instructions say, I pass the tests.
Please go to the FreeCodeCamp Forum and open a topic.
Github issues are only for technical issues, not for asking for lesson-specific help. :slightly_smiling_face:

.penguin {
**/* Only change code below this line */
--penguin-skin: _gray_;
--penguin-belly: _white_;
--penguin-beak: _orange_;
/* Only change code above this line */**

position: relative;
margin: auto;
display: block;
margin-top: 5%;
width: 300px;
height: 300px;

}


[media-common-openvpn] Initial version

Special notes for your reviewer:
@DirtyCajunRice This is the library chart to provide openvpn add-on support to media-common. See #45 for implementation
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [radarr])

This looks really good.


v0.2.7

Updates dependencies and introduces new URLs (original author donated to r-lib).
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender


Use <IP_ADDRESS> for livereload address

🚀 Feature
At the moment live reload is hardcoded to use localhost for its address which stops it working inside a docker container. This request is to change it to <IP_ADDRESS> to allow livereload to work when visited from the host machine.
Have you read the Contributing Guidelines on issues?
Yes
Motivation
To enable Docusaurus to be containerised it would be handy to have livereload work from outside the container.
Pitch
If a developer is able to view the output of livereload served from within a container then a Docusaurus instance can be packaged in a node based Docker container and a self contained environment can be given to other developers so they can write documentation without having node installed locally.

Guys any chance this will be implemented soon?


Modify log to add ngx.var.uri in request object

Summary
ngx.var.request_uri is the original uri and is not updated if the uri is changed using ngx.set_uri(newUri). Instead, ngx.var.uri reflects the new uri. Added a new field to reflect the modified uri.
Full changelog

Use the same name as the Nginx variables in request object of logs
Rename request_uri to request_url
New unit test

Issues resolved
Fix #2441

request_uri contains query arguments, uri does not. If the only difference here is a post-normalized representation, I think we need to append the query string. Thoughts?

@shiprabehera any update on the changes requested above?

Thanks for the update @shiprabehera! There is a merge conflict in the serializer though. Can we resolve this?

@p0pr0ck5 , thanks for mentioning that.
0010bce has core router changes and does not refer to variables from the log file I have updated. This patch makes log variable names same as Nginx, does not change any core functionality.
Also, few integration tests seem to fail. Could this be related?
Thanks.

Hi @shiprabehera, sorry for the delay on this end. I will look over this again soon and let you know!

@thibaultcha do you still have pending requested changes here? I still need to review this :) Just catching up on any blockers.

@p0pr0ck5 Nothing outstanding! This is looking good to me, at a glance. Although, if we are about to break to introduce more meaningful names to those properties, I'm thinking: "why not renaming uri to upstream_uri...

Thanks thibaultcha!

why not renaming uri to upstream_uri

@shiprabehera any thoughts on this comment?

@p0pr0ck5 @thibaultcha
Sounds good! As long as we have clear distinction between them, no problem. Will update this asap.

@thibaultcha
Fixed it.

This LGTM. Will wait for @thibaultcha to dismiss the review, then I think we're good to go here.

Looking good to me! Good to highlight this will be our first breaking change introduced after the 0.11.0 release - which means once this gets merged to next, it will be the first non-backwards compatible change compared to master!

(It looks like this patch could use some rebasing though - @shiprabehera will you take care of it to release a bit of the burden from @p0pr0ck5's shoulders? 😄)

@shiprabehera Thanks for giving it a try, but could we have only 1 commit here, like:
feat(log) improve uri fields in basic log serializer

* add `request.upstream_uri`
* rename `request.uri` to `request.request_uri`
* rename `request.request_uri` to `request.request_url`

From #2445

And no merge commit at all?
Thanks!

@thibaultcha
Done. Thanks!

@shiprabehera Great, thank you!

Merged! Thank you @shiprabehera - and sorry for the delay on our side. As per our breaking change policy, this should be scheduled for release in our next major version.

Thank you @thibaultcha


Error in Setup

HI,
thank you very much for this integration. I tried to setup this according your documentation.
I added all the files to custom components (including the 2 subfolders).
I restarted and found the integration in HA.
I then setup the hub put in Name, Host, User and PIN. I saw that it tried to connect but in the logs I got this fault:
`Logger: homeassistant.setup
Source: setup.py:333
First occurred: 12:59:31 (1 occurrences)
Last logged: 12:59:31
Error during setup of component qsys_qrc
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 333, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/qsys_qrc/init.py", line 259, in async_setup
CONF_CONFIG: config[DOMAIN],
~~~~~~^^^^^^^^
KeyError: 'qsys_qrc'`
Any idea?

Hi,
I could solve the Problem by editing the config file and adding the
change_group:           poll_interval: 1.0           request_timeout: 5.0
(Also described in another issue I did not see yesterday: https://github.com/nkvoll/home-assistant-qsys-qrc/issues/1)
Thanks a lot for the work :-) I could realize my first toggle with your integration.
I now want to setup a 7x1 Input router but do not get it to work. Any idea?
I posted it in the HA forum: https://community.home-assistant.io/t/qsys-qrc-integration/693476
Thanks S

I think the first error may simply be that I assume there is at least some related config for the integration present in configuration.yaml. Definitely something that should be fixed.
For the latter, I've just responded on the HA forums since you put the details there :)

Closing this as #1 should be fixed. Let me know if the problem actually haven't been resolved.


Get BoxOffice List

Please Add Get BoxOffice List in PHP-IMDB-Grabber Class

The /business page is difficult to parse. Not only would the script need to do another request (which slows down the output), but the layout of this page seems to be random most of the times. :(

for function boxoffice list , only get (Poster,Title,Weekend,Gross,Weeks)
with this link:
http://www.imdb.com/chart/?ref_=hm_cht_sm


About running the project

Hi sir
Can you please help me to run this project i didn't understand what should I run first and what next.
So can you please provide me the  "sequence of the python files or the commands to be executed "to get the output.

First, you have to install all the required pip packages, simply run
pip3 install -r requirements.txt

Next, you need to follow the README.md to prepare dataset.
With dataset being ready, you can run do the following things:

for training 3d radar Object Detection.python3 train.py

for training 3d radar Object Detection.python3 train_cart.py

for testing:python3 evaluate.py

for visualization of the dataset itselfpython3 visualize_testdata.py

In addition, you can change your GPU id with the code below:
import os
os.environ["CUDA_DEVICE_ORDER"]="PCI_BUS_ID"
os.environ["CUDA_VISIBLE_DEVICES"]="0"

change the value 0 to the GPU id you want.
Hope I made this clear.

First, you have to install all the required pip packages, simply run
pip3 install -r requirements.txt

Next, you need to follow the README.md to prepare dataset.
With dataset being ready, you can run do the following things:

for training 3d radar Object Detection.python3 train.py

for training 3d radar Object Detection.python3 train_cart.py

for testing:python3 evaluate.py

for visualization of the dataset itselfpython3 visualize_testdata.py

In addition, you can change your GPU id with the code below:
import os
os.environ["CUDA_DEVICE_ORDER"]="PCI_BUS_ID"
os.environ["CUDA_VISIBLE_DEVICES"]="0"

change the value 0 to the GPU id you want.
Hope I made this clear.

Thank you for the reply sir😊
While running the visualization of testdata.py file i am getting the error in this line "config = loader.readConfig()" loader has no attribute named readconfig can you please suggest me the solution?

You may need to goto the project root dir to run this script. It wull call the readConfig() function in util/loader.py.

Thank you for your response
I have tried to call the function from the root directory only but i am
getting error
On Fri, 25 Nov 2022, 1:36 pm ZhangAoCanada, @.***>
wrote:

You may need to goto the project root dir to run this script. It wull call
the readConfig() function in util/loader.py.
—
Reply to this email directly, view it on GitHub
https://github.com/ZhangAoCanada/RADDet/issues/22#issuecomment-1327133814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIYNX33APQ2JRXHFELBOB3WKBXPHANCNFSM6AAAAAARGAT3PU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you please share the trained waits so can i use it directly for the
testing purpose
On Fri, 25 Nov 2022, 2:07 pm 01fe19bec162 ., @.***>
wrote:

Thank you for your response
I have tried to call the function from the root directory only but i am
getting error
On Fri, 25 Nov 2022, 1:36 pm ZhangAoCanada, @.***>
wrote:

You may need to goto the project root dir to run this script. It wull
call the readConfig() function in util/loader.py.
—
Reply to this email directly, view it on GitHub
https://github.com/ZhangAoCanada/RADDet/issues/22#issuecomment-1327133814,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIYNX33APQ2JRXHFELBOB3WKBXPHANCNFSM6AAAAAARGAT3PU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi, the pre-trained weights are already provided in README.md.
I am attaching it here for convenience. https://drive.google.com/drive/folders/1EZQtcAUzVKYmYHDuiiV_FB5Obk7PbSoE?usp=sharing

Thanks sir , I'll check it out.
On Mon, 28 Nov 2022, 8:53 am ZhangAoCanada, @.***>
wrote:

Hi, the pre-trained weights are already provided in README.md.
I am attaching it here for convenience.
https://drive.google.com/drive/folders/1EZQtcAUzVKYmYHDuiiV_FB5Obk7PbSoE?usp=sharing
—
Reply to this email directly, view it on GitHub
https://github.com/ZhangAoCanada/RADDet/issues/22#issuecomment-1328485447,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOIYNXYYD6RRLHKJV4VEFZ3WKQQTLANCNFSM6AAAAAARGAT3PU
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey, in evaluate.py you're loading the data for the plot.

In line 219, 233 and 238 the code is trying to access paths "input_dir, image_dir and gt_dir which arent in the config. Therefore an error occurs with "file not found".
are these just the test directorys and then the gt, rad and image directorys?
thanks!


Outdated data displayed on iOS

On computer I can see D2R data (such as new area 85 areas), but on iPhone I see only the legacy data. It is reflected in the code as classes ios-hidden and ios-visible respectively. The former has new data, the latter is outdated.
Please update the mobile part, or, better, merge the tables so there is only one source of data and control how is it displayed by using RWD.

Thanks for the bug report!  Fixed in v1.72.

Ah, RWD = Responsive Web Design.  Thanks for the tip.  Something to look into in the future.


Add the md5sum field to parquet filenames

Need to extract md5 info from filename in send_msg_file

Whoops md5.h included unistd.h

Whoops md5.h included unistd.h

unistd.h needed by read() etc...