Changes in animation's behavior starting from 1.4.7

Hi,
I've recently updated from 1.4.3 and found changes in the animation's behavior.
My code is something like this, nothing specific:

But what I see after update starting from 1.4.7 is random flickering on the nested ng-if.
I'll try to provide an example, but could anyone review this issue and say, is it a bug or just undocumented changes in the behavior?
I can debug only changes in data-ng-animate attribute: they are 1 and 2. Also I don't see any animation specific classes on the divs, like ng-enter, ng-leave etc

Can you please post a plnkr.co etc. that shows the problem? We've fixed a lot of bugs in ngAnimate, but there's also a known issue with nested animations.

You should also see if the problem persists in 1.4.9.

The problem persists in all the versions after 1.4.7, oncluding 1.5.0-rc1

@havenchyk Ok. Please try to get a working demo running.

@Narretz unfortunately I haven't been able to pull the example from my application, but it looks like that the problem is similar like described here https://docs.angularjs.org/guide/animations#preventing-flicker-before-an-animation-starts
So, I've added styles for ng-enter-prepare and ng-leave-prepare and now things are better, but I get some flickering even after this workaround.
Maybe guys you can advice, how to debug angular animations and for what things I need to take a look, I'd like to help, but don't know how.

Ok, here is something similar that I have. If you click on the button, you will see "jumps" down of the button.

This is a result of https://github.com/angular/angular.js/commit/ea8016c4c8f55bc021549f342618ed869998e335, which went into 1.4.5. As of now, this is expected behavior, unfortunately.
Applying display: none only to the enter animation removes the flicker: http://jsbin.com/diwixeziba/1/edit?html,css,js,output
This makes sense. The enter element is added to the DOM, and because it's a child element, the regular display: none is only applied after an animationFrame. So there's a very short time frame where the element is visible, even though it shouldn't be. With leave, we don't have this problem, because the element is already there. Probably should make this more clear in the guide.

@Narretz heh, it solves my problem. It would be great if you could add details to the guide, it was unclear for me before your comment.
Thanks!

BTW, I still have flickering even after display: none. Animation disabling with $animate.enabled(element, false) solves the problem, but it's a workaround as well.

@havenchyk Which browser is that?

Latest Google Chrome and Chrome Canary

Hm, I can't reproduce this. I've used the jsbin I linked to.

@havenchyk What OS are you using?

@Narretz I can't reproduce the issue with an example on jsbin, but have it in my complex application. I use win7 and the problem can be reproduced in latest Google Chrome, FF and IE11. Current workaround is to disable animation with $animate.enabled(element, false);

@havenchyk At the moment, this is an expected side-effect of a change in 1.4.5 that was necessary to fix other bugs. We've introduced a new class that can be used to prevent the flicker. Mabye it works for you: https://code.angularjs.org/snapshot/docs/guide/animations#preventing-flicker-before-an-animation-starts

@Narretz if you check our previous comments on current issue, you will see that I already tried it and it doesn't work for me. I'll attach video to show, what's going on, because I can't reproduce the issue from the scratch.

@havenchyk Sorry, I confused this issue with the one that you linked.

@havenchyk check if you updated your angular-animate to the latest version

@teterovic of course I updated it as well.

I'm going to close this issue because we have no reproduction of the issue. Feel free to reopen this issue if you can provide a reproduction (ideally a runnable demo in a https://plnkr.co or similar. You can use this Plunker Template).


This isn't Node, silly

Several constructs used in the ping timeouts were dependent on Node-only features or Bluebird. This caused pings to be non-functional in browsers. Derp.

@connor4312, thanks for your PR! By analyzing the history of the files in this pull request, we identified @SimonSchick and @JamyDev to be potential reviewers.

typescript pls

hm?

Meant to say, this wouldn't have happened with TS 😛


Adds League SEA regions

No worries! Done.

Are you sure you've built the package before the 0.6.1 release? Looks like the changes are in the source code, but not in the distributed version.

Did you have a chance to look into this?

