Error 404 on npm install of 3.13.1 and Node 8

I tried multiple method install like none/global/save but no result, always same error with weird link :
Cannot download "https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz/linux-x64-57_binding.node":

HTTP error 404 Not Found

https://pastebin.com/3J5SNvdB

NPM version (npm -v): 5.0.4
Node version (node -v): 8.1.3
Node Process (node -p process.versions):

{ http_parser: '2.7.0',
  node: '8.1.3',
  v8: '5.8.283.41',
  uv: '1.12.0',
  zlib: '1.2.11',
  ares: '1.10.1-DEV',
  modules: '57',
  openssl: '1.0.2l',
  icu: '59.1',
  unicode: '9.0',
  cldr: '31.0.1',
  tz: '2017b' }

Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):

node-sass       https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz     (Wrapper)       [JavaScript]
libsass         3.3.6   (Sass Compiler) [C/C++]

npm node-sass versions (npm ls node-sass):

/home/storm1er/Documents/dev/wheelEvent
└──  extraneous error: Invalid version: "https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz

npm ERR! extraneous: node-sass /home/storm1er/Documents/dev/wheelEvent/node_modules/node-sass
npm ERR! error in /home/storm1er/Documents/dev/wheelEvent/node_modules/node-sass: Invalid version: "https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz"

[X] If you delete this text without following it, your issue will be closed.

Update node sass to v4.5 or down grade node to v6
On 1 Jul. 2017 6:52 pm, "storm1er"<EMAIL_ADDRESS>wrote:

I tried multiple method install like none/global/save but no result,
always same error with weird link :
Cannot download "https://github.com/sass/node-sass/releases/download/vhttps://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz/linux-x64-57_binding.node":
HTTP error 404 Not Found
https://pastebin.com/3J5SNvdB

NPM version (npm -v): 5.0.4
Node version (node -v): 8.1.3
Node Process (node -p process.versions):

{ http_parser: '2.7.0',
node: '8.1.3',
v8: '5.8.283.41',
uv: '1.12.0',
zlib: '1.2.11',
ares: '1.10.1-DEV',
modules: '57',
openssl: '1.0.2l',
icu: '59.1',
unicode: '9.0',
cldr: '31.0.1',
tz: '2017b' }

Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):

node-sass       https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz     (Wrapper)       [JavaScript]
libsass         3.3.6   (Sass Compiler) [C/C++]

npm node-sass versions (npm ls node-sass):

/home/storm1er/Documents/dev/wheelEvent
└──  extraneous error: Invalid version: "https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz
npm ERR! extraneous: node-sass /home/storm1er/Documents/dev/wheelEvent/node_modules/node-sass
npm ERR! error in /home/storm1er/Documents/dev/wheelEvent/node_modules/node-sass: Invalid version: "https://registry.npmjs.org/node-sass/-/node-sass-3.13.1.tgz"

If you delete this text without following it, your issue will be
closed.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sass/node-sass/issues/2034, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWIEqxyG5uscFt3SPboTfCKILN_KAks5sJgjEgaJpZM4OLQpS
.

This isn't really an acceptable solution.  Popular packages use 3.13.1 as a dependency which breaks any new installs, such as Laravel Elixir (2000+ installs/day: https://www.npmjs.com/package/laravel-elixir).  It seems pretty ridiculous that a legacy version would be removed knowing it would cause a boatload of cascading issues with node-sass being such a popular dependency.

@jeremybalog nothing was removed, there was never support for Node 8 in anything but release 4.5.3

@nschonni Then why are there numerous issues created saying just that?  The download links all return 404 and causes install failures.  Version 3.13.1 MUST have existed at some point, but is not listed as a release under releases anymore.  Something somewhere had to have been deleted, right?
Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node":

HTTP error 404 Not Found

^ actually I see the issue with that is node8 per the 57 ending, but even if I downgrade to node6 it still fails because 3.13.1 is not a version anymore...

^ actually I think I may have solved it--going to try installing node 7 and see if that does it.

@nschonni do you have any idea why some users seem to be stuck with 3.13.1?


Tutorial inadvertently blurs distinction between view models and DTOs

The sentence on this page "The subset of a model is usually referred to as a Data Transfer Object (DTO), input model, or view model" has confused at least one colleague into concluding that DTOs and view models are the same thing.  While the use of view models in ASP.NET server side code may be similar to DTOs, they are very different in general.  Would it be possible to remove or re-word this sentence please?  Thanks!

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

What did you have in mind? The or indicates they aren't necessarily the same thing. Sometimes you use a DTO, sometimes an input model, sometimes a view model.


Make post-processing backend configurable

It should be possible to configure the backend that is used for post-processing steps (similar to configuring the backend that is used by the Web API). By default we would want to use the same backend for all workflow executions. In some cases it might be desirable to use different backends (e.g., if benchmark runs are executed using a backend that depends on the account of the submitter).

Closed with commit #a171693ecc87d7295b991499790d400a3ea2d092


Producing video

Looking around the API, I didn't see a way to "Produce" a video, although it's possible that I missed it.
Camtasia has a "Batch Production" feature, but it looks like you have to specify each item in your batch manually... each time you want to produce a group of videos. I have a request into TechSmith to see if I'm missing something. That said, this would be a handy thing to manage via Python.
From a workflow perspective, I'd rather create all my videos and then build them all. I find that when I stop to wait for one to be rendered right after creating/editing it, I get distracted with other minutiae.

Sounds like a reasonable plan. I'll let you know if I hear anything interesting from TechSmith. It would make sense for the Camtasia app to support a simple command-line API for this. I have my fingers crossed.

From TechSmith, there isn't any command-line options or API for generating output. The best they suggested was a forum post indicating that you can drag-n-drop files onto the Batch Production dialog.
They directed me to their forum to post a request to add this as a feature, so I added my two cents to a post already asking for the same thing.

Ok, thanks for looking into this. We're looking into this a bit in-house,
but it'll likely involve applescript to meet our immediate needs.
On Wed, Sep 25, 2019 at 9:00 PM Scott Specker<EMAIL_ADDRESS>wrote:

From TechSmith, there isn't any command-line options or API for generating
output. The best they suggested was a forum post indicating that you can
drag-n-drop files onto the Batch Production dialog.
They directed me to their forum to post a request to add this as a
feature, so I added my two cents to a post already asking for the same
thing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sixty-north/python-camtasia/issues/10?email_source=notifications&email_token=AAATK6H7PJQU5CCTCHTD6T3QLO7NTA5CNFSM4I2A36L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7TFDCI#issuecomment-535187849,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAATK6HTFKFPDJ722ZZTZETQLO7NTANCNFSM4I2A36LQ
.


Install Prometheus

Install as described here.

Installing Prometheus might just setting enable_prometheus: "yes" in /etc/kolla/globals.yml. source

Installing Prometheus might just setting enable_prometheus: "yes" in /etc/kolla/globals.yml. source


Milestone 10: authorizations with cancancan

Pull Request Summary for Milestone 10 Completion

[x] All requirements completed.

Added:
/app/models/ability.rb

@ITurres: I have added the Ability class to define the user permissions.
This will allow the user to only edit and delete their own posts and comments.
It will also allow user's with the admin role to edit and delete any/all post or comment.

/db/migrate/20231214152949_add_role_to_user.rb

@ITurres: I have added the role column to the users table.

Modified:
/Gemfile and /Gemfile.lock

@ITurres: I have added the cancancan gem to the Gemfile and ran bundle install.

/README.md

@ITurres: I have the highlighted gems at the 'tech-stack' section.
@ITurres: check complete the 'authorization' task.

/app/controllers/posts_controller.rb

@ITurres: With the load_and_authorize_resource and destroy action, now we can delete posts.

/app/controllers/comments_controller.rb

@demesameneshoa: With the destroy action, now we can delete comments.

/app/models/post.rb

@ITurres: the update_posts_counter has been modified to accept a status of increment or decrement and update the posts_count accordingly.

/app/models/user.rb

@ITurres: All relationships with posts, comments and likes have been modified to dependent: :destroy to delete all associated posts and comments when a user is deleted.

/app/views/posts/show.html.erb

@ITurres: I have added the delete button to the posts show page.

/app/views/posts/_post.html.erb

@demasameneshoa: I have added the delete button to the posts partial.

/config/routes.rb

@ITurres && @demesameneshoa: We have added the :destroy action to the resources :posts and resources :comments routes.

/db/schema.rb

@ITurres: regenerated the schema with the new userrole column.

🛑 Important Note: due to 3 commits having been pushed to development you might miss the changes done to comments_controller.rb in the PR diff. You can check the changes here - commit #61ca4a2

Thank you for reviewing this PR. Feel free to reach out on Slack as Arturo (Arthur) Emanuel Guerra Iturres for any queries or further assistance. 🌟

Hi @V-Blaze! Thank you for your message! Given what you said, I will assume that you haven't read the full PR. If you kindly see the Important Notes made on it, I have mentioned that my coding partner has made changes and contributed to the project, but unfortunately, he committed those changes on the development branch, so we had to rebase it onto this branch, hence the changes diff aren't show here.
🛑 Please refer to these links for his changes:

https://github.com/ITurres/blog_app/commit/61ca4a2b871e717fbd507fe1cb9c971f1db00dec
https://github.com/ITurres/blog_app/commit/6f2abef61cbd6a5654c4b91d3c8a7732c2d0a477
https://github.com/ITurres/blog_app/commit/c74f57778556bf9bad88c38f53b169e4588d04d0

Hi @Shedrack-Sunday! Thank you for having reviewed and approved the PR 🤠! cheers!


not supported statement additions

@Cloud-Writer PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

@Cloud-Writer PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


[SEDONA-158] Fix wrong description about ST_GeometryN in the API docs

Did you read the Contributor Guide?

Yes, I have read Contributor Rules and Contributor Development Guide

Is this PR related to a JIRA ticket?

Yes, the URL of the assoicated JIRA ticket is https://issues.apache.org/jira/browse/SEDONA-158. The PR name follows the format [SEDONA-XXX] my subject.

What changes were proposed in this PR?

This PR fixes a wrong description about ST_GeometryN in the API document.

