Update stick.js

Only a single byte was used for the x and y positions of the analog sticks, which caused it to work improperly. I've made it so both 2 bytes per position of the analog sticks are used and reduced to a value between -2 and 2, where 0 is the neutral position. I've also included a dead zone (currently set to 0.75), to prevent hypersensitivity of the analog sticks.
I recommend finding a way to return the values set to the sticks in some way when for example xbox.on('leftstickUp') is called.

Thank you so much for the contribution @Gyohdon . Fix the  high sensitivity is a great improvement in the api. I'm in my job right now and don't  have how to test it. I'll do it when I get home.

I've tested your changes and it broke the linux implementation. It will be necessary adjust the linux part to the propose low sensitivity alteration.


examples removed

django examples, examples, sample folders have been removed.
will be shifted to ftd-django-app

@Heulitig Add these files to ftd-django-app and please create the documentation PR as well. Because you have moved django examples to different repo, so need to update docs how to do local setup.
Docs


Secure ASP.NET Core Web API using API Key Authentication

Hi, instead of generate token by authenticate using email and password.  Any idea how to implement API Key with in your clean architecture?

Hi,
I added the API Key for the JWT token example. If you are using the theme while developing a monolith application, you will need Login/Register. If you are using it for microservice architectures, Login will not be needed. You can use the proper external token directly.
Here's what I plan to add and change in the future

I plan to remove Identity Server. Change IS4 to openiddict or add manually
Client.WorkerService project to Blazor WebUI

Ok great, solved my issues. I use the redis so I can terminate the token anytime.


add waf.NewTransactionWithID

waf.NewTransactionWithID(ctx, id) can be used by connectors to use the web server ID instead of coraza generated IDs. Useful for logging.

Codecov Report
Base: 73.22% // Head: 73.22% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (ffd2a52) compared to base (61ecf72).
Patch coverage: 75.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           v3/dev     #455      +/-   ##
==========================================
- Coverage   73.22%   73.22%   -0.01%
==========================================
  Files         143      143
  Lines        6588     6595       +7
==========================================
+ Hits         4824     4829       +5
- Misses       1488     1490       +2
  Partials      276      276

Flag
Coverage Δ

no-tinygo
73.27% <75.00%> (-0.01%)
:arrow_down:

overall
73.22% <75.00%> (-0.01%)
:arrow_down:

tinygo
72.16% <75.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

waf.go
44.06% <0.00%> (-1.55%)
:arrow_down:

internal/corazawaf/waf.go
96.41% <100.00%> (+0.05%)
:arrow_up:

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

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


get_comment_count returns comments+trackpack+pingbacks but post.comments only comments

Expected behavior
{{ post.get_comment_count }} should return only comments count without trackpacks and pingbacks
because post.comments return only comments
Actual behavior
post.comments return only post comments
Steps to reproduce behavior
Add trackbacks and pingback, render {{ dd(post.comments) }}
What version of WordPress, PHP and Timber are you using?
WordPress  5.5.1
PHP 7.2,
Timber 1.18.0
How did you install Timber? (for example, from GitHub, Composer/Packagist, WP.org?)
WP.org

Thanks for this info @errand! I'll investigate and follow-up

@errand I realize that I'm really jammed between (regular) work and getting 2.x wrapped up. In case you're interested, I want to give you first crack at the PR opportunity here!

@jarednova I was checking the get_comment_count and is using the native get_comments_number of wp

@jarednova I was checking the get_comment_count and is using the native get_comments_number of wp

This is fixed in 2.0 with the new Timber\Post::comment_count. Closing this since we are not going to actively maintain 1.x

@errand I realize that I'm really jammed between (regular) work and getting 2.x wrapped up. In case you're interested, I want to give you first crack at the PR opportunity here!

OMG man! I just saw your comment thanx to @Levdbas ! Of course let's close it.


Support sending telemetry periodically

Codecov Report

Merging #185 into master will increase coverage by 0.73%.
The diff coverage is 61.53%.

@@             Coverage Diff              @@
##             master     #185      +/-   ##
============================================
+ Coverage     53.92%   54.65%   +0.73%
- Complexity      217      222       +5
============================================
  Files            74       75       +1
  Lines           879      891      +12
  Branches         53       53
============================================
+ Hits            474      487      +13
- Misses          365      367       +2
+ Partials         40       37       -3

Impacted Files
Coverage Δ
Complexity Δ

...der/config/ServiceBusTopicBinderConfiguration.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...eam/binder/config/EventHubBinderConfiguration.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...igure/eventhub/AzureEventHubAutoConfiguration.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...osmosdb/AzureCosmosDbMongoDbAutoConfiguration.java
100% <100%> (ø)
3 <1> (+1)
:arrow_up:

...onfigure/telemetry/TelemetryAutoConfiguration.java
50% <100%> (+5.55%)
3 <1> (ø)
:arrow_down:

...vicebus/AzureServiceBusTopicAutoConfiguration.java
100% <100%> (ø)
4 <1> (ø)
:arrow_down:

.../eventhub/AzureEventHubKafkaAutoConfiguration.java
18.75% <100%> (ø)
2 <1> (ø)
:arrow_down:

...d/autoconfigure/sql/AzureSqlAutoConfiguration.java
100% <100%> (ø)
2 <1> (+1)
:arrow_up:

...nfigure/storage/AzureStorageAutoConfiguration.java
36.36% <100%> (+16.36%)
3 <1> (+1)
:arrow_up:

...toconfigure/cache/AzureRedisAutoConfiguration.java
57.89% <100%> (ø)
3 <1> (ø)
:arrow_down:

... and 7 more

Continue to review full report at Codecov.

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


Quarterly Report and Emission Intensity Report status on the task list are linked[6]

Describe the Bug:
Quarterly report status and errors on the task list are in sync with the Emission Intensity Report; So all statuses on the task list for the Quarterly report will be the same for the Emission Intensity Report.
Probability (how likely the bug is to happen, scored from 1-5):5
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5):1
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Create a new project => open task list header for the quarterly report and the emission intensity report  => add a new quarterly report and see changes on both task list statuses.
Note: raising errors on the quarterly report will show up on the emission intensity report too.
Screenshots:
https://www.loom.com/share/ef45ae5285ca402db8c4197e44a9cb96
Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context

Thank you @BCerki! I can't recreate the bug based on the above steps :)


Implement destroy logic

Add destroy method for playback, plugins, container, core, media control and player.

 Player tocando em Background #16


fix 500 error when view an issue which's milestone deleted (#2297)

back port from #2297

LGTM

LGTM

Make L-G-T-M work


Failed account syncing spams the logs

If syncing an account with a host fails, it is retried infinitely with 60-70s intervals, spamming the logs with errors:
2023-05-23T15:41:00+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:d120301e656596b5572707d004d8d2e8d6276257786b14dbb7a604671bd0e229", "host": "ed25519:85510c2f465dabddefe9c9983e87b2ed4f059e689b84e2161e91ad8b62cc308a"}
2023-05-23T15:42:10+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:a8d4b432dfc29dc253cc0a6943cf21628b1a478a8664b994114232ed080bf139", "host": "ed25519:d6da8e55eb65522b32ab5188d709fc80dbba6ee5daa79576f2e14b8d12c15d3c"}
2023-05-23T15:42:10+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:d120301e656596b5572707d004d8d2e8d6276257786b14dbb7a604671bd0e229", "host": "ed25519:85510c2f465dabddefe9c9983e87b2ed4f059e689b84e2161e91ad8b62cc308a"}
2023-05-23T15:43:20+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:a8d4b432dfc29dc253cc0a6943cf21628b1a478a8664b994114232ed080bf139", "host": "ed25519:d6da8e55eb65522b32ab5188d709fc80dbba6ee5daa79576f2e14b8d12c15d3c"}
2023-05-23T15:43:20+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:d120301e656596b5572707d004d8d2e8d6276257786b14dbb7a604671bd0e229", "host": "ed25519:85510c2f465dabddefe9c9983e87b2ed4f059e689b84e2161e91ad8b62cc308a"}
2023-05-23T15:44:30+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:a8d4b432dfc29dc253cc0a6943cf21628b1a478a8664b994114232ed080bf139", "host": "ed25519:d6da8e55eb65522b32ab5188d709fc80dbba6ee5daa79576f2e14b8d12c15d3c"}
2023-05-23T15:44:30+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:d120301e656596b5572707d004d8d2e8d6276257786b14dbb7a604671bd0e229", "host": "ed25519:85510c2f465dabddefe9c9983e87b2ed4f059e689b84e2161e91ad8b62cc308a"}
2023-05-23T15:45:40+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:d120301e656596b5572707d004d8d2e8d6276257786b14dbb7a604671bd0e229", "host": "ed25519:85510c2f465dabddefe9c9983e87b2ed4f059e689b84e2161e91ad8b62cc308a"}
2023-05-23T15:45:40+02:00	ERROR	autopilot.accounts	autopilot/accounts.go:202	failed to sync account's balance: Post "http://<IP_ADDRESS>:9980/api/worker/rhp/sync": context deadline exceeded	{"account": "ed25519:a8d4b432dfc29dc253cc0a6943cf21628b1a478a8664b994114232ed080bf139", "host": "ed25519:d6da8e55eb65522b32ab5188d709fc80dbba6ee5daa79576f2e14b8d12c15d3c"}```

We have recently discovered a bug which causes syncs to fail. Once we have a fix this should be resolved.
These errors are only printed for contract set hosts since it's quite critical that we are aware of these hosts having EA issues.

Closing this for now since it seems like our recent fixes stopped the spam.


Require instance-storage 6.0

Align alternativeTitles in test samples

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


1823825 | Message fixes | Address validation issues | 52

This PR is for user story 1823825.
Fixed an issue with missing alt text descriptions.
If these changes are not appropriate, please let me know. I'm only trying to clean up validation issues in this repo. So I can easily close this PR or modify it in whatever way is best for the content.

Docs Build status updates of commit edfd86c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