Yeah , LeagueRegion enum in package still not update :(


add CosmWasm smart contract samples

close: #29

Please add a link to contract samples to root's README.
Please unify CW, Cw, and, cw.
Please unify CosmWasm and Cosmwasm.

Is it necessary to recommend using Docker for compilation because the RUST version in our document is 1.69.0, while some samples need version 1.70.0 or higher?

Please add a link to contract samples to root's README.
Please unify CW, Cw, and, cw.
Please unify CosmWasm and Cosmwasm.

I will unify it like below.

CosmWasm
cw20, cw721

Is it necessary to recommend using Docker for compilation because the RUST version in our document is 1.69.0, while some samples need version 1.70.0 or higher?

I think it would be a good idea to add this warning to the smart contract tutorial or guide.

This PR's title may confuse that this PR adds contracts programs not only information. Please make clear that this PR adds only information.

I found that this contract was overlooked
https://github.com/CosmWasm/cw-nfts/tree/main/contracts/cw721-expiration

I found that this contract was overlooked https://github.com/CosmWasm/cw-nfts/tree/main/contracts/cw721-expiration

Thank you. Now I added it.


this.props.url.push with params not working.

When i try to redirect or change the route using this.props.url.push i got 404 error.
i followed this [this.props.url.replace(/abc?param=value) But it
should not throw 404 error.
I have attached the screenshot of console in browser.

Please use next/router APIs.
These APIs are not supported.


Misleading error when an unsupported critical extension is found

In x509_get_crt_ext:
            if( is_critical )
            {
                /* Data is marked as critical: fail */
                return( MBEDTLS_ERR_X509_INVALID_EXTENSIONS +
                        MBEDTLS_ERR_ASN1_UNEXPECTED_TAG );
            }

This is somewhat misleading. MBEDTLS_ERR_X509_INVALID_EXTENSIONS + MBEDTLS_ERR_OID_NOT_FOUND would make more sense. And that would be written as
            if( is_critical )
                return( MBEDTLS_ERR_X509_INVALID_EXTENSIONS + ret );

This could break applications that are overly picky about error codes, so it must not be done in LTS, and perhaps only in 3.0. (But I think it would be an acceptable change in a non-LTS too.)
(Made a separate issue from https://github.com/ARMmbed/mbedtls/issues/4060#issuecomment-768602154)

According to https://github.com/ARMmbed/mbedtls/pull/4600, this is not a compatibility break, so we can do it after 3.0.


How to properly emulate a query with an array of options (has_many trough associations)?

Hi hackers!
I am trying to move my self-documented code from swagger-docs to swagger-blocks, so far everything is working very sweet.
But I was wondering if... is there a way to send via query an array/hash, for example, guide[language_ids][]?
These are my models:
class Guide < ApplicationRecord
  has_many :guide_languages
  has_many :languages, through: :guide_languages
end

class Language < ApplicationRecord
  has_many :guide_languages
  has_many :guides, through: :guide_languages
end

class Guide < ApplicationRecord
  has_many :guide_languages
  has_many :languages, through: :guide_languages
end

class Language < ApplicationRecord
  has_many :guide_languages
  has_many :guides, through: :guide_languages
end

class GuideLanguage < ApplicationRecord
  belongs_to :guide
  belongs_to :language
end

This is what I have been trying so far:
  class GuidesController < ApiController
    include Swagger::Blocks

    before_action :set_guide, only: [:show, :update, :destroy]

    swagger_path '/guides' do
      # POST
      operation :post do
        key :description, 'Creates a new guide. Duplicates are allowed'
        key :operationId, 'addGuide'
        key :produces, [
          'application/json'
        ]
        key :tags, [
          'guide'
        ]
        # Parameters
        parameter do
          key :name, 'guide[name]'
          key :in, :query
          key :description, 'Name'
          key :required, true
          key :type, :string
        end
        parameter do
          key :name, 'guide[lastname]'
          key :in, :query
          key :description, 'Lastname'
          key :required, true
          key :type, :string
        end
        parameter do
          key :name, 'guide[language_ids][]'
          key :in, :query
          key :description, 'Language ID '
          key :required, false
          key :type, :string
        end
        # Response
        response 200 do
          key :description, 'guide response'
          schema do
            key :'$ref', :Guide
          end
        end
        response :default do
          key :description, 'unexpected error'
          schema do
            key :'$ref', :ErrorModel
          end
        end
      end
    end
...

Thanks in advance!

I also try:
        parameter do
          key :name, 'guide[language_ids][]'
          key :in, :query
          key :description, 'Language ID '
          key :required, false
          key :type, :array
          items do
            key :type, :integer
            key :format, :int32
          end
        end

But it doesn't work either (Only sends the first value of the array).

An option would be creating a virtual instance method before hand in guide model:
# models/guide.rb

def language_ids
  pluck(:id)
end

Let me know it that works.

I think this comment from a while back is related: https://github.com/fotinakis/swagger-blocks/issues/4#issuecomment-70575007

Please edit your post.
You have duplication there.

Closing due to inactivity.


Disposer does not cleanup after rejection

Good day everyone,
today I encountered an issue with the Disposer object which looked pretty nice at first glance but seems to be a tricky to use.
First things first:

Bluebird version: 3.5.0
Platform: Windows 7 (x64)
Node version: 4.4.3

"Did this issue happen with earlier versions of bluebird"?
I am not sure. First I thought it worked with 3.3.5 but that was not the case.
The issue
Alright, I might not use the correct approach to use Disposers and Promise.using so please let me know when I failed that regard - if I didn't mess up it might be my understanding of Disposers and resources in general; Again, please let me know.
Code explains better than my linguistic skills would allow:
'use strict';

const Promise = require('bluebird');

function eww() {
  return Promise.reject(new Error('evil issue'))
    .delay(100)
    .disposer(() => {
      console.log('should be called but never is');
    });
}

Promise.using(eww(), () => {
  console.log('positive case - never called');
})
.catch((err) => {
  console.log('failed as expected - resource is not cleaned up.');
})

The basic issue is that my disposer function is never called which should be a Bluebird issue.
The reason being - again, my understanding - that whenever I attempt to claim a resource, the disposer always takes care about the proper cleanup.
Currently, when my resource claiming function (eww() from the example) fails, I have to manually clean up my mess - which may is impossible when I wrap my code behind the disposer.
The problem is this code chunk.
The issue is not to be mistaken with this issue.
I suspect it never worked like I thought it would..
Can anyone confirm this behavior?
I wonder if this is intended. If I have to manually clean up after disposers, I rather not use them at all.
The caller should not care about cleaning up in such cases - especially in rejection cases.
Edit:
I changed the code within the using.js to the following (resource method):
Disposer.prototype.resource = function () {
        if (this.promise().isFulfilled()) {
            return this.promise().value();
        }
        if (this.promise().isRejected()) {
            return this.promise().reason();
        }
        return NULL;
    };

This causes the disposer to work as intended. If this is a proper change to you, let me know and I'll PR you it.
Best regards,
Philipp

The issue is that the resource was never acquired in the first place. If the promise that acquires a resource fails, it makes sense to assume that the resource was not acquired and is therefore unnecessary to clean it up.

The thing is we can't be certain that the resource was never acquired. Surely, we didn't receive a connection (to simplify the terms a bit) but what if we already created like a socket or something similar which doesn't clean up itself (or not at all) and the reason for the rejection may be something different like setting a flag based on wrongly configured connections.
The current patterns makes aggregations over different steps impossible.
One example would be that I want to create a bound LDAP client using ldapjs.
For that I'd create a new function createBoundLdapClient that returns a bound Ldap client.
So when the creation works but the bind fails I'm at a dead end with disposers and can't roll back - the socket is forever open and memory is leaked.
The workaround would be to always resolve a disposer function and open another channel to propagate errors (like events) but that sounds like a big anti pattern..

Yes, chaining disposers is important. I reopened #1379

Hi,
today I checked with c# (which I assume worked as heavy inspiration for Bluebird Disposers) and their Dispose (or IDisposable interface) works exactly the same way - they do not execute the Disposer upon thrown exceptions.
I'm sorry for the heavy tone and look forward to Disposer chaining.
Cheers

@ptusch if you're interested, when we designed using I asked this from a C# perspective: https://stackoverflow.com/questions/21118201/can-using-with-more-than-one-resource-cause-a-resource-leak

@benjamingr Ahh, I just read your comment there. I didn't know that a .disposer function requires to guarantee no throw.
Thanks for the link!

Disposer cannot be called because there is nothing to call it with.


Change URI parser to take absl::string_view.

Also move the tests to a more appropriate directory (should have been done as part of #17050).

Known issues: #23822

The "Bazel RBE Debug C/C++" is an infrastructure failure.
The "Bazel RBE TSAN C/C++" failure is tracked internally as b/164973818.


Invalid argument

Hi, congratulation, escuse my bad english
My problem is, I use lenovo (notepad) cam EasyCamera embeeded
deepseg v0.2.0
(c) 2021 by<EMAIL_ADDRESS>https://github.com/floe/deepbacksub
debug:  2
ccam:   /dev/video0
vcam:   /dev/video1
width:  640
height: 480
flip_h: no
flip_v: no
threads:2
back:   (none)
model:  models/segm_full_v679.tflite
loopback.cc:66(loopback_init): Failed to set device video format: Invalid argument
Failed to initialize vcam device.

Don't forget the modprobe command and check which video device is created in /dev/video*.

You can specify numbering and device names, here's what I have:
to ensure the loopback module is loaded:
/etc/modules-load.d/v4l2loopback.conf:
v4l2loopback

to configure the loopback module with two additional devices, /dev/video10 == 'Virtual Camera' /dev/video11 == 'Test Loopback':
/etc/modprobe.d/v4l2loopback-options.conf:
options v4l2loopback video_nr=10,11 exclusive_caps=1 card_label="Virtual Camera,Test Loopback"

Tks
Is working now, but in green screen.
What replace the background image.
Regards

You need to provide an image file with -b. See also the usage information shown with -? for further details.

@SANDRORRFREIRE is this fixed for you now?

No feedback, closing.

@SANDRORRFREIRE how did you fix that issue?

@cojack at a guess, I think @SANDRORRFREIRE sorted out their v4l2loopback devices (see my earlier description of how I have mine arranged), then discovered the -b option to load a background image :smile:


Tolerate missing readme file for a repo

Fixes https://github.com/MeltanoLabs/tap-github/issues/40

@laurentS - it's hard for me to have confidence in merging while the pipelines are failing due to rate limits. Some proposals to address in #42 and #43 - as well as with rotation described in #39 .


add typing as var contrib: any (#103)

See #103

thanks, meanwhile #127 already covers this but thanks for adding this


User Profile Screen

I can make UI for profile screen with
Customizable Avatars:
Allow users to select or upload avatars. Include options for personalization (e.g., background colors, stickers).
About Me Section:
A brief description area where users can add interests and tags, enhancing their discoverability.
Activity Feed:
Display recent activities, events attended, or updates shared by the user, giving others insight into their interests.
Please assign me this issue under gssoc and hacktoberfest tag.
Please give level2 tag.

@shreyad2806
Customizable Avatars ❌:
we already have options to select profile picture.
About Me Section ✅:
This can be added below bio section
Activity Feed ❌:
This doesn't align with NextGen purpose.

@shreyad2806 you can work on About me section you have mentioned.
Add interest section below bio.
UI:
Show interests in chips.

Do I have to add two sections (about me / interest) or just interest section?


Adding a new Workflow execution phase LAUNCHED

cc @schottra @katrogan @kumare3
Not sure if this would break UI. Will have to check.

what's the point of this though?  can we document the difference between queued, launched, and running?

what she said.

@wild-endeavor @katrogan Closing this PR. QUEUED does the job for me. I thought it was used for something else. But looks like it is not.


Problem with auto-deploy on External switch and DHCP

Hi.
I'm provisioning EFLOW on Azure VM with Windows Server 2019.  The 0 argument is less than the minimum allowed range of 1. Supply an argument that is greater than or equal to 1 and then try the command again. BUT, I can see that it has already created the external virtual switch correctly.

So it basically searches for Prefix and "" doesn't have any meaning to the script in DHCP format. When I use 24, then it starts complaining about ip4Address and ip4GatewayAddress, which is understandable because it tries to assign IP.
Am I missing something in my user config to apply DHCP?
Below is the execution log.
PS D:\EFLOW> .\eflowAutoDeploy.ps1 -AutoDeploy
Running eflowAutoDeploy version 1.0.220831.0800
HostOS	: Microsoft Windows Server 2019 Datacenter(8)
Version	: 10.0.17763.3532
Lang	: en-US
Name	: vm-Edge-azar-wi
Total CPUs		: 2
Free RAM / Total RAM	: 14 GB / 16 GB
Free Disk / Total Disk	: 114 GB / 126 GB
Running as a virtual machine in Azure environment with Nested Hyper-V enabled
Azure IoT Edge,<IP_ADDRESS>92 is installed.
Loading D:\EFLOW\eflow-userconfig.json..
Hyper-V is enabled
Azure IoT Edge,<IP_ADDRESS>92 is installed.
Importing AzureEFLOW..
WARNING: The names of some imported commands from the module 'AzureEFLOW' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list
of approved verbs, type Get-Verb.
AzureEFLOW Module:0.0.1
Hyper-V is enabled
* Using virtual switch EFLOW
* Using vSwitchType External
--- Verifying virtual switch IP address allocation...
* No static IP address provided - DHCP allocation or auto-static ip(internal switch) will be used
--- Checking proxy settings...
*** No errors found in the Network Configuration.
Creating VMSwitch EFLOW - External...

--- Verifying EFLOW VM Deployment Configuration...
--- Verifying EULA and telemetry...
* EULA accepted.
- Optional telemetry not accepted. Basic telemetry will be sent.
--- Verifying virtual switch...
Hyper-V is enabled
* Using virtual switch EFLOW
* Using vSwitchType External
--- Verifying virtual switch IP address allocation...
* No static IP address provided - DHCP allocation or auto-static ip(internal switch) will be used
--- Checking proxy settings...
*** No errors found in the Network Configuration.
* Name:EFLOW - Type:External
--- Verifying virtual machine resources...
* Virtual machine will be created with 4 vCPUs.
* Virtual machine will be created with 4096 MB of memory.
* Virtual machine VHDX will be created with 32 GB disk size.
* No custom data size used - Using default configuration, virtual machine VHDX will be created with 10 GB of data size.
--- Verifying GPU passthrough configuration...
* No GPU passthrough being used - CPU only allocation
*** No errors found in the Deployment Configuration.
Starting EFLOW VM deployment...
Deploy-Eflow : Cannot validate argument on parameter 'ip4PrefixLength'. The 0 argument is less than the minimum allowed range of 1. Supply an argument that is greater than or equal to 1 and then try the command again.
At D:\EFLOW\eflowAutoDeploy.ps1:726 char:28
+     $retval = Deploy-Eflow @eflowDeployParams
+                            ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Deploy-Eflow], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Deploy-Eflow

Error: EFLOW VM deployment failed with the below error message.
Error message : .
D:\EFLOW\eflowAutoDeploy.ps1 : Deployment failed
At line:1 char:1
+ .\eflowAutoDeploy.ps1 -AutoDeploy
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,eflowAutoDeploy.ps1

Hi @arminghasemazar,
There was an issue with empty string network parameters. I just pushed some changes to fix that. Could you please try it again?
Thanks,
Francisco

Hi @arminghasemazar,
I fixed the first issue you mentioned. For the other two issues, I see that you're using Internal Switch, but your config file suggests you're using an External Switch. Could you please clariify?
Thanks,
Francisco

Hi @arminghasemazar,
A couple of things you may try to change

If you're using "Internal" switch, the parameter "adapterName" is not needed, so you may want to leave that empty
For DNS servers, use the "dnsServers" field. This will set the DNS servers before trying to provision
If you still face the same issues, try restarting the IoT Edge service.

Thanks,
Franicsco

Hi @arminghasemazar,
A couple of things you may try to change

If you're using "Internal" switch, the parameter "adapterName" is not needed, so you may want to leave that empty
For DNS servers, use the "dnsServers" field. This will set the DNS servers before trying to provision
If you still face the same issues, try restarting the IoT Edge service.

Thanks, Franicsco

Hi Francisco.
Unfortunately same problems still persist.
[10/20/2022 08:16:20] Virtual machine created successfully.

[10/20/2022 08:16:20] Successfully created virtual machine

[10/20/2022 08:16:20] Virtual machine hostname: vm-Edge-azar-ef-EFLOW

[10/20/2022 08:16:31] Error setting static IP

[10/20/2022 08:16:31] Testing SSH connection...

[10/20/2022 08:17:05] ...successfully connected to the Linux VM

 - Please check your DNS configuration to ensure Internet connectivity. Refer https://aka.ms/AzEFLOW-DNS for more details.

[10/20/2022 08:17:06] Deployment successful

* EFLOW VM deployment successfull.
Setting DNS Servers to <IP_ADDRESS> <IP_ADDRESS>

--- Verifying EFLOW VM Provisioning Configuration...
--- Verifying provisioning type...
* DpsSymmetricKey
--- Verifying provisioning parameters..
* scopeId Ok
* symmKey Ok
* registrationId Ok
No errors found in the Provisioning Configuration.
Starting EFLOW VM provisioning...

[10/20/2022 08:17:08] Provisioning virtual machine...

[10/20/2022 08:17:09] Provisioning iotedge for the first time.

[10/20/2022 08:17:09] Setting provisioning information for provisioning type: DpsSymmetricKey

[10/20/2022 08:17:31] Exception caught!!!

 - iotedge service not running after provisioning, please investigate manually at line 2416
Error: EFLOW provisioning failed with the below error message.
Error message : iotedge service not running after provisioning, please investigate manually.
D:\EFLOW\eflowAutoDeploy.ps1 : Deployment failed
At line:1 char:1
+ .\eflowAutoDeploy.ps1 -AutoDeploy
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,eflowAutoDeploy.ps1

Result of iotedge check
Configuration checks (aziot-identity-service)
---------------------------------------------
√ keyd configuration is well-formed - OK
√ certd configuration is well-formed - OK
√ tpmd configuration is well-formed - OK
√ identityd configuration is well-formed - OK
√ daemon configurations up-to-date with config.toml - OK
√ identityd config toml file specifies a valid hostname - OK
‼ aziot-identity-service package is up-to-date - Warning
    Installed aziot-identity-service package has version 1.3.0 but 1.4.1 is the latest stable version available.
    Please see https://aka.ms/aziot-update-runtime for update instructions.
√ host time is close to reference time - OK
√ preloaded certificates are valid - OK
√ keyd is running - OK
√ certd is running - OK
√ identityd is running - OK
× read all preloaded certificates from the Certificates Service - Error
    could not load cert with ID "aziot-edged-trust-bundle"

    Caused by:
        parameter "id" has an invalid value
        caused by: not found
√ read all preloaded key pairs from the Keys Service - OK
√ ensure all preloaded certificates match preloaded private keys with the same ID - OK

Connectivity checks (aziot-identity-service)
--------------------------------------------
‼ host can connect to and perform TLS handshake with iothub AMQP port - Warning
    Could not retrieve iothub_hostname from provisioning file.
    Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    Since no hostname is provided, all hub connectivity tests will be skipped.
‼ host can connect to and perform TLS handshake with iothub HTTPS / WebSockets port - Warning
    Could not retrieve iothub_hostname from provisioning file.
    Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    Since no hostname is provided, all hub connectivity tests will be skipped.
‼ host can connect to and perform TLS handshake with iothub MQTT port - Warning
    Could not retrieve iothub_hostname from provisioning file.
    Please specify the backing IoT Hub name using --iothub-hostname switch if you have that information.
    Since no hostname is provided, all hub connectivity tests will be skipped.
√ host can connect to and perform TLS handshake with DPS endpoint - OK

Configuration checks
--------------------
√ aziot-edged configuration is well-formed - OK
√ configuration up-to-date with config.toml - OK
√ container engine is installed and functional - OK
× configuration has correct URIs for daemon mgmt endpoint - Error
    SocketError - SocketErrorCode (TimedOut) : Operation timed out
    One or more errors occurred. (Got bad response: )
‼ aziot-edge package is up-to-date - Warning
    Installed IoT Edge daemon has version 1.3.0 but 1.4.2 is the latest stable version available.
    Please see https://aka.ms/iotedge-update-runtime for update instructions.
√ container time is close to host time - OK
‼ DNS server - Warning
    Container engine is not configured with DNS server setting, which may impact connectivity to IoT Hub.
    Please see https://aka.ms/iotedge-prod-checklist-dns for best practices.
    You can ignore this warning if you are setting DNS server per module in the Edge deployment.
‼ production readiness: logs policy - Warning
    Container engine is not configured to rotate module logs which may cause it run out of disk space.
    Please see https://aka.ms/iotedge-prod-checklist-logs for best practices.
    You can ignore this warning if you are setting log policy per module in the Edge deployment.
× production readiness: Edge Agent's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeAgent container
× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error
    Could not check current state of edgeHub container
√ proxy settings are consistent in aziot-edged, aziot-identityd, moby daemon and config.toml - OK

Connectivity checks
-------------------
19 check(s) succeeded.
7 check(s) raised warnings. Re-run with --verbose for more details.
4 check(s) raised errors. Re-run with --verbose for more details.
7 check(s) were skipped due to errors from other checks. Re-run with --verbose for more details.

Also, even though the provision script claims that it has set DNS servers, I cannot see them applied.

And I think I know the reason because in the script there is only
Set-EflowVmDNSServers -dnsServers $eflowConfig.network.dnsServers
while I also use
Set-EflowVmDNSServers -vendpointName vm-Edge-azar-ef-EFLOWInterface -dnsServers @("<IP_ADDRESS>","<IP_ADDRESS>")
In any case I don't think this DNS issue has anything to do with DPS provisioning. I also tried provisioning with device connection string and it went well and I can see the edge is working as it should. So there is something wrong with the DPS settings. Values for "scopeId", "symmKey", and "registrationId" are correct since I can provision a device on Ubuntu with similar values.

Some more logs:
journalctl -u aziot-certd
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW systemd[1]: Started Azure IoT Certificates Service.
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - Starting service...
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - Version - dev build
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - Starting server...
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - <-- GET /certificates/aziot-edged-trust-bundle?api-version=2020-09-01 {"host": "certd.sock"}
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - !!! parameter "id" has an invalid value
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - !!! caused by: not found
Oct 20 09:06:33 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:06:33Z [INFO] - --> 400 {"content-type": "application/json"}
Oct 20 09:07:06 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:07:06Z [INFO] - <-- GET /certificates/aziot-edged-trust-bundle?api-version=2020-09-01 {"host": "certd.sock"}
Oct 20 09:07:06 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:07:06Z [INFO] - !!! parameter "id" has an invalid value
Oct 20 09:07:06 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:07:06Z [INFO] - !!! caused by: not found
Oct 20 09:07:06 vm-Edge-azar-ef-EFLOW aziot-certd[3150]: 2022-10-20T09:07:06Z [INFO] - --> 400 {"content-type": "application/json"}
Oct 20 09:07:27 vm-Edge-azar-ef-EFLOW systemd[1]: Stopping Azure IoT Certificates Service...
Oct 20 09:07:27 vm-Edge-azar-ef-EFLOW systemd[1]: aziot-certd.service: Deactivated successfully.

Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [INFO] - Starting service...
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [INFO] - Version - dev build
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [INFO] - Provisioning starting.
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [ERR!] - Failed to provision with IoT Hub, and no valid device backup was found: DPS client error
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [ERR!] - service encountered an error
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [ERR!] - caused by: DPS client error
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [ERR!] - caused by: invalid Content-Type; expected JSON
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]: 2022-10-20T09:13:34Z [ERR!] -    0: backtrace::backtrace::trace
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW aziot-identityd[5612]:    1: backtrace::capture::Backtrace::new
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW systemd[1]: aziot-identityd.service: Main process exited, code=exited, status=1/FAILURE
Oct 20 09:13:34 vm-Edge-azar-ef-EFLOW systemd[1]: aziot-identityd.service: Failed with result 'exit-code'.
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW systemd[1]: aziot-identityd.service: Scheduled restart job, restart counter is at 115.
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW systemd[1]: Stopped Azure IoT Identity Service.
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW aziot-edged[4030]: 2022-10-20T09:13:39Z [WARN] - Failed to send HTTP request (attempt 2 of 2): connection error: Connection reset by peer (os error 104)
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW aziot-edged[4030]: 2022-10-20T09:13:39Z [ERR!] - Failed to obtain device identity: connection error: Connection reset by peer (os error 104)
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW aziot-edged[4030]: 2022-10-20T09:13:39Z [INFO] - Requesting device reprovision
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW aziot-edged[4030]: 2022-10-20T09:13:39Z [WARN] - Failed to clear provisioning cache before reprovision: No such file or directory (os error 2)
Oct 20 09:13:39 vm-Edge-azar-ef-EFLOW aziot-edged[4030]: 2022-10-20T09:13:39Z [WARN] - Failed to send HTTP request (attempt 1 of 2): error trying to connect: Permission denied (os error 13)

Hi @arminghasemazar,
Thanks for your information. I tried your same config json and script and it worked for me, so I'm a bit confused. A couple of more questions

Have you tried using the normal installation without the script? Do you see the same "static IP" error?
Normal provisioning works right? Can we open a new issue in the IoT Edge repo for the DPS specific issue?

Thanks,
Francisco

Hi @arminghasemazar,
Thanks for your information. I tried your same config json and script and it worked for me, so I'm a bit confused. A couple of more questions

Have you tried using the normal installation without the script? Do you see the same "static IP" error?
Normal provisioning works right? Can we open a new issue in the IoT Edge repo for the DPS specific issue?

Thanks, Francisco

Hi Francisco.
It also confuses me a lot since the script is straightforward and shouldn't be any problem.

Yes I see the same. But, I tried using the script on my personal computer and I didn't see the static IP problem. So most probably that issue is related to Azure VM. So we can ignore it.
Yes normal provisioning works both with script and normal installation. Yes, agree, we need to open issue with IoT Edge repo. Will do that shortly.

Thanks for your help BTW,

Just before creating a new issue in IoT Edge repo, I tried deploying EFLOW manually on my personal PC. I installed EFLOW X64 <IP_ADDRESS>92 and tried to deploy EFLOW with the following command:
Deploy-Eflow -acceptEula Yes -acceptOptionalTelemetry No -cpuCount 1 -memoryInMB 4098 -vmDiskSize 22 -vswitchName "EFLOW" -vswitchType External. But I am facing the following error. I'm using the latest version of Win 10 Pro with latest update. Hyper-V has been installed and an external switch is there and working.
[10/21/2022 10:44:39] Setting dynamically expanding virtual hard disk maximum size to 23 GB

 - Creating storage vhd (file: AzureIoTEdgeForLinux-v1-EFLOW)
 - Creating vnic (name: DESKTOP-415VL1V-EFLOWInterface)
 - Instantiating virtual machine (name: DESKTOP-415VL1V-EFLOW)

[10/21/2022 10:44:46] Error: Virtual machine creation failed!

[10/21/2022 10:44:46] Cleaning up...

[10/21/2022 10:44:46] Exception caught!!!

 - C:\Program Files\Azure IoT Edge\nodectl.exe  compute vm show --name DESKTOP-415VL1V-EFLOW -o json failed to execute [Error: rpc error: code = NotFound desc = [Store] unable to filter entity from store for type[VirtualMachineInternal], FilterName[Name], FilterValue[DESKTOP-415VL1V-EFLOW]: Not Found] at line 4288

[10/21/2022 10:44:46] Exception caught!!!

 - Unable to create virtual machine. (L1229)

[10/21/2022 10:44:46] In order to attempt another deployment, please uninstall the Azure IoT Edge msi and start from fresh

Hi @arminghasemazar,
Thanks for the update - We've been able to reproduce the Static IP issue, and we will fix it in our next update.
Regarding the VM creation error, could you please share the logs? Also, what's your free memory on the device?
Thanks,
Francisco

Hey. Below is the full deploy log. The available free memory is 6 GB. I changed the deployment to 1 GB for memory and the same error still persists.
PS C:\Users\armin> Deploy-Eflow -acceptEula Yes -acceptOptionalTelemetry No -cpuCount 1 -memoryInMB 1024 -vmDiskSize 22 -vswitchName "EFLOW" -vswitchType External

[10/24/2022 10:18:22] Deploying Azure IoT Edge for Linux on Windows

 - WARNING: This is a Public Preview version of Azure IoT Edge for Linux on Windows Continuous Release, not intended for production use.
 - WARNING: A clean install may be required for production use once the final General Availability (GA) release is available. For more information, check https://aka.ms/AzEFLOW-CR.
 - Configuration does not exist. Creating a default configuration...

[10/24/2022 10:18:22] Creating configuration

 - Configuration created successfully

[10/24/2022 10:18:23] Enabling Microsoft Update. This will allow Azure IoT Edge for Linux on Windows to receive updates.

 - Microsoft Update is enabled.

[10/24/2022 10:18:23] Step 1: Preparing host for Azure IoT Edge for Linux on Windows

[10/24/2022 10:18:23] Checking host for required features

 - Checking the status of 'Microsoft-Hyper-V'
 - Checking the status of 'Microsoft-Hyper-V-Management-PowerShell'
 - Checking the status of 'Microsoft-Hyper-V-Hypervisor'
 - Checking the status of 'OpenSSH.Client*'
 - Verifying whether Hyper-V is enabled and functional
 - Hyper-V core services are active

[10/24/2022 10:18:30] Checking for virtual switch with name 'EFLOW'

 - The virtual switch 'EFLOW' of type 'External' is present

[10/24/2022 10:18:31] Step 2: Validating pre-requisites and deployment parameters...

 - Verifying host requirements for selected configuration (22 GB disk size, 1024 MB memory, 1 CPUs)

[10/24/2022 10:18:31] Verifying Host OS can support requested EFLOW configuration

[10/24/2022 10:18:31] Verifying required storage, RAM and number of cores are available

 - Drive 'C:' has 35 GB free
 - A minimum of 24 GB disk space is required on drive 'C:'
 - Host has 5768 MB free memory
 - A minimum of 1024 MB memory is required
 - Host has 4 CPU cores
 - A minimum of 1 CPU cores is required

[10/24/2022 10:18:31] Step 3: Configuring Azure IoT Edge for Linux on Windows runtime

[10/24/2022 10:18:34] Associating wssdagent service with nodectl

 - Creating container (EflowStorageContainer)

[10/24/2022 10:18:35] Creating vnet (name: EFLOW)

[10/24/2022 10:18:36] Verifying installation

 - Verifying expected Windows host binaries
 - Verifying expected Linux VM image
 - Extracting Linux VM image
 - Testing for ssh key
 - Generating SSH key...
 - Testing for wssdagent service
 - Testing if wssdagent is running
 - Testing if container resource is provisioned
 - Testing if vnet resource 'EFLOW' is provisioned

[10/24/2022 10:19:05] Step 4: Runtime configuration complete. Creating virtual machine

[10/24/2022 10:19:09] Creating virtual machine. Verifying host requirements for selected configuration (13 GB disk size, 1024 MB memory, 1 CPUs)

[10/24/2022 10:19:09] Verifying Host OS can support requested EFLOW configuration

[10/24/2022 10:19:09] Verifying required storage, RAM and number of cores are available

 - Drive 'C:' has 33 GB free
 - A minimum of 13 GB disk space is required on drive 'C:'
 - Host has 5801 MB free memory
 - A minimum of 1024 MB memory is required
 - Host has 4 CPU cores
 - A minimum of 1 CPU cores is required

[10/24/2022 10:19:20] Setting dynamically expanding virtual hard disk maximum size to 23 GB

 - Creating storage vhd (file: AzureIoTEdgeForLinux-v1-EFLOW)
 - Creating vnic (name: DESKTOP-415VL1V-EFLOWInterface)
 - Instantiating virtual machine (name: DESKTOP-415VL1V-EFLOW)

[10/24/2022 10:19:26] Error: Virtual machine creation failed!

[10/24/2022 10:19:26] Cleaning up...

[10/24/2022 10:19:26] Exception caught!!!

 - C:\Program Files\Azure IoT Edge\nodectl.exe  compute vm show --name DESKTOP-415VL1V-EFLOW -o json failed to execute [Error: rpc error: code = NotFound desc = [Store] unable to filter entity from store for type[VirtualMachineInternal], FilterName[Name], FilterValue[DESKTOP-415VL1V-EFLOW]: Not Found] at line 4288

[10/24/2022 10:19:26] Exception caught!!!

 - Unable to create virtual machine. (L1229)

[10/24/2022 10:19:26] In order to attempt another deployment, please uninstall the Azure IoT Edge msi and start from fresh

Unable to create virtual machine.

Hi @arminghasemazar.
Thanks for sharing that. Could you please share the WSSDAgent logs from C:\ProgramData\wssdagent\logs?
Thanks,
Francisco

wssdagent

There are many folders in C:\ProgramData\wssdagent\logs that are all empty. Besides, there are three files, which I attach below. (I added .txt to all to be able to be able to upload here directly)
agent-log-0.txt
logconf.txt
wssdagent.log.txt
Let me know if you can find something there.

Hi @arminghasemazar.
Thanks for sharing that. Could you please share the WSSDAgent logs from C:\ProgramData\wssdagent\logs?
Thanks, Francisco

There are many folders in C:\ProgramData\wssdagent\logs that are all empty. Besides, there are three files, which I attach below. (I added .txt to all to be able to be able to upload here directly)
agent-log-0.txt
logconf.txt
wssdagent.log.txt
Let me know if you can find something there.

Hi Armin,
Thanks for sharing the logs. I do see that the WSSDAgent fails to create the EFLOW VM.  Could you please share the Windows version you're using? You can use winver command.
Thanks,
Francisco

Hi Armin,
Thanks for sharing the logs. I do see that the WSSDAgent fails to create the EFLOW VM. Could you please share the Windows version you're using? You can use winver command.
Thanks, Francisco

Hey.

I I just tried to create an Ubuntu VM from inside the Hyper-V to test whether the Hyper-V is working and as you can see it is. So I don't see any issue with virtualization or PC config.

Hi Armin,
This issue was fixed in the latest EFLOW 1.4LTS version. Please use this version to get the latest feature updates and CVEs fixes.
Thanks,
Francisco

Hi Armin,
This issue was fixed in the latest EFLOW 1.4LTS version. Please use this version to get the latest feature updates and CVEs fixes.
Thanks, Francisco

Hi Franciso.
Thanks for the update. All other issues have been fixed. However, I still have problem with DPS symmetry key provision and I see the following error. I'm pretty sure I'm doing everything right and script and user config are correct. I also checked the config.yaml file and it looks ok. So something is wrong with 1.4.2 version while using EFLOW. I must say DPS provision within Ubuntu works fine (exactly the same device and same input). So seems like there are some inconsistency between EFLOW and DPS SymmetryKey. I'll  open a bug report in IoTEdge repo.
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]: 2022-11-15T14:38:56Z [ERR!] - Failed to provision with IoT Hub, and no valid device backup was found: DPS client error
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]: 2022-11-15T14:38:56Z [ERR!] - service encountered an error
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]: 2022-11-15T14:38:56Z [ERR!] - caused by: DPS client error
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]: 2022-11-15T14:38:56Z [ERR!] - caused by: invalid Content-Type; expected JSON
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]: 2022-11-15T14:38:56Z [ERR!] -    0: backtrace::capture::Backtrace::create
Nov 15 14:38:56 LDKCPH03816-EFLOW aziot-identityd[8727]:    1: backtrace::capture::Backtrace::new
Nov 15 14:38:56 LDKCPH03816-EFLOW systemd[1]: aziot-identityd.service: Main process exited, code=exited, status=1/FAILURE
Nov 15 14:38:56 LDKCPH03816-EFLOW systemd[1]: aziot-identityd.service: Failed with result 'exit-code'.

