improvement: Bump using directives to 1.0.0

This includes the changes to simplify using directives:

remove the possibility of nesting from API
allow to omit commas in lists of values
don't allow multiline comments
remove multiline strings
remove require and @require syntax support
allow values without quotes
remove @using
remove multiline directives

Fixes https://github.com/VirtusLab/scala-cli/issues/2049
Fixes https://github.com/VirtusLab/scala-cli/issues/1954

I updated some of the tests to use the new syntax, not sure if there is a new to do it for everything, but I would write new tests with the new syntax.


Cant find similiar to Observable.FromCoroutine

UniRx => Observable.FromCoroutine....
What should I use instead of this method in R3?

Since Coroutine is async/await in nature, it is appropriate to handle it with UniTask.

while (!operation.isDone && !cancellationToken.IsCancellationRequested) {
                    if (progress != default(IProgress<float>)) {
                        try {
                            progress.Report(operation.progress);
                        } catch (Exception e) {
                            throw;
                        }
                    }
                    await UniTask.Yield();
                }


Kubernetes authenticated by token

I'm getting this warning when i run mvn fabric8:xxxxx (any goal)
[WARNING] F8: Cannot access cluster for detecting mode: Failure executing: GET at: https://kubernetes.service.infra.development.kubernetes.intranet/. Message: Forbidden! User development doesn't have permission. User "xxxxxxx" cannot get path "/"..
It's a develpment environment authenticated by token.
In a sandbox environment (wich I have a root equivalent permission) this don't happen.
I think it is trying to do a GET in the server root context instead my namespace. Not sure.

f-m-p version : 3.5.25

Maven version (mvn -v) : 3.3.3

Kubernetes / OpenShift setup and version : Kubernetes 1.7.3

this is a problem in the kubernetes-client https://github.com/fabric8io/kubernetes-client/issues/850

I think we need to fix fabric8io/kubernetes-client#850 first, then we can jump onto this


ponyfill you say...

ES2015 Object.assign() ponyfill  ;)

What are you asking?

project description is misspelled i funny way ponyfill

It's not ➡ https://ponyfill.com

my bad :-)


Minor language fix

A slight improvement to the language, because:

"anymore" is not word
the second usage is also ambiguous - does it mean "we don't use it fromhereonin" or "we no longer use it"?

Thanks!


GCC error - missing cast in MVE arm_biquad_cascade_df1_q15

We've had a report that GCC doesn't like the MVE version of arm_biquad_cascade_df1_q15. And its complaint seems valid:
https://github.com/ARM-software/CMSIS-DSP/blob/302897a523f5abae63fae9bdb3bbfc1e3089a55a/Source/FilteringFunctions/arm_biquad_cascade_df1_q15.c#L105-L108

arm_biquad_cascade_df1_q15.c:106:13: error: incompatible types when assigning to type 'q15x8_t' {aka 'int16x8_t'} from type 'int32x4_t'

I'd say you need an explicit (q15x8_t) cast on the output of vsetq_lane_s32.
What's not clear to me is why armclang accepts it, which it does. Indeed, armclang doesn't seem to require the existing (q31x4_t) casts either, at least within that C file.
Pasting the same function into some other C++ code I had handy made armclang produce the equivalent error, unless you have 3 casts. Is it performing implicit conversion in C mode, maybe? Intentionally? Possible armclang bug?

While looking around build systems, I've just noticed that GCC's behaviour here is configurable via -flax-vector-conversions.

It is advised to use -flax-vector-conversions because there are some cases where the use of the intrinsic is valid but gcc is nevertheless generating a warning.
But, I'll look at above case because I think it needs the cast.

Any thoughts on the C vs C++ difference in armclang (if that's what it is)? I don't see such a thing documented. Can you control it?

I don't know the differences between C and C++ for handling the intrinsics.
So you confirm that for the arm_biquad_cascade_df1_q15,  you get cast warnings in C++ with armclang but none from C ?
Can you share the compilation options you used ? I'll try to reproduce and then check with our compiler team.

Yes, I've stripped it down, and confirm that it's a C/C++ difference
Given this source:
#include "arm_mve.h"

int16x8_t test(int32x4_t a)
{
    return a;
}

That's accepted if it's input as C:
armclang --target=arm-arm-none-eabi -mcpu=cortex-m55 -O2 -S vectest.c

But rejected with the type error if it comes in as vectest.cpp. Compiler version 6.18.

Compiler team tells me that the C and C++ standards are not managing implicit casts in the same way. But otherwise, for this specific example they can't say more.

Arm C Language Extensions document just says that such implicit conversions are not portable (for C or C++) - and to use vreinterpretq. (It doesn't actually say explicit conversions via casts are portable.)
So the C compiler is free to give the error, and I think it would be far more helpful if it did. Was trying to check whether this has changed since armcc, but don't have a copy to hand.

Minor update, as I found some discussion elsewhere - clang and armclang do also have the -flax-vector-conversions flag, slightly extended to support three options: =none, =int, =all.
Documentation for clang says the default is -flax-vector-conversions=int = -flax-vector-conversions, but as we saw above, the default is actually none for C++.
You can get armclang to reject the above code in C by adding -flax-vector-conversions=none or -fno-lax-vector-conversions. I'll be adding that to my own projects. (I've made too many mistakes from its absence!)
Which in turn means that the change in #65 technically needs to also be applied for armclang.  If someone has made vectors strict in the global CMake compile flags (or a future clang has tightened up), it needs to be overridden for the CMSIS-DSP target.

@kjbracey Thanks for the feedback !

@kjbracey I have added a cmake option to enable / disable lax vector conversions when building for Helium with gcc or ArmClang.
By default it is ON since currently some parts of the library won't build without it.

@kjbracey You're right. It build without problems with integer. I have just pushed the change.


Implement Meshes

Implement the base mesh class

Hey @cesarecaoduro! Could you give me some insight on what Mesh type you were thinking of implementing for g-shark?
I would be happy to port my Mesh class from https://github.comparamdigma/core into G-Shark. It's a half-edge mesh implementation, but if you have any preference for any other mesh implementation I'd also be happy to look into it.
https://github.com/Paramdigma/Core/blob/master/src/Geometry/Mesh.cs
I'm looking into some fun tasks to accomplish through-out this Christmas and this sounds like a nice one! Anyway, happy to have a chat about this before getting started with anything.

Half-edge would be awesome! Yes pls!

Perfect, I'll get the ball rolling by the end of the week. I may open a Draft PR first to start a discussion on implementation details, etc... once I have a working ported Mesh :D

Fantastic, Alan! Amazing to have you contributing! 💪

Just catching up in the morning :)
Amazing to have you contributing to Gshark.
We’ve been in silent mode for quite some time due to different work commitments, but we’re planning to come back now.
Mesh implementation was absolutely in the roadmap, as CSG and some form of BREP.

Just catching up in the morning :)
Amazing to have you contributing to Gshark.
We’ve been in silent mode for quite some time due to different work commitments, but we’re planning to come back now.
Mesh implementation was absolutely in the roadmap, as CSG and some form of BREP.

IMHO we're not going to need CSG if we implement Brep, especially in terms of operations. The latter is more flexible and has wider applications. Is there a specific use case for CSG you had in mind?

CSG is less computation intensive for simple operations (and sometimes all you need is a simple boolean), but I agree, if we manage to get BREP going, we can avoid developing CSG.
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Guido Maciocci @.>
Sent: Tuesday, December 20, 2022 7:12:49 AM
To: GSharker/G-Shark @.>
Cc: Cesare Caoduro @.>; Mention @.>
Subject: Re: [GSharker/G-Shark] Implement Meshes (#225)
Just catching up in the morning :)
Amazing to have you contributing to Gshark.
We’ve been in silent mode for quite some time due to different work commitments, but we’re planning to come back now.
Mesh implementation was absolutely in the roadmap, as CSG and some form of BREP.
IMHO we're not going to need CSG if we implement Brep, especially in terms of operations. The latter is more flexible and has wider applications. Is there a specific use case for CSG you had in mind?
—
Reply to this email directly, view it on GitHubhttps://github.com/GSharker/G-Shark/issues/225#issuecomment-1358239567, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJG6AYWWRYJR4BYTS5OEBLWOC6UDANCNFSM5BLP7EEA.
You are receiving this because you were mentioned.Message ID: @.***>