technical-reference/issoticket-members.md
:white_check_mark:Succeeded
View

technical-reference/issoticket-methods.md
:white_check_mark:Succeeded
View

technical-reference/iteration-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/less-than-functoid.md
:white_check_mark:Succeeded
View

technical-reference/less-than-or-equal-to-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-and-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-date-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-existence-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-functoids-reference.md
:white_check_mark:Succeeded
View

technical-reference/logical-numeric-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-or-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-string-functoid.md
:white_check_mark:Succeeded
View

technical-reference/looping-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/lowercase-functoid.md
:white_check_mark:Succeeded
View

technical-reference/mass-copy-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/mathematical-functoids-reference.md
:white_check_mark:Succeeded
View

technical-reference/maximum-value-functoid.md
:white_check_mark:Succeeded
View

technical-reference/minimum-value-functoid.md
:white_check_mark:Succeeded
View

technical-reference/modulo-functoid.md
:white_check_mark:Succeeded
View

technical-reference/multiplication-functoid.md
:white_check_mark:Succeeded
View

technical-reference/natural-exponential-functoid.md
:white_check_mark:Succeeded
View

technical-reference/natural-logarithm-functoid.md
:white_check_mark:Succeeded
View

technical-reference/not-equal-functoid.md
:white_check_mark:Succeeded
View

technical-reference/octal-functoid.md
:white_check_mark:Succeeded
View

technical-reference/promote-properties-dialog-box.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 14f82c7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

technical-reference/issoticket-members.md
:white_check_mark:Succeeded
View

technical-reference/issoticket-methods.md
:white_check_mark:Succeeded
View

technical-reference/iteration-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/less-than-functoid.md
:white_check_mark:Succeeded
View

technical-reference/less-than-or-equal-to-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-and-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-date-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-existence-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-functoids-reference.md
:white_check_mark:Succeeded
View

technical-reference/logical-numeric-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-or-functoid.md
:white_check_mark:Succeeded
View

technical-reference/logical-string-functoid.md
:white_check_mark:Succeeded
View

technical-reference/looping-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/lowercase-functoid.md
:white_check_mark:Succeeded
View

technical-reference/mass-copy-functoid-reference.md
:white_check_mark:Succeeded
View

technical-reference/mathematical-functoids-reference.md
:white_check_mark:Succeeded
View

technical-reference/maximum-value-functoid.md
:white_check_mark:Succeeded
View

technical-reference/minimum-value-functoid.md
:white_check_mark:Succeeded
View

technical-reference/modulo-functoid.md
:white_check_mark:Succeeded
View

technical-reference/multiplication-functoid.md
:white_check_mark:Succeeded
View

technical-reference/natural-exponential-functoid.md
:white_check_mark:Succeeded
View

technical-reference/natural-logarithm-functoid.md
:white_check_mark:Succeeded
View

technical-reference/not-equal-functoid.md
:white_check_mark:Succeeded
View

technical-reference/octal-functoid.md
:white_check_mark:Succeeded
View

technical-reference/promote-properties-dialog-box.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


bevy 0.15

Yes

Bevy 0.15 uses wgpu 0.23 (Cargo.toml) but it will still cause issues with vello 0.3 using wgpu 22.0. However the main branch of vello upgraded to wgpu 23.0 so the next vello release will probably be compatible.

After some conversation in Zulip, it looks like there will indeed be a vello 0.4 launched on wgpu 0.23 soon(tm) that will unblock our issues.

@simbleau I actually have a branch with the bevy 0.15 update, maybe it can help you as a starting point. The branch builds without errors (but only with the default features) and the examples that don't require the extra features build as well. Some examples run fine and some have glitches. Let me know if I can help with something!

@elaye submit it as a PR please :)


Diff editor: show path as description

I often miss that git diff editors do not show the path of a resource as description, e.g. here:

Me too. It happens because git uses the title option when invoking vscode.diff, as you once told me to do. Without passing a title option, this is how it looks:

Notice the description never appears, independently of using title or not. The vscode.diff command also does not support passing description.
Ultimately I think the fix should be in the diff editor: it just seems like it never shows a description.

@joaomoreno opened https://github.com/microsoft/vscode/pull/109289 to support passing in a description to the vscode.diff command, e.g.:
commands.executeCommand<void>('vscode.diff', left, right, title, 'Hello Diff Description', opts)

As I am not an expert in git code, could you adopt this for those diffs where the left and right resource is basically the same? I think that is the only case where the description would make sense.
In workbench core, we use this code to get a description label:
this.labelService.getUriLabel(dirname(resource), { relative: true });

Replied in PR.

Pushed a generic solution on the layer of the diff editor: if left and right resource can be handled by our file service and share the same parent path, a description is added.

Unfortunately on the index, we only show the full path because of the git query I think:

Verification: with tabs disabled, verify you see the folder as part of the editor label description when you click on a change from the SCM changes view. Make sure to click on a simple file change, not a rename, add or delete operation.


Highlighter ignores the culled fragment map entries

Describe the bug 📝
I am streaming an ifc file and trying to highlight nodes from the relationTree (where each entry would have a list of express ID's), but the highlight ignores highlighting the fragments that are culled from the scene.
Reproduction ▶
No response
Steps to reproduce 🔢

Use IFCStreamer to use any ifc file
Open RelationsTree tool, try to select any RelationsTree table entry (which contains children)
Check the Highlighters Selection Mapping

System Info 💻
System:
    OS: Linux 6.5 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 6.18 GB / 15.30 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.9.0 - /usr/bin/node
    npm: 9.6.3 - /usr/bin/npm
  Browsers:
    Chrome: 124.0.6367.118

Used Package Manager 📦
npm
Error Trace/Logs 📃
No response
Validations ✅

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
[X] Check that this is a concrete bug. For Q&A join our Community.
[X] The provided reproduction is a minimal reproducible example of the bug.

Hey, this is already fixed from<EMAIL_ADDRESS>Before reading the answer, keep in mind that the goal of streaming is to only load the geometries that the user sees. If you are building an app where the user highlights all items at all times, you will hit performance issues for bigger models and more modest machines, simply because that's the computational cost of loading that amount of geometry at the same time. This doesn't mean it won't work, but it's something to keep in mind.
I'm using the streaming tutorial code as starting point. There are 2 possible use cases:
Case 1
You want to highlight, stream the highlighted elements and show them to the user. For example: show the user all the furnishing elements of a project. This can now be done like this:
  const model = await loader.load(geometryData, true, propertiesData);
  console.log(model);

  const highlighter = components.get(OBCF.Highlighter);
  const classifier = components.get(OBC.Classifier);
  classifier.byEntity(model);

  const furnitures = classifier.find({ entities: ["IFCFURNISHINGELEMENT"] });
  highlighter.add("example", new THREE.Color("red"));
  highlighter.config.world = world;

  window.addEventListener("keydown", async (event) => {
    if (event.code === "KeyP") {
      const furnituresIDs = Object.keys(furnitures);
      await loader.setStatic(furnituresIDs, true, false);
      await highlighter.highlightByID("example", furnitures, false, true);
    }
  });
}

When using setStatic, you are forcing the given items to be streamed. They will be kept in memory until the model is disposed or until they are removed from the static using false as the second setStatic parameter. The third parameter of setStatic determines whether the culler should be applied to these elements or not. I'm using false to ensure the elements are kept visible. When you are done highlighting the items, remember to set them static to false or the geometry will be kept in memory.  The result:
https://github.com/user-attachments/assets/631d0809-f98b-47e2-b04e-e27f78fa284a
Case 2
You want to highlight the currently streamed elements, and highlight the ones that get streamed as they are discovered. For example: apply a red filter to all the furnishing elements of a project, but don't necesarily show them. This can now be done like this:
  const model = await loader.load(geometryData, true, propertiesData);
  console.log(model);

  const highlighter = components.get(OBCF.Highlighter);
  const classifier = components.get(OBC.Classifier);
  classifier.byEntity(model);

  const furnitures = classifier.find({ entities: ["IFCFURNISHINGELEMENT"] });
  highlighter.add("example", new THREE.Color("red"));
  highlighter.config.world = world;

  window.addEventListener("keydown", async (event) => {
    if (event.code === "KeyP") {
      await highlighter.highlightByID("example", furnitures, false, true);
    }
  });

  loader.onFragmentsLoaded.add((frags) => {
    highlighter.updateFragments(frags);
  });
}

As you see, in this case the highlighting style is applied to fragments only when they are streamed. This is the result:
https://github.com/user-attachments/assets/f0fd367a-2382-4f93-8b2b-83de8198d522
I hope this helps. Let me know how it goes!

This is awesome, thanks. I am aware about the performance issues, but it will not be a problem with the particular case where I do for instance only want to load the furnishing elements. That's quite a common case for me. I might also want to load columns from model A and windows from model B together. In this case I would probably also build the JSON config on the fly so the streamer would never try to request anything but the elements in scope.
I will work on the implementation and give you a heads up if I discover something unexpected. Thanks a million for the swift response, that's much appreciated!

Works pretty well now, I would say! This is an example of how I use it for spatial decomposition of the model 🤩
https://github.com/user-attachments/assets/6392834c-14f3-42dd-a43d-d66bc10ec977


Bug 1731024: Bumpin Jenkins version in centos image

Bumpin Jenkins version in centos image

/assign @waveywaves

/lgtm

The ART Team has been asked to release with this card: https://jira.coreos.com/browse/ART-799


sh:or constraints not supported

Although, simple cases can be rewritten with other shacl constructs and be more efficient

covered in branch: feature/ShaclLogicalConstraints


Backports for 0.2.1

Preparing the release!

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

In the file src/einsteinpy/coordinates/utils.py:

Line 66:9: W503 line break before binary operator
Line 68:13: W503 line break before binary operator
Line 110:9: W503 line break before binary operator
Line 111:9: W503 line break before binary operator
Line 115:9: W503 line break before binary operator
Line 116:9: W503 line break before binary operator
Line 155:9: W503 line break before binary operator
Line 156:9: W503 line break before binary operator
Line 160:9: W503 line break before binary operator
Line 161:9: W503 line break before binary operator

