Something wrong in perspective transform (Matrix4)

I try to bring up some 3-D effects by changing the perspective of Matrix4 but the result is a bit odd. The following codes and images will illustrate my problem:

Without perspective:

class FlipWidget extends StatelessWidget {
  Widget child;

  FlipWidget({Key key, this.child}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Column(
      mainAxisSize: MainAxisSize.min,
      children: [
        Transform(
          alignment: Alignment.bottomCenter,
          transform: Matrix4.rotationX(math.pi / 3),
          child: ClipRect(
              child: Align(
            alignment: Alignment.topCenter,
            heightFactor: 0.5,
            child: child,
          )),
        ),
        Padding(
          padding: EdgeInsets.symmetric(vertical: 0.5),
        ),
        ClipRect(
            child: Align(
          alignment: Alignment.bottomCenter,
          heightFactor: 0.5,
          child: child,
        )),
      ],
    );
  }
}

With perspective:

class FlipWidget extends StatelessWidget {
  Widget child;

  FlipWidget({Key key, this.child}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Column(
      mainAxisSize: MainAxisSize.min,
      children: [
        Transform(
          alignment: Alignment.bottomCenter,
          transform: (Matrix4.identity()..setEntry(3, 2, 0.005)) * Matrix4.rotationX(math.pi / 3),
          child: ClipRect(
              child: Align(
            alignment: Alignment.topCenter,
            heightFactor: 0.5,
            child: child,
          )),
        ),
        Padding(
          padding: EdgeInsets.symmetric(vertical: 0.5),
        ),
        ClipRect(
            child: Align(
          alignment: Alignment.bottomCenter,
          heightFactor: 0.5,
          child: child,
        )),
      ],
    );
  }
}

With perspective transform, the result looks like more 3-D effect but there's something wrong in the bottom of the transformed result.

The code using FlipWidget is the same:

@override
  Widget build(BuildContext context) {
    return new Scaffold(
      appBar: new AppBar(
        title: new Text(title),
      ),
      body: new Center(
        child: FlipWidget(
          child: Container(
            alignment: Alignment.center,
            width: 96.0,
            height: 128.0,
            decoration: BoxDecoration(
                color: Colors.black,
                borderRadius: BorderRadius.all(Radius.circular(4.0))),
            child: Text(
              '0',
              style: TextStyle(
                fontWeight: FontWeight.bold,
                fontSize: 80.0,
                color: Colors.yellow,
              ),
            ),
          ),
        ),
      ),
    );
  }

The doctor logs:

[✓] Flutter (Channel master, v0.5.6-pre.48, on Mac OS X 10.13.5 17F77, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] Connected devices (1 available)

• No issues found!

I figured out that using a very small value instead of zero in rotateX() transform (or without rotateX()), for example: rotateX(0.0001), will temporarily get around this matter.

Hi @hnvn,
I tried on latest stable (1.20.3) and observed below in perspective transform, not sure if this is the expected behavior thogugh.

Can you confirm at your end if this is still an issue ?
Thanks.

flutter doctor -v
Flutter 1.20.3 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 216dee60c0 (2 days ago) • 2020-09-01 12:24:47 -0700
Engine • revision d1bc06f032
Tools • Dart 2.9.2

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.3, on Mac OS X 10.15.2 19C57, locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions.
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


sideways scrolling in jupyter notebooks also scrolls page

Issue Type: Bug
When I have a big plot in a jupyter notebook I can press shift to scroll sideways through the plot. However, the notebook also still scrolls, which is annoying and obviously not the desired behaviour.
Steps to reproduce:

Create jupyter notebook
-Create very wide plot using pyplot (wider than the vscode window)
-Press shift and scroll while hovering over the plot.

VS Code version: Code - Insiders 1.56.0-insider (9a4d524f909e09079fec7abb82f2efde2172da7c, 2021-04-27T06:13:35.200Z)
OS version: Linux x64 5.11.0-7614-generic

/duplicate of https://github.com/microsoft/vscode/issues/115084


Add pytest-xdist to speed up test

xdist distributes tests across multiple CPUs
This allows to speed up

Planned for next cleanup event.


Pipeline not creating results folder

Hi,
We're getting the following error. It appears the pipeline isn't making the results directory
RROR ~ Error executing process > 'TYPEx:TISSEG:preprocess_panck (1)'
Caused by:
 Process `TYPEx:TISSEG:preprocess_panck (1)` terminated with an error exit status (255)
Command executed:
 ## Using params.input_dir as an absolute path
 ImageJ-linux64 --ij2 --headless --run "/nemo/lab/lloydc/home/users/travesw/IMC/TYPEx/git/TYPEx/bin/panck_filters.ijm" ome'rootDir="imctools/", tumour="tumour=164Dy_panCK.tiff"'
Command exit status:
 255
Command output:
 (empty)
Command error:
 WARNING: skipping mount of /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto: stat /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto: no such file or directory
 FATAL:  container creation failed: mount /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto->/camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto error: while mounting /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto: mount source /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto doesn't exist
Work dir:
 /nemo/lab/lloydc/home/users/travesw/IMC/TYPEx/git/TYPEx/work/8a/1556b4d4a299883ea8e529d8a6b774
Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`
 -- Check '.nextflow.log' file for details
[travesw@login006 TYPEx]$ cd results
-bash: cd: results: No such file or directory

We are also getting an issue with the path TYPEx///composites
RROR ~ Error executing process > 'TYPEx:TISSEG:run_classifier'
Caused by:
 Process `TYPEx:TISSEG:run_classifier` terminated with an error exit status (1)
Command executed:
 files=` find /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/TYPEx///composites/ -name "*tiff" `
 	echo " [/nemo/lab/lloydc/home/users/travesw/IMC/TYPEx/git/TYPEx/work/88/ffe6a0587dbcbf2fec42827e73dca2/panck_preprocessed_images.txt] "
 if [ -n "` find /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/TYPEx///composites/ -name "*tiff" `" ]; then
 mmand /ilastik-release/run_ilastik.sh --headless 				--project=/camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/models/tumour_stroma_classifier.ilp /TYPEx/results/TYPEx///compo/camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/TYPEx///composites/*tiff
 else
 /nemo/echo 'No composite images for tissue segmentation created'
 fi
Command exit status:
 1
Command output:
 (empty)
Command error:
 find: '/camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/TYPEx///composites/': No such file or directory
