Synched fork merge

Synched from master and resubmitted pull request
Updates
nginx for performance and security improvements
uwsgi
postgres 9.5. checkpoint_segments option no longer used
python
Edits
toggled vpc for postgres config
New Capabilities
security DH params
papertrail TLS
syslog for all supervisor configs stdout and stderr
postgis
Disabled volumes for python and postgres as these are based containers and extended containers are not able to commit. The volumes can instead be added at runtime or if necessary they can be defined at the child container.
new libsodium container
nginx syslog for access and error log
base container
Travis build scripts for automated build on commit

This was incorporated into the aws-deploys branch, which is merged into master in PR #8.


Add "Active Pools" filter

As we have more pools, it gets to be more useful for users to have a quick way to only see the pools where they have funds deposited.
This could be a filter, a tab, or anything

Done


Make request conform to JSON API specification

Requests must containt payload under a data key in particular.

Need to discuss this further.


Handle new VAR syntax

Next Robot Framework release may bring new variable syntax (in place of Set Variable). We will need to update several rules (especially those checking the variable scope).
Refer to https://github.com/robotframework/robotframework/issues/3761

This issues splits into two:

Update existing rules to handle VAR
Add new rule(s) to warn on use of Set Local/Test/Task/Suite/Global Variable

Since VAR is additional syntax, it's not counted as keyword call for test/keyword call counts rules:
Test case 'Overwrite reserved with VAR' has too few keywords inside (0/1) (too-few-calls-in-test-case)
We should support count it as keyword call in such case.

Also need to updated rule that checks variable definition for missing value. Following code is accepted:
VAR    ${scalar}
Log    ${scalar}  # empty string
VAR    @{list}
Log    ${list}  # empty list

We should suggest using explicit values (${EMPTY}, @{EMPTY}). Though I'm not sure since VAR  ${scalar} looks compact

And still not sure about suggesting to replace Create List / Create Dictionary with VAR. But maybe it makes sense and makes code cleaner?
Create List    ${list}    value1    value2
VAR   @{list}    value1    value2

And still not sure about suggesting to replace Create List / Create Dictionary with VAR. But maybe it makes sense and makes code cleaner?
Create List    ${list}    value1    value2
VAR   @{list}    value1    value2

I will introduce two new rules:
replace-set-variable-with-var (or similiar name) - it can be replaced with deprecated-statement in the future
replace-create-with-var (or similiar name) - for Create List/Dictionary

Rules that still need VAR support: ossible-variable-overwriting, inconsistent-variable-name

Also check how Catenate could be replaced with VAR and if it does make sense to add rule for it (replace-catenate-with-var)

All tasks are resolved. The only thing left is handling new parsing errors (such as invalid variable name in VAR) but I'm leaving it for now as we have other task open for revisiting all possible parsing-errors .


Fix issue3163

Coverage remained the same at 54.828% when pulling affcfdacbe8c5e81425f02b5db0b9835fef1308d on wy65701436:fix-issue3163 into f4df7ccec7836a03173f72f18def3cfdb5f1ff80 on vmware:release-1.2.0.

Coverage increased (+0.008%) to 54.837% when pulling 98e2563a5f9d178b821662ddede3a824ed3df581 on wy65701436:fix-issue3163 into f4df7ccec7836a03173f72f18def3cfdb5f1ff80 on vmware:release-1.2.0.

Coverage decreased (-0.02%) to 54.811% when pulling 98f4d9ddd5c86c18daba88a082e80af2ddf5e351 on wy65701436:fix-issue3163 into f4df7ccec7836a03173f72f18def3cfdb5f1ff80 on vmware:release-1.2.0.

Coverage increased (+0.008%) to 54.837% when pulling adbb45842734cbf23a1fcab87292c16e83223d31 on wy65701436:fix-issue3163 into f4df7ccec7836a03173f72f18def3cfdb5f1ff80 on vmware:release-1.2.0.

Coverage decreased (-0.008%) to 54.82% when pulling adbb45842734cbf23a1fcab87292c16e83223d31 on wy65701436:fix-issue3163 into f4df7ccec7836a03173f72f18def3cfdb5f1ff80 on vmware:release-1.2.0.


Problem with statistics

Today the statistics is overwriting to 0 after every game
Roofkiller, did you disconnect us from statistics server?
Community is shocked
Its not intresting to play without statistics.
Please fix it.

Seems to be a bug with memory managment, I restarted the server, should be fixed. (My PC is broken I am not able to fix the bug, I can only restart the server right now)

Ty
It was fixed
P.S. Can we hope for your return to bug fixing after solving the problem with your PC?

too many crash after 7,04 patch


OpenML