Hi @arminghasemazar,
Thanks for the clarification. If possible, could you please open a new issue with the logs and the error you're getting? I'll make sure to involve the IoT Edge team and try to troubleshoot the issue with them.
Thanks,
Francisco

Hi @arminghasemazar,
Thanks for the clarification. If possible, could you please open a new issue with the logs and the error you're getting? I'll make sure to involve the IoT Edge team and try to troubleshoot the issue with them.
Thanks, Francisco

Hi Francisco.
I think I solved my issue. It is either my misinterpretation of EFLOW deploy configuration or it is really misleading :D
So basically below is the correct interpretation:

symmKey: it's the derived device key of the device NOT the primary key of the DPS enrollment group
registrationId: It's the desired device name to be registered in the IoT hub NOT the derived device key.

And apparently the eflow provision function is not able to automatically generate derived key (based on device id and primary key of the dps). So one should first generate that device key (with the input of DPS primary key and device name) and then run the eflow deploy (with the input of device name and device key).
BTW, I think you need to update Values of eflowProduct parameter in the JSON schema table. The current value for the latest 1.4 LTS is "Azure IoT Edge 1.4 LTS X64" but it's not seen in the table.

Hi @arminghasemazar,
Thanks for the suggestions. I'll make sure to update the documentation and JSON schema table.
Thanks,
Francisco