In the file src/einsteinpy/symbolic/christoffel.py:

Line 71:25: W503 line break before binary operator
Line 72:25: W503 line break before binary operator

In the file src/einsteinpy/symbolic/constants.py:

Line 6:55: W291 trailing whitespace
Line 17:59: W291 trailing whitespace
Line 20:47: W291 trailing whitespace
Line 21:51: W291 trailing whitespace
Line 51:30: W291 trailing whitespace
Line 53:1: W293 blank line contains whitespace

In the file src/einsteinpy/symbolic/einstein.py:

Line 24:121: E501 line too long (134 > 120 characters)

In the file src/einsteinpy/symbolic/metric.py:

Line 104:67: W291 trailing whitespace

In the file src/einsteinpy/symbolic/predefined/de_sitter.py:

Line 42:1: W293 blank line contains whitespace

In the file src/einsteinpy/symbolic/ricci.py:

Line 157:121: E501 line too long (121 > 120 characters)

In the file src/einsteinpy/symbolic/schouten.py:

Line 24:121: E501 line too long (134 > 120 characters)
Line 67:17: W503 line break before binary operator

In the file src/einsteinpy/symbolic/stress_energy_momentum.py:

Line 25:121: E501 line too long (134 > 120 characters)
Line 52:13: W503 line break before binary operator
Line 53:13: W503 line break before binary operator

In the file src/einsteinpy/symbolic/tensor.py:

Line 80:121: E501 line too long (121 > 120 characters)
Line 189:55: W291 trailing whitespace
Line 190:62: W291 trailing whitespace
Line 207:1: W293 blank line contains whitespace
Line 208:1: W293 blank line contains whitespace
Line 223:1: W293 blank line contains whitespace
Line 229:77: W291 trailing whitespace
Line 232:121: E501 line too long (134 > 120 characters)
Line 236:121: E501 line too long (122 > 120 characters)
Line 236:123: W291 trailing whitespace
Line 239:69: W291 trailing whitespace
Line 308:1: W293 blank line contains whitespace
Line 322:121: E501 line too long (129 > 120 characters)

In the file src/einsteinpy/symbolic/vector.py:

Line 22:121: E501 line too long (133 > 120 characters)
Line 54:55: W291 trailing whitespace
Line 55:110: W291 trailing whitespace

In the file src/einsteinpy/symbolic/weyl.py:

Line 26:121: E501 line too long (136 > 120 characters)
Line 85:29: W503 line break before binary operator
Line 86:29: W503 line break before binary operator
Line 87:29: W503 line break before binary operator
Line 89:25: W503 line break before binary operator
Line 91:21: W503 line break before binary operator
Line 93:25: W503 line break before binary operator
Line 94:25: W503 line break before binary operator

In the file src/einsteinpy/tests/test_symbolic/test_tensor.py:

Line 90:12: E713 test for membership should be 'not in'
Line 155:13: W503 line break before binary operator
Line 156:13: W503 line break before binary operator
Line 157:13: W503 line break before binary operator


show language name in it's own language

same as https://github.com/aldryn/aldryn-boilerplate-bootstrap3/pull/150

:+1:

LGTM


ed25519 cert support?

I'm trying to add a cert. let message: Message = from_bytes(bytes)?; fails with an error like this:
error: Utf8Error {
    valid_up_to: 2,
    error_len: Some(
        1,
    ),
},

❯ ssh-add
Enter passphrase for /home/bbigras/.ssh/id_ed25519:
Bad passphrase, try again for /home/bbigras/.ssh/id_ed25519:
Identity added: /home/bbigras/.ssh/id_ed25519 (bbigras@desktop)
Certificate /home/bbigras/.ssh/id_ed25519-cert.pub (some_id) add failed: communication with agent failed

Message needs to be a valid ssh agent message. Could you share a bigger example or link to your repo?

I don't know a simpler way to get a cert yet, but you can get one with vault:
# start vault
docker run -it --rm --cap-add=IPC_LOCK -p 1234:1234 -e 'VAULT_DEV_ROOT_TOKEN_ID=myroot' -e 'VAULT_DEV_LISTEN_ADDRESS=<IP_ADDRESS>:1234' vault

export VAULT_ADDR='http://<IP_ADDRESS>:1234'

# password is "myroot"
vault login

vault secrets enable -path=ssh-client-signer ssh

vault write ssh-client-signer/config/ca generate_signing_key=true

vault write ssh-client-signer/roles/my-role -<<"EOH"
{
  "algorithm_signer": "rsa-sha2-256",
  "allow_user_certificates": true,
  "allowed_users": "*",
  "allowed_extensions": "permit-pty,permit-port-forwarding",
  "default_extensions": [
    {
      "permit-pty": ""
    }
  ],
  "key_type": "ca",
  "default_user": "ubuntu",
  "ttl": "30m0s"
}
EOH

vault write -field=signed_key ssh-client-signer/sign/my-role \
<EMAIL_ADDRESS>> id_ed25519-cert.pub

Now, if I run ssh-add:

with the normal ssh-agent, id_ed25519-cert.pub is added successfully
with https://github.com/wiktor-k/ssh-agent-lib/blob/71ff9a09c7ffea64b163c2c7dd60f4835b2f40ac/examples/key_storage.rs , the cert is not added

Hi,
I've generated a sample cert using this guide and reproduced your issue: yep, the SSH certs are not supported. It seems the parser logic for certs is not right.
I'll add a PR welcome label if anyone wants to tackle this issue.

I've begun some work on this in https://github.com/wiktor-k/ssh-agent-lib/commit/2bb7482c7fc5e649e9f82e4a9c30dcaa101df4e1 but it appears the serialization for keys with certs is not supported.

The Opaque deserializers in ssh-key project (https://docs.rs/ssh-key/0.6.5/src/ssh_key/private/opaque.rs.html#80-89) just read a vector and that's it but my understanding at the moment is that one can't just do that.
So the fix would probably be adding the certs formats directly to ssh-key crate and then it'd be automatically supported here.
I'll CC @baloo who is knowledgable enough that he can double-check my thinking :)
So... no happy news now but maybe there's a way forward.
Thanks for your attention~! :wave:

This should be fixed by #33, Please post a new comment if we missed something.


[RESTEASY-3380] Introduce an ExceptionMapper which handles JsonProces…

…singException's, logs the error then returns an innocuous response.
https://issues.redhat.com/browse/RESTEASY-3380
Upstream: #3928

The failure is due to file names being too long for Windows. Nothing to be concerned about for now as this is an unsupported branch.


Enhancing Note Presentation for Improved Readability and Usability

I think it would be relevant to improve the presentation of notes to facilitate their reading and use. This would be a minor effort and a good improvement in my opinion. 🙃
Here are some ideas:

Place the summary/key points at the top of the note if a summary or key points have been generated
Replace the transcript with its cleaned-up version if such a version has been generated
Replace the created at and updated at properties with dates in Obsidian's date and time format (I think we can do without milliseconds ^^)
Replace the duration property with a readable format .m.s

What do you think? 🦦
PS : I'd be delighted to work on it tomorrow if the idea appeals!

These ideas are intriguing, can't wait to use them!

closed with #35 -- beta version available via BRAT and if no big issues come up we can push v0.0.20 out to everyone


WIP : Modularized integration tests

Moved common variables and utils to seperate folder
Fixes #134
For now only single_replica_stop_start is implemented. I would like to get some initial feedback before proceeding further.
Signed-off-by: Jayadeep KM<EMAIL_ADDRESS>

Link to original file : https://github.com/openebs/jiva/blob/master/ci/start_init_test.sh

cc @payes @utkarshmani1997

cc: @ksatchit @payes

Hi @kmjayadeep changes are looking good. Can you please rebase your PR and incorporate latest changes accordingly ?

Hi @kmjayadeep thanks for the refactoring. Closing this PR as the review comments have not been addressed since very long time. You can reopen this PR or raise another for the same :)


Enable the use of Unstructured loaders with Google drive loader

Feature request
The goal of this issue is to enable the use of Unstructured loaders in conjunction with the Google drive loader.
Motivation
This would enable the use of the GoogleDriveLoader with document types other than the standard Google Drive documents/spreadsheets/presentations.
Your contribution
I can create a PR for this issue as soon as I have bandwidth. If another community member picks this up first, I'd be happy to review.

I've been offering a pull-request 5135 with this functionality for several weeks now.


Portfolio: finish mobile version

Finished HTML and CSS for the mobile version.

Adjusted card images width to work properly on all mobile devices, added missing features from the template and corrected HTML structure.


Exam. First try

Gadt + Dsl
Task about queries

I added fixes. Gadt is now used to be able to insert values of different types. The main thing is that each type should have instance "ToSqlStr".
String should  be wrapped in single quotes : VALUES ('val1', 'val2')
Numbers without quotes.
Booleans : True False.
GADT are used to provide type constraint ToSqlStr to the INSERT and UPDATE data constructors of QueryF.

Ah, Ok.


Invert Binary Tree

Problem Link: https://leetcode.com/problems/invert-binary-tree/

Sure, add this problem under the Leetcode Problem folder which is inside the tree folder.


How do you run this?

Tried:
pip install -e setup.py   got: setup.py should either be a path to a local project or a VCS url beginning with svn+, git+, hg+, or bzr+
python main.py

Hi, sorry for the late response. It looks like you're using setup.py incorrectly.
You should run:
python setup.py install
python main.py
The above should work. I just tested it on my machine and it worked correctly. Let me know if you have any other questions.


Add self-update command test

big one, I will need deeper look.
can we somehow split it ?

Updated to keep final classes final and use interfaces for mocks instead.
@keradus I think some small parts could be extracted, but most of the changes are directly tied to adding the SelfUpdateCommand test, so not worth it IMO.

1.3k lines on diff, not sure if "not worth it" indeed

See #3246.

#3246 got merged. please merge/rebase with 2.2

Rebased.