How was this patch tested?

Ran mkdocs serve and checked the generated document.

Did this PR include necessary documentation updates?

Yes, I have updated the documentation update.

Oh sorry, I've just noticed that I didn't have to file a new issue on JIRA since it's just a documentation fix.


'Potentially Dangerous alternative prefix'

As of essentials-1.12.2-1.2.0, forge is reporting warnings in the console:
[00:34:24] [main/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `crossroads_brazier`, expected `essentials`. This could be a intended override, but in most cases indicates a broken mod.
[00:34:24] [main/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `crossroads_slottedchest`, expected `essentials`. This could be a intended override, but in most cases indicates a broken mod.
[00:34:24] [main/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `crossroads_sortinghopper`, expected `essentials`. This could be a intended override, but in most cases indicates a broken mod.
[00:34:24] [main/WARN] [FML]: Potentially Dangerous alternative prefix `minecraft` for name `crossroads_itemchuteport`, expected `essentials`. This could be a intended override, but in most cases indicates a broken mod.
[00:34:24] [main/WARN] [FML]: Potentially Dangerous alternative prefix `crossroads` for name `port_extender`, expected `essentials`. This could be a intended override, but in most cases indicates a broken mod.

Some of those seem to overlap with your crossroads mod, so you probably need to fix both in one shot :).

This is a known "issue". The tile entity IDs were not changed when moving features from Crossroads, as changing them would corrupt existing worlds. As 1.13 will be a world-breaking update most likely anyway, the IDs will be changed to the correct mod ids.
In the meantime, having the wrong ID doesn't really break anything other than spamming startup logs.

Fixed in the 1.13 version.


Please tell me why I am reporting a cuda memory error when I perform data preprocessing according to your operation. Please help me. I will be grateful.

Please tell me why I am reporting a cuda memory error when I perform data preprocessing according to your operation. Please help me. I will be grateful.
(python310Tigre) yuanpeng@DESKTOP-6RR65PH:/mnt/d/谷歌下载/DIF-Net-main/DIF-Net-main/scripts$ ./test.sh
Namespace(name='dif-net', epoch=400, dst_list='knee_cbct', split='test', combine='mlp', num_views=10, view_offset=0, out_res=256, eval_npoint=100000, visualize=False)
mixed_dataset: ['knee_cbct']
输出dst_name: knee_cbct
CBCT_dataset, name: knee_cbct, split: test, len: 1.
load ckpt from /mnt/d/谷歌下载/DIF-Net-main/DIF-Net-main/scripts/logs/dif-net/ep_400.pth
DIF_Net, mid_ch: 128, combine: mlp
Traceback (most recent call last):
File "/mnt/d/谷歌下载/DIF-Net-main/DIF-Net-main/code/evaluate.py", line 120, in
metrics, results = eval_one_epoch(
File "/mnt/d/谷歌下载/DIF-Net-main/DIF-Net-main/code/evaluate.py", line 29, in eval_one_epoch
for item in loader:
File "/home/yuanpeng/conda/envs/python310Tigre/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 630, in next
data = self._next_data()
File "/home/yuanpeng/conda/envs/python310Tigre/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 676, in _next_data
data = _utils.pin_memory.pin_memory(data, self._pin_memory_device)
File "/home/yuanpeng/conda/envs/python310Tigre/lib/python3.10/site-packages/torch/utils/data/_utils/pin_memory.py", line 63, in pin_memory
return type(data)({k: pin_memory(sample, device) for k, sample in data.items()})  # type: ignore[call-arg]
File "/home/yuanpeng/conda/envs/python310Tigre/lib/python3.10/site-packages/torch/utils/data/_utils/pin_memory.py", line 63, in
return type(data)({k: pin_memory(sample, device) for k, sample in data.items()})  # type: ignore[call-arg]
File "/home/yuanpeng/conda/envs/python310Tigre/lib/python3.10/site-packages/torch/utils/data/_utils/pin_memory.py", line 58, in pin_memory
return data.pin_memory(device)
RuntimeError: CUDA error: out of memory
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with TORCH_USE_CUDA_DSA to enable device-side assertions.

It seems that your machine did not have enough memory (out of memory). To solve it, you may

reduce the number of views (num_views), e.g., set this to 6 to fewer.
use a smaller batch size.

It seems that your machine did not have enough memory (out of memory). To solve it, you may

reduce the number of views (num_views), e.g., set this to 6 to fewer.
use a smaller batch size.

But I am on a 3090ti machine with a video memory size of 24g. I preprocessed the data to a size of 256256256 according to your paper. During the data loading process, the data type has been reduced from float64 to float32, and the spacing is 0.8*0.8. *0.8 size, batch size is set to 1,
Setting num_views to 10 will exceed the video memory limit, and the maximum can only be set to 4. The data set used is the DirLab lung data set, with a total of 10 patients and 10 different phase data for each patient, a total of 100 sets of data.
According to the setting of 10 num views in your paper, 24g should be able to put it down, but it is not good after testing. My WeChat abc01072131, if you can help me solve it, I will be grateful.


Feature: Schedule tasks from http://localhost:8787/cdn-cgi/mf/scheduled

What version of Wrangler are you using?
0.0.24
What operating system are you using?
Linux
Describe the Bug
Would be nice to have support for manually triggering crontab tasks via a curl get request, similar to how wrangler1 (iirc) and miniflare support
https://miniflare.dev/core/scheduled

Admittedly we haven't put much work into the dx for scheduled workers in wrangler2, but we definitely want to do this soon. Thanks for filing this issue!

Added support for this in local dev mode via #738

@threepointone We don't have an API to trigger a cron trigger preview using wrangler dev. We'll need to engage with Runtime to conjure up something. wrangler1 can't preview a cron trigger.

Dropped some notes here for how we could potentially support it without runtime support https://github.com/cloudflare/wrangler2/issues/570#issuecomment-1084654222

@mattbdc could you share how wrangler1 does this? I'm actually not familiar with it and haven't heard so.

Sorry I was probably getting confused - exhausted - as I had looked at Wrangler1, Wranger2 via wrlanger@beta with a lower semver than Wranger1, Miniflare ootb, Miniflare with Wrangler 1 config, Miniflare breaking with Wrangler2 config....  And no solid story on what to use and when. Flashbacks to 1password versioning during the transition to unify everything, or finding the right google sku for chat 🤣
Thanks for the addition, I hope it all comes together


tests: make several txn tests less flaky

What is changed and how it works?

Issue Number: Close #12520
What's Changed:

This commit intends to make test_atomic_getting_max_ts_and_storing_memory_lock
and test_pessimistic_lock_check_epoch less flaky.

Instead of using pause and sleep to control order, this commit uses channels
and fail::callback_cfg to control the order more deterministically.

Check List
Tests

Integration test

Release note
None

cc @tonyxuqqi

/run-check-issue-triage-complete

/merge

/test


fix: await during DockerClientProviderStrategy test method

Current behavior
The current test method performs the following socket test:
https://github.com/testcontainers/testcontainers-java/blob/e35705bd373bed4c9dd54643e89f71af1ef20e48/core/src/main/java/org/testcontainers/dockerclient/DockerClientProviderStrategy.java#L209-L223
Using the config client.ping.timeout
client.ping.timeout = 5 Specifies for how long Testcontainers will try to connect to the Docker client to obtain valid info about the client before giving up and trying next strategy, if applicable (in seconds).

Consider the following scenario where I set client.ping.timeout=60 because my docker host and local machine are in different locales and I expect a network lag.
Duration timeout = Duration.ofMillis(200);
Awaitility
    .await()
    .atMost(TestcontainersConfiguration.getInstance().getClientPingTimeout(), TimeUnit.SECONDS) // do not wait more than 60 seconds
    .pollInterval(timeout) // check status every 200ms
    .pollDelay(Duration.ofSeconds(0)) // start checking immediately
    .ignoreExceptionsInstanceOf(SocketTimeoutException.class) // Ignore the expected timeout
    .untilAsserted(() -> socket.connect(socketAddress, (int) timeout.toMillis())); // Try to connect and timeout after 200ms

Currently, the client.ping.timeout configuration is essentially ignored because the socket will always timeout before atMost is ever reached.
Proposed Behavior
Instead, we should not provide a timeout to socket.connect.
If we take the same example as previously mentioned:
Awaitility
    .await()
    .atMost(TestcontainersConfiguration.getInstance().getClientPingTimeout(), TimeUnit.SECONDS)  // do not wait more than 60 seconds
    .pollInterval(Duration.ofMillis(200)) // check state every 200ms
    .pollDelay(Duration.ofSeconds(0)) // start checking immediately
    .untilAsserted(() -> socket.connect(socketAddress)); // Try to connect with an unlimited timeout

If the client.ping.timeout is reached, then Awaitility will interrupt the Runnable and still throw a ConditionTimeoutException.

Thanks for your contribution, @KyleAure !


Add shortcuts to rotate display

Add Ctrl+Left and Ctrl+Right shortcuts to rotate the scrcpy window.
Contrary to --lock-video-orientation (#1151), the rotation has no impact on recording, and can be changed dynamically (and immediately).
This provides an alternative solution for #218.
There are now 3 different (cumulative) rotations:

Ctrl+r to request the device to rotate between portrait and landscape
--lock-video-orientation to force a mirroring/recording orientation
Ctrl+← and Ctrl+→ to rotate the scrcpy window

Please review/test on your platform :) Feedbacks welcome.
I'll probably merge in dev soon.
Thank you

My phone must be a piece.
Screen rotation works with all apps other than my built in camera app. The SCRCPY window within my PC refuses to rotate out of vertical portrait layout to a horizontal landscape layout.
I've attached screenshot. The image shows multiple 'request to rotate' msgs but nothing happens.
Hopefully a screenshot doesn't violate tos :(

Maybe I failed to uninstall the old build correctly(?). Will keep trying when I'm free tomorrow. I have appointments remainder of the day and an evening event too.
Thx for a killer app nonetheless.

You requested to rotate to landscape, but the app refuses. This is expected for many camera apps.
The new feature in this PR consists in rotating the scrcpy window with Ctrl+LEFT and Ctrl+RIGHT.

Fetaure merged in dev.
I also added --rotation value to set the initial rotation.

Excellent app and great feature !
For whoever ends here, it seems to have been changed to ALT + LEFT and ALT + RIGHT (scrcpy 2.3.1, Ubuntu 22.04).

@perrette Yes, the default shortcuts modifier has been changed a long time ago (since v1.15 by #1598).
https://github.com/Genymobile/scrcpy/blob/master/doc/shortcuts.md


(maint) Enable Lint/UselessAccessModifier Rubocop cop

The Lint/UselessAccessModifier can let us know when we think we've marked something as public/protected/private, but haven't. Some examples of common reasons for things being not-actually private are Ruby syntax, or Ruby not actually supporting the thing in question being private at all.
We have a large number of violations of the Lint/UselessAccessModifier cop for a few different reasons:

Trying to mark constants private. Ruby doesn't do this.
Trying to mark classes private. Ruby doesn't do this.
Trying to mark class methods defined using def self.foo private. This doesn't work by placing the definition below private, and needs to be done by calling private_class_method :foo after the method definition.
Marking the following methods as public when the methods were already in a public context.
Trying to mark class methods as protected. Ruby doesn't do this, as it's effectively the same as a private class method.

In all cases where we were trying to mark a method as private, but not actually doing so, the method is now marked as private as long as it didn't break any tests.
In cases where we were redundantly marking things as public, or where making it private would have broken tests, the method is left as public.
In cases where we were trying to mark things as private and Ruby doesn't support having them as private, the decoration has been removed.

CLA signed by all contributors.


Add Staircase Problem to Recursion

Add the Staircase problem to recursion and state its implementation and problem statement

Kindly assign this issue to me and add the labels

You don't need to create multiple issues to collaborate

ok
I would suggest keep the issue open so that someone else can contribute

What I meant was to keep the issues in a generalized format

Okay


Add a github action for linting the go_modules/helpers code

I found https://github.com/dependabot/dependabot-core/pull/3583 by running golangci-lint against the go_modules/helpers directory.
It'd be nice to automate that as a dedicated linter through GitHub Actions to prevent issues like this from creeping in down the road...

See also https://github.com/dependabot/dependabot-core/issues/4448 which may completely remove the go_modules/helpers directory.


Use const/let instead of var

I've been bitten one too many times by var. Let's use const/let instead.

This sounds like good first-timer. I can give this a try if no one else is working on it.

that's great @oguzbilgic, thanks!

Ooops, sorry @oguzbilgic! I didn't see your comment until after I had already done the work. :(
Let's make a first-timer label so it'll be easy for people to find them in the future.


Change template to be more flexible

What kind of change does this PR introduce?
Flexibilizes the template text. Not all PR's need tests. Adds conditions that if a PR

is big or important
decreases coverage

Then it requires tests.
Did you add tests for your changes?
Nope.
Does this PR introduce a breaking change?
No :)

Codecov Report

Merging #244 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #244   +/-   ##
=======================================
  Coverage   70.25%   70.25%
=======================================
  Files          96       96
  Lines         659      659
  Branches      132      132
=======================================
  Hits          463      463
  Misses        163      163
  Partials       33       33

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 974126e...c3d2f4b. Read the comment docs.


lambda default in Adam doesn't make sense

Error in the paper[1], see discussion here: https://twitter.com/ogrisel/status/568316753593434112
[1] http://arxiv.org/pdf/1412.6980v2.pdf

Awesome! thanks louis


Error applying deployment...

Hi,
Thanks for this great config.  I'm having a bit of an issue getting to work...
The hal-deploy-apply job exists with this non-error:
│   Generating all Spinnaker profile files and endpoints: Building service endpoints                                                                                │
│ _ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Building service endpoints                                                                                │
│ - Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 1 custom profile for clouddriver                                                                             │
│ ^ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 1 custom profile for clouddriver                                                                             │
│ * Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 4 profiles and discovered 1 custom profile for deck                                                                                │
│ _ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 4 profiles and discovered 1 custom profile for deck                                                                                │
│ - Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 0 custom profiles for echo                                                                                │
│ ^ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 0 custom profiles for echo                                                                                │
│ * Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 1 custom profile for front50                                                                                │
│ _ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 1 custom profile for front50                                                                                │
│ - Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 1 custom profile for gate                                                                                │
│ ^ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 0 custom profiles for igor                                                                                │
│ * Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 2 profiles and discovered 0 custom profiles for igor                                                                                │
│ _ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ - Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ ^ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ * Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ _ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ - Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 3 profiles and discovered 1 custom profile for orca                                                                                │
│ ^ Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 20 profiles and discovered 0 custom profiles for rosco                                                                                │
│ * Apply deployment                                                                                │
│   Generating all Spinnaker profile files and endpoints: Generated 20 profiles and discovered 0 custom profiles for rosco                                                                                │
│ + Apply deployment                                                                                │
│   Success                                                                                │
│ + Run `hal deploy connect` to connect to Spinnaker.                                                                                │
│ ! ERROR Error encountered running script. See above output for more                                                                                │
│   details.                                                                                │
│

Although it says Success, none of the Spinnaker services are created.
If I run hal deploy apply from a shell in the spin-halyard pod I get a little bit more info about the failure:
+ Preparation complete... deploying Spinnaker
+ Get current deployment
  Success
+ Apply deployment
  Success
+ Run `hal deploy connect` to connect to Spinnaker.
/home/spinnaker/.hal/default/install.sh must be executed with root permissions; exiting
! ERROR Error encountered running script. See above output for more
  details.

I'm pretty sure I've run hal deploy apply without root before.  Is it just me having this issue?  Any suggestion how to work around?  I'm happy to fix it and make a PR, but I'm kind of stuck.

Derp... LocalDebian type was specified in halconfig.


unwrap html from CDATA

Soundcloud wraps the html in CDATA so it has to be stripped first.

Turns out Soundcloud is escaping the CDATA section.
<![CDATA[]]>


Modifier Tags

Add all the modifier tags, perhaps on a nested obj e.g. comment.modifiers.internal

Closed by 7ed59d2da76f4da8b6f0ff58255c04d029281f34


More verbose console

Sanjo, great work on stabilising jasmine, the tests are now not run multiple times and it's getting more clear on what is going on. What I'm still missing is information what tests are bing currently displayed. Having following does not tell me much about which tests ran.
0 specs, 0 failures
I20141205-10:14:23.906(11)? Finished in 0 seconds
I20141205-10:14:37.656(11)? Started
I20141205-10:14:37.656(11)?
I20141205-10:14:37.656(11)?
I20141205-10:14:37.656(11)? 0 specs, 0 failures
I20141205-10:14:37.656(11)? Finished in 0 seconds
W20141205-10:14:37.840(11)? (STDERR) connections property is deprecated. Use getConnections() method
I20141205-10:14:37.981(11)? Started
I20141205-10:14:38.042(11)? ....
I20141205-10:14:38.042(11)?
I20141205-10:14:38.042(11)? 4 specs, 0 failures
I20141205-10:14:38.043(11)? Finished in 0.062 seconds
I20141205-10:14:45.640(11)? Started

It would be nice to add a single line saying what tests are being displayed in the console.

Test reporting is no longer part of sanjo:jasmine.


README+=link to Tracing re: profiling-with-tracing

Definitely makes sense to add tracing there, thanks!
Do you think it would make sense to keep it alphabetized?
The tracing logo is very large on desktop. I'd rather keep it smaller since it's cosmetic only/not conveying information. We could just use the left half of the logo and crop down the whitespace around it? Or leave the logo out would be fine too.
It might make sense to very briefly summarize what tracing is and why it's useful since it's different from the others. I'll give it a try:

"The tracing backend injects tracing span!() macros that match the lifetime of the profiling macros. tracing uses callbacks rather than inlining specific pre-determined code, so it is more flexible than profiling (at the cost of more lines of code and potentially non-zero overhead). This allows existing and new tracing-compatible handlers to work with profiling."

Yw! :D

Do you think it would make sense to keep it alphabetized?

Probably yes, but in IMHO separate PR
Regarding rest:
(Could you) PTAL (please take another look)?


Allow Chewie controls to be positioned to allow for a larger safe area.

LGTM. Once it passes automated checks, then it'll get merged into master.

@jweidner-mbible please re-sync your change with master. Thanks.

@diegotori I just re-synced my change with master.

@diegotori Any idea on when this might get merged into master? :)

@caitlynbell399 rerunning the lint and format CI tasks. If they're green, then they'll look good to me

@jweidner-mbible looks like the CI checks failed. Please address them, or else I won't be able to merge.
Thanks.

@diegotori Committed a fix for the issue. Thank you for your help with this :)

LGTM. Merging.


Feature: Save different profiles per device, optionally when that device connects, switch to a preferred profile.

Disclaimer:
Please go through existing feature requests to avoid creating duplicates. If you found a similar issue please post a comment there. If you are uncertain your issue is related to others then create the issue. Obvious ignorance of this rule might get you blocked from posting new issues. Please tick the box below to show that you have followed the guideline.

[x] I have checked for a similar issue and sure it hasn't been reported before.

Description:
Requested if #171 #165 #67
Most people will have different settings depending on the audio device they are currently using.
Would be awesome for eqMac to automatically switch to the preferred profile.
User flow & interface:
A couple of questions to consider:

Which "effects"/settings would be saved for each profile? (Volume, Balance, EQ) and what about future effects?
How would the UI looks like? eqMac currently has quite compact UI, would have to hide all of this profile setting menu behind modals, unless the to be expanded.

Which "effects"/settings would be saved for each profile?
I think all of them, but the volume level must not be treated as a part of preset so user would have no need to change it every time to his linking. Standard system-like behaviour it needed. This also will fix to #248 248

How would the UI looks like?
I think current one if lovely. A drop-out with devices (which is there but doesn't work as a menu) will be handy enough.

But let me note one more interface suggestion - it would be much better if the interface will be a kind of fly-out menu dropping out of the icon, in iStats Menu style. Also this will solve the confusion with the X button which quits the app (another dedicated button for killing the process would be needed than though).
Taking different approach, you could save the current UI as a window, but adding a fast preset/device switching to icon drop-out menu.
Thank you for your work once again! Waiting for the automatic preset switching passionately, I hope it'll be there soon (even if paid upgrade)

It would also be nice if the presents have unique names. In my case I used the same name for different presets and you cannot tell which is what.

BTW I really like the app!

Which "effects"/settings would be saved for each profile?

I think all of them but the volume, it's level must not be treated as a part of preset so user would have no need to change it every time to his linking. Standard system-like behaviour it needed. This also will fix #248

How would the UI looks like?

I think current one if lovely. A drop-out with devices (which is there but doesn't work as a menu) will be handy enough.
But let me note one more interface suggestion - it would be much better if the interface will be a kind of fly-out menu dropping out of the icon, iStats Menu style. Also this will solve the confusion with the X button which quits the app (another dedicated button for killing the process would be needed than though).
Taking different approach, you could save the current UI as a window, but adding a fast preset/device switching to icon drop-out menu.
Thank you for your work once again! Waiting for the automatic preset switching passionately, I hope it'll be there soon (even if paid upgrade)

Great comment Intenditore, you have explained every improvement that I could expect for the app.

The fly-out menu dropping out of the icon, instead of the window with the X button.
Keeping the volume level on profile changes, but everything else could be saved for the profile.

I think that one issue that I'm having is also related with that topic.
Every time that I turn off my monitor, or take away my MacBook, the eqMac just close itself, making me go to applications reopen it, and select the playback device (monitor).
I'm the only one with that issue??
Congratulations for your great job, the app is just amazing and it's getting even better.

Which "effects"/settings would be saved for each profile? (Volume, Balance, EQ) and what about future effects?
Volume automatically gets handled by the OS (at least in Catalina), so I feel like balance and EQ would be the notables.

How would the UI looks like? eqMac currently has quite compact UI, would have to hide all of this profile setting menu behind modals, unless the to be expanded.
Not necessarily. It could be as simple as a small checkbox labeled "Remember device settings" nearby the dropdown selector. I would think you could handle checking/unchecking the box appropriately depending on the new device using something like onChange

@nodeful Thanks for the great release, I was aondering what you were working on :)
Anyway, how do you assign an EQ to a preset? I have tried creating the preset with my desired EQ set, or setting it while the preset is selected and then clicking save in the dialog.
But my EQ (Expert mode) never changes at all when I swap profiles.
Am I not seeing the right button? Or missing something else?

Sorry @Doridian I missed your question, I replied to a similar question here: https://github.com/bitgapp/eqMac/issues/732
Here's a copy paste:

I knew this would come up at some point as I agree the User Experience is not the most straight forward with this feature.
You know how when you have an EQ preset selected and you made a change the presets switches to Manual and you have  to save the preset again if you want those settings to apply to a preset.
With Super Presets the behaviour is a little different. If you have a Super Preset selected and you make any changes it is
instantly saved to the selected preset. So what probably happened in your case is that you created a preset for 1 setup,
then instantly started to create a setup for the 2nd preset, but this whole time you were applying the new settings to the
1st preset.
What you need to do once you created the first preset is press the "Deselect" button or create a new preset straight away. Only then start applying the settings that you want for the 2nd preset.
I hope this explains the behaviour, if you have a suggestion on how I can make this better, please let me know, I'm open to  discuss and modify this feature.

I will be closing this issue for house keeping, feel free to comment regardless on this issue or the one I referenced. Thank you for your cooperation and patience!

I don't understand, is this feature active? I can't find it anywhere.
I want to activate eqMac only on the external monitor.
Can you explain how? Thanks

I also want to know the answer

I don't understand, is this feature active? I can't find it anywhere. I want to activate eqMac only on the external monitor.
Can you explain how? Thanks

I believe I found the solution, you should use Super Preset, create different profiles, say one for you Mac and one for your headphone, then in the equalizer select a different profile for each, say for Mac use the default one, that is flat, and for your headphone use a custom eq, now go switch between audio device output, you will see each time to switch there, it will also switch in the eqMac.


RealNVP can't reconstruct samples

Hi!
I was playing with RealNVP and tried to reconstruct samples after a forward and backward pass through the flow. After training the network on moons dataset, I ran the following program
x, label = datasets.make_moons(1000, noise=.05)
x = torch.from_numpy(x.astype(np.float32))

with torch.no_grad():
    z, _ = model._transform(x, context=torch.nn.Identity()(None))
    x_hat, _ = model._transform(z, context=torch.nn.Identity()(None))

The following plots show the distribution of the points after each pass
Original x:

Normalized z:

Reconstruction x_hat:

The forward pass looks great, since it forms a normal distribution. However, the backward pass doesn't reconstruct the input x_hat similar to x as expected. Any feedback on what is happening would be of great help. Thanks!

Double-checking my code I just realized my program was performing two forward passes instead of a forward and backward pass. After changing the last line to x_hat, _ = model._transform.inverse(z, context=torch.nn.Identity()(None)) the reconstruction was perfect.
Sorry for the false alarm, I'm closing this issue.


Migrate test code to TypeScript

I have renamed the files to .ts but tsconfig.json is not including them so it is not working properly.

I know use ts-node so the test code is now interpreted as TypeScript but the UMLWebWidget distribution is missing its type information and the test code is not using type annotation.


Fix AM/PM for times with hour of 12

What
Change condition for when to use AM vs PM
Why
Currently a time of 12:xx is given suffix of AM which is incorrect. 00:xx is AM, 12:xx is PM.

Are you really familiar with all those languages you modified, @robtpaton ? Are you sure they all use the same logic?
Also, your modification would output "00:15 AM", "06:15 AM" and "00:15 PM". If we're gonna fix it, I think we should fix it properly.

Are you really familiar with all those languages you modified, @robtpaton ? Are you sure they all use the same logic?

No, only English! Seems like a good thing to fix this in as many languages as possible at the same time. I see labels have automatically been added to the PR for the other languages, I'll look at how to tag language leaders of each of those for reviewing.

Also, your modification would output "00:15 AM", "06:15 AM" and "00:15 PM". If we're gonna fix it, I think we should fix it properly.

Good point 🤦

I'll look at how to tag language leaders of each of those for reviewing.

They've already been tagged. My point was that it's not a good idea to have a multi-language PR.

I'll look at how to tag language leaders of each of those for reviewing.

They've already been tagged. My point was that it's not a good idea to have a multi-language PR.

OK, I took an educated guess that the setup is similar for these languages, since the existing logic was similar, but I see your point and accept the contributing guide does say to prefer single language PRs.
My follow-up question would be: what is the best mechanism for raising "I think this might be wrong across multiple languages?" type issues? Maybe we could add some more nuance/details in the contributing guidelines.
Have taken another look at the logic also 👍

what is the best mechanism for raising "I think this might be wrong across multiple languages?"

Usually language leaders keep an eye out for English changes. To be sure, you could add an issue and tag it with other language tags. The language leaders will then be assigned. I can't remember if automatically or not.

Related issue: https://github.com/home-assistant/core/issues/134224

Looks good to mean. I'd like to hear from the other language leaders, so let's give it a little time. This fix needs to be in the intents bump for the next release though.

Also here to chime in that English looks good. Something worth flagging (but I don’t think we can address yet) is that the way localization of times work is not necessarily directly tied to language, though I think it’s often enough.
It seems to me like it would be better for Home Assistant, which knows the localization format of the user, to pass a localized string back to the assistant rather than unlocalized numbers.


Register: Two password fields for confirmation

On register, the password field should be duplicated

I agree ^^


Inserting missing text and link to TAP

@alfredmyers,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


ModSecurity strips POST data information from request in DetectionOnly mode

MODSEC-390: For a Dutch bank we purchased the commercial ruleset from TrustWave labs. In the process of setting-up the ModSecurity in combination with IIS we hit an issue which we cannot solve and basically renders the ModSecurity module unusable for our environment.
When enabling ModSecurity for the default virtual host, POST parameters are no longer passed to the JBoss application server via the mod_jk plugin.
We deployed on this virtual host the mod_jk ISAPI module which works as expected when ModSecurity is disabled.
After enabling ModSecurity (DetectionOnly mode), access to the the login-page via Java ServerFaces works fine (and access to all other dynamic content which does not require POST information to be sent) until we try to submit for instance the username.
The submitted username is received by IIS (confirmed this through our Web Debugging Proxy (Charles)), but the POST parameter data itself is empty when received by our application (confirmed by the log files produced by the application).
In the Windows EventLog Application log there are no ModSecurity errors, only warnings concerning rules have been hit.
We installed ModSecurity using the MSI installer on IIS.
Installation seems successful, we see the in Windows EventLogger the ModSecurity Information logs:
ModSecurity for IIS (STABLE)/2.7.3 (http://www.modsecurity.org/) configured.
ModSecurity: APR compiled version="1.4.6"; loaded version="1.4.6"
ModSecurity: PCRE compiled version="8.30 "; loaded version="8.30 2012-02-04"
ModSecurity: LUA compiled version="Lua 5.1"
ModSecurity: LIBXML compiled version="2.7.7"
Please advice,
All the best,
Robin Huiser

SecStreamInBodyInspection On    worked on IIS7.5 ARR2.5

We are using Microsoft Dynamics NAV 2016 Web Client but POST parameters won't forward correctly when SecRequestBodyAccess is set as On.
Adding SecStreamInBodyInspection On to config file works on IIS8.5.

SecStreamInBodyInspection On to config file works on IIS8.5, Server 201212 R2 (in Azure)
Also I checked that POSTed variables were still checked : they are J

SecStreamInBodyInspection should be turned on for IIS.
As for Nginx, support for this module in ModSecurity 2.9.x branch is deprecated. This shouldn't be a concern with libModSecurity.
Thanks!


feat(module:input-number): support formatter & parser

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage decreased (-0.03%) to 40.828% when pulling 908ffd782ad2b5304ca5c59a5675dc84c2540a2d on vthinkxie:support-input-number-formater into 504fdc8c57436b46e2914105c7f394025e783260 on NG-ZORRO:master.


Dashboard client services do not respect receive_timeout parameter

I am using ROS2 Humble, and I have installed the binary driver in ubuntu 22.04 as described in the README. I am connected to a UR5 robot simulated with the CB3 URSim docker image.
After launching the ur_control.launch.py launch file, I then ran the command:
ros2 param set /dashboard_client receive_timeout 4.0
Then I tried to load a program on the UR5 dashboard with ros2 service call /dashboard_client/load_program ur_dashboard_msgs/srv/Load "filename: '/G-253/ros_control_v2.urp'"
I am currently running ROS2 from inside an agonizingly slow linux VM, so that service call sometimes takes more than 1 second to complete. Thus, I get the following error:
waiting for service to become available...
requester: making request: ur_dashboard_msgs.srv.Load_Request(filename='/G-253/ros_control_v2.urp')

response:
ur_dashboard_msgs.srv.Load_Response(answer='Did not receive answer from dashboard server in time. Disconnecting from dashboard server.(Configured timeout: 1 sec)', success=False)

As can be seen from the error, the timeout is configured at 1 second despite setting it to 4 seconds previously. I have tried setting the timeout parameter to even higher values and I still sometimes receive the same error. It is clear that the timeout is not actually being set to the desired value.
Any thoughts?

Thanks for reporting this. We'll try to reproduce and investigate this further. If you encounter something in the meantime, please let us know.

Experiencing the same. We're setting it in the ur_control.launch.py.
dashboard_client_node = Node(         package="ur_robot_driver",         condition=IfCondition(launch_dashboard_client)         and UnlessCondition(use_fake_hardware),         executable="dashboard_client",         name="dashboard_client",         output="screen",         emulate_tty=True,         parameters=[{"robot_ip": robot_ip, "receive_timeout": 240.0}],     )

It looks like its reset to 1 second in the URCL connect function:
  // Reset read timeout to "normal" socket timeout
  tv.tv_sec = 1;
  tv.tv_usec = 0;
  TCPSocket::setReceiveTimeout(tv);

This should get fixed by https://github.com/UniversalRobots/Universal_Robots_Client_Library/pull/171

Since the PR has been merged and the issue is quite old, I will close this.
Feel free to re-open, if still relevant!


Are there plans to add this library to the conan center?

https://conan.io
Conan Center
https://conan.io/center/

Yes, we plan to. I'll keep this issue as a reminder.

I have a recipe ready, I will probably create a pull request within a few days. I wanted to wait for the initial surge of fixes to settle down.

Looks like someone beat me to the punch, it seems it's already there: https://github.com/conan-io/conan-center-index/pull/13499

Issue solved: https://github.com/conan-io/conan-center-index/pull/13499

@stephenberry FYI I think you can remove the link to my recipe in the README. The one in Conan Center is actually maintained, and should be what people use.

@Ahajha, thanks! Will do.


Please Add Option To Allow Dorako UI Interactive Token Coloring

In the newest 1.4 version you haven't added a option to NOT automatically turn off Dorako UI's Colorize PF2e Interactive Tooltip's setting.

This might look cluttered, but to me, it looks WAY more legible despite the messiness. Can this feature please be a toggleable thing rather than a hard set one? It ain't pretty, but to me, this module isn't about looking pretty, it's about functionality. Which is why I thought the Toggleability in the main sheets was a smart middle-ground.
Please give me back my pink brain! 🧠

The blandness hurts my soul. 😭

Added again in v1.4.1, with a new settings option


Add missing recursive vistor on copied import type nodes

And swap to using the cached (and much more robust) getSpecifierForModuleSymbol for generating new specifiers while we're at it (so we can more often know to reuse the input node when the specifier matches).
Fixes #58159

I can confirm that this fixes the issue in our codebase


Create New Applicant is not smooth -

When you create a new applicant, the screens go:
enter name
and then the output is a screen that says lots of information is missing and then you have to hit edit.
That doesn't feel super smooth to me. Why doesn't it just take you to the edit.

Buttons to add/remove income sources on the onboarding page seems a bit too in-depth for the onboarding page, and more like something that should be implemented in the income section of the main form.  So, I'm going to close this issue, and save the income updates for #179.


Adds a last compiled date to the homepage

@arnavs as of sphinxcontrib-jupyter=0.5 we now include timestamp information in all notebook metadata. This can enable a `last compiled feature for the website if you wish to enable it. On the python side it looks like:

here is the julia screenshot

Thanks @DrDrij @mmcky, looks good to me.


directive from class on svg element

I'm trying to create test directive on SVG element with class selector and it doesn't work. It works as attribute or element.
app.directive('test', function(){
  return {
    restrict: 'AEC',
    templateNamespace: 'svg',
    template: '<svg><circle cx="10" cy="10" r="10" /></svg>',
    replace: true
  };
})

<svg class='test' />      #bug
<svg test />              #ok
<test></test>             #ok

  #ok

I created a plunker: http://plnkr.co/edit/XJevcJgrYy3l5MvOqg59?p=preview

Ah, it looks like node.className for an svg gives us an SvgAnimatedString object:
{
  animVal: "test",
  baseVal: "test"
}

So when we get to the step where we're checking to see if node.className is a string the test fails and we don't invoke addDirective() on the class. This explains why your plunker works when applying the class to a div, but not a svg.

Here is the code block in the $compile service where the check occurs and is failing.

@aabenoja Thanks for investigating. As far as I am concerned nothing speaks against fixing this. Unless it hurts performance. @caitp you have done lots of stuff for svg, can you take a look?

if I recall, we weren't going to fix this because class-directives were not widely used. But it may have just been comment directives that I'm thinking of.

I'm not very familiar with svgs. What is the difference in using animVal and baseVal?

animVal is as it sounds like, the value during animation --- it is the same as the baseVal in other cases, though


Feedback doesn't work on mobile+Android+Chrome

Feedback doesn't work on mobile+Android+Chrome
As per title. Please see attached screenshot.

fbitem-67cbf865735ab20856e1e6649eab1c4073bc341e
Reported by: @kbraak
System: Firefox 51.0.0 / Mac OS X 10.10.0
Referer: https://demo.gbif.org/
Window size: width 1569 - height 968
API log
Site log

No and it should. but the mobile menu isn't fully implemented yet. thanks for reporting


Finish sign in/sign out ui

Made it so when users hit "sign in" on the nav bar it renders the google sign in pop-up automatically and when users hit "sign out" on the nav bar it signs them out immediately

https://user-images.githubusercontent.com/36006871/149873653-6f34b0e4-19aa-4ad8-a2d4-e108d33108f4.mov
Here's the screen recording!


Colorblind comparing in shaders

I made a shader that checks if pixel has a given color and if yes, it replaces it with another one (so basically a color replacement). The issue is that it doesn't work for all colors. OpenGL ignores some colors as if it couldn't see them. Example one is RGB: 0/91/32 (and even ones with similar values).
Below the example shader and program. Link to example: https://www.dropbox.com/s/sjkw70bjsdzpde4/colorblind.zip?dl=0
Shader code:
uniform sampler2D in_Texture;

varying vec2 var_TexCoord;

void main()
{
  vec4 color = texture2D(in_Texture, var_TexCoord);

  vec4 test1 = vec4(0.0/255.0, 91.0/255.0, 32.0/255.0, 1); //the bugged color
  vec4 test2 = vec4(44.0/255.0, 210.0/255.0, 190.0/255.0, 1); //random working color

  if (color == test1) {
    gl_FragColor = vec4(1,1,1,1); //change to white if green
    return;
  }
  else if (color == test2) {
    gl_FragColor = vec4(0,0,0,1); //change to black if cyan
    return;
  }
  else
    gl_FragColor = color;
}

Program code:
require 'gosu'
require 'ashton'
include Gosu

class GameWindow < Gosu::Window
  def initialize
    super(640, 480, false)
    self.caption = "Test Game"

    @image = Image.new(self,'image.png')

    shader = Ashton::Shader.new(fragment: "shader.frag") #initialize shader

    new=Ashton::Texture.new<EMAIL_ADDRESS>#make a texture for processing
    shader.enable
    new.render{@image.draw(0,@image.height,0,1,-1)} #draw image on texture using shader
    shader.disable
    @image=new.to_image #replace old image with new one
  end

  def draw
    @image.draw(32,32,0) #draw the resulting image
    #cyan (44,210,190) is replaced with black
    #green (0,91,32) is replaced with wh... oh ,wait. It's not replaced :(
  end
end

GameWindow.new.show

Original image:

Result:

Concluson: it replaces one of colors (bottom-right), but can't change the one in background.
My specs: Win 7 x64 GeForce GT540M

I've merged the 4fv "hack". Feel free to give me a 3fv pull request too.

I should close this though, since the issue was with rounding by GLSL, not Ashton.


Claims identity schema

There is this list of identity schema on this page

oid > http://schemas.microsoft.com/identity/claims/objectidentifier
tid > http://schemas.microsoft.com/identity/claims/tenantid
unique_name > http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name
upn > http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn

Is it fine to replace with https as this causes codeql warnings?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a5d00031-82e8-a8ee-0a66-e9b84231e837
Version Independent ID: 9a9da08f-83e2-c493-61af-c4b5316c6f8e
Content: Work with claim-based identities in multitenant applications - Azure Architecture Center
Content Source: docs/multitenant-identity/claims.md
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 355890

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 355890

No, sorry, these are schema identifiers and are not URLs.  They looks like URLs, but they are technically URIs and schemas do not need to resolve to a network location.  They are defined by the schema owner.  You can find the common schema ids at https://learn.microsoft.com/azure/active-directory/develop/reference-saml-tokens.  Please set your tooling to make an exception on these.


(c) on LICENSE

LICENSE should ready (c) University of Kansas, because the work was either directed research, or funded research. See wakarusa for an example.

Thanks for this, I tend to forget about these important logistics.


Handle older assay IDs

Please add the following
  # Handle older assay probe labels
  if (pkcData[["RTS_ID"]][1] %like% "^RTS" &
    probeAssay[["RTS_ID"]][1] %like% "^RNA") {
    # replace RTS00 with RNA in probeAssay[["RTS_ID"]]
    probeAssay[["RTS_ID"]] <- gsub("^RNA", "RTS00", probeAssay[["RTS_ID"]])
  }

https://github.com/andrewrech/GeomxTools/commit/d567c3590cffc1afd8387e09d55a0a3942b33780
to handle assays that use the older probe labels.
thanks
Andrew

Hi Andrew,
Thanks for this fix, we will consider this for the next release.
What PKC are you using so we can make sure future GeomxTools releases are fully compatible with legacy files still in use?
Maddy

Gotcha. So older DCC files and a newer PKC file. I will add that to our internal bug so we can test the correct situation.
Thanks,
Maddy

Has this been fixed? I get the following error when I try the Mm_R_NGS_WTA_v1.0.pkc which I'm assuming is due to incompatibility of pic file and the dcc files.
Error in data.frame(RTS_ID = pkcData[zeroProbes, "RTS_ID"], Count = rep(0,  :
  arguments imply differing number of rows: 20175, 0

The code I'm trying is:
> dccSet <-
+     suppressWarnings(readNanoStringGeoMxSet(dccFiles = dccFiles,
+                            pkcFiles = PKCFiles,
+                            phenoDataFile = SampleAnnotationFile,
+                            phenoDataSheet = "SegmentProperties",
+                            phenoDataDccColName = "SegmentDisplayName"))

Many thanks for your time
Shani.

Hi @shaniAmare,
Yours might be a different issue. Our customer support team will be able to help you with this. Please email<EMAIL_ADDRESS>with your issue.
Thanks,
Maddy


FEAT enable logging with colors

Is your feature request related to a problem? Please describe.
When enabling verbose mode of an orchestrator (e.g., EndTokenRedTeamingOrchestrator) the printed logs are sometimes tricky to read as it's all in the same color.
Describe the solution you'd like
It would be nice to enable different colors for system prompts, user prompts, assistant prompts, but also separate colors per conversation (e.g., "user" in the red teaming chat conversation is different from "user" in the target conversation).
Additionally, this should be possible to turn on/off since people with difficulty to see colors may prefer the single color experience.
Describe alternatives you've considered, if relevant
Not sure if this is the best approach but it's a starting point: https://stackoverflow.com/questions/384076/how-can-i-color-python-logging-output#:~:text=A Python 3 solution%2C with no additional packages,%3D logging.StreamHandler() ch.setLevel(logging.DEBUG) ... 3 3. And use%3A
It might be best to try a few options and report back in this issue before starting a PR as maintainer will want to chime in on the best solution.
Additional context

We used to have color printed logs in a notebook (see this notebook: https://github.com/Azure/PyRIT/blob/e378c824d4a81f846514f453a6df538df480b95f/doc/demo/2_multiturn_strategies.ipynb) but it was not part of the package code, only in an example.

Please assign this one to me @romanlutz

Hi @romanlutz
I'm currently giving this one a go and would like to get some feedback on a few things:

Do you want to prevent including extra libraries?

I see that in multi-turn attack results, colorama is being used to print the conversation. Judging from the issue here, I would've guessed you wanted to have an implementation without additional libraries.

What would the preferred "configurability" of the loggers be?

Should enabling the verbosity of an orchestrator automatically make related targets verbose as well, or should the verbosity of targets be configurable on their own?

Is the file https://github.com/Azure/PyRIT/blob/main/pyrit/common/logger.py just something that's left over from trying out logging before?

My first approach (WIP, using just the logging library)
A logging class to set it all up, the setup_logging function can be called in scripts using PyRIT and the top-level logger is named "ai-red-team" (I just used what I found in logger.py for now):
import logging
import logging.config
from pyrit.common.path import LOG_PATH
from pyrit.common.color_formatter import ColorFormatter
import os
import sys

format = '[%(asctime)s][%(name)s][%(levelname)s][%(message)s]'

def supports_color():
    """
    Returns True if the running system's terminal supports color, and False otherwise.
    """
    if sys.platform.startswith('win'):
        color_supported = sys.getwindowsversion().major >= 10 or 'ANSICON' in os.environ or os.getenv('COLORTERM') is not None
    else:
        color_supported = True

    is_a_tty = hasattr(sys.stdout, 'isatty') and sys.stdout.isatty()
    return color_supported and is_a_tty

def setup_logging(default_level=logging.INFO, use_color=False):
    logging_config = {
        'version': 1,
        'disable_existing_loggers': False,
        'formatters': {
            'default': {
                'format': format,
            },
            'console': {
                '()': ColorFormatter if use_color and supports_color() else logging.Formatter,
                'format': format,
            }
        },
        'handlers': {
            'file': {
                'class': 'logging.FileHandler',
                'level': 'DEBUG',
                'formatter': 'default',
                'filename': LOG_PATH,
                'mode': 'a+'
            },
            'console': {
                'class': 'logging.StreamHandler',
                'level': 'INFO',
                'formatter': 'console',
            },
        },
        'loggers': {
            'ai-red-team': {
                'level': default_level,
                'handlers': ['console', 'file'],
                'propagate': True,
            },
        },
    }
    logging.config.dictConfig(logging_config)

The ColorFormatter picks a color based on log level and keywords:
import logging

class ColorFormatter(logging.Formatter):

    # ANSI color codes
    bold_blue = "\x1b[1;34m"
    bold_cyan = "\x1b[1;36m"
    bold_grey = "\x1b[1;30m"
    bold_green = "\x1b[1;32m"
    bold_magenta = "\x1b[1;35m"
    bold_red = "\x1b[31;1m"
    bold_white = "\x1b[1;37m"
    bold_yellow = "\x1b[1;33m"
    blue = "\x1b[34;20m"
    cyan = "\x1b[36;20m"
    green = "\x1b[32;20m"
    grey = "\x1b[38;20m"
    magenta = "\x1b[35;20m"
    red = "\x1b[31;20m"
    reset = "\x1b[0m"
    white = "\x1b[37;20m"
    yellow = "\x1b[33;20m"

    # The desired structural format
    format_str = '[%(asctime)s][%(name)s][%(levelname)s][%(message)s]'

    keyword_colors = {
        'user:': red,
        'assistant:': yellow,
    }

    level_colors = {
        logging.DEBUG: cyan,
        logging.INFO: blue,
        logging.WARNING: yellow,
        logging.ERROR: red,
        logging.CRITICAL: bold_red
    }

    def format(self, record):
        message = record.getMessage()
        color = self.grey  # Default color

        # Check for log level
        if record.levelno in self.level_colors:
            color = self.level_colors[record.levelno]

        # Check for keyword in message
        for keyword, color_code in self.keyword_colors.items():
            if keyword in message:
                color = color_code
                break

        log_fmt = color + self.format_str + self.reset
        formatter = logging.Formatter(log_fmt)
        return formatter.format(record)

Hi @lesydimitri ! These are excellent points and questions for clarification. I've assigned the item to you for now so that nobody else thinks this is up for grabs 😄
I'll say upfront that my thinking on this has evolved a little in the last few weeks and that may bring some clarity to these points (and hopefully make the solution simpler than I had originally thought).
To your questions:

Do you want to prevent including extra libraries?

As much as possible, it's always preferable not to add new dependencies. That said, if it's a light dependency (e.g., one without additional downstream ones) then it's something we can discuss. In any case, I would suggest you raise it with maintainers (e.g., here! or in a PR) before spending a lot of time including it in your implementation to avoid potential waste of time.
Did you have any particular ones in mind?

What would the preferred "configurability" of the loggers be?
Should enabling the verbosity of an orchestrator automatically make related targets verbose as well, or should the verbosity of targets be configurable on their own?

This is what I've been thinking about a lot... Every orchestrator has the verbose arg which, at the end of the day, just sets global logging levels. So why even have that at the orchestrator level? It seems way more intuitive to set that globally like everyone else does in Python. We do something similar with memory configuration now, too.

Is the file https://github.com/Azure/PyRIT/blob/main/pyrit/common/logger.py just something that's left over from trying out logging before?

It's definitely a file that's left over from something someone tried quite a while ago. Feel free to remove or edit. Nothing in common is loaded by default, so I wonder if this is even used...

Regarding the implementation proposal:

I'm not sure I understand the difference between the handlers. It makes sense that we output to console and also write to a file, perhaps even at different levels by default (DEBUG for file, INFO for console) but the loggers section seems to separately also set the log level to whatever the argument is set to. I don't think I understand what happens here.
Understanding aside, the setup_logging function could be something we call at the start of every notebook. Maybe by default it's set to INFO but if people want more details they can set DEBUG.
I'm happy with colors like this for debug output. In the existing print_conversation methods we typically use different colors for the various targets that send messages. That makes sense there, and I think the colors per level make sense here, too.
[This is probably worth ignoring for now and could potentially be a separate item if anyone finds this useful:] Of course, if there's a way to have variations for the various targets that would be quite nice, too. Usually, the messages from targets all happen on the INFO level which is set to blue. Maybe one color for the user role and one for assistant would work, but then again this wouldn't be ideal for orchestrators that talk to multiple targets. Hmm... If it is possible to assign colors based on substrings (let's say prefixes) of the records then we could maybe standardize to something like <role> / <target>, e.g., user / objective_target -> green, assistant / objective_target -> blue, `user / adversarial_chat" -> orange, etc. but that standardization would require quite a few changes, too... just mentioning here in case you have any idea if that sort of thing is possible so that we can capture it for the future.


Task: Create a device twin configuration for the models

US #373
The device model configuration should be used to update device properties by targeting devices using their tags.

Please add :

[ ] Tag value in Target conditions
[ ] Property should use a select for the name
[ ] Property value input must be dependant to the property type (see device detail page for exemple)


deps: Update patch-level versions of Erlang & Elixir

No ticket

erlang from <IP_ADDRESS> to <IP_ADDRESS>
elixir from 1.13.3 to 1.13.4

Successful build and deploy

@lemald I think this should hopefully be quick, but please let me know if you are too busy.


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
Arm.GnuArmEmbeddedToolchain
Package Version
10 2021.10
Please describe the changes you would like to see
There is a few new versions available:
12.2 is what I see here: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
The gnu-rm version that you have on winget was deprecated (see https://developer.arm.com/downloads/-/gnu-rm).

Gday, just noting, the version currently on winget is officially deprecated.

Gday, just noting, the version currently on winget is officially deprecated.

Is the new software "Arm Gnu Toolchain" a direct replacement for "Arm Gnu Embedded Toolchain" or can they exist side by side on the same machine?

You can have them both, in the same way you could have 10.3 + 9.3 etc...
Often times people will want multiple versions in order to re-compile something with the same tooling.

I will try submit a PR :)

https://github.com/microsoft/winget-pkgs/pull/110755


Add toggle for basing encounter generation/difficulty-display on "Total XP" instead of "Adjusted XP"

It would be nice if there were a toggle for basing encounter generation/difficulty-display on the DMG "Total XP" instead of the (so far as I can tell) KFC original "Adjusted XP". I'm using straight DMG rules, so having to do the manual conversion adds another step to every encounter made. To KFC's credit it does display all the information required for that, but it's still a thing which could easily be made less troublesome.
Edit: To clarify, there's stuff like the single-monsters, which, per DMG, should have an x1 modifier, but seem to have an x0.5 in KFC. The enemy count multipliers for higher-numbers of stuff also seem to be slightly different. Hence the request for just being able to base it on Total.

Read the DMG. Specifically the part about large groups.


Add dataframe statement params to query executions in dataframe writer

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #NNNN

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Follow up https://github.com/snowflakedb/snowpark-python/pull/755. For credit usage when queries are executed via writer APIs.

I have read the CLA Document and I hereby sign the CLA

recheck


I bought OpenManipulator.

I bought an OpenManipulator-X. How can I go about to change the source code on
Arduino to make the Gripper Open wider.
I want to move the gripper to  90 instead of 0.009

I'm using the Processing 3 software ( hand guide) to move the gripper open and close.
the Gripper is able to open very small angle. How can i go about to modify the source code to allow the
Gripper open wider angle. I need help or advice.

Hi @zebracheng
Thank you for using our OpenMANIPULATOR-X.
The Unit of the gripper movement is 'm', not 'mm', and it means the moving distance of one gripper finger.
And the range of the grippper position is -0.009m to 0.009m. The gripper position of the open state is 0.009m, and it of close state is -0.009mm.
So that the 0.009 means that the gripper fingers gap is about 4cm.
And that is maximum value.
Please check that the gap is 4cm at the open state.
If it is not 4cm, It may be a situation that the gripper dynamixel does not move more due to the current limit.
If so, it is possible that the 4 Flange bush screws on the gripper are overtightened. Please loosen that a little.
Another way is to raise the current limit. please add below codes to source code.
(under the open_manipulator.initOpenManipulator(platform_state); of the void setup() function in the .ino file)
STRING gripper_dxl_opt_arg[2];
void *p_gripper_dxl_opt_arg = &gripper_dxl_opt_arg;
gripper_dxl_opt_arg[0] = "Goal_Current";
gripper_dxl_opt_arg[1] = "300";
open_manipulator_.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);

The value '300' can be changed in the range of 200 to 1193. Increasing this value increases the gripping force output by the Dynamixel.

Thanks so much for getting me so quickly.
what I mean is that I will not use the gripper in my application. I will remove the gripper off the the

i will remove the gripper off from the end of tool and leave the servo ID 15 attached on the end of tool. my application is to able  to move the server 15 to 0 degree or negative or pasitive 90 degree.  i did some testing under U2D2 hardware using the application i was able to move the ID15 to zero degree or +90 or -90 degree. My application is to pick up some small label and turn the label in landscape direction and apply label on the box. if this idea work I will by 3 to 4 Robots. I will try the code that you mentioned to see if it  will work. it is hard to send mail. is there any way I can chat on the phone with you. This is just and idea to see if the OpenMani Robot will work. Then later I will and modify the end of tooling and add IO on the Open CR using Arduino hardware. The Robot hardware is good but the software is limited me to move on. i have to prove that my concept is working then my manager will allow me to buy the pro version Robots because it has longer pay load and longer reach

I remove the left and right grippers and use the hand guide software it is still move only 0.009 or -0.009.
so it not related to over tie or current. Some how the code is set to 0.009 and -0.009.  is there a way that you can show me how to change to larger value allow me to move to like 0 degree or +90 or -90 by using hand guide teach.

Hi again,
Unfortunately, I can't directly contact you on phone or chat due to my another busy works, but I will reply asap on mails.
First of all, to apply your application, you have to add another tool such as vacuum tool at the end of dynamixel ID15. I think the vacuum tool is best choise to pick up the labels. Is that passible?
If you can, OpenMANIPUALTOR can work enough on your application.
Please refer openMANIPULATOR-X emanual and instrucable page about how to add and use vaccum tool to openManipulator-X.
And then the OpenMANIPULATOR source code is working based the ROBOTIS manipulator Library. please refer e-manual about this ROBOTIS manipulator Library.

Hi Kim
(under the open_manipulator.initOpenManipulator(platform_state); of the void setup() function in the .ino file).
To add code where can I find the source file.
From: Hye-Jong KIM<EMAIL_ADDRESS>Sent: Monday, June 24, 2019 8:08 PM
To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Cc: Cheng, Meng<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ROBOTIS-GIT/open_manipulator] I bought OpenManipulator. (#107)
[External Email]
Hi @zebrachenghttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zebracheng&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=DA-3CuF43w4EkbmPQ4vPljZyuKQq-AqClhGYyEPaepE&e=
Thank you for using our OpenMANIPULATOR-X.
The Unit of the gripper movement is 'm', not 'mm', and it means the moving distance of one gripper finger.
And the range of the grippper position is -0.009m to 0.009m. The gripper position of the open state is 0.009m, and it of close state is -0.009mm.
So that the 0.009 means that the gripper fingers gap is about 4cm.
And that is maximum value.
Please check that the gap is 4cm at the open state.
If it is not 4cm, It may be a situation that the gripper dynamixel does not move more due to the current limit.
If so, it is possible that the 4 Flange bush screws on the gripper are overtightened. Please loosen that a little.
Another way is to raise the current limit. please add below codes to source code.
(under the open_manipulator.initOpenManipulator(platform_state); of the void setup() function in the .ino file)
STRING gripper_dxl_opt_arg[2];
void *p_gripper_dxl_opt_arg = &gripper_dxl_opt_arg;
gripper_dxl_opt_arg[0] = "Goal_Current";
gripper_dxl_opt_arg[1] = "300";
open_manipulator_.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);
The value '300' can be changed in the range of 200 to 1193. Increasing this value increases the gripping force output by the Dynamixel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ROBOTIS-2DGIT_open-5Fmanipulator_issues_107-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAMODBQCUV5PFYAVQUOT232LP4FVXXA5CNFSM4H3C3O32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYOU4OA-23issuecomment-2D505237048&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=WHR3zJ-s68NFFy29blmnrkswczIotFvq-EWWSzb0DxQ&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMODBQDZ7HVBJIGIRLUXKATP4FVXXANCNFSM4H3C3O3Q&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=3uTmmHimOvX6fQwKthSfAbDxYBLi9J7w0L1pZpH0RFg&e=.

CONFIDENTIAL-

This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.

Hi Kim,
I found where to add the code .
open_manipulator_.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);
is not define in the scope.
Help
From: Hye-Jong KIM<EMAIL_ADDRESS>Sent: Monday, June 24, 2019 8:08 PM
To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Cc: Cheng, Meng<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ROBOTIS-GIT/open_manipulator] I bought OpenManipulator. (#107)
[External Email]
Hi @zebrachenghttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_zebracheng&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=DA-3CuF43w4EkbmPQ4vPljZyuKQq-AqClhGYyEPaepE&e=
Thank you for using our OpenMANIPULATOR-X.
The Unit of the gripper movement is 'm', not 'mm', and it means the moving distance of one gripper finger.
And the range of the grippper position is -0.009m to 0.009m. The gripper position of the open state is 0.009m, and it of close state is -0.009mm.
So that the 0.009 means that the gripper fingers gap is about 4cm.
And that is maximum value.
Please check that the gap is 4cm at the open state.
If it is not 4cm, It may be a situation that the gripper dynamixel does not move more due to the current limit.
If so, it is possible that the 4 Flange bush screws on the gripper are overtightened. Please loosen that a little.
Another way is to raise the current limit. please add below codes to source code.
(under the open_manipulator.initOpenManipulator(platform_state); of the void setup() function in the .ino file)
STRING gripper_dxl_opt_arg[2];
void *p_gripper_dxl_opt_arg = &gripper_dxl_opt_arg;
gripper_dxl_opt_arg[0] = "Goal_Current";
gripper_dxl_opt_arg[1] = "300";
open_manipulator_.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);
The value '300' can be changed in the range of 200 to 1193. Increasing this value increases the gripping force output by the Dynamixel.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ROBOTIS-2DGIT_open-5Fmanipulator_issues_107-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAMODBQCUV5PFYAVQUOT232LP4FVXXA5CNFSM4H3C3O32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYOU4OA-23issuecomment-2D505237048&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=WHR3zJ-s68NFFy29blmnrkswczIotFvq-EWWSzb0DxQ&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMODBQDZ7HVBJIGIRLUXKATP4FVXXANCNFSM4H3C3O3Q&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=gT7ZWVyX0jAnfixj1BGJ34fmLlRik6gU1PEeftnOM0k&s=3uTmmHimOvX6fQwKthSfAbDxYBLi9J7w0L1pZpH0RFg&e=.

