launch at login not working

brew config output
HOMEBREW_VERSION: 3.6.1
ORIGIN: https://github.com/Homebrew/brew
HEAD: 6e2b162c4786e075323f038d46bfb566d91889e7
Last commit: 10 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 58aed4a3d5bc19a6200069eab46d2b6a95e3398a
Core tap last commit: 4 days ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: :1
HOMEBREW_EDITOR: vim
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.8 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8_1/bin/ruby
CPU: dodeca-core 64-bit zen
Clang: N/A
Git: 2.30.2 => /bin/git
Curl: 7.74.0 => /bin/curl
Kernel: Linux 5.18.0-0.deb11.4-amd64 x86_64 GNU/Linux
OS: Debian GNU/Linux 11 (bullseye) (bullseye)
Host glibc: 2.31
/usr/bin/gcc: 10.2.1
/usr/bin/ruby: N/A
glibc: 2.35
gcc@11: 11.3.0
xorg: N/A

brew doctor output
Your system is ready to brew.

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I want to have brew services launched when I log into my session (postgresql, redis).
What happened (include all command output)?
Despite the doc, brew services start redis does start the service but does not "register it to launch at login" (not running with sudo).
Or maybe it does register it, but the system (debian bullseye / gnome shell) doesn't run the necessary brew magic to start the services?
What did you expect to happen?
I did expect the brew services to be running after new login / reboot.
Step-by-step reproduction instructions (by running brew commands)
On debian bullseye / gnome shell:
1. brew install redis
2. brew services start redis
3. log out and in again, or reboot
4. brew services shows that redis is not running
(brew services start redis launches redis properly)

What happens when you run systemctl --user status homebrew.redis after login?

It shows the following:
● homebrew.redis.service - Homebrew generated unit for redis
     Loaded: loaded (/home/user/.config/systemd/user/homebrew.redis.service; enabled; vendor preset: enabled)
     Active: inactive (dead)

Can I look up somewhere whether the necessary hook / service file has been set up by brew services start redis?

Well, it's reported as loaded and enabled so it seems your login somehow didn't trigger systemd to start the service. Anything to that extend in journalctl -u homebrew.redis?

Not much, apparently just saying that there is indeed nothing to start up:
-- Journal begins at Thu 2022-09-15 12:03:04 CEST, ends at Wed 2022-09-21 13:50:26 CEST. --
-- No entries --


User not being removed from database while autokick

Example:

(via bypass, kicked by TAK ban)

Interesting, looks like it bot doesn't listen for own events. This will be fixed soon.

fixed in 4c6021d1e2522b01eac794ce46e410818184007d


TILA-2582: Update Django to 4.2.1 and Python to 3.10

Change log

Updated Django to 4.2.1
Updated a ton of packages to latest version
Updated code to work with upgraded packages and with Python 3.10

Other notes
Well that was an adventure, but at least it works on my machine. All tests are green and I also tested Django Admin and GQL API and didn't find any issues.
PostgreSQL 11 is not supported anymore so for local development image must be upgraded to version 13. This might mean database reset unless you want to somehow backup and restore all the data. Existing database files are not compatible with version 13.
Deployment reminder

[ ] Update environments to use Python 3.10

Existing database files are not compatible with version 13.

🙈


Introduce a common props template for C++ projects

As mentioned here, we're using many msbuild properties which we must copy-paste to keep consistent across all our .vcxproj. It's error-prone and time-consuming process. I suggest we do the same thing we did for Version and deps

We're going to split common library as part of this task as well.


Add some patterns to the background

Pure white can be boring and a bit blinding at times.

I'm thinking the ICPC zoom background patterns (on Figma?) with some parallax.

I spent like 3 hours on this and got nowhere. Nevermind.


Fix logging for expired FQDN IPs

Current logging has been implemented in #14878 using Warning level.
As reported in #15935 this causes lots of log lines to be generated at
each garbage collection cycle.
The fix here is to move the log generation from Warning to Debug.
Fixes: #15935
Signed-off-by: Youssef Azrak<EMAIL_ADDRESS>

No need for more testing than the default GitHub actions. Marking as ready to merge.

could we consider this PR to be back-ported in 1.10?

Makes sense to me given it's a fix. I added the label.

awesome, thanks @pchaigno! :bow:


added image removal functionality

Codecov Report

Merging #63 (1b2bdaa) into main (c06c8bf) will decrease coverage by 3.02%.
The diff coverage is 30.88%.