Thank you @julienfalque.


VS 2019 can't open project files from sln

The global.json file specifies latestPatch as the allowed roll forward instead of latestFeature, so anyone installed DNCore SDK 3.1 in the past week and getting 3.1.201 instead of the specified 3.1.101 can't open the projects.

https://github.com/mathnet/mathnet-numerics/pull/699 created to allow SDK 3.1.x instead of 3.1.101.x.

It seems the 3.1.1 SDK got uninstalled? If I remember correctly, the Visual Studio updater sometimes uninstalls SDKs if, and only if, they were originally installed by the updater. But VS works perfectly well with the 3.1.1 SDK if installed. I've added a note to the build instructions that the SDK is required. Thanks for the heads up.

I see what happened.  Anyone downloading VS 2019 now like I did just to work on this is getting 16.5 which included 3.1.3 / 3.1.201. (Why can't they just pick a version number?)
I'll download 3.1.101, but it compiled fine on 3.1.201 as well in case you do decide not to lock it 3.1.101.x in the future.

We're quite restrictive currently because we've been affected by Microsoft breaking stuff in feature updates in the past. But maybe setting rollForward to feature (instead of the current latestPatch and the proposed latestFeature) would be a good compromise - we would still normally build on 3.1.1, also on CI, but it would not have broken you if I understand it correctly.

I've just pushed this to master. Thanks anyway for the PR!

Been bitten by the occasionally broken updated library as well.  I did install 3.1.101 on my machine and all the projects were then able to open just fine under 2019 16.5.


Any luck during sending list message?

i am trying to send with exact data
.sendListMessage but no luck could you guide me or send me working one?

What's the actual issue or error?
I'm no longer maintaining the library.

For the issue is

TypeError: messenger.sendListMessage is not a function

Oh, it's because I haven't published latest code to npm. That PR is not public on the npm module.
Please install the module from the git repo

thanks a lot..

I've published 1.2.0 to npm :)


feat: dynamic members docker packaging and compose setup

Reference: #122
The dynamic-members code of raftify has been packaged using Docker. Additionally, a Docker Compose configuration for a 3-node example has been added.
Currently, the local binding is not configured, so the recovery option cannot be used. Plans to add local binding in the future to enable recovery functionality are underway.

Thanks!


no station name is working

Hi Folks,
no matter which station name i put in the config file,
i always get
"The name of the station is not correct, please check on MVG."
tried at least 20 different stations which definitely exists.
same with default "Hauptbahnhof".
raspbian 9 (stretch)
MagicMirror 2.9.0
any ideas?

Thank you man!!!!!
You pointed in the right direction.
The guy responsible for the python wrapper you pointed to already figured out what changed.
obviously mvg indeed changed the urls...
to get it back working, open the mvgmunich.js
find the lines 18 & 19
within the link, simply swap positions of "api" and "fahrinfo"
-->  .../api/fahrinfo.....
and voila !
its working again!
thank you for pointing in the right direction !

Thanks, that worked for me, too!

@cerberus82 thank you for reporting the issue
@magic21nrw thank you for the pointing to the problem
@all fix is available in the master branch


feat(material): Allow focus origin to be an optional input to focus() methods.

Feature Description
WHAT: For Angular Material components that have a focus() method, allow for the origin param to be optional and remove the default origin value.
WHY: For cases where the focus() method is called and the origin is already defined, we don’t want to override the origin using focusVia to always be some default value. In many cases, we want to leave the origin unchanged, but if there are cases that need the origin to be updated, allow for this with an optional origin param.
Use Case
If the focus origin value is keyboard, and some interaction happens where we want to set focus to another element somewhere on the page by explicitly calling focus(), then in cases where the focus origin should remain the same, the current implementation causes the origin to change and the interaction to be weird. This is also due to the fact that we use a single, global focus monitor attached to the document body in eventual detection mode.
Here are the components to update:
-button
-checkbox
-menu item
-menu trigger
-radio
-expansion panel header
-slide toggle
-step header

Would it work for your use case if the FocusMonitor publicly exposed lastFocusOrigin so you could just read that and pass it through to the focus method manually?
Changing the default behavior if no origin was specific would be a breaking change that would potentially be difficult to land in Google, so doing it manually would be an easier change to make, especially since we seem to already track the last focus origin.

Another problem with adding origin parameters everywhere is that we'd have to inject and use FocusMonitor in components that don't use it at the moment which will be a breaking constructor change.

Interesting thought, yes that would work for components where we call focus and could pass lastFocusOrigin in. However, this wouldn't work for Angular Material components that call focus on another Angular Material component.
My main concern is that when calling focus one would need to know to access the lastFocusOrigin from the global focusMonitor and pass that through the focus call vs. just using .focus() which is more intuitive.
I am curious how "bad" the breaking change would be? I attempted to look through the history of some of these focus methods and couldn't exactly understand the reason why the default focus origin (and the chosen value that is different for different components) was necessary? Do you have more background knowledge on that?

@crisbeto I believe all the components I want to add an origin param to (the focus methods of radio, slide toggle, etc.) already inject FocusMonitor, though I may have missed something and understand incorrectly!

@jelbourn I am currently trying to see how many issues my change would cause in Google with button.
@crisbeto Here is an example PR: https://github.com/angular/components/pull/20898 for the change I am proposing for button (and other components as well).
Let me know if this information helps!

I think this seems fine as long as it doesn't turn out to be too breaking (which it seems not to be). The proposal isn't to add origin parameters everywhere, its just to stop defaulting the parameter to 'program' in places where it has already been added. Instead we will allow the origin to be set according to whatever the FocusMonitor decides it should be.

Closing this since it has been resolved and the changes have been made.


Cross Site Script Vulnerability on "Page" in Monstra version 3.0.4

Hii, Team Monstra!!!
Describe the bug
An authenticated malicious user can take advantage of a Stored XSS vulnerability in the "Page" feature.
To Reproduce
Steps to reproduce the behavior:

Login into the panel Monstra

Go to 'admin/index.php'

Click 'Create New' -> 'Page'

Insert Payload XSS:
">
'><details/open/ontoggle=confirm("XSS")>
// # "><svg/onload=prompt(1337)>
<svg/on

Save and Exit

Click 'Pages' new -> xss alert message!

Impact
Commonly include transmitting private data, like cookies or other session information, to the attacker, redirecting the victim to web content controlled by the attacker, or performing other malicious operations on the user’s machine under the guise of the vulnerable site.
Screenshots
Infor Monstra version:

Ex1 payload xss:
a. Creat new page:

b. click page:

c. xss alert mess:

Desktop (please complete the following information):
OS: Windows
Browser: All
Version:
I Hope you fix it ASAP!!!!

Alternatively, I can insert the payload into the item 'Metada' and 'Setting'
Payload XSS: 'Metada'

Payload XSS: 'Setting'


New rename_vars() method seems to be missing from dataset attributes

I tried to use this on a netcdf file that needs to be made CF-compliant.
But:
Traceback (most recent call last):
  File "/home/smartmet/bin/hops-raw_to_cf.py", line 28, in <module>
dsm.rename_vars({'soilt_node_1':'stl1','soilt_node_2':'stl2','soilt_node_3':'stl3','soilt_node_4':'stl4','evapo':'e','uz_vol':'swl2','lz_vol':'swl3','snow':'h_snow','snowpack':'w_snow','precip':'tp','tempc':'t','runoff':'ro'})
  File "/home/smartmet/anaconda3/lib/python2.7/site-packages/xarray/core/common.py", line 179, in __getattr__
    (type(self).__name__, name))
AttributeError: 'Dataset' object has no attribute 'rename_vars'

I don't see how I should in another way call this rename_vars method.
Thanks for any fix/help

I think we dropped py27 a long time ago and rename_vars was added since then. To confirm, could you print your python and xarray version (or the output of xr.show_versions())?
In general, if you can, you should try to use python >= 3.6.

Bummer! That's the issue. We have a conda installation for python2.7 as the HOPS model hasn't been cleaned up for python3...

Cheers
Mikko

no worries


Simplify job

The previous version of the job created an incorrect environment, which led to errors:
+ OS_BUILD_ENV_TMP_VOLUME=/tmp
+ hack/env JUNIT_REPORT=true make test-integration
go test ./test/integration/...
# _/go/github.com/openshift/image-registry/test/integration/imagelayers
test/integration/imagelayers/imagelayers_test.go:12:2: cannot find package "github.com/docker/distribution" in any of:
	/usr/lib/golang/src/github.com/docker/distribution (from $GOROOT)
	/go/src/github.com/docker/distribution (from $GOPATH)
FAIL	_/go/github.com/openshift/image-registry/test/integration/imagelayers [setup failed]

@kargakis please review

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_image-registry/17/test_pull_request_image_registry_integration/23/

The code was cloned to /data/src/github.com/openshift/image-registry but GOPATH is /go/src/...

The integration tests can not be run in the docker.

https://github.com/openshift/image-registry/pull/19

The integration tests can not be run in the docker.

@dmage @legionus this is going to be a suuuuper hard TODO for y'all to tackle soon by the way


HADOOP-16252 add prefix to dynamo tables in tests

This adds a configurable prefix to the table names used in the dynamo tests so that they can be run by a user given dynamo permissions only on tables with the configured prefix.
I have successfully executed the full test suite with this change, my own prefix defined in auth-keys.xml, and a user with dynamo permissions only to tables with the configured prefix.
I executed the tests with:
mvn -T 1C verify -Dparallel-tests -DtestsThreadCount=8 -Ds3guard -Ddynamo

I did have to re-execute 3 of the tests individually due to transient failures:
mvn -T 1C verify -Dtest=skip -Dit.test=ITestS3AFileSystemContract -Ds3guard -Ddynamo
mvn -T 1C verify -Dtest=skip -Dit.test=ITestS3AEmptyDirectory -Ds3guard -Ddynamo
mvn -T 1C verify -Dtest=skip -Dit.test=ITestS3AContractGetFileStatusV1List -Ds3guard -Ddynamo

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
843
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 7 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
1047
trunk passed