CONFIDENTIAL-

This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.

sorry, it wasn't correct.
it was not open_manipulator_.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);,
it is open_manipulator.setToolActuatorMode(TOOL_DYNAMIXEL,p_gripper_dxl_opt_arg);.

Hi Kim,
The code that u provided that not help.
The R+ Manager is able to turn the ID15 0 degree to +90 or -90.
The suction cup code provided by Robotis is not working  because it did  not use ID15 servo .
This make the arm short reach.
For my application I need  ID11 to ID15 on my project. Application needs  longer reach.
Is there any way that you can help to show me how to modify gripper ( Gripper open or Gripper close )code to 0 to + 90 or -90 instead 0.009 or -0.009.
From: Hye-Jong KIM<EMAIL_ADDRESS>Sent: Monday, June 24, 2019 11:10 PM
To: ROBOTIS-GIT/open_manipulator<EMAIL_ADDRESS>Cc: Cheng, Meng<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [ROBOTIS-GIT/open_manipulator] I bought OpenManipulator. (#107)
[External Email]
Hi again,
Unfortunately, I can't directly contact you on phone or chat due to my another busy works, but I will reply asap on mails.
First of all, to apply your application, you have to add another tool such as vacuum tool at the end of dynamixel ID15. I think the vacuum tool is best choise to pick up the labels. Is that passible?
If you can, OpenMANIPUALTOR can work enough on your application.
Please refer openMANIPULATOR-X emanualhttps://urldefense.proofpoint.com/v2/url?u=http-3A__emanual.robotis.com_docs_en_platform_openmanipulator-5Fx_tool-5Fmodification_-23vacuum-2Dgripper&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=o-N2cVBE-ix7oBU9JuFoec25RULD9Bmn5moIhyVKgaA&s=6MZzUFJhzUE-ujdQZqwvPw6F28j3tABmIsbS5slKe1s&e= and instrucable pagehttps://urldefense.proofpoint.com/v2/url?u=https-3A__www.instructables.com_id_Vacuum-2DGripper-2DSystem-2DUsing-2DOpenCR_&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=o-N2cVBE-ix7oBU9JuFoec25RULD9Bmn5moIhyVKgaA&s=SUPGJvVxnEl8nPdUyEp2Au9F2Aqv3DsRrgNEW1MNANg&e= about how to add and use vaccum tool to openManipulator-X.
And then the OpenMANIPULATOR source code is working based the ROBOTIS manipulator Library. please refer e-manualhttps://urldefense.proofpoint.com/v2/url?u=http-3A__emanual.robotis.com_docs_en_software_robotis-5Fmanipulator-5Flibs_&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=o-N2cVBE-ix7oBU9JuFoec25RULD9Bmn5moIhyVKgaA&s=8IveypKXADgpy8KA6Iyt3pkOE8oREzYhTz6NNfxylbg&e= about this ROBOTIS manipulator Library.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ROBOTIS-2DGIT_open-5Fmanipulator_issues_107-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAMODBQHC5J7CRH5PYN5LIDDP4GK77A5CNFSM4H3C3O32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYO56DA-23issuecomment-2D505274124&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=o-N2cVBE-ix7oBU9JuFoec25RULD9Bmn5moIhyVKgaA&s=BoMqbaR-_s2X_C7EffOhbKAQDMKbBdqhtzQ6bjAgbRE&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMODBQB4NJV6W4PNDZEAGXDP4GK77ANCNFSM4H3C3O3Q&d=DwMCaQ&c=Qwsh1H-X9ypOoLLEcAIltQ&r=VK8JMXj9hwZUR9NDfn_6uQ&m=o-N2cVBE-ix7oBU9JuFoec25RULD9Bmn5moIhyVKgaA&s=iXVbyKc2kHp1zb3mQMH9m0g_WgNt6tV5xTV89IbECts&e=.

CONFIDENTIAL-

This email and any files transmitted with it are confidential, and may also be legally privileged. If you are not the intended recipient, you may not review, use, copy, or distribute this message. If you receive this email in error, please notify the sender immediately by reply email and then delete this email.

You can not modify the information about the structure of the manipulator in the source code of open_manipulator_chain of the existing example. If you refer to open_manipulator_vacuum.h in open_manipulator_chain_vacuum, you will know how to modify the information.
The source code you are using in OpenCR is in the github repository at the link below.
https://github.com/ROBOTIS-GIT/OpenCR
Look at the link below.
https://github.com/ROBOTIS-GIT/OpenCR/blob/master/arduino/opencr_arduino/opencr/libraries/OpenManipulator/src/open_manipulator_libs/src/open_manipulator.cpp
The following code is the part that declares the structure of the manipulator.
  addTool ("gripper", // my name
          "joint4", // parent name
          math :: vector3 (0.126, 0.0, 0.0), // relative position
          math :: convertRPYToRotationMatrix (0.0, 0.0, 0.0), // relative orientation
          15, // actuator id
          0.010, // max gripper limit (0.01 m)
          -0.010, // min gripper limit (-0.01 m)
          -0.015); // Convert unit from `meter` to` radian`

-0.015); // Convert unit from meter to radian is the part that converts Dynamixel angle and input value of send function.
If you change this to 1.0, the Dynamixel will move as the input value.
Of course, you must also change the limit. This value is in radians.
The details of this, as I explained before, are listed below.
http://emanual.robotis.com/docs/en/software/robotis_manipulator_libs/#usage-tutorials

