Microsoft Security Advisory CVE-2018-8409: ASP.NET Core Denial Of Service Vulnerability

Microsoft Security Advisory CVE-2018-8409: ASP.NET Core Denial Of Service Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
Microsoft is aware of a denial of service vulnerability when ASP.NET Core improperly handles web requests. An attacker who successfully exploited this vulnerability could cause a denial of service against an ASP.NET Core web application. The vulnerability can be exploited remotely, without authentication. A remote unauthenticated attacker could exploit this vulnerability by providing a specially crafted web requests to the ASP.NET Core application.
The update addresses the vulnerability by correcting how ASP.NET Core handles parsing web requests.
The underlying problem exists in the System.IO.Pipelines package. If you have other software which uses this package please follow the instructions in the .NET Core bulletin.
Original Announcement
The original announcement for this issue can be found at https://github.com/aspnet/Announcements/issues/316
Mitigation factors
There are no mitigating factors for this vulnerability.
Affected software
Any ASP.NET Core based application that uses either of the packages with a vulnerable version listed below.

Package name
Vulnerable versions
Secure versions

Microsoft.AspNetCore.All
2.1.0, 2.1.1, 2.1.2, 2.1.3
2.1.4

Microsoft.AspNetCore.App
2.1.0, 2.1.1, 2.1.2, 2.1.3
2.1.4

System.IO.Pipelines
4.5.0
4.5.1

Advisory FAQ
How do I know if I am affected?
Applications which use Microsoft.AspNetCore.App or Microsoft.AspNetCore.All
ASP.NET Core 2.1 is distributed as part of the .NET Core runtime. To check the current installed runtimes open a command prompt and run the dotnet --info command. If you have a 2.1 or greater runtime installed you will see output like the following;
.NET Core SDK (reflecting any global.json):
 Version:   2.1.401
 Commit:    91b1c13032

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.401\

Host (useful for support):
  Version: 2.1.3
  Commit:  124038c13e

.NET Core SDKs installed:
  2.1.4 [C:\Program Files\dotnet\sdk]
  2.1.401 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

If the highest .NET Core SDK version is less that 2.1.402 or the highest Microsoft.AspNetCore.App runtime version is less that 2.1.4 you are vulnerable to this issue. You may not see any SDK versions if you have only installed the runtime.
To update ASP.NET Core 2.1 you should download and install the .NET Core SDK 2.1.402 on your development machines and build servers, and the .NET Core Runtime 2.1.4 on your deployment servers. Your application will roll forward to these versions on an application restart.
Applications not using Microsoft.AspNetCore.App or Microsoft.AspNetCore.All
System.IO.Pipelines is distributed both in ASP.NET Core 2.1 and separately as a NuGet package. If you are not using Microsoft.AspNetCore.App or .All, you may still be affected if you are referencing the System.IO.Pipelines package.
Direct dependencies
Direct dependencies are discoverable by examining your csproj file. They can be fixed by editing the project file or using NuGet to update the dependency.
Transitive dependencies
Transitive dependencies occur when you add a package to your project that in turn relies on another package. For example, if Contoso publishes a package Contoso.Utility which, in turn, depends on Contoso.Internals and you add the Contoso.Utility package to your project now your project has a direct dependency on Contoso.Utility and, because Contoso.Utility depends 'Contoso.Internals', your application gains a transitive dependency on the Contoso.Internals package.
Transitive dependencies are reviewable in two ways:

In the Visual Studio Solution Explorer window, which supports searching.
By examining the project.assets.json file contained in the obj directory of your project for csproj based projects

The project.assets.json files are the authoritative list of all packages used by your project, containing both direct and transitive dependencies.
There are two ways to view transitive dependencies. You can either use Visual Studio’s Solution Explorer, or you can review the project.assets.json file).
Using Visual Studio Solution Explorer
To use Solution Explorer, open the project in Visual Studio, and then press Ctrl+; to activate the search in Solution Explorer. Search for the vulnerable package and make a note of the version numbers of any results you find.
For example, searching for Microsoft.AspNetCore.Mvc.Core in an example project that contains a package that takes a dependency on Microsoft.AspNetCore.Mvc shows the following results in Visual Studio 2017:

The search results appear as a tree. In the previous results, you can see that a reference to Microsoft.AspNetCore.Mvc.Core version 1.1.2 is discovered.
Under the Dependencies node is a NuGet node. Under the NuGet node is the list of packages you have directly taken a dependency on and their versions.
In screenshot, the application takes a direct dependency on Microsoft.AspNetCore.Mvc. Microsoft.AspNetCore.Mvc in turn has leaf nodes that list its dependencies and their versions.
The Microsoft.AspNetCore.Mvc package takes a dependency on a version of Microsoft.AspNetCore.Mvc.ApiExplorer, that in turn takes a dependency on a version of Microsoft.AspNetCore.Mvc.Core.
 Manually reviewing project.assets.json
Open the project.assets.json file from your project’s obj directory in your editor. We suggest you use an editor that understands JSON and allows you to collapse and expand nodes to review this file.
Visual Studio and Visual Studio Code provide JSON friendly editing.
Search the project.assets.json file for the vulnerable package, using the format packagename/ for each of the package names from the preceding table. If you find the assembly name in your search:

Examine the line on which they are found, the version number is after the /.
Compare to the vulnerable versions table.

For example, a search result that shows System.IO.Pipelines/4.5.0 is a reference to version 4.5.0 of System.IO.Pipelines.
If your project.assets.json file includes references to the vulnerable package, then you need to fix the transitive dependencies.
If you have not found any reference to any vulnerable packages, this means either

None of your direct dependencies depend on any vulnerable packages, or
You have already fixed the problem by updating the direct dependencies.

How do I fix the issue?
Fixing direct dependencies
Open projectname.csproj in your editor. If you're using Visual Studio, right-click the project and choose Edit projectname.csproj from the context menu, where projectname is the name of your project. Look for PackageReference elements. The following shows an example project file:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="System.IO.Pipelines" Version="4.5.0" />
  </ItemGroup>
</Project>

The preceding example has a reference to the vulnerable package, as seen by the single PackageReference element. The name of the package is in the Include attribute.
The package version number is in the Version attribute. The previous example shows a single direct dependency on System.IO.Pipelines version 4.5.0
To update the version to the secure package, change the version number to the updated package version as listed on the table previously.
In this example, update System.IO.Pipelines to the appropriate fixed package number for your major version. Save the csproj file. The example csproj now looks as follows:
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.1</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="System.IO.Pipelines" Version="4.5.1" />
  </ItemGroup>
</Project>

If you're using Visual Studio and you save your updated csproj file, Visual Studio will restore the new package version.
You can see the restore results by opening the Output window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you're not using Visual Studio, open a command line and change to your project directory. Execute the dotnet restore command to restore the updated dependencies.
Now recompile your application. If after recompilation you see a Dependency conflict warning, you must update your other direct dependencies to versions that take a dependency on the updated package.
Fixing transitive dependencies
If your transitive dependency review found references to the vulnerable package, you must add a direct dependency to the updated package to your csproj file to override the transitive dependency.
Open projectname.csproj in your editor. If you're using Visual Studio, right-click the project and choose Edit projectname.csproj from the context menu, where projectname is the name of your project.
Look for PackageReference nodes, for example:
<Project Sdk="Microsoft.NET.Sdk.">
  <PropertyGroup>
    <TargetFramework>net461</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="ThirdParty.NotUpdatedYet" Version="2.0.0" />
  </ItemGroup>
</Project>

You must add a direct dependency to the updated version of the vulnerable package by adding it to the csproj file.
You do this by adding a new line to the dependencies section, referencing the fixed version.
For example, if your search showed a transitive reference to a vulnerable System.ServiceModel.Http version, you'd add a reference to the fixed package number.
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>net461</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="System.IO.Pipelines" Version="4.5.1" />
    <PackageReference Include="ThirdParty.NotUpdatedYet" Version="2.0.0" />
  </ItemGroup>
</Project>

After you've added the direct dependency reference, save your csproj file.
If you're using Visual Studio, save your updated csproj file and Visual Studio will restore the new package versions.
You can see the restore results by opening the Output window (Ctrl+Alt+O) and changing the Show output from drop-down list to Package Manager.
If you're not using Visual Studio, open a command line and change to your project directory. Execute the dotnet restore command to restore the new dependencies.
Rebuilding your application
Finally you must rebuild your application, test, and redeploy.
Other Information
Reporting Security Issues
If you have found a potential security issue in .NET Core, please email details to<EMAIL_ADDRESS>Reports may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue on GitHub in the .NET Core or ASP.NET Core organizations. These are located at https://github.com/dotnet/ and https://github.com/aspnet/. The Announcements repo for each product (https://github.com/dotnet/Announcements and https://github.com/aspnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the discussion issue.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
CVE-2018-8409
Revisions
V1.0 (September 11, 2018): Advisory published.
Version 1.0
Last Updated 2018-09-11

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Fix memory usage on Celery worker

