pylintgui error

Description
What steps will reproduce the problem?

Using miniconda I tryed to upgrade spyder to 5.3.3 version

conda update
conda install spyder=5.3.3

When opening Spyder 5.3.3 an error occurs
Traceback
  File "/opt/anaconda3/lib/python3.7/site-packages/spyder_pylint/widgets/pylintgui.py", line 446, in show_data
    self.treewidget.set_results(filename, results)
  File "/opt/anaconda3/lib/python3.7/site-packages/spyder_pylint/widgets/pylintgui.py", line 82, in set_results
    self.refresh()
  File "/opt/anaconda3/lib/python3.7/site-packages/spyder_pylint/widgets/pylintgui.py", line 106, in refresh
    for module, lineno, message, msg_id in messages:
ValueError: too many values to unpack (expected 4)

Versions

Spyder version: 3.3.6
Python version: 3.7.0
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Darwin 17.7.0

Dependencies
pyflakes >=0.6.0  :  2.1.1 (OK)
pycodestyle >=2.3 :  2.5.0 (OK)
pygments >=2.0    :  2.4.2 (OK)
sphinx >=0.6.6    :  2.2.0 (OK)
rope >=0.9.4      :  0.14.0 (OK)
jedi >=0.9.0      :  0.15.1 (OK)
psutil >=0.3      :  5.6.3 (OK)
nbconvert >=4.0   :  5.6.0 (OK)
pandas >=0.13.1   :  0.25.1 (OK)
numpy >=1.7       :  1.17.2 (OK)
sympy >=0.7.3     :  1.4 (OK)
cython >=0.21     :  0.29.13 (OK)
qtconsole >=4.2.0 :  4.5.5 (OK)
IPython >=4.0     :  7.8.0 (OK)
matplotlib >=2.0.0:  3.1.1 (OK)
pylint >=0.25     :  2.4.2 (OK)

Hey @blancfrederic, thanks for reporting. You said:

Using miniconda I tryed to upgrade spyder to 5.3.3 version

It seems your attempt was not successful because the error you're reporting is related to Spyder 3.3.6, which we don't support anymore. So, the easiest way to make Spyder work again is to uninstall Anaconda and reinstall its latest version. Please follow the instructions in our video to learn how to do that in the right way.


SAK-31608 Adding context.xml for all webapps to set scanClassPath=false

It's entirely possible that EVERY webapp/META-INF doesn't need a context.xml and only a few would fix this bug. But I don't know how to figure out which few need it. I started up without errors and without log warnings after adding it to everyone. 2 of them already had a context.xml which I just modified.

From what I can tell not every webapp needs this, it just looks like maybe these ones. And it some contrib tools might have a problem. I'm not sure what it is about these that are causing it. The easiest solution is just to modify conf/context.xml but OOTB this provides a better experience.
Ideally if someone could dig into this more and provide a test case/fix to tomcat it would be great, but I don't see that as a valuable time investment with such an easy workaround.
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/oauth-tool.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/authn.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/sakai-calendar-tool.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/emailtemplateservice-tool.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/sakai-editor.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/sakai-syllabus-tool.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/sakai-mailarchive-tool.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/sakai-reset-pass.war
INFO: Deploying web application archive /home/matt/sakaibin/sakai-bin-12-SNAPSHOT/webapps/dashboard-tool.war

One thing to remember is that this will not cover contrib tools or other webapps someone may include.
Optionally the sakai maven plugin's deploy mojo could be updated to have the context.xml be added to tomcats global context.xml.
But yeah any of these strategies are secondary to having the Apache Tomcat project just fix the issue!

Yeah, if this error did come in a contrib tool it could be fixed by adding this context.xml
And yeah, we could deploy it there but there might be local modifications someone would make rather than use this version. So yeah nothing is ideal.
They already ignore a lot of specific jars from the scanner for some reason and I'm not sure why .

One other thing to note if any webapp in the future wanted to perform configuration via annotation's like servlet 3.0's @WebServlet they will probably need this to work, and not have it disabled!

So with the tomcat issue merged what do you think about this one? Was either merge this change to every tool, or just try it on the ones specifically affected. It doesn't seem to matter either way.

Closing, will be incorporated by SAK-25750


chore: clean backport

When the backport task runs inside a cloned repository directory, it doesn't do a fresh clone, and relies on the local git status to be up to date.
Instead of trying to update it, always run the backport task in an empty directory. This causes some performance hit, but is worth the stability.

💔 All backports failed

Status
Branch
Result

❌
k8s-21/main
An unhandled error occurred. Please see the logs for details