This issue has been closed as there weren't recent activities. Please feel free to reopen this thread if there's any opinion to throw. Thanks.


Add some info on automated C/C++ code review/analysis

for example, using Codacy (with cppcheck) or SonarQube (with C++ plugin). Anyone using these in the projects?

My current C++ projects are not in public repos, so I'm not using them, but I've used cppcheck on my code locally before. It mainly checks for the kinds of errors you get in C, if you write nice modern C++, then it doesn't help all that much. Then again, most C++ code in the world is not nice modern C++, so I think it would be quite useful in most cases.
So yes, that would be good to have!

Related #30


Deploy Admin UI to dev environment

In order to ensure all production assets are tested consistently and thoroughly, the Admin UI needs to be deployed to the development environment.
Acceptance Criteria

[ ] The Admin UI is available the development environment.

@eddietejeda and @jessykacastillo do you use the admin UI? Trying to determine the priority of this story.

This is a good idea as part of standardizing the environments, but the Admin UI doesn't change very often. @jessykacastillo occasionally uses the production admin ui.


minted: doesn't handle framebreaks in beamer

Consider the following document:
---
header-includes:
  - \usepackage[outputdir=/tmp/pandoc]{minted}
---

# Hello world
## foo
~~~~~~~
foo bar
~~~~~~~