What is needed?
Fix memory usage on Celery worker
Background

Celery worker is steadily increasing the used RAM until it's restarted
It makes us think it's a memory leak: https://github.com/celery/celery/issues/4843

Solution
Setting worker reboot after a number of tasks or after ram is used:

https://docs.celeryproject.org/en/stable/userguide/configuration.html#std-setting-worker_max_tasks_per_child
https://docs.celeryproject.org/en/stable/userguide/configuration.html#worker-max-memory-per-child

It's currently not supported for gevent, only prefork: https://docs.celeryproject.org/en/stable/userguide/workers.html#max-tasks-per-child-setting

Maybe max_memory_per_child works, there's no warning or error when running Celery with that flag


Firefox's delete score must be HARD or IMPOSSIBLE

Backstory

https://github.com/mozilla/fxa/issues/12372
https://support.mozilla.org/en-US/questions/1372988

The old user who changed their email address at least once cannot delete their account at all. Also confirmed this on my account as well.
Data

name:
url:
url_CODE:
difficulty:

notes:
email:
email_subject:
email_body:
domains:

I can't replicate. Firefox allowed me to delete my account regardless of whether I've changed my email or not.


test(ticdc): Accelerating the generation of goveralls coverage report

What problem does this PR solve?

Issue Number: close #4302
What is changed and how it works?
Add -parallel param to goveralls to accelerate the generation of coverage report.
Check List
Tests

Unit test
Integration test

Release note
None

/merge

/merge

/run-verify

/run-dm-integration-test

@zhaoxinyu Do we need cherry pick this PR?


Fix links that reference other quickstart steps

Contributions

[X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates
In the quickstart guides, the links that reference other steps within the same quickstart don't work. Example:
https://docs.getdbt.com/quickstarts/databricks?step=5

I noticed this for most of the quickstart pages so all pages should be checked.
What part(s) of the page would you like to see updated?
https://docs.getdbt.com/quickstarts
example: https://docs.getdbt.com/quickstarts/databricks?step=5
Additional information
No response

Thank for opening this, Mirna.  I marked this medium priority.  The links aren't working so this could be confusing though not too hard to figure out.

Fixed


Under which license terms is this program published?

Hello @johanhaleby ,
I'd like to use your script in my codebase, under which terms are you publishing your modifications? (I'm already asking @lavoiesl about the original license, see https://github.com/lavoiesl/bash-templater/issues/2)
Cheers!

Good question, and I'm embarrassed to say that I don't know. I presume that'll go with the same license as @lavoisel.

Awesome, let's see what @lavoiesl says, thanks for the quick answer! : )

Just made it MIT, thanks.

Added the same license file in my repo.

Thank you too @johanhaleby !

Hi both,
Me and @Stegoo added a header to the script that we copied. Considering that it is not packaged, copying is probably the way most people would use templater.sh, and I think it might be worth adding a similar header at the source. (It could make easier for anyone to comply with the terms of the MIT license.)
For what it's worth, here's our header, that you can re-use if you wish : )
#!/bin/bash
#
# Very simple templating system that replaces {{VAR}} by the value of $VAR.
# Supports default values by writting {{VAR=value}} in the template.
#
# Copyright (c) 2017 Sébastien Lavoie
# Copyright (c) 2017 Johan Haleby
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all
# copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
# OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# See: https://github.com/johanhaleby/bash-templater
# Version: https://github.com/johanhaleby/bash-templater/commit/5ac655d554238ac70b08ee4361d699ea9954c941

readonly PROGNAME=$(basename $0)

config_file="<none>"
print_only="false"
silent="false"

# [..]

Thanks, I'll add it here as well!


View all templates button opens a new tab

When I click the button to 'View all templates' the action takes me back as expected but it does so by opening a new tab. This is only happening on dmptool prod. Correct behavior is to remain in the same tab.

this is working as expected now. closing.


"Defined in" Should not exist on module pages

In the ember api docs, Defined in does not show up.
It does show up for modules this theme, but (at least in our case) with an erroneous link to the first class (not to the actual module definition)
Shall I include this fix in a PR?

@dangreenisrael I've noticed that before. I dont believe this to be a bug with this theme but an issue with yuidoc. As showing the defined in on a module is considered "standard", I think we should add an option (hideModuleDefinedIn) instead of just removing it altogether.

That makes sense,
I was thinking about adding options for:

hideModuleDefinedIn
hideTagLinkInSidebar

Thoughts?

@dangreenisrael those 2 work for me 😄


RATIS-1760. Bump Netty to 4.1.86.Final to fix CVE-2022-41881

See https://issues.apache.org/jira/browse/RATIS-1760

@MarcusWalzCollibra , could you comment on https://issues.apache.org/jira/browse/RATIS-1760 so I can assign it to you?
BTW, please file a JIRA when submitting a pull request.

@MarcusWalzCollibra , could you post a comment on https://issues.apache.org/jira/browse/RATIS-1760 so that we can assign it to with your JIRA account?


Update sql-database-get-started-sql-data-sync.md

Clearing up confusion when the tutorial starts by saying it is using the "Preview" portal but actually is using the older Management portal. Back when SQL Azure Data Sync was first available the HTML 5 based management portal was the Preview portal, but now it's the old portal and Ibiza is the preview portal.

Hi @mikewo, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, AZPRBOT;

@spelluru
FYI

Thanks!


Added Gravit and Photopea

Added Gravit and Photopea to UI Design Tools

@webchun many thanks for adding Gravit & Photopea. Both of them looks very interesting (and free 😃)

Np at all Lisa. Glad you like it 😊


More improvements to trait resolution

This fixes a few more things about trait resolution. In particular, I added a step that removes all regions so we can finally use normal equality between predicates instead of comparing strings.

Charon breakage is because this fixes come bugs which is great


More info needed on web socket communication

the documentation says "if you can't connect to a notebook, ensure that web socket communication is not disabled", with no info on where or how to ensure that web socket communication is not disabled.

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

ID: 25d37573-7e5e-f808-2dce-9f5efc25c3bf
Version Independent ID: 08bd729f-fd87-ae90-4ae4-f6f47bc5a2f2
Content: Run Jupyter notebooks in your workspace - Azure Machine Learning
Content Source: articles/machine-learning/how-to-run-jupyter-notebooks.md
Service: machine-learning
Sub-service: core
GitHub Login: @AbeOmor
Microsoft Alias: osomorog

@nickrags Thanks for the feedback! We are currently investigating and will update you shortly.

@AbeOmor Hello, could you please check on this issue and update the document if needed? Thanks.

Added the link to this doc: https://docs.microsoft.com/en-us/azure/machine-learning/how-to-access-azureml-behind-firewall?tabs=ipaddress#microsoft-hosts.. It will show users how to ensure the right hosts are not blocked

#please-close


[BUG] "Fatal: index-pack failed' during Repository Clone

Environment

Camera:  ZWO  or  RPi - include the model  RPi HQ camera
OS: Buster or Bullseye   Bullseye
Allsky version:  v2023.05.01_04
Pi model and amount of memory (512 MB, 1, 2, 4, or 8 GB)  PI 4 4GB

Bug Description
During the install process on my Raspberry Pi 4 I was cloning into Allsky.
It moseyed along for a while and then I received the error that is attached in the screenshot.
Please advise my next steps.

Log / configuration files
No log files as I didn't get past the GIT Clone process

@rdwhynot,  Since this happened before Allsky was installed, it's not an Allsky issue.  Sometimes GitHub hiccups or your network went down.  Please remove the "allsky" directory and try the git clone again.
Yesterday I had to try "git clone" several times on one of my test machines and had to reboot it to get it to work.  I assume the Pi was in a funky state.

You can close this issue.   I figured out the issue, my network connection
wasn't good.   I rebooted and changed the cable and the Git Clone worked
fine.
Thanks, and Happy New Year
On Sat, Dec 30, 2023 at 4:32 PM Eric Claeys @.***>
wrote:

@rdwhynot https://github.com/rdwhynot, Since this happened before
Allsky was installed, it's not an Allsky issue. Sometimes GitHub hiccups or
your network went down. Please remove the "allsky" directory and try the git
clone again.
Yesterday I had to try "git clone" several times on one of my test
machines and had to reboot it to get it to work. I assume the Pi was in a
funky state.
—
Reply to this email directly, view it on GitHub
https://github.com/AllskyTeam/allsky/issues/3262#issuecomment-1872618695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABLTBOMJL54ZRZUAKIY7PPTYMCJARAVCNFSM6AAAAABBHYZWAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGYYTQNRZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@rdwhynot, glad you figured it out.
Hope you don't mind, but I'm using your screenshot in a new Issue to add a Troubleshooting documentation page for git problems.


Use tabs in go docs