Not to hijack completely this conversation into a CSG vs Brep discussion... but if I were to choose I would choose both.
There is no good CSG library for C# that you can rely on to make mesh booleans for you afaik. It's 2 different use-cases for 2 different type of users I guess.
The way I see it, CSG is just a "set of procedural steps that result in a specific shape" and as such, could be applied to BREP generation too (or any type of geometry really), and it's a concept that is closer to Grasshopper than Rhino modelling. It also serialises into nothing (as opposed to serialising a Brep)
If you've ever manually created BREP's with rhinocommon you'll know of the pain in the ass that it is, and how easy it is to wreck the entire BREP data structure 😅 A CSG way of building those BREPs to me would be a dream, but it would still require having a working Brep class and working Brep intersection methods.
PS: Maybe a new issue should be opened for this 😅

New issue here: https://github.com/GSharker/G-Shark/issues/386#issue-1504814779
So yeah... We probably want both 😁


ZHA log helper

Description:
When doing debug logging in ZHA component, every log line specifies some sort of an identifier for the logged event. Use a helper log function to universally print ID information for each logged message
Checklist:

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

If the code communicates with devices, web services, or third-party tools:

[x] The manifest file has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

You could just use a new logger instance as member of the entity.

Can you you provide an example implementation? Do you mean I could use a logging adapter?

self.logger = logging.getLogger('{}.{}'.format(__name__, channelid))
Just a thought. Not sure it would be cleaner.

This is good to merge once the lint failures are fixed and the build passes.

self.logger = logging.getLogger('{}.{}'.format(name, channelid))

I see what you mean. The downside we'll be creating a logger instance for each ZHA entity and multiple ZHA channels. May I play "I'm concerned about memory usage" card? :) Not a problem for me running on intel NUC, but  RPi users have much less memory.
From what I was reading a logging adapter would be a way to go, but then it would be something like self.adapter.debug(...) and it extra few characters used of 79 line limit. Essentially I used the same approach for logging as the underlying zigpy library


packet: remove node_private_cidr variable

This variable was causing some confusion, also the fact that it was dependent on the region was a little bit annoying IMHO.
While studying the packet terraform provider I realized it was possible to get that value from it, so why not?

I'll review thoroughly tomorrow, but this will actually fail on the new project. User needs to create any server for cidr to be allocated and only then it will work. I used this in buoyant project where we figured that out.

Can we test if Packet actually allows traffic between two projects when the internal 10.x.x.x IPs are used? If this is not allowed anyway, then we can remove the iptables rule which blocks non-project traffic and just use <IP_ADDRESS>/8 for Calico to find the network interface.

Can we test if Packet actually allows traffic between two projects when the internal 10.x.x.x IPs are used? If this is not allowed anyway, then we can remove the iptables rule which blocks non-project traffic and just use <IP_ADDRESS>/8 for Calico to find the network interface.

For the record: I tested and two servers in different projects are not able to communicate using their private addresses.
Using a fixed <IP_ADDRESS>/8 has two main problems:

It'll bring some security concerns as the range is a lot bigger than the /25 allocated by packet.
If packet decides to use a different range the whole thing would break.

I'll review thoroughly tomorrow, but this will actually fail on the new project. User needs to create any server for cidr to be allocated and only then it will work. I used this in buoyant project where we figured that out.

That's correct, if there have been created servers on a facility this will fail because the private IP range hasn't been assigned yet.  We can document that this is a prerequisite to have those ranges allocated before trying to deploy a server pool in that facility.
The main difference with the current solution is that once the ranges are allocated, the user doesn't have to care updating them (for instance if changing the facility), in case of error this is clear and happens right after trying to deploy, not 10 minutes later as it happens currently if the range has a wrong value.
I agree this is not the ideal solution, but for the time being this improves things a little bit. The ideal solution would be to remove the prerequisite of having those preallocated, maybe by allocating them before creating the instances (not possible by terraform packet provider now) or by using another solution that doesn't require this value when creating the servers (a k8s controller for instance).

I tried the PR on an empty project with no machine created yet, hence no IP address blocks or any CIDRs associated with the project yet.

And this is the error I got:
$ terraform apply
data.packet_precreated_ip_block.project_ip_block: Refreshing state...
data.template_file.etcds: Refreshing state...

Error: Error refreshing state: 1 error occurred:
        * module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: 1 error occurred:
        * module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []

I got following debug output of above command in debug mode and extracted the snippet where the call to the packet api is being made:
...
2019/07/30 18:28:01 [DEBUG] Starting graph walk: walkRefresh
2019/07/30 18:28:01 [DEBUG] Setting Unknown Variable Value for computed key: worker_nodes_hostnames
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalCoerceMapVariable
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalTypeCheckVariable
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.etcds" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin": module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.worker_host_endpoints": module.packet-lithium.data.template_file.worker_host_endpoints
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.worker_host_endpoints" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.packet_precreated_ip_block.project_ip_block": module.packet-lithium.data.packet_precreated_ip_block.project_ip_block
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.packet_precreated_ip_block.project_ip_block" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet": module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet
2019/07/30 18:28:01 [TRACE] root.packet-lithium: eval: *terraform.EvalSequence
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.controller_host_endpoints": module.packet-lithium.data.template_file.controller_host_endpoints
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet" references: []
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller_host_endpoints" references: []
data.packet_precreated_ip_block.project_ip_block: Refreshing state...
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:01 [DEBUG] Packet API Request Details:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: ---[ REQUEST ]---------------------------------------
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: GET /projects/f97d9a73-31b8-43e2-8f7c-31e6676d0032/ips HTTP/1.1
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Host: api.packet.net
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: User-Agent: packngo/0.1.0
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Connection: close
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept: application/json
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Type: application/json
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Auth-Token: [REDACTED]
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Consumer-Token: [REDACTED]
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Encoding: gzip
data.template_file.etcds: Refreshing state...
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: -----------------------------------------------------
2019/07/30 18:28:01 [DEBUG] Setting Unknown Variable Value for computed key: kubeconfig
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalCoerceMapVariable
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.template_file.configs": module.worker-pool-helium.data.template_file.configs
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.controller-configs": module.packet-lithium.data.template_file.controller-configs
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller-configs" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.ct_config.ignitions": module.worker-pool-helium.data.ct_config.ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.ct_config.ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.ct_config.controller-ignitions": module.packet-lithium.data.ct_config.controller-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.ct_config.controller-ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.template_file.install": module.worker-pool-helium.data.template_file.install
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.template_file.install" references: []
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller-install" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.ct_config.install-ignitions": module.worker-pool-helium.data.ct_config.install-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.ct_config.install-ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.ct_config.controller-install-ignitions": module.packet-lithium.data.ct_config.controller-install-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.ct_config.controller-install-ignitions" references: []

Error: Error refreshing state: 1 error occurred:
	* module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: 1 error occurred:
	* module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []

2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:02 [DEBUG] Packet API Response Details:
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: ---[ RESPONSE ]--------------------------------------
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: HTTP/2.0 200 OK
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Length: 19
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Ranges: bytes
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Ranges: bytes
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Age: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Age: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Cache-Control: max-age=0, private, must-revalidate
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Type: application/json; charset=utf-8
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Date: Tue, 30 Jul 2019 16:28:02 GMT
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Etag: W/"d2c01dd196ed1c5417be0e0cbdd6ac72"
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Status: 200 OK
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Vary: Origin
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Via: 1.1 varnish
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Cache: MISS
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Cache-Hits: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Content-Type-Options: nosniff
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Frame-Options: SAMEORIGIN
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Instana-S: 64a133f3c9c71013
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Instana-T: 64a133f3c9c71013
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Request-Id: b2c1e263-ff7d-4c2a-9f92-de62aa4ffa1b
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Served-By: cache-fra19165-FRA
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Timer: S1564504082.134779,VS0,VE238
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Xss-Protection: 1; mode=block
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: {
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:  "ip_addresses": []
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: }
2019/07/30 18:28:02 [ERROR] root.packet-lithium: eval: *terraform.EvalReadDataApply, err: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []
2019/07/30 18:28:02 [ERROR] root.packet-lithium: eval: *terraform.EvalSequence, err: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []
2019/07/30 18:28:02 [TRACE] [walkRefresh] Exiting eval tree: module.packet-lithium.data.packet_precreated_ip_block.project_ip_block
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: -----------------------------------------------------
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "provider.packet.default (close)"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "module.packet-lithium.data.template_file.host_protection_policy"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "provider.template.default (close)"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "root"
2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.377+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: stream copy 'stderr' error: stream closed
2019-07-30T18:28:02.377+0200 [DEBUG] plugin.terraform-provider-local_v1.3.0_x4: 2019/07/30 18:28:02 [ERR] plugin: stream copy 'stderr' error: stream closed
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform: remote-exec-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin960654796: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform: remote-exec-provisioner (internal) 2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin892138199: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-ct_v0.4.0: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin142966687: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-aws_v1.60.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin556754829: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin478386774: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform-provider-tls_v1.2.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin537576982: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform-provider-local_v1.3.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin079634543: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-template_v1.0.0_x4
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-null_v1.0.0_x4
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.terraform.d/plugins/terraform-provider-ct_v0.4.0
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-tls_v1.2.0_x4
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.local/bin/terraform
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-packet_v1.7.2_x4
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.local/bin/terraform
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-local_v1.3.0_x4
2019-07-30T18:28:02.405+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-aws_v1.60.0_x4