@@            Coverage Diff             @@
##             main      #63      +/-   ##
==========================================
- Coverage   88.32%   85.30%   -3.03%
==========================================
  Files          13       14       +1
  Lines        1293     1347      +54
==========================================
+ Hits         1142     1149       +7
- Misses        106      153      +47
  Partials       45       45

Impacted Files
Coverage Δ

rm.go
0.00% <0.00%> (ø)

ls.go
86.84% <100.00%> (-0.97%)
:arrow_down:

runtime.go
90.16% <100.00%> (+3.49%)
:arrow_up:

Continue to review full report at Codecov.

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


fix(back-office-subscribers): rename nsip-document and whitelist properties to consume

update Document table schema to reflect latest changes to nsip-document message schema
amend consumer function to store only from a pre-defined list of columns

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

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

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


WHERE keyword not implemented properly

Azure Data Studio Version:

Steps to Reproduce:
Getting an error saying "Invalid column name 'name'".
I wrote:
SELECT * FROM table
WHERE column="name";
I'm getting red squigglies on "name" showing the error message

What you pasted isn't a valid statement to begin with - for example " aren't valid string delimiters in T-SQL.
Could you provide more information such as the table schema you're trying to select from and paste the exact query that's giving you the error?

Nevermind, put this issue as resolved. Sorry for the convenience

@RedRevYol thanks for confirming.


getEthGas polish

Change
previous interface
{
  "method": "eth_getEthGas",
  "params": [21000000, 64100, 1000000]
}

current interface
{
  "method": "eth_getEthGas",
  "params": [{
      "gasPrice?": 21000000,
      "gasLimit?": 64100,
      "validUntil?": 1000000
  }]
}

now every param is optional, so developers can do the following default query to get default gas params for big gas operations, such as contract deployment.
{
  "method": "eth_getEthGas",
  "params": []
}

which returns same result as
{
  "method": "eth_getEthGas",
  "params": [{
      "gasPrice": 21000000,
      "gasLimit": 64100,
      "validUntil": currentBlock + 150
  }]
}

Test
added tests accordingly

hold on one sec there is one small type

@gluneau @ThunderDeliverer could you double check the new interface makes sense? If it does I will merge it and deploy to public mandala, thanks


MediaSample project.  The method or operation is not implemented.

I am trying to make your sample project working on Android but it always throws "The method or operation is not implemented." for the first time I click "Take Photo" on
var file = await CrossMedia.Current.TakePhotoAsync(...
and "Only one operation can be active at at time" on the next attempts during one debug session.
Compile using Android version: 8.1 Oreo (tried 7.0 and 7.1)
Debugging via Xamarin Live player.
VS Community 2017 ver. 15.7.6
Xamarin   <IP_ADDRESS>
Version Number of Plugin: Xam.Plugin.Media <IP_ADDRESS>
Device Tested On: Meizu PRO7, Xiaomi mi5c
Could it be that I am doing something wrong?
Maybe StackTrace will help
at System.Reflection.Assembly.GetName (System.Boolean copiedName) [0x00000] in :0
...

I have the same problem and I still can't solve it, I read that it would work with a "try catch" but when selecting the button again it does not call me to the function

this happens when I debug with Xamarin Live. Deploying to the physical device works fine.


GeoJSONLayer doesn't update on layerOptions.filter change

Related to #169. map.setFilter was only added to Layer.

Is it okay if I work on this issue?

@4xDMG That would be awesome. I am currently using Layer + Source instead.

@4xDMG  Sure any PR for this is welcome :)

Awesome. I'll give it ago tomorrow.

@4xDMG any update on this by any chance?

Since I need that, I'm also woring on it

Released with version 2.3.0


podmanv2 pod ps

add the ability to list pods in podmanv2
Signed-off-by: Brent Baude<EMAIL_ADDRESS>

Tested local and remote. Smoke tests are working fine but the output differs from v1 and --format doesn't work.
* `--format` doesn't seem to work.

libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --format "{{ .ID }}"
Error: template: listPods:1:15: executing "listPods" at <.ID>: can't evaluate field ID in type *entities.ListPodsReport

* The output of `--ctr-ids` has changed (CONTAINER INFO -> IDS) and from single item slice to a comma-separated string. Similar issue for `--ctr-{names,status}`.