Reported by Simon Klee on Slack.
Pre-merge checklist
Performance:

[ ] Compare zig benchmark on linux before and after this pr.# benchmark results before
...

# benchmark results after
...

OR

[x] I am very sure this PR could not affect performance.

bors r+


Add ISES (Faculdade Sumare)

Adding the Sumare Institute of Higher Education.

Web page: https://sumare.edu.br/

@Cicero-Oliverio Pull request merged. Thank you!


Assassin's Creed® III Liberation [PCSE00053]

App summary

App name: Assassin's Creed® III Liberation
App serial: PCSE00053
App version: 1.00

Vita3K summary

Version: v0.1.5
Build number: 2708
Commit hash: https://github.com/vita3k/vita3k/commit/025f87b1
CPU backend: Dynarmic

Test environment summary

Tested by: gymzatan
OS: Windows 11
CPU: AMD Ryzen 7 5800H
GPU: AMD Radeon(TM) Graphics
RAM: 16 GB

Issues
Game runs at low frame rate (1-2 FPS) with severe graphics issues that render it unplayable.
Screenshots

Log
vita3k.log
Recommended labels

Ingame -
graphics bug
slow

This should be retested, the graphics might have become a lot better

App summary

App name: Assassin's Creed® III Liberation
App serial: PCSE00053
App version: 1.00

Vita3K summary

Version: v0.2.0
Build number: 3596
Commit hash: https://github.com/vita3k/vita3k/commit/418f2343
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary
Tested by: MrSythos
OS: Windows 11
CPU: Ryzen 5 5600X
GPU: GTX 1050 TI
RAM: 32 GB
Issues
The game's framerate is surprisingly strong staying at 30fps most of the time. The real problem is with the graphics. Turning all resolution settings to 1x and having renderer accuracy on high results in most buildings loading in. The characters however, remain as black figures with no detail. Even with these setbacks I was able to play out the beginning of the tutorial just fine, and presumably the game would be playable if not for the graphics issues.
Screenshots

Log
vita3k.log
Recommended Labels

Ingame+

No, this game should still be in Ingame- because it requires the back touchpad pretty early in the game and that has nor been implemented in Vita3k yet.

No, this game should still be in Ingame- because it requires the back touchpad (to open letters) pretty early in the game and that has not been implemented in Vita3k yet.

I thought that did work if you're using a Dual shock 4 or 5 with the touchpad on the controller.

No, this game should still be in Ingame- because it requires the back touchpad (to open letters) pretty early in the game and that has not been implemented in Vita3k yet.

I didn't get as far as opening letters to test that in AC3 Liberation, but I can attest that the touchpad does work in Vita3K as long as your using a controller that has one like a Dual shock or dualsense

No, this game should still be in Ingame- because it requires the back touchpad (to open letters) pretty early in the game and that has not been implemented in Vita3k yet.

You are actually right. I jumped back into the game and pushed a bit further in. I didn't realize that Vita3K didn't have the rear touchpad emulated. While the touchpad on a Dualshock or Dualsense can emulate the touchscreen, it doesn't emulate the rear pad making the game impossible to complete unless Vita3K implements it. I also noticed upon retesting that the combat music stays long after leaving combat.
Screenshots

Log
vita3k.log
Recommended Labels

Ingame -
Touchscreen Issues
Audio Bug


Can I include a 'conditional' statement  in the config.json?

I am trying to use my Dash button as an ON/OFF trigger for a hue bulb. I would like to 'GET' the current state and accordingly 'PUT' an ON or OFF command to the bulb . Any advice? I am currently using IFTTT as a workaround but I think it might be faster to directly communicate to the hub.
Thanks

There’s no mechanism for reading state. You’ll want to do this on the receiving end.


Hotkeys for "Switch to virtual desktop number X" and "Move window to virtual destop number X"

Provide a description of the new feature / enhancement
Currently, you can only move back and forth between the viral desktops.
The same goes for moving windows.
We really need customizable hotkeys to switch to a virtual desktop with a specific number, as well as to move a window to a virtual desktop with a specific number.

Feels like #19, #16 would be the tracking items for this.


Add SD card button on the quick access menu

add a sd card button here

2nd button is sd card;)
Op za 27 jan. 2024 01:05 schreef joe32 @.***>:

add a sd card button here
image.png (view on web)
https://github.com/TFyre/bambu-farm/assets/78875887/1c55c91b-46e4-4bbc-b9c2-592e9a7a785f
—
Reply to this email directly, view it on GitHub
https://github.com/TFyre/bambu-farm/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALGZAT6V7WP4XDY67SPJI3YQRADDAVCNFSM6AAAAABCM4J25SVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYDGMBXHE2DINA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

The 2nd button is SD card


Mark Postal.Email.Send method as virtual

Currently, we can use member hiding (new keyword) to extend the behavior of Postal.Email.Send:
class CustomEmail : Postal.Email
{
    public MailAddressCollection Recipients { get; set; }

    public string CrazySpecialProperty { get; set; }

    public new void Send()
    {
        // record stuff in the database here

        base.Send();
    }
}

My suggestion is that Postal.Email.Send be marked virtual so that derivative classes may have the option of overriding it. As it stands today, any extended Send behavior would be lost if the custom email class was cast to its base class.

+1 we also do this

@tuespetre Why close this? It hasn't been addressed has it?

I was able to satisfactorily move behavior out of the Send method and I don't want it on my issue list any more. I wouldn't blame you for opening your own though ;)

