DATA: Clean up the date field

The first_date field in the data layer is not always filled. We need to find a solution to complete this, maybe using the system attribute CreationDate. Question is to make it manual or automatic?

Solution: Calculate a new field finalDate like this: COALESCE("first_date", "last_date", "CreationDate")
Use the webapp to always check if there is a new entry and fill this field

Done, but realized it only works when logged in. And there is a lag. Maybe we need to find another solution


Switch from the removed yaml.safeLoad to yaml.load

Solves the following error when using a YAML config file:
Parse options error: Cannot read config file: /app/.groovylintrc.yaml
Error: Function yaml.safeLoad is removed in js-yaml 4. Use yaml.load instead, which is now safe by default.

What is the issue with the safeLoad ?

As the error states safeLoad was removed in js-yaml version 4 and thus the entire yaml system is broken. The normal load function notes is safe by default.
Probably needs a unit test so that yaml loading can have regressions like this detected automatically.


Add string constraints (pattern)

for issue #50

Coverage decreased (-0.2%) to 94.099% when pulling 2270e43c4940c1cb0597de5f70b03b8f5c367249 on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

Coverage decreased (-0.2%) to 94.099% when pulling a35d23b647ff1c17c509d1b7552dc69f547dbd7a on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

Coverage increased (+0.05%) to 94.31% when pulling ea0334a115fb1b840f59bf238e7c167ded9b06be on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

Coverage decreased (-0.3%) to 93.911% when pulling f07283b21b9172ab19ee8d18f75cd5959e8e1416 on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

In order to check the error of regex.Compile, I compile pattern to regex before we call decodeString() in string_test.go.
By the way, for the coverage result of field.go, should I also add some testing to test pattern for compiledRegexp ?

Agreed.
Em 4 de out de 2017 10:04, "Hung-Wei Chiu"<EMAIL_ADDRESS>escreveu:

@hwchiu commented on this pull request.
In schema/string.go
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142663415
:

}