libpod (v2podps) $ sudo podman pod ps --ctr-ids
POD ID         NAME   STATUS    CREATED         CONTAINER INFO                                  INFRA ID
276c991d67e4   bar    Created   4 minutes ago   [3f2d23b8ea47] [77b09cf530d7]                   77b09cf530d7
414c1d262dc4   foo    Created   4 minutes ago   [2114797d8640] [4fc699833841] [c5db7907f6ef]    4fc699833841
libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --ctr-ids
POD ID        NAME    STATUS   CREATED        IDS                                     INFRA ID
276c991d67e4  bar     Created  4 minutes ago  3f2d23b8ea47,77b09cf530d7               77b09cf530d7
414c1d262dc4  foo     Created  4 minutes ago  2114797d8640,4fc699833841,c5db7907f6ef  4fc699833841

Tested local and remote. Smoke tests are working fine but the output differs from v1 and --format doesn't work.

    --format doesn't seem to work.

libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --format "{{ .ID }}"
Error: template: listPods:1:15: executing "listPods" at <.ID>: can't evaluate field ID in type *entities.ListPodsReport

    The output of --ctr-ids has changed (CONTAINER INFO -> IDS) and from single item slice to a comma-separated string. Similar issue for --ctr-{names,status}.

libpod (v2podps) $ sudo podman pod ps --ctr-ids
POD ID         NAME   STATUS    CREATED         CONTAINER INFO                                  INFRA ID
276c991d67e4   bar    Created   4 minutes ago   [3f2d23b8ea47] [77b09cf530d7]                   77b09cf530d7
414c1d262dc4   foo    Created   4 minutes ago   [2114797d8640] [4fc699833841] [c5db7907f6ef]    4fc699833841
libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --ctr-ids
POD ID        NAME    STATUS   CREATED        IDS                                     INFRA ID
276c991d67e4  bar     Created  4 minutes ago  3f2d23b8ea47,77b09cf530d7               77b09cf530d7
414c1d262dc4  foo     Created  4 minutes ago  2114797d8640,4fc699833841,c5db7907f6ef  4fc699833841

Tested local and remote. Smoke tests are working fine but the output differs from v1 and --format doesn't work.
* `--format` doesn't seem to work.

libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --format "{{ .ID }}"
Error: template: listPods:1:15: executing "listPods" at <.ID>: can't evaluate field ID in type *entities.ListPodsReport

* The output of `--ctr-ids` has changed (CONTAINER INFO -> IDS) and from single item slice to a comma-separated string. Similar issue for `--ctr-{names,status}`.

libpod (v2podps) $ sudo podman pod ps --ctr-ids
POD ID         NAME   STATUS    CREATED         CONTAINER INFO                                  INFRA ID
276c991d67e4   bar    Created   4 minutes ago   [3f2d23b8ea47] [77b09cf530d7]                   77b09cf530d7
414c1d262dc4   foo    Created   4 minutes ago   [2114797d8640] [4fc699833841] [c5db7907f6ef]    4fc699833841
libpod (v2podps) $ sudo ./bin/podmanV2 pod ps --ctr-ids
POD ID        NAME    STATUS   CREATED        IDS                                     INFRA ID
276c991d67e4  bar     Created  4 minutes ago  3f2d23b8ea47,77b09cf530d7               77b09cf530d7
414c1d262dc4  foo     Created  4 minutes ago  2114797d8640,4fc699833841,c5db7907f6ef  4fc699833841

use {{ .Id}}

and yes, format is changing a bit for clarity

/hold
/lgtm

/hold cancel


Implement better-npm-run

Issue #1: Figure out how to forward on CLI arguments so commands such as dev:nw and dev:no-debug don't need to entirely duplicate the dev command. Tracking https://github.com/benoror/better-npm-run/issues/20.
Issue #2: Wait for an npm release that includes this fix: https://github.com/benoror/better-npm-run/pull/15 so that better-npm-run does not have to be explicitly referenced inside of node_modules. This isn't necessary to re-integrate better-npm-run, but it would be nice.

@fuczak adding you here just in case you happen to know of a quick fix for issue #1. I temporarily pulled out better-npm-run because the solution through duplication was fairly inelegant. In the meantime, I removed the explicit NODE_ENV=development prefixes, which were no longer necessary anyways.

I've had a busy weekend, too. Sorry I couldn't help but it seems that new version of better-npm-run will solve both issues so that's nice.