fix: remove deprecation that breaks SDK

See comment bellow

More details.
We have been using model.mustache that is customised in the repository:
https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/c2e0d76158fe955b227e200491bbaf06b33cd8a9/openapi/templates/model.mustache
This change does specifically rename fields that are deprecated in order to be able to return them.
However in circumstances where:

FIeld is required
FIeld is deprecated

Any generator that doesn't use that approach would fail:

In general it seems reasonable that a field should not be deprecated and required at the same time. @wtrocki can you confirm that the CLI / UI is able to deal with this field missing?

In general it seems reasonable that a field should not be deprecated and required at the same time

I am not sure about this. Why can't a required field be deprecated from the OpenAPI point of view? In any case I would like to reiterate that fundamental design point is independent from the issue being reported meaning we can tackle them at separate times.

In general it seems reasonable that a field should not be deprecated and required at the same time

I am not sure about this. Why can't a required field be deprecated from the OpenAPI point of view?

+1 with this. Something being deprecated it does not mean its original behavior should change.

In any case I would like to reiterate that fundamental design point is independent from the issue being reported meaning we can tackle them at separate times / independently

+1.

@wtrocki #1030 is merged now, can you please rebase when you get a chance?

@pb82 Done rebase. Thank you so much for taking look at this.

I'm ok to rebase it again after I get approval