+1
compile
31
trunk passed

+1
checkstyle
21
trunk passed

+1
mvnsite
34
trunk passed

+1
shadedclient
653
branch has no errors when building and testing our client artifacts.

+1
findbugs
46
trunk passed

+1
javadoc
22
trunk passed

_ Patch Compile Tests _

+1
mvninstall
29
the patch passed

+1
compile
27
the patch passed

+1
javac
27
the patch passed

-0
checkstyle
15
hadoop-tools/hadoop-aws: The patch generated 2 new + 14 unchanged - 1 fixed = 16 total (was 15)

+1
mvnsite
29
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
694
patch has no errors when building and testing our client artifacts.

+1
findbugs
47
the patch passed

+1
javadoc
21
the patch passed

_ Other Tests _

+1
unit
281
hadoop-aws in the patch passed.

+1
asflicense
28
The patch does not generate ASF License warnings.

3946

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-742/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/742

Optional Tests
dupname  asflicense  mvnsite  compile  javac  javadoc  mvninstall  unit  shadedclient  findbugs  checkstyle

uname
Linux cfdd925f034c 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 254efc9

maven
version: Apache Maven 3.3.9

Default Java
1.8.0_191

findbugs
v3.1.0-RC1

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-742/1/artifact/out/diff-checkstyle-hadoop-tools_hadoop-aws.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-742/1/testReport/

Max. process+thread count
413 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-aws U: hadoop-tools/hadoop-aws

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-742/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

Reviewed the PR and it looks ok to me. Running the tests against Ireland the only test failing was org.apache.hadoop.fs.s3a.commit.staging.integration.ITestDirectoryCommitMRJob.testMRJob which is a known issue under HADOOP-1620.

Realized I forgot to mention the region I did my test run against -- us-west-2.

merged via a pull-patch-commit operation


get_server_url throws an AttributeError on rbt login/logout

If you execute rbt login or rbt logout with nothing in self.options.server then the command will fail with an AttributeError:
CRITICAL:'NoneType' object has no attribute 'scan_for_server'
rather than showing the friendly error message.

Hi,
We don't use pull requests. Can you please post this on https://reviews.reviewboard.org/?
Thanks!


deta-base: Added exists method

Method to determines if an object with specific key exists in the database

Hi @jorgeajimenezl 👋
We really appreciate the contribution! This helpful method but get does job very well. We also try to keep the API as small as we can. My apology but I have to close this PR.


support implace vector functions?

hi, i saw your discourse post and then the repository and im really like it. On our package, we had to add a fixed point solver (just with damping) to solve some thermo problems: , but i would be glad to depend on an external package instead, specially if it provides convergence advantages over simple and damped fixed point iterations.
While the vector solver provided in this package is fine, it allocates a vector on each call. this will quickly becomes the main bottleneck. one idea is to provide an "implace" version of afps, afps! that accepts a function f!(out,x). then the function calls just overwrite a buffer vector instead of creating a new one.

I'll be happy to provide an inplace version, I'll work on it


dinov2 pretrain

Can you provide the 'pretrained/dinov2/dinov2_vitl14_pretrain'?

The code is here https://github.com/PaddlePaddle/PASSL/blob/main/passl/models/dinov2/dinov2_vit.py#L644
The model of vit large is unavailable


Do not use Etags in HMAC Key tests or samples.

Apparently they do not work as I expect, until we figure out if my expectations
or the code are wrong, just don't use them.

This change is

I was able to run this version 100 times on my workstation without any flaky failures, so I guess it is Okay?


Performance Issues On Datagrid with expandable rows

Describe the bug
Compared to v1, v2 datagrid with expandable rows performance is worse.
How to reproduce
v1: https://stackblitz.com/edit/clarity-light-theme-v1-0-xux9hr
v2: https://stackblitz.com/edit/clarity-light-theme-v2-ycwsj6
Steps to reproduce the behavior:

Go to stackblitz link for v1 and v2
Click on the load button
See that for v1 it takes a few seconds but v2 takes way longer (30+ seconds)

Expected behavior
v2 and v1 datagrid with expandable rows should have similar load time
Versions
App

Angular: 8
Node: 10
Clarity: 2.2.0

Device:

Type: macbook
OS: Mojave
Browser Chrome
Version 77

Additional notes
According to Ivan

I located the issue to be with an undesired initial animation. Though it is "empty" animation it is still requesting animation frames.

I confirm I have a fix for this. Needs to be prioritized, so it can get tested and merged.

@Jinnie do you know when the fix would be merged?

Done! Thanks for pinging, @tran2
Expect to have it in the next v2 release.


Desperados: Wanted Dead or Alive colorkey issues

Hello,
Desperados (the original DDraw from 2001, not the SDL remake from 2018) has the same issue as Kohan: Immortal Sovereigns.

The upperbound on colorkey is unset in Desperados? After setting
lpColorKey->dwColorSpaceHighValue = lpColorKey->dwColorSpaceLowValue;
in
https://github.com/FunkyFr3sh/cnc-ddraw/blob/ce84abfac06fc929b59da162ed4f41caa7ecd0c0/src/IDirectDraw/IDirectDrawSurface.c#L309-L315
the game is displayed correctly. I don't know if this the "correct" way of solving it :), I just got inspired from wine where the HighValue is also set to LowValue (https://pastebin.com/SmdfCa2b) i.e. fixed_color_key.dwColorSpaceLowValue = fixed_color_key.dwColorSpaceHighValue = color_key->dwColorSpaceLowValue;
I leave it to your expertise on how to fix this...
Demo for the game can be downloaded from https://archive.org/details/desperadosDemo

Yes that was indeed the problem. The wine solution would have worked in this game, but it would have dropped support for other games since they pretty much disabled the entire colorspace feature.
I added the missing check for DDCKEY_COLORSPACE and it should be working now for everygame.
Posting from my alt-account currently because I need to setup 2FA on main account, github doesn't let me log in atm! So I probably better don't post a build here since you can't know if it's really me posting. Do you know how to build it on your own?

No problem, I was just going through some ddraw games I used to play. Thanks for the fix!


Deployment to S3 - error document config not applied in IE