Closing this issue for now since better-npm-run is not actually needed with the removal of explicit NODE_ENV overrides in npm scripts. Willing to re-open if a need arises.


Handle hrefs during line breaking.  #1022

Fix line breaking to handle hrefs properly both when they are split and when they are not.  This affects HTML-CSS, CHTML, and SVG output.  Resolves issue #1022.

lgtm


gRPC API Endpoint

Description
Rekor could expose a gRPC endpoint along with REST which will help with performance #481 to publish large binaries

https://github.com/sigstore/rekor/issues/481#issuecomment-970236333


Turbo homepage is unbearably laggy without hardware acceleration

Which project is this feature idea for?
Turbopack
Describe the feature you'd like to request
Without hardware acceleration enabled on your browser, turbo.build is unbearably laggy. I've tried on the latest version of Brave and Chrome browsers and on both my personal and work computer. I can barely even scroll down on the page. I was having the same issue with the vercel conf signup page.
With hardware acceleration enabled, everything works smoothly.
I'm honestly not sure why it's so slow, but I suspect it has something to do with the grid animation, mainly because the page otherwise seems simple.
I hope I don't sound too critical, I'm a huge fan of the work vercel has been doing and enabling.
But right now,  it's a bit frustrating to need to use a separate browser without hardware acceleration enabled to view a docs page.
Describe the solution you'd like
Performance without hardware acceleration improved
Describe alternatives you've considered
Using specific browsers and settings for vercel docs

This does look like a legitimate issue with rendering the many gradients and animations involved on the home page. However, I'm seeing just 4 reactions on here after over a year and I'd have to assume that having hardware acceleration turned off is a distant edge case.


Improve the list of current games

We should not force the user to install additional software (such as extensions and others) so that he can view a list of current and past games.
In other words, you need to receive data from the block, regardless of the user environment
see https://github.com/EverscaleGuild/everscale-random
Actual

Expect

@thanhlmm Please keep up to date, or decide to give up, let us know it is essential, and of course, ask any questions.

Thanks @ilyar, I will take a do and keep you update :)

I added a PR for this issue, please take a look @ilyar

@thanhlmm make submit PR on gitcoin

@thanhlmm There are technical difficulties on our side, we will close the bounty a little later within 1-2 days

@thanhlmm 0:8f01e2034bd4b3a736c2213d3ffc49fc86da13a39498d1ecd16e3d9135fccad4 I sended 10 coins for testing, send back 1 coin so I can make sure you control the address (Satoshi Test).

Hi @ilyar , I transfer back 1 coin to you, here is tx https://everscan.io/transactions/7ec4f648f0318ec7de72795d458a54d780357b90f7f3de9e9fad4d55a026d536

@thanhlmm thx https://everscan.io/transactions/310ec4cd15f6a8d3a8bf8694a86909d60618bdc752cae9ec1c45116801ae3c17

Thanks @ilyar , I would love to work more if you guys have any issue with Everscale and its ecosystem :)


fix compiler switch fallthrough warning

Coverage decreased (-2.06%) to 80.415% when pulling e07e5a32357d1fe646b6f2b6f122016e5788e86f on rrojo/fix-fpga_hw-build into b2a80e3a6bab302464d1b31d3d2b79ab8c23609b on master.


Use a dropdown (single-choice) property for the type of STK asset

In Blenders scene properties, you are able to select multiple types of STK assets (library, track kart). Only one should be valid. For creating multiple assets in one Blender file, multiple scenes should be used.

Done in 773a85aa7dc3df83649a07957e3d0d9c74ca0d0a, along with so much more conditional UI improvements.


Add travis test configs

The current travis config tests js, go, ruby, python and rust.
But cpp, dart, java, js/closure are not automatically tested. Also weirdly travis thinks it tests js three times and I don't know what's going on there.
The new travis.yml file uses matrix:include to set up a node.js and rust instance.
Travis has a language setting for dart.
cpp, java and js/closure are currently tested using bazel BUILD files. It may make sense to have a single configuration that tests all three to reduce the number of times bazel has to be fetched.

All configs are added except for visual basic. I'm ok with this since it's formatted as a spreadsheet macro, not plain VB code.


Using Infer for Technical-Debt calculation?