if maxLength != 0 && len(v) > maxLength {

return fmt.Errorf("constraint check error: %s:%v %v > maximum:%v", t, v, maxLength)

return fmt.Errorf("constraint check error: %v %v > maximum:%v", v, len(v), maxLength)

}
if pattern != nil {

match := pattern.MatchString(v)

I think we still need to check if compiledRegexp is nil, because the
compiledRegexp won't be initialized in some cases.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142663415,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIiWQ9DYV3oGNy7iath0pBsg4tnmDLe7ks5so4J0gaJpZM4PrnkL
.

Exactly! It is okay to use in our testing.
Em 4 de out de 2017 10:15, "Hung-Wei Chiu"<EMAIL_ADDRESS>escreveu:

@hwchiu commented on this pull request.
In schema/string_test.go
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142665808
:

@@ -29,9 +32,20 @@ func TestDecodeString_ErrorCheckingConstraints(t *testing.T) {
{"InvalidMaxLength_UUID", "6fa459ea-ee8a-3ca4-894e-db77e160355e", stringUUID, Constraints{MaxLength: 1}},
{"InvalidMaxLength_Email"<EMAIL_ADDRESS>stringEmail, Constraints{MaxLength: 1}},
{"InvalidMaxLength_URI", "http://google.com", stringURI, Constraints{MaxLength: 1}},

{"InvalidPattern_UUID", "6fa459ea-ee8a-3ca4-894e-db77e160355e", stringUUID, Constraints{Pattern: "^[0-9a-f]{1}-.*"}},

{"InvalidPattern_Email"<EMAIL_ADDRESS>stringEmail, Constraints{Pattern: "[0-9].*"}},

{"InvalidPattern_URI", "http://google.com", stringURI, Constraints{Pattern: "^//.*"}},

ok, The reason why I don't use MustCompile before is it will panic the
program when it compile fails rather than issue an error.
I think we can control those testing pattern to make sure it always
compile success, so, it's fine to use MustCompile to pass complied patten.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142665808,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIiWQ7qR1slINS7UZMoPweEhUHnzHGwmks5so4TXgaJpZM4PrnkL
.

But we will in our production code, which is what matters for this snippet.
So the test case should adapt and pass both: Pattern and compiled pattern.
In that way you have the testing mimicking production, which is super
desired.
Em 4 de out de 2017 10:21 AM, "Hung-Wei Chiu"<EMAIL_ADDRESS>escreveu:

@hwchiu commented on this pull request.
In schema/string.go
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142667452
:

}

if maxLength != 0 && len(v) > maxLength {

return fmt.Errorf("constraint check error: %s:%v %v > maximum:%v", t, v, maxLength)

return fmt.Errorf("constraint check error: %v %v > maximum:%v", v, len(v), maxLength)

}
if pattern != nil {

match := pattern.MatchString(v)

if false == match {

	return fmt.Errorf("constraint check error: %v don't fit pattern : %v ", v, pattern)

I think we should print out the compiled pattern to show the pattern
instead of the Constraints.Pattern, because we won't pass any
pattern(string) to Constraints in our testing function (string_test.go).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/frictionlessdata/tableschema-go/pull/52#discussion_r142667452,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIiWQx9sQJoA5MpNLI0QoNo8nHHwGv0bks5so4ZugaJpZM4PrnkL
.

Coverage decreased (-0.3%) to 93.924% when pulling ea0f0f63f3fe968cc954238d7d0b25e30b05db38 on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

ok, I will pass pattern to constraint too

Coverage decreased (-0.3%) to 93.924% when pulling 73082d035797e5c22c47bee26d3985de8ee5d534 on hwchiu:add-string-constraints into 8912050fec40fd0560512d547472f27b9c85d1d8 on frictionlessdata:master.

Super! Thanks for those changes!


Internal Service Error on Ubuntu and RPi3

Describe The Problem
Cannot login to dashboards on either a Ubuntu or a RPi install. Ubuntu install was installed with fresh WireGuard install, RPi install had an already configured WireGuard setup.
Attempting to login with the dashboard with the default username admin and password admin results in an internal server error:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.

Expected Error / Traceback
For Ubuntu:
[2022-01-24 11:47:39,116] ERROR in app: Exception on /auth [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 2073, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1518, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1516, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1502, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "dashboard.py", line 704, in auth
    password = hashlib.sha256(data['password'].encode())
TypeError: 'NoneType' object is not subscriptable'

For RPi:
[2022-01-24 11:41:35,080] ERROR in app: Exception on /auth [POST]
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 2073, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1518, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1516, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.7/dist-packages/flask/app.py", line 1502, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "dashboard.py", line 704, in auth
    password = hashlib.sha256(data['password'].encode())
TypeError: 'NoneType' object is not subscriptable

Sidenote: Are my user permissions bad? I see the traceroute says fail on /auth is that for my authentication or is that on wg-dashboard? This error is the same across two distros so it must be something consistent with either wg-dashboard or my network.
To Reproduce
I did a fresh install of both wg-dashboard and wireguard into their default directories running them with ./wgd.sh start. I then tried to access them via the ip and port with default credentials. Upon entering credentials I am greeted with an internal server error.
OS Information:

OS: Ubuntu 20..04.1

Python Version: 3.8.10

OS: Linux 5.10.63-v7+

Python Version: 3.7.3

Sample of your .conf file
Ubuntu:
[Interface]
Address = <IP_ADDRESS>/24
SaveConfig = true
ListenPort = 51820
PrivateKey = ABCD
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -t nat -A POSTROUTING -o wlp0s20f3 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -t nat -D POSTROUTING -o wlp0s20f3 -j MASQUERADE

RPi:
[Interface]
Address = <IP_ADDRESS>/32
ListenPort = 47111
PrivateKey = ABCD
DNS = <IP_ADDRESS>

PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

[Peer]
#x360
PublicKey = ABCD
PresharedKey = ABCD
AllowedIPs = <IP_ADDRESS>/32, fd08:4711::2/128, <IP_ADDRESS>/24

If any more information is required please let me know! I know I'm prone to making simple errors sometimes lol

Hi, i'm sorry that you encountered problems. Would you mind telling me which browser did you used?

All good! Problems happen especially with homebrew stuff, no sweat 👍
I'm using the Brace browser (chromium based I think). I just tried Firefox and got the same result:
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 2073, in wsgi_app
    response = self.full_dispatch_request()
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1518, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1516, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/local/lib/python3.8/dist-packages/flask/app.py", line 1502, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "dashboard.py", line 704, in auth
    password = hashlib.sha256(data['password'].encode())
TypeError: 'NoneType' object is not subscriptable

I may have misunderstood the order of operations for this dashboard so I will attempt to clarify my thoughts:
Does there need to be an initial peer set up to connect to the WG tunnel? I assumed one could do a fresh WG install without any peers, connect to the dashboard from any PC on their LAN, and then create peers that way.
If you need clarification let me know, when I translate thoughts-to-words I usually tend to overcomplicate, sorry!

This is weird. I will check on the front-end code, it seems like when you click Sign In, it did not send the password to the server, so it caused the issue.  I assumed one could do a fresh WG install without any peers, connect to the dashboard from any PC on their LAN, and then create peers that way.

As for this, you don't need to configure initial peers to have it work, as long as you have an initial configuration, then you can add peers with the dashboard ;)

This is weird. I will check on the front-end code, it seems like when you click Sign In, it did not send the password to the server, so it caused the issue.  I really appreciate it.

Does there need to be an initial peer set up to connect to the WG tunnel? I assumed one could do a fresh WG install without any peers, connect to the dashboard from any PC on their LAN, and then create peers that way.

As for this, you don't need to configure initial peers to have it work, as long as you have an initial configuration (empty configuration with no peers), then you can add peers with the dashboard ;)

Ok cool so my brain is working correctly, thank goodness haha

Hmmm.. I've test couple of times on my side with different browser and they all works well. Could you briefly tell me how did you sign in? I will continue to look into the code to see if anything that is causing the trouble ;)

Hmmm.. I've test couple of times on my side with different browser and they all works well. Could you briefly tell me how did you sign in? I will continue to look into the code to see if anything that is causing the trouble ;)

Sure; I navigated into the IP of the host using the default port, entered admin into the username space and admin into the password space and then hit sign in. After doing that I get the server internal error.

Hmm.. Do you mind help me to debug something? I made a GIF on what i'm looking for. Basically I want to know if the browser did send the username and password to the server.

Yeah sure! Be back in a few minutes.

Thank you!!

Got the following out. Could if be my windows firewall blocking the submission...? Will test that out with port cleared from windows firewall side.

Hmm but if that's the case, you won't even able to open the webpage. Is this a screenshot from Brave?

Yup its a screenshot from Brave, I'll do the same sequence in chrome and post the result.

It seems like, you did a "Form" post, instead of a ajax post... So basically your webpage file is from an older version, and the server (python codes) is from a new version. Do you mind updating the server and try it out? You can follow this https://github.com/donaldzou/WGDashboard#update-method-2 to update the dashboard

Attempted update, got return that it was latest image, attempted login again and got same error.

This got me thinking... Did you disabled Javascript on your browser?

GOT IT
Holy moly this one is extremely unique to me. I recently set up some blocklists on my Pi-Hole and one of them was blocking
code.jquery.com
(blocked cds.s5x3j6q5.hwcdn.net)

After adding that to the whitelist the login works perfectly.
Thanks so much for your help @donaldzou! Sorry this took so long and ended up being such a niche use-case.

Ahah nice!! I would consider to move all dependencies to local. But the reason is flask running on HTTP 1.1, and it need to wait for resources 1 by 1, so would cause longer loading time. By using CDN can have faster loading speed on scripts and CSS libraries. I will close this issue now, if you have any more questions please let me know!!


When creating a plugin for a OpenAPI description with no operationId, the plugin is created with no functions or runtime info

What are you generating using Kiota, clients or plugins?
Kiota plugin
In what context or format are you using Kiota?
Source Build
Client library/SDK language
None
Describe the bug
When trying to create a plugin form an OpenAPI description with no operationId, Kiota is able to generate the right sliced OpenAPI description:
openapi: 3.0.1
info:
  title: JSONPlaceholder
  version: '1.0'
servers:
  - url: https://jsonplaceholder.typicode.com/
paths:
  /posts:
    get:
      description: Get posts
      parameters:
        - name: userId
          in: query
          description: Filter results by user ID
          style: form
          schema:
            maxItems: 1
            type: integer
        - name: title
          in: query
          description: Filter results by title
          style: form
          schema:
            maxItems: 1
            type: string
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/post'
components:
  schemas:
    post:
      type: object
      properties:
        userId:
          type: integer
        id:
          type: integer
        title:
          type: string
        body:
          type: string
  parameters:
    post-id:
      name: post-id
      in: path
      description: 'key: id of post'
      required: true
      style: simple
      schema:
        type: integer

However, the plugin manifest is created with no functions or runtime:
{
  "schema_version": "v2",
  "name_for_human": "JSONPlaceholder",
  "description_for_human": "Description for JSONPlaceholder",
  "description_for_model": "Description for JSONPlaceholder",
  "namespace": "getplugin",
  "capabilities": {
    "localization": {}
  }
}

Expected behavior
The plugin manifest should have a functions and runtime objects even when the OpenAPI description has no operationId
How to reproduce
Use the OpenAPI description above to create a plugin
Open API description file
No response
Kiota Version
workspace feature
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
Click to expand log
```

</details>

### Other information

_No response_

@maisarissi what would you have as a placeholder?
I'm assuming the sliced description also needs the operationId to be set, correct?

They are not required. At runtime, random GUIDs will be generated to ensure their unicity.

so we don't need to change anything here?

We need to generate the functions in the plugin for sure. If they are not generated, they are ignored and won't get called.

ok so back to my previous question, I'm guessing we're using a guid as a placeholder. And I'm guessing the sliced description needs the same guid as operation id?

Do we have better ways to generate operation Ids based on the path? I feel it would be a lot more dev friendly.

Maybe we could generate an operationId combining the endpoint with the HTTP method?
Something like: posts#GET could be posts-list, then posts/{posts-id}#GET could be posts-get, posts#PATCH posts-patch, posts/{posts-id}/comments#GET posts-comments-list, posts/{posts-id}/comments/{comment-id}#GET posts-comments-get and so on and so forth.

According to the validator, we would need the operationId to have the format ^[a-zA-Z0-9_]*$ (essentially number,digits and underscores). So, using something like posts-list would lead to validation error by the plugins lib and we would need to use underscores instead rather than the dash.
Another idea is that we can use the same logic Kiota uses for namespacing for a path and append the operation name at the end and separating them with underscores.
posts#GET => posts_get
posts/{posts-id}#GET => posts_item_get
posts/{posts-id}/comments#GET => posts_item_comments_get
posts/{posts-id}/comments/{comment-id}#GET => posts_item_comments_item_get
Back to the question by @baywet, we probably need to answer,

Should the openApi file that is also generated/sliced from the original description at output also be updated with the added operationIds to match?
Should we attempt to sanitize operationId for the sake of the validator if the original operationId does not match the plugin validation rules? (and update the openApi description as well?).

That's a great proposal @andrueastman. I think this would be optimal! For the questions:

I'd say yes. The orchestrator will report on the operationIds used (not the function names from the plugin) and it'll be super useful for debugging later as devs will know which operation was called.
This is a good question... And I think this is a fair way to ensure success. I'd vote for sanitizing both the plugin function names and the operationIds in a consistent manner. Basically "always" sanitize them to ensure full supportability.

Agree with @sebastienlevert.

Yes, we should add the operationIds to the sliced OpenAPI description.
If the existing operationId in the original OpenAPI document does not match with the validation rules, we should ensure success and sanitize them to successfully generate the sliced OpenAPI and the plugin.


Kadane's Algorithm

I would like to add Kadane's Algorithm for maximum subarray sum problem. It is a famous dynamic programming algorithm.

Thanks for your interest! Kadane's is already implemented here. How refactoring it into an .hpp file as part of the reorganise effort? More details in #163.


Use injected usage supplier in RuntimeTaskImpl.

Summary
Use injected usage supplier in RuntimeTaskImpl.
Context
Currently CgroupsMetricsCollector is hard-coded in RuntimeTaskImpl.java, so if it is overridden using the  mantis.taskexecutor.metrics.collector field in the Mantis agent properties, that isn't respected. This change uses the dynamically loaded implementation of MetricsCollector.
Checklist

[ ] ./gradlew build compiles code correctly
[ ] Added new tests where applicable
[ ] ./gradlew test passes all tests
[ ] Extended README or added javadocs where applicable

I accidentally closed this PR, so I created https://github.com/Netflix/mantis/pull/674.


V1.1.0 - VPaid and no duration (-1)

Hi,
Since the new version of this plugin, you changed the calculation of Ad duration and remaining time
Here you can find before VS now (I simplified and removed functions)
In bold(V1.1.0), the changing line
V0.8:
      var remainingTime = this.adsManager.getRemainingTime();
      var duration =  this.currentAd.getDuration();
      var currentTime = duration - remainingTime;
      currentTime = currentTime > 0 ? currentTime : 0;

      var remainingMinutes = Math.floor(remainingTime / 60);
      var remainingSeconds = Math.floor(remainingTime % 60);
      if (remainingSeconds.toString().length < 2) {
        remainingSeconds = '0' + remainingSeconds;
      }

V1.1.0:
  var remainingTime = this.adsManager.getRemainingTime();
  var duration = this.currentAd.getDuration();
  var currentTime = duration - remainingTime;
  currentTime = currentTime > 0 ? currentTime : 0;

  **var remainingTime = duration - currentTime;** // We override the first remainingTime here

  var remainingMinutes = Math.floor(remainingTime / 60);
  var remainingSeconds = Math.floor(remainingTime % 60);
  if (remainingSeconds.toString().length < 2) {
    remainingSeconds = '0' + remainingSeconds;
  }

As we use VPaid, sometimes there are strange cases where:
this.currentAd.getDuration() returns -1
this.adsManager.getRemainingTime() return 15 seconds for example (this method seems to be more stable, and return a value in more cases than the other)
As we don't use it anymore to calculate the remaining time, we have sometimes VPaid with -1;-1 values which were not the case in 0.8
Any reasons the two methods return different results?
Thanks

Hey there - sorry I sent out a PR but forgot to respond here. I'm changing the plugin to avoid re-calculating the remainingTime, so this should fix your issue.

This fix is now available in 1.1.1.


"處理程序" doesn't  the translation

"處理程序" is keyword doesn't the translation, use origin "process" keyword.

文件詳細資料
⚠ 請勿編輯此區段。 這是 docs.microsoft.com ➟ GitHub 問題連結的必要項。

ID: 44aeb504-236b-28fd-bd33-13ebafecaec4
Version Independent ID: eb33ef93-6440-eb5d-e6cb-b1de47d4c211
Content: Hyper-V 隔離
Content Source: virtualization/windowscontainers/manage-containers/hyperv-container.md
Service: windows-containers
Product: windows-containers
GitHub Login: @scooley

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Incorrect commit-index after restart

This is related to #24 .

Members={A,B,C,D}
Start A, B, C, A is leader
Kill C, now we have no majority
Make a change: last-applied=1, commit-index=0 in A and B
Kill B and A
Restart A and B, start C
-> commit-index should now (we have the majority) be 1, but it is still 0 in A, B and C

Another issue: when we have 2 requests (3-4) in the leader's RequestTable with last_applied=4 and commit_index=2, and the leader crashes and is restarted (or a new leader is started), then RequestTable needs to be populated with pending requests.
If this is not done, the new leader will start trying to commit pending entries 3 and 4 and when the AppendEntries responses are received, and the RequestTable is empty, we won't ever commit entries 3 and 4.
Solution: when becoming leader, populate RequestTable from the log: add entries in range [last_applied+1 ..  commit_index].

We have this scenario on restart of A and B (2 changes):

A: last_applied=2, commit_index=0
B: last_applied=2, commit_index=0

The code in RAFT.sendAppendEntriesMessage() does not handle this situation; we will never resend entries 1 and 2 !

Todo: unit test for #30 and for changing of leader

Unit test for #30 and #31 is AppendEntriesTest.testLeaderRestart()


HDDS-8867. Datanode re-registration memory leak

What changes were proposed in this pull request?
Fix a memory leak where datanodes re-registering with different address were left in the dnsToUuidMap.  This was caused by trying to remove dnsName instead of uuid from the value Set<String> of dnsToUuidMap.  The bug is revealed by changing Set<String> to Set<UUID> (being done in HDDS-8854).
Reproduced by adding assertion in existing test:
TestSCMNodeManager.testScmRegisterNodeWithUpdatedIpAndHostname  Time elapsed: 3.104 s  <<< FAILURE!
org.opentest4j.AssertionFailedError: expected: <[]> but was: <[4cea4603-f41f-4008-9ec5-6862bf56737b(host2/<IP_ADDRESS>)]>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
	at org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
	at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
	at org.apache.hadoop.hdds.scm.node.TestSCMNodeManager.testScmRegisterNodeWithUpdatedIpAndHostname(TestSCMNodeManager.java:2082)

Get rid of SuppressFBWarnings by using computeIfAbsent instead of get and put.
https://issues.apache.org/jira/browse/HDDS-8867
How was this patch tested?
Unit test modified.
CI:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/5287322307

Thanks @sodonnel for the review.


arch:risc-v:bl602: enable FPU for this target.

Summary
This patch enables the FPU support for arch:risc-v:bl602 SoC.
Impact
RV32IM targets.
Testing
The FPU tests within ostest passed.

@hotislandn please run to fix the CI error:
./tools/refresh.sh --silent bl602evb:fpu

tools/refresh.sh --silent bl602evb:fpu

Thanks for your advice, xiaoxiang781216. And here comes the updated version.

@xiaoxiang781216 I would like to give this a look this weekend before merging so I can test if that's alright.

@xiaoxiang781216 I would like to give this a look this weekend before merging so I can test if that's alright.

Sure, let's wait your test.

There was a small style issue that I fixed, but tested and looks good.
@xiaoxiang781216 did want to get your thought on this.  Seems like we should just move this section to be common per arch as a general cleanup?
https://github.com/apache/incubator-nuttx/pull/2809/files#diff-4901235976e131b4b1ba0507040dc1d33d669366a5973196d4cab6c43626078bR73-R95

Yes, I think it's better to part of rv32/rv64 to avoid the duplication in each chip. We can refine it with new PR.

Yes, I think it's better to part of rv32/rv64 to avoid the duplication in each chip. We can refine it with new PR.

Sounds good, I can put one together for all the arch this week.

Yes, I think it's better to part of rv32/rv64 to avoid the duplication in each chip. We can refine it with new PR.

Sounds good, I can put one together for all the arch this week.

Thanks and have a nice day!


fix: external import of block

@buuhuu I added fixes for the following issues to this PR as well.

https://github.com/hlxsites/sony-biotech/issues/340

https://github.com/hlxsites/sony-biotech/issues/341

custom sort filter order

do not display empty product thumbnails

do not include format filter of "0"

combine facet buckets across multiple categories when in grouped view

Build form this branch is included with https://github.com/hlxsites/sony-biotech/pull/342


Python 2.6 is no longer supported by the most recent version of virtualenv

I'm trying to use this container to test my library against multiple Python versions with tox.
 However, this is the error I get with Python 2.6: tox can't use the modern virtualenv to create a Python 2.6 testing environment:

GLOB sdist-make: /app/setup.py
py26 create: /app/.tox/py26
ERROR: invocation failed (exit code 101), logfile: /app/.tox/py26/log/py26-0.log
ERROR: actionid: py26
msg: getenv
cmdargs: ['/.pyenv/versions/3.7.0/bin/python', '-m', 'virtualenv', '--python', '/.pyenv/shims/python2.6', 'py26']
ERROR: None
ERROR: this script requires Python 2.7 or greater.
Running virtualenv with interpreter /.pyenv/shims/python2.6
ERROR: Error creating virtualenv. Note that some special characters (e.g. ':' and unicode symbols) in paths are not supported by virtualenv. Error details: InvocationError('/.pyenv/versions/3.7.0/bin/python -m virtualenv --python /.pyenv/shims/python2.6 py26 (see /app/.tox/py26/log/py26-0.log)', 101)

This has happened because virtualenv has dropped support for Python 2.6 since 16.0.0.
If I manually install virtualenv==15.2.0, which supports Python 2.6, there's another error:

root@10ac4fa81171:/src# tox -e py26
GLOB sdist-make: /src/setup.py
py26 create: /src/.tox/py26
py26 installdeps: -rrequirements-dev.txt
ERROR: invocation failed (exit code 1), logfile: /src/.tox/py26/log/py26-1.log
ERROR: actionid: py26
msg: getenv
cmdargs: ['/src/.tox/py26/bin/python', '-m', 'pip', 'install', '-rrequirements-dev.txt']
/src/.tox/py26/bin/python: pip is a package and cannot be directly executed

An ugly solution is to add the following line to tox.ini:
install_command=pip install {opts} {packages}(ARGV)

This gives a new error:

tox.exception.ConfigError: ConfigError: 'install_command' must contain '{packages}' substitution

This is a tox bug. Got to update it first:
$ pip install -U tox

And now, finally, the container works fine.
But it does not have to be like that, does it? :)

Another partial solution that worked for me was to switch to a different Python version.
I ran this inside the container:
$ pyenv local 3.6.6
$ pip install -U pip setuptools virtualenv tox tox-pyenv
$ /docker-entrypoint.sh tox

This fixed Python 2.6, but failed on every Python3.

First things first: Thanks for conceiving docker-tox, Matthew. We had the pleasure to use it for mqttwarn and it worked like a charm.
After just adding py26 to our list of environments, the build process [1] on CircleCI croaked like that:
GLOB sdist-make: /root/project/setup.py
py26 create: /root/project/.tox/py26
ERROR: invocation failed (exit code 1), logfile: /root/project/.tox/py26/log/py26-0.log
================================== log start ===================================
Traceback (most recent call last):
  File "/.pyenv/versions/3.7.5/lib/python3.7/site-packages/virtualenv.py", line 53, in <module>
    print("ERROR: {}".format(sys.exc_info()[1]))
ValueError: zero length field name in format
Running virtualenv with interpreter /.pyenv/versions/2.6.9/bin/python2.6

=================================== log end ====================================
ERROR: InvocationError for command /.pyenv/versions/3.7.5/bin/python -m virtualenv --no-download --python /.pyenv/versions/2.6.9/bin/python2.6 py26 (exited with code 1)

[1] https://app.circleci.com/jobs/github/jpmens/mqttwarn/15


collect and view system metric data

we will be able to collect system metric data and view the data.
Data is collected through telegraf and stored in pinot.
Before the function is completed, work on the system metric branch first.

How to use telegraf agent collect data


<EMAIL_ADDRESS>

transaction to be made in advance of the payment generated from our account details and we shall also forward the receipt to you 😀


I found a bug in this repository.

When I import a file from the oldest version of the Voxel Builder, the .vox file is not showing up on the latest version. I am working on a blender project, and the newest version is not accepting the file. Why is it doing this?

Old version:
New version:

That's not a bug, but thank you for the report!
File format changed since v3.6.0, to add new layering system,
To fix that, just add ",true" to every single line. (try VSCode to find and replace in batch)
[ Old file format ]
0,0,0,#FFFFFF
1,1,1,#FFFFFF
[ New file format ]
0,0,0,#FFFFFF,true
1,1,1,#FFFFFF,false

Ok thanks! It will take a while, but I guess it is the only way lol

Ok thanks! This helps a lot :D

New File Format Updater addon for backward compatibility
Thank you @TheRealDigitalMaster

YW :)


when using Nested Routes,  hot-reload is not working,  child page can not  be rerendered

Version
3.2.3
Environment info
windows 10

Steps to reproduce
none
What is expected?
rerender the page
What is actually happening?
rerender the page is not happening

this happens when a router has multi-children, and you change path in the browser between these path, then you change you code in any of  multi-children components, page can not be rerendered

Please provide a reproduction repo.

it's my vue.config.js's problem, I find it.

Can you please mention what should be placed in the config specifically? I'm actually having the same issue

I have same issue as well. How to fix this?

Please provide a reproduction repo.

it's my vue.config.js's problem, I find it.

Please provide solution

I found the solution.
You need to add the following in your index.html under

I found the solution.
You need to add the following in your index.html under

I found the solution.
You need to add the following in your index.html under
<base href="/" />

Thank you @nehalshah50 . This solved the issue

I am facing the same issue in nested routes and after adding <base href="/" /> still not working.
Here is my vite config,
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import eslintPlugin from "vite-plugin-eslint";
import path from "path";

export default defineConfig({
  plugins: [
    react(),
    eslintPlugin({
      cache: false,
      emitError: true,
      failOnError: true,
    }),
  ],
});


runtime_bytecode coverage calculation misses a rare case

Description
There are two contracts in a solidity, let call them A and B. A does not inherit B and B also does not inherit A.
But  A creates an instance of  B in itself.
In this case, the runtime_bytecode of  A includes the creation_bytecode of B.
But in coverage calculation of runtime_bytecode of A, the covered code of B is not considered. Instead, the coverage of covered code of B is given separately based on the code of B and sometimes with a few extra opcodes added.
As a result, there are 3 types of coverage shown.

This can explain why when there are three types of coverage produced, the coverage of runtime_bytecode of a specified contract is rather low.

Of course, if A inherits B, there is not such issue. Since A's code  contains B's code, and the covered code of B is considered in A's coveage calculation.
My assumption is that if B's code is included in A's code, then the covered code in B should also be considered in coverage calculation of B.
But if this assumption is not correct on Mythril, then, this is not a bug at all.
SolidifiedDepositableFactory_05.txt

Yes, thats how it works.
When A inherits B then A contains B's code and it is possible to touch the instructions using some calldata.
In case when A creates an instance of B then B's code in A is unreachable as it is bounded by STOP, it's something like
A's code
....
....
....
STOP
INVALID
INVALID
B's code

The format  varies depending  on the solidity versions.
The B's code can't be reached from A by any means. This code is only used for being loaded into the memory by CODECOPY opcode and then executing CREATE.

Thank you!
In a case of A having an instance of B, B's code is unreachable, why is the code of B not removed from code of A?  Does the code of B is included in A by solc compiler or by Mythril?

It's included by solc.

Thanks!


Add getter/parser for PVGIS hourly-radiation

[x] Closes #849
[x] I am familiar with the contributing guidelines
[ ] Tests added
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Pull request is nearly complete and ready for detailed review.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Add getter/parser for PVGIS hourly-radiation

@mikofski @wholmgren Should the tests for the hourly radiation functions just mimick those for the TMY functions?

That's probably okay. I think the goals for testing should be,  "have I sent the request correctly?"  "Is the response what I expected?" and "did it get parsed right?" Make sure to mark api calls with pytest.remotedata & flaky using the timeout constants from conftest. Thanks.  PS i'm sure my tests could be improved. Don't feel constrained to repeat my mistakes ;)

@kanderso-nrel  @mikofski
The pvgis hourly API is able to return data in three different formats (specified by the outputformat keyword): json, csv, and basic.
The basic format is essentially the same as the csv option, but without a header or metadata. Is there any interest in supporting this option?
Note that for PVGIS TMY the basic format has a header, which it is NOT supposed to have according to the development team behind PVGIS.


Make test_framework available for users when creating scenarios

This changes two important things about how scenarios are written:

Scenario files must be in a directory next to test_framework
Scenario files must have a main() function, instead of (or in addition to) the __name__ == "__main__" logic:

example:
def main():
    ConnectDag().main()

Projects
When a user creates a project, they will get a scenarios/ directory which includes our default scenarios like miner_std.py as well as a complete copy of test_framework. They are welcome to edit the framework, the code in that directory is actually deployed.
Running Scenarios
When executing warnet run <path> this PR bundles up the scenario file, commander.py and the entire test_framework directory into a .pyz archive which is compressed, base64 encoded, and added as raw data in a config map that is deployed along with a vanilla, unmodified image of python:3.12-slim. Deploying our (current) biggest scenario signet_miner.py results in a config map of 118,459 bytes, which is still significantly below the 1 MB recommended maximum for configMap.
Side effects
The grossest thing about this PR in my opinion is that all the scenarios we use only for tests have to be moved as well, so they are in a directory with test_framework. To deal with that, I adjusted the "exclude" logic in copy_scenario_defaults() to filter by regex and then exclude TEST_*.py.
TODO

[ ] add a test that calls warnet init on an empty directory, runs a network and scenario from there to fully test the user flow (reccomend reviewers do this!)

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts
Reviewers, this pull request conflicts with the following ones:

#614 (swap out kubectl by mplsgrant)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

fuck, right...
OSError: [Errno 7] Argument list too long: 'helm'
I guess a command line option with 100,000 bytes of base64 is overkill. Abandoning.


PR: Move Pylint plugin to new API

Description of Changes

[x] Wrote at least one-line docstrings (for any new functions)
[x] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Took the opportunity to simplify the buttons so that it is similar to find in files (start/stop are the same button)

Issue(s) Resolved

Depends on #11741
Fixes #12183
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @goanpeca

Hello @goanpeca! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/api/widgets.py:

Line 452:80: E501 line too long (82 > 79 characters)
Line 696:80: E501 line too long (85 > 79 characters)

In the file spyder/plugins/ipythonconsole/plugin.py:

Line 423:21: E222 multiple spaces after operator

In the file spyder/plugins/pylint/plugin.py:

Line 72:80: E501 line too long (81 > 79 characters)
Line 102:80: E501 line too long (81 > 79 characters)
Line 129:80: E501 line too long (80 > 79 characters)
Line 201:1: W293 blank line contains whitespace

In the file spyder/plugins/pylint/widgets/pylintgui.py:

Line 173:40: E261 at least two spaces before inline comment
Line 292:71: W291 trailing whitespace
Line 296:71: W291 trailing whitespace

/binder

Some comments about this PR:

The shortcut F8 is not working for running the code analysis
Clicking on an element in the pane (warning, error, message) doesn't go to the line corresponding to this element. However if I close the file and click the error message in the pane it opens the file (but again it doesn't go to the corresponding line) This was a bug that we found and it was fixed by @ccordoba12  in 4.1.4 so not sure why it is not working here. I tested it in 4x and it works fine.
The hamburger menu doesn't have the expand/collapse items that it had before.
When selecting a file in the pane with the "Select python file" button, the analysis doesn't run automatically which it did before. It does display the path of the file selected in the combobox but when pressing analyze, it runs the analysis on the file that is selected in the editor and displays the path of this last file in the combobox.
When reducing the width of the pane it is noticeable that there is some sort of "invisible" item between the analyze button and the hamburger menu button which shouldn't be there. In contrast, the combobox should take the full space when the width is less (as it did before in 4.x)

Hi @juanis2112, thanks for the review:

The shortcut F8 is not working for running the code analysis

I cannot reproduce this. On my Mac pressing Fn+F8 run the analysis as expected.

Clicking on an element in the pane (warning, error, message) doesn't go to the line corresponding to this element.

Fixed

The hamburger menu doesn't have the expand/collapse items that it had before.

Fixed

When selecting a file in the pane with the "Select python file" button, the analysis doesn't run automatically which it did before

Fixed

When reducing the width of the pane it is noticeable that there is some sort of "invisible" item between the analyze button

Fixed

more differences between 4.x and this PR:

Fixed.

/show binder

The shortcut F8 is not working for running the code analysis

This is still a problem on Linux and Windows. Please check it on a virtual machine.
All the other problems reported by @juanis2112 and I are solved now. Great job @goanpeca!

This is still a problem on Linux and Windows. Please check it on a virtual machine.

Could not reproduce but introduced a change that might help. Could you check @juanis2112, @ccordoba12 ?

Could not reproduce but introduced a change that might help.

It's working now. Thanks @goanpeca.
@dalthviz will give this one a final manual review and if he finds everything in order, he'll merge it.

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point):

This one is related to this PR, I will fix!
Thanks @dalthviz :-)

This error is also present in 4.1.4 so I will create an issue or maybe already one is open @ccordoba12 ?

Please open a new issue about this one. I don't remember seeing this reported yet.

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point):

@dalthviz I could not reproduce on Mac, will check on a Win VM and see if it is a windows thing only.

@goanpeca, please address this comment from @dalthviz:

While testing this I found some things but the only related with this PR is that seems like a min width is being set so is not possible to resize the window (it only allows you to resize up to certain point)

so we can merge it.

@dalthviz I could not reproduce on Mac, will check on a Win VM and see if it is a windows thing only.

I cannot reproduce this on the windows VM, any particular thing that might be triggering it?

@goanpeca after checking a little bit more seems like the strange behavior is related with the way the toolbars are being contracted (sometimes the resize gets stuck, although I don't now why):

Looking at the code seems like a custom handling is being implemented for the resizeEvent to emit a custom signal: https://github.com/spyder-ide/spyder/blob/a24398264e5cb5dbbb72fda6a35555fd08fb40a4/spyder/api/widgets/init.py#L540-L545. Maybe that could be causing the resize to get stuck?

Thanks for checking @dalthviz. Just to check is it associated to the speed in which you move?

Looking at the code seems like a custom handling is being implemented for the resizeEvent to emit a custom signal:

Correct, that change was needed to be able to have the toolbar items use as much area as possible.
Question: If you do it slowly it does not get stuck, but if you do it faster it does?

@dalthviz made some small changes to see if the situation improves.
Does increasing this number helps?
https://github.com/spyder-ide/spyder/pull/12160/files#diff-f34c043d56467c819418192611e89a6eR421

@goanpeca checked again and seems the problem is still there :/

Question: If you do it slowly it does not get stuck, but if you do it faster it does?

The behavior is the same

Does increasing this number helps?

I'm not sure what number is that, is an option?
From what I'm seeing seems like the resize signal is applying only for the first toolbar that isn't contracted from right to left. So, to contract the rest, you need to again start the resize action. Maybe this GIF illustrates that (first the working directory toolbar needs two resize events to contract - probably do the combobox - and then the rest of the toolbars need one resize event each):

From what I'm seeing seems like the resize signal is applying only for the first toolbar that isn't contracted from right to left. So, to contract the rest, you need to again start the resize action. Maybe this GIF illustrates that (first the working directory toolbar needs two resize events to contract - probably do the combobox - and then the rest of the toolbars need one resize event each)

Thanks @dalthviz, I understand what you mean. However the changes  I made refer to the toolbar in the Docks (each pane has now the options as a toolbar)

But it should now have any effect on the application toolbars. It seems like it is a separate issue. On master you see the same behavior?

Checking with master (3bf92535c) I don't see that behavior:

@dalthviz I cannot reproduce on any of the systems (binder linux) local mac and Win 10 VM. It is going to be really hard to try to fix something I cannot reproduce.
Could we add an item to https://github.com/spyder-ide/spyder/issues/13527 and move forward. Seems like a very minor issue to block this PR from merging.

Could we add an item to #13527 and move forward

I don't agree with this. Please set up a Zoom call with @dalthviz so they two of you can fix this issue.

@ccordoba12 the issue stems from trying to address this comment:

If I revert the "fix", then the problem is gone, but the "invisible" item is back.
That is a problem that affects all plugins that provide a widget inside the Pane (like the combobox in this case) and it deserves a fix that covers all widgets. It is not a problem specific to this Plugin, even if it was a comment that came out of reviewing it.

@dalthviz please create an event whenever it suits you. Available hours are visible on the company calendar.

I don't agree with this. Please set up a Zoom call with @dalthviz so the two of you can fix this issue.

Fair enough, but even if you do not agree with this, @dalthviz should be able to have also an opinion and a vote, after all the question was addressed to him.

@dalthviz please create an event whenever it suits you. My available hours are visible on my company calendar.

Ok :+1: done

@goanpeca please rebase this one to get the changes done in #13600

@goanpeca please rebase this one to get the changes done in #13600

Done @dalthviz.

/show binder

@goanpeca left a question and also I think this plugin should use the spinner. Besides that LGTM 👍

Thanks for the feedback @dalthviz, made the requested fix.

@andfoy @steff456 could you give to this PR a manual test on Linux and Mac? Thanks!

/show binder

Hi @goanpeca and @dalthviz,
With @andfoy we manually review this PR and everything is working as expected.

@goanpeca one last comment, please unify the use of " to enclose strings, there is a mix (as an example the pylint main_widget.py in the setup of the actions) and using just " could improve future readability of the code. Thanks!

Fixed @dalthviz.

Edit: Seems like the Analyze button always triggers the action using the current filename in the Editor

Bug!
Will fix.

Hey @dalthviz, is this one ready for merge?

@ccordoba12 I would say that some testing could be nice, otherwise the missing thing is a squash


[doc]Update Feedback & Suggestions from support

visit the documentation https://sprakash57.github.io/create-react-saga/#/support and edit the Feedback & Suggestions section with the below details -

Do you have any feedback/idea/suggestion to improve create-react-saga? Post them here https://github.com/sprakash57/create-react-saga/discussions

P.S - Please raise a PR against gh-pages branch.

I can do it

Hey, can I work on this issue? If anyone is not working on it?

I will tag people on a first come first serve basis. Since it's a hacktoberfest specific ticket I will assign them from 1st October onwards.

okay

@rajdama Hey, I have assigned it to you. Let me know if you are still interested in doing this. Otherwise I will give it to others.

@sprakash57  I am interested in doing this.

Hey @rajdama are you still working on it?

 Create React Saga v1.x

commit 115e45 takes care of it. Closing this!!


Plans for a release >2.3.1

Are there any plans for a new release?
Some annoying typing issues where fixed since last release https://github.com/graphql-python/graphql-core-legacy/compare/v2.3.1...master 4 months ago. For example, following error I'm getting with mypy==0.770 is already fixed, but awaits a release:
***: error: Argument "loop" to "AsyncioExecutor" has incompatible type "AbstractEventLoop"; expected "Optional[_UnixSelectorEventLoop]"

Version 2.3.2 with these fixes has been released now.


Writes into a single node log-cache are discarded when LocalOnly isn't set

We tried to write some logs into a single log-cache node. We didn't set LocalOnly and noticed that the logs were being discarded. This seems un-intuitive. It would be strange to expect clients to change the way they talk to log-cache based on knowledge of the cluster size.
cc/ @jasonkeene

This was deployed without a scheduler which is likely why everything was being discarded. Since we only had a single log-cache node we thought the scheduler wouldn't be needed.
This raises the following questions:

For small footprint environments where only a single log-cache node is being used, should we support deployments without a scheduler since the single node will always be the route for all logs?
For ease of use by developers and in testing environments that do not require HA, do we want to support a single node experience?

Thanks for the follow up. I think for now we are ok with the scheduler being deployed, even in Small Footprint configurations.


the best practice when executed sql script against test enviroment need to update?

Hi guys, i have a question about when a sql scripts execute successful against  test environment and have been recorded into flyway_schema_history table, but the developer or tester find something wrong with the sql scripts. they need to update or fix the sql scripts. what is the best practice to do it. we can not create a new version of sql scripts, because we don't want run the older version against production, it may break something.
so we need to update the sql scripts directly. but the thing is when I update the sql scripts , flyway will check the checksum of files, it will failed in the next execution. so what i have to do now is that:

Fix sql scripts on the old version directly.
2.Run "flyway repair" to generate new checksum value.

it means every time I need to fix or update sql scripts, i need do repair first.
so i want to know how you guys do this?

Hi! Updating the script and using repair to fix the checksums is the simplest and best way to do it. The only issue might be that you haven't actually run the script in its final form against the test environment, and that may be problematic for you if the changes made are risky.
You could also try:

write an undo script for each migration; if your script needs a fix then flyway undo to back it out and then flyway migrate again after you have fixed the script, or

take a database backup before the migration; if your script needs a fix then restore the backup and then migrate again after you have fixed the script (warning: only for environments where you don't mind data changes since the migration being lost).

@juliahayward yeah the problem is that when I fixed the sql scripts and run flyway migrate again.
it will not run the fixed scripts against test env. i have to do it manually.
for undo and backup, it's too complex for us. i wonder is there something that like R__ I can rerun the fixed sql scripts against test env when the V__ scripts updated.

That's a workable idea - turn the problematic V-script into an R-script while you're working on it, and then rename it back when you're ready to commit. This would require that you make the script idempotent (for example CREATE TABLE foo would have to be preceded by DROP TABLE IF EXISTS foo) but that's not a bad thing in itself; plus you'd need a certain amount of care not to introduce more V-scripts as the sequencing would potentially be wrong.


seafile-*: 4.0.6 -> 4.4.2

Duplicate of https://github.com/NixOS/nixpkgs/pull/10751 ?

Yeah, just a different travis fail. Patch works locally.

cc @matejc


fixed react-native-windows path definition

- About our project
In our project we use reactive-native-device-info and some other "Native" packages, and we provide automatic CI process for three platforms: IOS, Android and Windows UWP.
We had some difficulties with setting up CI for Windows UWP.
- Notice
Before describing the problem and solution, I want to warn you that I'm not a professional windows developer, and maybe my actions were not the most faithful.
- About problem
RNDeviceInfo requires a reference to the react-native-windows package. And there are two possible locations for the folder with a react-native-windows package:
First:
react-native-windows can be located in the node_modules folder in the most react-native-device-info, then in the file
react-native-device-info / windows / RNDeviceInfo / RNDeviceInfo.csproj on the line 116 of code should have such path
<ProjectReference Include="..\..\node_modules\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">
(The folder react-native-windows lies on two levels above and in the folder node_modules)
Second
The folder react-native-windows can be located next to the folder react-native-device-info in node_modules of another project (as in our case)
In this case, the path to the reactive-native-device-info / windows / RNDeviceInfo / RNDeviceInfo.csproj on the 116 line of code should have this path
<ProjectReference Include = ".. \ .. \ .. \ react-native-windows \ ReactWindows \ ReactNative \ ReactNative.csproj">
(The folder react-native-windows is three levels higher)
If we build our project using Visual Studio 2017, the process of restoring references to the dependency modules occurs (it's incomprehensible to me)
And path
. .\..\node_modules\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj
Automatically turns into
..\..\..\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj
And projects are going well!
But we use an automatic CI system based on the msbuild console utility from Microsoft
And although Visual Studio is based on msbuild, when assembling through it, there is no restoring of references (for two days of searching I have not found the answer why this works exactly the same way and how the mechanism for restoring links in the msbuild console starts)
- Solution
In the windows / RNDeviceInfo / RNDeviceInfo.csproj file, replace the root path of the variable
<ProjectReference Include="..\..\node_modules\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">
<ProjectReference Include="$(ReactWindowsRoot)\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">

And add a special condition for updating this route
< PropertyGroup >
  <ReactWindowsRoot>..\..\node_modules</ReactWindowsRoot>
</PropertyGroup>

<PropertyGroup Condition="Exists('..\..\..\react-native-windows')">
  <ReactWindowsRoot>..\..\..</ReactWindowsRoot>
</PropertyGroup>

This change guarantees us the correct path definition to react-native-windows
P.S. - and the build-reactive-native-device-info requires WinRTXamlToolkit because in the file windows / RNDeviceInfo / project.json, depending on which we wrote the line "WinRTXamlToolkit": "2.0.0"
P.S.S. - Thank you for a good package if you have ideas and how best to solve or bypass this problem I will be glad to discuss them

Hi @Hirurgo and thank you so much for taking the time to send this PR and the related explanations.
For starters, like you, I'm not a UWP developer, and in fact I just finished this morning setting up a Windows 10 to be able to maintain this library :)
Some members of the react-native-windows project are usually hanging out on Reactiflux in #react-native-platforms. Maybe you could join there and try to understand the issue you're facing.
From what I've read, you are correct, and we're missing an additional "../" in the path in the csproj file.
I'll test your PR as soon as I have a working environment for tests and will get back to you.
Meanwhile, could you please re-explain the addition of WinRTXamlToolkit to the .json file? I'm not sure I understood what was the problem with that.
By the way, if any other native packages you used, with a windows implementation, is publicly available, I'd really love to check them out.
Thank you again for reaching out!

By the way, I published 0.20.0 with more Windows support yesterday:
https://github.com/rebeccahughes/react-native-device-info/releases/tag/v0.20.0
Since you're the only one I know of with a production application running on UWP, would you mind giving it a try and tell me if I broke anything? It was my first attempt at C# 😅

I apologize for my long absence in solving this problem, as before with the current version of 0.22.3 I have the same error

@machour , I'm struggling with the same problem that the ReactNative.csproj file was not found.
Here's a package I'm using that is currently not giving any errors or trouble:
https://github.com/itinance/react-native-fs

@Brynjulf Thanks, for your comment, react-native-fs have fixed and correct path to react-native-windows
134 line from RNFS.csproj:
<ProjectReference Include="..\..\..\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">

@Hirurgo, @machour To follow up a bit more on the OP, WinRTXamlToolkit": "2.0.0 is something that visual studio complains about missing when attempting to build the solution. This is not necessary to reference if you instead upgrade TargetPlatformVersion (and TargetPlatformMinVersion) to 10.0.15063.0 and use the new way of referencing[1]. This would mean that you need to remove the project.json  and its reference inside RNDeviceInfo.csproj, this would also remove another error about uap mismatch generated from specifying the framework and runtimes inside the project.json.
Below is my entire patch file for running my project with react-native-device-info, it was generated using patch-package[2]. This patch enables builds in visual studio, terminal or remote (we're using vsts to deploy). It also works for debug, release and bundled release/debug.
patch-package
--- a/node_modules/react-native-device-info/windows/RNDeviceInfo/RNDeviceInfo.csproj
+++ b/node_modules/react-native-device-info/windows/RNDeviceInfo/RNDeviceInfo.csproj
@@ -11,11 +11,16 @@
     <AssemblyName>RNDeviceInfo</AssemblyName>
     <DefaultLanguage>en-US</DefaultLanguage>
     <TargetPlatformIdentifier>UAP</TargetPlatformIdentifier>
-    <TargetPlatformVersion>10.0.14393.0</TargetPlatformVersion>
-    <TargetPlatformMinVersion>10.0.10586.0</TargetPlatformMinVersion>
+    <TargetPlatformVersion>10.0.15063.0</TargetPlatformVersion>
+    <TargetPlatformMinVersion>10.0.15063.0</TargetPlatformMinVersion>
     <MinimumVisualStudioVersion>14</MinimumVisualStudioVersion>
     <FileAlignment>512</FileAlignment>
     <ProjectTypeGuids>{A5A43C5B-DE2A-4C0C-9213-0A381AF9435A};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</ProjectTypeGuids>
+    <ReactWindowsRoot>..\..\node_modules</ReactWindowsRoot>
+    <RestoreProjectStyle>PackageReference</RestoreProjectStyle>
+  </PropertyGroup>
+  <PropertyGroup Condition=" '$(Configuration)' != 'Development'">
+    <ReactWindowsRoot>..\..\..</ReactWindowsRoot>
   </PropertyGroup>
   <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
     <PlatformTarget>AnyCPU</PlatformTarget>
@@ -102,10 +107,6 @@
     <UseVSHostingProcess>false</UseVSHostingProcess>
     <ErrorReport>prompt</ErrorReport>
   </PropertyGroup>
-  <ItemGroup>
-    <!-- A reference to the entire .Net Framework and Windows SDK are automatically included -->
-    <None Include="project.json" />
-  </ItemGroup>
   <ItemGroup>
     <Compile Include="RNDeviceInfoPackage.cs" />
     <Compile Include="RNDeviceInfoModule.cs" />
@@ -113,11 +114,16 @@
     <EmbeddedResource Include="Properties\RNDeviceInfo.rd.xml" />
   </ItemGroup>
   <ItemGroup>
-    <ProjectReference Include="..\..\node_modules\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">
-      <Project>{c7673ad5-e3aa-468c-a5fd-fa38154e205c}</Project>
+    <ProjectReference Include="$(ReactWindowsRoot)\react-native-windows\ReactWindows\ReactNative\ReactNative.csproj">
+      <Project>{C7673AD5-E3AA-468C-A5FD-FA38154E205C}</Project>
       <Name>ReactNative</Name>
     </ProjectReference>
   </ItemGroup>
+  <ItemGroup>
+    <PackageReference Include="Microsoft.NETCore.UniversalWindowsPlatform">
+      <Version>6.1.7</Version>
+    </PackageReference>
+  </ItemGroup>
   <PropertyGroup Condition=" '$(VisualStudioVersion)' == '' or '$(VisualStudioVersion)' < '14.0' ">
     <VisualStudioVersion>14.0</VisualStudioVersion>
   </PropertyGroup>
deleted file mode 100644
--- a/node_modules/react-native-device-info/windows/RNDeviceInfo/project.json
+++ /dev/null
@@ -1,16 +0,0 @@
-{
-  "dependencies": {
-    "Microsoft.NETCore.UniversalWindowsPlatform": "5.2.2"
-  },
-  "frameworks": {
-    "uap10.0": {}
-  },
-  "runtimes": {
-    "win10-arm": {},
-    "win10-arm-aot": {},
-    "win10-x86": {},
-    "win10-x86-aot": {},
-    "win10-x64": {},
-    "win10-x64-aot": {}
-  }
-}
\ No newline at end of file

Visual studio is more forgiving when finding references, and i suspect it doesn't solely search for path reference but also project id when you've linked up dependencies. It would make sense given that you can still run failed builds (because of certain errors) from visual studio, but not from the terminal.
I hope this helps.
Reference:

https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files
https://github.com/ds300/patch-package

@Brynjulf - a fellow patch-package user, I love that package. Would you be willing to confirm if your patch is still in use by you and working? And that it is all that is necessary to resolve this issue?
If so, I'll copy it out to a diff and merge it in (or you could propose a PR and I'll merge it)

@mikehardy, it's an awesome package albeit a little rough when using it while changing OS'. We currently have 4 apps that are using the dynamic path patch.
I made a pull request for you  here

Closed in favor of #608


Documentation wrong on customizing tasks

The groovy and kotlin examples for configuring tasks are labeled backwards, the one labeled kotlin is groovy and vice versa.
Also for the kotlin example (incorrectly labeled as groovy) tasks.named is going to need a type parameter unless you are just using basic task properties like enabled.

Can you point which Kotlin example is labelled as Groovy? 🤔 By "configuring tasks" do you mean Customizing tasks, Custom tasks or Configuration?

Also for the kotlin example (incorrectly labeled as groovy) tasks.named is going to need a type parameter unless you are just using basic task properties like enabled.

I see 2 usages of named() and they are correctly labelled as Groovy. With Kotlin DSL you get computed extensions on tasks container which you can call as tasks.taskName {} which then exposes typed accessor 👀
Can you share which Kotlin DSL examples don't work for you?

I was referring to Customizing tasks. I could not get tasks.taskName { } to work and not sure how you could make that work in Kotlin.
Unfortunately, I was just trying to switch from our hand done ktlint invocation to one of the plugins, but I could not get any of them to filter worth a darn and could not exclude some generated and third party source code from being linted.

As far as groovy you don't need to use named, you can just do taskName { }

Actually, you shouldn't use taskName { } in Groovy as it configures the task eagerly and the lazy version with tasks.named('taskName') is the preferred way - docs. Kotlin DSL is smarter, and it calls named() under the hood, so you get build performance improvements unknowingly.
I tried the tasks.lintKotlinMain { } (as shown in the documentation) on the test-project and all seems to be working as expected:

you can even see the extension implementation I was referring to:

You probably want to verify you configured Kotlin DSL correctly and if you're configuring the right task 👀
I'd even say in most cases you want to configure all tasks, not just one, running for a particular soruceSet, so I'd guess that what you're actually looking for is:
tasks.withType<LintTask>().configureEach {
    experimentalRules.set(true) // or any other config
}

tasks.withType<FormatTask>().configureEach {
    experimentalRules.set(true) // or any other config
}

Thanks for the answers @mateuszkwiecinski and hopefully that worked for you @dalewking
Regarding:

Unfortunately, I was just trying to switch from our hand done ktlint invocation to one of the plugins, but I could not get any of them to filter worth a darn and could not exclude some generated and third party source code from being linted.

There are some good notes on how to do that here.
Because our tasks inherit from SourceTask, excludes are based on package root. So if you need to go above the package root to customize source paths to exclude you need to edit the source of the task -- which it brings in from the matching Kotlin compile task for the particular sourceSet you are changing:
tasks.named("lintKotlinMain") {
    source = source - fileTree("$buildDir/generated")
}
tasks.named("formatKotlinMain") {
    source = source - fileTree("$buildDir/generated")
}

In fact, really ought to update our docs to include that note on additional exclude styles 🤔

Tested and determined readme has correct syntax here.

so, in order to make Jeremy's code work, I had to explicitly cast this to LintTask so it would pick up the source value (using Gradle 7.6.1) - not sure why I had to do that and he did not.

Oh, interesting. I thought I tested it, but feel free to issue a PR against the Read.me if it needs a correction and you have the syntax working.

After reviewing @mateuszkwiecinski's post again, here's where I ended up:
   tasks.withType<LintTask> {
       this.source = this.source.minus(fileTree("src/generated")).asFileTree
   }

   tasks.withType<FormatTask> {
       this.source = this.source.minus(fileTree("src/generated")).asFileTree
   }

I had to do the final call to asFileTree because minus (or the operator) returns a FileCollection that has to be cast.


chore: fix build error after upgrade containernetworking/plugin

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
fix build error after upgrade containernetworking/plugin #782
Which issue(s) this PR fixes:

Fixes #812
Special notes for your reviewer

coverage: 80.775% (-0.08%) from 80.856%
when pulling 61b8aca42f306765410621c18a4b8c81a81dd397 on jwtty/fix-plugin
into 7bcf2d4c68a5b8bd5c3e62dd9b07f6a566e18da3 on main.


[Bug]Runtime error when using "-p" option

Info
dotenv-cli: 7.4.0
Steps to reproduce
Execute below command:
$  ENV_VALUE=dummy npx --package dotenv-cli dotenv -p ENV_VALUE

Behavior
# ENV_VALUE=dummy npx --package dotenv-cli dotenv -p ENV_VALUE
/Users/satsuta/.npm/_npx/075ae4738b5e8eb2/node_modules/dotenv-cli/cli.js:94
    value = `\`${value}\``
          ^

TypeError: Assignment to constant variable.
    at Object.<anonymous> (/Users/sa2taka/.npm/_npx/075ae4738b5e8eb2/node_modules/dotenv-cli/cli.js:94:11)

Reason
Following code seems to be attempting to overwrite the value defined by const, which seems to be causing an error.
ref: #105
const value = process.env[argv.p]
if (typeof value === 'string') {
  value = `\`${value}\``
}

Thanks.

I'm also seeing this since 7.4.0

Weird! That must have been the linter. I believe I had that as a let before o.o
I haven't checked to see if a PR was pushed up to fix it yet, but if not, I'll push up and additional PR to fix asap.

https://github.com/entropitor/dotenv-cli/releases/tag/v7.4.1


HEIC image support

Hi, I've been using this library for a while and it works really great, one thing that came up recently is to give HEIC image support, but when I try to load them, it cannot be done, it shows an error, it would be possible to add support for those images with this library?
Thanks.

Thanks for your suggestion @batusai513.
I've marked this as a feature request, but it's likely that I will only add this if the HEIC format (HEIF) is natively supported by browsers.
There is the following library that supports converting HEIC images to JPEG/PNG/GIF on the client-side:
https://github.com/alexcorvi/heic2any
Unfortunately the distribution file for heic2any is more than a Megabyte in size.
See also: https://github.com/blueimp/jQuery-File-Upload/issues/3645

You may be interested in https://github.com/exif-heic-js/exif-heic-js for reading HEIC EXIF metadata. It is a relatively small library.

Thanks for sharing @edent.
I think it's worth considering if reading HEIC EXIF metadata alone is worth it, but so far I still prefer to see if the format will get broad browser support first.

@blueimp do you support now heic files loading ? Would be really wonderfull

Not yet supported unfortunately.


remove umd copies of firmware header files

Copy of the issue from old open-umd  repo - https://yyz-gitlab.local.tenstorrent.com/tenstorrent/open-umd/-/issues/10

UMD is has copies of noc header files.  Instead, umd should require an include path that the clients (metal) specify to get to their copies of those files

This is a duplicate of multiple issues adressing this, closing it...


Handle OTLP StartTime (similar to OpenMetrics Created timestamp)

Proposal
The OTLP field StartTime / StartTimeUnixNano is described here.
If I understand correctly, under Cumulative Temporality it could be used exactly like the Created timestamp in #6541, to add a 0 at the beginning of a series and hence avoid losing the first increment in rate().
(The only place I could find OTLP StartTime mentioned was at https://github.com/prometheus/prometheus/issues/13192, although it is only there incidentally)

Related nuanse https://github.com/open-telemetry/opentelemetry-specification/issues/4184 with the current CT zero injection and rates.


NTR: Polaroplast

Please provide as much information as you can:

Suggested term label:

Polaroplast

Definition (free text)

The polaroplast is a specialized structure within microsporidian spores that plays a crucial role in the germination and infection process. It is composed of multiple layers of membranes that swell during spore activation, contributing to the build-up of pressure inside the spore. This pressure is essential for the expulsion of the polar tube and the delivery of the sporoplasm into the host cell.

Reference, in format PMID:#######
DOI:10.1111/j.1462-5822.2009.01362.x
DOI:10.1016/j.ijpara.2005.04.003

Gene product name and ID to be annotated to this term

Parent term(s)

GO: 0110165

Children terms (if applicable) Should any existing terms that should be moved underneath this new proposed term?

Synonyms (please specify, EXACT, BROAD, NARROW or RELATED)

Cross-references

For enzymes, please provide RHEA and/or EC numbers.

Can also provide MetaCyc, KEGG, Wikipedia, and other links.

https://en.wiktionary.org/wiki/polaroplast

Any other information

+[Term]
+id: GO:0160201
+name: polaroplast
+namespace: cellular_component
+def: "A membrane-bounded organelle found in a microsporidian spore,  that swells with water, and exerts pressure to rupture the polar cap and evert the polar tube through which the sporoplasm escapes to infect the host." [PMID:16005007, PMID:19673893, Wikipedia:polaroplast]
+is_a: GO:0043231 ! intracellular membrane-bounded organelle
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/28569" xsd:string
+created_by: rynl
+creation_date: 2024-07-25T22:10:47Z

Thanks @raymond91125! Do you know when this will be available?

@uermel It is available from GitHub GO project download. But I don't know how long it may take your curation tool to get the update. Sorry.

No worries, thanks again. We're using purl.obolibrary.org to link out, that's what I was referring to.

@cmungall Does purl.obolibrary.org  consume data from the GO release? How does that work ?

I just got off a call with @uermel, we're all clear, but just for references, the OBO PURLs are just redirects, there is no separate ingests


⚠ Bofrost.at has degraded performance

In e5c12b2, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1762 ms

Resolved: Bofrost.at performance has improved in 4d7e9e8.


Inconsistent rest search request with command line usage

When creating, indexing and serving, we always refer to an index by its URI.
But for querying on the rest API, we need to pass the index id as a path param like this ``.
This is not really consistent. We can either:

put the index uri in the query and not use the index id
be more explicit in the documentation of what we are doing with an index uri: metastore uri + index id

I vote for the second.

I vote for the second too.

done in #263


Move to blind quicker using MAX_BLINDS_ON_REMOTE

After adding MAX_BLINDS_ON_REMOTE I can now use very simple algorithm to move to a different number quicker.
Example:
from 9th blind to 1st
previously 8 times command "down"
now 2 times command "up"
Also renamed 2 functions.
Long description:
In my setup I use different number of blinds. I only have 9 blinds for now so on my remote there is only 10 blind numbers allowed and I use 10th as blind to synchronize- if sent command to that number - nothing happens.
When making a copy of pwrozycki setup I discovered a couple of small improvements. This is a first one.
On the Mobilus remote the channels numbers rotate, i.e. when last blind is reached (default 99) and button "up" is pressed again - then next blind channel number is 1. It goes both ways- when channel 1 is selected- the button "down" moves to the last available blind channel- by default it's 99, in pwrozycki setup it's 22, in my setup it's 10.
Moving to the the blind channel that is requested in mqtt message was already fast, but before in case user was on channel 1 and wanted to move to channel 99- button "up" had to be pressed 98 times. Now, in the same scenario- button "down" will be pressed only once.
That way moving to the requested blind will happen even faster.

Thanks for your PR. I wasn't expecting that someone will find this project useful ... apart from me ;-)
It is certainly a good idea to cycle in reverse direction if it is more optimal to do so.
I merged your commit but needed to make some adaptations so that it also works correctly if MAX_BLINDS_ON_REMOTE != 22.
I left original method name for displayEquals22 and changed markSynchronizedIfBlind20Reached to markSynchronizedIfBlind22Reached, because 22 is really the spot where synchronization occurs ("c" segments are turned off on both LCD displays), so 22 in the name is adequate.
I changed value of MAX_BLINDS_ON_REMOTE = 99, because this is the default setting of COSMO remote, even though I use MAX_BLINDS_ON_REMOTE == 30 in my setup.

@pwrozycki you're welcome. I will have another one but I still need to clean that up a bit.
I'm a huge fan of what you did here. When I bought the blinds I was surprised how bad the situation was when it comes to automation. I'm sure working out the hardware would take me a lot of time and with your work - I could just start using it.
Talk to you soon when I will have a second PR ready 😄


Neural Architecture Search

Is there any chance to be able to implement a self made Neural Architecture Search (RNN part) one day ?
Because looking at Keras' limitations (https://github.com/fchollet/keras/issues/4112) it seems that it will not be possible for a very long time.
Regards.

I have a more or less working implementation which fuses Keras to build the generator models and Tensorflow directly to train the RNN Controller.
https://github.com/titu1994/neural-architecture-search
I can't guarantee strict adherence to the original papers though.


Using pack gives error with apply.sh

Adding 1/1 app layer(s)
ERROR: failed to export: creating launcher layers: failed to stat launcher at path '/cnb/lifecycle/launcher'
ERROR: failed to build: executing lifecycle: failed with status code: 62

latest: Pulling from cf-build-service-public/ci/kpack-builder
Digest: sha256:14125235875ada6ffc67d37b86b1ce187c457fae7f130de6be5c2dc94420dc2c

pack version 0.22.0
root@227dfb312b02:/cnb# ls -la
total 24
drwxr-xr-x 1 root root 4096 Nov 23 14:49 .
drwxr-xr-x 1 root root 4096 Nov 23 14:58 ..
drwxr-xr-x 1 root root 4096 Nov 23 14:49 buildpacks
drw------- 2 root root 4096 Nov 23 14:48 lifecycle
-rw-r--r-- 1 root root  456 Jan  1  1980 order.toml
-rw-r--r-- 1 root root  156 Jan  1  1980 stack.toml
root@227dfb312b02:/cnb# cd lifecycle/
root@227dfb312b02:/cnb/lifecycle# ls -la
total 13552
drw------- 2 root root     4096 Nov 23 14:48 .
drwxr-xr-x 1 root root     4096 Nov 23 14:49 ..
lrwxrwxrwx 1 root root        9 Jan  1  1980 analyzer -> lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 builder -> lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 creator -> lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 detector -> lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 exporter -> lifecycle
-rwxr-xr-x 1 root root  2514944 Jan  1  1980 launcher
-rwxr-xr-x 1 root root 11350216 Jan  1  1980 lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 rebaser -> lifecycle
lrwxrwxrwx 1 root root        9 Jan  1  1980 restorer -> lifecycle
root@227dfb312b02:/cnb/lifecycle#

It seems to happen during export since the /cnb/lifecycle permissions look incorrect.
docker version
Client:
 Version:           20.10.7+azure
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        f0df35096d5f5e6b559b42c7fde6c65a2909f7c5
 Built:             Mon May 31 09:40:07 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server:
 Engine:
  Version:          20.10.7+azure
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.13.15
  Git commit:       b0f5bc36fea9dfb9672e1e9b1278ebab797b9ee0
  Built:            Tue Jun  1 22:34:42 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.9+azure
  GitCommit:        e25210fe30a0a703442421b0f60afac609f950a3
 runc:
  Version:          1.0.1
  GitCommit:        4144b63817ebcc5b358fc2c8ef95f7cddd709aa7
 docker-init:
  Version:          0.19.0
  GitCommit:

I believe this is an issue with the kpack deployment that is creating the kpack-builder having an outdated lifecycle. I will update this issue when the builder is updated with https://github.com/pivotal/kpack/pull/870.

This should now be resolved.


Problems installing HEIC/HEIF support

I tried to install HEIC/HEIF support using the instructions here, but after running for about 15 minutes on a rPi 4 (8gb) ended up with the message fatal: unable to access 'https://github.com/libffi/libffi.git/' Could not resolve host: github.com  (Strange error because I don’t have any problem with that link when I enter it into a browser.  )
Only the libde265  and libheif directories were created (both in /home/pi/picframe_data/config).
I realized that I may have run the command from the wrong directory, so I changed to /home/pi and tried again.  I got a very similar error after 15 minutes or so, but this time, only the libde265  directory was created:
fatal: unable to access 'https://github.com/strukturag/libheif.git/': Could not resolve host: github.com
Do you have any idea what may be going on?  Or how to “uninstall” what I’ve already installed?  (Can I just remove the new directories?)
I've attached the terminal log in case it helps.
heic log.txt

I can't tell, what went wrong. But you can try to complete the rest step by step.
start with git clone https://github.com/strukturag/libheif.git

Step by step seemed to work!  Now when I run picframe -v, it shows pyheif 0.5.1 as an installed optional package.
My successful installation is in /home/pi.  Earlier, I had an aborted install in /home/pi/picframe_data/config, so there are libde265  and libheif  subdirectories there.  To clean up, can I just remove those directories or is there something else I need to do?

Good to hear. I think you can can delete everything under /home/pi related to your libheif istalltions. Those are only source code folders which were used to build the required libs. After installation they should be copied under /usr/lib or should exist in the python site packages.

All seems good, so I'm closing this issue.  Many thanks!


Add support for windows 10 mail/Outlook

This adds support into the default template for M$ based email clients e.g Windows 10 Mail and Outlook.
 His PR may not work, but your PR is not perfect either.
Three things are missing:

Regeneration of examples (see https://github.com/matcornic/hermes/blob/master/CONTRIBUTING.md#creating-a-built-in-theme)
Flat theme has not been modified
https://github.com/matcornic/hermes/blob/master/CONTRIBUTING.md has not been modified (section https://github.com/matcornic/hermes/blob/master/CONTRIBUTING.md#action-injection)

Normally, I will take charge of these 3 steps this evening by improving main.go (apart from generating emails, i will provide running examples to send emails with go-mail)
Your PR (and others) are welcomed, but please don't be toxic.

I know mine is not perfect, I've ignored the too long lines error above as having that in single line might be important for Outlook however I didn't try it.
Now for the flat theme I'm not using it and I've tested this with live emails :P so that's the reason.
I don't know what you mean by pt 3. unless that's supposed to be a part of pt. 2

@mvrhov It's about the action section. It explains to users who want to create new theme how to implement the "action button". We should update snippet code (and document that Outlook has some specific thing todo)
Thanks your your answer :)

Actually, @mvrhov I need your help for the flat theme 😸 . I have Outlook on Mac, but it's not the same engine than Windows version (it's Webkit for Mac Outlook). So I cannot reproduce in a real environment 😞
Could you implement it ?
Flat theme:

No round corner
Button takes all width (if possible with VML)

In the meantime, I will push this evening the main.go I was working on, on master. So you can test all examples in one click.

@matcornic master is updated with examples ;)

So, is there a fix for the Windows 10/Outlook issue?

@forensicsguy20012004 could you test this PR with Windows Outlook ?

Hello @matcornic , i'm currently facing the same issue on windows 10 / Outllook with hermes v2.0.2
How can i help ?

Hey @vjeantet, can you test this PR for Windows 10 Outlook ? That would be nice :)

KO with windows10 / outlook 2016.
logo is very very large... and the action button appears but without background color.

Before this pull request: https://litmus.com/pub/376b1f9
After this pull request: https://litmus.com/pub/3a9ba94

Hello @matcornic @mvrhov any updates on this? I happens to had this issue recently.

Any updates?


Fixed a bug in vmi creation

Signed-off-by: Dana Orr<EMAIL_ADDRESS>
📝 Description
Fixed a bug in vmi creation
🎥 Demo

/lgtm

/retest


customize drift-detection-manager deployment

Feature implemented here
Add a section with examples explaining how to patch drift-detection-manager

https://github.com/projectsveltos/sveltos/pull/320


Feat: added support for rego files to filter input messages

Issue #175

@DmitriyLewen
Coverage of patch isn't very well. It needs to be improved


Add multi-arch binary build capability

This commit adds a new target for
building multi-arch preflight
binaries:

make build_multi_arch

Signed-off-by: Rafael Peria de Sene<EMAIL_ADDRESS>

@samira-barouti @bcrochet could you take a look on this one?

Why all the '@'? That is doing more in this patch than just adding multiarch support. Can you limit the changes to just what is necessary for adding multiarch?

@bcrochet the @ is to avoid printing the command when running make. I removed it from the parts I didn't touch for multi-arch.

@bcrochet the @ is to avoid printing the command when running make. I removed it from the parts I didn't touch for multi-arch.

I am curious as to why that would be desirable? Honest question. When running make, I personally would prefer to see the progress and what is being run, especially if there are variables involved.


Add metadata section, support constant and metadata in parser & printer

relax.const support in parser and printer, parse for ast.ArrayLiteral
metadata section support in printer and parser, support ir_moduel(metadata=json_str) as @junrushao1994 proposed.

@YuchenJin @ZihengJiang @hypercubestart

Is the PR has any problem? Constant printing and parsing are very important. So could we merge it as soon as possible?

Is the PR has any problem? Constant printing and parsing are very important. So could we merge it as soon as possible?

Thanks Siyuan! I got several comments from Yuchen, and will update it accordingly shortly. Would be good if you take a look at this pr.

@yongwww  Thanks for the great work!
I am not sure about the current metadata text format design as we argued in the review comments.
Even we make the show_meta_data=False by default, it seems still not that good to have a very long meta data section at the beginning of text format. Imaging that user want to print the relax model first, edit it and load it back, this design means he have to scroll down every time when he want to view/edit it.
I can understand that this design is because we would like to make it can be executed with Python directly, so the metadata need to be declared at the beginning. One thought from me is we could leave the meta_data as a required argument for the Module so that we can feed it later.

Hi Ziheng @ZihengJiang, thanks for the comment and suggestion! I agree that scrolling down to the bottom to see the program might be inconvenient if show_meta_data=True.  For the purpose of viewing program I would recommend specifying show_meta_data=False to avoid printing the meta out. It is kind of a design trade off. Personally I still prefer printing the meta in the beginning of the text, since then we can directly copy paste the text into python code without extra modification/hacking.
If we change irmodule to accept meta_data later, we would run into errors since the parsing for the ir_module/function happens in the decorators (e.g, @R.ir_module), during the parsing for the ir_module, once we meet something like meta[relay.Constant][0] we need to fetch it from metadata section there, which is not fed yet for this change.  And we also need to do the similar change to function as well since a single relax function could have big constant (therefore meta generated) as well.
How do you thinks?

Ok, let's take this way and see whether we can improve it in the future

Thanks @yongwww for the great work, and @Hzfengsy and @ZihengJiang for the reviews!


Fix bug on allNamespace-view: removing, creating & editing of resources

Description
Changes proposed in this pull request:

Fixed removing & editing of resources by providing correct URL of resource
...
...

Related issue(s)

/retest

/woof

/retest


Use JET.jl to Look for Type Warnings

I already found some spurious allocations due to an accidental Any return type

Did, found nothing :)


Screen naming

Changes Screen.width and Screen.height to Screen.windowWidth and Screen.windowHeight to clear up their roles.
Changes ContainerScreen.containerWidth (and respective height) to ContainerScreen.width to remove redundancy.

Out of curiosity, is that "scaled" size or the actual (client) window size?
May I suggest screenWidth if the former, and windowWidth or clientWidth if the latter?

Screen.width and Screen.height are scaled. As far as I can tell they are equal to your window width or height / GUI scale. I would also prefer Screen.screenWidth rather than Screen.windowWidth.

Out of curiosity, is windowWidth the "scaled" size or the actual (client) window size?
May I suggest screenWidth if the former, and windowWidth or clientWidth if the latter?

My original proposal was scaledWindow....
But screen... really sounds better - Changed it.  😉


Update Cargo.lock for Rust 1.56.0

This is the result of running cargo update with Rust 1.56.0.
Fixes #670.

Ups, running cargo test gives me
error: package `clap v3.2.25` cannot be built because it requires rustc 1.56.1 or newer, while the currently active rustc version is 1.56.0

After that I get:
error: package `rayon-core v1.11.0` cannot be built because it requires rustc 1.59 or newer, while the currently active rustc version is 1.56.1

and finally
error: package `log v0.4.19` cannot be built because it requires rustc 1.60.0 or newer, while the currently active rustc version is 1.59.0

So I guess the MSRV should be bumped to 1.60 now.

Perfect, merged. Thanks!


Re-enable now-passing 'Reflection/typeref_decoding.swift'

We are now seeing this test UPASS in various Linux aarch64 package bots.
e.g. https://ci.swift.org/job/oss-swift-package-ubuntu-20_04-aarch64/1837/

@swift-ci smoke test


not working when integrated with WP Plugin

i have integrated swiftmailer with a plugin i have made which is called using POST and adding a route to WP , the plugin works perfectly , however the Swiftmailer doesn't , as i call it from inside a function of a class but the $message->toString(), but $mailer->send() always returns 0 not matter what the email is , i have made sure that the swiftmailer loaded correctly and there is no error or not found file at all, but when i loaded swiftmailer alone as a separate plugin it works and it seems like the problem at this part :

my plugin index has to call a request handler to handle requests for the website at this link : example.com/someRoute with this action hook :
add_action('parse_request', array( 'RequestsHandler', 'processRequests' ));

the requests handler calls a datahandler which calls swiftmail inside a fuction with this code :
public function sendEmails()
{
$this->prepareRequestDataToSendEmail();
require_once plugin_dir_path(plugin_dir_path(FILE)) . 'senders/swiftmailer/swift_required.php';
$transport = Swift_MailTransport::newInstance();
$mailer = Swift_Mailer::newInstance($transport);
$message = Swift_Message::newInstance();
$message->setSubject($this->senderSubject);
$message->setFrom(array($this->senderFromEmail => $this->senderFromName));
$message ->setTo(array($this->senderReceiverEmail));
$message ->setBody($this->senderContent, 'text/html');
echo $message->toString();
echo $result = $mailer->send($message, $failures) ;
var_dump( $failures );
}

What is your os ?  Do you have a mail server available ?  Does the mail()
function work on your system ?  What is the php version ?
Thanx
Le jeu. 31 déc. 2015 20:44, heshamfathi<EMAIL_ADDRESS>a écrit :

i have integrated swiftmailer with a plugin i have made which is called
using POST and adding a route to WP , the plugin works perfectly , however
the Swiftmailer doesn't , as i call it from inside a function of a class
but the $message->toString(), but $mailer->send() always returns 0 not
matter what the email is , i have made sure that the swiftmailer loaded
correctly and there is no error or not found file at all, but when i loaded
swiftmailer alone as a separate plugin it works and it seems like the
problem at this part :
1 my plugin index has to call a request handler to handle requests for the
website at this link : examplecom/someRoute with this action hook :
add_action('parse_request', array( 'RequestsHandler', 'processRequests' ));
the requests handler calls a datahandler which calls swiftmail inside a
fuction with this code :
public function sendEmails()
{
$this->prepareRequestDataToSendEmail();
require_once plugin_dir_path(plugin_dir_path(FILE))
'senders/swiftmailer/swift_requiredphp';
$transport = Swift_MailTransport::newInstance();
$mailer = Swift_Mailer::newInstance($transport);
$message = Swift_Message::newInstance();
$message->setSubject($this->senderSubject);
$message->setFrom(array($this->senderFromEmail => $this->senderFromName));
$message ->setTo(array($this->senderReceiverEmail));
$message ->setBody($this->senderContent, 'text/html');
echo $message->toString();
echo $result = $mailer->send($message, $failures) ;
var_dump( $failures );
}
—
Reply to this email directly or view it on GitHub
https://github.com/swiftmailer/swiftmailer/issues/709.

What is your os ?  Do you have a mail server available ?  Does the mail()
function work on your system ?  What is the php version ?
Thanx
Le jeu. 31 déc. 2015 20:44, heshamfathi<EMAIL_ADDRESS>a écrit :

i have integrated swiftmailer with a plugin i have made which is called
using POST and adding a route to WP , the plugin works perfectly , however
the Swiftmailer doesn't , as i call it from inside a function of a class
but the $message->toString(), but $mailer->send() always returns 0 not
matter what the email is , i have made sure that the swiftmailer loaded
correctly and there is no error or not found file at all, but when i loaded
swiftmailer alone as a separate plugin it works and it seems like the
problem at this part :
1 my plugin index has to call a request handler to handle requests for the
website at this link : examplecom/someRoute with this action hook :
add_action('parse_request', array( 'RequestsHandler', 'processRequests' ));
the requests handler calls a datahandler which calls swiftmail inside a
fuction with this code :
public function sendEmails()
{
$this->prepareRequestDataToSendEmail();
require_once plugin_dir_path(plugin_dir_path(FILE))
'senders/swiftmailer/swift_requiredphp';
$transport = Swift_MailTransport::newInstance();
$mailer = Swift_Mailer::newInstance($transport);
$message = Swift_Message::newInstance();
$message->setSubject($this->senderSubject);
$message->setFrom(array($this->senderFromEmail => $this->senderFromName));
$message ->setTo(array($this->senderReceiverEmail));
$message ->setBody($this->senderContent, 'text/html');
echo $message->toString();
echo $result = $mailer->send($message, $failures) ;
var_dump( $failures );
}
—
Reply to this email directly or view it on GitHub
https://github.com/swiftmailer/swiftmailer/issues/709.

Issues Fixed , it was a server error, i found a php.ini file in the folder however it had only the config for showing errors but when i deleted it everything worked, the thin is swiftmailer worked even when this file was there but not inside the wp plugin , anyway it works now

Issues Fixed , it was a server error, i found a php.ini file in the folder however it had only the config for showing errors but when i deleted it everything worked, the thin is swiftmailer worked even when this file was there but not inside the wp plugin , anyway it works now


Can someone explain what's difference between this plugin and influx and backlink?

Thank you very much

I think they are helping with the same problem but with different approaches. I would suggest trying both and see which approach is appealing to you (Or even both).


Adding pod priority for all the components.

This PR is to add system level pod priority classes, to all the components that are installed using kubespray.

ci check this

/assign @chadswen

/approve
/lgtm