@riccardo-forina is UI ok with this new behaviour for supported_instance_types as mentioned above?

I'm not sure I fully grasp the impact of this, but given how all fields are nullable the UI does a lot of defensive coding, so not having the property shouldn't be a problem.

There is no impact on any client because:

All our clients including UI and CLI are already using that modification on our side (we made manual changes in SDKs to make things compile
deprecation being an object. Problem would be if deprecated element would be an base field like boolean

Rebasing 🤹


publicRuntimeConfig variables on client side always equals undefined

Versions

nuxt: @nuxt/cli v2.15.8
node: v12.22.10

Reproduction
PROBLEM:
Env variables in publicRuntimeConfig sections works on server, but client always are undefined, if use in vuex process.env
CASE:

Fill .env file, for example:
TEST=1
store/index

if (process.browser) {
    console.log(process.env.TEST);
}

On server it works, but on client env.TEST is undefined
if use dotenv module, it works on server and client

It stops migrate from dotenv to native publicRuntimeConfig environments variables

@nestle49
Are you defining publicRuntimeConfig in nuxt.config.js like this
publicRuntimeConfig: {
testPublicenv: process.env.TEST,
},

once you have this you can use
nuxt config to access this like $config.testPublicenv

@nestle49 Are you defining publicRuntimeConfig in nuxt.config.js like this publicRuntimeConfig: { testPublicenv: process.env.TEST, }, once you have this you can use nuxt config to access this like $config.testPublicenv

It is begin of store/index.ts file.
I haven't access to $config here and can't use context. I can use only process.env, but on client process.env.example equal undefined

In vuex store you could use nuxtservereinit to access nuxt $config.

No, I can't. It's outside hooks! In plugins!
if (debug) {
    pluginsBeforeExport.push(
        createLogger({
            // do not output on the server (because they're shitting)
            logMutations: process.browser && !process.env.VUEX_LOGGER_HIDE_MUTATIONS,
            logActions: process.browser && !process.env.VUEX_LOGGER_HIDE_ACTIONS
        })
    );
}

....

export const state = () => {
    return {};
};

....

NuxtServerInit

It's reason why i can't use nuxtServerInit, context, other hooks!
I can use only process.env here!
And it's work on server, but doen't work on client side for runtimePublicConfig, the same time it's correct work server and client for dotenv module

We are approaching the Nuxt 2 EOL date (June 30, 2024) - see this article for more information. This is advance warning that I'm going to close this issue then, as it's currently marked as a Nuxt 2 related bug.
If it's a critical or security issue, please do comment and let me know, in case it is possible to address it before the EOL date.
If it's a an issue you think is relevant for Nuxt 3, please feel free to open a fresh issue (or just comment here so I can update labels, etc.). 🙏
Thank you for your understanding and for your contribution to Nuxt. ❤

It's the day, at last. Nuxt 2 is now marked end-of-life.
My apologies we never got round to resolving this bug in the 2.x branch, but we do have to draw a line somewhere. Again, if you think this is still relevant for Nuxt going forward, please feel free to open a fresh issue (or just comment here so I can update labels, etc.). 🙏


SNIP-1: outdated

I believe SNIP-1 is outdated (reviewer for example) and could be reworked to match some specific features of Starknet

up?

Up


Typo within LppFrame.add_humidity

When reviewing https://github.com/thiasB/terkin-datalogger/commit/11bd35be by @thiasB, I just spotted a typo within lpp_frame.py.
https://github.com/smlng/pycayennelpp/blob/c0e3bf6f44d402be4f43acaad1b3b217177868c2/cayennelpp/lpp_frame.py#L103
add_humitidy should actually be called add_humidity [1], right?
I suggest to rename the main function and to provide an alias for backward-compatibility like add_humitidy = add_humidity at the very bottom of the module.

@amotl nice find, I guess I should add a spell checker to the travis.yml to avoid such in the future. Do you really think we need backwards compatibility? I would rather make a new release and put in a note on this change.
So people can adapt their code or fix the package version to the old one.
Anyhow, you wanna make a PR?

I go along with Andreas suggestion. You may remove the alias in the release following the next.


Need full sticky scrolling line

Notice that the sticky scroll line has a gap on the far right of the editor and does not cover the interface, which is generally unsightly.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

Please tell me which one was duplicated with.


Automatically delete bags that fail virus checks

Can someone from @RockefellerArchiveCenter/marist confirm/point to code that does this?


clearab from OPS portal: Merge from master to live

OPS Build status updates of commit 9439050:
:clock10: Preparing: average preparing time is 46 sec(s)

OPS Build status updates of commit 9439050:
:clock10: Incremental building: average incremental building time is 20 sec(s)

OPS Build status updates of commit 9439050:
:warning: Validation status: warnings

File
Status
Preview URL
Details

.openpublishing.redirection.json
:warning:Warning

Details

msteams-platform/concepts/concepts-overview.md
:warning:Warning

Details

msteams-platform/concepts/tabs/tabs-in-sharepoint.md
:warning:Warning

Details

msteams-platform/resources/schema/manifest-schema.md
:warning:Warning

Details

msteams-platform/redirects/get-started-dotnet
:white_check_mark:Succeeded

msteams-platform/redirects/get-started-nodejs
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/activityfeed.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/appcapabilities.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/apps-package.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/apps-sideload.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/auth.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/authentication.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botapis.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botevents.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botmenu.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/bots-channel-conversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/bots-personal-conversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/bots.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/bots1on1.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botsadd.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botsconversation.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botscreate.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botsinchannels.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/botsmessages.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/cards-actions.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/code.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/compose-extensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/composeextensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/connectors.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/createconfigpage.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/createcontentpage.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/createpackage.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/cross-domain.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/crossdomain.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/custom-bot.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/debugging.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/deeplinks.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/design.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/faq.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/feedback.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/get-started-dotnet.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/get-started-nodejs.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/getusercontext.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/graph.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/index.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/jslibrary.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/messaging-extensions.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/outgoingwebhook.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/prerequisites.md
:white_check_mark:Succeeded

msteams-platform/redirects/msteams-docs_deleted_redirects_2019-2-7_14-15-576/previewfeatures.md
:white_check_mark:Succeeded

This comment lists only the first 50 files in the pull request.

.openpublishing.redirection.json

[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/concepts/connectors/connectors-creating.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/get-started/get-started-dotnet.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/get-started/get-started-nodejs.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/publishing/apps-package.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/scenarios/bots-channel-conversation.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/scenarios/bots-personal-conversation.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/scenarios/scenarios.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/concepts/compose-extensions.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/concepts/cards-actions.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/concepts/custom-bot.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/concepts/messaging-extensions.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/resources/general/cross-domain.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/resources/general/requirements.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.
[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'msteams-platform/resources/design/framework/compose-extensions.md'. However, the file already exists in the Git repo in conflict with the redirection rule. OPS will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.

msteams-platform/concepts/concepts-overview.md

Line 17: [Warning] Invalid file link:(~/concepts/apps/apps-overview).
Line 18: [Warning] Invalid file link:(~/concepts/tabs/tabs-overview).
Line 19: [Warning] Invalid file link:(~/concepts/bots/bots-overview).
Line 20: [Warning] Invalid file link:(~/concepts/cards/cards).
Line 21: [Warning] Invalid file link:(~/concepts/authentication).
Line 22: [Warning] Invalid file link:(~/concepts/activity-feed).
Line 23: [Warning] Invalid file link:(~/concepts/connectors/connectors).
Line 24: [Warning] Invalid file link:(~/concepts/bots/bots-notification-only).
Line 25: [Warning] Invalid file link:(~/concepts/messaging-extensions).
Line 26: [Warning] Invalid file link:(~/concepts/task-modules/task-modules-overview).
Line 27: [Warning] Invalid file link:(~/concepts/deep-links).

msteams-platform/concepts/tabs/tabs-in-sharepoint.md

Line 76: [Warning] Invalid file link:(~/concepts/apps/apps-package).
Line 78: [Warning] Invalid file link:(~/concepts/tabs/tabs-context).

msteams-platform/resources/schema/manifest-schema.md

Line 176: [Warning] Invalid file link:(~/concepts/bots/bots-create).
Line 225: [Warning] Invalid file link:(~/concepts/apps/apps-package#icons).
Line 288: [Warning] Invalid file link:(~/concepts/bots/bots-menus).
Line 352: [Warning] Invalid file link:(~/publishing/apps-publish#updating-your-app).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Sync test code with Cocoon

This is the last sync between https://github.com/flutter/cocoon/tree/master/agent/lib/src and the main repo before killing the test sources in Cocoon.
/cc @cbracken

lgtm


Update Routing docs

Dynamic route params are no longer added to the instance of the component but rather the .params property of the component, updated docs accordingly.

 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.


Fix local package installation

When packaging the dependencies only the first local package would be
included in the final bundle. This change adds support for any number
of local directory links to be treated as buildable dependencies. Tests
were also added for the case of 1 or 2 local directory links specified
in the requirements.txt.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@TheSriram can you review?


[ENH]Update Channel Selection code

Reference Issues/PRs
Fixes #107

What does this implement/fix? Explain your changes.
Updated channel selection code.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Did you add any tests for the change?

Any other comments?

PR checklist

For all contributions

[ ] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[ ] The PR title starts with either [ENH], [MNT], [DOC], or [BUG] indicating whether the PR topic is related to enhancement, maintenance, documentation, or bug.

For new estimators

[ ] I've added the estimator to the online documentation.
[ ] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

Thanks @lmmentel. I will update the docstring and type hints. However, I'm not sure about changing name of classes, as they refer to class in the dataset, and referenced paper.

can you change this to use numpy3d in shape (n_instances, n_dimensions, series_length)? We are moving to remove nested_univ and pandas from classification related code

I'm happy with this @lmmentel would you like to review again?


emulation-dumper fails for MHWilds (OTB)

Describe the bug
I tried to convert the il2cpp_dump.json created in REF Nightly 01032 using emulation-dumper.py, an error occurred.
Upload logs and any crash dumps
68.124025%ace.AceException
68.124402%ace.AceException.AssertException
68.124779%ace.AceGA
Traceback (most recent call last):
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 284, in hook_code
    dis = next(cs.disasm(emu.mem_read(address, size), address, 1))
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\unicorn\unicorn.py", line 462, in mem_read
    raise UcError(status)
unicorn.unicorn.UcError: Invalid memory read (UC_ERR_READ_UNMAPPED)
 EXCEPTION 0x140024F60

after any inputs:
Traceback (most recent call last):
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 883, in <module>
    fire.Fire(main)
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\fire\core.py", line 143, in Fire
    component_trace = _Fire(component, args, parsed_flag_args, context, name)
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\fire\core.py", line 477, in _Fire
    component, remaining_args = _CallAndUpdateTrace(
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\fire\core.py", line 693, in _CallAndUpdateTrace
    component = fn(*varargs, **kwargs)
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 856, in main
    struct_layout = detect_members_chain(struct_name, chains[struct_name]["deserializer_chain"])
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 799, in detect_members_chain
    "layout": detect_members(int(entry["address"], 16))
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 770, in detect_members
    emu.emu_start(meta_frame["start"], deserializer_start + 0x10000)
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\unicorn\unicorn.py", line 344, in emu_start
    raise self._hook_exception
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\unicorn\unicorn.py", line 212, in wrapper
    return func(self, *args, **kwargs)
  File "C:\Users\pc\AppData\Local\Programs\Python\Python38\lib\site-packages\unicorn\unicorn.py", line 507, in _hookcode_cb
    cb(self, address, size, data)
  File "E:\desktop\REFramework-master\reversing\rsz\emulation-dumper.py", line 414, in hook_code
    if dis.mnemonic != "ret":
UnboundLocalError: local variable 'dis' referenced before assignment

Identify the REFramework version
REF Nightly 01032
Additional context
OS: Windows10 (Japanese)
Python: 3.8.10
I have attached the JSON data for ace.AceGA where the error occurs.
ace.AceGA.json

Working on it. Lots of inlined functions which is causing some massive problems with the dumper, but I can still work around it.

Understood. I will wait.
Thanks for the big project release and update.

Fixed


Can't issue an ssl certificate for domains proxied by Cloudflare

Hello!
I was playing around with lua-resty-auto-ssl and everything worked  perfectly until I tried issuing a certificate for a domain proxied by Cloudflare (orange cloud).
This is/are the error/s that I'm getting for the domain that is proxied:
2021/05/27 22:49:03 [error] 102203#102203: *20 [lua] ssl_certificate.lua:68: issue_cert(): auto-ssl: failed to obtain lock: timeout, context: ssl_certificate_by_lua*, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2021/05/27 22:49:03 [error] 102203#102203: *20 [lua] ssl_certificate.lua:291: auto-ssl: could not get certificate for xyz.example.com - using fallback - failed to get or issue certificate, context: ssl_certificate_by_>
2021/05/27 22:49:03 [error] 102203#102203: *19 open() "/usr/local/openresty/nginx/html/.well-known/acme-challenge/dImjROwMMdY-dfPkAE-edit" failed (2: No such file or directory), client: <IP_ADDRESS>, serv>
2021/05/27 22:49:03 [error] 102203#102203: *5 [lua] lets_encrypt.lua:40: issue_cert(): auto-ssl: dehydrated failed: env HOOK_SECRET=edited HOOK_SERVER_PORT=8999 /usr/l>
startup_hook
Processing xyz.example.com
 + Signing domains...
 + Generating private key...
 + Generating signing request...
 + Requesting new certificate order from CA...
 + Received 1 authorizations URLs from the CA
 + Handling authorization for xyz.example.com
 + 1 pending challenge(s)
 + Deploying challenge tokens...
deploy_challenge
 + Responding to challenge for xyz.example.com authorization...
invalid_challenge
Invalid challenge: DOMAIN=xyz.example.com RESPONSE={
  "type": "http-01",
  "status": "invalid",
  "error": {
    "type": "urn:ietf:params:acme:error:unauthorized",
    "detail": "Invalid response from https://xyz.example.com/.well-known/acme-challenge/dImjROwMMdY-dfPkAE-edit [2606:4700:3035::ac43:8192]: \"\u003chtml\u003e\\r\\n\u003chead\u003e\u003ctitle\u003>
     "status": 403
  },
  "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/13492436985/xRMMmQ",
  "token": "dImjROwMMdY-dfPkAE-edit",
  "validationRecord": [
    {
      "url": "http://xyz.example.com/.well-known/acme-challenge/dImjROwMMdY-dfPkAE-edit",
      "hostname": "xyz.example.com",
      "port": "80",
      "addressesResolved": [
        "<IP_ADDRESS>",
        "<IP_ADDRESS>",
        "2606:4700:3035::ac43:8192",
        "2606:4700:3036::6815:2be"
      ],
      "addressUsed": "2606:4700:3035::ac43:8192"
    },
    {
      "url": "https://xyz.example.com/.well-known/acme-challenge/dImjROwMMdY-dfPkAE-edit",
      "hostname": "xyz.example.com",
      "port": "443",
      "addressesResolved": [
        "<IP_ADDRESS>",
        "<IP_ADDRESS>",
        "2606:4700:3035::ac43:8192",
        "2606:4700:3036::6815:2be"
      ],
      "addressUsed": "2606:4700:3035::ac43:8192"
    }
  ],
  "validated": "2021-05-27T22:48:32Z"
}
 err: nil, context: ssl_certificate_by_lua*, client: <IP_ADDRESS>, server: <IP_ADDRESS>:443
2021/05/27 22:49:03 [error] 102203#102203: *5 [lua] ssl_certificate.lua:97: issue_cert(): auto-ssl: issuing new certificate failed: dehydrated failure, context: ssl_certificate_by_lua*, client: <IP_ADDRESS>, server: <IP_ADDRESS>>
2021/05/27 22:49:03 [error] 102203#102203: *5 [lua] ssl_certificate.lua:53: issue_cert_unlock(): auto-ssl: failed to unlock: lock does not match expected value, context: ssl_certificate_by_lua*, client: <IP_ADDRESS>, server>
2021/05/27 22:49:03 [error] 102203#102203: *5 [lua] ssl_certificate.lua:291: auto-ssl: could not get certificate for xyz.example.com - using fallback - failed to get or issue certificate, context: ssl_certificate_by_l>

Here is my nginx.conf (pretty much the default one but I'm using redis to store the ssl certificates):
user root;

events {
  worker_connections 1024;
}

http {
  access_log /var/log/openresty/access.log;
  error_log /var/log/openresty/error.log;

  lua_shared_dict auto_ssl 10m;
  lua_shared_dict auto_ssl_settings 64k;
  resolver <IP_ADDRESS> ipv6=off;

  init_by_lua_block {
    auto_ssl = (require "resty.auto-ssl").new()

    auto_ssl:set("renew_check_interval", 86400)
    auto_ssl:set("storage_adapter", "resty.auto-ssl.storage_adapters.redis")
    auto_ssl:set("redis", {
      host = "x.x.x.x",
      auth = "password",
      port = "6379",
      prefix = "ssl"
    })

    auto_ssl:set("allow_domain", function(domain, auto_ssl, ssl_options, renewal)
      return true
    end)
    auto_ssl:init()
  }

  init_worker_by_lua_block {
    auto_ssl:init_worker()
  }

  server {
    listen 443 ssl;

    ssl_certificate_by_lua_block {
      auto_ssl:ssl_certificate()
    }

    ssl_certificate /etc/ssl/resty-auto-ssl-fallback.crt;
    ssl_certificate_key /etc/ssl/resty-auto-ssl-fallback.key;
  }

  server {
    listen 80;

    location /.well-known/acme-challenge/ {
      content_by_lua_block {
        auto_ssl:challenge_server()
      }
    }
  }

  server {
    listen <IP_ADDRESS>:8999;

    client_body_buffer_size 128k;
    client_max_body_size 128k;

    location / {
      content_by_lua_block {
        auto_ssl:hook_server()
      }
    }
  }
}

After trying once to issue the ssl certificate for the proxied domain this is what I have in redis:
1) "ssl:xyz.example.com:challenge:lZsCo9o6iNsNKnTPNGjnUavffxTBI0I-cdwfef"
2) "ssl:xyz.example.com:challenge:XfxXtUQ9y08GIrO8Il3MY5_t94ZOxduYHRg"
3) "ssl:xyz.example.com:challenge:xe9E_szfJ_xcRD70d3uGJGaur5QFH-6co-FLtaGdY"
4) "ssl:xyz.example.com:challenge:BQaUHoAHk1NiauSJNvLmRPSd5eS1FoyK9WEsa1Vp9NA"
5) "ssl:xyz.example.com:challenge:dImjRzwMtdY-ddo2ix-yx8izv_qP_o-cu5KxACveqQo"

And...again, if I use DNS only instead of Proxied the ssl certificate is issued without a problem.
Can somebody help me understand what's happening? Is there something that I can change/implement in order to allow both proxied/dns only domains to get their own ssl certificate?
Thank you! :D

If your site is behind CloudFlare proxy, the best option is to not use Let’s Encrypt at all, but instead to use Cloudflare’s Origin CA: https://blog.cloudflare.com/cloudflare-ca-encryption-origin/

@gjongenelen I failed to mention that I'm trying to generate certificates for multiple domains and just some of them are on Cloudflare. I apologize for that :( .
Is there a way to generate a certificate for both, proxied and not proxied domains (through Crowdrole or any other dns console/proxy provider) ?

Do you have "Always SSL/HTTPS" option enabled in Cloudflare. Depending on your config, this may create issues as cloudflare will forward acme challenges to your HTTPS handler.

Oh, turning "Always SSL/HTTPS" off fixed it! Can you give me more info regarding the last part of your answer: "Depending on your config, this may create issues as cloudflare will forward acme challenges to your HTTPS handler" - how can it be configured in a way that would allow me to use "Always SSL/HTTPS"?
Thanky you!  I think copying this block to your https-handler would fix the issue. Please copy/duplicate and don't remove it from the http-handler, as let's encrypt will still use the http-handler for domains which aren't proxied via cloudflare.

Hey @gjongenelen , thank you so much for helping me (and hopefully others) but unfortunatelly that one didn't work (copy/paste the acme challenge location block from port 80 to 443) , i still can't issue certificates for domains that have "Always use https" enabled on cloudflare. Any other ideas? Thank you! 😄

You probably have:
location /.well-known/acme-challenge/ {
      content_by_lua_block {
        auto_ssl:challenge_server()
      }
    }

in your http (tcp/80) handler. I think copying this block to your https-handler would fix the issue. Please copy/duplicate and don't remove it from the http-handler, as let's encrypt will still use the http-handler for domains which aren't proxied via cloudflare.

This will probably wont work, letsencrypt always connects on http for challenge url

Any idea how one could do on-the-fly DNS validations and not try to generate certificates for those proxied calls ? Would it be adding custom code in allow_domain function ?

Sorry to hijack the post, but we're facing a similar issue. We've just moved over from Route53 to CloudFlare and have now turned on DNS proxy. With proxy turned on we get a similar "ERR_SSL_VERSION_OR_CIPHER_MISMATCH" error for custom domains that we pass via our openresty auto SSL EC2 server to have the SSL certificate created.
I've tried turning off the "Always SSL/HTTPS" setting but that didn't seem to make a difference.
We are also doing a DNS lookup in our lua script, so I'm not sure if that makes a difference.
I don't suppose anyone has any suggestions for other things we might want to check?

Hi Benjamin ,
Cloudflare also uses Letsencrypt to issue the certificates. So in case if
you have already issued a certificate using letsencrypt , there is a high
probability of cloudflare not issuing the certificate for same domain .
Few options :

Import your cert and pem in cloudflare as custom certificate
Dont use autossl in backend for endpoints using cloudflare
revoke the certificate generayed by autossl enabling cloudflare to issue
the certificate

Let know if you require technical support for it
Thanks & Regards,
Abhishek Sharma
On Fri, 27 Jan 2023, 8:16 pm Benjamin Dell, @.***>
wrote:

Sorry to hijack the post, but we're facing a similar issue. We've just
moved over from Route53 to CloudFlare and have now turned on DNS proxy.
With proxy turned on we get a similar "ERR_SSL_VERSION_OR_CIPHER_MISMATCH"
error for custom domains that we pass via our openresty auto SSL EC2 server
to have the SSL certificate created.
I've tried turning off the "Always SSL/HTTPS" setting but that didn't seem
to make a difference.
We are also doing a DNS lookup in our lua script, so I'm not sure if that
makes a difference.
I don't suppose anyone has any suggestions for other things we might want
to check?
—
Reply to this email directly, view it on GitHub
https://github.com/auto-ssl/lua-resty-auto-ssl/issues/258#issuecomment-1406603058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHU3WWMXLW5A3BIUHBSU3ZTWUPNTTANCNFSM45VJ6NAA
.
You are receiving this because you commented.Message ID:
@.***>

Amazing, thanks Abhishek. Just wanted to clarify a couple of things if that's OK.
I don't think we actually created a cert and pen on our EC2 SSL server (the one that uses auto SSL to generate SSL certs for our customers custom domains). Or will there be one on the server that im not aware of?
I'd be interested in some technical help if that's OK? Is that something I can pay you for perhaps?

Autossl generates a certificate and keeps it on a local server. Location is dependent on configuration. For default file storage you can find in some subidrectory of /etc/resty-auto-ssl location. You can run locate or find command to search the certificate
I need to understand and evaluate the requirements based on the platform. We can start a new communication thread in case you require support, please DM me directly

Thanks - I've just sent you an email to see if you're able to help directly.


Awake is not working properly

Microsoft PowerToys version
0.78.0
Installation method
GitHub
Running as admin
No
Area(s) with issue?
Awake
Steps to reproduce
Until almost a week ago, Awake was working very good, however now, even with the option "Keep awake indefinitely" the pc doens't remain active. I use "Awake" for keeping the status in "Microsot Teams". Often I'm in a "on site meeting" but I use Awake to keep the "In meeting" status, Now, since last week, it doesn't work as before. It goes automatically after some minutes (5 or less) to "idle" or "away", :(
Thank you for your help, and I hope reporting the bug, could help improve your product.
✔ Expected Behavior
When I choose "Keep awake" the computer remains active and Microsoft Teams status stays at he status I was...
❌ Actual Behavior
Keep awake" all the options (30 mins/ 1 hour/ 2 hours/ indefinitely) doesn't work and the computer is not longer active. It goes sleep anyway.
Other Software
Microsoft teams M365.

Something recently changed with Teams. This is not an issue with Awake.
/dup #25256


throw specialized exception for NOSCRIPT answer

Expected behavior
Jedis should throw specialized exception(e.g. JedisNoscriptDataException) if evalsha answers with NOSCRIPT ('NOSCRIPT No matching script. Please use EVAL.').
Caller should retry with eval in this case
Actual behavior
Generic JedisDataException is thrown. So the only way to catch NOSCRIPT at the client side is to use
try {
   ret = cluster.evalsha(sha1Digest, keys, args);
} catch (JedisDataException ex) {
   if (ex.getMessage().startsWith("NOSCRIPT")) {
       //retry with eval + lua script body
   }
}

I suppose best way to improve it is to modify redis.clients.jedis.Protocol.processError. I can prepare PR if such solution is acceptable

Closed by #1353


Compile the program check_whitespace, find and fix any leaks it may have

Refer to Pre-Lab 2, Task 1
https://github.com/umm-csci-3412-fall-2022/c-programming-pre-lab-caidongting0823#using-valgrind-to-find-memory-leaks

This Issue has been finished and will be closed. : )


Add changelog / releases / tags

Have you considered adding documentation for releases? Right now I can't seem to find any details regarding what has changed (I'm aware I could look at the commits, but that's a bit cumbersome). Would you be open to adding a CHANGELOG.md file or changing the publish process to describe updates on Github releases?

Well since this is an npm package, you could use something like np to do the releasing. I commonly attach it as an package.json script called pub which just executes np. This is nice because it:

Publishes the package to npm
Runs tests before publishing
Commits and tags the new version
Pushes the commit and tag automatically

For the changelog, it could be based off the commits so no extra work is needed. Using something like generate-changelog could make this a breeze.
If you're interested in any part of this process, I'd happily make a PR.

@perry-mitchell sounds good to me. I would accept a PR for this :)