❌
k8s-20/main
Backport failed because of merge conflictsYou might need to backport the following PRs to k8s-20/main: - feat: bump cdk8s to version 2.x (#696)

Manual backport
To create the backport manually run:
backport --pr 695

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-21/main

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
k8s-20/main

Questions ?
Please refer to the Backport tool documentation


Aws Testing

I have FINALLY fixed and completed steps.  We are ready to start working on endpoints!

Ignore that some checks are not successful, that is Arjun's code conflicting with the Jest test system in place


Cog slash commands not registering in Discord

So, I've been trying to make slash commands work for my bot, but I didn't quite get it to work the way I wanted it to. I was only able to make slash commands work if I put them in the main bot file.
# main.py
from discord_slash import SlashCommand, SlashContext

cogs = []
for cog_file in os.listdir('cogs/'):
    if cog_file.endswith('.py'):
        cog_import = 'cogs.' + cog_file.split('.')[0]
        cogs.append(cog_import)

bot = commands.Bot(  # Create a new bot
    # ...
)
bot.slash = SlashCommand(bot, override_type=True, sync_commands=True, sync_on_cog_reload=True)

@bot.slash.slash(name="testnt", guild_ids=[1234567890])
async def _test(ctx: SlashContext):
    await ctx.send(content="test", hidden=True)
    # This works.

bot.run(token, bot=True, reconnect=True)

I cannot get it to work within cogs. Chances are I'm doing something wrong (which is why I opened an issue to get help).
# cogs/slash.py
import discord
from discord.ext import commands
from discord_slash import cog_ext, SlashContext

guild_ids = [1234567890]

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

    def cog_unload(self):
        self.bot.slash.remove_cog_commands(self)
        pass

    @cog_ext.cog_slash(name="testcog", description="Test", guild_ids=guild_ids)
    async def _test(self, ctx: SlashContext):
        embed = discord.Embed(title="embed test")
        await ctx.send(content="test", embeds=[embed], hidden=False)

def setup(bot):
    bot.add_cog(Slash(bot))

This is all I see in Discord.

It obviously tries registering testcog, but just can't, since if I try to define a slash command named testcog inside main.py, it throws an error at me talking about "hey there's two commands with the same name i can't register them" or something similar to that.

update: Slash commands in cogs only load after reloading the cog. I tried doing so with Jishaku and it only then showed the commands inside the cog.

When do you initially load the cog?

The cog is loaded on the on_ready() event.

Is it the first but of code excluding the slash command?

not sure I understand that...

You'll need to load cogs before the bot is run.

oh, that... explains a lot.
thanks.

You'll need to load cogs with slash commands before the bot is run.

Not just before the bot is running, but also after the SlashCommand client is created.
class BotClient(commands.Bot):
    def __init__(self, **kwargs) -> None:
...
        for cog in INITIAL_COGS:
            try:
                self.load_extension(cog)
                print(f"Cog \"{cog}\" loaded.")
            except Exception:
                traceback.print_exc()
...

if __name__ == "__main__":
    bot = BotClient()
    slash = SlashCommand(bot, sync_commands=True, sync_on_cog_reload=True, override_type=True)
    bot.run()

This didn't run either. To fix it I had to put SlashCommand client inside BotClient class __init__ before loading cogs.

I actually think that could be fixed to allow loading before. Might be worth opening a fr


How to install on google colab after forking the dm_control in your github account?

This was the error I received after trying to install the fork or clone of dm_control stored in my github account
ERROR: Command errored out with exit status 1: /usr/bin/python3 -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/content/src/dm-control/setup.py'"'"'; file='"'"'/content/src/dm-control/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(file) if os.path.exists(file) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.
this is the code I executed on google colab for installing the fork of dm_control stored in my github account
##@title Run to install MuJoCo anddm_control`
import distutils.util
import subprocess
if subprocess.run('nvidia-smi').returncode:
raise RuntimeError(
'Cannot communicate with GPU. '
'Make sure you are using a GPU Colab runtime. '
'Go to the Runtime menu and select Choose runtime type.')
mujoco_dir = "$HOME/.mujoco"
print('Installing OpenGL dependencies...')
!apt-get update -qq
!apt-get install -qq -y --no-install-recommends libglew2.0 > /dev/null
print('Downloading MuJoCo...')
MUJOCO_VERSION = 210
MUJOCO_ARCHIVE = (
f'mujoco{MUJOCO_VERSION}-{distutils.util.get_platform()}.tar.gz')
!wget -q "https://mujoco.org/download/{MUJOCO_ARCHIVE}"
!wget -q "https://mujoco.org/download/{MUJOCO_ARCHIVE}.sha256"
check_result = !shasum -c "{MUJOCO_ARCHIVE}.sha256"
if _exit_code:
raise RuntimeError(
'Downloaded MuJoCo archive is corrupted (checksum mismatch)')
print('Unpacking MuJoCo...')
MUJOCO_DIR = '$HOME/.mujoco'
!mkdir -p "{MUJOCO_DIR}"
!tar -zxf {MUJOCO_ARCHIVE} -C "{MUJOCO_DIR}"
Configure dm_control to use the EGL rendering backend (requires GPU)
%env MUJOCO_GL=egl
print('Installing dm_control...')
Installing dm_control
#################!pip install -q dm_control==0.0.403778684 #commented out
instead of using deepmind account use the fork of dm_control in your account
!pip install -e git+https://github.com/navidyou/dm_control#egg=dm_control==0.0.403778684
print('Checking that the dm_control installation succeeded...')
try:
from dm_control import suite
env = suite.load('cartpole', 'swingup')
pixels = env.physics.render()
except Exception as e:
raise e from RuntimeError(
'Something went wrong during installation. Check the shell output above '
'for more information.\n'
'If using a hosted Colab runtime, make sure you enable GPU acceleration '
'by going to the Runtime menu and selecting "Choose runtime type".')
else:
del suite, env, pixels
`

Could you please try again with the updated Colab notebook that was uploaded today?

Closing this issue. If the problem persists in the updated colab notebook please reopen.

Hello Saran, Thank you so much for your update. The package installs like before. However, I still cannot install a fork or clone of dm_control. Have you tried to fork or clone dm_control to a new github account and install it from there?

Try removing the -e flag from your pip install invocation ("edit-mode" installations don't work because of the way we automatically generate the ctypes bindings for MuJoCo during the build process)

@alimuldal  Removing -e flag from pip install solved my problem. You saved me from a lot of headache. Thank you so so much
I could install the clone of dm_control from my local github account.
@saran-t I did have to use the new colab that was updated today where Mujoco was downloaded from deepmind rather than mujoco.org. Thank you so so much
Thank you both for your help. I really appreciate it.


Add class diagram

Related issue

Helps DMT-106

Proposed changes

Add class diagram

Nice work! :+1:


Use react as a peer dependency

Fixes #19

Hi @marcosalles , thanks a lot for reporting this issue and please check the review changes.


write unix /var/run/docker.sock->@: write: broken pipe

I'm sending commands to different containers; this was working correctly until a few days ago. Since then, the only thing that changed is; a new Docker version was released and I switched from a TCP connection to a socket connection. Rest of the commands execute fine.
Information:
$ php -v
PHP 7.0.5-1~dotdeb+8.1 (cli) ( NTS )

$ docker -v
Docker version 1.11.0, build 4dc5990

$ uname -a
Linux docker-host 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux

$ cat /etc/issue
Debian GNU/Linux 8 \n \l

Apr 21 07:35:46 docker-host docker[11709]: time="2016-04-21T07:35:46.790486036Z" level=error msg="attach: stdout: write unix /var/run/docker.sock->@: write: broken pipe"
Apr 21 07:35:46 docker-host docker[11709]: time="2016-04-21T07:35:46.931491694Z" level=error msg="Error running exec in container: attach failed with error: write unix /var/run/docker.sock->@: write: broken pipe\n"
Apr 21 07:35:46 docker-host docker[11709]: time="2016-04-21T07:35:46.931563085Z" level=error msg="Handler for POST /exec/fc6c278bc319d31ae125e6bfe62aab3bed6ae54d64223597e2c7a367fd540153/start returned error: attach failed with error: write unix /var/run/docker.sock->@: write: broken pipe"
Apr 21 07:35:46 docker-host docker[11709]: 2016/04/21 07:35:46 http: response.WriteHeader on hijacked connection
Apr 21 07:35:46 docker-host docker[11709]: 2016/04/21 07:35:46 http: response.Write on hijacked connection

Update: The problem occurs also when using a TCP connection:
Update: When using a TCP connection there are less of these errors then when using a socket connection.
Apr 21 08:33:24 docker-host docker[25468]: time="2016-04-21T08:33:24.772961231Z" level=error msg="attach: stderr: write tcp <IP_ADDRESS>:2375-><IP_ADDRESS>:40968: write: broken pipe"
Apr 21 08:33:25 docker-host docker[25468]: time="2016-04-21T08:33:25.890528192Z" level=error msg="Error running exec in container: attach failed with error: write tcp <IP_ADDRESS>:2375-><IP_ADDRESS>:40968: write: broken pipe\n"
Apr 21 08:33:25 docker-host docker[25468]: time="2016-04-21T08:33:25.890563806Z" level=error msg="Handler for POST /exec/aca8b3206f70586afa35766edf858827b57dd1e7a5643878df1996c8c818f061/start returned error: attach failed with error: write tcp <IP_ADDRESS>:2375-><IP_ADDRESS>:40968: write: broken pipe"
Apr 21 08:33:25 docker-host docker[25468]: 2016/04/21 08:33:25 http: response.WriteHeader on hijacked connection
Apr 21 08:33:25 docker-host docker[25468]: 2016/04/21 08:33:25 http: response.Write on hijacked connection

Docker issue: https://github.com/docker/docker/issues/22221

I did a downgrade to Docker version 1.10.2. This version is working for me. I do still get partial error messages. The command did executed correctly.
Apr 22 12:11:19 docker-host docker[11787]: time="2016-04-22T12:11:19.080010253Z" level=error msg="attach: stdout: write unix /var/run/docker.sock->@: write: broken pipe"
Apr 22 12:11:19 docker-host docker[11787]: time="2016-04-22T12:11:19.109409630Z" level=error msg="Error running exec in container: attach failed with error: write unix /var/run/docker.sock->@: write: broken pipe\n"

I'm experiencing the same issue with Docker 1.9.1.

FYI, I upgraded and the problem is solved. Behind, it was an 400 response from the Docker daemon.

Networks errors, are mainly due to the socket lib used, however there is so many reasons when this can happens, i don't think there is a good way to fix that.
One of the possibility, if you have bad network, would be to add the RetryPlugin of php-http.
Closing this, dont hesite to reopen it, if you can produce a reproducible use case.


Unhandled Command:  114

Getting an error "Unhandled Command:  114" for command send using RM mini. Using the plugin for both RM pro and Rm mini, no error with RM pro.
A snippet of the log file
[2/11/2019, 11:22:25 AM] [Broadlink RM] Bed TV Volume Down sendHex (<IP_ADDRESS>; 78::0:F::77::1:9::F9::3:9)<PHONE_NUMBER>01289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 Unhandled Command:  114 [2/11/2019, 11:22:25 AM] [Broadlink RM] Bed TV Volume Down sendHex (<IP_ADDRESS>; 78::0:F::77::1:9::F9::3:9)<PHONE_NUMBER>01289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 Unhandled Command:  114 [2/11/2019, 11:22:26 AM] [Broadlink RM] Bed TV Volume Down sendHex (<IP_ADDRESS>; 78::0:F::77::1:9::F9::3:9)<PHONE_NUMBER>01289413121213121213121312131213121312133713371337133712371312133713371337133713371337121213121337131213121312131213121337133712131237130005440001264b13000d050000000000000000 [2/11/2019, 11:22:26 AM] [Broadlink RM] Bed TV Volume Down setSwitchState: (automatically turn off in 2.5 seconds) Unhandled Command:  114 [2/11/2019, 11:22:28 AM] [Broadlink RM] Bed TV Volume Down setSwitchState: false

Having this issue also with lights, seems that the setSaturation method isn't defined

Me too, same error on air conditioner:
[2019-5-28 22:26:21] [Broadlink RM] Air Conditioner Advanced setCurrentHeatingCoolingState: 0
May 28 22:26:21 octopi homebridge[3484]: Unhandled Command:  114

Me too, same error on air conditioner:
[2019-5-28 22:26:21] [Broadlink RM] Air Conditioner Advanced setCurrentHeatingCoolingState: 0
May 28 22:26:21 octopi homebridge[3484]: Unhandled Command:  114

Same exactly error. What are we doing bad? I only have two settings on A/C:
"defaultCoolTemperature": 25,
"defaultHeatTemperature": 23,
What can be the reason? thanks

Is everyone getting this error using an RM Mini? I've been looking around under the hood and this error seems to happen when receiving data back from the device - which, other than learning codes and the initial negotiation, doesn't happen to my knowledge on an RM Mini.

Hi , got the sema error on my RM Pro Plus. the only thing that has changes is a firmware upgrade on the RM. Any clue ?

Hey, this is due to receiving a command back from the RM devices that we don't recognise. I guess it's a new one. It anyone actually seeing issues because of it?

I'm seeing this too. I suspect Broadlink have added an acknowledgment response. I haven't been able to find anything to support this theory but I only see this on successful commands. i.e. If I send a code when the Broadlink is off the network I don't get this message.

This morning I had a command fail to send at 5:30 which I then successfully resent at 5:34 by cycling the switch off then on again. The logs show no "Unhandled Command" for the failed command, but it's there for the successful one. This backs up my theory of it being a command send acknowledgement from the RM Mini.
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: false
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: true
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (<IP_ADDRESS>; 34:ea:34:6f:bb:f7)<PHONE_NUMBER>012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:29:57 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (<IP_ADDRESS>; 34:ea:34:6f:bb:f7)<PHONE_NUMBER>012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: true
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: false
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (<IP_ADDRESS>; 34:ea:34:6f:bb:f7)<PHONE_NUMBER>012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame getSwitchState: false
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame setSwitchState: true
Mar 11 05:34:10 homebridge[6738]: [Broadlink RM] Photo Frame sendHex (<IP_ADDRESS>; 34:ea:34:6f:bb:f7)<PHONE_NUMBER>012996121411151213121312381213111312131239113912381238121312381239113812381238123812391238121312131213121312131214121311141238123812381200052200012b4b12000c560001294c12000d05
Mar 11 05:34:10 homebridge[6738]: Unhandled Command:  114
Mar 11 05:34:11 homebridge[6738]: Unhandled Command:  114

Any updates on this issue?


Update i-o-request-packets.md

Correct typo from I/0 to I/O.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Ensure bytebufs are released if various encoders throw exception.

Performance boost for utf8 string encoding.

Good point! Thanks


make resize handle accept ref

Currently the resize handle doesn't accept a ref and a quick look at the code tells me it's because it's already being used internally.
I want to be able to forward a ref to the handle element and a quick solution to this is to compose the refs with something like this hook used by the radix team.
e.g.:
- export function PanelResizeHandle({
+ export const PanelResizeHandle = React.forwardRef<HTMLDivElement, React.ComponentPropsWithoutRef<"div"> & PanelResizeHandleProps>({
  // props...
  ...rest,
- }: PanelResizeHandleProps) {
+ }, forwardedRef) => {
const divElementRef = useRef<HTMLDivElement>(null);
+ const internalRef = useComposedRefs(divElementRef, forwardedRef)

// ...

 return createElement(Type, {
    ...rest,
    // ...
- ref: divElementRef,
+ ref: internalRef,

Not sure how the other components do it but I guess any method works

I want to be able to forward a ref to the handle element

I don’t want to add a ref-forward to this component because there is no API to it. The other components, the ones that have refs, only have them because of their APIs.
If you need to get a ref to the underlying DOM element, I suggest you read it in an effect (and store it in your own ref). All the resize handle does is render a single div (with a data attribute that you can use to query it).
Each of these components have data attributes to make them accessible via query selectors. That’s how I interact with them internally as well.
Let me know if you have any questions or if this doesn't make sense.

❤ → ☕ givebrian.coffee

Each of these components have data attributes to make them accessible via query selectors. That’s how I interact with them internally as well.

Oh alright, thanks. Though... I'm confused as to why having an API is a requirement to provide access to the underlying element? Do you see any disadvantage in making it available to the user?

It’s about consistency. Panel and PanelGroup components supports refs, but not as pass throughs to the DOM elements they render. Rather, their refs expose custom APIs (like a resize method).
You’re asking for a pass through to the underlying DOM element, which I could add, but then the resize handle component would be different/inconsistent with those other components.
The most consistent way to interact with the underlying DOM elements in this library is using the data attributes (in an effect).

❤ → ☕ givebrian.coffee

That makes sense, thanks for the awesome library ❤


az sql mi create fails with 400 error

Describe the bug
Creating a managed instance fails with 400 error.
Virtual cluster is created but no other resources are deployed.
Command Name
az sql mi create
Errors:
400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 603, in execute
    raise ex
cli/core/commands/__init__.py, ln 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
...
python3.6/site-packages/msrestazure/azure_active_directory.py, ln 486, in get_msi_token
    result.raise_for_status()
python3.6/site-packages/requests/models.py, ln 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Create subnet, nsg, route table using steps listed here https://blogs.msdn.microsoft.com/sqlserverstorageengine/2018/03/14/how-to-configure-network-for-azure-sql-managed-instance/
az sql mi create -n {} -u {} -p {} -g {} -l {} --vnet-name {} --subnet {}

Expected Behavior
Managed instance should be created
Environment Summary
Linux-4.15.0-1055-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.72

Additional Context

Minor update - the step creates a "Microsoft.Network/networkIntentPolicies" resource and "Virtual cluster" resource and leaves these in the resource group upon failing. They cannot be deleted manually, and running the command az sql mi delete produces the following result after some time:
The command failed with an unexpected error. Here is the traceback:

400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 603, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 661, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 654, in _run_job
    six.reraise(*sys.exc_info())
  File "/opt/az/lib/python3.6/site-packages/six.py", line 693, in reraise
    raise value
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 631, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 305, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 485, in default_command_handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/sql/operations/managed_instances_operations.py", line 407, in delete
    **operation_config
  File "/opt/az/lib/python3.6/site-packages/azure/mgmt/sql/operations/managed_instances_operations.py", line 370, in _delete_initial
    response = self._client.send(request, stream=False, **operation_config)
  File "/opt/az/lib/python3.6/site-packages/msrest/service_client.py", line 336, in send
    pipeline_response = self.config.pipeline.run(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/__init__.py", line 197, in run
    return first_node.send(pipeline_request, **kwargs)  # type: ignore
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/__init__.py", line 150, in send
    response = self.next.send(request, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/msrest/pipeline/requests.py", line 65, in send
    self._creds.signed_session(session)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/adal_authentication.py", line 26, in signed_session
    scheme, token, _ = self._token_retriever()
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/_profile.py", line 540, in _retrieve_token
    return self._get_token_from_cloud_shell(resource)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/_profile.py", line 373, in _get_token_from_cloud_shell
    auth = MSIAuthentication(resource=resource)
  File "/opt/az/lib/python3.6/site-packages/msrestazure/azure_active_directory.py", line 592, in __init__
    self.set_token()
  File "/opt/az/lib/python3.6/site-packages/msrestazure/azure_active_directory.py", line 598, in set_token
    self.scheme, _, self.token = get_msi_token(self.resource, self.port, self.msi_conf)
  File "/opt/az/lib/python3.6/site-packages/msrestazure/azure_active_directory.py", line 486, in get_msi_token
    result.raise_for_status()
  File "/opt/az/lib/python3.6/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://localhost:50342/oauth2/token

Hi, deploying managed instance has specific network requirements that can be found here. https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-connectivity-architecture#network-requirements
In order to prepare your vnet and subnet for managed instance deployment, you can follow instructions from this article as article that you have linked is not maintained anymore
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-configure-vnet-subnet

The same networking configuration was used to deploy managed instance using the Azure portal, therefore points to it being an issue with the azure cli not the networking setup.
Even so, expected failing behaviour of the cli command would be an output which describes the issue with the networking as per the portal.


Limit eth.getLogs range size with no contract address

Those are expensive and could time out. Not much performance is lost in that case since in the default scenario we'll just do 50 requests of size 500 to cover 10000 blocks.
Tested locally on subgraphs with and without contract address.

@leoyvens @olibearo This has been sitting here for a while, do we still want to integrate it?

I believe we do, @olibearo wanna approve this?

Looks good, just need to resolve the conflicts in the docs. The markdown unordered list symbol changed in my PR yesterday

@olibearo thanks, rebased.


Why is react-native-screens mandatory now?

Since the latest version react-native-screens is now mandatory required, otherwise the app throws an error.
At the moment react-native-screens is quite problematic, and it's also an alpha release, far from being stable and working for production.
Also given the fact that it's an optimisation and not a necessary core part of react-navigation, I wonder if it would be possible to keep it as an optional dependency, at least until it will reach a stable version.
At the moment I have to install it but luckily I can avoid to call enableScreens() and the library is disabled, but still I need to install it and I hope what I'm doing won't cause any problems.

It was always required to install. Nothing new. Metro doesn't support optional dependencies.
If you don't want to use it, don't enable it. It won't do anything.


Upgrading to the new integer protocols

@parkera I've just merged the new integers into master. Is it OK for me to merge this one?

This is blocking PR testing on Linux so I'm going to merge it.


example-vue-vite is broken

On Node.js v15.8.0 npm install gave me the following log:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vue
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@fower/vue
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Pull code and try again~

Pull code and try again~

Thanks!


Реализация автоподхвата односкриптовых тасков апи 2.0.0

https://github.com/xDrivenDevelopment/1c-syntax/issues/273
@nixel2007

Codecov Report

Merging #67 into develop will decrease coverage by 0.75%.
The diff coverage is 19.73%.

@@             Coverage Diff             @@
##           develop      #67      +/-   ##
===========================================
- Coverage    57.79%   57.04%   -0.76%
===========================================
  Files           21       21
  Lines         2175     2223      +48
  Branches       441      446       +5
===========================================
+ Hits          1257     1268      +11
- Misses         916      953      +37
  Partials         2        2


Icon request : Paket

I want to create an icon request for Paket
Icon Name: paket
Sample original Icon: https://dl.dropboxusercontent.com/u/11302680/logo.png
Extensions:

paket.dependencies
paket.lock
paket.references
paket.template
paket.local

Are this extensions or file names?

They're the file names


Split code

I move CLI display logic out of index.js
I move browse step out of index.js
I fix export in file.
--destFile was broken we should add test on it.

Perfect, thanks!


MAISTRA-531: Add multitenancy support to prometheus

linked to https://github.com/Maistra/istio-operator/pull/204

@knrc Would it make sense to separate the vendor changes into a separate PR? 720 files makes for a big CR.

@knrc Would it make sense to separate the vendor changes into a separate PR? 720 files makes for a big CR.

Not a separate PR, but a separate (pre) commit is worthy. That way reviewers can pick only the relevant commit to review.

@jwendell Stick with the first four files as I mentioned in the team meeting this morning.


Add the Mozilla central servo sync account as an operator.

r? @edunham
@globau tells me that https://github.com/moz-servo-sync is the account that sheriff backouts will appear as. In order to auto-approve and support treeclosed, I was thinking that it would make sense to make it an operator.

This change is

@larsbergstrom I agree with the idea of giving a shared sheriff account sufficient perms to close the tree. Can you or @globau point me to docs on:

Who gets access to that account Especially, who hands out access when they decide that a new sheriff needs it?
When they get access, what docs will a new account collaborator read to learn what they should and shouldn't do with it? (I'd like to make sure our instructions there are kept up to date if tree closure ever changes)
When someone leaves, what's the process for deprovisioning them from the shared account?

Even if these docs are behind a Mozilla LDAP wall, I would like to look over them just to make sure we aren't accidentally introducing a huge vulnerability by adding this account.

Who gets access to that account

the only people who have access are those who also have root access to the systems running servo-vcs-sync.  ie. selected dev-ops and developers.  this excludes sheriffs and contributors.
best to ask fubar about what happens with regards to staffing changes and access.

From further conversations with @globau, the credentials are stored in a wonderfully secure manner with extremely limited access to the underlying API key. I'm comfortable that the Firefox protections are at least as good as our own protection of the @bors-servo account :-)

Is this a human account or a bot account? If the latter, are we planning to add another interface for closing the tree than writing GitHub comments to bors-servo?

it's a bot account.
lars and i discussed a few times an out of band signalling mechanism such as SQS (it would help reduce race conditions) but it wasn't really viable to fit that into the schedule.  if need be we can investigate that later.

@edunham @metajack Can we get this landed now? We need this ASAP for testing!

@bors-servo r+
I'd appreciate a pointer to the code be left here, or a page created in the wiki so people know where to start looking if something weird happens.

:pushpin: Commit 817c124 has been approved by metajack

:hourglass: Testing commit 817c1242b8e78a0fd8827e90fecc81d64cdabb28 with merge 90c52cb5c1675fdd94cbf670908d99bce45c7d65...

The Gecko side backout code is here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1365181

:broken_heart: Test failed - status-travis

@bors-servo retry

repo timeout thing

:hourglass: Testing commit 817c1242b8e78a0fd8827e90fecc81d64cdabb28 with merge e013e0090a1839b2a61f76a2c602768b6d8d4831...

:sunny: Test successful - status-travis
Approved by: metajack
Pushing e013e0090a1839b2a61f76a2c602768b6d8d4831 to master...

I deployed this yesterday.


bug: ion-virtual-scroll  is overlapping on slow network connection

ion-virtual-scroll not rendering data correctly on slow network.
I tested with  3g network on chrome and the ion-virtual-scroll items gets overlapped.
This bug is related to https://github.com/ionic-team/ionic/issues/18409 but I created this ticket as this bug appears always on slow network.
e.g
home.page.html looks like
<ion-header>
  <ion-toolbar color="primary">
     Lorem
  </ion-toolbar>
</ion-header>
<ion-content *ngIf="(obser$| async) as testArray">
  <ion-virtual-scroll [items]="testArray" approxItemHeight="320px">
    <div *virtualItem="let item;">
    <app-demo [personTile]="item" ></app-demo>
    </div>
  </ion-virtual-scroll>
</ion-content>

and home.page.ts
export class HomePage {
  obser$: Obserable<Person[]>;
  constructor(private service: LoremService) {
    this.obser$ = this.service.getAllPersons();
  }

and app.demo.ts
export class AppDemoComponent {
  @Input()
  personTile: Person;

and app.demo.html
<ion-card>
 <ion-card-content>
    <ion-grid>
      <ion-row>
        <ion-col>
          {{personTile.name}}
        </ion-col>
          ....
       </ion-row>
    </ion-grid>
  </ion-card-content>
</ion-card>

Ionic version:
ionic cli : 5.4.15
"@angular/router": "~8.1.2",
"@capacitor/android": "^1.4.0",
"@capacitor/core": "1.4.0",
"@ionic-native/core": "^5.20.0",
"@ionic-native/splash-screen": "^5.20.0",
"@ionic-native/status-bar": "^5.20.0",
"@ionic/angular": "^4.11.10",

Thanks for the issue. I am going to close this as a duplicate of https://github.com/ionic-team/ionic/issues/18409. I was able to reproduce the issue regardless of network connection speed. ion-virtual-scroll does not make any network requests by default, so it may just be a matter of lazy loaded scripts loading in slowly.


Support for AnnotationTypeDeclaration

https://github.com/junit-team/junit4/commit/1273a35689bdcb3304f6634cdc3889c61f9b1b1f
src/main/java/org/junit/experimental/categories/Category.java
It seems AnnotationTypeDeclaration is not supported in the AST diff.

Commits
https://github.com/tsantalis/RefactoringMiner/commit/0c44557fdf6b60debef46bbcd29ef71c3e005f1f
https://github.com/tsantalis/RefactoringMiner/commit/14abb1ecb448c1754176ec4db907bb3a36077659
resolve the issue to some extent.

@tsantalis Thanks for the fix, Can we close the issue?


2024 Meetup Recap Edited with Link to Slides, Details and Grammar

Post for 2024 Nov. Meetup Recap changed to reflect:

PDF Slides for… presentation.
Grammer and addition detatails for the Dad and Daughter LNBITS.
Removed original post for 2024 Nov. Recap

Awesome, good catches. I also uploaded the slides to the assets folder as a pdf and linked them in the writeup.


Fix multi-stream reconnection

Codecov Report
Base: 43.35% // Head: 43.15% // Decreases project coverage by -0.21% :warning:

Coverage data is based on head (46c158a) compared to base (f0158c3).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #418      +/-   ##
==========================================
- Coverage   43.35%   43.15%   -0.21%
==========================================
  Files         119      119
  Lines       35819    35819
==========================================
- Hits        15531    15459      -72
- Misses      20288    20360      +72

Impacted Files
Coverage Δ

src/core/tcp.c
72.10% <0.00%> (-6.85%)
:arrow_down:

src/supplemental/http/http_client.c
21.73% <0.00%> (-5.22%)
:arrow_down:

src/platform/posix/posix_tcpconn.c
75.00% <0.00%> (-5.18%)
:arrow_down:

src/platform/posix/posix_resolv_gai.c
70.86% <0.00%> (-4.35%)
:arrow_down:

src/sp/transport/ws/websocket.c
75.76% <0.00%> (-3.42%)
:arrow_down:

src/supplemental/http/http_conn.c
70.14% <0.00%> (-1.98%)
:arrow_down:

src/sp/protocol/pubsub0/pub.c
90.47% <0.00%> (-1.59%)
:arrow_down:

src/sp/protocol/bus0/bus.c
94.78% <0.00%> (-1.43%)
:arrow_down:

src/core/aio.c
94.37% <0.00%> (-0.89%)
:arrow_down:

src/supplemental/websocket/websocket.c
62.04% <0.00%> (-0.85%)
:arrow_down:

... and 7 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


CSI driver should wrap all errors

/kind bug
Looking at the CSI driver code, it often returns naked fmt.Errorf() or errors.New() to gRPC as CSI response.
All errors should be wrapped into status.Error(codes.XXX, err.Error()). CSI spec explicitly enumerates what errors can be returned from each call and in what cases.

/assign


Add message types

askFoodTaken
foodTaken
askHP
HP
askFoodIntended
oodIntended
reject
leaveFood
Summary
Added all the messages in issue #40

Superceded by #96.


nuttx/syscall: export nxsem_getprioceiling and nxsem_setprioceiling v…

Summary

fix compilation errors when compiling priority protection interfaces in protected mode with pthread_mutex_setprioceiling and pthread_mutex_getprioceiling
can use the default lock even in priority protect mode

Impact
compile & ltp
Testing
ci

[Experimental Bot, please feedback here]
This PR appears to be missing some required information.
Here's a breakdown:
What's Good:

Summary: Provides a brief description of the issue and the proposed solution.
Testing: Mentions "ci", indicating Continuous Integration testing is expected.

What Needs Improvement:

Summary:

Lacks specificity about the functional code changes. Phrases like "compilation errors" and "use the default lock" are vague.
Missing related issue references (if applicable).

Impact:

Overly brief. "compile & ltp" doesn't explain the impact clearly.
Needs to address all impact points with "YES/NO" and explanations. For example:

Is new feature added?  Likely NO (since it's a fix)
Is existing feature changed? Likely YES (since a fix implies a change) - provide details.
Impact on user: Explain how the fix might affect users.
Impact on build:  If the fix affects the build process, describe how.
...and so on for all impact points.

Testing:

"ci" is not sufficient.  While CI is good, the PR should include:

Specific build host details (OS, CPU, compiler).
Specific target details (architecture, board, configuration).
Relevant testing logs from before and after the change to demonstrate the fix.

Recommendation:
Expand on the missing information to meet the NuttX PR requirements fully. Providing clear and detailed information ensures reviewers can understand the changes and their implications effectively.


[FLINK-30081][runtime] Reset jvm-overhead.min/max for local executor

What is the purpose of the change
https://issues.apache.org/jira/browse/FLINK-30081
In local executor, it's not possible to set different values for taskmanager.memory.jvm-overhead.max and taskmanager.memory.jvm-overhead.min. When setting them differently, local executor reports Exception in thread "main" java.lang.IllegalArgumentException error.
The problem was that we expect the max and min to equal, but they are not resolved to the same value for local executor. Actually the two values are not effective for local, we should reset them to the same value.
Brief change log

reset the two JVM overhead config to the same value for local executor
fix a bug in l

Verifying this change
This change is already covered by existing tests, such as TaskExecutorResourceUtilsTest. It also adds a new test case in this class.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

CC: @xintongsong for review. Thanks!


Support Frigate v0.12 UTC based recording paths

@NickM-27 Thank you. The new changes are very readable! Suggest removing the TODO, otherwise LGTM.

Thanks @NickM-27 !


MissingInternetConnectionException is appeared when it shouldn't be

Describe the bug
MissingInternetConnectionException throws when network connection is available.
SDK Version

Client: Kotlin
Version: 2.0.0-rc.0

To Reproduce
Steps to reproduce the behavior:
Error can occur during request or when just any Pairing exists
com.walletconnect.sign.core.exceptions.client.WalletConnectException$MissingInternetConnectionException: No connection available
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.checkConnectionWorking$sign_release(RelayerInteractor.kt:85)
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.publishJsonRpcRequests$sign_release(RelayerInteractor.kt:96)
        at com.walletconnect.sign.engine.domain.SignEngine$updateSession$2.invoke(SignEngine.kt:243)
        at com.walletconnect.sign.engine.domain.SignEngine$updateSession$2.invoke(SignEngine.kt:242)
        at com.walletconnect.sign.storage.sequence.SequenceStorageRepository$insertUnAckNamespaces$1$3$4.invoke(SequenceStorageRepository.kt:205)
        at com.walletconnect.sign.storage.sequence.SequenceStorageRepository$insertUnAckNamespaces$1$3$4.invoke(SequenceStorageRepository.kt:205)
        at com.squareup.sqldelight.TransacterImpl.transactionWithWrapper(Transacter.kt:260)
        at com.squareup.sqldelight.TransacterImpl.transaction(Transacter.kt:214)
        at com.squareup.sqldelight.Transacter$DefaultImpls.transaction$default(Transacter.kt:72)
        at com.walletconnect.sign.storage.sequence.SequenceStorageRepository.insertUnAckNamespaces(SequenceStorageRepository.kt:181)
        at com.walletconnect.sign.engine.domain.SignEngine.updateSession$sign_release(SignEngine.kt:242)
        at com.walletconnect.sign.client.SignProtocol.update(SignProtocol.kt:184)
        at com.walletconnect.sign.client.SignClient.update(Unknown Source:12)

Expected behavior
Error should be thrown when there's indeed no internet connection, and not when it's alive actually.
Device (please complete the following information):
The error is repeatable on any Android device

Hey @duprass! Thanks for submitting the bug report. May I ask for filling more info about device you are using?
Device (please complete the following information):

Device: [e.g. Pixel]
OS: [e.g. Android 12]
Browser [e.g. stock browser, chrome]

Also, may I ask about frequency of this error?

Hello @Elyniss!
As it was written it's reproduced on Android OS starting from 24 version regardless on device. The browsers were used on desktop as chrome, safari, brave. It seems that it doesn't depends on it too.

I spent the last hour trying to reproduce this error with no success.
What I did:
Using our sample Android wallet app and sample browser dapp, I created multiple paring and sessions with a physical Android device (Vivo V2109, Android 11) and desktop browser. After that, I called session requests from desktop Dapp, all of which I received on my phone. Later I emitted events from the Android device, and all of them were successful as well. I also left the device for a couple of minutes and retried the above tests.
@duprass May I ask for guidance on how to reproduce it?

Hello @Elyniss
I can almost shared the same stacktrace but with the call of SignClient.connet, for a really high frequency (8/10 times)
com.walletconnect.sign.core.exceptions.client.WalletConnectException$MissingInternetConnectionException: No connection available
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.checkConnectionWorking$sign_release(RelayerInteractor.kt:85)
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.subscribe$sign_release(RelayerInteractor.kt:174)
        at com.walletconnect.sign.engine.domain.SignEngine.proposePairing(SignEngine.kt:125)
        at com.walletconnect.sign.engine.domain.SignEngine.proposeSequence$sign_release(SignEngine.kt:109)
        at com.walletconnect.sign.client.SignProtocol.connect(SignProtocol.kt:110)
        at com.walletconnect.sign.client.SignClient.connect(Unknown Source:17)

Of course, SignClient.initialize is called on my Application class, and other methods are called after.
I noticed that this error seems to be random for me, on an Android Emulator & on my personal phone (Pixel 4XL).
Sometimes, I can also encountered this issues from your dApps sample:
WalletConnectViewModel: com.walletconnect.sign.core.exceptions.client.WalletConnectException$MissingInternetConnectionException: No connection available
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.checkConnectionWorking$sign_debug(RelayerInteractor.kt:85)
        at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.subscribe$sign_debug(RelayerInteractor.kt:174)
        at com.walletconnect.sign.engine.domain.SignEngine.proposePairing(SignEngine.kt:125)
        at com.walletconnect.sign.engine.domain.SignEngine.proposeSequence$sign_debug(SignEngine.kt:109)
        at com.walletconnect.sign.client.SignProtocol.connect(SignProtocol.kt:110)
        at com.walletconnect.sign.client.SignClient.connect(Unknown Source:17)
        at com.walletconnect.dapp.ui.connect.ConnectViewModel.connectToWallet(ConnectViewModel.kt:79)
        at com.walletconnect.dapp.ui.connect.ConnectViewModel.connectToWallet$default(ConnectViewModel.kt:54)
        at com.walletconnect.dapp.ui.connect.pairing_generate.PairingGenerationDialogFragment.onViewCreated(PairingGenerationDialogFragment.kt:30)

I got some timeout error too, but i can't reproduce at this time.
Feel free to ask more detail if you need.

I am also seeing this issue @Elyniss
Device: Pixel 6 Pro
OS: 12
I'm creating a Dapp app and initialize in the application class. On click of a button I am calling SignClient.connect and I receive the following crash
com.walletconnect.sign.core.exceptions.client.WalletConnectException$MissingInternetConnectionException: No connection available
         at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.checkConnectionWorking$sign_release(RelayerInteractor.kt:85)
         at com.walletconnect.sign.json_rpc.domain.RelayerInteractor.subscribe$sign_release(RelayerInteractor.kt:174)
         at com.walletconnect.sign.engine.domain.SignEngine.proposePairing(SignEngine.kt:125)
         at com.walletconnect.sign.engine.domain.SignEngine.proposeSequence$sign_release(SignEngine.kt:109)
         at com.walletconnect.sign.client.SignProtocol.connect(SignProtocol.kt:110)
         at com.walletconnect.sign.client.SignClient.connect(Unknown Source:17)
         at com.myapp.android.wallet.walletconnect.WalletConnectGenerateDeepLinkUriOperation.invoke(WalletConnectDapp.kt:54)
         at com.myapp.android.core.wallet.GeneratePairingDeepLinkUriUseCase.execute(MyFile.kt:12)
         at com.myapp.android.auth.ui.AuthScreenKt$AuthScreen$1$1$1.invokeSuspend(MyScreen.kt:55)
         at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
         at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
         at androidx.compose.ui.platform.AndroidUiDispatcher.performTrampolineDispatch(AndroidUiDispatcher.android.kt:81)
         at androidx.compose.ui.platform.AndroidUiDispatcher.access$performTrampolineDispatch(AndroidUiDispatcher.android.kt:41)
         at androidx.compose.ui.platform.AndroidUiDispatcher$dispatchCallback$1.run(AndroidUiDispatcher.android.kt:57)
         at android.os.Handler.handleCallback(Handler.java:938)
         at android.os.Handler.dispatchMessage(Handler.java:99)
         at android.os.Looper.loopOnce(Looper.java:201)
         at android.os.Looper.loop(Looper.java:288)
         at android.app.ActivityThread.main(ActivityThread.java:7870)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

Should be fixed with #305


Patch system for incremental changes

This PR is currently waiting on #221.
This PR responds to the necessity of applying incremental changes to the filesystem. It particulary concerns users with existing distros who update their launcher.
An example of this need is #213.

This PR got too bloated so I split it into #221, #223, and #225


[SPARK-40492][SS] Do maintenance before streaming StateStore unload

What changes were proposed in this pull request?
Before unload of a StateStore, perform a cleanup.

Why are the changes needed?
Current the maintenance of StateStore is performed by a periodic task in the management thread. If a streaming query become inactive before the next maintenance task fire, its StateStore will be unloaded before cleanup.
There are 2 cases when a StateStore is unloaded.

StateStoreProvider is not longer active in the system, for example, when a query ends or the spark context terminates.
There is other active StateStoreProvider in the system, for example, when a partition is reassigned.

In case 1, we should do one last maintenance before unloading the instance,

Does this PR introduce any user-facing change?
Shutdown delay of a query may increase because a maintenance task is scheduled.

How was this patch tested?
Add an integration test that verify that redundant delta file is deleted when StateStore instances is deactivated and unloaded.

@HeartSaVioR

Can one of the admins verify this patch?

I gave a feedback offline but also duplicate here for the history.
getStateStoreProvider also report active provider instance and get “inactive provider instances” which could be unloaded without maintenance.
We can defer these instances to be unloaded till next maintenance interval, but this may not be something we want, since we are effectively reverting SPARK-33827.
Technically, what we really want to do is just to ensure all state store provider instances run maintenance "at least once". That said, ideally we should not perform maintenance on unloading of provider if it has run the maintenance at least once.
In getStateStoreProvider, we should only defer some of inactive provider instances which didn't run any maintenance yet. In maintenance task, we need to let provider be unloaded without maintenance if it ran maintenance at least once.

Thanks! Merging to master.

Thanks @chaoqin-li1123 for the contribution! I merged this to master.


Write 😨 Getting further section of the wiki

This issue is now on hold due to the huge upcoming GUI refactoring


rez_pip_version metadata missing from produced package.py files

When running rez-pip2 on any package, the rez_pip_version metadata is missing from the produced package.py file.
This metadata is shown to be present in the docs but does not appear in produced package.py files.
Environment

Windows 10
Rez version 2.112.0
Rez python version 3.7
rez-pip 0.3.1

To Reproduce

Install new rez-pip
rez-pip2 semver==3.0.2 (can also try requests==2.31.0 or any other package at all)

Expected Behavior
rez_pip_version metadata present in pip attribute of package.py.
Actual Behavior
rez_pip_version is missing from pip attribute of package.py

Looks like we need to add a tiny bit of new code here.
@JeanChristopheMorinPerso mentioned we could just get the current version with importlib_metadata.version('rez-pip')

This is fixed in the latest version.


property name is always an empty string

property name is always an empty string. My E27 yeelight bulb have a name (from Yeelight app).
What is wrong?

The name is based on the result of the SSDP message.  You can debug this if you like. Look at the  updateBySSDPMessage function.


Properties tree view

Current coverage is 26.99% (diff: 2.36%)

Merging #1753 into master will decrease coverage by 0.05%

@@             master      #1753   diff @@
==========================================
  Files          1965       1965
  Lines         81185      81395   +210
  Methods       13758      13779    +21
  Messages          0          0
  Branches       1249       1249
==========================================
+ Hits          21958      21972    +14
- Misses        59150      59346   +196
  Partials         77         77

Powered by Codecov. Last update ea49b20...7342f2d


Remove Outbound data transfer from pricing

in https://docs.microsoft.com/en-us/azure/virtual-machines/linux/premium-storage#pricing-and-billing section, the outbound data transfer is mentioned in the storage pricing, which is a bit confusing, its more appropriate to have this only in the VM pricing section. as this doesn't impact the disk pricing.

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

ID: 5dec11a9-8b64-aff1-78ae-f739b5f26cf2
Version Independent ID: 163def32-3f42-df60-ea8b-e0a163a22fe2
Content: High-performance Premium Storage and Azure managed disks for Linux VMs
Content Source: articles/virtual-machines/linux/premium-storage.md
Service: virtual-machines-linux
GitHub Login: @ramankumarlive
Microsoft Alias: ramankum

@mohmdnofal Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@mohmdnofal This topic has been updated a few times since you originally filed this issue - has the issue been addressed?
I'm also going to reassign this to @roygara, who can close it if this is one of the changes he already made.
#reassign @roygara

@mohmdnofal Thanks for reaching out, apologies for the delayed response.
This has already been changed as part of our doc overhauls, so this no longer is an issue. Accordingly, I'm closing this out.
#please-close


Add a layout param to fields

Add a :
{% bootstrap_field field layout="horizontal" %}

support for bootstrap_field or make use of
BOOTSTRAP3['horizontal_label_class']
BOOSTRAP3['horizontal_label_class']

for fields.

Do you mean for forms? I think the bootstrap horizontal class applies to the form as a whole.

Fixed with renderers a while ago. Sorry for the late reply.


Failed to initialize wallet

Steps to reproduce

Go to connect app and login
go to wallets and try to initialize a wallet

I don't know if this happens because I have a wallet with the same name or not, but either way, we need to show more info in the error message.

@zaelgohary  Sometimes, reinstalling the wallet app can resolve initialization issues.If your app has an option to clear cache or reset settings, try that.

verified no longer reproducable
could intialize my wallet easily

@khaledyoussef24
where is the test case link ?


Make Conversion Class Diagram

For the conversion micro service, we must model the class diagram

It has been made by Georgiana, uploaded on drive, review on the 29th


Ladle breaking TypeScript when moduleResolution: "NodeNext"

Describe the bug
Ladle breaks Typescript type-checking (e.g. tsc --noEmit) when Typescript has the config moduleResolution: "NodeNext", even when skipLibCheck: true
Reproduction
https://stackblitz.com/edit/ladle-zq9ane?file=package.json
and run
npm run typecheck

The specific error that causes issues looks like the following, and note that it's looking in node_modules:
node_modules/@ladle/react/lib/app/exports.ts:2:33 - error TS2835: Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is 'node16' or 'nodenext'. Did you mean './src/context.js'?

2 import { useLadleContext } from "./src/context";

Environment

OS: MacOS
Browser: n/a
Version: n/a

More Context
From this TS issue (that apparently is "working as intended" for now), it seems that the error comes from the fact that Ladle's package.json#types field points to a .ts file instead of a .d.ts file.

Yes, I have the same problem. I just don't typecheck (yet) in my docs project.
Good that in our monorepo Ladle-dependent code lives only in separate docs projects (for component libraries), so its not a big issue.
I think a d.ts. File in the exports won't work because there are no .d.ts Files. This works because the files in Ladles lib directory are supposed to be processed by Vite/Esbuild all the time.
I am not sure how this problem can be solved. I experimented a bit by putting a local tsconfig.json in the ladle folder in node_modules and set  "moduleResolution": "node" there, but that didn't work.

Yeah, Ladle needs to generate .d.ts files for when it's published to npm, I don't think there's any way around that.
Fortunately it maybe isn't too hard to fix: add a tsc --emitDeclarationOnly before packaging up the library, and update the package.json to point to the .d.ts file that's generated. Maybe. 🙂

@frehner : I think this will not be enough. Typescript never touches the imports, the Node module resolution would still require the .js extension for relative imports. Pointing package.json to the .d.ts would also not help this.

Maybe an easy solution would be to append .js to all imports in the Ladle sources. This could be backwards compatible to the "legacy" Node resolution. Node16/NodeNext resolution could also maybe set in tsconfig.json to make sure all imports are correct.

@frehner : I think this will not be enough. Typescript never touches the imports, the Node16/NodeNext module resolution would still require the .js extension for relative imports. Pointing package.json to the .d.ts would also not help this.

I'm only talking about Ladle creating .d.ts files next to the .ts files in its own library, right before publishing to npm. It should work with that change I believe.

I'm only talking about Ladle creating .d.ts files next to the .ts files in its own library, right before publishing to npm. It should work with that change I believe.

Can you test this out? That seems like a simple fix if it works.

@tajo I have it working - but ONLY for external packages (tested using linking).
However, because the types are only generated right before creating the npm package and aren't kept in source control, that means that other packages in the ladle monorepo can't find the types and fail the typecheck step.
So I think you have a couple of options here:

Generated the .d.ts and keep them as part of the package / VCS / git history, so that they're always there
Change the library so that you compile the TS to .js and .d.ts (most libraries do things this way)
Other ideas?

Would it be helpful if I put up my changes so you could see them, even if it's not fully working yet?

Generate the .d.ts and keep them as part of the package / VCS / git history, so that they're always there

This is fine with me since we don't change the exported API that often anyway. As long as we have a CI test for it to make sure it's in sync.

Change the library so that you compile the TS to .js and .d.ts (most libraries do things this way)

This would mean flipping all the code (including node/CLI) into .ts? I really prefer the setup where the node code doesn't need an extra compilation step and types are defined through JSDoc.

This would mean flipping all the code (including node/CLI) into .ts?

No, not necessarily. They could remain as-is, if you wanted to go this route. You would only have to process the .ts files.
Actually, now that I think about it more, we don't necessarily have to put them into git / VCS:
Option 3, we could have the .d.ts files output to a folder that's ignored by .gitignore, and then would need to add an additional step (to contributing.md) when you spin up the project to generate the types files. Or maybe even run the type generation in a "postinstall" npm hook (for ladle monorepo support) and in a "prepack" npm hook (so they're included in the npm package/bundle)?


Wrong function return type inference (union type parameter)

TypeScript Version:  3.8.0-dev.20191114

Search Terms: Wrong union type parameter function result type inference
Code
interface ITestRequired {
    key: string
    ignoredKey: string
}

interface ITestOptional {
    key?: string
    ignoredKey?: string
}

export const unwrapTestObject = ({ key }: ITestRequired | ITestOptional) => ({ key })

// testObj is of ITestRequired type
const testObj: ITestRequired = {
    key: 'test',
    ignoredKey: 'test'
}

const testFilter = unwrapTestObject(testObj)

// testFilter.key should always be a string here, but instead we get
// testFilter.key is possibly 'undefined'.
console.log(testFilter.key.substring(0, 2))

Expected behavior:
Output type should be inferred from input type even when using Union types (because it is specified in the parameter type).
Actual behavior:
Parameter type is totally ignored.
Playground Link
Related Issues:
Did not find anything similar.

Are you looking for generic functions?

@AnyhowStep like so ?
export const unwrapTestObject = <T>({ key }: T) => ({ key })

indeed it seems to do the job, but I'm getting Property 'key' does not exist on type 'unknown'. as I'm trying to destructure the parameter (seems like TS generics and destructuring are not friends from what I could find in the issues).
Playground Link

More like
const unwrapTestObject = <T extends ITestOptional>({ key }: T): Pick<T, "key"> => ({ key })

The compiler is working as intended (the compiler doesn't distribute control flow analysis over union types); you might consider closing this issue.  Good luck!

That's a bit complicated but thanks it's working !
I was simply hoping for something more "generic" ^^
Sorry I opened a bug report for this.


Uploading an image using a multipart request with OAuth2 access token

I'm having trouble uploading an image using a multipart/form-data request. Traceback is below, I'm using oauthlib 0.6.1
Traceback (most recent call last):
  File "*******oauth_validators.py", line 30, in validate
    server.verify_request(uri, method, body, headers, scopes)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/oauth2/rfc6749/endpoints/base.py", line 61, in wrapper
    return f(endpoint, uri, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/oauth2/rfc6749/endpoints/resource.py", line 62, in verify_request
    request = Request(uri, http_method, body, headers)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/common.py", line 359, in __init__
    self.body = encode(body)
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/common.py", line 354, in <lambda>
    encode = lambda x: to_unicode(x, encoding) if encoding else x
  File "/usr/local/lib/python2.7/dist-packages/oauthlib/common.py", line 288, in to_unicode
    return unicode_type(data, encoding=encoding)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 613: invalid start byte

It seems that as part of request verification, oauthlib expects the body byte string to be encoded in utf-8. Since the image's raw bytes are present in the multipart/form-data body, converting the body to unicode raises the UnicodeDecodeError.
I may be understanding this incorrectly, but is there no way to upload the image as raw bytes instead of base64 encoding the image?

https://github.com/idan/oauthlib/blob/master/oauthlib/oauth2/rfc6749/tokens.py#L196 is probably the culprit. The file uses unicode_literals, but headers should be bytes, not unicode.
In my case (with Flask-OAuthlib) I simply subclassed OAuthRemoteApp and fixed it in http_request:
    @staticmethod
    def http_request(uri, headers=None, data=None, method=None):
        # WTF. the oauth2 lib adds the token header as unicode, which
        # breaks if the body is bytes (e.g. binary image data)
        if headers:
            headers = {k.encode('utf-8'): v.encode('utf-8') for k, v in headers.iteritems()}
        return super(FixedOAuthRemoteApp, FixedOAuthRemoteApp).http_request(uri, headers, data, method)

If you use oauthlib directly you'll probably need to add similar code somewhere else

This problem is still happening in the latest version (2.0.6).
What would be the ideal solution? Not try to convert the body to unicode at all (but I imagine that this could break the backwards compatibility)?
cc @ib-lundgren (sorry, not sure who is the best one to answer this).

Hi everyone,
Would it be possible to add more details on how to reproduce it ? Doing a small testcase would be ideal, else, even pseudo code would be great.
Also, while @ThiefMaster mentionned Flask-OAuthlib, we don't know about the others. Is it with requests-oauthlib, with OAuth1.0 server, with OAuth2.0, .. Any details are welcomed.

The code below should reproduce the bug using web.py and Python 2.7.  Once the server and client code are run, the stacktrace should be printed to stdout on the console where the server is running.
Server

import web # pip install web.py==0.38
from oauthlib.oauth2 import WebApplicationServer, RequestValidator

class DummyValidator(RequestValidator):
    def validate_bearer_token(self, *args, **kwargs):
        return True

SERVER = WebApplicationServer(DummyValidator())

class View(object):
    def GET(self):

        uri, http_method, body, headers = (
            web.ctx.fullpath, web.ctx.method, web.data(), web.ctx.headers
        )
        scopes = []

        valid, request = SERVER.verify_request(
            uri, http_method, body, headers, scopes
        )

        return 'success'

    def POST(self):
        return self.GET()

if __name__ == "__main__":
    web.application(('/', View)).run()

Client
import requests

blank_gif_data = (
    'GIF89a\x01\x00\x01\x00\x80\x00\x00\xff\xff\xff\xff\xff\xff!\xf9'
    '\x04\x01\n\x00\x01\x00,\x00\x00\x00\x00\x01\x00\x01\x00\x00\x02'
    '\x02L\x01\x00;'
)

r = requests.post('http://localhost:8080/', files=dict(image=('blank.gif', blank_gif_data)))
r.raise_for_status()

print r
print r.content

Thanks for your test case !
We can cleary see a gap in the implementation and the RFC. We should read the access_token in the body only if :

(...)
o  The HTTP request entity-header includes the "Content-Type" header
field set to "application/x-www-form-urlencoded".
(...)

See section 2.2.  Form-Encoded Body Parameter for all the details: https://tools.ietf.org/html/rfc6750#section-2.2
That's cleary a bug and it needs to be fixed.


Pull Restaurant place and ID & Store

[x] Pull the API values from the Review page and feed into Firebase as file structure

Pulled from res-details.js and used in chat.js


Don't "flatten" nested if expressions when formatting

Summary
Closes #6939
Test Plan
cargo test

This PR regresses formatting of
# Reduce Model instances to their primary key values
row_data = tuple(
    d._get_pk_val()
    if hasattr(d, "_get_pk_val")
    # Prevent "unhashable type: list" errors later on.
    else tuple(d)
    if isinstance(d, list)
    else d
    for d in row_data
)
if row_data and None not in row_data:
    pass

Black collapses the second else as it seems because of the comment.
# Reduce Model instances to their primary key values
row_data = tuple(
    d._get_pk_val() if hasattr(d, "_get_pk_val")
    # Prevent "unhashable type: list" errors later on.
    else tuple(d) if isinstance(d, list) else d
    for d in row_data
)
if row_data and None not in row_data:
    pass

without the comment
# Reduce Model instances to their primary key values
row_data = tuple(
    d._get_pk_val()
    if hasattr(d, "_get_pk_val")
    else tuple(d)
    if isinstance(d, list)
    else d
    for d in row_data
)
if row_data and None not in row_data:
    pass

I prefer our formatting because there's a smaller difference between with/without comment.

Thank you!


the launcher failed to connect to Shadow

when im trying to run shadow and click on "Start now", i get the error "the launcher failed to connect to shadow (code: L:100)" ..
i am using Ubuntu 19.04 with KDE Plasma 5 and Nvidia MX 150 graphic card.
i googled a lot but didnt find anything matching this issue.
any ideas? :/

Hello mate !
We will need more information about your setup. Can you print here the vainfo result please ? (sudo apt install vainfo)

output is:
libva info: VA-API version 1.4.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nvidia_drv_video.so
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

any ideas? :thinking:

NVIDIA MX 150 cards may not be supported by the VA-API. You will have to tweak to have a nice vainfo.
A tutorial is available over here. If you succeed to make it work, please give your feedback over here :) You may find some help from the Discord community aswell.

Did you succeed to run it?

I close this very old issue. You can reopen it if you want.

no, i didnt succeed but doesn't matter now. :)


Browser sample broke

http://hydrabolt.github.io/discord.js/browser.html
When I tried to log in, it seems like it errored out.
Uncaught TypeError: Cannot read property 'evalPerms' of null

You do see the spot where it said "Experimental?" As far as I know, that's not even using a recent version of Discord.JS. It's not a proper implementation of D.JS, you should follow the docs to install your own instance.

@khionu webdists should be built for latest (6.0.0), though don't think they've been tested.

WebDists? Yeah. But specifically that instance?

Not prevalent to the Library as far as development.

Still a legit issue with the demo

Works fine for me?

Might have been fixed and the issue simply not updated. I'll ping the team.

Fixed in https://github.com/hydrabolt/discord.js/commit/8021bbdb5ecba3c6868e1597a090bcc7a03119cd


WIP

Closing for now. There's a lot of migration and update work to be done. Might not be worth it in the short term.


Inconsistent handling of inheritance

Input
→ View on sorbet.run (partial)
See a full example in https://github.com/DavidS/sorbet-playground
# this is valid
class ExampleError < RuntimeError
  attr_accessor :original
  def initialize(message, original=nil)
    super(message.scrub)
    @original = original
  end
end
ExampleError.new("message").message

# this is - except for the require - structurally the same and is flagged as erroneous
require 'puppet/error'
Puppet::Error.new("message").message

Observed output
david@zion:~/git/sorbet-playground$ bundle exec srb tc
lib/example.rb:7: Method message does not exist on Puppet::Error https://srb.help/7003
     7 |Puppet::Error.new("message").message
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Errors: 1
david@zion:~/git/sorbet-playground$

Expected behavior
Both ExampleError and Puppet::Error inherit the message method from RuntimeError. It is inconsistent that one works and the other doesn't.
Looking at the generated rbi file, I think the underlying issue is that rbi does not capture inheritance info:
Compare https://github.com/puppetlabs/puppet/blob/master/lib/puppet/error.rb#L1-L3
module Puppet
  # The base class for all Puppet errors. It can wrap another exception
  class Error < RuntimeError

with
https://github.com/DavidS/sorbet-playground/blob/17f3241a0cbe04ae5479345157b0aebb0be553d8/sorbet/rbi/hidden-definitions/hidden.rbi#L12841-L12850
class Puppet::Error
  def initialize(message, original=T.unsafe(nil)); end

  def original(); end

  def original=(original); end
end

class Puppet::Error
end

Browsing through other definitions, I can see other instances where inherited methods are not shown on child classes.

Do you think Puppet::Error should have some inheritance? Can you try
puts Puppet::Error.ancestors

and see what the runtime things is the hierarchy?

Yes:
david@davids:~/git/puppet$ bundle exec pry
[1] pry(main)> require 'puppet/error'
=> true
[2] pry(main)> puts Puppet::Error.ancestors
Puppet::Error
RuntimeError
StandardError
Exception
Object
JSON::Ext::Generator::GeneratorMethods::Object
PP::ObjectMixin
Kernel
BasicObject
=> nil
[3] pry(main)>

See also the original source at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/error.rb#L1-L3 (it's OSS)

I tried to repro this. I made a Gemfile with this contents:
$ cat Gemfile
source 'https://rubygems.org'
gem 'puppet'

and then ran srb init. And I only have:
$ grep -R 'class Puppet::Error' .
./sorbet/rbi/gems/puppet.rbi:class Puppet::Error < RuntimeError
./sorbet/rbi/gems/puppet.rbi:class Puppet::ErrorWithData < Puppet::Error

I'm not sure how you're getting the missing methods having those definitions and how you're getting them to not have the ancestry? We do model ancestry in that file. Maybe you're monkeypatching something?

For some reason in my case the definitions end up in rbi/hidden-definitions instead of rbi/gems:
[...]
Would you like to continue? [Y/n]
Generating: sorbet/config
Generating: sorbet/rbi/sorbet-typed/
Generating: sorbet/rbi/gems/
Generating: sorbet/rbi/hidden-definitions/
Requiring all of your code
Naming all Modules
Generating /tmp/d20190624-25117-c5bxv1/reflection.rbi with 2320 modules and 86 aliases
Printing your code's symbol table into /tmp/d20190624-25117-c5bxv1/from-source.json
Printing /tmp/d20190624-25117-c5bxv1/reflection.rbi's symbol table into /tmp/d20190624-25117-c5bxv1/reflection.json
Reading /tmp/d20190624-25117-c5bxv1/from-source.json
Reading /tmp/d20190624-25117-c5bxv1/reflection.json
Building rbi id to symbol map
Building source id to symbol map
Writing /tmp/d20190624-25117-c5bxv1/hidden.rbi.tmp
/home/david/tmp/vendor/ruby/2.5.0/gems/sorbet-0.4.4296/lib/hidden-definition-finder.rb:215: warning: constant ::Data is deprecated
/home/david/tmp/vendor/ruby/2.5.0/gems/sorbet-0.4.4296/lib/hidden-definition-finder.rb:215: warning: constant ::Data is deprecated
Generating split RBIs into sorbet/rbi/hidden-definitions/
Generating: sorbet/rbi/todo.rbi

Done!

This project is now set up for use with Sorbet. The sorbet/ folder should exist
and look something like this:

[...]

Please don't hesitate to give us your feedback!

david@davids:~/tmp/sorbet-playground$ grep -R 'class Puppet::Error' .
./sorbet/rbi/hidden-definitions/hidden.rbi:class Puppet::Error
./sorbet/rbi/hidden-definitions/hidden.rbi:class Puppet::Error
./sorbet/rbi/hidden-definitions/hidden.rbi:class Puppet::ErrorWithData
./sorbet/rbi/hidden-definitions/hidden.rbi:class Puppet::ErrorWithData
david@davids:~/tmp/sorbet-playground$

I played around with it a little bit more and even with other gems (rake, bundler, rspec, a1409yo_health) and with a system-wide gem install of srb, I was unable to get srb init to produce a sorbet/rbi/gems directory:
david@davids:~/tmp/new$ find sorbet/
sorbet/
sorbet/rbi
sorbet/rbi/hidden-definitions
sorbet/rbi/hidden-definitions/errors.txt
sorbet/rbi/hidden-definitions/hidden.rbi
sorbet/rbi/todo.rbi
sorbet/rbi/sorbet-typed
sorbet/rbi/sorbet-typed/lib
sorbet/rbi/sorbet-typed/lib/bundler
sorbet/rbi/sorbet-typed/lib/bundler/all
sorbet/rbi/sorbet-typed/lib/bundler/all/bundler.rbi
sorbet/rbi/sorbet-typed/lib/ruby
sorbet/rbi/sorbet-typed/lib/ruby/all
sorbet/rbi/sorbet-typed/lib/ruby/all/open3.rbi
sorbet/rbi/sorbet-typed/lib/ruby/all/resolv.rbi
sorbet/config
david@davids:~/tmp/new$

@DavidS, did you ever get this resolved? I also have no sorbet/rbi/gems directory being generated.

I can't reproduce this and this issue is 6+ months stale. Closing for the time being.


Update authors in CITATION.bib in preparation for 0.2 release

And here's the output of the "preview" workflow:


Service always changes enable from False to True

For every puppet run the Service/enable is getting changed:
Notice: /Stage[main]/Redis/Redis::Instance[redis-default]/Service[redis-6900]/enable: enable changed 'false' to 'true'
I am running the manifest on a Debian Wheezy using puppet 3.2.2
how can I fix this?

Archiving this repo and closing all open issues and pull requests. Please fork and maintain any changes in another repo. Sorry for the inconvenience.


Unclear re cost vs consumption

Doc states: "In the Azure portal, budgets are defined by cost. Using the Azure Consumption API, budgets are defined by cost or by consumption usage."
This needs further explanation. What is cost vs consumption? Need to give examples of what would count as cost but not consumption, and vice-versa. And what would count as both.

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

ID: 97484428-195e-80cc-f484-1cc2e7aee855
Version Independent ID: b5711fa9-cec5-d930-ed72-039ef01b36a2
Content: Monitor usage and spending with cost alerts
Content Source: articles/cost-management/cost-mgt-alerts-monitor-usage-spending.md
Service: cost-management
GitHub Login: @bandersmsft
Microsoft Alias: banders

Thanks for your comment. The feedback has been shared with the content owner for further review. Thanks for your patience.

@jtuliani Usage-based budgets are created using an older version of the Budgets API and are not commonly used. I'll update the article to provide more context.
#please-close