------

~~~~~~~
baz goo
~~~~~~~

When compiled to beamer pdf with
pandoc --standalone --pdf-engine=xelatex --pdf-engine-opt=-shell-escape --pdf-engine-opt=-output-directory=/tmp/pandoc --slide-level=2 --to beamer --no-highlight -o test.pdf test.md

It works (frame "foo" is split into two)
However, when compiled with minted filter like this:
pandoc --standalone --pdf-engine=xelatex --pdf-engine-opt=-shell-escape --pdf-engine-opt=-output-directory=/tmp/pandoc --slide-level=2 --to beamer --no-highlight --lua-filter minted.lua -o test.pdf test.md

It fails with an obscure error:
Error producing PDF.
! FancyVerb Error:
  Extraneous input ` baz goo \end {minted} \end {beamer@frameslide}\ifbeamer@tw
oscreenstext \beamer@dosecondscreennow {\begin {minted}[autogobble]{text} baz g
oo \end {minted} }\fi \ifbeamer@anotherslide \advance \beamer@slideinframe by 1
\relax \relax \expandafter \iterate \fi \let \iterate \relax \beamer@writeslide
ntry \beamer@reseteecodes ' between \begin{minted}[<key=value>] and line end
.
\FV@Error ...ncyVerb Error:^^J\space \space #1^^J}

l.107 \end{frame}

This error changes a lot depending on relative positions of code blocks, frames and line breaks, so I wasn't able to determine the exact cause or suggest a fix.
CC @svenevs

Do you get reliable behavior if you follow the suggested approach of md -> tex then tex -> pdf (do not use pandoc to go md -> pdf)?
https://github.com/pandoc/lua-filters/blob/master/minted/README.md#pdf-compilation
The linked issue was closed, but I don't think this is actually fixed. Presumably the unreliable / changing error is directly related to this, especially if you reuse the same directory each time without deleting it. It would be great if there was a better fix, but I'm not going to be able to fix it myself and I don't think the filter side can either.

No, the behavior is reproducible with md -> tex -> pdf too:
$ pandoc --standalone --pdf-engine=xelatex --pdf-engine-opt=-shell-escape --pdf-engine-opt=-output-directory=/tmp/pandoc --slide-level=2 --to beamer --no-highlight --lua-filter minted.lua -o test.tex test.md

$ xelatex -shell-escape -output-directory=/tmp/pandoc test
<...>
! FancyVerb Error:
  Extraneous input ` baz goo \end {minted} \end {beamer@frameslide}\ifbeamer@tw