Integration with OpenML API. It is possible to pull datasets from OpenML.org from MLJBase.
For example, the iris dataset has the ID 61 in OpenML.org (https://www.openml.org/d/61). The OpenML.load(61) function will return a Vector of NamedTuples that can be transformed with a DataFrame or other tabular formats.
ntp = OpenML.load(61)
df = DataFrame(ntp)

did you mean to close this?

yes, I did a new PR with a few changed (removed) lines.


[My habits] Habit  isn't automatically transferred to the section of 'Acquired habits' from 'Habits in progress'  if it has 100% progress

Environment:** OS Windows 10, Mac OS, browsers: Google Chrome, Mozilla Firefox.
Reproducible: always.
Build found:29.01.2021
E.g. "commit 147fa44"
Preconditions
Precondition:

Registered User is logged in;
User has at least one 'Habits in progress', where (duration=habit_streak-1).

Steps to reproduce

Go to https://ita-social-projects.github.io/GreenCityClient/#/
Go to 'My Habits' page.
Click "Mark as done" switcher of 'Habits in progress', where duration=habit_streak-1

Actual result
1.Habit  isn't automatically transferred to the section of 'Acquired habits' from 'Habits in progress'  if it has 100% progress
2."Habit_streak" and 'Duration' is represented on card of 'Habits in progress'.
3. 'Mark as done' switcher is is represented on card of 'Habits in progress'
4. 'Mark as done' label is s represented on card of 'Habits in progress'
Expected result
1.Habbit is automatically transferred to the section of 'Acquired habits', and not represented in 'Habits in progress'.
Counter of 'Habits progress': -1.Counter of 'Acquired habits': +1
2.'Duration' is represented on card of 'Acquired habits'.
3.Star' icon is represented on card of 'Acquired habits'.
4."Great! You've got a habit!" text is represented on card of 'Acquired habits'.
User story and test case links
E.g.: "User story #1160  https://github.com/ita-social-projects/GreenCity/issues/1160
Test case GC-1816 "
Labels to be added
"Bug",
Priority ("pri: high"),
Severity ("severity:major"),
Type "UI,
Attachments:
Actual result

expected result

pre-condition

Steps to reproduce

Mark as 'Done' any habit on my habits list
Check if it is automatically marked as 'Done' in a pop-up in the calendar
Mark as 'Done' any habit in a pop-up in the calendar
Check if it is automatically marked as 'Done' on my habits list

Actual result:
Habit isn`t marked as done automatically. It is marked as done only after refreshing the page
Expected result:
Habit is marked as done automatically

OksanaRom, this bug was about inprogress --> acquired habit, but not about connection with calendar popup!

Cannot reproduce this bug. The new bug is found #2709

Defect is still presented. Habit isn't automatically transferred to the section of 'Acquired habits' from 'Habits in progress'


Add a mechanism for keeping the IDE up to date

Currently, once you add a connection, it will use that version of the IDE forever.
It would be convenient if you could update the IDE for that connection.  Some ideas:

Before connecting ask "There is a newer version, do you want to update?"
Add an "Update" button next to the IDE version.
Could let the user choose between latest stable and latest EAP, although maybe we automatically choose based on whether the current was stable or EAP?

And as a follow-up, should it show as a new connection so you can still use the old version if you change your mind?  Or should it replace the existing connection?  Should it also delete the old IDE?  And to take that to the extreme, should we always allow only one version of each IDE per workspace?
My thinking: We should allow multiple versions if you explicitly choose different versions through the regular flow (so no change there), but from the recents screen an upgrade should replace the connection being upgraded and should delete the IDE if it is not being used for any other connections (for disk space reasons, mostly).

@code-asher I like your proposal! I feel like we shouldn't automatically choose but maybe always ask the user if they want to update. Agree that unused versions should be deleted.

Implemented in https://github.com/coder/jetbrains-coder/commit/43eb600127de16fd70a2d838dab4932a31164a26


How to use the app.config when running Tests using Visual Studio task in build vNext

Hello,
In our company, we developp in C#, we have an unit test project and there is an app.config into this project to specify the database used (connectionString). Our units tests use this database to perform the tests.
When we running tests using Visual Studio task in build vNext, the app.config doesn't seem to be taken in account : we got this message "Unable to create instance of class "...". Error: System.Data.SqlClient.SqlException: CREATE DATABASE permission denied in database 'master'".
How can we use this app.config for the Visual Studio Test in build vNext ?
Bests regards,
Gilles.

Hi Gilles,
The app.config file should be present next to the built test assemblies. We tested it out with Visual Studio test task and things worked fine.
Thanks
Atin.

Hi Atin,
When you say next to the built test assemblies, it's in the binairies folder ? (In my case "bin\Release).
Because I got my app.config at the root folder of my project but I got the message "Unable to create instance of class "...". Error: System.Data.SqlClient.SqlException: CREATE DATABASE permission denied in database 'master'".
Thanks.

Yes, it should be in the Release folder. You can set the property on the file to always copy to the output folder. Thanks!

This doesn't seem to work when it comes to assembling binding redirects.
I have a test project that requires this in the app.config:
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Collections.Immutable" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

And while that works fine when running locally, it appears that these binding redirects are ignored by the Visual Studio Test task. Setting the app.config to copy to the build output folder doesn't help.

@idg10
Hi Ian,
I tried to reproduce this and found that the assembly redirection is working fine for me. Can you please give us more details on<EMAIL_ADDRESS>(logs)? We will follow up from there.
Thanks

was this resolved? what's the solution?

We did not get any mail. Are you facing the same issue?

resolved.
turned out it was a nuspec issue in separate package

ok, this has come back again. Getting
System.IO.FileLoadException : Could not load file or assembly 'Newtonsoft.Json, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
for anything that tries to create an HttpClient with a JsonMediatTypeFormatter.
System.Net.Http.Fomatting refs v6 of Netwonsoft. But my app.config does the appropriate bingingRedirect. Everything works just fine locally.
But in vsts it seems to ignore the redirects.
Any clues or debugging techniques gratefully received

this exception comes from a test project (nunit3, nunit2 also fails). It is creating a "service client" from another package (written by me) that wraps an HttpClient configured with JsonMediaTypeFormatter.
The test project (and the code it is testing) and the service client package, all have redirects to Newtonsoft.Json v7.0.1
The exception is thrown from within the ctor of the service client. No line numbers are available even though I have ref'd the symbols version of the package.

another project in the same sln works fine. There must be a difference between them. No luck finding the diff yet though

I'm running into a related issue. I have many tasks and a single connection-string file referred to at the top of the configs for each test:
    <?xml version="1.0" encoding="utf-8"?>
    <configuration>
      <configSections>
        <!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 -->
        <section name="entityFramework" type="System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" />
      </configSections>
      <connectionStrings configSource="connectionStrings.config" />
      <startup>
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
      </startup>

Error:
System.Configuration.ConfigurationErrorsException: Unable to open configSource file '.\connectionStrings.config'.

No matter what relative path I give it, I always get the error. It's in the same directory. I've referred to it as both "connectionStrings.config" and ".\connectionStrings.config", as well as pointing to each of the directories above it. I looked in VSTest.ps1 (the PS script behind the task), in order to investigate more about the flow, but it refers to Invoke-VSTest, which isn't seeming defined as clear-text PowerShell logic anywhere on my disk. So, I'm assuming it's defined in an assembly somewhere.
I should mention that I'm running this from a release-process. Since this task doesn't seem to indicate that it is expected to run either only under build mode or release mode, I'm assuming that this is valid.
The task is passing $workingDirectory as a parameter to Invoke-VSTest. This is set to the release staging directory. In this/my case, this is "D:\Agents\A3_work\464b36816". I also tried putting the connection-string file there, but it didn't make a difference.
Anyone?

We're getting a similar error which I think may be related.
One of our test projects tests some code which uses ClaimsPrincipalPermissionAttribute.
When we run the tests locally they work correctly but when we run the tests on the server the test runner complains that the system.identityModel element is missing from the configuration..

Use of ClaimsPrincipalPermission attribute has been attempted and possibly there is no <system.identityModel> configuration section defined

That setting is definitely there in our test projects app.config but presumably that's not the app.config that's being used in the context of the test runner.
How can we get this setting into that context?

@B3nCr Can you try manually executing the test assemblies build generated by Build Task, using vstest console command and see if the execution passes/fails?
Vstest console exe's location would be somthing like: "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe".

I've set the app.config to copy local = true on the test project and it's miraculously fixed all our tests.
This seems like some black magic. What happens if we set more than one projects app.config to copy local = true?

@B3nCr if you set copy local=true for all dlls the app.config will be renamed to dllname.config and will be copied to binaries directory next to dll. It wont be copied as app.config and hence there wont be a conflict.

Generally, only the app.config of the executing assembly will be used. Hence, a test project generally can't use the app.config of the tested project, unless you do something like mentioned above (copy the .config file into the same folder etc.)

Generally, only the app.config of the executing assembly will be used. Hence, a test project generally can't use the app.config of the tested project, unless you do something like mentioned above (copy the .config file into the same folder etc.)

I don't quite get why tested project cannot have app.config as an application does. A test project has every reason as an application has to take into account of an app.config

you can use this code in your app
`
using System;
using System.Collections;
using System.Collections.Generic;
using System.Collections.Specialized;
using System.Configuration;
using System.Text;
using System.Xml.XPath;
using System.IO;
namespace Configuration
{
///
/// Provides an testable ConfigurationManager lite based on System.Configuration.ConfigurationManager
/// using the section.SectionInformation.GetRawXml() member to get sections definition.
/// Try to store add elemnt information in a namevalue collection
///
///
/// var tcm = new TestableConfigurationManager("MyFullname_App.config");
/// var nvcDlF = tcm.GetSection("saveTheWorldSection");
/// Assert.AreEqual(12-5, saveTheWorldSection.Count);
///
public class TestableConfigurationManager
{
public IDictionary Sections = new Dictionary<string, NameValueCollection>();
    /// <summary>
    /// Stores all existing error free processable  @keys @value pairs of add elements from all sections in a configuration file
    /// in namevalue collection according to its section sectionname.
    /// </summary>
    /// <param name="pathToConfigFile">FullPath of a configuration file</param>
    /// <remarks>
    /// - missing propper error handling (what if you have identical keys in a configuration)
    /// - missing namespace handling
    /// - unknown whats happens with appsettings
    /// . feel free to make version 1.1
    /// </remarks>
    public TestableConfigurationManager(string pathToConfigFile)
    {
        //check
        if (!File.Exists(pathToConfigFile))
        {
            throw new ConfigurationErrorsException($"Konfigurationsdatei {pathToConfigFile} nicht vorhanden oder fuer User {Environment.UserName} nicht erreichbar.");
        }

        //read and loop all sections
        ExeConfigurationFileMap customConfig = new ExeConfigurationFileMap
        {
            ExeConfigFilename = pathToConfigFile
        };
        var eSections = ConfigurationManager.OpenMappedExeConfiguration(customConfig, ConfigurationUserLevel.None).Sections.GetEnumerator();
        while (eSections.MoveNext())
        {
            try
            {
                var nvc = new NameValueCollection();
                var section = ((ConfigurationSection)eSections.Current);
                var sectionName = section.SectionInformation.SectionName;
                //reding configuration sections xml
                var csXml = section.SectionInformation.GetRawXml();
                if (!string.IsNullOrWhiteSpace(csXml))
                {
                    var docNav = new XPathDocument(new MemoryStream(Encoding.UTF8.GetBytes(csXml)));
                    var nav = docNav.CreateNavigator();

                    //loop over all add elements in section
                    var addIterator = nav.Select(".//add");
                    while (addIterator.MoveNext())
                    {
                        //pupulate NameValueCollection assuming if there is an key you will have an value also
                        var key = addIterator.Current.SelectSingleNode("@key");
                        if (key != null)
                        {
                            var name = addIterator.Current.SelectSingleNode("@key").Value;
                            var value = addIterator.Current.SelectSingleNode("@value").Value;
                            nvc.Set(name, value);
                        }
                    }
                }
                //store namevalue collection according to sections sectionname
                Sections.Add(sectionName, nvc);
            }
            catch (Exception)
            {
                //todo errorhandling
                //throw;
            }
        }
    }

    /// <summary>
    /// Gets Section like System.Configuration.ConfigurationManager would do in an application for its app.config
    /// </summary>
    /// <param name="sectionName">Section namne of the section</param>
    /// <returns></returns>
    public NameValueCollection GetSection(string sectionName)
    {
        return ((NameValueCollection)Sections[sectionName]);
    }
}

}
`


R0.10

I need it for test

Can one of the admins verify this patch?

This has conflicts, and I don't think we're supporting r0.10 anymore -- consider making these changes to your own fork instead!  Thanks!


Properly indented docstrings result in incorrectly rendered Markdown in openapi docs

Describe the bug
A properly formatted docstring is indented to match the indentation of the function or method. The markdown rendering that is passed into the API docs seems to be interpreting these indentations in such a way that the markdown is not properly formatted unless the docstring is out-dented to an unconventional flush left.
To Reproduce
I have the following function definition with docstring:
async def content_classifier_model_details(model_name:str) -> ModelClassDetailsResponse:
    """Retrieve the variants and versions of a group of content classifier models for a
    given named classification.

    Models can be specified at the `classify` endpoint as follows:

    - **Class name only** (`model_name`). E.g. `climate_action`. Will utilize the
    default model as indicated by the default flag in the model details. _This format
    is provided primarily for development and exploratory purposes._ In production
    code, it is recommended that the variant be specified.
    - **Class with variant** (`name-variant`). E.g. `climate_action-nx`. Will utilize
      the current version of the specified variant as indicated by the `current` field
      in the model details.
    - **Full versioned identifier** (`name-variant-version`). E.g. `climate_action-nx-1` is
      useful for pinning your application to a specific historical version.
    """

The result is shown in the screenshot titled incorrect-markdown-render.png. The expected rendering is shown in correct-markdown-render.png which can be achieved by the following unconventional docstring format:
async def content_classifier_model_details(model_name:str) -> ModelClassDetailsResponse:
    """Retrieve the variants and versions of a group of content classifier models for a
given named classification.

Models can be specified at the `classify` endpoint as follows:

- **Class name only** (`model_name`). E.g. `climate_action`. Will utilize the
default model as indicated by the default flag in the model details. _This format
is provided primarily for development and exploratory purposes._ In production
code, it is recommended that the variant be specified.
- **Class with variant** (`name-variant`). E.g. `climate_action-nx`. Will utilize
  the current version of the specified variant as indicated by the `current` field
  in the model details.
- **Full versioned identifier** (`name-variant-version`). E.g. `climate_action-nx-1` is
  useful for pinning your application to a specific historical version.
"""

incorrect-markdown-render

correct-markdown-render
(achieved via unconventional docstring out-denting)

Oh, I encountered this too earlier but forgot to create an issue and post a fix.
Will do that in 15 minutes


chore: update lit to 3.0

Known issues

[ ] @open-wc/lit-helpers still has a dependency on lit 2.0 which causes the "Multiple version of lit..." warning

We're currently processing your upload.  This comment will be updated when the results are available.

LGTM. can we not remove this.requestUpdate in setters now? -> https://lit.dev/blog/2023-10-10-lit-3.0/

We now call requestUpdate() automatically for @Property and @State decorated accessors where previously that was the setter's responsibility.

I thought that we would need to do that once we started using standard decorators but you might have a point. I might have misinterpreted it.
We also need to move the @property and @state decorators from the getters to the setters.
I'll test if it's true that the 'request update' is called automatically now


Adding documentation for adding toolbar buttons

Is your feature request related to a problem? Please describe.
Adding custom toolbar buttons is relatively easy, but not described in the YARL documentation website (that I could find)
Describe the solution you'd like
On the customization page, between Styling and Custom Icons, add a new section called Adding Toolbar Buttons:
To add a button, add a JSX element to the buttons property of the toolbar prop. Be sure to add the string "close" if you want to keep the close button. If you have included any plugins, those buttons will be prepended to the front of the buttons list in the order of the Plugins prop array.
If you need to access information about the current slide when your button is clicked, see the Toolbar Buttons section of the Advanced API documentation
<Lightbox
  toolbar={{
    buttons: [
      <button type="button" className="yarl__button">
        hi
      </button>,
      "close",
    ],
  }}
</Lightbox>

(I'd do a PR myself, but I couldn't find the source of the documentation in Github)
Describe alternatives you've considered
No response
Additional context
No response

Great suggestion! I've added toolbar customization section to the documentation.
https://yet-another-react-lightbox.com/customization#AddingToolbarButtons
P.S. I'll work on extracting documentation into this repo. Please check back soon.


Surface the documentation for civis.find and civis.find_one

The docstrings for civis.find and civis.find_one have been recently added at #224, but the two functions aren't explicitly mentioned anywhere in the current Sphinx documentation. Currently there isn't a page dedicated to utility functions of this sort. Given that their major use case is to filter civis.response.Response objects, how about adding a section like "Utility Functions" or something in responses.rst?
@stephen-hoover @keithing

I agree that surfacing that documentation would be nice. It doesn't look like responses.rst makes it into the built documentation, though. It's also pretty empty. Maybe we could add a note about find and find_one in user_guide.rst under "Working Directly with the Client"?

It doesn't look like responses.rst makes it into the built documentation, though.

I thought this page was the result of responses.rst?

 My apologies. I do still think that these functions could make more sense in the user_guide.rst file, but they might also work in responses.rst if that section gets some explanatory text..

Looking more closely, the user_guide.rst seems to be the helper-y kind for what I was getting at above, and it's more front and center than the more embedded/hidden page of responses.rst. So adding a note about find and find_one in user_guide.rst sounds like a good idea to me. Though in terms of style, this page is written mostly in prose, and so adding also in this page the Sphinx-ified docstrings (which I'd like to see in the docs somewhere) of find and find_one would look less than ideal. Maybe we should have a brief note (in prose) in user_guide.rst, with the hyperlinks pointing to docstrings shown in responses.rst? I'll make a PR and see how things go.


BucketIntegrationTest.RpoPatch fails intermittently

This may be related to all the recent changes.  I could not repro on the first attempt, but it has happened at least in one CI and a couple of PR builds.  It seems to happen with the RestClient, but I am not certain of that bit.

GCB: https://console.cloud.google.com/cloud-build/builds;region=us-east1/9b2b845c-2790-4d56-818a-8737573a9b98;tab=detail?project=cloud-cpp-testing-resources
Raw: https://storage.googleapis.com/cloud-cpp-community-publiclogs/logs/google-cloud-cpp/main/31752f679ce790157e9ef195483ff2a365355980/fedora-36-cmake-gcs-rest/log-9b2b845c-2790-4d56-818a-8737573a9b98.txt

[ RUN      ] BucketIntegrationTest.RpoPatch
/workspace/google/cloud/storage/tests/bucket_integration_test.cc:482: Failure
Value of: insert_meta
Expected: code is equal to OK and message is anything
  Actual: 904-byte object <B0-91 C9-01 00-00 00-00 00-FF FF-FF FF-FF FF-FF 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 BF-4C 2E-73 1D-7F 00-00 80-A4 C7-01 00-00 00-00 E0-B1 2A-73 1D-7F 00-00 13-E3 76-72 1D-7F 00-00 ... 01-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 80-3F 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00 20-00 00-00 00-00 00-00 00-00 00-00 00-00 00-00>, whose status is INVALID_ARGUMENT: Permanent error in CreateBucket: Received HTTP status code: 400, with a code that isn't equal to OK, but a message that is anything

Up to 200 repeats on my workstation, no repro.  I may need to move the test to a GCE instance.

I was not able to repro, and it is not repeating.  I have asked the GCS team to check their side, but there is nothing actionable at this time.  Not planning to continue work on this until it repeats.

It has been 90d without repeats, closing.


Can't view uploaded files / images

Is this a known issue? I can see the files but when I try to view them in web I get a 404 on a path that doesn't look like it exists

This doesn't happen in my environment neither in the test one,
can you check if the file has been uploaded through the filesystem?

Yea, they are uploaded

I was with the same error here I ran php artisan storage:link and it worked


Transfer Learning

I was reviewing one of the ML.NET Transfer Learning tutorials and came across this particular paragraph.
Create a struct for Inception model parameters
The Inception model has several parameters you need to pass in. Create a struct to map the parameter values to friendly names with the following code, just after the Main() method:
How does someone know where to get the parameters required for the Model?

Hi @JamesCann
Thank you for your question. The parameters are specific to each model. In many cases, it's enough to know the height and width of the images used to train the model so when you try to use the model to classify / predict your data, you know the dimensions the model expects. In the case of this tutorial, the images were 224 x 224, which is what they're being resized to in the pipeline by the ResizeImages transform. With regards to the other parameters (scale, mean, channellast) they too are somewhat model specific. In the ExtractPixels transform, those parameters specify the order in which to get the pixels from an image. An pixel (color) can be represented by an array of values ranging from 0-255 corresponding to RGB. However, depending on how the image is stored, that representation can be in a specific order RBG,GBR,etc. Depending on the framework, that arrangement may differ. With regards to TensorFlow models, the typical arrangement is channel-last. Finally, the scaling / mean are used to normalize images. Because you're working with many values for each image (224 x 224 x 3 -> 150,528 values) each ranging from 0-255 it can help to normalize these values to fall between 0-1 to make it easier to compute and have all of the values in a more uniform range. That's where the mean and scale come in to normalize the pixel values as they're being extracted. In the tutorial, the scaling / channel last parameters were included to show some of the options available when consuming a TensorFlow model. However, as I mentioned in most cases, it is often enough to just know the height / width of an image.


Support for destruction of group

Currently only supports creating a new group and getting an existing group, is it possible to provide a way to destroy an existing group?

Sorry, I submitted to the wrong project, close it.


Unfreeze SimpleCov::VERSION

Older versions of rubygems choke on an immutable version string.
I wasn't able to actually get rubocop to complain about the mutable constant so I couldn't verify that the second commit actually does anything.

Thanks!


MicStreamDemo.cs demo example doesn't exist

Hi,
looking through the front page of https://github.com/microsoft/MixedRealityToolkit it mentiones an example demo on this repo https://github.com/microsoft/MixedRealityToolkit-Unity/blob/master/Assets/HoloToolkit/Input/Tests/Scripts/MicStreamDemo.cs but that page doesn't exist; is the demo/scripts still available?

That demo can be found in the old HoloToolkit branches: https://github.com/microsoft/MixedRealityToolkit-Unity/blob/htk_release/Assets/HoloToolkit-Examples/Input/Scripts/MicStreamDemo.cs

I just updated the README on the other site and fixed this up there, closing this out for now.


Win auth concurrency fix

Doneness:

[x] Build is okay - I made sure that this change is building successfully.
[x] No Bugs - I made sure that this change is working properly as expected. It doesn't have any bugs that you are aware of.
[x] Branching - If this is not a hotfix, I am making this request against develop branch

PR resolves #394 and also fixes a recently introduced issue with body consumption for responses during ReRequests.

:white_check_mark: Build Titanium-Web-Proxy 3.0.380 completed (commit https://github.com/justcoding121/Titanium-Web-Proxy/commit/9ec61a4c4c by @)


Install problem

Your recent change to the package json, specifically the postinstall where you're trying to scrape stats is causing install failures
"postinstall": "TID=UA-265870-43 node scripts/install-stats.js"

@Auxolust just published a new version that shouldn't allow that to cause install issues


[Dependency Issue]: Git.Git as dependency can't be found by main installer after it's installed

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Other
Brief description of your issue
This installer has Git as a dependency. It finds Git in the Windows Path during install to register itself. But the Windows Path in most Command Prompt and PowerShell windows appears to only update at window launch. One window must be opened for the dependency install, and then another window opened for the main package install. Observed in

https://github.com/microsoft/winget-pkgs/pull/90133

Similar behavior was observed in this PR - the installer completed, but validation failed as it used the same PowerShell window, and thus couldn't find Git in the Windows Path.

https://github.com/microsoft/winget-pkgs/pull/90517

Steps to reproduce
For 90133 - On new system, modify the package's manifest to have Git.Git as a dependency, then install in a VM.
Actual behavior
The installer will error "Could not find Git; can not register Git LFS."
Expected behavior
Winget could help the client window to update its local Windows Path variable from the registry, so subsequent installers could install successfully, and programs run from the same window could find Git to execute successfully.
Environment
Windows Package Manager (Preview) v1.4.3132-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1288
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.3132.0

Screenshots and Logs
No response

Related to:

https://github.com/microsoft/winget-cli/issues/549


MAHOUT-1828: Change the access of blas method in sparkbindings

+1

Merged to branch - 'flink-binding'


⚠ Community has degraded performance

In b4ebf65, Community (https://community.wrk.com/health) experienced degraded performance:

HTTP code: 200
Response time: 194 ms

Resolved: Community performance has improved in 81db61d.


Horns GUI update

kinda new design
less text
GUI to bind horns

While you're at it. Can you also do the following changes?

Change window title to 'GreenCoins Shop'
Remove the 'Welcome to the Green-Coins shop!' text.
Change 'Greencoins: XXX' to 'XXX GreenCoins', align it to the right and make it more visible. Maybe a white 1px border/stroke around it?

Done. I tried with white shadow, looks very ugly. I've stopped at a small black shadow


Clang 14.x ornery about std::experimental::coroutine_traits

Environment:

Debian Bookworm x64
Qt 6.6.1
Android NDK 25.1.8937393
Clang v14.0.6 AARCH64 (provided in NDK)

While compiling for Android, we get:
support for std::experimental::coroutine_traits will be removed in LLVM 15; use std::coroutine_traits instead

Which promotes from a warning to an error.  Workaround is to specify in CMakeLists.txt
if(CMAKE_CXX_COMPILER_ID STREQUAL "Clang")
    add_compile_options(-Wno-error=deprecated-experimental-coroutine)
endif()

Which gets us going, but presumably Clang 15+ that will fail.  However, I see PRs in this repo which are using Clang 17.  So who knows.  All I know is my Android compile failed without the workaround

std::experimental isn't used if the standard library defines __cpp_lib_coroutine, thus I suspect something is fishy with clang/libc++ in Android NDK...I downloaded the Android NDK 25 (I downloaded 25.2.9519653, which is slightly newer than yours, but that shouldn't matter), and searching the NDK I can only find the <experimental/coroutine> header:
❯ cd android-ndk-r25c
❯ find . -name "coroutine"
./toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/experimental/coroutine
./sources/cxx-stl/llvm-libc++/include/experimental/coroutine

The reason why is most likely because the Android NDK ships clang 14, but the libc++ standard library is older:
❯ cat toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/include/c++/v1/__libcpp_version
11000

libc++ 11 indeed does not have the <coroutines> include header, only <experimental/coroutines>, so QCoro falls back to including that, which triggers the warning from clang.
I'll add the compile option to QCoro when building on Android....

Btw I also checked NDK 26, which ships libc++ 17 which does have full coroutine support, so QCoro should work there out of the box without any changes.

Your attention to detail is remarkable.  Thank you!


templates/base: Add self-hosted plausible analytics

Don't merge until the ethics of this are reviewed in a team meeting,
but this is ready to go.

I checked team meeting minutes and it seems a conclusion was not yet reached so parking this a bit until we discuss this. Please correct me if you have concluded otherwise during a meeting.

Before we merge this we should add an entry in our privacy note on what we collect and how we will use this data.


23

Description

Describe your pull request here

Checklist
5

[x] Does npm test pass with this change (including linting)?
[x] Is the new or changed code fully tested?
[x] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

23

23sfda


Fix AdmissionReview uid quoted string

Without this change, the JSON-encoded AdmissionReview response object
contains a uid string with escaped double quotes. When used as a webhook
in Kubernetes, the API server will reject a valid pod creation request
with a log message like this:
failed calling webhook "rule-0.chimera.admission.rule": expected response.uid="44286a79-e64e-45f8-b66a-7ef4342e856f", got ""44286a79-e64e-45f8-b66a-7ef4342e856f""
This is because the uid is a serde_json::Value object[1]. It needs to be
converted to a &str with as_str and then to a String with to_string() in
order to avoid the extra quotes.
[1] https://docs.serde.rs/serde_json/#operating-on-untyped-json-values

Thanks for the fix, I noticed that and I was pretty sure this would have broken the API server, but I didn't test that :)

Thanks for the fix, I noticed that and I was pretty sure this would have broken the API server, but I didn't test that :)


Bracket handling

This PR improves Concept label handling in two ways:

When constructing the sub NFA for a given label raises an exception a warning is printed. Furthermore the sub automata will not be considered when converting to DFA.
Brackets will be escaped when handling labels.

I tested this both with YSO (the version before the bracket issue was fixed) and the NALT snapshot that had caused problems earlier. Now the vocabulary parsing doesn't fail anymore, so the fix appears to work!

thank you @osma .


Lack of backward compatibility for verify-attestation

Description

Images attested with cosign v1.4.1 (for full output from cosign version refer to the Version section) cannot be verified with verify attestation due to the lack of payloadType field compatibility when verified with cosign 1.9.0.
To reproduce the problem (using cosign 1.4.1):
grype -ojson <image>:<tag> > test.cve.result.json
cosign attest --predicate test.cve.result.json --key <key> <image>:<tag>

syft -ospdx <image>:<tag> > test.sbom.spdx
cosign attest --predicate test.sbom.spdx --type spdx --key <key> <image>:<tag>

Then using the cosign 1.9.0:
cosign  verify-attestation --key <key> <image>:<tag>

Output:
Error: no matching attestations:
invalid payloadType https://spdx.dev/Document on envelope. Expected application/vnd.in-toto+json
 invalid payloadType cosign.sigstore.dev/attestation/v1 on envelope. Expected application/vnd.in-toto+json
main.go:52: error during command execution: no matching attestations:
invalid payloadType https://spdx.dev/Document on envelope. Expected application/vnd.in-toto+json
 invalid payloadType cosign.sigstore.dev/attestation/v1 on envelope. Expected application/vnd.in-toto+json

Expected output:
Cosign should return two attestations.
Version

attesting version:
GitVersion:    v1.4.1
GitCommit:     934567a4c606cf59e6ab17af889b4db3ee0a3f0b
GitTreeState:  clean
BuildDate:     '2021-12-10T16:54:56Z'
GoVersion:     go1.17.5
Compiler:      gc
Platform:      darwin/amd64

verifying version:
GitVersion:    1.9.0
GitCommit:     a4cb262dc3d45a283a6a7513bb767a38a2d3f448
GitTreeState:  "clean"
BuildDate:     2022-06-03T13:47:07Z
GoVersion:     go1.18.3
Compiler:      gc
Platform:      darwin/amd64

@sfzylad Thanks for the issue. I have a couple of questions. Is there any reason to use 1.4.1 ? Why don't you use the same cosign version for the attestation and verification ?

@hectorj2f I've encountered this problem trying to verify the attestation that's been created some time ago when version 1.4.1 was the most recent or close to the most recent. The described problem started just after updating.

Hey,
Sorry about this one. We were incorrectly storing attestations before, and confusing the DSSE envelope with the in-toto attestation in a few areas. The bug fix was unfortunately backwards incompatible.

Not much we can do here now, apologies for not remembering this would break at the time.


cannot connect to X server

when i run the visualization.py in the program, it shows me cannot connect to X server. if i disable GUI, program tells me there is a invad sample rate

Can you explain your issue in a little more detail? A screenshot would also help.
What's your setup looking like and what platform are you using?

most likely this means you have the GUI set to to true, and don't have xhost, so just disable the gui in the config.py

@karthushuang Let me know if there's anything more you need help with, for now, I'm closing this.


Method of programmatically determining when values have been persisted back to Neo4J

I am using NodeJS to trigger the pagerank algorithm. I understand once I end up with a ton of nodes and edges that it could take some time, but I wanted to have an automated way of determining when that process is complete so I can start additional logic that depends on the Neo4J nodes being updated with the values calculated by Mazerunner.
You had mentioned that I could check the log file. I think I can make that work using Node, to simply tail that file and scan the output.
Is there another way? Perhaps the original http call to trigger the job could return a jobId and then I can poll another http endpoint with that jobId for status/progress?  I'm probably misusing the project anyway :-), but figured I would ask.
Here is my code:
http.get(CONF.neo4J.paths.pageRank, function(response) {

            var body = '';

            response.on('data', function(d) {
                body += d;
            });

            response.on('end', function() {

                var parsed = JSON.parse(body);
                if(parsed.result && parsed.result === "success") {

                    jobTaskInstance.complete({success:'awesome'});

                } else {

                    jobTaskInstance.error('Unknown error running PageRank');
                }
            });

        }).on('error', function(e) {
            jobTaskInstance.error(e.message);
        });

So maybe the response body could look like?
{"result":"success", "jobId":1234}

Love this project!!!

Hi @gitsome, thanks for the issue. Sorry it's taken this long to get back to you on this thread. I think it makes sense to do a resource-based REST API that allows you to do simple job management. Thanks for putting that example together, it makes a lot of sense.
I've been putting off job management because there are so many great tools out there that do things like job management and scheduling.
I guess the question for me at this point is whether or not a job scheduler should be the responsibility of a new microservice that Neo4j integrates with or if it should be a part of the Mazerunner extension. That leads to another question which is whether or not Mazerunner should become a platform or continue to be maintained as a simple tool dedicated to solving a well defined problem.
Open source is hard. :)
Should we make this thing a full framework and potentially a cloud-native platform, or should we keep it a simple tool?

No worries, thanks for taking a look at this. I have noticed you have been a busy man these days! Seems you are mixed up in some exciting things (all of which I'm trying to keep up with).
I wouldn't put too much emphasis on my opinions, I have mostly front-end experience, but from my perspective it seems this should continue to be a simple tool. That is how I am using it, however, I do need to know when this tool has completed it's task.   So if I simply need to monitor logs, then no problem, perhaps just highlighting documentation on how to do that would be sufficient?
Regardless thanks again for this great work!  Providing these types of tools really has enhanced my own projects!


Numbro function do not work in external vite app in published @daohaus/common-utilities package

This is the error I'm seeing:
https://github.com/BenjaminVanRyseghem/numbro/issues/403
Not sure if it's with the build or in the vite app ts config.

@skuhlmann has this already been fixed?


Release 0.4.1

Ⅰ. Describe what this PR does
Release koordlet can not access kubelet bugfix.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews

Hi, please add commit 282342cda18c9b035bd110a0702bd89dffaebb95 into 0.4.1 as well.


using fixture with reflexive relation throws model.hasInverseFor is not a function

I have an article model that is reflexive to itself through a related_articles fields. In order to have a finer control of the context in my tests, I want to use fixture.
model
// app/models/article.js
export default Model.extend({
  featured: attr('boolean'),
  related_articles: hasMany('article', { inverse: null })
});

fixture
// mirage/fixtures/articles.js
  export default [{
    id: 2,
    featured: true,
    related_articles: [1, 2]
  }];

scenario
// mirage/scenarios/default.js
export default function(server) {
  server.createList('category', 10);
  server.loadFixtures('articles');
}

Test
test('has related-articles block', function(assert) {
  authenticate(this.application);
  server.loadFixtures('articles');

  visit('/app/articles/2');
  andThen(function() {
    let relatedArticlesBlock = document.querySelectorAll('.related-articles');
    assert.ok(relatedArticlesBlock.length);
  });
});

Error

Mirage: Your GET handler for the url /api/v2/employee/articles/2 threw an error: model.hasInverseFor is not a function

Question
There is no related articles in the related_articles key returned by mirage. What's the matter?

Hello Edouardo, i am having this exact same issue.  Have you found an answer?  Thanks in advance for your help.

Nope, went back to use factories and the following syntax to create object in a more controlled way:
// mirage/scenarios/default.js
server.createList('article', 10, { pinned: true });

interesting...  that was my plan b also.  thank you for your response.

try use include property in serializer:
// serializers/article.js
import { RestSerializer } from 'ember-cli-mirage';

export default RestSerializer.extend({
  include: ['related_articles']
});

// scenarios/default.js
let relatedArticles = server.createList('relatedArticle', 10);
let articles = server.create('articles', [ relatedArticles ]);

Tell me if you solve the problem.
see more options:
http://www.ember-cli-mirage.com/docs/v0.4.x/serializers/#serializeids

We fixed this in a recent release, could you try 0.4.4 and see if it fixes your bug?

Closing this as the original issue is quite old, but feel free to ping here and I can reopen if it's still an issue!

I had this error because I was defining relationships in my mirage factories, when I didn't have to since I'm using JSONAPI and the models were created automatically by mirage.
So if you're using JSONAPI with Ember, no need to setup relationships in your mirage factories


fix: update tests to account for a sqlserver fix in prisma/prisma-engines#5056

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


cloud-init: 23.3.3 -> 23.4

Description of changes

The automatic update from https://github.com/NixOS/nixpkgs/pull/273497 fails tests because of this upstream change: https://github.com/canonical/cloud-init/commit/0044c83512d915137ccc79553b57c0250b0f474f
The nixos support patch for cloud-init had to be updated accordingly.
nixosTests.cloud-init has also been updated to make it fail faster.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 273707 run on x86_64-linux 1

2 packages built:

cloud-init
cloud-init.dist

Result of nixpkgs-review pr 273707 run on x86_64-linux 1

2 packages blacklisted:

nixos-install-tools
tests.nixos-functions.nixos-test

2 packages built:

cloud-init
cloud-init.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3267

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1392


[Regression] Avoid showing a black canvas during zooming with a drawingDelay set (PR 15812 follow-up)

After the changes in PR #15812 we'll now intermittently display completely black canvases during zooming. To reproduce this, try switching to wrapped-scrolling and zoom in/out very quickly using either the mouse-wheel or pinching.

/botio integrationtest

/botio-linux preview


which model is the basemodel (Embedding + MLP)

Can you please suggest which model is closest to base model for CTR prediction, i.e. Embedding + MLP?
Thanks.

from deepctr.models import WDL


How to work with next.js via dopio

I have react project build on Next.js and i want to add my site in my custom app

https://github.com/The-Commit-Company/frappe-react-sdk/issues/41

Since, NextJS is a standalone framework, it needs to run separately in most cases. But you can use frappe-js-sdk to talk to your Frappe backend from your NextJS server side code.


"Anonymous Variable" false positive

code like
    /**
     * @param MethodCall $node
     *
     * @return array<string|RuleError>
     */
    public function process(Node $node, Scope $scope): array
    {
        if (!$node->name instanceof Node\Identifier) {
            return [];
        }

        $type = $scope->getType($node->var);
        if (!$type instanceof TypeWithClassName) {
            return [];
        }

        $errors = [];
        foreach ($this->forbiddenMethods as $forbiddenMethod => $errorMsg) {
            list($className, $methodName) = explode('::', $forbiddenMethod);

            if (!(new ObjectType($className))->isSuperTypeOf($type)->yes()) {
                continue;
            }

            if ($node->name->toString() !== $methodName) {
                continue;
            }

            $errors[] = RuleErrorBuilder::message(sprintf(self::ERROR_MESSAGE, $className.'::'.$methodName, $errorMsg))->build();
        }

        return $errors;
    }

errors with a "Anonymous varible" error. I guess the problem is the "inline-new" construction

arghs.. the problem cause was that the use PHPStan\Type\ObjectType; statement was missing

:+1:


refactor: styling component structure

#416

Please add screenshot of the changes or a demo video

Created styles folder and specific css files for different components

Thank you for your valuable contribution :)


Current gerbers don't have default dimensions

When uploading the zipped PCB gerbers from latest master to JLCPCB the dimensions aren't automatically filled in:

If I switch to tag 1.6 and upload those gerbers it fills them in:

Not sure if the dimensions stayed the same between the versions so I figured I'd raise it here.
I'd open a PR but I have no idea how to use KiCad. I'll download it and see if I can figure it out but if you beat me to it I wouldn't be mad either :)

This appears to be an issue with the JLCPCB gerber loader, if the gerbers take too long to process for whatever reason then it cannot determine the size of the PCB.
I've tried exporting the gerbers with different settings but nothing I've tried appears to "fix" the issue.
Gerbers themselves only contain the shapes, JLCPCB determines the PCB size from the shapes in the outline layer within the gerber.
Perhaps an update to the documentation specifying this and the PCB dimensions to use would be the best solution until JLCPCB fix their form.

Thanks for the quick response. I was about to start a PR and saw that you beat me to it, much appreciated.


2827 Incorrect information for System.Net.Dns

Updating info about local host IP addresses returned by the Dns class
Summary
The Dns class can be used to return the IP addresses of the local host, by passing an empty string. The addresses returned are IPv4 and IPv6, so updating the topic to make this clear, and removing obsolete reference to WS2003 being an exception (which it is not).
Fixes #2827

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

/cc @pedro-w who opened the issue


Add crossOrigin option

For loading the viewer/content across domains,
it would be helpful to be able to set the crossOrigin for the image requests.
Failed to execute 'texImage2D' on 'WebGLRenderingContext': The cross-origin image

The regression was introduced a week and a half ago when I refactored the multires texture loading; it should be fixed now.

Thanks for the fast response.
There is a different error now:
Image from origin 'http://example.com' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://example2.com' is therefore not allowed access.

The server isn't configured to allow CORS, which is needed to load the images via JavaScript from a page on a different domain.


Can't connect with FTP

Greetings. I am not a networking guy so please bear with me.
I am trying to connect to a server using SFTP. Specifically, I am using WinSCP on my laptop running Windows with this software providing my internet access.
I have no issues connecting to the server with other connections.  I have read it might be a NAT issue or something that could be resolved with IP tables? (https://superuser.com/questions/456406/how-can-i-access-my-desktop-computer-when-its-tethered-to-my-android-phone)
Also, I noticed that the Ping command in CMDPrompt no longer works.
I love the software and use it frequently. Hopefully someone knows of a way to get S/FTP and SCP working.

Hi,
We only deal with HTTP traffic in TetherFi currently. I am also not a dedicated network guy and have no idea if it is even possible to forward proxy FTP.
This is not a full tether, it's just an HTTP proxy, so unfortunately we are limited in how general purpose we can be.
Sounds like TetherFi is the wrong tool for your use case


Non --demo option seems to fail

Hello, on 0.4.1, I'm creating (inside a Docker container), a minimal notebook:
jupyter-book create host/tmp_book

And this seems to fail:
Copying new book to: ./host/tmp_book
Traceback (most recent call last):
  File "/opt/conda/bin/jupyter-book", line 11, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.7/site-packages/jupyter_book/main.py", line 31, in main
    commands[args.command]()
  File "/opt/conda/lib/python3.7/site-packages/jupyter_book/create.py", line 119, in new_book
    _check_file_exists(args.content_folder)
  File "/opt/conda/lib/python3.7/site-packages/jupyter_book/create.py", line 37, in _check_file_exists
    raise FileNotFoundError("Couldn't find file: {}".format(path))
FileNotFoundError: Couldn't find file: /opt/conda/lib/python3.7/site-packages/jupyter_book/minimal/content

If I run jupyter-book create host/tmp_book --demo, it works OK.
Also, in case it helps, if I check on the file that does not find, it appears not to exist indeed:
jovyan@d8c5e8667ee0:~$ ls /opt/conda/lib/python3.7/site-packages/jupyter_book/
__init__.py  __pycache__  book_template  build.py  create.py  main.py  run.py  toc.py  utils.py
jovyan@d8c5e8667ee0:~$

Am I doing something wrong?

hmmmm, I wonder if the file isn't being linked properly in the install bundle...will look into this now!

ok @darribas can you try uninstalling, then re-installing from the master branch on github with:
pip install git+https://github.com/jupyter/jupyter-book

and let me know if it works now?

Yes! This seems to work now. Thanks!

I had the same issue and I can confirm it's fixed on master :)

Recommend adding a warning to the installation instructions.

@ketozhang thanks for the suggestion - I think in this case a faster fix would be to just cut a new release. I'll do that now.

new release is out there! Please do give it a shot and hopefully it'll work with pip install -U jupyter-book!


UserType::Real is deprecated

warning: use of deprecated item 'UserType::Real': because reasons
   --> juniper-from-schema/tests/doc_test.rs:118:1
    |
118 | / graphql_schema! {
119 | |     schema {
120 | |         query: Query
121 | |     }
...   |
173 | |     union SearchResult = User
174 | | }
    | | ^ in this macro invocation
    | |_|
    |

@theduke Do you have any idea what could be causing this deprecation warning? rg Real gives me nothing so I suspect it is coming from a macro somewhere.

Well the enum variant is marked as deprecated in the schema, so i guess a Rust deprecated attribute is created somewhere.
ps: cargo-expand is great for debugging macros

Lol yeah that is probably why. Thanks!


Infer request

When only one handled ToolMessage is compatible with the arguments provided by the LLM, but the LLM did not specify request (especially common on weaker models, but still occurs with GPT-4o), uses the only compatible function call.

@nilspalumbo there was an interesting edge-case triggerred by the sql-chat GetTableNames tool -- the tool has no parameters, and the maybe_parse was attempting to parse the results of running GetTableSchemas (which is a dict) into GetTableNames, and was succeeding because the ToolMessage did not have Config.extras="forbid" enabled:
json_data = {
  description = "The departments table...",
  columns = {'id': 'INTEGER', 'name': 'VARCHAR'},
}

This was being successfully parsed as an instance of GetTableNames which has no required params.
The fix is to add this to ToolMessage:

class ToolMessage:
    ...
    class Config:
         extra="forbid"

great pr, thanks @nilspalumbo


EF6.3 Within NetCoreApp3.0 Library and PMC Migrations

I have a .NET Core 3 library which references EF6.3 and configuration.json. When I execute entityframework6\enable-migrations  I run into a problem with using  configuration.json which is used to read the connection string from appsettings.json within the IDbContextFactory method. This is due to the package references not being copied to the bin directory during build.
I have hard coded the connection string for now, but would like to use .Net Core 3 configuration to get the connection string.
I haven't been able to find any csproj setting that will allow my to use .Net Core 3 configurations

@bricelam  "This is due to the package references not being copied to the bin directory during build." is this known/expected?

Ah, we inject this on EF Core to make it work:
  <PropertyGroup>
    <GenerateRuntimeConfigurationFiles>True</GenerateRuntimeConfigurationFiles>
  </PropertyGroup>

We may also hit binding redirect issues on .NET Framework class libraries for similar reasons

Hmm, looks like I'm talking about a different problem. @ToddThomson do you have a repro project I can dig into?

Hi @bricelam . I created a simple repro project for you, but everything ( enable-migrations; add-migration ) worked properly. This project only included EF 6.3 and configuration json.
The only difference I can think of is that the project that was giving me problems included both EF 6.3 and EFCore 3.0.
Let me go back and confirm that the issue still exists...

@bricelam The issue results from having:
<ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
  </ItemGroup>

included in any library project in the dependency chain.

I don't follow. Can you share a repro? Also, what error are you seeing?

@bricelam Here is a link to the repo Issue 1400 repo.
Within VS2019 latest open the Nuget Package Manager Console. Type enable-migrations. This will work properly.
Now edit the project file and remove the comments around the lines:
<ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
</ItemGroup>

Remove the migration configuration file that was previously created from running the enable-migrations command.
In the PMC try running the enable-migrations command again. The command will fail.

Thanks! Setting GenerateRuntimeConfigurationFiles to True does indeed fix the problem.
The gory details
Using the Microsoft.AspNetCore.App framework reference tells CoreCLR to load Microsoft.Extensions.* assemblies from the framework instead of from the NuGet packages directory. But without a *.runtimeconfig.json the tools use the Microsoft.NETCore.App which doesn't include these libraries leading to the following error.

Could not load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.

@ajcvickers Looks like we should take (at least part of) PR #1419 in 6.4

@bricelam Sounds reasonable.


Change the UI design of Tonomy App Manager

Redo the design of Tonomy App Manager to match the General Design System so there is consisteny throughout the  apps of Tonomy Foundation.

Vote at the end

30 pages;


Update Chinese(Simplified) Translation

Resolved / Related Issues

None

Details of Changes

Fixed (Most of the) Untranslated Items

Validation
How did you test these changes?

[ ] Built and ran the app
[ ] Tested the changes for accessibility

Thank you!

@HappyDrop674 can you take a look at #7625?


HOTFIX: Remove deprecated parameter from phase_cross_correlation

The return_error keyword has been removed from phase_cross_correlation:
https://scikit-image.org/docs/stable/api/skimage.registration.html#skimage.registration.phase_cross_correlation
Removing from our code too to avoid crashes. Previously we had this set to True, but it seems that this is returned regardless now, so no major changes needed.

What version of skimage did the parameter get removed in? Consider having this PR also update the installation requirements or dependencies, if relevant.
Specifically, if someone is running with an older version of skimage, which does have and need that parameter, they would not get the returned error, and the code would probably raise an exception of not having the expected number of outputs  from that function.

It was removed as of 0.23 (the current stable release). Fortunately, the default for 0.22 was to have return_error=True, so we were really just repeating that anyways, and I don't think we'll bump into any issues with not having the correct number of expected outputs.
https://scikit-image.org/docs/0.22.x/api/skimage.registration.html#skimage.registration.phase_cross_correlation

To be specific, my question is, if someone tries to install spaceKLIP in an environment with version 0.21, or 0.20, or older, does any error message tell them not to do that?
Currently, requirements.txt doesn't even list any minimum versions of any packages, nor does pyproject.toml. In general that's not ideal, because we're not really telling users anywhere "hey, this won't work if you have versions older than X"

The default value of return_error in older versions of phase_cross_correlation is True. So, assuming someone has an older version installed, there would be no negative impact to removing us the manual setting that parameter in the function call. The code will still work.
I agree that we should think about defining minimum requirements, but that seems to be a broader effort (which I will make an issue for now).


Target Rust for AoT compilation

Is your feature request related to a problem? Please describe.
Cranelift is great for JIT but Rust is probably better Quality of Life and Utility for AoT. It would be nice to generate Rust libraries from LSTS compilation to be reintroduced into a more lively ecosystem of code. This would also cement LSTS as a build tool, rather than as a standalone platform which it isn't and will never be.
Describe the solution you'd like
Generate pretty source code for AoT compilation of Rust assets. This is the also the quickest route to Closures as a supported feature.

New repo dedicated to this subproject. https://github.com/andrew-johnson-4/L1IR_Rust

LM is new backend.


flynn-host cluster refactor

After attempting to implement #1170 a few different ways, and observing some production failures of sampi, I have a new plan.
In the new model, each flynn-host instance exposes an API that can be used to run jobs on that instance.
The concept of a cluster state leader (sampi) is removed and replaced with a set of "monitors" that keep track of the cluster state. The sampi model had a serious failing in that it made it appear that there is a consistent view of the cluster, when that is not actually true. At any point in time there may be hosts that are not connected to sampi due to a network partition or other issues. Hosts could also disconnect during scheduling, causing requested jobs to never be run. Since pretending that there is a consistent cluster state only complicates things, we can switch to an eventually consistent model. The first iteration will have "monitor" instances that discover hosts via service discovery and unify the state from all of them in memory. To run jobs, the scheduler must connect to the target host and request that the jobs be run. Since the scheduler needs to connect to the host anyway to monitor the job, this has basically no impact.
Layer 0 bootstrap is removed entirely, and the concept of layer 0 mostly disappears. All services, including discoverd, etcd, and flannel are started by bootstrap. A discovery URL or list of flynn-host IPs is passed to bootstrap in order to find all of the nodes. This simplifies bootstrap and allows us to have tighter control over the process without splitting configuration across multiple steps (no more implicit layer 0 bootstrap + etcd config). The user experience is also better because we can health check etcd/flannel while starting them, and expose any error logs and diagnostics right away (#1148). It also becomes much easier to register everything in the controller for management and updates, and move to idempotent bootstrap (#225) in the future.
In the future, we'll want to apply policy across the cluster to schedulers (for example limiting the total amount of resources allowed). This will be accomplished by having a set of "arbiter" services that watch trusted monitors. In order to schedule a new job or resize an existing job, a scheduler will provide details to and request a ticket from the arbiter. The ticket will time-limited and be accepted by the specified host, providing permission to access the resources.
TODO

[ ] Remove sampi, and modify each host to be standalone, capable of running jobs via its API.
[x] Remove layer 0 bootstrap.
[ ] Implement discovery URL system for hosts.
[ ] Add API to configure networking, remove knowledge of flannel.
[ ] Add API to configure discoverd registration.
[ ] Move etcd, discoverd, flannel to bootstrap, register in controller.
[ ] Implement cluster monitor service.
[ ] Update all consumers of the cluster API to use the new system.

@titanous this sounds sensible, one thing I am wondering is if the monitor and scheduler are the same thing? The scheduler needs to know what is running across the cluster to intelligently schedule jobs, and it watches all the hosts to track job states, which sounds like what the monitor service would also do?

Yeah, I'm going back and forth on that. The main thing is figuring out how one-off jobs are scheduled in that scenario? Does the scheduler expose an API? That seems a bit weird as the scheduler is specific to the controller and there is the possibility of running many schedulers (what about them? do they implement the same monitoring code?)

I think it makes sense for the scheduler to run the one-off jobs too, perhaps the controller creates job records in the database, and there is an AFTER INSERT trigger which the scheduler uses to actually run the job? Even if the monitor and scheduler are separate though, we still have that issue right?
WRT multiple schedulers running, I was wondering whether we should relax the constraint that only the leader schedules jobs, and use postgres advisory locks (like the deployer) to "lock" a formation / job and make the necessary cluster changes?
Thinking more about the schedulers being the monitors, they could maintain the full cluster state in service metadata, and then when scheduling a job they first place the job in-memory and then try to update the service metadata, and only if that succeeds would they then actually run the requested jobs (which would make it similar to the shared-state scheduler described in the Omega paper).
Of course my suggestions require a functioning etcd, discoverd & postgres, so we may need to handle the case of scheduling those separately.


feat: add methods to handle jobs in terratest

This PR is for adding Job to Terratest.
implement :

ListJob
GetJob
WaitUntilJobSucceed

add job_test too

The overall build failed, but the relevant kubernetes tests passed, so we can merge this in. Thanks for your contribution!


ArrayIndexOutOfBoundsException thrown by or() method in some multithreaded application

Describe the bug
An ArrayIndexOutOfBoundsException gets thrown when OR-ing 2 bitmaps.
java.lang.ArrayIndexOutOfBoundsException: null
at org.roaringbitmap.Util.unsignedUnion2by2(Util.java:1025) ~[RoaringBitmap-0.8.12.jar:?]
at org.roaringbitmap.ArrayContainer.ior(ArrayContainer.java:738) ~[RoaringBitmap-0.8.12.jar:?]
at org.roaringbitmap.Container.ior(Container.java:652) ~[RoaringBitmap-0.8.12.jar:?]
at org.roaringbitmap.RoaringBitmap.or(RoaringBitmap.java:2266) ~[RoaringBitmap-0.8.12.jar:?]

To Reproduce
I think the issue is that bitmap2 which is getting OR-ed with bitmap1 can also be getting OR-ed with other bitmaps at the same time. That is not to say that bitmap2 is being modified itself, but it is being used to add its contents to other bitmaps. I have not seen this happen in single threaded tests, and only under load in a Production environment.
RoaringBitmap roaringBitmap1; // method local bitmap
RoaringBitmap roaringBitmap2; // shared bitmap used across multiple threads
roaringBitmap1.or(roaringBitmap2); // leads to AIOOBE

RoaringBitmap version:
0.8.12
Java version:
openjdk version "1.8.0_252"
OpenJDK Runtime Environment (build 1.8.0_252-b09)
OpenJDK 64-Bit Server VM (build 25.252-b09, mixed mode)

Thanks for the report.
You need to either produce a reproducible case that we can inspect, or else, you need to provide an analysis to demonstrate that there is a bug in the RoaringBitmap library. It is simply impossible for us to do anything right. We do not have evidence that there is a bug in RoaringBitmap.

I think the issue is that bitmap2 which is getting OR-ed with bitmap1 can also be getting OR-ed with other bitmaps at the same time.

The most straightforward conclusion from your report is that you have some data race. The RoaringBitmap library does not provide thread safety. It is entirely the responsibility of the user to avoid data races.
You can use a tool such as RaceD to diagnose the data race in your application. There are other such tools and techniques to diagnose data races.
If, after diagnosing the data race, you trace it back to a bug in RoaringBitmap as opposed to a bug in your application, we will be eager to work with you to fix it.

@lemire you are absolutely correct, it turns out that what I thought was a method local bitmap was actually shared and multiple threads could access it at the same time. Apologies for taking some of your time, closing this issue.

Note that mere access should be fine if the data is nit mutated.


[DO NOT MERGE] Upgrade terraform provider google beta to v5.0.0

This pull request presents a major version upgrade for the Pulumi Google Provider. This work is tracked in #1183.

Removes deprecated resources and hard aliases; see schema-diff summary below.
Removes security policy patch as fixed via the bridge and adds integration test to verify it works as expected
Addresses bigquery.dataset patch as still needed and adds test to verify correct behavior
Adjusts patch set for upstream changes
Tests remain enabled for major version upgrade 🎉
Fixes bucket-go tests

Ready for review; waiting on bridge update and upgrade tests to merge and rebase.
Recommendation: When merged, cut alpha release and pivot to #1248.
Fixes #1229
Fixes #1189
Fixes #1187

Couple of preliminary notes...

we'll need an explanation for removed resources and functions; were those removed upstream? were these the hard aliases? there's a few so we might need to divide-and-conquer chasing these down - I see you mention "Removes deprecated resources and hard aliases; see schema-diff summary below." but we might need the detail for the migration guide? Perhaps if schema-diff can distinguish "removed hard alias" or some such we could quickly fix it up to give a more informative summary to save work here?

following how we did the AWS release I think we should be able to cut alphas from a release branch, so we can verify them in templates/examples before merging

do any of the changes like removing patches easily separable into their own PRs so we can check them onto main branch or that's not worth it?

Just a quick comment to note that I've recently rerun the benchmarks for this branch vs master and there do not appear to be any significant performance differences:
                                                                                │   old.txt    │                 new.txt                  │
                                                                                │    sec/op    │    sec/op      vs base                   │
/newPlugin/gcp                                                                                212.9m ±  0%    208.5m ±  0%    -2.09% (n=220+210)
/newPlugin/yaml:/Users/mjeffryes/workspace/pulumi/gcp/.pulumi/bin/pulumi-language-yaml                                16.21m ±  1%    15.35m ±  1%    -5.27% (n=210+200)

/bigquery-table/ResourceProvider/CheckConfig/pulumi:providers:gcp                                     243.5m ±  4%    263.6m ±  9%    +8.26% (p=0.035 n=10)
/bigquery-datasetaccess-3/ResourceProvider/CheckConfig/pulumi:providers:gcp                           235.7m ±  5%    253.6m ±  8%    +7.61% (p=0.029 n=10)
/compute-disk-3/ResourceProvider/CheckConfig/pulumi:providers:gcp                                     239.3m ±  6%    252.8m ±  9%    +5.63% (p=0.043 n=10)
/storage-bucketobject/ResourceProvider/CheckConfig/pulumi:providers:gcp                               235.0m ±  3%    250.9m ±  9%    +6.74% (p=0.001 n=10)

/bigquery-datasetaccess-3/ResourceMonitor/RegisterResource/pulumi:providers:gcp                       448.9m ±  3%    465.5m ±  4%    +3.69% (p=0.011 n=10)
/cloudfunctions-function/ResourceMonitor/RegisterResource/gcp:storage/bucket:Bucket                   148.8m ±  6%    160.5m ± 10%    +7.89% (p=0.005 n=10)
/compute-disk-1/ResourceMonitor/RegisterResource/gcp:compute/disk:Disk                                153.5m ±  8%    167.3m ±  6%    +9.03% (p=0.019 n=10)
/dns-recordset/ResourceMonitor/RegisterResource/gcp:dns/recordSet:RecordSet                           150.8m ±  5%    162.7m ±  8%    +7.91% (p=0.007 n=10)
/pubsub-topic/ResourceMonitor/RegisterResource/gcp:pubsub/topic:Topic                                 155.8m ±  6%    161.5m ± 32%    +3.66% (p=0.011 n=10)
/storage-bucketobject/ResourceMonitor/RegisterResource/pulumi:providers:gcp                           450.0m ±  2%    457.8m ±  5%    +1.75% (p=0.007 n=10)

The smattering of differences in CheckConfig and RegisterResource I think are mostly artifacts of the number of different metrics collected (you test enough things, you find an effect somewhere https://xkcd.com/882/); I've spot checked a few of these by running the benchmarks again and they don't reappear.
The very slight decrease in plugin load time was stable.
Anyway, no performance concerns for the release. (yay!)


Adds POST as a verb for the delete action

I was trying to delete a resource and received an error saying: No route matches [POST] /author/1/delete
The error was happening because the DELETE route for rails admin is expected to use either GET (to access the delete view) or DELETE (for the destroy action). But the form was generated to have its method attribute equal to POST. AFAICT, this is normal behavior and the real http verb is kept in a hidden field with name _method. See actionview-4.1.7/lib/action_view/helpers/form_tag_helper.rb @ line 714 ActionView::Helpers::FormTagHelper#extra_tags_for_form.
In any case, I made the changes in this PR and it is now working for me (although the flash message is not showing). Also I had to prefix t with I18n.
Can anyone else delete resources? When you do, does the form submit a POST or a DELETE request?

FYI—I have similar problems when editing a resource.

I don't get it.
What you say is partially true(with DELETE request, form's method becomes POST and real http verb is kept in _method), but Rack::MethodOverride automatically uses preserved _method value as HTTP method, so no special care in app will be needed.
Can you create minimal app to reproduce this problem?

Thanks for the tip @mshibuya. I was using rails-api and the MethodOverride middleware wasn't being added to the stack.
I set config.api_only = false in application.rb and now the request goes through. However, I had to prefix all calls to t with I18n. Otherwise Rails can't find the method t. This is the only change in the PR. Is this change needed?

By parent_controller config option(#2217), setting RailsAdmin::ApplicationController's base class to ActionController::Base will solve this problem.

@matstc +1


Escape spaces in IPv6 ZoneID with %20

Link-local IPv6 addresses may have ZoneID attached at the end. ZoneId is name of corresponding network interface. On Windows usually it is "Local connection". Space in ZoneID causes problem when ICE candidate is parsed so it has to be escaped. It looks that there is no escaping defined specifically for SDP; the closest one is RFC 6874 for URI. This fix partially uses this approach and replaces spaces with %20.
Description
Reference issue
Fixes #...

I have read more about this ZoneID and found that it has only local meaning and should not be sent out over the wire. So this PR is invalid, and different fix is needed here. I will create it.


feat: support boolean attributes

https://github.com/markdown-it/markdown-it/issues/598
Supports:

.attrSet('download') on Token
.attrs.push(['download']) on Token
.attrs.push(['download', null]) on Token
.attrs.push(['download', undefined]) on Token

We need do discuss final data format in original issue. I don't like duality (null & undefined) for single case, especially when it's hidden behind api call.

@puzrin
I'm okay with just checking against undefined, but that would mean that doing .setAttrs('attr', null) -> attr="null" is expected behavior.
Let me know what you decide and I'll update.

I'm okay with just checking against undefined, but that would mean that doing .setAttrs('attr', null) -> attr="null" is expected behavior.
Let me know what you decide and I'll update.

I understand. I left issue open to discuss signature proposals from other users. Did not thinked about it myself, because issue is not too hot and can be hacked at user side (without dependency on my personal opinion).

I have no strong preference but would like to add that boolean attributes can also be set to their own name to signify a true value (e.g.
Something hidden and HTML5 compliant
) which is what we just settled with for now.


chore(cli): bump

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


Supports service discovery with Consul

Ⅰ. Describe what this PR did
Supports service discovery with Consul
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #728 into develop will decrease coverage by 0.54%.
The diff coverage is 1.76%.

@@             Coverage Diff              @@
##             develop    #728      +/-   ##
============================================
- Coverage      32.75%   32.2%   -0.55%
+ Complexity       924     922       -2
============================================
  Files            229     230       +1
  Lines           8937    9048     +111
  Branches        1088    1097       +9
============================================
- Hits            2927    2914      -13
- Misses          5662    5785     +123
- Partials         348     349       +1

Impacted Files
Coverage Δ
Complexity Δ

...aba/fescar/discovery/registry/RegistryFactory.java
34.78% <0%> (-3.32%)
2 <0> (ø)

...ery/registry/consul/ConsulRegistryServiceImpl.java
0% <0%> (ø)
0 <0> (?)

...libaba/fescar/discovery/registry/RegistryType.java
40% <40%> (-1.18%)
2 <0> (ø)

...om/alibaba/fescar/core/rpc/netty/ShutdownHook.java
56.25% <0%> (-25%)
6% <0%> (-2%)

...scar/core/rpc/netty/AbstractRpcRemotingClient.java
19.89% <0%> (-3.23%)
7% <0%> (ø)

Continue to review full report at Codecov.

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

Can you please add some unit test to verify this new feature ?
i have done the integration testing.


Storage support updating pool config during create

When using loopback images the pool's config is updated after the driver create function has run to record the newly created loopback image location.
Adds generic support for updating config during create.
Includes https://github.com/lxc/lxd/pull/6605

As @stgraber points out this is already covered by the functionality in storagePoolCreateLocal


Add heads for ACAR-Net

Signed-off-by: Jael Gu<EMAIL_ADDRESS>

Codecov Report

Merging #1255 (906f284) into main (a391d3b) will increase coverage by 0.19%.
The diff coverage is 87.02%.

@@            Coverage Diff             @@
##             main    #1255      +/-   ##
==========================================
+ Coverage   68.72%   68.91%   +0.19%
==========================================
  Files         258      259       +1
  Lines       12439    12570     +131
  Branches     2069     2085      +16
==========================================
+ Hits         8549     8663     +114
- Misses       3353     3361       +8
- Partials      537      546       +9

Impacted Files
Coverage Δ

towhee/models/acar_net/head.py
83.80% <83.80%> (ø)

towhee/models/acar_net/__init__.py
100.00% <100.00%> (ø)

towhee/models/acar_net/utils.py
90.69% <100.00%> (+12.91%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


chore: Refactoring code for entity explorer on app editor to support package editor

Description
Refactoring code for entity explorer on app editor to support package editor
PR fixes following issue(s)
Fixes #26049
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

[x] Manual
[ ] JUnit
[ ] Jest
[x] Cypress

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test


test: [M3-8458] - Fix StackScripts pagination test failure

Description 📝
This fixes the StackScripts pagination test failure. The test fails because Cloud Manager filters certain StackScripts from the landing page, and our test didn't account for that when it checked for content in the StackScripts list.
Shout out to @AzureLatte for identifying the cause of the failure!
Changes  🔄

Do not assert that StackScripts exist in the list when they only support deprecated or Kube Images
Rename smoke-community-stackscrips.spec.ts to smoke-community-stackscripts.spec.ts

How to test 🧪
We can rely on CI since the test currently fails 100% of the time. However, you can run the test locally to manually verify the changes:
yarn cy:run -s "cypress/e2e/core/stackscripts/smoke-community-stackscripts.spec.ts"

As an Author I have considered 🤔
Check all that apply

[ ] 👀 Doing a self review
[ ] ❔ Our contribution guidelines
[ ] 🤏 Splitting feature into small PRs
[x] ➕ Adding a changeset
[x] 🧪 Providing/Improving test coverage
[ ] 🔐 Removing all sensitive information from the code and PR description
[ ] 🚩 Using a feature flag to protect the release
[ ] 👣 Providing comprehensive reproduction steps
[x] 📑 Providing or updating our documentation
[ ] 🕛 Scheduling a pair reviewing session
[ ] 📱 Providing mobile support
[ ] ♿  Providing accessibility support

Interesting that we've never encountered this failure caused by a stackscript that should be filtered out before now.

Yeah! It only leads to a failure when the first item on a page returned by the StackScripts endpoint is hidden by Cloud, since those are the only StackScripts the test actually checks.
If we checked every StackScript, or even just a larger random sample, we probably would have noticed it a long time ago (although using a random sample of StackScripts would've been a lot harder to troubleshoot, too!)

getting a failure here consistently - not sure if due to my setup

getting a failure here consistently - not sure if due to my setup
(Screenshot)

Hm. This isn't caused by the changes in this PR (different test), but it has been flaky so I don't think it's caused by your setup either (at least not entirely).
My instinct seeing that error message is that Cloud is either selecting a region that doesn't support the Dedicated 8gb plan (don't think such a region even exists) or Cloud is failing to select a region altogether: this test selects a region by typing its name and hitting enter, which doesn't actually manifest as a failure if the desired region is absent from the drop-down, it just silently fails to select a region.
My guess is that Cypress is randomly selecting a region to use which is missing some capability that is required by StackScripts, so when it attempts to select that region in the UI, it's absent from the drop-down and as a result the Dedicated 8gb plan fails to show up. What doesn't make sense to me is why this would be happening consistently for you -- it should eventually pick a region that works. Is your copy of Cloud built against another environment where there might be a lot of regions lacking some capabilities?
(If you have any time today, Cypress should have saved a recording of the failure in packages/manager/cypress/videos -- if you send that over on Slack I'd love to take a look!)

@jdamore-linode the error I am getting is indeed due to the region selection failing
ui.regionSelect.find().click().type(${region.id}{enter});

typing the ID won't return the region in the select, but the label would.
confused why I am the only one getting this. It this a flag configuration discrepancy with distributed regions UI?

@abailly-akamai I'm a bit confused by this too -- we've always been able to search by regions by ID as far as I'm aware so not sure why that wouldn't be working now (and seemingly only for you).
One way to rule out a Feature Flag discrepancy would be to build and serve Cloud with yarn build && yarn start:manager:ci so any locally configured feature flags via the dev tool won't be a factor. Either way, I've created M3-8471 to look into this since it might become a bigger problem.


Support FormData when using ipfs helper from Node js

Description

Related Issue

Types of changes

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

This PR is related to the discussion https://github.com/capsule-corp-ternoa/ternoa-js/discussions/111


Clarification for Windows Node OS updates are needed

Per statement above one have to perform AKS upgrade which upgrades version of kubernetes. Link points to process of upgrading Kubernetes version as well from 1.12 to 1.14. So how do you exactly upgrade worker nodes to new version of OS if Kubernetes is already on latest version?

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

ID: eadf3bc9-bea3-b51f-1477-8f76ccfce7da
Version Independent ID: 12d0be59-8947-e0a2-d73a-8834f2e5f8b2
Content: Update and reboot Linux nodes with kured in Azure Kubernetes Service (AKS)
Content Source: articles/aks/node-updates-kured.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

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

Windows server containers are currently in Preview. You can't automatically update and manage reboots for windows using kured as with Linux nodes in AKS.
Therefore, for windows node, follow the steps in this document.
Here is the document for Current limitations for Windows Server node pools and application workloads in Azure Kubernetes Service (AKS) which mentions

Windows Server nodes in AKS must be upgraded to a latest Windows Server 2019 release to maintain the latest patch fixes and updates. Windows Updates are not enabled in the base node image in AKS. On a regular schedule around the Windows Update release cycle and your own validation process, you should perform an upgrade on the Windows Server node pool(s) in your AKS cluster. For more information on upgrading a Windows Server node pool, see Upgrade a node pool in AKS.

@mlearned @sauryadas Can you please share your insights on customer's last question? Thanks :)

@artisticcheese Have you tried using this document to upgrade the node pool version. For example, let's say your kubernetes version and node pool version are different and kubernetes version is the latest. If you use this to upgrade the node pools to the version same as the kubernetes version by using the command,
az aks nodepool upgrade \
    --resource-group myResourceGroup \
    --cluster-name myAKSCluster \
    --name mynodepool \
    --kubernetes-version 1.12.7 \
    --no-wait

Just run it but it did not update versions of Windows worker nodes.

@jluk Did you get a chance to take a look at this question? Is it possible to upgrade the Windows OS versions, while in Preview? Please share your insights. Thanks :)

@MikkelHegn who owns windows

@MikkelHegn Can you please help answer customer's question on Windows Node OS version update. Thanks. :)

@jluk Is there anyone else who can help with this while Mikkel is out of office. Thanks. :)

@palma21 or @macols do you know if there is a work around for this today? To my knowledge this is new functionality we need to deliver given same version upgrade won't work on a non-failed state cluster.

@macols Is this something you can help confirm? Thanks.

No workaround today we are building this functionality as we speak.

@artisticcheese Hope that helped answer your question. I will share the update when we have this functionality ready.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


GURU ebuild does not work

The ebuild installs just fine, but I receive this error. I already tried installing gtk-layer-shell but it does not work. Is there a dependency missing or is the ebuild not setup correctly? Here is the output:
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/nwg_displays/main.py", line 24, in <module>
    gi.require_version('GtkLayerShell', '0.1')
  File "/usr/lib/python3.11/site-packages/gi/__init__.py", line 126, in require_version
    raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkLayerShell not available

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python-exec/python3.11/nwg-displays", line 5, in <module>
    from nwg_displays.main import main
  File "/usr/lib/python3.11/site-packages/nwg_displays/main.py", line 26, in <module>
    raise RuntimeError('\n\n' +
RuntimeError:

If you haven't installed GTK Layer Shell, you need to point Python to the
library by setting GI_TYPELIB_PATH and LD_LIBRARY_PATH to <build-dir>/src/.
For example you might need to run:

GI_TYPELIB_PATH=build/src LD_LIBRARY_PATH=build/src python3 /usr/lib/python-exec/python3.11/nwg-displays
➜  ~

I know nothing on Gentoo, so the only thing I can say is that the gi.require_version('GtkLayerShell', '0.1') command execution was unsuccessful. Looks like a missing dependency. You need to contact the packager.

@WhitleyStriber  You need the following installed:
dev-python/i3ipc
gui-libs/gtk-layer-shell with the introspection use flag enabled.
The ebuild needs to be fixed to reflect this, but that is not @nwg-piotr  responsibility :)


at (@) keyboard shortcut does not work on mac with swiss german keyboard layout

In the swiss german mac keyboard layout, the at (@) sign is made using the ALT-G keyboard shortcut. In atom, this does not work, which makes it very inconvenient to code.

Try this:
Go to File>Settings>Packages and search for the autoflow Package and disable it. After restarting Atom it should work.

Did not make any difference. I still can't write any "@"s in atom.

I found a solution to my problem:
Two packages were using the ALT-G keybindings. git-diff and open-on-github. In the git-diff package settings i could deactivate the keybindings, so this was not a problem. The open-on-github package on the other hand did not have such an option, so I deactivated it. After a restart of Atom, it worked perfectly.
This could be still an issue for other users with the swiss german mac keyboard layot.

Atom currently can't handle non-US keyboard layouts.  See atom/atom-keymap#35 for more information and workarounds.

@aaronschmied Thank you, I disabled git-diff and open-on-github and it's working for me now (swiss fr keyboard)