I tried the PR on an empty project with no machine created yet, hence no IP address blocks or any CIDRs associated with the project yet.
And this is the error I got:
$ terraform apply
data.packet_precreated_ip_block.project_ip_block: Refreshing state...
data.template_file.etcds: Refreshing state...

Error: Error refreshing state: 1 error occurred:
        * module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: 1 error occurred:
        * module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []

I got following debug output of above command in debug mode and extracted the snippet where the call to the packet api is being made:
...
2019/07/30 18:28:01 [DEBUG] Starting graph walk: walkRefresh
2019/07/30 18:28:01 [DEBUG] Setting Unknown Variable Value for computed key: worker_nodes_hostnames
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalCoerceMapVariable
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalTypeCheckVariable
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.etcds" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin": module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-admin" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.worker_host_endpoints": module.packet-lithium.data.template_file.worker_host_endpoints
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.worker_host_endpoints" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.packet_precreated_ip_block.project_ip_block": module.packet-lithium.data.packet_precreated_ip_block.project_ip_block
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.packet_precreated_ip_block.project_ip_block" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet": module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet
2019/07/30 18:28:01 [TRACE] root.packet-lithium: eval: *terraform.EvalSequence
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.controller_host_endpoints": module.packet-lithium.data.template_file.controller_host_endpoints
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.module.bootkube.data.template_file.kubeconfig-kubelet" references: []
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller_host_endpoints" references: []
data.packet_precreated_ip_block.project_ip_block: Refreshing state...
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:01 [DEBUG] Packet API Request Details:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: ---[ REQUEST ]---------------------------------------
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: GET /projects/c71122c6-339f-4def-ae08-e97760100bce/ips HTTP/1.1
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Host: api.packet.net
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: User-Agent: packngo/0.1.0
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Connection: close
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept: application/json
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Type: application/json
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Auth-Token: [REDACTED]
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Consumer-Token: [REDACTED]
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Encoding: gzip
data.template_file.etcds: Refreshing state...
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:01.873+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: -----------------------------------------------------
2019/07/30 18:28:01 [DEBUG] Setting Unknown Variable Value for computed key: kubeconfig
2019/07/30 18:28:01 [TRACE] root: eval: *terraform.EvalCoerceMapVariable
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.template_file.configs": module.worker-pool-helium.data.template_file.configs
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.template_file.controller-configs": module.packet-lithium.data.template_file.controller-configs
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller-configs" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.ct_config.ignitions": module.worker-pool-helium.data.ct_config.ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.ct_config.ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.ct_config.controller-ignitions": module.packet-lithium.data.ct_config.controller-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.ct_config.controller-ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.template_file.install": module.worker-pool-helium.data.template_file.install
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.template_file.install" references: []
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.template_file.controller-install" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.worker-pool-helium.data.ct_config.install-ignitions": module.worker-pool-helium.data.ct_config.install-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.worker-pool-helium.data.ct_config.install-ignitions" references: []
2019/07/30 18:28:01 [DEBUG] Resource state not found for "module.packet-lithium.data.ct_config.controller-install-ignitions": module.packet-lithium.data.ct_config.controller-install-ignitions
2019/07/30 18:28:01 [DEBUG] ReferenceTransformer: "module.packet-lithium.data.ct_config.controller-install-ignitions" references: []

Error: Error refreshing state: 1 error occurred:
	* module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: 1 error occurred:
	* module.packet-lithium.data.packet_precreated_ip_block.project_ip_block: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []

2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:02 [DEBUG] Packet API Response Details:
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: ---[ RESPONSE ]--------------------------------------
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: HTTP/2.0 200 OK
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Length: 19
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Ranges: bytes
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Accept-Ranges: bytes
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Age: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Age: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Cache-Control: max-age=0, private, must-revalidate
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Content-Type: application/json; charset=utf-8
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Date: Tue, 30 Jul 2019 16:28:02 GMT
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Etag: W/"p1p11pp111pp1p1111p"
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Status: 200 OK
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Vary: Origin
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: Via: 1.1 varnish
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Cache: MISS
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Cache-Hits: 0
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Content-Type-Options: nosniff
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Frame-Options: SAMEORIGIN
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Instana-S: 33a333a3a3a33333
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Instana-T: 33a333a3a3a33333
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Request-Id: 60d8d54e-befb-478a-89db-b859de9f77ee
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Served-By: cache-fra19165-FRA
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Timer: S1564504082.134779,VS0,VE238
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: X-Xss-Protection: 1; mode=block
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: {
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4:  "ip_addresses": []
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: }
2019/07/30 18:28:02 [ERROR] root.packet-lithium: eval: *terraform.EvalReadDataApply, err: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []
2019/07/30 18:28:02 [ERROR] root.packet-lithium: eval: *terraform.EvalSequence, err: data.packet_precreated_ip_block.project_ip_block: Could not find matching reserved block, all IPs were []
2019/07/30 18:28:02 [TRACE] [walkRefresh] Exiting eval tree: module.packet-lithium.data.packet_precreated_ip_block.project_ip_block
2019-07-30T18:28:02.375+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: -----------------------------------------------------
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "provider.packet.default (close)"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "module.packet-lithium.data.template_file.host_protection_policy"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "provider.template.default (close)"
2019/07/30 18:28:02 [TRACE] dag/walk: upstream errored, not walking "root"
2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.377+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: stream copy 'stderr' error: stream closed
2019-07-30T18:28:02.377+0200 [DEBUG] plugin.terraform-provider-local_v1.3.0_x4: 2019/07/30 18:28:02 [ERR] plugin: stream copy 'stderr' error: stream closed
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform: remote-exec-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin960654796: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform: remote-exec-provisioner (internal) 2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-packet_v1.7.2_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin892138199: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-ct_v0.4.0: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin142966687: use of closed network connection
2019-07-30T18:28:02.402+0200 [DEBUG] plugin.terraform-provider-aws_v1.60.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin556754829: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin478386774: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform: file-provisioner (internal) 2019/07/30 18:28:02 [DEBUG] plugin: waiting for all plugin processes to complete...
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform-provider-tls_v1.2.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin537576982: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin.terraform-provider-local_v1.3.0_x4: 2019/07/30 18:28:02 [ERR] plugin: plugin server: accept unix /tmp/plugin079634543: use of closed network connection
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-template_v1.0.0_x4
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-null_v1.0.0_x4
2019-07-30T18:28:02.403+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.terraform.d/plugins/terraform-provider-ct_v0.4.0
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-tls_v1.2.0_x4
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.local/bin/terraform
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-packet_v1.7.2_x4
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/.local/bin/terraform
2019-07-30T18:28:02.404+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-local_v1.3.0_x4
2019-07-30T18:28:02.405+0200 [DEBUG] plugin: plugin process exited: path=/home/suraj/study/prreview/lokomotive-kubernetes-pr-43/.terraform/plugins/linux_amd64/terraform-provider-aws_v1.60.0_x4


Confusion regarding bug position