oscreenstext \beamer@dosecondscreennow {\begin {minted}[autogobble]{text} baz g
oo \end {minted} }\fi \ifbeamer@anotherslide \advance \beamer@slideinframe by 1
\relax \relax \expandafter \iterate \fi \let \iterate \relax \beamer@writeslide
ntry \beamer@reseteecodes ' between \begin{minted}[<key=value>] and line end
.
\FV@Error ...ncyVerb Error:^^J\space \space #1^^J}

l.107 \end{frame}

?

The full tex file: https://0x0.st/i0KQ.tex


update spectrogram code to be more consistent

we now have a couple tf-decomposition functions we wrote (calc_mt_tfr and calc_cwt_tfr) as well as one from bmi3d that works in a completely different way (multitaper_lfp_bandpower).
a wrapper around calc_mt_tfr and calc_cwt_tfr to average across frequencies would be more consistent with the way multitaper_lfp_bandpower works. we should update the naming to be consistent, too.

i'm also unclear why these functions are in analysis when the mtfilter function is in precondition -- we should add a wrapper around mt_bandpass_filter to calculate band power across time into aopy.analysis, perhaps


Figure out why Tom can't export the homepage successfully

Reproducible test case, party on it!

This is fixed. It had to do with the fact that the area didn't yet exist in the destination locales and the commit being exported was later than the one that created it. So the fix was twofold:

Be tolerant: create missing areas when applying patches.
Implement support for exporting old commits, because there are more complicated scenarios where this still wouldn't be enough.

However more attention must continue to be lavished on improving the application of patches, new issues are being opened.