Description
When deploying CRA apps to S3, the error document is effectively ignored by IE11. This causes all routes outside of the root route to reach IE's default 404 page. I have not yet tested this on other IE versions.
Expected behavior
If error document is set to index.html, the application should still display the App.js component when visiting <S3-route>/anything. (Alternatively, if a customerror.html is set, it should display that, but doesn't.)
Chrome, Firefox and Safari perform this behavior as expected.
Actual behavior
IE default 404 page.
Environment

npm ls react-scripts<EMAIL_ADDRESS>node -v: v5.5.0
npm -v: 3.5.3

Have tested from:

Operating system: Win 8.1
Browser and version: IE11

Reproducible Demo
I've got an example S3 deployment set up. You'll notice that the root route works fine, but you'll get the IE 404 page with any addition to the URL.
S3 Configuration:
The bucket has an open permissions policy:
{
	"Version": "2016-11-1",
	"Statement": [
		{
			"Sid": "AddPerm",
			"Effect": "Allow",
			"Principal": "*",
			"Action": [
				"s3:GetObject"
			],
			"Resource": [
				"arn:aws:s3:::demo-party/*"
			]
		}
	]
}

and is configured for static website hosting:

More than happy to help debug further, but I'm about out of ideas on my end.

Still not sure how to address this specific issue, but I got around this by layering Amazon's CloudFront CDN service over the S3 bucket, then declaring a custom error document in that distribution. These SO answers were helpful for getting that configured.

I've written a blog post about deploying with S3 and CloudFront. Let me know if you'd like something added to the outputted README regarding either of these.

Thanks for the blog post! It would be really helpful to have these info in the README. 👍

@ggregoire You can add a paragraph with that link to the User Guide in the Deployment section and link to it from README.

When deploying CRA apps to S3, the error document is effectively ignored by IE11.

To be clear there's nothing we can do in Create React App to fix an issue with Internet Explorer. We didn't write it after all 😉
But it would be great to add a link to the article to user guide.

@gaearon @ggregoire quick PR up at: https://github.com/facebookincubator/create-react-app/pull/1071

Fixed in #1071.


Couldn't find a suitable function named eachI

On the first page of the Guide: (https://vale.dev/guide/introduction) $ Loops,
the code snippet:
fn main() export {
arr = ["Storm", "Earth", "Fire"];
eachI arr (i, x){
println(i + ": " + x);
}
}
gives the compiler error:
Couldn't find a suitable function named eachI with args (?3str, ??main<>().?0:319):
}
Rejected candidates:
C:\Vale\builtins\arrayutils.vale:64:1: eachI:
(run with --verbose to see some incomprehensible details)

Found it! There was an eachI for the Array class but not for known-size arrays.
Fixed in the nightly server (run against curl -X POST https://us-central1-valesite.cloudfunctions.net/vale-build -d @-), will mark this fixed when it has an integration test and gets into the next release.

Found it! There was an eachI for the Array class but not for known-size arrays.
Fixed in the nightly server (run against curl -X POST https://us-central1-valesite.cloudfunctions.net/vale-build -d @-), will mark this fixed when it has an integration test and gets into the next release.

Thanks!

Thanks!

Fixed in v0.1.1. Thanks Ivo!

Fixed in v0.1.1. Thanks Ivo!


nwbuild not recognized

I successfully installed nw-builder locally:
npm install nw-builder --save-dev
However, nwbuild is then not recognized:
D:<path where nw-builder installed>nwbuild -v 0.23.5 -p win64 .
'nwbuild' is not recognized as an internal or external command,
operable program or batch file.
Possibly something simple that I am missing?

I successfully installed nw-builder locally:
npm install nw-builder --save-dev
However, nwbuild is then not recognized:
D:nwbuild -v 0.23.5 -p win64 .
'nwbuild' is not recognized as an internal or external command,
operable program or batch file.
Possibly something simple that I am missing?

nwbuild : The term 'nwbuild' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the name, or
if a path was included, verify that the path is correct and try again.
At line:1 char:1

nwbuild

  + CategoryInfo          : ObjectNotFound: (nwbuild:String) [], CommandNotF
 oundException
  + FullyQualifiedErrorId : CommandNotFoundException

If you install nw-builder locally in your project, .\node_modules\.bin\nwbuild should work.


Add Keras layers support

This PR provides a KerasLayer class for converting a PennyLane QNode to a Keras layer, which can then be used within standard Keras features such as the Model/Sequential models.
Currently, the following is not added:

A tutorial/demo to show how to use this new feature
A section in "Using PennyLane" of the documentation showing a higher level picture. This and the above could be added together.
Supporting input of a QNodeCollection instead of a single QNode. This should be possible, we need to make the func.sig attribute available in the QNodeCollection and in qml.map.

Providing this functionality would help solve https://github.com/XanaduAI/pennylane/issues/166 and is also discussed in https://github.com/XanaduAI/pennylane/issues/133, https://discuss.pennylane.ai/t/qnode-inside-keras-layer/335/3 and https://discuss.pennylane.ai/t/creating-and-saving-models/46.

Also just reading through your main comment @mariaschuld:

In short, I would put a lot more examples in the docstring: small one-liners at the main part, and extensive examples in the UsageDetails section.

Thanks, I have added some more examples. One thing to also bear in mind that might help, is we plan to add a tutorial to go really in depth on how to use this feature.

This includes integration examples with PyTorch code. At the moment I have to piece things together from the tests to play around - I doubt a user would do that.

TF/Keras? The main example now shows how you can train a model :grin:

I also strongly suggest to add a section to "interfaces -> Tensorflow", which explains how the integration works. But this could be done in a follow up PR?

Do you mean add something to the documentation, e.g., https://pennylane.readthedocs.io/en/stable/introduction/interfaces/tf.html or https://pennylane.readthedocs.io/en/stable/code/api/pennylane.interfaces.tf.html#module-pennylane.interfaces.tf?
Would have to think about what to add here, it's a fairly light change so far (making the func attribute visible and control over the TF dtype). One follow up thing might be to make the dtype argument of to_tf be visible higher up, e.g. when you use the qnode decorator.

Don't forget to update CHANGELOG with the new feature.

Ok I forgot again :laughing: I'll just do that now.
Thanks again!

:fireworks:


Make toxiproxy provisioning optional

Some projects use sarama's vagrant install to run functional tests, but sometimes tests that are supposed to be deterministic are being messed up by toxiproxy. This PR makes it possible to exclude toxiproxy from the setup. If TOXIPROXY_VERSION env variable is defined then it is provisioned, otherwise it is not.

but sometimes tests that are supposed to be deterministic are being messed up by toxiproxy

I don't immediately understand this - toxiproxy is a deterministic invisible proxy by default, so if it's causing problems in its default state then that sounds like a bug.

Sometimes I saw connections to zookeeper and/or kafka timeout when running tests on Travis CI, so I wanted to remove and extra connection leg from the picture. But turned out that still happens even without toxiproxy. Well if you do not want to have an option to disable the proxy then just close this PR.

Since toxiproxy does nothing by default, I don't really want to carry any extra complexity around enabling/disabling it.


The requirements.txt file is missing.

Hello, sorry to bother you again. There is no requirements.txt file in the src/ directory. Can you help me find it ?

https://github.com/wey-gu/NebulaGraph-Fraud-Detection-GNN/tree/main/src/fraudd_backend
:)


Crashed when I asked to display icon in dock

See my comment in #1. When I selected Display keycastr icon in the dock before I had dragged the program into the dock from the finder keycastr crashed immediately and I had to track down and delete its Plist file before it would start again.
When it crashed and wouldn't start it gave me a message similar to the message it gave me before I enabled key caster in the accessibility security preferences.

I tried this (on Yosemite) and it didn't crash.  What version of OS X are you on?  Can you open Console.app and see if there is a crash log?
This change in the preferences does cause the app to prompt you to allow it to restart, which could also have been confused with a crash.
This feature might not be possible on modern OS X; I would vote we remove the option select list from the preferences pane and display the icon in the menu bar by default.  The user needs to drag it to the dock if desired.

On second thought, we shouldn't remove this, since the "display in dock" option is what causes KeyCastr to also show up in the cmd-tab list of active applications.  Perhaps this option needs a better name.

I am up-to-date with my OS X versions like you are. ~/Library/Logs/DiagnosticReports does not contain any crash dumps. I might've used the wrong word. It doesn't crash. It pops a box saying that it has detected a horrible situation that it thinks has to do with security preferences and that it's going to shutdown and then it does.
I find that I am still able to reproduce the issue when I select "in the dock".

And since I can reproduce it I might as well give you the exact error message.

This is not a crash - this is expected.  KeyCastr is telling you that you need to grant it permission.
To do this, visit the Security & Privacy preferences pane, and open the Privacy tab.  Select "Accessibility"in the left menu and unlock the preferences pane if it is locked.  Then drag your copy of KeyCastr into the list of applications "allowed to control your computer".
This is required in order for KeyCastr to catch keyboard events.

I know what it looks like but that's not it. I did grant permission and I've been using it all day. It's when I change that setting that it gives me the message as if I had not granted  permissions which I definitely did.

I've run into this issue before when upgrading or switching between development and released versions. It is normal. You will need to drag your current copy into that pane. Perhaps there is more than one copy of the app on your computer?

On Apr 3, 2015, at 21:47, Michael Fox<EMAIL_ADDRESS>wrote:
I know what it looks like but that's not it. I did grant permission and I've been using it all day. It's when I change that setting that it gives me the message as if I had not granted permissions which I definitely did.
—
Reply to this email directly or view it on GitHub.

BTW, I'm getting the same issue described by @gitfoxi
It works fine, except when I tell it to go to the dock, it crashes and displays the same error until I reinstall.


This PR is related to issue #45

with these changes we prevent any errors that can break the extension.
Not exactly, but something like this.

good!
consider using SOCIAL_RECOVERY_CHAINS, and useMemo.

Exactly 👍🏻


Update README for clarity and to remove redundancy

Addresses some concerns presented in issue #1157, although I don't think it is necessary to add click to the README.

Right on, thanks!


Add vtbls for IWeakReferenceSource and IWeakReference.

Fixes ADO#41937903
When resolving an IWeakReference from a different context, we resolve as IUnknown and then assume that Resolve is the next method in the vtbl, see https://github.com/microsoft/CsWinRT/blob/418229436353d05edccd4f94fd3f6539735d810a/src/WinRT.Runtime/Interop/IWeakReferenceSource.net5.cs#L256. This turns out to not be true and we end up calling an unrelated COM interface with incorrect parameters that than tries to allocate a very large array on the stack resulting in stack overflow.

Superseded by #1301. Thanks @manodasanW


Add bipartite network for correlation assay vs metadata app

Resolves #299
This PR adds a bipartite network plugin for the correlationAssayMetadata app. The plugin uses the statistics endpoint from the correlation compute plugin, and via plot.data converts these stats into a nice json output that structures the statistics as a bipartite network.

This PR now adds the correlation assay metadata plugin without calling out to R at all. The plugin reshapes the data accordingly. Successfully integration tested.
This is a temporary solution that will allow us to continue making progress on the front end and see the app on qa. Later we can return to the plot.data network classes.

feedback incorporated! Note that everything that is just the straight data became *data for consistency with other *data classes. I think that's more clear.


ctags unrecognised, and fails to self-install on mac

Environment data

VS Code version: 1.25.0
Extension version (available under the Extensions sidebar): 2018.6.0
OS and version: macOS 10.13.4 High Sierra
Python version (& distribution if applicable, e.g. Anaconda): 2.7 various
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: N/A

Actual behavior
Hitting "Go to Symbol in Workspace" pops up:

Hitting "yes" runs the internal terminal with:
$ "brew install ctags"
bash: brew install ctags: command not found
$

Which doesn't work because it's passed the whole thing as one command. Problem is, ctags is already installed via brew:
$ which ctags
/usr/local/bin/ctags
$ brew install ctags
Warning: ctags 5.8_1 is already installed and up-to-date
To reinstall 5.8_1, run `brew reinstall ctags`

I also get the same problems when explicitly specifying in the settings:
"python.workspaceSymbols.ctagsPath": "/usr/local/bin/ctags"

Expected  behavior
brew is properly called, but only if ctags isn't installed already.
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
----------Generating Tags----------
/usr/local/bin/ctags --options=/Users/nickd/.vscode/extensions/ms-python.python-2018.6.0/resources/ctagOptions --languages=Python --exclude=**/site-packages/** -o /Users/nickd/dials/dist/modules/.vscode/tags .

So it's definitely running ctags. When I run this command manually in the workspace folder, it takes > 5s to run on my project (and successfully runs), which is much longer than VSCode waits before prompting the ctags install. Even when I run the command externally (verifying that .vscode/tags is created) and re-open VSCode, I still get prompted to install.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
notificationsAlerts.ts:42 Install CTags to enable Python workspace symbols?

Hi @ndevenish.  Thanks for letting us know about this issue.  Please update VSCode (latest: 1.25.1) and the Python extension (latest: 2018.7.1).  Then let us know if you are still seeing the problem.  I expect that you will still run into the same failures, but I haven't been able to reproduce it on my end yet.

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


Clean up unit test for dscim.utils.utils.c_equivalence

Cleans up unit test for dscim.utils.utils.c_equivalence().

Refactors the single test for dscim.utils.utils.c_equivalence() into multiple tests, with each test checking for a single behavior/test case.
The expected outcome for each test was precalculated and stored explicitly with some precision rather than calculated dynamically when tests are run. The expected values were created using the same math and code in the original test. For example, expected = (np.divide(array ** (1 - 10), 1 - 10).values.mean() * (1 - 10)) ** (1 / (1 - 10)) is now just expected = xr.DataArray(np.array(2.32634448)).
The test now checks against expected outcomes with xr.testing.assert_allclose(actual, expected) rather than assert expected == actual, as the original had done. This is helpful because == checks between floats can be difficult, if not impossible, and unreliable.  Using xr.testing.assert_allclose allows for some "fuzziness".

We're using xr.testing.assert_allclose with the default rtol=1e-05 and atol=1e-08. I'm not sure if we need to change how tight the tests are.


Adjustable info log for server startup

I want to be able to silence the info log that Bandit by default prints. The :log option is lifted from how it's usually dealt with in Plug and Phoenix.
But I wonder if there should be an info log by default? With Plug.Cowboy and :httpd there are no info log for server start. This is something that Phoenix adds to the Cowboy2 adapter. If you start the server yourself you would already be aware of the URL/port settings. It makes sense for higher level like Phoenix though.
So I think maybe this info log belongs in Bandit.PhoenixAdapter instead. It should maybe also have a pretty print of common errors just like the Cowboy2 adapter. Right now with :eaddrinuse it just shows this:
     ** (EXIT from #PID<0.13506.0>) shutdown: failed to start child: :listener
         ** (EXIT) :eaddrinuse

Phoenix instead pretty prints this (using the info private function):
[error] Running MyAppWeb.Endpoint with cowboy 2.9.0 at http failed, port already in use

(Ugh, I had a whole multiple paragraph bit of response here and Safari ate it. The gist of it was that I feel pretty strongly that it's Bandit's job to be logging things as it does today, and that I don't think that moving the responsibility into the Phoenix Adapter furthers Bandit's fundamental goal of clarity).
That being said, I like this change a lot and am happy to see it land! A couple of things though;

I wonder if we should call it log_startup to reflect the fact that it only affects startup logs. As it's named now, folks might think it would affect logging everywhere within the app
I'd be happy to see an extra clause added to the case block around bandit.ex:289 to handle address in use errors as you suggest!

I don't think that moving the responsibility into the Phoenix Adapter furthers Bandit's fundamental goal of clarity

Yeah, as long as it's possible to silence the info log then it's all good. But I want to expand a little on my thoughts here.
When I manually start Bandit I'm aware of the status and opts since it's all right there. I don't think I need a log entry to know that the server has started or what the address/port is, it's already given?
However, the info log becomes very necessary when there's any abstraction, i.e. like it being part of the Phoenix supervision tree. In that case I wouldn't necesarily know anything about the Bandit server or how to access it.
Here's an example from the Plug readme with the Plug.Cowboy server:
require Logger
webserver = {Plug.Cowboy, plug: Router, scheme: :http, port: 4000}
{:ok, _} = Supervisor.start_link([webserver], strategy: :one_for_one)
Logger.info("Plug now running on localhost:4000")

If we imagine that Plug.Cowboy was spitting out the info log in the child process inside the supervisor supervision tree, would that really make sense rather than handled outside the supervision tree?
Obviously not a big deal, you can just deal with this by reordering the supervision tree so all the required children will fail before it gets to Bandit. Another counter point is that default/implicit port and address makes it more necessary to info log it at low level.
Again it's all good with ability to silence the info log, just some thoughts on why it should be there in the first place 😄

Again it's all good with ability to silence the info log, just some thoughts on why it should be there in the first place

Yep, totally agree - I think the config point we're adding here handles this well. I really do like having the logging by default for all Bandit installs; I personally use it all the time just to double check myself.

Ended up significantly simplifying the error message in this case. I've been on the record before (also here about the tradeoffs in in (not) wrapping the underlying libraries' error responses and overall concepts, and this is another one where I think that 'not trying to be too clever' is the right thing to do.
There are just too many corner cases with trying to divine what exact address / port the user is binding to for me to feel comfortable with us trying to tell the user anything too specific. Even within Thousand Island, we don't necessarily know the bind address / port that would end up being used (for example, if the user specifies port 0, it's up the the OS to find a port for us. The default bind address may change between TCP and SSL, and so on). Rather than getting on a treadmill of trying to cover off all the possible cases, I think it's best to be transparent and unobtrusive with the underlying error.
WDYT?

Yeah that makes sense. LGTM! 🚢
Only alternative I see here would be to ensure the port/address is available in the caller process somehow (like how ranch does it with ETS), but would be way overkill and a rabbit hole to just have the ability to print address/port in the error message.

Only thing I could think of here would be to ensure the port/address is available in the caller process somehow (like how ranch does it with ETS), but would be way overkill and a rabbit hole to just have the ability to print address/port in the error message. And you will end up in the same situation of trying to deal with edge cases.

That's the thing though - the eaddrinuse error comes from here, and in that case, we simply don't know what the actual resolved bind address/port was that failed (we do know what we passed into the transport module as options, but it's entirely possible that the transport module overrode those / set defaults that aren't really spelled out in authoritative detail anywhere in the Erlang docs). You can really only know the bind info after a successful bind; it's fundamentally a chicken and egg scenario.
Reviewing ranch's code for this here and elsewhere further down in that file, it's not clear to be that ranch is ever in a situation to meaningfully provide bind data for a ref corresponding to a server that failed to start (it reads as if it exits gracelessly and indeed this is what seems to happen if you try and start two out of the box phoenix apps on the same port.
I wonder if perhaps the error lines in CowboyAdapter never actually match? I can't seem to get them to.....

You are right. Didn't realize that the address and port is never shown (I even have this as an example in the issue). It just catches the arg error and returns the scheme:
  defp bound_address(scheme, ref) do
    case :ranch.get_addr(ref) do
      {:local, unix_path} ->
        "#{unix_path} (#{scheme}+unix)"

      {addr, port} ->
        "#{:inet.ntoa(addr)}:#{port} (#{scheme})"
    end
  rescue
    _ -> scheme
  end

So nevermind, pretty sure it'll never show up if the address/port is not used, and is only ever used for when it succeeds.

Pushed a small change so it conforms the message by handling nil pid instead. I should have looked at it more carefully, it should probably be updated in Cowboy2. Maybe there's a possibility that the address/port fails to fetch even when it's running and that's why it's handled in such an odd way.

@mtrudel just amended change to fix linter error.

Thanks for the PR!


Update kafka-streams-scala to 7.0.4-ce

Updates org.apache.kafka:kafka-streams-scala from 7.0.0-ce to 7.0.4-ce.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.kafka", artifactId = "kafka-streams-scala" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #114.


Problems with stopping

linkerd doesn't seem to daemonize properly. Maybe that isn't the right term, but when I execute ./linkerd start, I get a message that it has started. However, when I attempt to stop linkerd, it tells me it isn't running.
ADMIN_PORT=$(grep -A1 '^admin:' config/linkerd.yaml | grep 'port:' | awk '{print ":" $2}') // :9990 by default
curl -s $ADMIN_PORT/admin/ping
echo $?  // returns 6

Prepending localhost in the ADMIN_PORT assignment seems to fix the issue.
ADMIN_PORT=$(grep -A1 '^admin:' config/linkerd.yaml | grep 'port:' | awk '{print "localhost:" $2}')

Thanks for reporting this!  That's a neat fix, but I think we're inclined to just remove the wrapper script in favor of platform-specific rc/init controllers.  I've opened https://github.com/BuoyantIO/linkerd/issues/118 to track that.

In the most recent release, we removed the linkerd wrapper script in favor of an executable that simply runs in the foreground.


added config path to Service interface

For some sort of automations it is practical to get information where service files are stored.

This may be alright. But, the ConfigPath would need to be a separate interface; right now it breaks windows I think.

I haven't tested it with Windows. Do you have a suggestion how to avoid
breaking the build for Windows?
On Thu, Dec 17, 2020, 18:30 Daniel Theophanes<EMAIL_ADDRESS>wrote:

This may be alright. But, the ConfigPath would need to be a separate
interface; right now it breaks windows I think.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kardianos/service/pull/255#issuecomment-747585110,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7RER3CBVILCWRFDTOKPA3SVI52HANCNFSM4U7ZSOSA
.

GOOS=windows go build .

@kardianos Fixed it for windows.
I also wanted to check with you if I did it right. In most of cases I renamed configPath() string, error to ConfigPath()string and refactored accordingly. Do you think that's the best approach or maybe it should be done differently?

So yes, for this change to happen:

Make the ConfigPath return (string error).
Remove it from the service interface.
Make an optional interface it may support (windows won't implement).
Require a type assertion for it to use.

@kardianos  Do you mind if I call the optional interface Config? (I can't think of a better name right now)

No. How about Metaer :) or ConfigPather
hmmm, maybe PatholoConfiger ... I'm getting worse.
Not Config, but maybe not PatholoConfiger either.

I think ConfigInfo sound ok then we can have ConfigPath and what other information might be stored there.

@kardianos I just refactored it to use the optional interface ConfigInfo, later we can decide on the name.

Coverage decreased (-0.3%) to 12.525% when pulling 20d92e3e240c990e23cf8a1da2b0dd38151a1e22 on jasmingacic:configpath into ef35c563203c809a5c48a2310ca90430c064e7c3 on kardianos:master.

Coverage decreased (-0.3%) to 12.525% when pulling 20d92e3e240c990e23cf8a1da2b0dd38151a1e22 on jasmingacic:configpath into ef35c563203c809a5c48a2310ca90430c064e7c3 on kardianos:master.

@kardianos can you help me out with the test for ConfigPath how do you want to have it implemented?

Go ahead and read the diffs and correct the other OSes. Also, no need to have an exported method and un-exported method that do the same thing. Just use the exported method.

So getting config value like this is fine?
	_, err = s.(service.ConfigInfoer).ConfigPath()

Also I'm not sure what you mean by read the diffs and correct the other OSes, I already did that. Unless I'm missing something.

ping

ping


sun.security.validator.ValidatorException: PKIX path building failed

Got this error when saving a specific page:
Traceback (most recent call last):
  File "/home/user/my-project/.venv/bin/savepagenow", line 10, in <module>
    sys.exit(cli())
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/savepagenow/api.py", line 127, in cli
    archive_url = capture(url, **kwargs)
  File "/home/user/my-project/.venv/lib64/python3.7/site-packages/savepagenow/api.py", line 42, in capture
    raise WaybackRuntimeError(error_header)
LiveDocumentNotAvailableException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable

The code I'm using:
import savepagenow

archive_url, captured = savepagenow.capture_or_cache("https://www.chp.gov.hk/files/pdf/local_situation_covid19_tc.pdf")
print(archive_url)

The same code works for some other URL normally.
I presume this is a server side error because I don't think this library is calling Java on my workstation. Strangely, if I post on the Save Page Now form, it actually creates a snapshot of the URL. What is going on?
The URL I'm trying to archive:
https://www.chp.gov.hk/files/pdf/local_situation_covid19_tc.pdf

To me this reads like some kind of SSL issue with your web request from the script.

Is there any option to circumvent the SSL error from blocking the program?


2024-10-22_01-34-59_master-next_amazon-ssm-agent

Automatically created.

Backport failed for kirkstone-next, because it was unable to cherry-pick the commit(s).
Please cherry-pick the changes locally and resolve any conflicts.
git fetch origin kirkstone-next
git worktree add -d .worktree/backport-10060-to-kirkstone-next origin/kirkstone-next
cd .worktree/backport-10060-to-kirkstone-next
git switch --create backport-10060-to-kirkstone-next
git cherry-pick -x 21ada32e35939ed76591d28b26bd18e3f3129b95

Successfully created backport PR for scarthgap-next:

#10070

Successfully created backport PR for styhead-next:

#10071


New update logic

works with
gateway: https://github.com/code-kern-ai/refinery-gateway/pull/35
updater: https://github.com/code-kern-ai/refinery-updater/pull/7
frontend: https://github.com/code-kern-ai/refinery-ui/pull/47

env variable for gateway missing UPDATER=http://refinery-updater:80

[ ] resolved

i think since the readme now uses the release branch we need to add it to the cli logic
https://github.com/code-kern-ai/refinery/blob/c3f78abffca1b4c31384cf3707a914485056d4a1/refinery/cli.py#L31
Also I think we might want to change the default branch to release so the clone command doesn't need the release branch info (this would also then still be usable with the install from github portion on https://www.kern.ai/ )

[ ] discussed
[ ] resolved

[ ] remove changes in template docker-compose.yml


weechat input line behaives strange

Contour Terminal version
0.4.2-master-20f76b90
Installer source
Github: source code cloned
Operating System
Arch
Architecture
x86-64
Other Software
weechat 4.2.0 git master
Steps to reproduce
start weechat
input: /connect freenode
Expected Behavior
/connect freenode
Actual Behavior
it shows & the cursor seems to be positioned wrong
/connectfreenode
Additional notes
I did a check with urxvt to see if it is contour or weechat and urxvt is ok
TERM="contour"
COLORTERM="truecolor"
contour.yml -> https://paste.rs/JP5A4

Good morning. I thought I just fixed that (PR merged last night). I will check with weechat.
P.s. I did not check your version hash suffix (I am on phone right now), but maybe the fix was merged after you updated last time. :)

fixed with latest build :) thanks for the hint i didn't checked the commit messages this night. Have a great day.


fix(start_planner): not run other modules when back pull out

Description

    setIsSimultaneousExecutableAsApprovedModule(false);
    setIsSimultaneousExecutableAsCandidateModule(false);

when backward driving of pull out.
this prevents LC from being approved when back and generating invalid path
Screencast from 2023年06月22日 11時24分17秒.webm
Related links

tier4 internal ticket
Tests performed

psim
https://github.com/autowarefoundation/autoware.universe/assets/39142679/1a5232e6-f99d-4d67-841a-44ba3cfbb0de
Notes for reviewers

Interface changes

none
Effects on system behavior

none
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

We tested this with real vehicle and works fine.


Error when installing snap

Expected Behavior
snap should install withut any issues
Actual Behavior
We get an warning when installing .snap as it cannot find signature metadata
Reproduction Steps

Use ubuntu
try to install snap
fail

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
Ideally we won't need to install with the dangerous flag
Insomnium Version
0.2.1b
What operating system are you using?
Ubuntu
Operating System Version
22 lts
Installation method
downloaded snap from releases
Last Known Working Insomnium version
No response

aw thanks for the bug report; I haven't uploaded Insomnium to snapcraft yet;
I'll look up more into the snap tooling to see how to resolve this


Examples?

Hi guys, could someone provide a simple example how to generate winds/pressures from Best Track data? Thanks

@krober10nd Hi Keith. Here is the link to the documentation of PaHM.

After compilation of PaHM copy any of the sample files in PaHM/templates (for example pahm_control.tmpl) into pahm_control.in
Modify the pahm_control.in according to your needs
Run pahm as: pahm pahm_control.in. This will generate the output NetCDF file for the particular storm.
Important variables in pahm_control.in are
- bestTrackFileName (location of best track filename)
- meshFileType (always ADCIRC, this will allow to force the ADCIRC, SCHISM and possibly FVCOM models
- meshFileName (the mesh file to use, see inputs/adcirc_mesh-shinnecock.dat)
- unitTime (D, H, M, S)
- outDT (output time interval). For hourly outputs, when unitTime=D use outDT=0.041666667
- begDateTime and endDateTime, the begin/end simulation times, e.g: begDateTime=2018-08-30 12:00:00, endDateTime=2018-09-18 06:00:00 (if you use the DateTime variables comment out the begSimTime/endSimTime variables
- modelType=1 or 10 the model to use (Holland/GAHM)

Compilation:

To compile pahm first run the build.sh script as: build.sh --help to see all the available options to the script
Run: build.sh [--platform linux] --compiler gnu to generate the pahm executable
NOTE: make sure that you use a recent version of CMake and that the NetCDF libraries are in your path. You might need to set the NETCDF_HOME environment variable before running the script.

I hope this answers your question.

Thank you very much. As an aside it could also be useful to export to a structured grid in the form of a netcdf file.

The structured and other meshes/grids are in the todo list. Thanks.


Introduce a builder for Identity

Introduce a builder for Identity

I also removed public constructors for Identity, I don't believe users are constructing Identity

Please maintain backwards compatibility.


packet/nodes: switch back to baremetal_0 as default node type

Otherwise upgrading from v0.1.0 will cause all nodes to be recreated.

I think this PR was not necessary. Instead, users wishing to not migrate their worker pools to new type should define the value explicitly and we should recommend users to re-create the pools.

I think this PR was not necessary. Instead, users wishing to not migrate their worker pools to new type should define the value explicitly and we should recommend users to re-create the pools.

That's a fair point. We could update this and mention in the release notes the change and recommend to define explicitly the instance type if using the default one.


CodeWars/DISEMVOWEL_TROLLS.js

Closing Issue/Referencing Issue
issue reference (#)
Available in: https://www.codewars.com/kata/52fba66badcd10859f00097e/train/javascript
Changes Made In Pull Request

Available in: https://www.codewars.com/kata/554e4a2f232cdd87d9000038/train/javascript


Controllers that auto-sleep do not reconnect to the pi3hat spine

Bug description
This bug happens when using a USB controller that goes off to sleep if unused for some amount of time.
Currently the spine does not reconnect to the controller after it wakes up again. (Guess: I suspect it's become /dev/input/js0 is removed then a new one is created, whereas the spine keeps using the previous file handle.)
Expected behavior
When the controller wakes up again (user presses a button), the spine detects it and reconnects to it.
Context

OS: Raspberry Pi OS
Upkie version: 5.2.0

After investigation with the specific sleepy USB controller: the controller does not wake up on any button, but it does wake up with one of the A, B (e-stop), X or Y buttons. Closing issue with this workaround.


Create C++ Program to Remove all Characters in a String Except Alphab…

…ets.cpp
Congratulations on making a pull request!
Please make sure you check all the items.

[ ] The numbering of the company that you added starts with 1.
[ ] You have increased the Total Companies Added count.

…ets.cpp
Congratulations on making a pull request!
Please make sure you check all the items.

[ ] The numbering of the company that you added starts with 1.
[ ] You have increased the Total Companies Added count.

Hey man are you all right ?


feat: configurable h1 stripping for autogen titles

Adds a configuration option to strip out the first h1 in a document if its used for automatic title generation.
Prevents cases where a document winds up with two "titles" being rendered, like this:

I'm kind of confused on this one.
Wouldn't you just not render an H1 in your layout if you're going to auto gen titles by H1v

Mostly a convenience thing enabling more use of the first-h1-as-title feature. You can then use a layout level title, and do things like put a date next to it.
If thats not a strong enough justification, feel free to close this one haha, I'm not wedded to it


Work around https://bugs.swift.org/browse/SR-1927

Fixes https://github.com/apple/swift-protobuf/issues/508

New version up that immediately corrects the index so all uses are correct.


Enable breaking from selection construct.

There seems to be at least 1 driver that does not like generating conditional branches that exit from a selection construct.  That was fine until #1850 was merged, because we did not generate those types of instructions.
This issue is to revert part of #1850 until the driver has been fixed.  We fix for the problem with infinite loops will still be fixed by break out of loops, which seems fine.
This issue will remain open until all of #1850 is reenabled.

The latest version of merge return is better.  No need to generate this code anymore.


Is alphalens on PyPi ?

I am getting an error below, and a quick search on PYPI website did not find alphalens.
(finance-env)➜  Finance pip install alphalens
Collecting alphalens
  Could not find a version that satisfies the requirement alphalens (from versions: )
No matching distribution found for alphalens.

Python versions tried 2.7.13 and 3.60
Python 2.7.13 (default, Dec 19 2016, 08:09:44)
[GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-8<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
I installed alphalens successfully directly from Github (finance-env)➜  Finance pip install git+https://github.com/quantopian/alphalens

It's not on pypi yet but should be soon. In the mean-time you can install:
pip install git+https://github.com/quantopian/alphalens

Dup of https://github.com/quantopian/alphalens/issues/29.