Work dir:
 /nemo/lab/lloydc/home/users/travesw/IMC/TYPEx/git/TYPEx/work/55/4d7273802f18b32b506b4cad495da7
Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`
 -- Check '.nextflow.log' file for details

Thanks, Sara. It seems that TYPEx is trying to use deep-imcyto input specified as the path /camp/home/travesw/home/users/travesw/IMC/TYPEx/git/TYPEx/results/deep-imcyto but the folder does not exist. Can you confirm the path where deep-imcyto was run?


Integration fails to initialize with unknown tariff

Describe the bug
Integration initialization failure caused by error:
 Exception: Failed to retrieve rates for tariff 'BUS-PANELP-12M-FIXED-SEPTEMBER2029'

I'm guessing the tariff isn't found for some reason? (It is valid)
Background: this is the "PanelPower" business tariff (the small business version of the Octopus Export tariff)
Please let me know if you need further information or if I can help in any way with diagnosis.
Reproduction steps
Restart the integration. The error occurs. I've tried uninstalling and re-installing the integration.
Expected behaviour
The integration should retrieve the tariff information
Tariff Code
BUS-PANELP-12M-FIXED-SEPTEMBER2029
Integration Version
11.0.2
Home Assistant Version
HAOS 12.3 (Core 2024.5.4, Supervisor 2024.01.1)
Fresh Install?
Not specified
Home Assistant Logs
Logger: homeassistant.components.sensor
Source: helpers/entity_platform.py:356
integration: Sensor (documentation, issues)
First occurred: May 22, 2024 at 3:05:04 PM (1 occurrences)
Last logged: May 22, 2024 at 3:05:04 PM
Error while setting up octopus_energy platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
await asyncio.shield(awaitable)
File "/config/custom_components/octopus_energy/sensor.py", line 108, in async_setup_entry
await async_setup_default_sensors(hass, config, async_add_entities)
File "/config/custom_components/octopus_energy/sensor.py", line 279, in async_setup_default_sensors
total_unique_rates = await get_unique_electricity_rates(hass, client, electricity_tariff_code if tariff_override is None else tariff_override)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/octopus_energy/sensor.py", line 92, in get_unique_electricity_rates
raise Exception(f"Failed to retrieve rates for tariff '{tariff_code}'")
Exception: Failed to retrieve rates for tariff 'BUS-PANELP-12M-FIXED-SEPTEMBER2029'
Confirmation

[X] I confirm that I cannot find my solution within the documentation
[X] I confirm that I cannot find my solution within the FAQ

Hello and sorry you're seeing this issue. Unfortunately, it looks like business based tariffs don't follow the usual structure which is causing this issue. There should be a repair notice to indicate this, but it looks like this is breaking before that is reached now.
When I get some time, I'll see if I can support business tariffs, but a lot of the code base relied on a the predetermined well formed structure

Hi Dave - thanks for looking into this. Trust me to be an edge-case!
Very happy to help if I can. This is a three-phase supply with the "Green Octopus 36M Fixed" import tariff.
The integration was working fine, including the Octopus Mini, until we got our export tariff enabled.
If it's tricky to support the business export tariffs would it be possible to just ignore the error and continue to work with just the import numbers? Or to have manual input of the export rate (which is the standard Octopus 15p/kWh continuously) - although I appreciate that would probably be even more code changes...
Thanks anyway :-)
Chris
PS. Happily using the integration at home on Intelligent Go without issues :-)

I'll try and fix the repair notice issue, and update to ignore the offending entities if it can't be determined.

Sorry for the late response. The integration should now hopefully support business tariffs as part of v11.1.0.

Awesome - fab. Thank you. Installing now and will report back....

All looks good Dave - thank you so much :-)


Refs 3483: add ouia ids to errata filters

Summary

Adds ouia ids for snapshot errata filters to help with QE tests

Testing steps

https://issues.redhat.com/browse/HMS-3483

closing because this component is replaced in this PR. these updates are now in that PR


[WO-782] Log full traffic

All traffic is logged excluding long strings, literals and sensitive information (passwords and oauth2 tokens).
Additionally added connection ID to log strings, so if multiple connections are currently open the ID identifies traffic for a particular connection.
Examples

Password is hidden when logging authentication info ([1] identificates the connection)

[2015-02-17T09:47:15.254Z][browserbox IMAP] [1] C: W1 login "testuser" "(* value hidden *)"
[2015-02-17T09:47:15.257Z][browserbox IMAP] [1] S: W1 OK User logged in

Literals are hidden when logging responses

[2015-02-17T09:47:15.971Z][browserbox IMAP] [2] C: W2 FETCH 1:* (BODY.PEEK[])
[2015-02-17T09:47:15.972Z][browserbox IMAP] [2] S: * 1 FETCH (BODY[] "(* 228B literal *)")
[2015-02-17T09:47:15.973Z][browserbox IMAP] [2] S: W2 OK FETCH Completed

NB!
Replace wo-imap-handler version identifier in package.json before merging

Double yay!

Question: is it possible to set the log level to ERROR and log less stuff e.g. for production?
I'm wondering if logging everything will affect performance.

I think performance would only be affected for extremely high numbers of transactions (unlikely for IMAP, esp. given roundtrips) or for extremely large strings.  Since the imap-handler explicitly does not include the contents of literals and only provides the length for strings over 20 bytes, I would expect this all to be fine as-is.  Of course there's no harm in doing a log level check before engaging in string-building.


Two small improvements to caldav component

This component includes the data of the currently running event (if the binary sensor is on) or the next upcoming event (if it is off) in the attributes of the binary sensor. However, it only looks for events that take place today. The rationale is, I guess, that the python-caldav library does not admit to look for the next upcoming event but only allows a date search. However, I can think of many use cases where one would need the first event tomorrow, like trigger automation X if I have an appointment in the morning. So increasing the date search range to today + tomorrow seems like a reasonable compromise to me.
The other change concerns the inclusion of all-day events. Currently, all-day events are not included on the default calendars (i.e. if there are no custom calendars), while they are included for all custom calendars. I don't quite understand the motivation for this, but in any case I believe it would be useful to customize it. So I added the options include_all_day both to the default calendars and to the custom calendars. The default values are such that the current behaviour is reproduced, so there is no breaking change.
Description:
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#9156
Example entry for configuration.yaml (if applicable):
calendar:
  - platform: caldav
    username: MYUSER
    password: MYPW
    url: https://<MYNEXTCLOUD>/remote.php/dav/
    calendars:
      - Birthdays
    include_all_day: true

calendar:
  - platform: caldav
    username: MYUSER
    password: MYPW
    url: https://<MYNEXTCLOUD>/remote.php/dav/
    custom_calendars:
        - name: custom
          calendar: Personal
          search: 'Test.*'
          include_all_day: false

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

[x] Tests have been added to verify that the new code works.

I just implemented the CalDav component and was wondering why there were these limitation.
@DavidMStraub appreciate the pull request enhancing the CalDav component.  Look forward to its merge and eventual release.

Thank you so much for this PR. Both of these issues have been bugging me as well.

Is it possible for me to remove the print statements? I would love to get this in ASAP. This will help with a few caldav-related features.

Sorry, I somehow missed the above comments! I will remove it now.

@ronytomen thanks for the review, I had missed your comments earlier, I believe they are now fixed.

Looks like this branch has a test conflict. Any way I can help out to resolve it? would love to get this into hass!

@MartinHjelmare thanks, I think it's fine now!

@MartinHjelmare I added the unit test.  It was a bit complicated as I had to mock the date_search method, but it was worth it as I found a bug in the original implementation. Now it works and from my side this can be merged!

It's procedure to add tests. Personal attacking people that are enforcing procedures is NOT accepted. Mike has been blocked for 3 days.


[Event Request] Table 222 "Ship-to Address" - OnAfterLookupCity

Is it possible to add OnAfterLookupCity after the PostCode.LookupPostCode function.
Identical to issue 10850.
table 222 "Ship-to Address"
{
...
        field(7; City; Text[30])
        {
            Caption = 'City';
            TableRelation = IF ("Country/Region Code" = CONST('')) "Post Code".City
            ELSE
            IF ("Country/Region Code" = FILTER(<> '')) "Post Code".City WHERE("Country/Region Code" = FIELD("Country/Region Code"));
            //This property is currently not supported
            //TestTableRelation = false;
            ValidateTableRelation = false;

            trigger OnLookup()
            begin
                OnBeforeLookupCity(Rec, PostCode);

                PostCode.LookupPostCode(City, "Post Code", County, "Country/Region Code");

                //START
                OnAfterLookupCity(Rec, PostCode);
                //STOP
            end;

            trigger OnValidate()
            begin
                OnBeforeValidateCity(Rec, PostCode);

                PostCode.ValidateCity(City, "Post Code", County, "Country/Region Code", (CurrFieldNo <> 0) and GuiAllowed);
            end;
        }

    //START
    [IntegrationEvent(false, false)]
    local procedure OnAfterLookupCity(var ShipToAddress: Record "Ship-to Address"; var PostCodeRec: Record "Post Code");
    begin
    end;
    //STOP

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Incorrect language classication

https://github.com/Anobium/Great-Cow-BASIC
All GCB files are BASIC files.  Currently https://github.com/Anobium/Great-Cow-BASIC is classified as C or INI.
Can we add GCB to the Language ids please?
Evan

Please have a look at the guidelines to add support for a new language to Linguist. If GCB meets the requirement on in-the-wild usage and you can provide the necessary information, feel free to submit a pull request.


Number of records for data packages resources

Currently we don't display total number of records for data package resources. Should we start doing that?
@peterdesmet
What needs to be done:

[x] Store data about how many records were published in the version history (including partition by table schema)
[x] Display actual number of records in the home and manage tables (number of observations for camtrap)
[x] Add "Data Records" section to the resource page
[x] Display actual number of records in the versions table

Yes, think that would be useful.

No, the number of records per resource (cf. core + extensions of Darwin Core Archives).

Sorry, not sure what you mean..
What would be displayed in the home table? https://ipt3.gbif-uat.org/
I though something like: 3967747 ( combined of 1539 deployments, 3782401 media, 183807 observations)

Oh, right, I forgot the homepage also shows a single number. For Camtrap DP specifically, I would opt to show the number of observations. The sum of the resources is not relevant.

I see. There is also a versions table, I guess similar to home page.
And what place did you have in mind?

I had the Data Records section in mind: https://ipt.inbo.be/resource?r=meetnetten-abv2-occurrences#anchor-dataRecords:

Oh, I see. We don't have that section currently

Great! Cool to see https://ipt3.gbif-uat.org/resource?r=mica-full#anchor-dataRecords
Could the resources be sorted (in their default order): deployments, media, observations?

Yes, sure, I can use that order


package depends on vulnerable packages<EMAIL_ADDRESS>

<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>gulp-header  >=1.8.10
Depends on vulnerable versions of lodash.template
Seems helper-for-markdown is not maintained anymore and still using<EMAIL_ADDRESS>Any chance to upgrade the package?

@hkjeffchan - interesting idea to just replace it. I created this pull request if you want to contribute: https://github.com/jaredwray/fumanchu/pull/44

@hkjeffchan - this will go out in the latest release today

lodash.template  *
Severity: high
Command Injection in lodash - https://github.com/advisories/GHSA-35jh-r3h4-6jhm
fix available via npm audit fix
node_modules/lodash.template
gulp-header  >=1.8.10
Depends on vulnerable versions of lodash.template
node_modules/gulp-header
2 high severity vulnerabilities
└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Can we remove helper-md? @jaredwray


[Question] Map all except controllers for SPA

I previously tried to use Microsoft.AspNetCore.SpaServices.Extensions to develop a SPA (Vue) inside my aspnetcore app. Sadly this package does not support authentication thus everything send to my API controllers gets 304 redirected to my auth provider (Azure).
I thought maybe a "plain" proxy could do the same. That's how I landed here.

I want to make every call to my app /, /some.js, ... use the proxy.
I want my controllers to overrule this mapping. So if I have /api/controller/action I don't want to proxy this request.

So far I got it working either way (but not both):

/ + controllers work but no "static files" from my spa (via app.UseProxy)
/ + every "static file" from my spa but no controllers (via app.RunProxy)

Any suggestions?

There are multiple ways to do this.  The easiest probably to use MapWhen, or to just be careful with the ordering.
You don't want RunProxy because RunProxy "stops" all other routing handlers registered with the middleware.
Can you share a snippet of your UseProxy code so I can help you with how to use it.  Usually, the way it works is that each thing you call like Map or Use is put on a "stack" of middleware, so we can fit it together in a way where your controllers are matched "first", and everything else goes to the proxy.
However, I have a feeling that you may want something else entirely.  Are you using a CDN, or are you proxying another server or microservice that you own?  If it is "another server", then this is a good solution; if it is a CDN, then I would recommend a different approach, and I am happy to help you out. 😄

Thanks for the quick response!
This is what my code looks like right now:
app.UseAuthentication();
app.UseRouting();
app.UseAuthorization();
app.UseEndpoints(endpoints =>
{
    // api controllers
    endpoints.MapControllerRoute(
        name: "areas",
        pattern: "{area}/{controller}/{action=Index}/{id?}");
});
if (env.IsDevelopment())
{
    app.UseProxies(builder =>
    {
        builder.Map("/", x =>
        {
            x.UseHttp("http://localhost:5173");
        });
    });
}
else
{
    app.UseStaticFiles();
}

I do not want to forward my requests to a CDN. I have a local Vue dev server (vite.js) and aspnetcore should redirect every request except controller routes to that server.

I was able to make it work with this mapping:
proxies.Map("{*url}", proxy =>
{
    proxy.UseHttp((_, args) => $"http://localhost:5173/{args["url"]}");
});

Is this a good approach?

Yes, that should work, but I think you want to use ** for nested folders, etc.  Using just * will escape things like slashes, so my/path would become my%2Fpath.  If you use **, then my/path stays as my/path.

That's interesting because it works for subfolders as well.
From what I understand from the docs is that * is equal to **. So it's just a matter of preference?

Cool: that's fine then. :)


[JENKINS-31214] added Job DSL for GhprbPullRequestMerge and docs

This is a follow-up for #229.

Thank you for this pull request! Please check this document for how the Jenkins project handles pull requests.

Thanks! I also added a section to the plugin's wiki page, see https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin#GitHubpullrequestbuilderplugin-JobDSLSupport.


[WIP] Create templates in Twig.templates object

Hi,
I'd like to get some feedback on this and also see what happens with the build (it does pass locally.)
Cheers

Bah, build failed :disappointed:. I've been testing this version with our codebase and it's working nicely.

I'm sad that CI didn't like this. It turned out that getting made redundant didn't lead to quite as much free time as I was hoping so I've not really been able to dive into the reason why it didn't run. Plus I've admittedly been being a bit lazy and making the most of the downtime :innocent:
One possibility did occur to me though. These new automated integration tests are lovely in that they test so many things instantly and let us make big changes with confidence. But if there's one or two weird edge cases where they don't help, because of a false negative like this one, then maybe the pragmatic thing to do is just live without one of those tests for this bit of functionality?
What do you think? Would the build be green without include_variable_template_name.test?

No worries, totally understandable. Congrats on your new role too, best of luck with that.
I'm not sure about removing that test, it seems pretty necessary. Must admit we have our own fork of this project again with the changes in and it's working out well. Did bust AMD compilation but fixed it with this interesting... commit.
Do you think it's worth creating a new PR with the changes to contribute back to the project?

Nice. That commit does take care of all the painful little bookkeeping that I figured we'd need to have in place for this to work right. And the fact that it's actually running in probably the most battle-hardened production deploy of Twig.js out there is a very big stamp of approval. Also, it looks like that awkward test is running fine in BK's branch, which is good news too.
I reckon throw a PR over with those two commits in it. Let's see what Travis CI makes of it. If it's green I think we should just get this merged and do a major version bump.


HDDS-4102. Normalize Keypath for lookupKey.

What changes were proposed in this pull request?
When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the Keyname.
Now when user tries to read the file from S3 using the keyName which user has used to create the Key, it will return error KEY_NOT_FOUND
The issue is, lookupKey also need to normalize path, when ozone.om.enable.filesystem.paths is enabled. This is a common API used by S3/FS.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4102
How was this patch tested?
Added a test.

Thanks for the patch @bharatviswa504, I would suggest adding a related robot test, too, which would make it possible to test the AWS compatibility of the change.
What do you think?

Tested and file/ and file are different:
$ aws s3api get-object --bucket=ozonetest --key=test1/file /tmp/www
{
    "AcceptRanges": "bytes",
    "LastModified": "Wed, 26 Aug 2020 14:24:06 GMT",
    "ContentLength": 79,
    "ETag": "\"6fcb0dbe8f0ef330b38f81a6a6a7a66e\"",
    "ContentType": "text/markdown",
    "Metadata": {}
}

aws s3api get-object --bucket=ozonetest --key=test1/file/ /tmp/www

An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist.

Just an idea: what do you think about normalizing the path on the client side? (o3fs/ofs). Would it make any problems?

Tested and file/ and file are different:
$ aws s3api get-object --bucket=ozonetest --key=test1/file /tmp/www
{
    "AcceptRanges": "bytes",
    "LastModified": "Wed, 26 Aug 2020 14:24:06 GMT",
    "ContentLength": 79,
    "ETag": "\"6fcb0dbe8f0ef330b38f81a6a6a7a66e\"",
    "ContentType": "text/markdown",
    "Metadata": {}
}

aws s3api get-object --bucket=ozonetest --key=test1/file/ /tmp/www

An error occurred (NoSuchKey) when calling the GetObject operation: The specified key does not exist.

Just an idea: what do you think about normalizing the path on the client side? (o3fs/ofs). Would it make any problems?

Thank You @elek for the test.
Uploaded design doc has provided reasoning to perform on the OM side.
And also when used via ofs/o3fs, it uses path Object, and paths are normalized already.

Thanks for the patch @bharatviswa504, I would suggest adding a related robot test, too, which would make it possible to test the AWS compatibility of the change.
What do you think?

Opened a jira to test S3 test suite with ozone.om.enable.filesystem.paths enabled.

Opened a jira HDDS-4154 to test S3 test suite with ozone.om.enable.filesystem.paths enabled.

Thanks. I think we need additional s3 tests as the behavior what I tested above (and failing) is not part of the current test suite.

Uploaded design doc has provided reasoning to perform on the OM side.

Thanks to share it. Now I understood the motivation. But what is your opinion about the AWS compatibility? For me it seems to be a bigger problem compared to having the validation code in one at the OM or one place at the client side.
What is your opinion about AWS compatibility issues?

Opened a jira HDDS-4154 to test S3 test suite with ozone.om.enable.filesystem.paths enabled.

Thanks. I think we need additional s3 tests as the behavior what I tested above (and failing) is not part of the current test suite.

Uploaded design doc has provided reasoning to perform on the OM side.

Thanks to share it. Now I understood the motivation. But what is your opinion about the AWS compatibility? For me it seems to be a bigger problem compared to having the validation code in one at the OM or one place at the client side.
What is your opinion about AWS compatibility issues?

When this flag is enabled, 333

Opened a jira HDDS-4154 to test S3 test suite with ozone.om.enable.filesystem.paths enabled.

Thanks. I think we need additional s3 tests as the behavior what I tested above (and failing) is not part of the current test suite.

Uploaded design doc has provided reasoning to perform on the OM side.

Thanks to share it. Now I understood the motivation. But what is your opinion about the AWS compatibility? For me it seems to be a bigger problem compared to having the validation code in one at the OM or one place at the client side.
What is your opinion about AWS compatibility issues?

Currently, the test is simulated in the Integration test. As when this flag is enabled user has chosen to consider key as unix paths. I will add a test suite in HDDS-4154. For now, all tests are in integration tests.
  <property>
    <name>ozone.om.enable.filesystem.paths</name>
    <tag>OZONE, OM</tag>
    <value>false</value>
    <description>If true, key names will be interpreted as file system paths.
      "/" will be treated as a special character and paths will be normalized
      and must follow Unix filesystem path naming conventions. This flag will
      be helpful when objects created by S3G need to be accessed using OFS/O3Fs.
      If false, it will fallback to default behavior of Key/MPU create
      requests where key paths are not normalized and any intermediate
      directories will not be created or any file checks happens to check
      filesystem semantics.
    </description>
  </property>

So, test/file/ will be normalized to test/file. This PR provides user ability to read with the same file name user has used during the creation of key "test/file/".

@elek Any more comments?

@elek Any more comments?

Looks like we don't have the consensus, yet, in HDDS-4097. It was discussed yesterday during the community meeting, and I felt that everybody agree more or less, but I am not sure if @arp7 fully agrees.

What is your opinion about AWS compatibility issues?

What exactly is the compatibility issue? If the paths are not interpreted (default behavior), then there is full AWS compatibility.

@elek
There is no issue with this. As the other argument is when the flag is disabled to support HCFS.
And I believe we have agreed on the part we need this like 100% HCFS with few changes to AWS S3 semantics.
Let me know if you have any concerns.

I uploaded my proposal to https://issues.apache.org/jira/browse/HDDS-4097, please let me know your opinion.
I think the normalization should be optional and should be driven by a configuration which is independent of the intermediate directory creation (ozone.om.enable.filesystem.paths).
While intermediate directories are a must-have for providing services for both S3 and HCFS, normalization seems to be an optional (but very useful) feature.

I have rebased this PR.
cc @elek @arp7


fix(platform-serverless): add support of REQUEST type lambda authorizer

Information

Type
Breaking change

fix
No

Information
This PR improve support of lambda authorizer for the REQUEST type event
Todos

[x] Tests
[x] Coverage
[x] Example
[x] Documentation

:tada: This PR is included in version 7.79.4 :tada:
The release is available on:

v7.79.4
GitHub release

Your semantic-release bot :package::rocket:


Set default digital number format to minFrac=0, maxFrac=9

It's a bit late to be making changes like this, but since we keep approving them, I'll suggest another
new Intl.DurationFormat("en", { style: "digital" }).format({ seconds: 1, milliseconds: 230 });

I think the above line should display "1.23 seconds".
This can be accomplished by setting the default second format to minFrac=0, maxFrac=9.

I support the change of defaults but we should nonetheless discuss, especially the change of options for DurationFormat.

Yes. There are a few options here:

Keep things as spec'd.
Change the default maximumFractionDigits to 9, but the fractionalDigits setter continues to work the same.
Change the default maximumFractionDigits to 9, and also change the options to be [min/max]imumFractionDigits instead of fractionalDigits.

TG2 approval: https://github.com/tc39/ecma402/blob/master/meetings/notes-2023-04-06.md#set-default-digital-number-format-to-minfrac0-maxfrac9-144


docs incorrects for 'how to customize templates' section

Hi there!
There is an error in the docs, specifically in the [how to customize templates section].(https://django-oscar.readthedocs.io/en/2.1.0/howto/how_to_customise_templates.html)
According to issue #1378, the base.html mentioned in the examples should be in 'templates/oscar/base.html' instead of 'templates/base.html'.
I'm new to django oscar, and I spent a couple of hours before I could realize what were wrong, so I think it would be very helpful to new devs :)
Regards!

Hi!
I'm reading this part of the docs also and I cannot figure out how to customize the templates. I tried what you said here but nothing changes apparently.
Could you explain a little bit about the correct steps to customize the templates?
Thanks a lot!

@hungiscoding please use Stack Overflow using the django-oscar tag, or our slack workspace or mailing list for help.


pip install h2o4gpu fails on Windows 10, 64-bit env

Environment (for bugs)

OS platform, distribution and version (e.g. Linux Ubuntu 16.04):  Windows 10
Installed from (source or binary):
Version:
Python version (optional):  3.6.6
CUDA/cuDNN version:  9.0/7.2
GPU model (optional):  nVidia Geforce 1070
CPU model:  i7
RAM available:  16GB

Description
After cloning the h2o4gpu into my projects directory,
cd D:\projects\h2oai\h2o4gpu
pip install h2o4gpu

Running pip install fails

running install
running build
Traceback (most recent call last):
File "setup.py", line 125, in
cmdclass={'bdist_wheel': bdist_wheel, 'build': H2O4GPUBuild, 'install': H2O4GPUInstall},
File "C:\ProgramData\Anaconda3\lib\site-packages\setuptools_init_.py", line 140, in setup
return distutils.core.setup(**attrs)
File "C:\ProgramData\Anaconda3\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "C:\ProgramData\Anaconda3\lib\distutils\dist.py", line 955, in run_commands
self.run_command(cmd)
File "C:\ProgramData\Anaconda3\lib\distutils\dist.py", line 974, in run_command
cmd_obj.run()
File "setup.py", line 62, in run
install.run(self)
File "C:\ProgramData\Anaconda3\lib\site-packages\setuptools\command\install.py", line 65, in run
orig.install.run(self)
File "C:\ProgramData\Anaconda3\lib\distutils\command\install.py", line 545, in run
self.run_command('build')
File "C:\ProgramData\Anaconda3\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "C:\ProgramData\Anaconda3\lib\distutils\dist.py", line 974, in run_command
cmd_obj.run()
File "setup.py", line 21, in run
EXT = ".dylib" if os.uname()[0] == "Darwin" else ".so"
AttributeError: module 'os' has no attribute 'uname

@cpoptic we don't support Windows.

Hello,
I wonder if there have been any developments to getting h2o4gpu on Windows 10.
Thank you!


Make writing output files in a separate process

Writing the data to disk is a bottleneck for the application. We could make writing to disk as another process to free up the main process for submitting new tasks

We compute energies of 16 heavy atom molecules faster than we can write them to disk with 128 nodes.


Expo: Not able drag in simulator but on real device works fine

After upgrade all libs to latest i am not able to drag in simulator but on real device works fine
Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

Platform: ios simulator
React Native or Expo version: Expo "^41.0.0",
Reanimated version: "^2.1.0",
React Native Gesture Handler version: "~1.10.2",

same issue here

a repro snack would be helpful

I use react native cli, and am not too familiar with expo versions. I am unable to reproduce it in a snack but will keep trying. here's a list of my app's dependencies and the snack I'm working with so far.
{   "name": "AppName",   "version": "0.0.1",   "private": true,   "scripts": {     "start": "react-native start",     "test": "jest",     "lint": "eslint app --ext .js",     "react-devtools": "react-devtools",     "postinstall": "npx jetify",     "storybook": "start-storybook",     "build-storybook": "build-storybook",     "prestorybook": "rnstl"   },   "config": {     "react-native-storybook-loader": {       "searchDir": [         "./app/Component/",         "./app/Templates/",         "./app/Screens/"       ],       "pattern": "**/*.stories.js",       "outputFile": "./storybook/storyLoader.js"     }   },   "build:ios": "react-native bundle --entry-file='index.ios.js' --bundle-output='./ios/asumobileapp/main.jsbundle' --dev=false --platform='ios' --assets-dest='./ios'",   "dependencies": {     "@apollo/client": "3.4.0-beta.1",     "@react-native-community/art": "^1.2.0",     "@react-native-community/async-storage": "^1.12.0",     "@react-native-community/checkbox": "^0.5.5",     "@react-native-community/clipboard": "^1.5.1",     "@react-native-community/datetimepicker": "^3.0.9",     "@react-native-community/geolocation": "^2.0.2",     "@react-native-community/masked-view": "^0.1.10",     "@react-native-community/netinfo": "^6.0.0",     "@react-native-community/push-notification-ios": "^1.5.0",     "@react-native-firebase/analytics": "^11.0.0",     "@react-native-firebase/app": "^11.0.0",     "@react-native-firebase/crashlytics": "^11.0.0",     "@react-native-firebase/perf": "^11.0.0",     "@react-navigation/material-top-tabs": "^5.3.15",     "@react-navigation/native": "^5.8.10",     "@react-navigation/stack": "^5.12.8",     "@turf/helpers": "^6.0.1",     "apollo-cache-inmemory": "^1.6.6",     "apollo-client": "^2.6.10",     "appcenter": "4.1.0",     "appcenter-analytics": "4.1.0",     "appcenter-cli": "^2.7.1",     "appcenter-crashes": "4.1.0",     "apsl-react-native-button": "^3.1.0",     "aws-appsync": "^4.0.1",     "aws-appsync-auth-link": "^3.0.2",     "aws-appsync-react": "^4.0.1",     "aws-appsync-subscription-link": "3.0.3",     "aws-sdk": "^2.883.0",     "aws4-react-native": "^0.0.2",     "axios": "^0.21.0",     "code-push": "4.0.4",     "core-js": "^3.8.1",     "crypto-js": "^4.0.0",     "graphql": "^15.4.0",     "graphql-tag": "^2.11.0",     "jsc-android": "^250230.2.1",     "lodash": "^4.17.20",     "lottie-ios": "3.1.8",     "lottie-react-native": "^4.0.2",     "md5": "^2.2.1",     "metro-react-native-babel-preset": "^0.65.1",     "moment": "^2.21.0",     "moment-timezone": "^0.5.21",     "npm": "^7.9.0",     "prop-types": "^15.6.0",     "react": "17.0.2",     "react-apollo": "2.5.8",     "react-dom": "^17.0.1",     "react-native": "0.63",     "react-native-android-location-services-dialog-box": "^2.4.4",     "react-native-animatable": "^1.3.2",     "react-native-app-link": "^1.0.0",     "react-native-background-fetch": "3.1.0",     "react-native-background-geolocation-android": "CustomPackUrl",     "react-native-barcode-builder": "^2.0.0",     "react-native-base64": "^0.2.1",     "react-native-button": "^3.0.1",     "react-native-calendar-events": "^2.1.0",     "react-native-calendars": "1.403.0",     "react-native-cards": "^1.1.4",     "react-native-code-push": "^7.0.0",     "react-native-collapsible": "^1.5.3",     "react-native-communications": "^2.2.1",     "react-native-cookies": "^3.2.0",     "react-native-dev-menu": "^4.0.2",     "react-native-device-info": "^8.0.0",     "react-native-draggable-flatlist": "^2.6.2",     "react-native-dropdown-picker": "^3.7.0",     "react-native-easy-grid": "^0.2.2",     "react-native-easy-toast": "^2.0.0",     "react-native-elements": "^3.0.0",     "react-native-error-boundary": "^1.1.6",     "react-native-event-listeners": "^1.0.3",     "react-native-exit-app": "^1.0.0",     "react-native-fab": "^1.0.17",     "react-native-flipper": "0.84.0",     "react-native-gesture-handler": "^1.10.3",     "react-native-htmlview": "^0.16.0",     "react-native-image-progress": "^1.1.1",     "react-native-imei": "^0.2.0",     "react-native-keychain": "^6.2.0",     "react-native-linear-gradient": "^2.5.6",     "react-native-localize": "^2.0.0",     "react-native-modal": "^11.0.1",     "react-native-modal-dropdown": "CustomPackageUrl",     "react-native-permissions": "^3.0.0",     "react-native-popup-menu": "^0.15.6",     "react-native-push-notification": "CustomPackageUrl",     "react-native-qrcode2": "^0.3.0",     "react-native-randombytes": "^3.6.0",     "react-native-reanimated": "^2.1.0",     "react-native-responsive-dimensions": "^3.1.1",     "react-native-responsive-image": "^2.3.1",     "react-native-restart": "^0.0.22",     "react-native-safari-view": "^2.1.0",     "react-native-safe-area-context": "^3.1.9",     "react-native-screens": "^2.0.0-alpha.34",     "react-native-secure-key-store": "^2.0.9",     "react-native-sensitive-info": "^5.5.8",     "react-native-share": "^5.1.0",     "react-native-simple-radio-button": "^2.7.1",     "react-native-size-matters": "^0.4.0",     "react-native-skeleton-content": "^1.0.20",     "react-native-snap-carousel": "3.9.1",     "react-native-sortable-grid": "^2.0.0",     "react-native-sortable-list": "^0.0.24",     "react-native-splash-screen": "^3.1.1",     "react-native-svg": "^12.1.1-0",     "react-native-svg-charts": "^5.3.0",     "react-native-swipeable": "^0.6.0",     "react-native-switch": "^2.0.0",     "react-native-tab-view": "^2.16.0",     "react-native-table-component": "^1.2.1",     "react-native-text-ticker": "^1.12.0",     "react-native-torch": "^1.1.3",     "react-native-vector-icons": "^8.0.0",     "react-native-vitals": "^2.0.1",     "react-native-webview": "^11.0.0",     "reactotron-react-native": "^5.0.0",     "rn-async-storage-flipper": "^0.0.9",     "use-global-hook": "^0.2.1"   },   "devDependencies": {     "@babel/core": "^7.13.15",     "@babel/runtime": "^7.12.5",     "@react-native-community/eslint-config": "^2.0.0",     "@react-navigation/drawer": "^5.11.4",     "@storybook/addon-actions": "^6.2.5",     "@storybook/addon-essentials": "^6.2.5",     "@storybook/addon-knobs": "^6.2.5",     "@storybook/addon-links": "^6.2.5",     "@storybook/addon-ondevice-actions": "^5.3.23",     "@storybook/addon-ondevice-knobs": "^5.3.23",     "@storybook/react-native": "^5.3.23",     "@storybook/react-native-server": "^5.3.23",     "babel-eslint": "^10.0.2",     "babel-loader": "^8.1.0",     "babel-plugin-module-resolver": "^4.0.0",     "babel-plugin-transform-remove-console": "^6.9.4",     "enzyme": "^3.11.0",     "enzyme-adapter-react-16": "^1.15.4",     "enzyme-to-json": "^3.5.0",     "eslint": "^7.8.1",     "eslint-config-airbnb": "^18.2.0",     "eslint-config-prettier": "^8.1.0",     "eslint-plugin-import": "^2.18.2",     "eslint-plugin-jsx-a11y": "^6.2.3",     "eslint-plugin-prettier": "^3.1.0",     "eslint-plugin-react": "^7.23.1",     "jest": "^26.6.3",     "prettier": "^2.1.1",     "react-devtools": "^4.8.2",     "react-native-storybook-loader": "^2.0.2",     "react-test-renderer": "^17.0.1"   },   "jest": {     "preset": "react-native",     "transform": {       "^.+\\.js$": "<rootDir>/node_modules/react-native/jest/preprocessor.js"     },     "transformIgnorePatterns": [       "node_modules/(?!(jest-)?react-native|react-navigation|react-clone-referenced-element|expo|@expo/*|exponent|@exponent/*)"     ],     "snapshotSerializers": [       "enzyme-to-json/serializer"     ]   },   "rnpm": {     "assets": [       "./assets/fonts"     ]   } }

ok thanks for looking, without a repro i'm flying blind. I just checked out an expo bare app with the same specs as OP and was able to drag in ios simulator.

Experiencing same issue on iOS. Android simulator works fine.

So it seems simulator iPhone 11 13.3 does not work, but iPhone 12 14.3 simulator works

It seems if I have React-Native debug mode on then it doens't work on iOS simulator, but if I disable it, then it starts working again.

Its not relates to simulator or device
its relates to with debugger or not
when not debugger works fine
with debugger not working

Thanks @ButuzGOL ,
Try to stop debugging

Its not relates to simulator or device its relates to with debugger or not
when not debugger works fine with debugger not working

This works for me, but what is the reason?


Render Error: Cannot assign to read-only property 'current'

Call Stack:
useSetupRefs
RefProvider
const animationConfigRef = useRef(animConfig);
animationConfigRef.current = animConfig;
it crashes when trying to set animationConfigRef value
Describe the bug
This bug only occurs in Debug mode but it's working fine in release mode.
The initial render for the screen works fine but in case of triggering rerender when any state changes it crashes with this error.
This is different to what's mentioned in the issue #496 where the bug could be solved by passing a function that returns a component to ListHeader, in my case even removing ListHeader component doesn't solve the issue.
To Reproduce
         <DraggableFlatList           horizontal           showsHorizontalScrollIndicator={false}           activationDistance={30}           data={subImagesUris}           keyExtractor={item => item}           contentContainerStyle={{paddingVertical: 8}}           onDragEnd={({data}) => {             applyNewOrder(data);           }}           renderItem={({item, drag, isActive}) => (             <ScaleDecorator>               <Pressable                 key={item}                 onPress={() => onSelect(item)}                 onLongPress={() => {                   Vibration.vibrate();                   setTimeout(() => {                     Vibration.cancel();                   }, 50);                   drag();                 }}                 delayLongPress={125}                 disabled={isActive}>                 <Image style={styles.subContainer} source={{uri: item}} />               </Pressable>             </ScaleDecorator>           )}           ListFooterComponent={             subImagesUris.length >= 10 ? undefined : (               <TouchableOpacity style={styles.pickSubImageButton} onPress={onPickSubImages}>                 <AddCircularIcon />               </TouchableOpacity>             )           }         />
Note that in my my case it's enough to render the component with much simpler props and error would still occur in debug mode.
Platform & Dependencies
Please list any  applicable dependencies in addition to those below (react-navigation etc).

react-native-draggable-flatlist version: 4.0.1
Platform: Android, iOS
React Native : 4.0.1
Reanimated version: 4.0.1
React Native Gesture Handler version: 4.0.1

Same issue

Duplicate #496

The fix can be found here in PR 484
It has not been committed by the maintainer/s of this lib, but I have used it and it resolves the issue. Apply it using patch-package. All credit to NoahCardoza


Update documentation to reflect updates to LandCoverChanges

Provide description of InsectDefoliation functionality
Describe repeat harvest functionality for LandCoverChanges
Describe how to specify order of application of LandCoverChanges

Can we make this a priority? We have been trying to test the changes to the model but I can't figure out how to invoke these. I tried RepeatHarvest everywhere I could think of but the model didn't like it. From  looking at the code it looks like it is invoked from within the LandCover?

Yes I'll update this ASAP as I've made significant changes to the way the landuse.txt file is written and parsed to control modifications to land uses.

Closing for update to 1.3


Driver level search index APIs

Codecov Report
Base: 82.78% // Head: 81.98% // Decreases project coverage by -0.80% :warning:

Coverage data is based on head (c970a86) compared to base (cc664ca).
Patch coverage: 75.56% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #234      +/-   ##
==========================================
- Coverage   82.78%   81.98%   -0.80%
==========================================
  Files          30       32       +2
  Lines        2893     3248     +355
==========================================
+ Hits         2395     2663     +268
- Misses        369      437      +68
- Partials      129      148      +19

Impacted Files
Coverage Δ

driver/driver.go
87.10% <ø> (ø)

driver/internal.go
93.75% <ø> (ø)

driver/types.go
0.00% <ø> (ø)

driver/search_http.go
72.13% <72.13%> (ø)

driver/search_grpc.go
78.44% <78.44%> (ø)

driver/grpc.go
86.01% <100.00%> (+0.10%)
:arrow_up:

driver/http.go
76.01% <100.00%> (+0.06%)
:arrow_up:

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

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


Migrate Move alarm to spring boot 2

at MoveAlarmServ folder it contain spring boot project pls migrate to spring boot version 2.0.6

Hi,
I would like to start work on this


Is there a way to set attributes on a list?

What happened?
There is no way to set attributes on a list, i.e. to get an AST like:
{
  "type": "list",
  "attributes": {
    "ordered": false,
    "foo": "bar"
  }
}

To reproduce
I tried various ways to set attributes on a list, such as
{% #mylist %}
- one
- two

However, none resulted in a list node with attribute "id": "mylist".
Version
0.1.4
Additional context
I know I can set attributes on heading and paragraph nodes with syntax like:
# Header {% #custom-id %}

However, I don't know how to set such attributes on other node types, like list, image, em, etc., or whether this is even possible.
(If it's not possible, that's basically fine. I'll instead define a custom tag that accepts these attributes. But I would like to know whether it's possible to set these attributes directly on a list first.)

I'll instead define a custom tag that accepts these attributes.
This is exactly what we do at Stripe, and it is likely the best way to handle it today.

We have previously considered the possibility of creating a built-in tag in Markdoc that applies its attributes to its direct descendent—something like this:
{% apply #foo bar="baz"  %}
* This is a bulleted list
{% /apply %}

We decided that we preferred to have explicit tags like list in userspace, but I'm very open to revisiting the apply feature if there's sufficient interest. We'd want to special-case it in the validator and other places so that it works as expected (the validator would make sure that the attributes on it are valid for the element that it surrounds).

Closing this issue with the answer from @rpaul-stripe above. @jameshfisher please feel free to open a new issue, or question in our discussions forum (https://github.com/markdoc/markdoc/discussions) instead.


Loading the config files too soon

Hello,
I'm having an issue with the config files being loaded too soon I think.
Do you happen to load them in the package ?
I load the config files of the modules in my core service provider's boot method.
It looks like you do that in the register method or something. Could you wrap that around a this->app->booted closure ? To be sure laravel is booted before loading the config files?
Thanks

Hm the register method is ran before the boot method. So it's loading even sooner now.


Allow nodeIntegration

Allows nodeIntegration, with false as default value

@gatsbimantico hi and thanks for the contribution 🙂.

A little context, please. Why this? What does it do? What does it fixes? What does it enable?
Why make it an option? Nativefier already has totally waaaaaaaay too many options. Can/should we make this default instead?
If you confirm an option is the right thing to do, docs (md & CLI) docs please. Here's a recent simple PR that you can use as example: https://github.com/jiahaog/nativefier/pull/747/files

@ronjouch thank you for reviewing 🙂.

Context
This edit allows you to keep access to node in the app, allowing you to call require in the front-end. It doesn't do anything extra, mostly because websites do not expect you to have access to node in the browser. But allows you to build apps and use nativefier to package them, that do use node.

Why an option?
The value was hardcoded as false, because (as a comment in the code says "might conflict with global variables in sites like messenger.com", so the default can not be true.

I'll work on the changes requested soon.

Already fixed by https://github.com/jiahaog/nativefier/pull/826 , closing.


More Access to a JsonExportable's Metadata

A motivation for this change

Fixes the lack of access to post data that is only accessable through the instagram-private-api (e.g. saved_collection_ids).
added get_json_structure(structure: JsonExportable) function to be an attribute of an Instaloader instance. This allows for the access of post data that is not directly accessible through the Instaloader API (e.g. saved_collection_ids).

The completeness of this change

Is it just a proof of concept? No
Is the documentation updated (if appropriate)? No
Do you consider it ready to be merged or is it a draft? Read to be merged
Can we help you at some point? Sure!

The implementation does not seem well though-through. The Post._iphone_struct method is simply duplicated and private methods are called from outside of the class.


Support for IdP creation

Hello,
Does this crate support building an IdP? It seems that there are bits only to build an app as SP.

Currently, no, though someday it likely will

Hi @njaremko
This post is old. There are currently support to create an IDP?
Thanks!

Yes, you can make an IDP now

Could you please give an example?

Writing an IdP is non-trivial. See https://github.com/oxidecomputer/omicron/blob/5f52a74592948b4a6417edfb3457065fe4dd162f/nexus/db-queries/src/authn/silos.rs#L27


React Native & React version upgrade

React Native version upgrade to 0.66.3
React version upgrade to 17.0.2

 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.

 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.


Resolution for retina: (2560 x 1600)

I'm running the native resolution on my Macbook (2560 x 1600) and the screensaver looks terrible.  Is there anything that can be done about this?

@Mochlate The videos are created by Apple for the 720p Apple TV. If you want higher resolution videos, I'm sorry but you'll need to speak to them. :)


[Cosmos V4] evaluate the correctness of volatile variable increment

Volatile member variables are incremented. These increments don't guarantee atomicity for "read|increment|update". Double-check whether these increments are intended to be called from multiple threads if yes then switching to AtomicInteger is safe if no concurrency involved then volatile could be removed.
https://github.com/Azure/azure-sdk-for-java/blob/591d77d6260d9da8a148d1f1ffda2372c4a06143/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/RetryPolicyWithDiagnostics.java#L54
https://github.com/Azure/azure-sdk-for-java/blob/591d77d6260d9da8a148d1f1ffda2372c4a06143/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/changefeed/implementation/AutoCheckpointer.java#L64
https://github.com/Azure/azure-sdk-for-java/blob/591d77d6260d9da8a148d1f1ffda2372c4a06143/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/query/DefaultDocumentQueryExecutionContext.java#L153

Ref: https://errorprone.info/bugpattern/NonAtomicVolatileUpdate

Working on this.


downgrade packer to 1.9.2

It was observed recently in Metal3 CI, that packer was producing tcp errors at the last stage of the image build process. The images were built and uploaded correctly but packer still finished the build process with a tcp error (sanitized):
==> openstack: Error creating image: Post "https://<ostack_api_url>/v3/<proj_id>/volumes/<volume_id>/action":
    read tcp ip:port->ip2:port2: read: connection reset by peer

==> openstack: Provisioning step had errors: Running the cleanup provisioner, if present...

==> openstack: Deleted temporary floating IP '<floating_ip_id>' (<floating_ip>)

==> openstack: Terminating the source server: <vm_id> ...

==> openstack: Error terminating server, may still be around: Resource not found

==> openstack: Waiting for volume packer_<hash> (volume id: <volume_id>) to become available...

==> openstack: Deleting volume: <volume_id> ...

Build 'openstack' errored after 12 minutes 50 seconds: Error creating image:
Post "https://<ostck_url>/v3/<proh_id>/volumes/<volume_id>/action": read tcp ip:port->ip2:port2:
read: connection reset by peer

The issue could be caused by a packer bug or incompatibility somewhere between the packer, the packer OpenStack plugin and the OpenStack.
This commit:

Downgrades the packer version to the previous version in hopes of getting rid of the tcp issue.

/test-integration-metal3-dev-tools-centos
/ test-integration-metal3-dev-tools-ubuntu

/test-integration-metal3-dev-tools-centos
/test-integration-metal3-dev-tools-ubuntu

/test-integration-metal3-dev-tools-centos
/test-integration-metal3-dev-tools-ubuntu

/test-integration-metal3-dev-tools-centos
/test-integration-metal3-dev-tools-ubuntu

/test-integration-metal3-dev-tools-centos
/test-integration-metal3-dev-tools-ubuntu

/test-integration-metal3-dev-tools-centos

/test-integration-metal3-dev-tools-centos

/test-integration-metal3-dev-tools-centos

/hold


docker-engine RC versions for 1.13.0 have disappeared from Ubuntu repos!

I'm working with docker-engine 1.13.0 rc2 for a a couple of weeks, and today trying to install docker engine on the new machine, I got this message:
stderr: E: Version '1.13.0~rc2-0~ubuntu-trusty' for 'docker-engine' was not found
And indeed the list of version in https://apt.dockerproject.org/repo/dists/ubuntu-trusty/testing/filelist does not include any of 1.13.0 RC version any more!
Is it a mistake? When it's going to be fixed??
It a HUGE BLOCKER for my work!

cc @andrewhsu

I can confirm the filelist does not contain the correct contents. Working on a fix at the moment.

@liyaka fixed in production now, the filelist should have 1.13.0

Thank you!

Thanks @andrewhsu, and apologies for the hiccup @liyaka
I'll close this issue, as it's resolved


Allow DRY definition of branch names in file content verification steps

Right now, the file content verification step looks like this:
And now I have the following committed files
  | BRANCH   | FILES            | CONTENT          |
  | feature2 | feature2_file    | feature2 content |
  | feature2 | conflicting_file | main content     |

It would be better if it looked like this:
And now I have the following committed files
  | BRANCH   | FILES            | CONTENT          |
  | feature2 | feature2_file    | feature2 content |
  |          | conflicting_file | main content     |

Blocking on #435


Az appconfig kv set error if value containing close bracket

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug

Updating/Creating with value that contains ")" close bracket will generate error.
Example, when running following command
'az appconfig kv set --value ")test" '
it will return error message:  test was unexpected at this time.
To Reproduce

Run 'az appconfig kv set --value ' , and set the value to any string that contains ).
Expected behavior

The command should insert the value without error.
Environment summary

Windows 10
Az cli version
{
"azure-cli": "2.17.1",
"azure-cli-core": "2.17.1",
"azure-cli-telemetry": "1.0.6",
"extensions": {
"azure-firewall": "0.8.0",
"ip-group": "0.1.2",
"logic": "0.1.2"
}
}
Additional context

appconfig

appconfig

Possibly the problem in the windows cmd shell.
Command:  az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json
Will be translated to following cmd call
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value )TestValue --label TEST --yes -y --content-type application/json
The close bracket value are not written inside double quotes. I think instead of )TestValue , it should be ")TestValue"  - with double quotes like this :
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value ")TestValue"  --label TEST --yes -y --content-type application/json

Possibly the problem in the windows cmd shell.
Command:  az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json
Will be translated to following cmd call
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value )TestValue --label TEST --yes -y --content-type application/json
The close bracket value are not written inside double quotes. I think instead of )TestValue , it should be ")TestValue"  - with double quotes like this :
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value ")TestValue"  --label TEST --yes -y --content-type application/json

I can confirm the double quotes solve the problem.
I hope the team can make this simple changes.

Possibly the problem in the windows cmd shell.
Command: az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json
Will be translated to following cmd call
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value )TestValue --label TEST --yes -y --content-type application/json
The close bracket value are not written inside double quotes. I think instead of )TestValue , it should be ")TestValue" - with double quotes like this :
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json

I can confirm the double quotes solve the problem.
I hope the team can make this simple changes.

Possibly the problem in the windows cmd shell.
Command: az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json
Will be translated to following cmd call
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value )TestValue --label TEST --yes -y --content-type application/json
The close bracket value are not written inside double quotes. I think instead of )TestValue , it should be ")TestValue" - with double quotes like this :
"C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin..\python.exe" -IBm azure.cli appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y --content-type application/json

Hi @cakriwut, if you are trying to create a key-value with JSON content type (--content-type application/json), the value must be an escaped JSON string. Please see this document for more info on JSON key-values in AppConfig: https://docs.microsoft.com/en-us/azure/azure-app-configuration/howto-leverage-json-content-type#create-json-key-values-using-azure-cli

Hi @cakriwut, if you are trying to create a key-value with JSON content type (--content-type application/json), the value must be an escaped JSON string. Please see this document for more info on JSON key-values in AppConfig: https://docs.microsoft.com/en-us/azure/azure-app-configuration/howto-leverage-json-content-type#create-json-key-values-using-azure-cli

Hi @avanigupta , it doesn't help.
az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y
Please try on following environment.

Windows Powershell => ERROR.
Windows CMD  => OK

Problem
When running az cli command from Powershell, it seems invoking "phyton.exe" azure.cli  {args}. However the arguments are not quoted.

Hi @avanigupta , it doesn't help.
az appconfig kv set -n appconfig --key TestKEY --value ")TestValue" --label TEST --yes -y
Please try on following environment.

Windows Powershell => ERROR.
Windows CMD  => OK

Problem
When running az cli command from Powershell, it seems invoking "phyton.exe" azure.cli  {args}. However the arguments are not quoted.

@cakriwut, there is a known issue with parsing quotes in Powershell. This document can better explain the error you're seeing.
To prevent this error, you may use stop-parsing symbol --% between az and arguments.

@cakriwut, there is a known issue with parsing quotes in Powershell. This document can better explain the error you're seeing.
To prevent this error, you may use stop-parsing symbol --% between az and arguments.

Today while I using azure static app, I write this command
az staticwebapp appsettings set -n anirudhagupta4september1040 --setting-names MONGO_CONNECTION_STRING="commentedforprivacy/?retryWrites=true&w=majority"

I am getting error like ''w' is not recognized as an internal or external command,
operable program or batch file.'
@avanigupta  @cakriwut
Any idea to make it work. I tried both double quote and (""). None of both is solving the issue. I have reported it on static-app cli as well https://github.com/Azure/static-web-apps-cli/issues/551


using templateCache to load views

wait wait wait, I've committed to master, I'm closing this one to open a new PR from a branch, my bad, sorry


New Relic release tracking

Jira link
HOTT-n/a
What?
I have added/removed/altered:

[ ] Track releases in NewRelic

Why?
I am doing this because:

To see the release timeline in the NewRelic monitoring.

Have you? (optional)

[ ] Reviewed view changes with stake holders
[ ] Validated mobile responsive behaviour of view changes

Deployment risks (optional)

Makes changes to our complex routing setup that may affect apis to proxying to backend

Putting this back in the backlog as it need bigger changes in the CI jobs to get the Application ID dynamically


[KYUUBI #3911] Bump Jackson from 2.13.4 to 2.14.1

Why are the changes needed?

to close #3911 .
Bump Jackson from 2.13.4 to 2.14.1.

From 2.14, Java8 is required
v2.14.1 fixed heap consumption increased from 2.13.x to 2.14.0

Relase notes for 2.14 and 2.14.1
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14
https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.14.1
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

thanks @bowenliang123 and @Yikf, merged to master


Changes to work with Fedora-Camel 5.0.0

JIRA Ticket: https://jira.duraspace.org/browse/FCREPO-2787
Related PR: https://github.com/fcrepo4-exts/fcrepo-camel/pull/150
What does this Pull Request do?
Most of this is @dbernstein's work from before, I just dragged it across a line.
What's new?
I checked out a bunch of things from @dbernstein's update-fcrepo-parent-pom branch but stuck with the older versions of dependencies.
How should this be tested?
Should build and then you could try testing it out. I am going to try it in fcrepo-vagrant soon.
Additional Notes:
Example:

Does this change require documentation to be updated? no
Does this change add any new dependencies? no
Does this change require any other modifications to be made to the repository (ie. Regeneration activity, etc.)? no
Could this change impact execution of existing code? no

Interested parties
@peichman-umd @birkland @dbernstein or any other interested @fcrepo4/committers

I hope this works for you all, but it passed on my machine and I was like

Failure is due to log length, log length is due to seemingly a tonne of duplicate class in the Fedora war.

So yeah, Shiro seems to have classes included in multiple places or maybe its just the way Jetty scans but I started to try and exclude some artifacts in fcrepo-webapp and realized I had to pretty much exclude everything. So either we have waaay to much of shiro included as dependencies or Jetty 9.3 is just causing trouble

Yeah I maybe I don't understand what Shiro is trying to do but they have the same classes in different packages and then they have dependencies between those packages (ie. shiro-config-ogdl has a dependency on shiro-config-core)?
[/Users/whikloj/.m2/repository/org/apache/shiro/shiro-config-ogdl/1.4.0]
> unzip -t shiro-config-ogdl-1.4.0.jar | grep ConfigurationException -
    testing: org/apache/shiro/config/ConfigurationException.class   OK

[/Users/whikloj/.m2/repository/org/apache/shiro/shiro-config-core/1.4.0]
> unzip -t shiro-config-core-1.4.0.jar | grep ConfigurationException -
    testing: org/apache/shiro/config/ConfigurationException.class   OK

Ok this is an open issue for Shiro https://issues.apache.org/jira/browse/SHIRO-632

@whikloj : I'm going to put a picture of you on my desk and recall the good that you have done each day.  YES! It works and has taught me the value of restraint when it comes to unnecessary dependency updates.

@whikloj: Looks like it needs a rebasing as well when you get a chance.

@dbernstein I'll rebase this, I also want to see if I can bump the camel version 2.20 as that would alleviate the security warnings.
I'll also note it wasn't necessarily the dependencies causing the problems, two of the tests in fcrepo-service-camel were actually failing.
We used to emit 2 messages for a CREATE (one for the item and one for the parent). But now we emit 3 (one for item, one for parent and one for versions container).


Savings account:Need to remove.

If we are not showing the savings account on the home page then there is no point in showing it here on the account management screen.The mention of Savings account needs to be removed from everywhere.

I have tested this, It is not appearing on my side.

I can see the savings account in account management section.Tested on dev app v2.0.80(480)

Verified this issue on dev app v2.0.80(483)


No Rule to Make Target on Mac OSX

Expected behavior
Should continue compile of ACE
Actual behavior/symptoms
Halts compile and exits..
make[2]: *** No rule to make target 3rd_party/built/lib/libACE.so', needed by out/AuthExerciser'.  Stop.
make[1]: *** [Projects/CoX/Utilities/AuthExerciser/CMakeFiles/AuthExerciser.dir/all] Error 2
make: *** [all] Error 2
21:45:12: The process "/usr/local/bin/cmake" exited with code 2.
Steps to reproduce behavior/symptoms
Run Build All in Qt5 on Mac OS X
SEGS version
0.4.0 alpha
Operating system
Mac OS Sierra 10.12.6
C++ compiler and version
cmake version 3.10.2

Has this been resolved by #266?

We need someone to test it on the apple-pie machine :)

I’ll be happy to give this a go tomorrow while the Padawan is sleeping. 😃

Re puled the code, recompiled and works fine!


Design HCA hand-off of Matrix Service output to Terra

From https://docs.google.com/document/d/1qs_r6tBxgRYI4t52Us01WpKKFICReYiUQIP_HhPHtsY:
Brian - Data Browser/Data Store
We need handoff to Terra so search results in the portal can create workspaces in the Terra platform, available for arbitrary analysis using WDL (tutorial 2 above)
We need something from tutorial 1 that we can write a WDL for, UCSC can write the WDL version given our experience
We need a URL for a matrix service produced so we can cut and paste into a Jupyter notebook (tutorial 3 above) -- DONE, I see URLs are created as part of requesting a matrix such as this one.  Not sure how long the URLs last for.
handle the Jupyter notebook server setup via Terra
Updated vignette for the Jupyter notebook analysis
The UI on the Browser might need to be tweaked to better support slow matrix responses if the speed improvements don’t get us below 1 min
We need to write the tutorials with the partners above
Unassigned:
We need someone to take point on creating a vignette for local analysis that covers “support researchers downloading and conducting data comparisons on their own laptop”
We need someone to take point on creating (updating) a vignette for use in Terra’s Jupyter notebook system, really like this to be an updated version of Genevieve's notebook from our previous demo (“HCA Scanpy Demo”)
From https://docs.google.com/document/d/1-okI41MzQhAiTeX9uQXDg9yTBSKvGDV-mSNV_5sN09E:
Meeting notes from 12/20/2018: the URL is an https:// path, and it shouldn't change. In this case, the handoff happens from the matrix service. We envisioned that a row in Terra would include just 2 columns: URL to HCA data browser that's used to generate the matrix, and an https:// path that points to the matrix file. This will only handoff 1 matrix at a time, and the matrix is aggregated, and there is always 1 row in the table. In the future, we can look into handing over multiple matrix at a time. We also learned that a retry mechanism to retrieve the https:// URL is needed, and we will need to discuss further technical details.
Matrix Service: exports gene expression matrices in CSV, Loom, and MTX.  Has UI, available for experimentation now.
HCA Matrix Service endpoint will return a URL that Terra service can poll while HCA servers prepare matrix data for download.

Closing - planning to retire the DCP/1 Matrix Service.


Run callbacks when a dir is loaded/unloaded

It could be helpful to let the user run custom callbacks whenever a project dir is loaded or unloaded. This would provide a way to automatically load sessions created with plugins like vim-obsession.

Another potential use for the callback would be to switch virtualenv when working with multiple python projects.

This would solve many problems I have.


[11.x] Remove isset assumption on MYSQL Schema Connection

It is common for PDO::MYSQL_ATTR_SSL_CA to be set in database.php but have it disabled or empty, normally controlled by as an environment variable.
In the MySQL schema state, it is assumed that the PDO array element must contain data if it is set.
This causes errors when dumping schema files or importing schema files during migrations.
I've added a check in the original if statement and a test that replicates the original behaviour.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


swagger-typescript-api does not work with TypeScript >=4.8.0

The issue I've had
I've recently ran into issues getting swagger-typescript-api to work in my project even though it worked a few months ago.
The issue that I've ran into kept throwing me an exception:
TypeError: host.fileExists is not a function
    at Object.fileExists (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:167586:63)
    at Object.host.fileExists (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:117448:47)
    at getPackageJsonInfo (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44458:37)
    at loadModuleFromSpecificNodeModulesDirectory (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:45000:27)
    at loadModuleFromImmediateNodeModulesDirectory (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44981:58)
    at C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44971:39
    at Object.forEachAncestorDirectory (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:8370:26)
    at loadModuleFromNearestNodeModulesDirectoryWorker (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44965:19)
    at loadModuleFromNearestNodeModulesDirectory (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44957:16)
    at tryResolve (C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f\node_modules\typescript\lib\typescript.js:44052:34)

Findings
After digging for a few hours I've managed to trace that it was caused by a later version of TypeScript. It stops working if version >=4.8.0 is used.
This issue is not reproduced by cloning the repository and doing an npm i due to the package-lock.json file explicitly stating, that typescript 4.7.4 should be used. However package-lock.json is not included as part of an npm package. This and the fact, that the typescript dependency is with a caret (^) symbol installs the latest version of typescript for new projects depending on this package.
Reproduction
To reproduce this error you can simply:

git clone https://github.com/acacode/swagger-typescript-api.git
npm i<EMAIL_ADDRESS>npm i

This will yield an error during the tests run.
How to fix it on my machine?
If you're just a passer-by like me who stumbled across this issue on their project - you can resolve it like this:
If the package is in your package.json

npm i<EMAIL_ADDRESS>
Please keep in mind that this will affect your whole project.
If you're using npx

Find npx cache for swagger-typescript-api mine was in C:\Users\<MyUsername>\AppData\Local\npm-cache\_npx\ad2f6472e51cc62f
Add "typescript": "4.7.4" to the package.json
npm i

Duplicate of #370

Hi @martis347 , I think this problem fixed in 11.* release. Because of this I'm closing this issue, please reopen if you are still occurring with this bug


Initial draft of event mechanism

At the moment, Avalon adds mbId to specific nodes relevant to how Mindbender does their shading.
I've separated this out into Mindbender's configuration and implemented an event framework for hooking things back into the core.
from avalon import api

def on_new():
  print("A new scene was created!")

api.on("new", on_new)
api.emit("new")
# A new scene was created!

By default, these trigger on Maya init, new and save

Example use

Let me know your thoughts @aardschok.

This is still up for discussion, I merged for the docs to compile.


Mention new Elixir/OTP requirements in 0.10.0 CHANGELOG

See this comment for context.
This would explain why I've been having trouble connecting to my running application 🙂. The only mention of Elixir 1.15 in the CHANGELOG is referencing a fix for compiler warnings/deprecations, but it appears that 1.15.2+ and OTP 26+ are now required for attached nodes. Adding a Removed section to the 0.10 CHANGELOG with information on this will likely save at least a few folks some debugging time.

This is slightly trickier. We support earlier versions if you run it via the CLI or from the repo, but if you are using Docker/Desktop app, it is going to be with the built versions. For this reason I am not quite sure it belongs to Removing. Perhaps Changed? Can you please send a PR to the v0.10 branch?

Sure! To be clear, if you're running it via the CLI or from the repo, you need to make sure you're running it with the same version of Elixir/OTP as the remote node you're trying to connect to, right? Just want to make sure I get the explanation right.

Usually you can connect forward. So if you run OTP 25, you can connect with OTP 26. You should be able to connect back as well, but we also load modules, and those can only be forward (module compiled for 26 may not run on 25).

Closed in #2080.


update s2s config params

This PR update the s2s config for syncUrlModifier documentation and usage

released with 2.8


feat: added port validation feature and tests

Change Summary
Added port validation ( 0 - 65535 inclusive ) because it makes sense to validate the port number since you have IP Validation as well.
Related issue number
No
Checklist

[✅] Unit tests for the changes exist
[✅] Tests pass on CI and coverage remains at 100%
[✅] Documentation reflects the changes where applicable
[✅] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

Humm, I've never needed this.
I'm not sure it really needs to be included in pydantic, especially given how simple it would be to implement in your own code.
Would this get enough usage to indicate its inclusion in pydantic?

Humm, I've never needed this.
I'm not sure it really needs to be included in pydantic, especially given how simple it would be to implement in your own code.
Would this get enough usage to indicate its inclusion in pydantic?

I'll reopen if there's significant interest.
(in future, best to create an issue before creating a PR, I don't want to waste your time.)

I'll reopen if there's significant interest.
(in future, best to create an issue before creating a PR, I don't want to waste your time.)


some depdency is missing and cannot install per README.md

Errors with installtion:

C:\Users\jeffrey>pip3 install gpt-computer-assistant                                                                        WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.                          Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.                               To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.                                  Defaulting to user installation because normal site-packages is not writeable                                               Collecting gpt-computer-assistant                                                                                Downloading gpt_computer_assistant-0.6.12.tar.gz (163 kB)                                                                      |████████████████████████████████| 163 kB 163 kB/s                                                                     ERROR: Could not find a version that satisfies the requirement langgraph==0.0.55 (from gpt-computer-assistant) (from ver    sions: 0.0.8)                                                                                ERROR: No matching distribution found for langgraph==0.0.55 (from gpt-computer-assistant)

after install langgraph with command pip3 install langgraph==0.0.55, a new error occurred as follows:

C:\Users\jeffrey>pip3 install gpt-computer-assistant
WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of pip.                          Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.                               To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.                                  Defaulting to user installation because normal site-packages is not writeable                                               WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'Prox    yError('Cannot connect to proxy.', OSError(0, 'Error'))': /simple/gpt-computer-assistant/                                   WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'Prox    yError('Cannot connect to proxy.', OSError(0, 'Error'))': /simple/gpt-computer-assistant/                                   WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'Prox    yError('Cannot connect to proxy.', OSError(0, 'Error'))': /simple/gpt-computer-assistant/                                   WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'Prox    yError('Cannot connect to proxy.', OSError(0, 'Error'))': /simple/gpt-computer-assistant/                                   WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'Prox    yError('Cannot connect to proxy.', OSError(0, 'Error'))': /simple/gpt-computer-assistant/                                   ERROR: Could not find a version that satisfies the requirement gpt-computer-assistant==0.6.12 (from versions: none)         ERROR: No matching distribution found for gpt-computer-assistant==0.6.12

run command pip3 install gpt-computer-assistant==0.6.12 to install but still with above error.
Enviroment:

system: Win10
C:\Users\jeffrey>pip --version
WARNING: pip is being invoked by an old script wrapper. This will fail in a future version of
Please see https://github.com/pypa/pip/issues/5599 for advice on fixing the underlying issue.
To avoid this problem you can invoke Python with '-m pip' instead of running pip directly.
pip 24.0 from C:\Users\jeffrey\AppData\Roaming\Python\Python38\site-packages\pip (python 3.8)

Hmm, it seems about your python version, can you upgrade you python version to 3.12?

Hi, again, i just made a update and we just currently support >= 3.9

Great! It works well after upgrading my python version.


Fix plugin exit when transport is SMTP

Problem: The plugin does not exit correctly when the transport is SMTP.
Why:
Triggering the fastify.nodemailer.close(done) is expected to
start disposing of resources procedure. However the mailer implementation
proxies the execution to the underlying SMTP transport.
In order to exit properly (after the plugin successfully closed),
the callback has to be called on the plugin event close.

Good to go, IMO. :)


Replacing Cancan Model Adapters

I'm thinking of replacing the default AR adapter with my own, using the expressiveness of squeel, like in #296. Also, because I kind of need my queries to not eager load all the associated objects, in #238.
I'm thinking that I'd spawn a new gem for this new adapter, but I need to metaprogram and override Cancan::Adapter::AbstractAdapter.for_class?
Maybe we can spin off all the adapters to gems instead?

I've published the adapter as a gem: https://github.com/lowjoel/cancancan-squeel
I'm working on making the behaviour of the ability rules compatible with the AR adapter, but it doesn't appear that the AR adapter has got rules detailing how multiple rules are merged.

Hei! Nice work! :+1:

I've added some additional specs for the adapter, specifically regarding how rules are combined, and what special attributes the adapter will recognise: https://github.com/lowjoel/cancancan-squeel/blob/master/spec/cancancan/squeel_spec.rb
It should be a superset of the tests for the AR4 adapter.

I would love to have adapters pulled out. I'm fine with having a common active record adapter in CanCan, but mongoid and friends could be pulled out and maintained by people who have more domain knowledge in those areas. (I don't use mongodb, and largely have to rely on the community for those changes). I could pull these into the organization if it's desired.
I don't plan on adding squeel as a dependency though. The adapter problem is a long standing one, and there are PR's open for attempting to fix them, but each one adds quite a bit of complexity that honestly shouldn't be required. We should just be able to generate conditions the same way active record does instead of attempting to re implement the same interface ourselves. I've been looking into how to use the active record tools to do this to replace a lot of our adapter logic when I have time.
I understand the problem with eager loading that people are having, but I dont think adding an additional dependency is the right solution.

To remove eager loading there is also this PR: https://github.com/CanCanCommunity/cancancan/pull/238

I don't think that my cancancan-squeel gem would ever be part of the main cancancan distribution, because I think it's overkill for most, except the most complex, applications.
However, I'm asking for two things:

specs regarding the behaviour of the AR adapter, especially with regards to rule merging and priorities
the ability to supersede the default AR adapter, without resorting to reopening the AR4 adapter class and replacing the for_class method.

The second is automatically handled by extracting all adapters into gems, unless an alternative approach is provided.

@Senjai After implementing this, I'm running into #265 again, and because it's a change to the way cancancan evaluates rules, it affects all adapters.
Maybe it would be good to draw up some plan regarding what the next set of refactoring will be, and we all can work towards that. I would not like to have all those PRs go stale.


Positioning for HTML sprites not working

//this:
new Sprite(20, 30, "<button>hi</button>")
//does the same thing as this:
new Sprite(0, 0, "<button>hi</button>")

Just add absolute positioning to the elements and give them positions

http://stackoverflow.com/questions/28598910/position-an-html-element-at-any-x-y-coordinate-in-a-page


Apply RBACs for installer also for OpenShift

Up to now, the installer RBACs were not applied for OpenShift.
This resulted in a failing installer job.
This PR also applies the RBAC rules also for OpenShift.

Codecov Report

Merging #1943 into master will increase coverage by 0.04%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1943      +/-   ##
==========================================
+ Coverage   34.11%   34.16%   +0.04%
==========================================
  Files         146      146
  Lines        9221     9209      -12
  Branches      128      128
==========================================
  Hits         3146     3146
+ Misses       5655     5643      -12
  Partials      420      420

Flag
Coverage Δ

#moduleA
35.88% <ø> (ø)

Impacted Files
Coverage Δ

cli/cmd/install.go
21.15% <0.00%> (+0.59%)
: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 5e44481...a910974. Read the comment docs.


Scrolling and Panning in the code editor

What Happened
When trying to make complicated block setups such as if  or  detected then do , often times code blocks will exit the frame of the code editor.
While closing the block lists may widen up the space to code a small bit, implementing a scrolling and panning feature as seen in Scratch or other equivalent block programming tools would be much more helpful in the long run and I believe should be looked at very soon.
How to Reproduce
N/A
Operating System
No response
Logs or command-line output
No response
Anything else?
No response

@CaptchaBomb thanks! This was already implemented a week ago https://github.com/endlessm/godot-block-coding/pull/120, we just need to release.

Zoom and pan has been released: https://github.com/endlessm/godot-block-coding/releases/tag/v0.6.0


Allow to extend the default Webpack configuration

FYI, the latest version allows to customize the default Webpack configuration by creating config.js file in the root of your project that may look something like this:
config.js
module.exports = {
  // Extend the default Webpack configuration
  webpack: config => {
    // For example, add one more entry point
    config.entry.push('./server.js');
  },
};

Hello, first congratulations for this great contribution. And now I wonder if the master branch has been updated for edit webpack, or if there is another way to add sass to my project, I want to use  bootstrap and my own modules made in sass.


Fixed Virtio_block test

Added some parentheses.
It was complaining about:
error: reference to non-static member function must be called;

I need to update the environment so that the test finds the tools needed for mounting.

retest this please

Retest this please


SMIME support, should able to change encryption type in config

Currently, default encryption is CMSAlgorithm.AES256_CBC and should have ability to change where building Email

Where did you see the default in AES256_CBC? I can only find DES_EDE3_CBC being used in the code.

Any update, @asariev?

sorry for confusion, if I wanted to set CMSAlgorithm.AES256_CBC instead of CMSAlgorithm.DES_EDE3_CBC

Duplicate of #498


Issue on page /intro.html - mamba can't create environment from yaml file

Hi, this command doesn't seem to work:
mamba create -f environment.yml
there is an issue with this, documented here: https://github.com/mamba-org/mamba/issues/633
There are a couple of workarounds proposed on this issue page, including one that worked for me - create an empty env with mamba, then update it based on --file environment.yaml

It's still not fixed.
The correct command should be:
mamba env create --file envname.yaml


[Bug]: dragonfly doesnt accept custom environment variables

Description
dragonfly cannot read environment variables:

Minimal Reproduction (if possible, example repository)
just deploy the application from coolify UI and try to use custom variables
Exception or Error
No response
Version
v4.0.0-beta.323
Cloud?

[ ] Yes
[X] No

This will be fixed in the upcoming version.

Thank you very much for Coolify 🙏


done

ping @hustcc  改好了

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 5 (60.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+3.2%) to 63.158%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/fuck/fuck/index.tsx
2
4
50.0%

Totals

Change from base Build<PHONE_NUMBER>:
3.2%

Covered Lines:
12

Relevant Lines:
19

💛  - Coveralls


CCDScan doesn't show what data was registered on chain

Bug Description
It seems that the only thing CCDScan shows is the transaction type.

Versions

Software Version: 1.1.4-0

raised PR
https://github.com/Concordium/concordium-scan/pull/44


SPARQL Update in Patch must allow WHERE

The Solid Protocol relies on PATCH for fast update.   The PATCH operation is sent as a SPARQL Update language.
The patch body can include a WHERE clause, as this is used to patch data which has blank nodes.
CSS currently seems to not support WHERE clause, so client code which works with NSS and ESS does not work with CSS.   Please add WHERE clause support to the CSS PATCH engine.

This actually goes back to one of our oldest still open issues that never got resolved: https://github.com/solid/community-server/issues/15#issuecomment-658133139
So I'm guessing we just want to support simple BGP queries?

Indeed, BGP is a good start. Let's reject everything else for now.


GraphMatchingLinkPrediction

GraphMatchingLinkPrediction generates float predictions instead of int.
Below is SRI's hack to fix the problem. We need to something similar.
    def produce(self, inputs=None):
        outputs = self.fitted_pipeline.produce(inputs=inputs)[0]
        target = self.optimizer.config.get_target_name()
        task_type = self.optimizer.config.taskType
        outputs = outputs.drop(columns=['d3mIndex'])
        if task_type == 'communityDetection':
            outputs[target] = outputs[target].astype(int)
        return outputs

added in search.py for both training and testing_pickled_pipeline, merge req sent

Though results are still not good, they are not 0 now