@tuespetre Okay I may do that :)
Though I think this library may be abandonware, so not sure it matters :(


Fix: Header content in Members RHP overflows

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/45854
PROPOSAL: https://github.com/Expensify/App/issues/45854#issuecomment-2241302410
Tests

Go to staging.new.expensify.com
Submit an expense to any user
Go to transaction thread
Click Description
Enter at least 4 lines of description
Right click on the system message > Reply in thread
Click on the thread header

[x] Verify that the description is truncated to one line on report details page

Click Members

[x] Verify that the subtitle is truncated to one line below Members header

[x] Verify that no errors appear in the JS console

Offline tests

Same as test steps
QA Steps

Same as test steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/5ef3c94d-a979-4711-b872-185d6bd1307d

Android: mWeb Chrome

https://github.com/user-attachments/assets/52dfa73c-6a5d-455e-910f-ddb2fbbb4479

iOS: Native

https://github.com/user-attachments/assets/a6cae6d5-b994-472f-a418-beae7a74c191

iOS: mWeb Safari

https://github.com/user-attachments/assets/c82314fc-05fa-40e6-b30c-86514213a866

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/1f67c566-783f-4db4-8655-5b2449daa6b0

MacOS: Desktop

https://github.com/user-attachments/assets/34c22478-fb6e-4206-a458-eba35bd597eb

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

https://github.com/user-attachments/assets/3d1d5500-0ede-41d5-a6a7-6e33830a4be3

iOS: Native

iOS: mWeb Safari

https://github.com/user-attachments/assets/65ec06b6-4eec-4d73-bb0f-3adf7ba193f1

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/52dfdd44-5abe-4ef6-9a34-e081197b9670

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.15-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.15-9 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


update common

https://github.com/fractal-analytics-platform/fractal-common/pull/60

Let's bring back poetry.lock to its main state, and only update typing-extension - if possible.


🌐 Add Spanish translation for cookie-params docs/es/docs/tutorial/cookie-params.md

🌐 Add Spanish translation for cookie-params docs/es/docs/tutorial/cookie-params.md

📝 Docs preview for commit 41b18ce91f8faee57fa483d0d16f601bee913c1b at: https://cea9fea4.fastapitiangolo.pages.dev

another approved plz

Hi @fabianfalon Thanks for the contribution! I made a small change just to maintain consistency with the rest of the docs. Thanks for your help! :nerd_face: :rocket:
And thanks for the review @JavierSanchezCastro :v: :cake:


Support for sqlalchemy>= 1.4.0

In https://github.com/dask/dask/pull/7405 we temporarily pinned sqlalchemy<1.4.0 to avoid deprecation warnings from being raised inside pandas (xref https://github.com/pandas-dev/pandas/issues/40467) which caused CI here to start failing.
We should revisit this and make sure Dask is compatible with newer version of sqlalchemy.  It looks like those updates are being backported to pandas=1.2.4.
Though I'll note that when using the latest pandas nightly release (which includes the updates from https://github.com/pandas-dev/pandas/pull/40471) and sqlalchemy=1.4.0 I still get test failures like the one mentioned above

Ping. SQLAlchemy 1.4.0 was released almost 4 months ago, and dask is still blocking the upgrade.

(and there are packages that require sqlalchemy 1.4+ already)

Thanks for the ping @mgorny .  Is this something that you would like to take on?

With python3-sqlalchemy-1.4.23-1.fc36.x86_64, python3-pandas-1.3.0-2.fc35.x86_64 (current in Fedora 35), I only get one test failure because of a deprecation warning:
dask/dataframe/io/sql.py:115: in read_sql_table
    index = table.columns[index_col] if isinstance(index_col, str) else index_col
...
E           sqlalchemy.exc.SADeprecationWarning: The SelectBase.c and SelectBase.columns attributes are deprecated and will be removed in a future release; these attributes implicitly create a subquery that should be explicit.  Please call SelectBase.subquery() first in order to create a subquery, which then contains this attribute.  To access the columns that this SELECT object SELECTs from, use the SelectBase.selected_columns attribute. (deprecated since: 1.4)

/usr/lib64/python3.10/site-packages/sqlalchemy/util/langhelpers.py:1675: SADeprecationWarning


do not check build files with diff is empty

When updating with --devel --needed, VCS packages will be checked for update and only built if their source has been updated. However, the prompt to inspect build files will be displayed regardless of the outdated status of the sources.
Display the build files inspection prompt only for VCS packages that will be rebuilt. This should only apply when both --devel and --needed are used.

Not sure how tired I was when I entered this issue, but it doesn't make sense. For one thing, build files retrieval (git clone) is completely independent from the actual project source files, and if --devel is passed it means the build files have not changed at all. If the build files have been updated by the maintainer on the AUR, then there will be a new pull and diff view if enabled.
Instead, the build files diff should be skipped when empty.

Done in a2fe4aaf86c125b564e5fb70307378f045944c7e.

@avelkei @pakapusta @Yoshi2889 @ChuckDaniels87 @MakeNowJust @kyak
The above commit adds a single new string to translate (sorry!). Since you guys have an otherwise 100% complete translation, you might want to send an update before the next release.
Instructions are in the po/HOWTO file.
I hope to make the new release at the end of the week.

@rmarquis Ok, I will work it today. Thanks. 水曜日, 06 4月 2016, 06:28午前 +09:00 from Remy Marquis <<EMAIL_ADDRESS>:

@avelkei @pakapusta @Yoshi2889 @ChuckDaniels87 @MakeNowJust @kyak
The above commit adds a single new string to translate (sorry!). Since you guys have an otherwise 100% complete translation, you might want to send an update before the next release.
Instructions are in the po/HOWTO file.
I hope to make the new release at the end of the week.
—
You are receiving this because you were mentioned.
Reply to this email directly or  view it on GitHub

I'll try to update my translation today :) though my laptop will be going
in for repair so I'll need to setup a VM on my Mac or desktop.
I'll also fix the colorW issue on AUR upgrade.
Op wo 6 apr. 2016 03:14 schreef TSUYUSATO Kitsune<EMAIL_ADDRESS>
:

@rmarquis Ok, I will work it today. Thanks. 水曜日, 06 4月 2016, 06:28午前
+09:00 from Remy Marquis <<EMAIL_ADDRESS>:

@avelkei @pakapusta @Yoshi2889 @ChuckDaniels87 @MakeNowJust @kyak
The above commit adds a single new string to translate (sorry!). Since
you guys have an otherwise 100% complete translation, you might want to
send an update before the next release.
Instructions are in the po/HOWTO file.
I hope to make the new release at the end of the week.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/rmarquis/pacaur/issues/452#issuecomment-206062679

Thanks for the heads up, made a pull request.

@Yoshi2889 I can update the file for you if you tell me the translation (see a2fe4aaf86c125b564e5fb70307378f045944c7e).

@rmarquis That'd be great, thanks.
${colorW}$i${reset} build files are up-to-date -- skipping
translates to:
build bestanden voor ${colorW}$i${reset} zijn up-to-date -- overgeslagen
If you could also fix this issue while you're at it, that'd be great:
msgstr "$(colorW)AUR upgrade starten...${reset}"
needs to become:
msgstr "${colorW}AUR upgrade starten...${reset}"
(bracket change)
Thanks!

@Yoshi2889 Done in 677a77b328fc7e23e0a4c8e045283e7a34aa69dd.


[WIP] The barren plateau phenomenon

итого, автор не успел сделать лекцию, к сожалению. не добавляем в 0ю итерацию курса, но доделать надо

hey Arthur @artix41, I've read what's already there in the lecture and I should say it's shaping out as an amazing tutorial! we are now releasing the week of the course which includes your lecture thus we'll include it in the next run of the course, let me know if I can help here

@artix41 Hello! For your information: you can see a staging version of your lecture here: http://<IP_ADDRESS>/286_merge/_build/html/book/qnnblock/barrenplateau.html
It will update automatically after each commit in this pull-request)


Bug:  create_single_dose_dataset expects mandatory values that documentation says are defaults, related to issue #1408