In the paper, it is mentioned that the faulty locations are calculated based on the ground truth of developer patches. However, for the bug Closure 114, the modified line no is 578 (as shown in https://github.com/program-repair/defects4j-dissection/commit/714c5bd), whereas it is 585 according to the BugPositions.txt file.
Similar cases occur for bug Closure 107, Lang_21, etc.
Besides, the BugPositions.txt file. of AVATAR  differs from that of FL-VS-APR. For example, Closure_15, Chart_25 etc.
Can you please help me in this regard? Thanks in advance.

Hello @mou23,
For Closure-114, its patch
"} else if (!(parent.isCall() && parent.getFirstChild() == n)) {
recordDepScope(recordNode, ns);
}" is equal to
"} else {
if (!(parent.isCall() && parent.getFirstChild() == n)) {
recordDepScope(recordNode, ns);
}
}".
It is adding an if-check-statement for the line-578, so we consider the line-578 as buggy line.
For Closure-107, it is hard to decide the exact buggy line.
By considering the comments before line-861, only one code line in the block and "new EmptyMessageBundle();" assigned in the code line, we consider the line-861 as buggy line.
For Lang-21, lines 262-269 are for one statement, we are not sure that the line 265 can be identified as the buggy line since it is just one expression of the buggy statement. Therefore, we consider all lines of the buggy statement as buggy lines.
We had further discussion about the buggy positions, the data for FL-VS-APR is updated accordingly, we forgot to update the data in AVATAR.

Thank you so much @BruceKuiLiu for your valuable response. Now, these cases are clear to me. By the way, you mentioned that for Closure-114, line-578 should be considered as the buggy line. However, according to your file, the buggy location is 585. It would be helpful if you update it. Once again thank you so much.

Sorry for the typo "Line-578", it should be Line-585.

Won't it be more appropriate if you add both 578 and 585 as faulty lines as you did in Math-10?

Yeah, maybe.

Okay. Thank you so much for your help :smiley:


Why objects in manipulation scene don't match v-rep pose

When adding meshes to the manipulation scene via MoveIt! we need to subtract a offset (example) to add meshes in the proper position. It is not clear why this happen.

One first clue might be that when meshes are exported from v-rep their coordinates aren't {0,0,0,0,0,0} and instead the coordinates are the same as the ones in v-rep.

Was the reason above.


Fix turtle export

So far, the Turtle export (for CONSTRUCT queries) writes literals in QLever's internal representation, where, in particular, quotes are not escaped. This is fixed now.

I tried this on olympics (export the complete dataset using CONSTRUCT) and on Wikidata (export all objects of @en@rdfs:label using CONSTRUCT) and in both cases, the resulting Turtle is of a form that the QLever index builder accepts.
Note that it's still not perfectly valid Turtle because some of the strings contain UTF-8 sequences, which are not allowed in literals according to the standard, but which are fine with QLever's index builder

@RobinTF Thanks a lot for your review, Robin! Johannes and I have discussed it. Johannes can tell you more :-)


Code not touched for 5 months

I guess this code base is dead ?
Sorry to be so blunt
The idea behind Seurat is great but dead code is a bad sign. Did another approach take off ?

It works just fine (for my purposes at least). Code isn't an organic thing - it doesn't need to be touched just to stay relevant or "alive".


feat(tips): load files from config

closes #253
This could probably be split up into more arguments later on, for example

^tips opensource
^tips github

Thanks @AllanRegush @BOLT04 👍