closing due to inactivity


slide 8 map vs flatmap

based on what prof mentioned in the lecture, is it correct to say that if you are using two maps in a row, you ALWAYS have to use flatMap before map to avoid the 'bad return type' error?

No, not necessarily, imo I use flatMaps if my return type for your mapping function produces an Optional or Stream, then the flatMap will be useful to unwrap the values and map it accordingly

Take any wrapper like Optional with an element x wrapped inside. If the function takes in a x and produce Optional(y), you use flatMap here. For example it is possible to use map twice and i still want to map. E.g there is 2 function. One maps x -> y and other maps y -> z. In this case I would use map twice, once to turn x into y so i can then use the 2nd function to map y to z

The lecture note is referring to two generators (or unboxing), not
two maps. Here the two generators are m1 and m2
   Log<Pair<A,B>> seqP(Log<A> m1, Log<B> m2) {
    // below is a do-notation syntactic sugar
    do {
	    x <-m1;  // view this generator as an unboxing
	    y <-m2;  // view this 2nd generator as other unboxing
	    unit(new Pair(x,y))
	}
   }

The do-comprehension is a syntactic sugar notation for
flatMap. If you follow the translatio rules given,
you will get:
  Log<Pair<A,B>> seqP(Log<A> m1, Log<B> m2) {
      // below is a first-order syntactic sugar
      m1.flatMap( x ->
	    m2.flatMap (y -> unit(new Pair(x,y)))
  }

This is also equivalent to below where the
last generator is translated to a map instead
of flatMap.
  Log<Pair<A,B>> seqP(Log<A> m1, Log<B> m2) {
     // below is a first-order syntactic sugar
     m1.flatMap( x ->
	   m2.map (y -> new Pair(x,y))
  }

I think if the first map transforms each element into another collection or stream, then yep you gotta use flatMap afterwards. But if the first map operation transforms each element into a single element, then you can use map again

hi it is not wrong to use 2 maps consecutively (e.g. Optional.of(3).map(x -> x+1).map(x -> x*2))
you only need to use flatMap if the function that you want to apply to your value maps the value to another optional. (e.g. Optional.of(3).flatMap(x -> Optional.of(x))). In this case, flatMap will flatten the Optionals such that your output is only wrapped in one Optional. However if you use map instead, what map does is it takes the value in the original Optional, performs the function, and then wrap it back into another Optional causing your output to be Optional[Optional[3]]. Hope this helps!


cloudflare

Hi , how i can use this script? how run it?

This is not a script. It's a library to use with your own python scripts/programs etc. The basic usage can be found in the readme: https://github.com/pavlodvornikov/aiocfscrape#basic-usage
If you got a more specific question feel free to ask. If this already answered your question please close the issue.

Hi im swdlo9. I don't know how to use library with a python script, please can you tell me an example how to use that library? thanks


Ledger Curve fix

Ledger's provider underestimated the gas required for transaction when using Curve. This fixes the issue.

Is this ledger specific? I think this is probably using the estimateGas function from web3-provider-engine, it probably should be a problem for other connectors if it is for ledger. We might need to pass some arguments to the constructor of web3-provider-engine or even the connectors if they allow it?


Creation/update of an invoice in sent status

[x] Journal missing at the time of creation.
[x] Inventory entry amount (wrong amount) used to make entry.

Issue Closed


create_case_metadata workflow, make invisible to end user

There are possibilities in ERT to make the workflow automatically hooked for all users. This would make it possible to remove this from local config.
This should be considered.

[ ] How do we make sure lots of FMU workflows don't instantly crash when this takes effect? How do we handle non-standard setups, etc
[ ] How do we get rid of the optional arguments which would then not be available to end users, e.g. --sumo and --config_path.

When contents of global_variables or path to global_variables is available in a way that does not require user input, this workflow can automatically hooked for all users aka made invisible.
This will most likely also require some config element stating if a specific model setup is onboarded on Sumo or not.


Support combination of milestone and release name

Fixes #132

@GeertvanHorrik your changes have been merged, thanks for your contribution 👍


Add fortran-curl as dependency and a minimal GET request example

Add fortran-curl as dependency and a minimal GET request example, also added a simple_get.f90 file in example folder

Alright, I'll make the required changes

I suggest also organizing defining the derived types and their related procedures in their respective modules, and use http_client module only to make available the public API, i.e. response_type, http_request, HTTP_GET etc.

Thanks, @milancurcic. So basically, I need to generate four files.

request.f90
response.f90
client.f90
`http-client.f90

request.f90 should contain the definition of the request_type along with its corresponding helper procedures. response.f90 should have the definition of the response_type and its helper procedures. Similarly, client.f90 should contain the client_type and its helper procedure. Finally, http-client.f90 will provide access to the public API.

Thanks, @milancurcic. So basically, I need to generate four files.

request.f90
response.f90
client.f90
`http-client.f90

request.f90 should contain the definition of the request_type along with its corresponding helper procedures. response.f90 should have the definition of the response_type and its helper procedures. Similarly, client.f90 should contain the client_type and its helper procedure. Finally, http-client.f90 will provide access to the public API.

Yeah, Looks good. But maybe use snake_case for naming http_client.f90 as well ?

I see, good point. In that case, should we rename our package to just http? Shorter, simpler (no hyphen caveats), although less specific, but that's probably fine.

OK, let's go ahead then and rename it in pyproject.toml and I'll rename the repo after we merge the PR.

It just occurred to me that this PR is also on a branch on fortran-lang/http-client rather than your fork (rajkumar/http-client). Please work only on development branches on your fork going forward. I'll merge this PR as is to not complicate further, and let's tackle the outstanding comments in separate PRs.


Fixed Dangerfile if pr_body or pr_title is empty

Fixes https://circleci.com/gh/fastlane/fastlane/142
Dangerfile:3:in `block in parse':  (Danger::DSLError)
[!] Invalid `Dangerfile` file: undefined method `+' for nil:NilClass. Updating the Danger gem might fix the issue.

 #  from Dangerfile:3
 #  -------------------------------------------
 #
 >  if (pr_body + pr_title).include?("WIP")
 #    warn("Pull Request is Work in Progress")
 #  -------------------------------------------
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/lib/danger/dangerfile.rb:86:in `eval'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/lib/danger/dangerfile.rb:86:in `block in parse'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/lib/danger/dangerfile.rb:82:in `instance_eval'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/lib/danger/dangerfile.rb:82:in `parse'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/lib/danger/commands/runner.rb:44:in `run'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/claide-0.9.1/lib/claide/command.rb:312:in `run'
	from /tmp/vendor/bundle/ruby/2.0.0/gems/danger-0.5.2/bin/danger:5:in `<top (required)>'
	from /tmp/vendor/bundle/ruby/2.0.0/bin/danger:22:in `load'

:+1: Nice!

Once https://github.com/danger/danger/issues/121 gets merged and released we can remove this workaround https://github.com/danger/danger/issues/121


python3Packages.pyparsing: 2.4.6 -> 2.4.7

Motivation for this change
Bump to the latest version.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Please change the commit message to python3Packages.pyparsing
Please target staging branch as this causes a massive rebuild.

Done. Sorry for the noise @ other maintainers who were pinged while I was switching target branches.

Please change the commit message to python3Packages.pyparsing
Please target staging branch as this causes a massive rebuild.

Done. Sorry for the noise @ other maintainers who were pinged while I was switching target branches.

Known issue. A fix for this is in the making.

@GrahamcOfBorg build python3Packages.requests

@GrahamcOfBorg build python3Packages.requests

Did you perhaps mean this to be python3Packages.pyparsing, or am I missing something?

Did you perhaps mean this to be python3Packages.pyparsing, or am I missing something?

I guess requests has pyparsing as its dependency, so Jonathan wants to check whether it still builds

yea, a successful requests build means that sphnix, pytest, and a few other critical libraries all work. Usually doesn't take too long, but looks like staging just had the gcc10 changes applied, so it has to rebuild from stdenv


Models migrations

Coverage increased (+39.5%) to 79.624% when pulling 23c5fa9a0b1824b98347e407df2325dc22095068 on models_migrations into d8f96e8ae2a4cb6e01fef7ef9006c9ed4a03a5a5 on master.


Clean up Cargo.toml files and use workspace inheritance

Remove redundant/incorrect "documentation" keys from Cargo.toml
Remove redundant "readme" key from Cargo.toml
Inherit package.repository from the workspace
Inherit package.homepage from the workspace

Haven't gotten to the "t"s yet of updating my repos to my latest template...


error running a local server

When running turbiniactl -R server, I get the following error:

[INFO] Turbinia version: 20181004
[ERROR] --run_local flag is not compatible with server/worker flags

I thought turbinia could run a server and workers locally?  My TASK_MANAGER is currently set to Celery.

-C is the flag you will want to use if you're intending to use Celery instead of GCP (include it when starting the server, workers and sending requests). We're working on updating the documentation.
-R will:

Run completely locally without any server or other infrastructure. This can be used to run one-off Tasks to process data locally.

Thanks for the report @jgrover and the answer @ericzinnikas :)
I think this one is solved now, so I'll close this, but feel free to re-open if you are still running into issues.


How to contribute to this repo?

Hi. I wonder if this repo accept recommendation (or PR of some sort). I've built a Taichi-lang based renderer that supports multiple PBR features, from volumetric tracers, BDPT to transient radiance renderer, etc. I believe the completeness should be appropriate, for this renderer to be categorized in Renderer. The repo can be found here: AdaPT.

Hi, sure, we are accepting contributions! An example would be this: https://github.com/taichi-dev/awesome-taichi/pull/14/files
Thank you! AdaPT looks great!

Thanks! I'll be making a PR soon.


DefaultAuthenticationPolicy parameter missing

The -DefaultAuthenticationPolicy parameter that is live in the Exchange Online CMDLET appears to be missing from this doc.

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

ID: 9e3ab3f0-cc05-e279-8876-6da0b323bcac
Version Independent ID: bfb49814-d60b-564a-25cc-f902dfa42b10
Content: Set-OrganizationConfig (exchange)
Content Source: exchange/exchange-ps/exchange/organization/Set-OrganizationConfig.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@JaMcCarter, I added it.
Thanks for the feedback.


tor: fix build

Monotonic timer test expects sleep(200ms) to take at most 1s. On loaded systems like hydra, it's possible for such a test to take longer than 1 second.
Tests expecting sleep(200ms) to take at least 175ms weren't removed, because load shouldn't cause sleep to be shorter.

Motivation for this change
ZHF: #80379
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg test tor

Thanks! Backported as 6121d36f47078ec2400503af1e9888c9ed2bf5df.