What happened?
create_single_dose_dataset function documentation describes ASTDT, ASTDTM, AENDT and AENDTM as function default values but running with admiral version 0.9.0 ASTDT, ASTDTM, AENDT and AENDTM are now apparently mandatory variables.  I expected to define my own variable names (as below) in the function as done previously and create a ex_single dataframe to use in ad_adae.R.
start_date = EXSTDT,
start_datetime = EXSTDTM,
end_date = EXENDT,
end_datetime = EXENDTM
Session Information
Error in assert_data_frame():
! Required variables ASTDT, ASTDTM, AENDT and AENDTM are missing.
Reproducible Example
Several EX preprocessing steps are required before the final step where the ex_mod dataframe contains derived date and datetime variables
ex_single <-
create_single_dose_dataset(
ex_mod,
dose_freq = EXDOSFRQ,
start_date = EXSTDT,
start_datetime = EXSTDTM,
end_date = EXENDT,
end_datetime = EXENDTM
lookup_table = dose_freq_lookup,
lookup_column = CDISC_VALUE
) %>%
Select only unique values
distinct(STUDYID,USUBJID,EXTRT,EXDOSE,EXDOSFRQ,DCUTDT,DTHDT,EXSTDT,EXENDT

@oreillb1 , thanks for reporting this bug.
It is caused by the default value of keep_source_vars. It is hard-coded to vars(USUBJID, EXDOSFRQ, ASTDT, ASTDTM, AENDT, AENDTM) but should depend on the start_* and end_* arguments.
For now you need to specify the keep_source_vars argument. In your case keep_source_vars = vars(USUBJID, EXDOSFREQ, EXSTDT, EXSTDTM, EXENDT, EXENDTM).

Since multiple treatments can be given at the same time I believe EXTRT needs to be included in the keep_source_vars = vars(USUBJID, EXTRT, EXDOSFRQ, EXSTDT, EXSTDTM, EXENDT, EXENDTM) but there continues to be an error
Error in filter():
! Problem while computing ..1 = is.na(EXSTDT) | is.na(EXENDT) | is.na(ASTDTM) | ....
Caused by error:
! object 'ASTDTM' not found

Having made changes and setting up ex_mod using admiral test data, I now see this error
Error in mutate():
! Problem while computing dose_periods = case_when(...).
Caused by error in if_else():
! false must have class Date, not class POSIXct/POSIXt.
when running this code
ex_single <-
create_single_dose_dataset(
ex_mod,
dose_freq = EXDOSFRQ,
start_datetime = EXSTDTM,
start_date = EXSTDT,
end_datetime = EXENDTM,
end_date = EXENDT,
lookup_table = dose_freq_lookup,
lookup_column = CDISC_VALUE,
keep_source_vars = vars(STUDYID,USUBJID,EXTRT,EXDOSFRQ,DCUTDT,DTHDT,EXSTDT,EXSTDTM,EXENDT,EXENDTM)
)

This part of the code is causing trouble because TRTEDTM does not have class = Date so I'm not able to replace NA values.
EXENDTM = if_else (is.na(EXENDTM) & is.na(DTHDT), DCUTDT, EXENDTM)


Call to a member function beginTransaction() on null

When I fire php artisan queue:work command , it throws following error
PHP Fatal error:  Call to a member function beginTransaction() on null in /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 576
PHP Stack trace:
PHP   1. {main}() /var/www/html/push_admin/setupl/artisan:0
PHP   2. Illuminate\Foundation\Console\Kernel->handle() /var/www/html/push_admin/setupl/artisan:36
PHP   3. Symfony\Component\Console\Application->run() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:107
PHP   4. Symfony\Component\Console\Application->doRun() /var/www/html/push_admin/setupl/vendor/symfony/console/Application.php:117
PHP   5. Symfony\Component\Console\Application->doRunCommand() /var/www/html/push_admin/setupl/vendor/symfony/console/Application.php:186
PHP   6. Illuminate\Console\Command->run() /var/www/html/push_admin/setupl/vendor/symfony/console/Application.php:794
PHP   7. Symfony\Component\Console\Command\Command->run() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Console/Command.php:155
PHP   8. Illuminate\Console\Command->execute() /var/www/html/push_admin/setupl/vendor/symfony/console/Command/Command.php:256
PHP   9. Illuminate\Container\Container->call() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Console/Command.php:169
PHP  10. call_user_func_array:{/var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Container/Container.php:507}() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Container/Container.php:507
PHP  11. Illuminate\Queue\Console\WorkCommand->fire() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Container/Container.php:507
PHP  12. Illuminate\Queue\Console\WorkCommand->runWorker() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php:79
PHP  13. Illuminate\Queue\Worker->pop() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php:126
PHP  14. Illuminate\Queue\Worker->getNextJob() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:149
PHP  15. Illuminate\Queue\DatabaseQueue->pop() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:180
PHP  16. Illuminate\Database\Connection->beginTransaction() /var/www/html/push_admin/setupl/vendor/laravel/framework/src/Illuminate/Queue/DatabaseQueue.php:162
[Symfony\Component\Debug\Exception\FatalErrorException]
Call to a member function beginTransaction() on null
Anybody have any idea about it? Please help!!!

Also posted question on stack overflow http://stackoverflow.com/questions/39615770/php-fatal-error-call-to-a-member-function-begintransaction-on-null-in-connect

Hello,
I'm also getting this same error.
[2016-11-12 20:18:45] local.ERROR: exception 'Symfony\Component\Debug\Exception\FatalErrorException' with message 'Call to a member function beginTransaction() on null' in C:\wamp\www\blog\vendor\laravel\framework\src\Illuminate\Database\Connection.php:611
Stack trace:
#0 {main}
Can anybody please help me?
Thanks,

@sachinvrg , Have you configured queue properly as described over here:
https://github.com/jenssegers/laravel-mongodb#queues
I have found the issue with my project.
I had not followed the queue configuration of the package.
Just follow the proper instruction and it works very well.

The specific issue that it's complaining about is that it's trying to get the PDO on a database connection that doesn't have it.
https://github.com/laravel/framework/blob/5.3/src/Illuminate/Database/Connection.php#L612
The getPdo() method returns null in the case of the mongodb driver connection. You may have to avoid using the database queue driver if you use this package, or you can overload the beginTransaction method to simply do nothing.

Having this issue on Laravel 5.8 (latest) when attempting to connect through API.
Call to a member function beginTransaction() on null {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalThrowableError(code: 0): Call to a member function beginTransaction() on null at /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:109) [stacktrace] #0 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php(93): Illuminate\\Database\\Connection->createTransaction() #1 /var/www/html/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php(23): Illuminate\\Database\\Connection->beginTransaction() #2 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php(183): Illuminate\\Database\\Connection->transaction(Object(Closure)) #3 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/DatabaseStore.php(122): Illuminate\\Cache\\DatabaseStore->incrementOrDecrement('97ae145b1055ad7...', 1, Object(Closure)) #4 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/Repository.php(331): Illuminate\\Cache\\DatabaseStore->increment('97ae145b1055ad7...', 1) #5 /var/www/html/vendor/laravel/framework/src/Illuminate/Cache/RateLimiter.php(65): Illuminate\\Cache\\Repository->increment('97ae145b1055ad7...') #6 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Middleware/ThrottleRequests.php(56): Illuminate\\Cache\\RateLimiter->hit('97ae145b1055ad7...', 60) #7 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Routing\\Middleware\\ThrottleRequests->handle(Object(Illuminate\\Http\\Request), Object(Closure), 60, '1') #8 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #9 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #10 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(682): Illuminate\\Pipeline\\Pipeline->then(Object(Closure)) #11 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(657): Illuminate\\Routing\\Router->runRouteWithinStack(Object(Illuminate\\Routing\\Route), Object(Illuminate\\Http\\Request)) #12 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(623): Illuminate\\Routing\\Router->runRoute(Object(Illuminate\\Http\\Request), Object(Illuminate\\Routing\\Route)) #13 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Router.php(612): Illuminate\\Routing\\Router->dispatchToRoute(Object(Illuminate\\Http\\Request)) #14 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(176): Illuminate\\Routing\\Router->dispatch(Object(Illuminate\\Http\\Request)) #15 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(30): Illuminate\\Foundation\\Http\\Kernel->Illuminate\\Foundation\\Http\\{closure}(Object(Illuminate\\Http\\Request)) #16 /var/www/html/vendor/fideloper/proxy/src/TrustProxies.php(57): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #17 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Fideloper\\Proxy\\TrustProxies->handle(Object(Illuminate\\Http\\Request), Object(Closure)) #18 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #19 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #20 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure)) #21 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #22 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/TransformsRequest.php(21): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #23 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\TransformsRequest->handle(Object(Illuminate\\Http\\Request), Object(Closure)) #24 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #25 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/ValidatePostSize.php(27): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #26 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\ValidatePostSize->handle(Object(Illuminate\\Http\\Request), Object(Closure)) #27 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #28 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Middleware/CheckForMaintenanceMode.php(62): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #29 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(163): Illuminate\\Foundation\\Http\\Middleware\\CheckForMaintenanceMode->handle(Object(Illuminate\\Http\\Request), Object(Closure)) #30 /var/www/html/vendor/laravel/framework/src/Illuminate/Routing/Pipeline.php(53): Illuminate\\Pipeline\\Pipeline->Illuminate\\Pipeline\\{closure}(Object(Illuminate\\Http\\Request)) #31 /var/www/html/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(104): Illuminate\\Routing\\Pipeline->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request)) #32 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(151): Illuminate\\Pipeline\\Pipeline->then(Object(Closure)) #33 /var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php(116): Illuminate\\Foundation\\Http\\Kernel->sendRequestThroughRouter(Object(Illuminate\\Http\\Request)) #34 /var/www/html/public/index.php(55): Illuminate\\Foundation\\Http\\Kernel->handle(Object(Illuminate\\Http\\Request))

@phillmorgan28 did you eventually resolve this?

Anyone solved this problem? i am not using queue.

This issue still persists. I've already configured my queue.ph according here: Laravel MongoDB Queues
Already ran php artisan config:cache and this are the values for my queue.php

config('queue.connections.database')
[
     "driver" => "mongodb",
     "table" => "jobs",
     "queue" => "default",
     "retry_after" => 90,
]

config('queue.failed')
[
     "driver" => "mongodb",
     "database" => "mongodb",
     "table" => "failed_jobs",
]

Any other fix for this?

This issue still persists. I've already configured my queue.php according here: Laravel MongoDB Queues
Already ran php artisan config:cache and this are the values for my queue.php
config('queue.connections.database')
[
     "driver" => "mongodb",
     "table" => "jobs",
     "queue" => "default",
     "retry_after" => 90,
]

config('queue.failed')
[
     "driver" => "mongodb",
     "database" => "mongodb",
     "table" => "failed_jobs",
]

Any other fix for this?

@paouriel can't recreate, check that you've correct mongodb settings, probably you're not even connecting to db.

@divine I managed to create a workaround for this. I've created a temporary command.
Here: LaraveL MongoDB Transaction Fix

@divine I managed to create a workaround for this. I've created a temporary command.
Here: Laravel MongoDB Transaction Fix

This is really bad practice to modify vendor files. As I've said can't really recreate it.
Fork this library https://github.com/Smolevich/demo-mongo-application and add configuration as well as examples so it will be easy to recreate issues you're having.

Any solution for this headache issue ?

The specific issue that it's complaining about is that it's trying to get the PDO on a database connection that doesn't have it.
https://github.com/laravel/framework/blob/d1a4f3fc7951c04ff91855511ed8c73b1a98e533/src/Illuminate/Database/Connection.php#L612
The getPdo() method returns null in the case of the mongodb driver connection. You may have to avoid using the database queue driver if you use this package, or you can overload the beginTransaction method to simply do nothing.

Explain more please

The problem still exists. @jenssegers, please reopen this issue.

The problem still exists. @jenssegers, please reopen this issue.

See https://github.com/jenssegers/laravel-mongodb/pull/1904
Thanks!


Atom will not open a large JS file after update to 1.14.1 or 1.14.2

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When opening a large file, in this case it is any file that has multiple js minified plugins in it. Atom will just freeze and eventually comes up to ask if I want to keep waiting or close, if I choose keep waiting it will continue in that loop until I click close.
Steps to Reproduce

Open a large file with quite a few minified jquery plugins in it
Wait

Expected behavior: [What you expect to happen]
With the 1.13.1 release I was on, it would take about 5 - 10 seconds and then open with proper syntax highlighting and I could work with the file.
Actual behavior: [What actually happens]
Atom will freeze and eventually comes up to ask if I want to keep waiting or close, if I choose keep waiting it will continue in that loop until I click close.
Reproduces how often: [What percentage of the time does it reproduce?]
100% of the time I try to open this type of file.
Versions
Atom    : 1.14.2
Electron: 1.3.13
Chrome  : 52.0.2743.82
Node    : 6.5.0
apm  1.15.3
npm  3.10.5
node 4.4.5 x64
python 2.7.10
git 2.7.4
Additional Information
We use atom in production at our agency, and this is currently affecting all that have updated to the 1.14.1 and 1.14.2 versions.

@bferdinand - looks like this is a duplicate of the issue you opened here?
https://github.com/atom/text-buffer/issues/209
Going to go ahead and close but if I'm mis-understanding and this is a separate issue, let me know :v:


[Bug]: Dataflow streaming runner, improve commit stream throughput after network disruption

What happened?
Temporary VM network connection issues ended up causing minutes of latency for the grpc streams from the worker to the Streaming Engine service.
One possible cause of this could be connection deadline and backoff.
The deadline appears to default to 30 seconds for Netty. We could also look into stopping the backoff when connected based upon https://github.com/grpc/grpc-java/issues/6473
Issue Priority
Priority: 2 (default / most bugs should be filed as P2)
Issue Components

[ ] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[ ] Component: Website
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[X] Component: Google Cloud Dataflow Runner

.take-issue

The connection backoff logic while it can reach a large maximum, would take many attempts to reach that maximum. It also doesn't align with the monitoring available which shows that the stream is connected but not performing well. Stack traces indicate that the streams are often waiting for isReady to become true. From https://github.com/grpc/proposal/pull/135 it appears that is based upon 32KB queued output and is not configurable.  We have more data we want to send, and putting more data in the queue (within reason) seems like it could improve throughput by ensuring that there is always data available and not blocking on isReady to return.  Since we have a maximum message size of 2MB I think that the windmill DirectStreamObserver could be changed to evaluate isReady only every 10 messages to increase the effecting outgoing buffer size.


Add v2 column to wiki:Home w/ an initial pass

https://github.com/fl0w/koa/wiki
I basically did some manual labour here (thus error-prone).
I did NOT practically test any of these.
For a checkmark, I required one of the following:

has a next (or equivalent branch), actually checked it was of Koa v2 type branch as well.
library root export has v2 signature
repo has a clear example in readme of v2 usage

To be fair, from the looks of things - most will actually work out of the box (due to koajs/convert), so I'm thinking this might be misleading initially?
Related issue: #618

Looks good. Maybe add a note about koa-convert at the top?

@PlasmaPower Added a paragraph. Phrasing might be off, mind taking a peak?

Looks good!

@fl0w :+1: i don't mind if you guys update the wiki here. i never look at it (i just search koa on npm). i really like the format, but it seems like a lot of work to maintain. haha

@jonathanong I'm with you. Never use it.
Had no idea it was open to public to non-members.
So, I just did the update. It's easily reverted if anyone else within the org objects. Closing this one.


Color keying and PNG transparency

When I built and ran the game on my macOS machine with nix, the color keying for transparency didn't work, so I had a lot of pink/purple on the screen.
I found this question with a comment suggesting that having an alpha channel in the PNG file could fight the color keying. I used imagemagick's convert utility to remove the alpha channel from each PNG, and -- lo! -- it worked.
Not sure how widespread the issue might be, but it seems like it couldn't hurt to remove the alpha channel if it's not being used. I can PR the no-alpha PNGs if it's helpful.

@acowley Hmm... What's your architecture? This seems sort of familiar. I may have I've encountered this issue before which I think was a little-endian vs big-endian issue. This was how it was solved with SDL 1. https://github.com/jxv/gridland/blob/master/src/GridLand/SDL.hs#L49
If not, digging into how the imagemagick's convert utility works would shed some light.

I don't think convert is doing anything interesting. My guess would be along the lines of the comments on that link I included: it either has to do with some default OpenGL texture format, and that may end up being informed by the windowing system, or it's that image loading on some platforms discards alpha from PNGs while on others it is retained. If the image data from the PNG has no alpha channel, SDL uses the color key to synthesize it when filling the texture (which is what we want).
In any case, the original PNGs do have alpha channels (I don't know if you have a macOS machine or not, but I checked this by opening them in Preview.app and looking at the More Info tab of the Inspector window), which they probably don't need. Some image editing applications save a fully opaque alpha channel by default, which is what I'd guess has happened here.
It's not a big deal, the game works and is fun to play even when the sprite masking isn't working. Call it collision box visibility mode 😜

I'm running OSX as well.
~% uname -a
Darwin Joes-MacBook.local 16.7.0 Darwin Kernel Version 16.7.0: Thu Jan 11 22:59:40 PST 2018; root:xnu-3789.73.8~1/RELEASE_X86_64 x86_64```

In any case, thanks for bringing this up.

I’ll try to find some time to come up with a code fix.


client.getDiscoInfo broken in 7.0.1 (6eee99e)

I've noticed a small undeterminism when calling client.getDiscoInfo().
When client.getDiscoInfo() is executed in 7.0.1 providing it the client's own full JID, sometimes the discoInfo returned is an empty object (that is: There aren't even fields such as features, extensions, etc.).
Given this call:
<EMAIL_ADDRESS>null, function(error, reply) {
    console.warn("Here is the discoInfo: ", reply.discoInfo);
});

The raw responses look like this:
raw:outgoing <iq xmlns="jabber:client"<EMAIL_ADDRESS>type="get" id="6de5f060-4ef2-469d-a932-c544854797d2"><query xmlns="http://jabber.org/protocol/disco#info"/></iq>
raw:outgoing <r xmlns="urn:xmpp:sm:3"/>
iq:get:discoInfo Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "get"…}
iq Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "get"…}
stanza Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "get"…}
id:6de5f060-4ef2-469d-a932-c544854797d2 Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "get"…}
stream:data i {xml: n, _extensions: Object, _name: "iq", _eventname: undefined, _NS: "jabber:client"…}
 raw:incoming <iq type='get'<EMAIL_ADDRESS><EMAIL_ADDRESS>id='6de5f060-4ef2-469d-a932-c544854797d2' xmlns='jabber:client'><query xmlns='http://jabber.org/protocol/disco#info'/></iq>
 Here is the discoInfo:  Object {}
 raw:outgoing <iq xmlns="jabber:client"<EMAIL_ADDRESS>id="6de5f060-4ef2-469d-a932-c544854797d2" type="result"><query xmlns="http://jabber.org/protocol/disco#info"><identity category="client" type="web"/></query></iq>
 stream:management:ack Object {h: 28}
stanza:acked i {xml: n, _extensions: Object, _name: "iq", _eventname: undefined, _NS: "jabber:client"…}
stream:data i {xml: n, _extensions: Object, lang: "", _name: "smAck", _eventname: "stream:management:ack"…}
raw:incoming
raw:outgoing <r xmlns="urn:xmpp:sm:3"/>
iq Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "result"…}
stanza Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "result"…}
id:6de5f060-4ef2-469d-a932-c544854797d2 Object {discoInfo: Object, id: "6de5f060-4ef2-469d-a932-c544854797d2", to: 235.n.JID, from: 235.n.JID, type: "result"…}
stream:data i {xml: n, _extensions: Object, _name: "iq", _eventname: undefined, _NS: "jabber:client"…}
raw:incoming <iq type='result'<EMAIL_ADDRESS><EMAIL_ADDRESS>id='6de5f060-4ef2-469d-a932-c544854797d2' xmlns='jabber:client'><query xmlns='http://jabber.org/protocol/disco#info'><identity type='web' category='client'/></query></iq>
stream:management:ack Object {h: 29}
stanza:acked i {xml: n, _extensions: Object, _name: "iq", _eventname: undefined, _NS: "jabber:client"…}
stream:data i {xml: n, _extensions: Object, lang: "", _name: "smAck", _eventname: "stream:management:ack"…}
raw:incoming

Note that first, the success handler is executed using a prematurely built object (it's completely empty). In the further response, the object seems to be built. Note that even though the object is built, important properties (such as features) are missing.
Providing another JID than the own client's will result in the same behavior. It seems currently impossible to get another stanza.io client's features.
Function calls like these (that is, getting my own disco info) shouldn't be necessary anyway (I know that this information is stored in client.disco), but AFAIR this did work in 6.x.
Is this still compliant to the standard? It feels like a bug, though.

I've not been able to reproduce this in 7.0.1. How often does it occur for you?
This was a reliably produceable issue in 6.x because it was actually capturing the received iq-get request and treating that as the result (and that would look like an empty discoInfo object). That is supposed to be fixed in 7.x

It seems to work just fine on demo.html, given that discoInfo.features.length === 1 is normal (I expected a lot more than that, it has "http://jabber.org/protocol/pubsub#publish" as only feature). It also has an identity property, and until now, I couldn't reproduce having the same undeterminism within demo.html. Only discoInfos that look a little too small to me.
But I'm really not doing a lot more than demo.html does, anyway. It's not just the app itself, it's basically every call sent from DevTools responding in this manner (not for demo.html, it seems…).

Ok, so something is still odd if demo.html is only giving you one feature. It should be giving you ~60 of them. Does client.disco.features[''] give you the full set of features or is that also truncated?

Yes, client.disco.features[''] is giving me the full ≈60 features. By the way, I just noticed that
client.getDiscoInfo(client.config.jid.full, null, function(error, success) {
    console.warn("Responses: ", error, success);
});

will actually be sent out to the wrong client in demo.html, namely the resource that I entered in the input (which is actually not the resouce that the client actually has). Therefore, this upper call will always result in a timeout. Is this behavior intended?

Intended. You'd want to use client.jid.full instead of client.config.jid, because the first is always what you were actually assigned during binding (event the localpart could have changed, not just resource).

I see, thanks. :)
This might have something to do with my app then; I might register features in an unintended way, which destroys the correct behavior (returning a discoInfo with features) for
client.getDiscoInfo(client.jid.full, null, function(error, success) {
    console.warn("Responses: ", error, success.discoInfo);
});

Currently, I define a handfull of stanzas at runtime and pass it to client.use before client.connect is executed. These stanza functions start with
client.disco.addFeature(NS);

with NS being their namespace. Am I supposed to add it to my feature list by just pushing it into the array, maybe?


Migrate away from Gulp

The current build system uses Gulp, which I think is no longer supported.
For:

CSS: Dart Sass
Docs: see #7

Closing as #10 fixed build issues... and if it ain't broke!
However, #7 will likely remove the docs build task


Unit autoscale matplotlib and pyqtgraph graphs

@WilliamHPNielsen
Add methods to autoscale graphs backported and improved from qcodes-dk
Must currently be called manually

Nice stuff. But when running a standard QCoDeS loop, the fixUnitScaling function should be called before the plot is dumped as a .png (and preferably before that). I guess it would make sense to include it in the updater for the plot?

Done. I have put it in the create function and added support for rescaling the limits. I think this is better than the update both because it's waist of time to do it at every update and because it might change the limits during the plot which I doubt is a good idea. Note that rescaling of non array parameters to the correct limits requires you to pass them to the function. This is not done automatically as the plot does not know the limits before the data is acquired


Inconsistencies in results in Mistral, CodeLlama and some strange behavior.

So, I also came across some inconsistencies in results. Also, when I was going to raise the issue, I also came across this issue #142. So, I was trying to reproduce the results for codellama-7B and Mistral-7B. Let's discuss on HumanEval benchmark (this same happens for benchmarks like MBPP and Multipl-e too).
I would like to discuss these in-consistencies in two parts:
Part 1: Inconsistencies in paper results.
So here are the results of CodeLlama7B and Mistral7B for HumanEval benchmark.
CodeLlama-7B: (in codellama paper) 33.5%
CodeLlama-7B: (in Mistral paper) 31.1%
CodeLlama-7B  (from Bigcode Leaderboard) 29.9%

Mistral-7B: (in Mistral paper) 30.5%

When I did the experiments, with the required greedy configuration, I saw it was giving me a score of 29.8 %, which was same as the leaderboard. However, I still had questions that why we have a difference of such a value of ~ (2-3) % w.r.t. the paper. Although this clarifies a part of my doubt.
However, I also want to know is there any reasons, these model's repo (like mistral-src or codellama repo), do not provide any reproducibility script?
Part 2: Mistral giving higher result with int-4 (bnb) rather fp32.
So, I also evaluated Mistral model and there I saw a very strange phenomenon. At first here are the evaluation results on HumanEval:
Mistral-7B fp16: 28.6 (deviating by 1.89 %)
Mistral-7B int-4: 29.8

Now, I made some slight code changes, where instead of passing the model precision from command line, I made a custom change in the model using BitsAndBytes config and passed it the evaluation engine. Here is the sample code:
bnb_config = BitsAndBytesConfig(
    load_in_4bit=True,
    bnb_4bit_use_double_quant=True,
    bnb_4bit_quant_type="nf4",
    bnb_4bit_compute_dtype=torch.bfloat16
)

model_id = "filipealmeida/Mistral-7B-v0.1-sharded"
model = AutoModelForCausalLM.from_pretrained(
    model_id,
    quantization_config=bnb_config,
    device_map="auto"
)

tokenizer = AutoTokenizer.from_pretrained(
    model_id,
    truncation_side="left",
    padding_side="right",
)

So, instead of flagging --load_in_4bit I passed the model with above changes. Because --load_in_4bit just adds this under model_kwargs. Now the question is, just doing this, it increases the evaluation performance score by huge amount. I wonder why is that the case?
Here are the results of both the model when evaluated using BitsAndBytes.
Mistral-7B with BitAndBytes int-4 loading: 30.49 %
CodeLlama with BitsAndBytes int-4 loading: 31.71 %

What is super strange is that now the models are giving very close results to that it was in the paper. And for all the cases I set do_sample to False.
I would love to discuss and understand more on this and what might go unusual.

When I did the experiments, with the required greedy configuration, I saw it was giving me a score of 29.8 %, which was same as the leaderboard. However, I still had questions that why we have a difference of such a value of ~ (2-3) % w.r.t. the paper. Although https://github.com/bigcode-project/bigcode-evaluation-harness/issues/142#issuecomment-1757169293 clarifies a part of my doubt.

yes as explained in my comment, it might be due to small differences in post-processing or inference precision. When comparing models it should be fine as long as you use the same framework and pipeline which is what the leaderboard is intended for, instead of just comparing scores across research papers which might use different implementatins.

However, I also want to know is there any reasons, these model's repo (like mistral-src or codellama repo), do not provide any reproducibility script?

That's up to the Mistral and CodeLLaMa authors to answer ^^
Regarding the differences you're observing with respect to quantization, greedy evaluation might have more noise than top-p sampling with a large number of solutions e.g 50, where you give the model 50 chances to solve each problem instead of one, maybe try the evaluation again with this setup?

where you give the model 50 chances to solve each problem instead of one, maybe try the evaluation again with this setup?

That's something worth trying out, will do that. Thanks for clearing some of my doubts.

May I also ask what is the decoding strategy is applied by default? Does it affect the performance observed? Much appreciated.

After re-reading the learderboard about and Huggingface document (https://huggingface.co/blog/how-to-generate) I assume that the decoding strategy used is nucleus sampling with temperature=0.2 and top_p=0.95? Thanks.

After re-reading the learderboard about and Huggingface document (https://huggingface.co/blog/how-to-generate) I assume that the decoding strategy used is nucleus sampling with temperature=0.2 and top_p=0.95? Thanks.

Yes you are right. But for pass@1, we want greedy decoding (which should provide deterministic response) and so, temp is kept to 0 and top_p is not required so None should work.

The leaderboard uses top-p sampling, top-p=0.95 to generate 50 samples per problem to compute pass@1.
You can also use greedy which is deterministic for the model under the same setup and gives results with a 1 or 2 points difference to top_p sampling with 50 samples. However if you want to reduce noise doing sampling with a large number of samples (e.g 50 or 100) might be less noisy than greedy since you give the model more than one chance to solve each problem.

Oh, I see. Actually I was following the convention provided by codellama paper. However, this makes sense. I would like to do that for my case of evaluation.

The leaderboard uses top-p sampling, top-p=0.95 to generate 50 samples per problem to compute pass@1.

I am kinda confused here, because does by definition pass@1 means to use the model's generation only one time?

From Codex paper

pass@k metric, where k code samples are generated per problem, a problem is considered solved if any sample passes the unit tests, and the total fraction of problems solved is reported. However, computing pass@k in this
way can have high variance. Instead, to evaluate pass@k, we generate n ≥ k samples per task (in this paper, we
use n = 200 and k ≤ 100), count the number of correct samples c ≤ n which pass unit tests, and calculate the unbiased estimator

Ahh I see, got it, thanks for this reference appreciate this :)


updating preflight task to use preflight v1.4.3

Updating preflight tats to v1.4.3, which mainly has dependency updates.

Signed-off-by: Adam D. Cornett<EMAIL_ADDRESS>

@komish Thanks for adding the comment, forgot it when opening the PR.


inspector - expand, narrow selection via +/- shortcut on keyboard

Describe the problem
The inspector is great. The only shortcoming is that sometimes when I select an element, it opens the target component (e.g. Button.svelte) and not the container of that component (e.g. Nav.svelte).
Sometimes it's impossible to select precisely, because there's not even a margin to click in to select (in this case) Nav.svelte.
This feature is literally perfect, and I use it all the time.
This is the only thing missing.
Describe the proposed solution
I press my toggleKeyCombo, and while holding it, I strangle the + key on the numeric keypad.
Then the selection should expand from button to parentElement, which is nav.
In the other direction, the - key on the numeric keypad.
Alternatives considered
It doesn't.
Importance
would make my life easier

This is a nice idea. It would have to reset when moving the mouse over a different element though.


Human Explanation in English

Google says
For example, I can send the whining of the zap to my friend by simulating a call from his mother, and when he answers, AAAWN OOOWN NHAAA AWWWWN AAAAAH (inclusive, you just fell on the zap of written zap).

I didnt understand really.

@dsslimshaddy, think of a NSFW Rick Roll audio

I'm just gonna leave this here:
https://www.youtube.com/watch?v=peNTqOo9Qf0

Just to clarify, "gemido" should be translated as "moaning" and not "whining". "Gemidão do zap" should be translated as "whatsapp's moaning", since "zap" is not a slang that people would understand outside Brazil.


Updating ActivationOperations.java to include optional parameter

Signed-off-by: Aman<EMAIL_ADDRESS>

Closing this as issues with dco-required


Newer release available antlr4_runtimes: 4.7.2 (current: 4.7.2)

Package Name<EMAIL_ADDRESS>Current Version: 4.7.2@2018-12-18
Available Version: 4.7.2@2021-11-06
Upstream releases: https://github.com/antlr/antlr4/releases

New version is available for this package
New Version: 4.9.3@2021-11-06
Upstream releases: https://github.com/antlr/antlr4/releases
New Issue Link: https://github.com/phlax/envoy/issues/99


Add custom appveyor configuration

@CAMOBAP795 the appveyor builds are failing with this message:
gem install --local .\metanorma-cli.gemspec -- --with-xml2-include=%XSLT_PROC%\include\libxml2 --with-xslt-include=%XSLT_PROC%\include --with-xml2-lib=%XSLT_PROC%\lib --with-xslt-lib=%XSLT_PROC%\lib
173ERROR:  Could not find a valid gem '.\metanorma-cli.gemspec' (>= 0) in any repository
174

Have some progress, original issue was with miss-match of ruby arch and native lib arch (because appveyor use x64 VMs chocolatey installed x64 version of libxslt)
For now we have test crashing because of processes metanorma options inside Asciidoc (FAILED - 1)
@ronaldtse let me know if it important to fix in near time

Yes it is important to fix ASAP. @opoudjis do you have a clue?

@ronaldtse investigation finished, it's not related to tests by itself it's about missing RUBY_DLL_PATH  which point to directory with libx[ml|slt].dll, fixed, PR on CI

@CAMOBAP795 AppVeyor build isn’t finding the gem dependencies, such as “Metanorma-iso” gem. Can we just directly “gem install”?
Or if we have to use bundle, there is some way to also install the dependencies?

@ronaldtse finally done, let me summarize all issues which was discovered during appveyor setup:

[x] miss-match architecture between ruby binaries and xsltproc binaries (they both must be the same x86 or x64)
[x] missing RUBY_DLL_PATH for xsltproc binaries
[x] RUBY_DLL_PATH not supported in ruby bellow 2.4.1, so we need just copy dll to ruby bin directory

Thank you very much!

@camobap795 please help ensure that the homebrew formula and the chocolatey formula takes care of all these issues too!

@ronaldtse good point for homebrew there will be no such issues because libxml2 & libxslt preinstalled  on OSX, regarding chocolatey because we control dependency installation it also not a case.
The only case when someone as developer will try to install metanorma-cli gem, for such users make sense to create some wiki page on GH or update README or something similar

(In a new PR please)

Sure, also I propose to add badges for all repos where we use appveyor https://www.appveyor.com/docs/status-badges/

@CAMOBAP795 yes please! Completely forgot...

@ronaldtse I haven't access to settings on appveyor, so I cannot get badge link (it's not such trivial as travis) could you please post link to badge ?

This:
https://ci.appveyor.com/api/projects/status/abmg1f8h3phducxs?svg=true


Automated cherry pick of #11970: fix(region): allow guest network zero bandwidth limit

Cherry pick of #11970 on release/3.7.
#11970: fix(region): allow guest network zero bandwidth limit

/lgtm

/approve


Correctly display Atlantis items

game-version: v2.10
tqvault-version: <IP_ADDRESS>
As you can see ALL Atlantis items are not being displayed correctly. Non-atlantis items work fine.

btw. if you switch back to v3.9, start the game once and open tqvault --> items are displayed correctly

Could you share one of these files?

Sure I can:
sample.vault.txt
remove ".txt" after downloading. Github doesn't support ".vault"
btw I resolved the issue by downloading Titan Quest v2.9 and linking TQVault to the v2.9 version. Afterward, I've downloaded TQv2.10. If you link TQVault to v2.10 it will display all Atlantis items like in the picture. My guess is that TQVault uses data from the game folder and v2.10 does something differently than v2.9.

I can't reproduce it on my machine using a fresh install of TQVault 3.8.
The game is still v2.9 on Steam (not v2.10).  What version are you using ?

look at my first post. the problem only happens if you use titan quest v2.10

look at my first post. the problem only happens if you use titan quest v2.10

Yes but v2.9 (Steam) is older than v2.10. So where did you get (platforme) that latest version ?

on Steam

the publicbeta - version is v2.10

game-version: v2.10
tqvault-version: <IP_ADDRESS>
As you can see ALL Atlantis items are not being displayed correctly. Non-atlantis items work fine.

Hey there im the same problem but im using a mod and me thinks thats the problem:
https://steamcommunity.com/sharedfiles/filedetails/?id=2045473788
If anyone can look in to it and would be greatly appreciated!

game-version: v2.10
tqvault-version: <IP_ADDRESS>
As you can see ALL Atlantis items are not being displayed correctly. Non-atlantis items work fine.

Hey there im the same problem but im using a hard mod and me thinks thats the problem:
https://steamcommunity.com/sharedfiles/filedetails/?id=2045473788
If anyone can look in to it and would be greatly appreciated! (TQ AE GOG v2.9)

Have you selected your mod in configuration before loading your character in TQVault? (Custom Map setting)

No.

Which mod?

See my answer about "Hard Mod" here #387.

so,  what's the solution for  KuniXl commented on Aug 19?
same problems with my vault <IP_ADDRESS>.
using TQ v 2.10

My solution was:

Download TQ 2.9 (just not 2.10)
Copy the game folder somewhere
Change the "TQ Game PAth" and IT Game Path" to the 2.9 folder
Download 2.10
Enjoy that TQVault displays everything correct, while being able to play 2.10

can't find TQ v2.9.
only 2.9 update-PLAZA

I guess that should be right.

my TQ 2.10 is Titan.Quest.Anniversary.Edition.Atlantis.v2.10-P2P
it's not PLAZA.

just don't have what to update with 2.9 update-PLAZA

They updated the texture file format for Atlantis and the new Expansion, this happens on the 2.10 version, I fixed it along with the new DLC support in a merge pending of approval, you can test it yourself if you have the official 3.8.0 here:
https://github.com/Ninakoru/TQVaultAE/releases/tag/3.8.0-TEST

i can't open this ;(((
On Monday, December 6, 2021, 07:18:11 PM GMT+1, Alejandro<EMAIL_ADDRESS>wrote:

They updated the texture file format for Atlantis and the new Expansion, this happens on the 2.10 version, I fixed it along with the new DLC support in a merge pending of approval, you can test it yourself if you have the official 3.8.0 here:
https://github.com/Ninakoru/TQVaultAE/releases/tag/3.8.0-TEST
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

Is a github public page, not sure what are you troubling with, the download is a standard ZIP.

Ninakoru, thank you! Confirmed this fixes the Atlantis bug! That was driving me nuts. Anyone else, just download ZIP provided and overwrite existing files (this is NOT a standalone installation; requires TQVaultAE already installed).

Good to know, I updated the build to also allow preview of characters with the new class (Neidan):
https://github.com/Ninakoru/TQVaultAE/releases/tag/3.8.0-TEST2

Please don't use the release on the previous post, use the latest official instead.
@EtienneLamoureux I think you can close this one too.

Please don't use the release on the previous post, use the latest official instead.
@EtienneLamoureux I think you can close this one too.


Trojan?

VirusTotal Report
It seems that lots of antivirus software are identifying this as a trojan.

Probably has something to do with the fact that its pulling things from registry keys that most programs would have no need to access
Would consider this a false positive, I will look into this if I find the time but I can assure you the program is 100% safe, and if you don't trust it you can take a look at the source yourself. Feel free to reopen this ticket if you have any other questions though

update: someone who previously ran a triage on it and submitted a negative review reran it and found that the program making registry activity was actually another process. some vendors still flag it as malicious, that has not changed, but at least this human reviewer can verify that it is safe: https://tria.ge/240603-mxp1gadb99

Probably has something to do with the fact that its pulling things from registry keys that most programs would have no need to access

What your app actually does barely changes the detection counts. The only real solutions are either individually mailing each AV vendor every single release, or just giving up and buying a code signing certificate.

Probably has something to do with the fact that its pulling things from registry keys that most programs would have no need to access

What your app actually does barely changes the detection counts. The only real solutions are either individually mailing each AV vendor every single release, or just giving up and buying a code signing certificate.

I have looked into a certificate, can't promise anything but its a possibility