[ISSUE #4109] add permission validation on broker side for ordinary topic

to solve the problem described in ISSUE #4109
This change will cause the broker to throw a "NO_PERMISSION" exception. If the producer uses SYNC mode, it will retry sending to another broker, seeing DefaultMQProducerImpl#sendDefaultImpl,  so the SYNC mode will not be affected.

Coverage decreased (-0.2%) to 51.728% when pulling 9e9c160996eef8b87c5fc709d4c9504d792fdaf3 on MatrixHB:fix_broker_permission into e7c87fa1cee96b48993fae0eb2de3974106e9e92 on apache:develop.

Adding the perm check for ordinary topic, the client will get exceptions and cannot failover during the matadata discovery time, which is up to 30 seconds.
For ordinary topics, the original design expects the client to discover the new topic route and send only to the writable brokers, which introduces no exceptions and makes the wipe-perm process more smoothly.

Adding the perm check for ordinary topic, the client will get exceptions and cannot failover during the matadata discovery time, which is up to 30 seconds.
For ordinary topics, the original design expects the client to discover the new topic route and send only to the writable brokers, which introduces no exceptions and makes the wipe-perm process more smoothly.

Thanks, this change is not so elegant actually. Maybe updating the client version is enough to solve this problem. Next time we meet this trouble we can discuss this again.


Keep Weekly tag corresponding to commit hash for avoiding loss of image sha

Currently, our workflows builds weekly tag based on cron schedule and pushes a image-mirror of image built on openshift-ci.
This pattern causes the image sha of the previous weekly tag to be orphan as the weekly tag move to the new image sha with the timeline. Causing users to use image sha of weekly tag face pull error with respect to weekly tag image.
Acceptance critera

[ ] Change the workflow to use skopeo copy to create the weekly tag from latest commit hash

This shall be fixed now.
Instead of using the weekly tag, we have removed it from the imagestream and now utilize the SHAs instead.
Moreover, the update process is performed through the digest updater workflow, which uses the latest git commit.
The leftovers from the weeklies into the CI can be removed through this PR

Related PR for implementation has been merged


Make work with proxy

Original Issue: https://github.com/RocketChat/Rocket.Chat/issues/4357

+1 also interested in a solution.
Thanks

+1

+1

+1

This is not possible yet?

Neither having touched any Electron code not being really a JavaScript developer I can guess only: It seems to be feasible from reading this post: https://evandontje.com/2020/04/02/automatic-system-proxy-configuration-for-electron-applications/


test failure while building macrobase

Hi - I am trying to run GUI version of macrobase and while building the application I am getting following test error.
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.347 s <<< FAILURE! - in macrobase.runtime.MacroBaseApplicationTest
[ERROR] simpleTest(macrobase.runtime.MacroBaseApplicationTest)  Time elapsed: 0.346 s  <<< ERROR!
java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
at macrobase.runtime.MacroBaseApplicationTest.simpleTest(MacroBaseApplicationTest.java:18)
Even if I go ahead by suppressing the test runs...application gets built but while running the frontend.sh I get the same issue. am attaching the full trace of the build
out.txt

Issue got fixed....Issue was java version.

@rameshtocode Hi, I have the same issue, what version did you use when u encountered the test failures? (I am using JDK14.0.2)


Adds AOs and VectorSpace

Is this pull request associated with an issue(s)?
No.
Description
This PR starts the wavefunction rewrite by introducing the VectorSpace and AOs classes. It also exposes them to Python.
TODOs
None. R2g if it passes CI.

🚀 [bumpr] Bumped! New version:v1.2.11 Changes:v1.2.10...v1.2.11


Update BSK for Duck Player fix

Task/Issue URL: https://app.asana.com/0/1201048563534612/1204993915251837/f
Tech Design URL:
CC: @shakyShane
Description:
This PR updates the iOS BSK version for the incoming Duck Player fix. Note that Duck Player is not supported on iOS, so this change should not have any noticeable effect.
BSK PR: https://github.com/duckduckgo/BrowserServicesKit/pull/410

Steps to test this PR:

Smoke test web features
Check that YouTube works as expected (videos/shorts play as expected)

Device Testing:

[ ] iPhone SE (1st Gen)
[ ] iPhone 8
[ ] iPhone X
[ ] iPhone 14 Pro
[ ] iPad

OS Testing:

[ ] iOS 14
[ ] iOS 15
[ ] iOS 16

Internal references:
Software Engineering Expectations
Technical Design Template

The iOS repo is already using a newer version of BSK that includes this fix, so I'm closing this one.


When you use an invalid password on Setup, Site is created without user

User is created thought this event handled by an Orchard.Users handler:
await eventBus.NotifyAsync<ISetupEventHandler>(x => x.Setup(
                        context.SiteName,
                        context.AdminUsername,
                        context.AdminEmail,
                        context.AdminPassword,
                        context.DatabaseProvider,
                        context.DatabaseConnectionString,
                        context.DatabaseTablePrefix)
                    );

Problem is if it fails it is not notified to the user and the creation of the site is completed but without any admin user, so you cannot access the new site.
I'm open to fix it, which should be the approach?

maybe we should use a cancellation token?

CancellationTokens are created with a CancellationTokenSource and as far as I know is the CancellationTokenSource what is used to cancel an operation. So, it looks the idea behind CancellationTokens is a consumer of an action can cancel an operation without matter how many different actions are running for complete that operationt.
I dont see how could it help here.

In the case we are aware that password validation failed what should be the action to take? To remove the tenant and report the error to the user?
In this particular case looks easier to validate password before the tenant is created to don't have to remove it if it is invalid.

maybe we need a ISetupValidationEventHandler ?

For the sake of maintaining modules decoupled ... ok

Using ISetupValidationEventHandler is to have the validation logic of the user int Orchard.Users module. However, how at that point no tenant exists handler defined in Orchard.Users is not loaded because the only feature enabled are Orchard.Logging.Console and Orchard.Setup.
I could add Orchard to be enabled by default, problem is Orchard.Users has dependencies like Orchard.Data, so at this point what would be best option in your opinion?


Is std::out_of_range suitable for out of range floating points?

From cppreference.com, std::out_of_range

reports errors that are consequence of attempt to access elements out of defined range.

Pitch and gain, for example, are floating points values, and thus IMHO should not throw this exception.  I'd suggest std::domain_error which is defined as

may be used by the implementation to report domain errors, that is, situations where the inputs are outside of the domain on which an operation is defined.

Disclaimer: the reason I'm filing this issue is that Cython translate std::out_of_range as IndexError while std::domain_error is mapped to ValueError, which is more appropriate in Python context.  I am not aware of the current usage of Alure 2 but I assume that backward compatibility might not be a major problem since you haven't made any official release of the new C++11 API.

Makes sense. Some may actually be better as std::invalid_argument, but for now I've changed the non-view-type std::out_of_range exceptions to std::domain_error, with commit 195e9347f0038bca9c27c2eeb7275efc1a2cdcf6.

I assume that backward compatibility might not be a major problem since you haven't made any official release of the new C++11 API.

Currently, Alure 2 makes no real promise to API/ABI compatibility. It will try to avoid any unnecessary or excessive changes, but given the C++ API and evolving functionality, it's not something that can be guaranteed.

Thank you for the quick response!  I agree that for some cases, the exception might not exactly fall under std::domain_error and the more general std::invalid_argument might be a better choice, but I'm happy with the current state.


Move to SSL

Enable HTTPS with Netlify.

Set up jekyll to work on Netlify. Changed DNS records to point at Hover. Now waiting for them to switch over.

Done.


update packages, cleanup

This updates to use the latest mocha, should, esprima, and estraverse. The primary motivation is to allow use of the latest ES2016+ features in scanned JS code.
All tests are passing.
By the way, thanks so much for this project!

Thanks for the updates.


Most title tags parse with unknown symbols

I needs to parse title and artist from id3 of mp3. When i receive id3 array with your library, most of them has unknown symbols ( ? ). I was forced filter output with preg_replace('/[^a-z-0-9]/i', '', $out) for receiving clear title of the track.

I currently also have this problem after having retagged alot of MP3 files. It seems to be related to if the ID3 tags is written in UTF-8, UTF-16 or ISO-8859-1. (Not sure if the version of ID3 tag is also a thing of this).
I have tried to mb_convert_encoding the output, this removed the fact that the program broke, however I am back to having the unknown symbols in my output.

Thanks


OWA configuration options

I'm trying to understand how to set config options in the container, specifically e-mail server settings for password resets. According to the owa wiki, you modify the owa-config.php file. Where's this file in this container? I'm using docker-compose. Do I need to set a persistent volume to somewhere?
Thanks

Bump. Anyone?

Not sure if you've solved this already, but the configuration file is located at /var/www/html/owa-config.php after you've configured the container.
I added a volume mount for the file to my docker compose so that the configuration isn't reset:
owa:
    image: vladk1m0/docker-owa:latest
    container_name: owa
    depends_on:
      - owa_db
      - nginx
    networks:
      - owa_net
      - network_all
    environment:
      - TIME_ZONE="Canada/Montreal"
    volumes:
      - /mnt/data/owa/owa-config.php:/var/www/html/owa-config.php

Actually I abandoned OWA and went to Matomo and haven't looked back


fix(curriculum): add a closing parenthesis

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Added a closing parenthesis to the text of Arithmetic Formatter of Scientific Computing with Python Projects.
It could also be considered adding a closing parenthesis AFTER period, like bellow:

the operator will be on the same line as the second operand, both operands will be in the same order as provided (the first will be the top one and the second will be the bottom.)

But the sentence in parentheses seems to relate only a sentence "both operands will be in the same order as provided" so I added one BEFORE period simply.
By only running my local clone and seeing the change in browser, I tested this change

.

Thanks!


Bad URL on ExperimentClient.start/fetch

We've noticed that we seem to be getting a fair few errors whenever we call the ExperimentClient.start / ExperimentClient.fetch methods.
We use Sentry for our error reporting, and we have set it up so that we send most errors through to Sentry whenever we get an error from the start call. You can see the exact details/numbers here via our Sentry reporting:

Start - https://trustpilot.sentry.io/share/issue/82f376794f074c72bfa7ca184b23de33/
Fetch - https://trustpilot.sentry.io/share/issue/c0fe8af82ba84cd0a1c4a3d85f830122/

Note that the error name contains the error code/domain

Based on the error code we're getting in the callbacks, it seems like the error is due to a bad URL (see NSURLErrorDomain codes), though based on the breadcrumbs in Sentry, the url seems to be fine.

Hi @nebsta sorry for the delay, and thanks for submitting this issue.
Not sure why this URL would return this error code...

What is the frequency of these errors? Is it very common or very uncommon?
Do you have any way to check where these users are located geographically?
Do you have any way to reproduce locally?

What is the frequency of these errors? Is it very common or very uncommon?
In total we've seen about 860 instances of this happening across 311 users. We're seeing about 20 instances of this exception occurring per day
Do you have any way to check where these users are located geographically?
I did a check and could see that the locale isn't consistent. Just doing a general check I saw users from Australia, Britain and Germany
Do you have any way to reproduce locally?
Unfortunately not

Based on the screenshots provided, the URLs look valid. Is it possible the users just have poor network connectivity, and this error is a red herring? Do you get other errors for connection timouts/DNS resolution errors?

@bgiori we do have some, but those are reported alongside this error.

Sorry for the delay. Unfortunately I am unable to reproduce this error. Is it possible to get more info from the error passed in the completion?
For example, when I turn of my network connectivity and run a test on my mac, I get the following error:
Error Domain=NSURLErrorDomain Code=-1009 "The Internet connection appears to be offline." UserInfo={_kCFStreamErrorCodeKey=50, NSUnderlyingError=0x60000336e9a0 {Error Domain=kCFErrorDomainCFNetwork Code=-1009 "(null)" UserInfo={_kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=50, _NSURLErrorNWResolutionReportKey=Resolved 0 endpoints in 1ms using unknown from cache, _NSURLErrorNWPathKey=unsatisfied (No network route)}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <B64B86B1-5327-484B-875C-713F6620215C>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
    "LocalDataTask <B64B86B1-5327-484B-875C-713F6620215C>.<1>"
), NSLocalizedDescription=The Internet connection appears to be offline., NSErrorFailingURLStringKey=https://api.lab.amplitude.com/sdk/v2/vardata?v=0, NSErrorFailingURLKey=https://api.lab.amplitude.com/sdk/v2/vardata?v=0, _kCFStreamErrorDomainKey=1}

The error returned in your stack trace seems terse: -1000:NSURLErrorDomain: Code: 9301


[BugFix] BE crash on illegal JSON

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes https://github.com/StarRocks/starrocks/issues/12816
Problem Summary(Required) ：

When the input is invalid JSON, like {"key": 1} "key": 2}, the 2nd document would not be parsed successfully. In order to get the context that leads the parsing failure, we use JsonFunctions::to_json_string(doc) to print the content of the doc. But for doc that is not parsed successfully, the  JsonFunctions::to_json_string(doc) would lead the BE crash.
This PR removes the printing of not parsed doc. The BE would record the current parsed location, and print the not-parsed content to the error log. In this way, not only the bug leading the crash would be resolved, but also the user is easier to get to know the error in the json input.
Besides, this PR would not change the behaviour of the SR. It would modify the error message and adds more content to the error log file.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

The output would be like this:
curl "http://<IP_ADDRESS>:18082/api/_load_error_log?file=error_log_b042825f98f8bb3f_7c38c767043b5bb3"
Error: Data quality error: construct row in object order failed, error: The JSON document has an improper structure: missing or superfluous commas, braces, missing keys, etc.. Row: {
{
Error: Data quality error: Failed to iterate document stream as object. error: The JSON element does not have the requested type..


Updated some steps in use-dkim-to-validate-outbound-email.md

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@MSFTTracyP Please merge this PR. Thanks

@MSFTTracyP Gentle reminder.

Closing this PR as that section was already updated as part of the "deep link" fixes.


New x2gd instance type missing

The x2gd instance type released today on 03/16/2021 is missing from the site

@doit-mattporter This is now resolved. Going to go ahead and close.


merger resolving: Added relabelMergers() function to refine segmentation on Ilastik

The relabelMergers() function was added, and is called from within opConservationTracking in Ilastik to request frames with refined merger segmentations.

This definitely reduces the memory footprint, but it means relabelMergers() is run twice per frame.
Unfurtunately, fitting GMMs (our current merger relabeling technique) is not deterministic, and so one might get out a tracking solution that doesn't necessarily fit to the images.

We could add another method to our merger resolving plugin and use the fit that we have already computed and stored (we only use the fits of the previous frames here https://github.com/chaubold/hytra/pull/6/files#diff-060028ca83bd4e2a8b4f1914aed823f5R137).
By doing so, we could simply not call GMM.fit() in https://github.com/chaubold/hytra/blob/development/hytra/plugins/merger_resolver/gmm_merger_resolver.py#L39  but only call GMM.predict() to reassign the pixels.


[ADDENDUM] HBASE-28947 Backport "HBASE-27598 Upgrade mockito to 4.x" …

…to branch-2.5

Remove references to mockito-core.version in pom to fix site build
Backports https://github.com/apache/hbase/commit/55b4bbc05785cc652b4425b9ac45f673b28597b4

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 42s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
2m 57s

branch-2.5 passed

+1 :green_heart:
compile
5m  0s

branch-2.5 passed

+1 :green_heart:
spotless
0m 43s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 45s

the patch passed

+1 :green_heart:
compile
5m  0s

the patch passed

+1 :green_heart:
javac
5m  0s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
xmllint
0m  0s

No new issues.

+1 :green_heart:
hadoopcheck
19m 37s

Patch does not cause any errors with Hadoop 2.10.2 or 3.2.4 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 42s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 14s

The patch does not generate ASF License warnings.

39m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6454

Optional Tests
dupname asflicense javac codespell detsecrets xmllint hadoopcheck spotless compile

uname
Linux 6d5f2326d064 5.4.0-200-generic #220-Ubuntu SMP Fri Sep 27 13:19:16 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / 46493a52a8cd32f8bc9aa5fadb51a6b1d92b1098

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
75 (vs. ulimit of 30000)

modules
C: . U: .

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 45s

the patch passed

+1 :green_heart:
compile
2m  5s

the patch passed

+1 :green_heart:
javac
2m  5s

the patch passed

+1 :green_heart:
javadoc
1m 49s

the patch passed

+1 :green_heart:
shadedjars
4m 57s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
260m 52s

root in the patch passed.

291m 47s

Subsystem
Report/Notes

Docker
ClientAPI=1.47 ServerAPI=1.47 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6454

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 005763a20ce4 5.4.0-195-generic #215-Ubuntu SMP Fri Aug 2 18:28:05 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / 46493a52a8cd32f8bc9aa5fadb51a6b1d92b1098

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/testReport/

Max. process+thread count
8036 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
1m  7s

Docker mode activated.

-0 :warning:
yetus
0m  8s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
4m  6s

branch-2.5 passed

+1 :green_heart:
compile
2m 53s

branch-2.5 passed

+1 :green_heart:
javadoc
2m 58s

branch-2.5 passed

+1 :green_heart:
shadedjars
8m 48s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 33s

the patch passed

+1 :green_heart:
compile
3m  9s

the patch passed

+1 :green_heart:
javac
3m  9s

the patch passed

+1 :green_heart:
javadoc
3m 35s

the patch passed

+1 :green_heart:
shadedjars
8m  6s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
256m 30s

root in the patch passed.

302m 13s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6454

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux e1e3c5b0a0fd 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / 46493a52a8cd32f8bc9aa5fadb51a6b1d92b1098

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/testReport/

Max. process+thread count
7786 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.5 Compile Tests _

+1 :green_heart:
mvninstall
2m 32s

branch-2.5 passed

+1 :green_heart:
compile
1m 36s

branch-2.5 passed

+1 :green_heart:
javadoc
1m 41s

branch-2.5 passed

+1 :green_heart:
shadedjars
6m 21s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
3m  8s

the patch passed

+1 :green_heart:
compile
2m 30s

the patch passed

+1 :green_heart:
javac
2m 30s

the patch passed

+1 :green_heart:
javadoc
2m  3s

the patch passed

+1 :green_heart:
shadedjars
5m 41s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

-1 :x:
unit
402m  8s
/patch-unit-root.txt
root in the patch failed.

433m 41s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6454

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 56cc6f0e219d 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.5 / 46493a52a8cd32f8bc9aa5fadb51a6b1d92b1098

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/testReport/

Max. process+thread count
4703 (vs. ulimit of 30000)

modules
C: . U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6454/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

Merging this as its a straight backport.


Exception when path contains unicode character

Hi Tim,
Thanks for your work, it's an awesome tool!
When the path contains a unicode character ("François") in my case, the script refuses to write the file:
[fti@Gramont Desktop]$ cd François\ CP/
[fti@Gramont François CP]$ ./mcx2profile.py --plist com.apple.security.firewall.plist --identifier com.apple.security.firewallTraceback (most recent call last):
  File "./mcx2profile.py", line 539, in <module>
    main()
  File "./mcx2profile.py", line 534, in main
    newPayload.finalizeAndSave(output_file)
  File "./mcx2profile.py", line 138, in finalizeAndSave
    writePlist(self.data, output_path)
  File "./mcx2profile.py", line 256, in writePlist
    "Failed to write plist data to %s" % filepath)
__main__.NSPropertyListWriteException: Failed to write plist data to /Users/fti/Desktop/François CP/com.apple.security.firewall.mobileconfig
[fti@Gramont François CP]$

ali


Error: checkServerTrusted is empty

My lint keeps throwing an error when I use your library:
/Users/saenic/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcpkix-jdk15to18/1.75/f16e5252ad7a46d5eaf255231b0a5da307599082/bcpkix-jdk15to18-1.75.jar: Error: checkServerTrusted is empty, which could cause insecure network traffic due to trusting arbitrary TLS/SSL certificates presented by peers [TrustAllX509TrustManager]
I looked through your code and couldn't find any trust manager implementations, so no clue why this occurs. Maybe you can find the source of the problem.

@saenic did you use Bouncy Castel in your app?

No I don't, but you are. I found out, that the "com.tom-roush:pdfbox-android" library you embedded is using Bouncy Castle.
Since you only need this PDF Box for accessibility you might reconsider using it.

@GRizzi91 any updates on this? I'm getting the following error because of bouncycastle I assume
SHA-256 digest error for org/bouncycastle/cert/AttributeCertificateHolder.class

Looks like for now excluding bouncycastle works as a workaround
implementation("io.github.grizzi91:bouquet:1.1.2") {
        exclude("org.bouncycastle")
    }


Intellisense with non static imports/require

Disclaimer

I am not sure if this is the right repo to place this issue, so please guide me if not.
I searched stackoverflow and existing issues and found nothing for it.

I was trying to find a way to make dynamic imports or non-static imports to provide intellisense. For example
I have a file called user.js with following contents
module.exports = function () {
  return {
    username: 'virk'
  }
}

And another file called index.js with following contents
var userModule = './user'

const user = require(userModule)()
console.log(user)

When typing user. I get no intellisense, since the engine behind autocomplete may not have access to the userModule value and hence it fails.
Hey that's not the right way?
Maybe you are right, but going there can be so many use cases where the require statements receives a dynamic value, which is part currently running application.
Also going forward, ES6 will have a Loader API, where you can register modules or even can define a custom loader for a given application and I do think that intellisense will fail in that case too.
No offense
The above points may have nothing to do with intellisense at all, since the design behind the entire system works on static analysis.
But the reason I created the issue, since I know that a TSServer runs inside a separate process to provide Typescript intellisense, which means there can be other ways too to use a loader which is part of a certain application.
Thanks 😄

This issue was moved to Microsoft/TypeScript#18656

Thanks for the report! I've moved this issue over to TypeScript, which powers both the JavaScript and TypeScript language support in VSCode


Less icons theme doesn't hide the icon during zen mode

I am not sure it should

That's OK, the icon is actually a link.


need to allow A-F in github token check

Hm looks like we also need to allow _ and e-z now https://github.blog/2021-04-05-behind-githubs-new-authentication-token-formats/

yep.

@tballmsft  @jwun Does this need to ported to other target like microbit?

It's an easy port and we still need to release the live=1 fix for micro:bit anyway so might as well (along with https://github.com/microsoft/pxt/pull/8055 which fixes the rest of the problem).
This only hits dev tokens right now though, and not oauth which I would expect to be much more commonly used, so it's not that urgent (and can work around by logging in in beta and then switching to live)

Can you please port it to stable channel in microbit? I am doing a point fix release this week.


Fix import for foscam

While waiting for a new pyfoscam release, we can fix this for users
just by changing the import. Foscam devices a pretty widely deployed,
so a regression here is definitely no fun.
Fixes Bug #8940
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

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

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

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I thought that this wouldn't work because the init file would get parsed before the submodule?

0.52.1/docker:
2017-08-28 22:26:19 INFO (MainThread) [homeassistant.components.camera] Setting up camera.foscam
2017-08-28 22:26:19 ERROR (MainThread) [homeassistant.components.camera] Error while setting up platform foscam
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/helpers/entity_component.py", line 164, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=self.hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.6/asyncio/futures.py", line 245, in result
    raise self._exception
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/camera/foscam.py", line 39, in setup_platform
    add_devices([FoscamCam(config)])
  File "/usr/src/app/homeassistant/components/camera/foscam.py", line 56, in __init__
    from foscam.foscam import FoscamCamera
  File "/usr/local/lib/python3.6/site-packages/foscam/__init__.py", line 1, in <module>
    from foscam import FoscamCamera
ImportError: cannot import name 'FoscamCamera'

In which Docker release will the Focam Cameras work again?
As stated above, in Docker version 0.52.1 it is not fixed...

Still broken in 0.53 for me too.

Fixed in 0.53.1 that went out 10 seconds ago

heyoooooo! great!

Thanx!


Add an option to display minimap to the left.

Now, you can put minimap to the left in the editor.
Like this:

 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.:x: saighost sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

#24395


Update Tailor to use ES6

Even though NodeJS (along with --harmony flag in v4) provides a lot of ES6 features, the Tailor code doesn't use all of them. Update the code to refactor the Tailor code using ES6. E.g.

Add destructuring to files

fragmentObj = Object.assign({}, { name: node.name, attributes: node.attribs});

to
const { name, attribs: attributes } = node;
fragmentObj = Object.assign({}, { name, attributes});

Use () => to avoid some boilerplate

const stripUrl = (fileUrl) => {
    return path.normalize(fileUrl.replace('file://', ''));
};

const stripUrl = fileUrl => path.normalize(fileUrl.replace('file://', ''));

@addi90 Thanks for the idea and yes indeed there are even lots of places where all the features are not utilised.
It would be even cool if we can get https://github.com/babel/babel-preset-env to work and ship to 4.4.x and major versions.

btw. you guys maybe consider looking into https://github.com/lebab/lebab ? As it does the opposite turns ES5 code into ES6/ES7 it might be interesting or worth checking out. Maybe it could save some time doing replacements manually ?

@fokusferit Looks interesting. I will try it today to see if it is exhaustive in the ES5-ES6 conversion. Thanks a lot for sharing this

Node 4.x active LTS period is up until 2017-04-01, for reference.


[FEAT] Please provide Flutter SDK for jwPlayer

JwPlayer doesn't have an official flutter sdk. These days all greenfield projects are choosing flutter for mobile app development. Not having JWPlayer SDK available on flutter would be a big let down.
Is there a plan for providing support for this anytime soon ? Would be great if you provide some rough timeline

Hi @nateshmbhat, We don't plan to create and support a Flutter plugin for our native SDKs. If this is a need, I'd suggest making your own plugin around our SDK, similar to how this repository does for React Native. I'd recommend checking out this repository, which a former employee made as an introductory guide to Flutter. It could serve as a starting point if you want to create your own interface.
I have brought your request up with our product team, but it would be helpful if you also logged this with your account manager or our support team via our requests portal so we can associate the ask with your account. I can't promise we will end up supporting Flutter, but the more interested customers, the more likely we will.


Verify if page exists inside "destination"

The site config destination is the directory where Jekyll will create the files, so when verifying if a page exists to include on the sitemap search inside this directory.

Apologies for the (huge) delay here. This project is no longer maintained, and I'm archiving it.


Cache filenames

Hi,
With large API parameter strings (like lookups for the IDs of a load of pilots, by name) the filenames of the cache files get too big. Can be solved by using an md5/sha1 hash of the argument list instead of the raw argument list.
Cheers :)

please see https://github.com/ppetermann/pheal/issues/19


Script generation requires connectionString

Running dotnet ef migrations script without a connectionstring causes it to fail: "The string argument 'connectionString' cannot be empty."
Running the command without a connectionstring on present is not uncommon on build servers.
Adding a dummy connectionString causes it not to fail.
Steps to reproduce
Run dotnet ef migrations script on any EF Core project.

Possible duplicate of #9244

This is covered by the work in #9244, #8494, and #8427


[DO NOT MERGE] Added logging to RowMerger and WatchDog to detect stuck streams

Builds on top of pr. New changes:

Moves the pr#2369 to bigtable-1.x branch
Adds logs to AbstractRetryingOperation to log channel id for cancelled operations as well
Add logs to RowMerger to enable a heartbeat. This will help us debug the absence of RowMerger logs from pr#2639 when stream gets stuck for 2+ mins.

Should this be closed now that there is a newer version #2769?

Please re-open if this is still needed


Supporting rewriting the issuer for split-plane networking

It's necessary to support more flexible rewriting of the issuer hostname to support scenarios like "pachd and enterprise server in the same cluster, both port-forwarded". This might not be a common use case but customer team will need it to experiment.

Hopefully this helps? You're right, issuer is the path from the user's browser to the enterprise server. The override is the path from pachd to the enterprise server, which isn't localhost in deployment example 3.
My hope would be that nobody actually does this in real life, and they do pattern 1, but I know customer team likes to have self-contained demos that don't depend on DNS, etc.

Closing this for now, it wasn't necessary for testing.


Doesn't support folders with spaces in name

Add quotations around %1 in the registry command.

Cheers for letting me know, and sorry for a delay in response.
I'll have a look at it

Ok that should be fixed now, have a look at the latest version and reopen the issue if something's wrong.
Have a nice day o7


Brew is 'Ignoring ffi-1.13.1 because its extensions are not built.'

brew config output
brew config
Ignoring ffi-1.13.1 because its extensions are not built. Try: gem pristine ffi --version 1.13.1
/Library/Ruby/Gems/2.6.0/gems/forwardable-1.3.1/lib/forwardable/version.rb:3: warning: already initialized constant Forwardable::VERSION
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:116: warning: previous definition of VERSION was here
/Library/Ruby/Gems/2.6.0/gems/forwardable-1.3.1/lib/forwardable/version.rb:4: warning: already initialized constant Forwardable::FORWARDABLE_VERSION
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:117: warning: previous definition of FORWARDABLE_VERSION was here
HOMEBREW_VERSION: 3.0.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: b712bcc01e8fdaae25d6f232f51637bf00db307f
Last commit: 8 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: c32b1b6839bb623442dfd5f901b84c421753317f
Core tap last commit: 37 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.zjTBMiJzP2/org.macosforge.xquartz:0
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: octa-core 64-bit kabylake
Clang: 12.0 build 1200
Git: 2.30.1 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.2.1-x86_64
CLT: <IP_ADDRESS>.1.1610135815
Xcode: N/A
XQuartz: 2.7.11 => /opt/X11
brew doctor output
brew doctor
Ignoring ffi-1.13.1 because its extensions are not built. Try: gem pristine ffi --version 1.13.1
/Library/Ruby/Gems/2.6.0/gems/forwardable-1.3.1/lib/forwardable/version.rb:3: warning: already initialized constant Forwardable::VERSION
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:116: warning: previous definition of VERSION was here
/Library/Ruby/Gems/2.6.0/gems/forwardable-1.3.1/lib/forwardable/version.rb:4: warning: already initialized constant Forwardable::FORWARDABLE_VERSION
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/forwardable.rb:117: warning: previous definition of FORWARDABLE_VERSION was here
Your system is ready to brew.

[X] The brew doctor above contains no "Warning" lines.

What were you trying to do (and why)?
run 'brew upgrade'
What happened (include all command output)?
I am getting these new errors pertaining to 'ffi' package and I am not sure what caused it.
What did you expect to happen?
I expect that it would not have these warnings.  I tried to run 'gem pristine ffi --version 1.13.1' but it did not help.  I do see that my system version of ruby (2.6) is older than the ruby I installed using brew (see below).
ruby --version
ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-darwin19]
Step-by-step reproduction instructions (by running brew commands)
see gist.

Gist: https://gist.github.com/gpkirk/3f68dc8540e325f0f4e12fec86313a8b

Started getting the same today, but for msgpack.
Ignoring msgpack-1.3.1 because its extensions are not built. Try: gem pristine msgpack --version 1.3.1

This can be fixed by uninstalling those gems from your system. I'm looking into the feasibility of brew ignoring those gems however, since it's not the first time user-installed gems has caused problems.
To be clear: they are warnings, not errors, but I can see that they are indeed annoying.

To be clear: they are warnings, not errors, but I can see that they are indeed annoying.

Closing given this.

That worked great!  Thanks!
Sincerely,
Geoff Kirk
<EMAIL_ADDRESS>1244 Williston Drive
Lawrenceville, GA  30044
mobile ~<PHONE_NUMBER>
On Mon, Feb 22, 2021 at 9:38 PM Bo Anderson<EMAIL_ADDRESS>wrote:

This can be fixed by uninstalling those gems from your system. I'm looking
into the feasibility of brew ignoring those gems however, since it's not
the first time user-installed gems has caused problems.
To be clear: they are warnings, not errors, but I can see that they are
indeed annoying.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Homebrew/brew/issues/10675#issuecomment-783836946,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIZH7L6VNITACSDVVFJ3LLTAMIJPANCNFSM4YBJ63FQ
.


Including pycocotools as explicit dependency

Addresses user feedback from Slack community:

Hey, I had installed fiftyone. Then when I tried running the sample script in #announcements channel, I got the pycocotools import error (ImportError: The requested operation requires that 'pycocotools' is installed on your machine). I then fixed this with : pip install "git+https://github.com/philferriere/cocoapi.git#egg=pycocotools&subdirectory=PythonAPI". In the next attempt, the script seems to be downloading the coco dataset (Downloading images zip to '/home/kritik/fiftyone/coco-2017/tmp-download/val2017.zip'). Perhaps the download progress should also be shown since it has not been downloaded in the past 10-15min and I cant figure out if it is working or not

Specifically, adds pycocotools as an explicit dependency (it's small), and fixes the lack of progress bar when downloading COCO.
The lack of progress bar was addressed by https://github.com/voxel51/eta/commit/336a27a0e0ac0ed6afbd02a204582b77d27ac1d2 and https://github.com/voxel51/eta/commit/03d3101d8f0a103c9130fa7d75959ed032359ee9, which will make their way into FiftyOne when running dataset = foz.load_zoo_dataset("coco-2017", split="validation") with a build of FiftyOne that includes the latest ETA.

When trying to download COCO on a clean install, I also ran into an error that torch wasn't installed. The zoo should check that the required ML backend is downloaded and provide a useful error message if torch/tf needs to be installed before loading a dataset

I'm going to convert this to an issue. Currently, if you try to download a zoo dataset without a valid ML backend, you get an error like ImportError: The requested operation requires that 'torch' is installed on your machine, which is fairly informative.
I think you're requesting an even more informative error like "You must install a supported ML backend to download datasets from the FiftyOne Dataset Zoo. See  for more information". This is fair, but it will take some more work.

Issue for @ehofesmann's request: https://github.com/voxel51/fiftyone/issues/415


Pandas deprecation error

I have installed Macest in an ad hoc Anaconda environment to make sure all the requirements meet the exact version required. This includes pandas==1.0.3
However, I am not able to make it work with Pandas dataframes due to a deprecation error:
File "test_macest.py", line 48, in
macest_model.fit(X_cal, y_cal)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/macest/classification/models.py", line 397, in fit
train_helper.fit(optimiser_args=optimiser_args)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/macest/classification/models.py", line 625, in fit
point_preds[conflicts] == self.y_cal[conflicts]
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/series.py", line 910, in getitem
return self._get_with(key)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/series.py", line 943, in _get_with
return self.loc[key]
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/indexing.py", line 1768, in getitem
return self._getitem_axis(maybe_callable, axis=axis)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/indexing.py", line 1954, in _getitem_axis
return self._getitem_iterable(key, axis=axis)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/indexing.py", line 1595, in _getitem_iterable
keyarr, indexer = self._get_listlike_indexer(key, axis, raise_missing=False)
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/indexing.py", line 1552, in _get_listlike_indexer
self._validate_read_indexer(
File "/home/mirix/anaconda3/envs/macest/lib/python3.8/site-packages/pandas/core/indexing.py", line 1654, in _validate_read_indexer
raise KeyError(
KeyError: 'Passing list-likes to .loc or [] with any missing labels is no longer supported, see https://pandas.pydata.org/pandas-docs/stable/user_guide/indexing.html#deprecate-loc-reindex-listlike'

It works if the dataframes are converted to numpy arrays.


Support creating users with a password

This allows for creating users with a password by setting the "password" attribute
if "Change Password Supported" is true, similar to how updateResource handles it

Please provide an additional unit test to prevent future regressions. There is already an existing unit test that you can use as template:
@Slf4j
public class UserHandlerTest extends AbstractScimEndpointTest
{

  /**
   * verifies that the user password can be updated if support is enabled
   */
  @Test
  public void testUpdatePassword()
...


use of model.eval() and torch.no_grad()

Hi, first of all congratulations on your great work and thanks for providing the code public!
I have couple questions about the usage of model.eval() and with torch.no_grad()
In main.py, for 'TENT' and 'EATA', you call the validate function defined on line 34, but for 'SAR' , the validation code is written inside the if state of  'SAR' from line 294 - 322. The difference is that for SAR, model.eval() and with torch.no_grad() are not used while both of them are used in the validate function.

Is there particular reason why SAR does not need model.eval() and with torch.no_grad() ?
Would the batch normalization parameters be optimized for 'TENT' and 'EATA' with model.eval() and torch.no_grad() ?

Thank you!

Hi, thanks for your appreciation!
A1. I think there should be no difference for SAR, regardless of whether [.eval() and .no_grad()] are used or not. Perhaps you could verify this?
A2. The norm parameters will be updated, as we use @torch.enable_grad() in all of the following: [tent.py, eata.py, sar.py].
Actually, it seems that the existence of .eval() and .no_grad() is simply due to copying the validate function from another project :)
Hope that helps!

Yeah I run the train code of SAR with model.eval() and torch.no_grad() inserted between line 300 and 301 for ResNet50-GN under mix_shifts corruption level 5 experiment setting and got 38.2 which is almost the same as the result reported in the paper.
So I guess the use of model.eval() and torch.no_grad() does not really matter.
May be the line 294 - 322 of main.py can be replaced by just calling the validate function.
Thank you!

No problem at all:)


Move repo to main tiki GitHub org

Consolidating GitHub orgs

GH Actions release workflow references NPM_TOKEN repo level secret.


Convert all v1 recordings to filter bank representations.

This is a separate task for filter banks from issue #3.

Task was completed.


Error handle error

Version of protoc (protoc --version)
3.0
Version of ProtocolBuffers.framework
2.4.1
.proto file to reproduce

Description
I got a lot of errors when running in Xcode with compile result.
I showed that
call can throw, but it is nor marked with 'try' and the error is not handled
Can we have a fix that?
Kind regards,
Than Dang

Get me example. How does you use try?

You have to input try! before an invoke function to fix the error. And I think the problem was about swift version, isn't it?

Here is the error I get https://monosnap.com/file/qXxX8LEuYJxT3SMVHFlDnk4pgsvCoA

You use very oldest version of protobuf-swift.

hmm, let me check. Thanks a lot.

Cool, great help. Thank you so much. What I missing is not follow all step of installation by thinking about use CocoaPod instead. But the last step 7.Add ./src/ProtocolBuffers/ProtocolBuffers.xcodeproj in your project. we don't need actually.