Infer is really great tool, I tried it for Android projects and was impressed by its detection of Context leaks, although it was a false positive [will upload the scenario with example] but was helpful to see that wrong parameter can cause problems.
I am doing master thesis at RWTH university Aachen, I need to develop a tool which will detect code smells / bad code design to determine and quantify Technical Debt. After initial research about existing platforms and tools I shortlisted two to compare and select one as a base. One is of course Infer and other is MOOSE [http://moosetechnology.org]
I wanted to know what do you think about me extending Infer platform by using existing infer AST and CHECKERS etc to crawl code repositories to determine Design flaws instead of bugs. And adding functionality or additional Checkers per say which can determine Technical Debt. Does current Infer stack give enough information about the code structure to determine different design flaws like, Deep Inheritance hierarchies , Feature Envy, Brain Method, Brain Class, Significant duplication etc.
I know I won’t get APIs or method calls which will just return me required information( that will be my job to develop these though) but just wanted to know before going deep into it, if it sounds like a good idea to someone who knows all in/outs of Infer already. Your feedback will be much appreciated.

Infer would likely be suitable for this. I don't know enough about the code smells you mention to know which ones will be easy vs hard, but if all you need is to look at the CFG/class hierarchy then Infer is good for that (and will work with multiple languages!).
You'd probably want to implement your each code smell analyses as a separate checker. Simple ones can just iterate over the CFG, and fancier ones that need dataflow information/interprocedural analysis can use the checkers abstract interpretation framework,
Let me know if you have any more questions or need some more specific pointers!

Closing for now, feel free to reopen or file a new issue if you have another question.


Error in Lapacke 'dstev' during the Lanczos_Gnd_Ut

When running Lanczos_Gnd and Lanczos_Gnd_Ut in DMRG one may encounter:
Error in Lapack function 'dstev' : Lapack INFO = -4
This means that the fourth argument (subdiagonal of the tridiagonal matrix?) had an illegal value, this may appear when the starting vector in a Lanczos iteration is already the eigenvector of the matrix in problem, causing the zero norm of vector in a iteration and may result in some divide by zero operations later.
We should optimize the workflow to avoid such a situation.

Similar issue should also occur when using Lanczos_ER, although in that case no Lapack error is observed so far but it may cause some numerical instability.

c3525255e9235be5fb72fa8447e9feeec880f33b


[app] Expand interaction to allow slash command and other.

Summary

This PR add the ability to create slash command, user command, message command on either the bot directly or on cogs.
This PR is still work in progress. :)
Sample:
from discord.ext import commands

bot = commands.Bot()

@bot.slash_command()
async def echo(ctx, message: str):
	await ctx.send(message)

bot.run("token")

Can also be used via cogs:
from discord.ext import app, commands

class TestCog(commands.Cog):
	def __init__(self, bot):
		self.bot = bot

	@app.slash_command()
	async def echo(self, ctx, message: str):
		await ctx.send(message)

bot = commands.Bot()
bot.add_cog(TestCog(bot))

bot.run("token")

Checklist

[x] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[ ] This PR fixes an issue.
[x] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

Difference between other repo (that I've seen atleast).

Use it's own folder for managing all applications.
Making sure it's being separated as much as possible from the original ext.commands implementation.
Allow using the same name as long as the type is different.
Most of the stuff are typed.

Most of the code as I'm writing this is ready, the only thing left is some implementation to Slash group.
I borrowed a lot of code from pycord first implementation and some part from dislash.py for the group implementation.
Most of the code written here are mostly the same as "improvement" that I'm making for pycord

After some more testing, slash/user/message now works as intended.

Hey! thanks for working on this.Is this going to be eventually merged with pycord?

No, it will be kept here since pycord already has their own implementation.
You can use the feature/slash branch on pycord if you want support for application command.

alright. Thanks!


Implement strict_mode keyword parameter in binascii.a2b_base64()

Since Python 3.11, binascii.a2b_base64() function became to provide strict_mode keyword parameter. ^1
Related links

Python docs: https://docs.python.org/3/library/binascii.html?highlight=binascii#binascii.a2b_base64
RustPython implementation: https://github.com/RustPython/RustPython/blob/1d8269fb729c91fc56064e975172d3a11bd62d07/stdlib/src/binascii.rs#L147
CPython implementation: https://github.com/python/cpython/blob/deaf509e8fc6e0363bd6f26d52ad42f976ec42f2/Modules/binascii.c#L388

I can try to take this on! I'm new to the project but I'll take a stab at it.

Not sure why that PR got closed - I'm still working on it, though it may take a while.

closed by #4460